While updating my natty install on my beagle board xm, I ran into the following
Preparing to replace libjpeg-turbo62 1.1.90-1inaro6 (using .../libjpeg-turbo62_1.1.90-1inaro6_armel.deb) ... DEB_HOST_MULTIARCH is not a supported variable name at /usr/bin/dpkg-architecture line 214. dpkg: error processing /var/cache/apt/archives/libjpeg-turbo62_1.1.90-1inaro6_armel.deb (--unpack): subprocess new pre-installation script returned error exit status 9 DEB_HOST_MULTIARCH is not a supported variable name at /usr/bin/dpkg-architecture line 214. dpkg: error while cleaning up: subprocess new post-removal script returned error exit status 9
This doesn't make much sense as
dpkg-query -l multiarch-support Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-====================-====================-======================================================== ii multiarch-support 2.13-0ubuntu13 Transitional package to ensure multiarch compatibility
Least I thought that's all you needed to have installed for multiarch support, judging by what I see in http://wiki.debian.org/Multiarch/Implementation
Am I missing something obvious?
Thanks!
+++ Tom Gall [2011-09-07 09:23 -0500]:
While updating my natty install on my beagle board xm, I ran into the following
Preparing to replace libjpeg-turbo62 1.1.90-1inaro6 (using .../libjpeg-turbo62_1.1.90-1inaro6_armel.deb) ... DEB_HOST_MULTIARCH is not a supported variable name at /usr/bin/dpkg-architecture line 214.
That's an error from dpkg-architecture, which is part of dpkg-dev. I presume the version of dpkg-dev on your board is too old to know about DEB_HOST_MULTIARCH (prior to 1.16.0).
This doesn't make much sense as
dpkg-query -l multiarch-support
That's not the package that's complaining.
Wookey
On Wed, 7 Sep 2011 15:46:32 +0100, Wookey wookey@wookware.org wrote:
This doesn't make much sense as
dpkg-query -l multiarch-support
That's not the package that's complaining.
But shouldn't it depend on a version of dpkg-dev that supports multiarch?
Maybe it's that we need a multiarch-support-dev package to do that?
Thanks,
James