Package: sks Followup-For: Bug #678924 IMHO the best way to handle this situation is with a debconf question defaulting to "don't make a backup". A debconf question has several advantages: - It can be preseeded to avoid the question during installation - An explanation can be show to the user to make an informed decision (about the risk of the upgrade) - It's the standard way to handle packaging situation without clear default.
And please don't store the backup in /var/backups. This directory contains backup copies of essential system state (mainly package manger and user accounts). I usually backup this to a remote location. I would be very surprised if it suddenly contains several GB of data that is easily recreatable. I guess that only a minority of keyservers don't peer with the global public keyserver network and therefore contain really valuable data in their database. Gaudenz -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
