On 09/23/2012 11:56 AM, Wayne Topa wrote:
On 09/23/2012 11:11 AM, The Wanderer wrote:
Has the procedure for working with 'dpkg --set-selections' changed at
some
point?
Yes & No. check with 'listbugs dpkg' when in doubt.
wtopa@dj:~$ bugs dpkg
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of dpkg (-> ) <marked as done in some version>
#679641 - dpkg: if mcstransd is unexpectedly stopped then dpkg uses
invalid SE Linux context (Fixed: dpkg/1.16.6 dpkg/1.15.8.13)
serious bugs of dpkg (-> ) <unfixed>
#684776 - dpkg incorrectly complains about conffile contents being
different for MA packages
Summary:
dpkg(2 bugs)
This is what I got at 11:55 EST
I get the same thing, but I don't see how any of that bears on the
problem I
described.
I do know how to report a bug and how to check to see whether it's
already been
reported. However, since this has been in place for as long as I've seen
it be
without a fix, I wanted to verify that it wasn't intended behavior (and
that it
isn't a "just me" situation) before trying to handle it as a bug.
At the very least I know it isn't *absolutely* just me; it was reported and
discussed earlier this year at
http://forums.debian.net/viewtopic.php?f=17&t=79006
But that's the only mention of it I've found so far - so either very few
people
use the 'set-selections' functionality for anything other than
already-installed
packages, or this doesn't happen for everyone.