Bug#545366: dselect 1.15.4 does not distinguish between new and old packages
reopen 545366 thanks dselect 1.15.4.1 (with dpkg 1.15.4.1) still does not distinguish between new and old packages. This makes dselect mostly useless on upgrades and completely useless on adding new repositories. The only difference between 1.15.4 and 1.15.4.1 is that former marks new and old packages as new, and the latter marks new and old packages as old. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551638: Bug#545366: dselect 1.15.4 does not distinguish between new and old packages
Version: 1.15.4.1 On Sun, 25 Oct 2009, Piotr Engelking wrote: The only difference between 1.15.4 and 1.15.4.1 is that former marks new and old packages as new, and the latter marks new and old packages as old. That's what we wanted. Closing this bug again. The fact that it doesn't keep track of new packages is tracked in #551638 and is not release critical for us. Please use the other bug for further discussion. Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551638: Bug#545366: dselect 1.15.4 does not distinguish between new and old packages
Raphael Hertzog hert...@debian.org: The only difference between 1.15.4 and 1.15.4.1 is that former marks new and old packages as new, and the latter marks new and old packages as old. That's what we wanted. Closing this bug again. The fact that it doesn't keep track of new packages is tracked in #551638 and is not release critical for us. While the change was, indeed, intended, it doesn't change the fact that it does nothing to fix the problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545366: dselect 1.15.4 does not distinguish between new and old packages
severity 545366 serious thanks On Tue, 08 Sep 2009, Petr Vandrovec wrote: IMHO change should be reverted until old functionality can be achieved through some other way - unless you can achieve such functionality today. I'd like to remind everybody that we're looking for someone to step up and maintain dselect: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282283 Here's your chance instead of requesting an instant fix from people who would rather not have to maintain dselect as part of dpkg. I'll mark this bug as RC so that it doesn't get into testing, you're free to downgrade dpkg in the mean time. Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545366: dselect 1.15.4 does not distinguish between new and old packages
Yes please, revert that commit. dselect is currently unusable. regards, Domenico -[ Domenico Andreoli, aka cavok --[ http://www.dandreoli.com/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545366: dselect 1.15.4 does not distinguish between new and old packages
Hi! On Mon, 2009-09-07 at 09:43:37 +0200, Sven Joachim wrote: 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 Hrmmmf, ok missed that one when doing the automatic forget change on dpkg... 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. The installability problems I assume is due to some transition going on in unstable right now. 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. The “tmp.i” file is normal, yes. 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. The problem is that dselect used the status file to track not seen and seen not-installed packages as either want_unknown or want_purge want states. And was setting all want_unknown packages to want_purge on normal exit (not using X keyibindig). This increases the status file, the parsing and processing time when doing dependency resolutions and package iterations for everyone, and just to be able to show new packages on dselect. The correct solution here is not to revert the change, but to store the seen/not-seen information in another place, in a similar way as how apt/aptitude do it. And ideally in a unified place which all front-ends can share, so we avoid duplication. I'll put it on the pending stuff to discuss with the front-end developers. regards, guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545366: dselect 1.15.4 does not distinguish between new and old packages
Guillem Jover napsal(a): Hi! This increases the status file, the parsing and processing time when doing dependency resolutions and package iterations for everyone, and just to be able to show new packages on dselect. The correct solution here is not to revert the change, but to store the seen/not-seen information in another place, in a similar way as how apt/aptitude do it. And ideally in a unified place which all front-ends can share, so we avoid duplication. IMHO change should be reverted until old functionality can be achieved through some other way - unless you can achieve such functionality today. Petr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545366: dselect 1.15.4 does not distinguish between new and old packages
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, maybe it applies by error on the available file as well and thus it believes that all packages are new everytime? Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545366: dselect 1.15.4 does not distinguish between new and old packages
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
Bug#545366: dselect 1.15.4 does not distinguish between new and old packages
Raphael Hertzog napsal(a): On Sun, 06 Sep 2009, Petr Vandrovec wrote: 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, maybe it applies by error on the available file as well and thus it believes that all packages are new everytime? 224f0285abc304bec059e61447781... is first bad commit commit 224f0285... Author: Guillem Jover guil...@debian.org Date: Sun Jul 12 20:11:53 2009 +0200 Obsolete --forget-old-unavail On parse mark not-installed leftover packages for automatic removal from the database on next dump ... Closes: #94, #429262 And while we are on it, checkin 7fa96f35... (disable default automake paths) causes FTBFS on my box. Petr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545366: dselect 1.15.4 does not distinguish between new and old packages
Package: dselect Version: 1.15.4 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. Thanks, Petr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
