On 2010-02-16 00:32 +0100, Zlatko Calusic wrote: > Package: dselect > Version: 1.15.5.6 > Severity: normal > > Although NOTHING depends on libunwind7 and libunwind7-dev, as soon as > I run update in dselect, those two packages are silently marked for > installation.
That is because these packages are of priority standard or higher. I have filed bugs[0,1] against the ftp.debian.org pseudopackage that the priorities should be downgraded. > It feels like Windows(tm), dselect is doing things behind my > back. It's very annoying... How about stopping using dselect then? It has _always_ selected new packages of priority >= standard for installation. Considering that priorities are often bogus, this is a behavior that I find most undesirable, but changing it may upset other people. > The packages are easily removed afterwards, but next time I run > dselect, it installs it again. And again, and again... Argh... That is because it treats every package as new, a bug[2] that probably warrants RC severity. You're welcome[3] helping to fix it. Sven 0. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570059 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570063 2. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559519 3. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282283 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
