On Thu, Feb 19, 2009 at 03:10:41PM +0000, Julian Gilbey <j...@debian.org> was heard to say: > On Wed, Feb 18, 2009 at 09:09:40AM -0800, Daniel Burrows wrote: > > On Wed, Feb 18, 2009 at 04:08:41PM +0000, Julian Gilbey <j...@debian.org> > > was heard to say: > > > Then there's this: > > > > > > burnside:~ # ls /etc/apt/apt.conf.d/ > > > 01autoremove 20archive 90rkhunter > > > 10periodic 50unattended-upgrades 99-localepurge > > > 15update-stamp 70debconf 99update-notifier > > > > > > I don't know if any of these would be of significance? > > > > If you grep for "available" or "/var/lib/dpkg" in those, does > > anything interesting show up? > > The culprit seems to be dpkg itself; at the end of running "dpkg > --unpack ..." (called from aptitude), the available file is updated > (or at least touched); the same happened at the end of "dpkg > --configure ...". > > Turns out this has been reported against dpkg itself, so I guess the > severity of this aptitude bug should be returned to wishlist.
Better yet, it can be reassigned to dpkg and merged with the existing bug. Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
