tag 673190 wontfix thanks Hi,
On Wed, 2012-05-16 at 22:04:30 +0200, Carsten Hey wrote: > Package: dpkg > Version: 1.16.3 > Severity: wishlist > dpkg-query --list should add arch suffix to all foreign arch packages. > > # dpkg --print-architecture > amd64 > # dpkg -l sc | grep ' sc' | tr -s ' ' > ii sc 7.16-3 Text-based spreadsheet with VI-like keybindings > # apt-get remove sc > ... > Package 'sc' is not installed, so not removed. Did you mean 'sc:i386'? > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > # dpkg -s sc | grep Arch > Architecture: i386 > > Actually there are two bugs shown above. One is that dpkg -l omits > important information. This has been discussed at length on the debian-dpkg list. Only changing foreign packages to be always arch-qualified would make the ouput inconsistent with the rest of the command's output, which need to always arch-qualify them for M-A:same because those are the ambiguous ones, and single-instanced packages should not really be arch-qualified because there will always only be a single instance, and them being considered foreign might change in case dpkg gets cross-graded, or the frontend (apt) for that matter. As long as the user enabled a foreign architecture, and the dependencies are fulfilled, I don't see why the fact that it's foreign or not is really important. If the user really wants to know there's always more explicit and reliable ways to query that, with dpkg-query -W for example. > The other is that apt-get only removes foreign packages if either the > arch suffix is added or if the package is not available on the native > architecture. The reasoning by apt's maintainers is that in the above > case sc:i386 must explicitly have been installed, which is obviously > wrong since that a packages is available on one architecture now does > not mean that it has been available on this architecture in the past and > apt installs foreign packages if the architecture suffix is not added > and the package does not exist on the native architecture. I think it's unfortunate that the command-line semantics when specifying packages is different between dpkg and apt, but the semantics dpkg uses are the ones that are required to properly support robust and safe cross-grading, and I happen to find the apt ones confusing when I want to get information about a foreign package. In any case I'm tagging this wontfix for now, and will be closing in a bit if no convincing new arguments are brought up. regards, guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
