Package: sks Version: 1.1.4-2.1+b1 Severity: important When sks is initially installed the file /var/lib/sks/berkeley_db.active which should hold information on the current Berkeley DB version of the key database is missing thus causing any follow-up attempt to configure the package to fail after several gigabytes of data have been backed up. The failure is caused due to the fact that if the file above is missing the post-install script falls back to Berkeley DB 4.7 while current releases of Debian might already have db5.1 or db5.3 installed.
Thus it might be nice to have the script detect the actual version of Berkeley DB if the status file to indicate this information was missing. Regards, BenBE. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'stable'), (750, 'experimental'), (700, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sks depends on: ii adduser 3.113+nmu3 ii db-util 5.3.0 ii libc6 2.18-4 ii libdb5.3 5.3.28-3 ii logrotate 3.8.7-1 ii zlib1g 1:1.2.8.dfsg-1 sks recommends no packages. Versions of packages sks suggests: ii postfix [mail-transport-agent] 2.10.2-1 ii procmail 3.22-21 -- Configuration Files: /etc/default/sks changed [not included] /etc/sks/membership changed [not included] /etc/sks/sksconf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
