backuppc (4.4.0-3) unstable; urgency=medium

  This is a major new version of BackupPC and existing configuration
  files will need substantial work to integrate the changes.
  The package will not attempt to do this automatically.

  In particular, if you back up client systems using the rsync method,
  you will need the backuppc-rsync package installed in order to take
  full advantage of the rsync protocol including BackupPC-specific changes.
  It is co-installable with the normal rsync Debian package.

  You also need to update /etc/backuppc/config.pl and add the line:

    $Conf{RsyncBackupPCPath} = "/usr/libexec/backuppc-rsync/rsync_bpc";

  Other settings such as $Conf{RsyncClientCmd} have had their meanings
  changed or even been removed altogether. For further details, please see
  /usr/share/doc/backuppc/UPGRADING

 -- Jonathan Wiltshire <jmw@debian.org>  Sun, 23 Aug 2020 10:45:19 +0100

backuppc (4.4.0-1) unstable; urgency=medium

  High I/O load after the first startup of BackupPC 4 after an upgrade
  from BackupPC 3 is expected as BackupPC will first convert the last
  backup of each backed up host into the new on-disk format of BackupPC 4.
  This will be listed as state "backup starting" in the web interface.

 -- Jonathan Wiltshire <jmw@debian.org>  Sun, 23 Aug 2020 10:45:19 +0100

backuppc (3.3.2-1) unstable; urgency=medium

  Debian's default BackupPC configuration file for Apache now restricts
  access to BackupPC to localhost by default because by default HTTPS is
  not enforced, i.e. "SSLRequireSSL" is commented out.

  Please refer to the comments in /etc/backuppc/apache.conf
  respectively /etc/apache2/conf-available/backuppc.conf what to
  uncomment and comment after having setup HTTPS, e.g. with certbot.

 -- Axel Beckert <abe@debian.org>  Wed, 14 Nov 2018 00:40:28 +0100
