[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#672160: Directory /boot/console-setup

On Sat, May 12, 2012 at 03:04:31PM +0300, Anton Zinoviev wrote:
> On Thu, May 10, 2012 at 02:54:16PM -0700, Steve Langasek wrote:
> > On Thu, May 10, 2012 at 07:43:46PM +0300, Anton Zinoviev wrote:
> > > Currently it creates files in the directory /etc/console-setup.  As 
> > > a result when the package is purged it is impossible to tell which 
> > > files in /etc/console-setup are automatically generated (so they 
> > > have to be removed) and which are put there by the admin (so we are 
> > > not permitted to remove them).

> > I think your premise here is false.  The /etc/console-setup directory is
> > owned by the console-setup package; there are certain predictable filenames

> The file names are not predictable unless one has acces to all previous 
> versions of the configuration files.  But even if they were predictable 
> we would need MD5 or other hash to be sure the files have not be 
> modified somehow by the admin.

No, you absolutely do *not* need this.  The policy rule isn't "on purge,
remove all config files if the admin hasn't edited them", it's "on purge,
remove *all configuration files*".

This "cache" subdirectory is pointless complexity.  The existing rm -rf
behavior is appropriate.

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org

Attachment: signature.asc
Description: Digital signature

Reply to: