Your message dated Thu, 22 Jan 2009 17:21:34 +0000
with message-id <[email protected]>
and subject line Re: found PURGE
has caused the Debian Bug report #511726,
regarding remove database entry upon a package purge
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
511726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511726
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debconf
Version: 1.5.24
Severity: wishlist
In /var/cache/debconf do config.dat and templates.dat just grow and
grow, never removing cruft from purged packages?
$ debconf-show --listowners|xargs dpkg -l
shows lots that are long gone.
I looked through the documentation but couldn't find anything about
removing an entry upon package purge. Ah ha:
$ man debconf-set-selections|grep -B1 away
or are installed. Otherwise you can end up with values in the database
for uninstalled packages that will not go away, or with worse problems
In my ideal, installing and then purging a package should just leave
behind a log entry at most.
Anyway, I was hoping to compare config.dat from machine A vs. from
machine B, but I couldn't find any "--forget-old-unavail" cleanup
function, like dpkg has.
You might say "well the user might one day want to install again, and
we want to give him familiar defaults." OK, but still I want to do a
yearly --forget-old-unavail.
OK, to do my comparison between the machines I will try
$ set $(debconf-show --listowners|xargs dpkg -l|
perl -alnwe 'print $F[1] if $F[0] eq "ii"')
$ debconf-show $@ > debconf_settings
which should be cruft free, and compare it to the same file from
machine 2.
And to actually clean up the databases, I would probably use
debconf-copydb configdb newdb --owner-pattern=\
$(echo $@|perl -plwe 's/\w+/^$&\$/g;tr/ /|/') ...
--- End Message ---
--- Begin Message ---
On Thu, Jan 15, 2009 at 06:16:10AM +0800, [email protected] wrote:
> OK, in /usr/share/doc/debian-policy/debconf_specification.html I found
> PURGE Call this in your postrm when your package is purged. It removes
> all templates and questions your package has generated.
> This will probably be the key for me to clean up behind packages that
> forgot to...
Any package that uses dh_installdebconf (the vast majority) already gets
this right. For the odd package that fails to do so, file bugs against
the individual packages.
--
Colin Watson [[email protected]]
--- End Message ---
