On Wed, Feb 18, 2009 at 12:27:44PM +0000, Julian Gilbey <j...@debian.org> was heard to say: > On Fri, May 02, 2008 at 02:08:29AM +0200, nutzt...@web.de wrote: > > Package: aptitude > > Version: 0.4.11.2-1 > > Severity: wishlist > > > > /var/lib/dpkg/available is not created|updated complete with 'aptitude > > update', > > like 'dselect update' does. > > It is just updated peu-a-peu after 'aptitude install ...'. > > I've upped the severity of this one to "important". Sometimes, and I > can't pin down when or why, either aptitude, apt or possibly dpkg > leaves the /var/lib/dpkg/available file in a broken state. After > this, dpkg refuses to function, and the only way of fixing it that I > have found is to run "dselect update". It would make sense if > aptitude/apt-get update were to always fully update the > /var/lib/dpkg/available file to avoid this potential problem.
aptitude never touches /var/lib/dpkg/available, and neither does apt-get (which is what this bug is about, not that it touches the file wrongly). apt-cache can print an "available" file to stdout, but it doesn't replace the dselect one. Your problem is somewhere else. Do you perhaps have a cron job that tries to update the available file? Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
