On Wed, 2012-11-28 at 14:35:21 +0000, Ansgar Burchardt wrote: > Package: dpkg-dev > Version: 1.16.9 > Severity: minor > File: /usr/bin/dpkg-architecture > > dpkg-archtecture -iany-armel does not work as expected, ie. it returns > false on armel: > > % dpkg-architecture -aarmel -iarmel; echo $? > 0 > % dpkg-architecture -aarmel -iany-armel; echo $? > 1 > > But returns true for -iany-arm: > > % dpkg-architecture -aarmel -iany-arm; echo $? > 0 > % dpkg-architecture -aarmel -ignueabi-any-arm; echo $? > 0 > > This happens as the actual comparison is done on triplets having the form > > gnueabi-linux-arm (armel) > any-any-armel (any-armel) > > However the man page for dpkg-architecture states: "-iarchitecture-wildcard" > and "architecture wildcard" is said to have the general form "<kernel>-<cpu>".
Precisely because it's the <cpu> and not the <arch>, as can be seen from «dpkg-architecture -aarmel -qDEB_HOST_ARCH_CPU». I can well concede that though, that this might not seem intuitive, but then lots of things in dpkg architecture names aren't either (like the omission of the kernel for Linux architectures, or that mipsel does not have mips as cpu...). Something that we could do is warn if a non-wildcard component of a Debian triplet is unknown, like the armel in any-armel there. Also maybe try to clarify these things a bit more in the man page. I can work on that. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
