On 2009-09-07 09:11 +0200, Raphael Hertzog wrote: > On Sun, 06 Sep 2009, Petr Vandrovec wrote: >> Since today's update run dselect is completely confused and does not >> remember which packages are new and which are old - it lists all >> available and not installed packages as new, again and again. And >> not only that, it also marks some of them for installation although >> I do not want them (and some are not installable at all - for some >> reason it wants to install libsasl2 which is not installable >> together with libsasl2-2). I see that it updates available & >> status, they seem to contain valid data, but on load it somehow >> ignores them. >> >> Besides that it creates some strange /var/lib/dpkg/updates/tmp.i >> which is full of lines saying '##padding', but other than that I do >> not see what can be wrong, and unfortunately diff between 1.15.3.1 >> and 1.15.4 is quite huge. > > You can use "git bisect" to isolate the problem more precisely. My bet > would be on the code that auto-cleans up the status database,
Certainly. FWIW, the problem occurs also if only dpkg is upgraded to 1.15.4 and dselect stays at 1.15.3.1. > maybe it applies by error on the available file as well and thus it > believes that all packages are new everytime? Given that the available package is as big as ever and dselect shows every package as new even after you run "sync-available" (from the dctrl-tools package), this does not seem to be the case. Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
