On Tue, 27 Oct 2009, Takehiko Abe wrote: > >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. > > What about the "it also marks some of them for installation although I > do not want them" part of the original report? That makes dselect > unusable. Is it not enough to be release critical?
Why would it do that? I supposed that this was a consequence of all packages being marked as new and somehow re-considered for installation. > Am I missing something? Puzzled. Yes, dselect has no real maintainer. Step up if you care about it. Our goal is to get rid of it within dpkg as soon as possible (i.e. when libdpkg is advanced enough for dselect). 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
