[Bug 1576960] Re: apt-mark prints ambiguous package name

2016-05-01 Thread Jarno Suni
$ dpkg-query -s "libfontconfig1" prints the status of the amd64 package, but $ dpkg-query -W -f='${binary:Package}\n' "libfontconfig1" prints the package name with both amd64 and i386 architectures. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribe

[Bug 1576960] Re: apt-mark prints ambiguous package name

2016-05-01 Thread David Kalnischkies
I presume that works (I would be using nativearch="$(dpkg --print- architecture)" through – and poking directly into info/ is discouraged. Checking exitcode of commands like 'dpkg-query -s "$1"' might be better), but note that with a "foo:all" you aren't talking about a package as packages can't ha

[Bug 1576960] Re: apt-mark prints ambiguous package name

2016-05-01 Thread Jarno Suni
The architecture of e.g. debconf is not some specific architecture, but "all". So when you want to use the output of apt-mark as an argument for dpkg(-query), you need to tune the name by a shell function like this, right? : dpkg-pkgname() { nativearch=$([ "$(uname -i)" = "x86_64" ] && echo amd6

[Bug 1576960] Re: apt-mark prints ambiguous package name

2016-05-01 Thread Jarno Suni
Correction, the last amd64 should be replaced by "$nativearch". -- 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 thi

[Bug 1576960] Re: apt-mark prints ambiguous package name

2016-04-30 Thread David Kalnischkies
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-ar