sks (1.1.6-11) unstable; urgency=medium

  sks no longer uses /etc/default/sks.  That file was historically used to
    determine whether the service should be enabled or not by default.
    Instead, you should use your standard system manager commands
    (e.g. "systemctl enable sks" or "udpate-rc.d sks enable", or their
    corresponding "disable" counterparts).

 -- Daniel Kahn Gillmor <dkg@fifthhorseman.net>  Wed, 02 Aug 2017 11:34:48 -0400

sks (1.1.5-2) unstable; urgency=low

  sks now uses the standard /var/backups directory rather than /var/backup
    for db upgrades. Please move or delete the old backups in /var/backup
    for yourself. On purge, both directories get deleted.

 -- Christoph Martin <christoph.martin@uni-mainz.de>  Wed, 15 Oct 2014 16:23:56 +0200

sks (1.1.1+dpkgv3-6.1) unstable; urgency=low

  sks now uses a Berkeley DB version 5.1 without XA environment.
  The postinst script should upgrade the database automatically.
  There will be backup in /var/backups/sks in case something went
  wrong.

 -- Ondřej Surý <ondrej@debian.org>  Fri, 13 May 2011 12:38:29 +0200

sks (1.1.1+dpkgv3-1) unstable; urgency=high

   *** NOTE ***

  sks now uses a different BerkelyDB version.
  You need to upgrade your database prior to starting sks.
  Please read README.Debian for instructions

 -- Christoph Martin <christoph.martin@uni-mainz.de>  Wed, 25 Aug 2010 17:55:07 +0200
