The names aren't ambiguous – if apt prints no architecture it is ALWAYS
the native architecture. This is this way for compatibility reasons as
apt hadn't previously printed any architecture – because they were all
native – so old tools, scripts, processes, … sticking to the common case
of single-architecture systems do not need to be touched/fixed.
It just happens to be a different convention than dpkg is using – which
prints the architecture only if it could be ambiguous, like for all
packages marked as M-A:same (Since recently it also shows the
architecture for M-A:foreign packages of a non-native architecture, too)
and in exchange requires an architecture to be given (for M-A:same) even
if it isn't ambiguous [which broke pre-multiarch tools, but most tools
interacting with dpkg do this via apt which shielded them].
APT can't operate with this convention as basically every package is
available in all architectures, so a package name is always ambiguous
and hence all package names would need to be fully arch-qualified all
the time. That would be a lot of noise…
** Changed in: apt (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576960
Title:
apt-mark prints ambiguous package name
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1576960/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
