Bug#672160: console-setup: unowned files after purge (policy 6.8, 10.8)
On Wed, May 09, 2012 at 06:55:56PM +0200, Andreas Beckmann wrote:
> On 2012-05-09 17:58, Anton Zinoviev wrote:
> > I don't know how I can fix this. There is no way to tell whether a file
> > in /etc/console-setup has been created by console-setup or it is some
> > unrelated font or keyboard file put there by the admin. (The file names
> OK, that sounds difficult to fix ...
> We can add /etc/console-setup/*.gz to the ignore list in piuparts and
> you can mark this bug as wontfix.
Well, it is not wontfix, becase I want to fix it. :)
Right now I am considering one possible solution. Instead of creating
files directly in /etc/console-setup, the package can put the files in
/etc/console-setup/.cache Then it will be possible to remove this
directory when the package is purged or even only removed. There could
be a file /etc/console-setup/.cache/README to explain the purpose of
this directory and to warn the admin that the package is free to remove
or overwrite at any time any files in this directory.
Perhaps an even better alternative is to use a directory
/boot/console-setup. I am going to ask in debian-devel for suggestions.