Package: sks Version: 1.1.3-1 on trying to upgrade from sks 1.1.1 to 1.1.3, the postinst configure invocation appears to try to make a full copy of the key database to /var/backup/sks. This file is large (7.5 GiB at the moment).
If /var/backup/sks isn't large enough to make the copy, the postinst script fails: Stopping sks daemons: sksrecon.. sksdb.. done. Unpacking replacement sks ... Setting up sks (1.1.3-1) ... Installing new version of config file /etc/cron.daily/sks ... Installing new version of config file /etc/init.d/sks ... Installing new version of config file /etc/sks/mailsync ... debian-sks uid check: ok debian-sks homedir check: ok cp: writing `/var/backup/sks/20120624-230002/DB/key': No space left on device dpkg: error processing sks (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... /usr/bin/mandb: can't write to /var/cache/man/15214: No space left on device Errors were encountered while processing: sks Maybe it would be more polite to check if there's enough room for a full copy before filling up /var, and bailing out early with suggestions about freeing up space? (or provide a way for a reckless administrator to avoid the backup step before launching the upgrade?) Thanks for maintaining sks in debian! --dkg
pgpB4xClyfM8s.pgp
Description: PGP signature
