On 15.04.2010 15:27, Raphaël Hertzog wrote:
tag 556889 pending thanksHello, Bug #556889 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=29fe363
First of all, i'd like to thank Robert for his work on the issue, to at least somewhat improve situation for dselect users, until proper fix is in place.
OTOH, if I'm reading the patch and description correctly, this change will kill new package detection in dselect, which I believe is one of the main features why aging dselect has so many trusty followers after all these years. For us that live with sid and like to upgrade often, it's certainly a killer feature. No new package enters the Debian repository, unless we check it out first and see if it's worth installing or not. :)
So, unless somebody disputes that the patch really disables new package detection, I guess many of us will probably stay with 1.15.3.1, because it's still the most stable and functional version. Though the situation only gets worse in time, of course. Because now other packages start to depend on newer version of dpkg, which means they have to be put on hold too. That happened to cron package, btw, a day or two ago.
I also tried other workarounds, namely using equivs package to block unwanted packages from the system, and that was only worse. Spent many hours working on that, all in vain, because self-installing packages just kept coming, which forced repackaging equivs-dummy package on multiple machines... :(
Too bad dselect was written in C++, otherwise I'd have invested my own time trying to fix this, long time ago. Unfortunately, I don't grok C++, just plain C.
Regards, -- Zlatko -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
