Hi, Quoting Stepan Golosunov (2016-01-31 08:21:27) > And no, Arch:all is Arch:armhf on an armhf system. And dpkg does not > implement any mechanism to change that for one package.
to expand on Stepan's reply: dpkg distinguishes between the native architecture and the set of foreign architectures. All arch:all packages implicitly become packages of the respective native architecture of the system. This in turn means that if a foreign architecture package depends on an arch:all package, then that arch:all package has to be marked as multi-arch:foreign because at this point, the arch:all package is actually a native architecture package. You can read more about this here: https://wiki.ubuntu.com/MultiarchSpec#Dependencies_involving_Architecture:_all_packages and in the cited footnote: https://wiki.ubuntu.com/MultiarchSpec#fnref-b110b386874a9b24eaecd36fa24653a467ee27c4 So this was basically done because it would be very difficult to teach dpkg how to do it otherwise and nobody has done the work. If you want to know more about problems of multiarch and how it could be improved, you can read these informative wiki pages: https://wiki.debian.org/HelmutGrohne/MultiarchSpecChanges https://wiki.debian.org/Multiarch/InterpreterProposal You might want to reassign this bug to libgtksourceview2.0-common to ask its maintainers whether marking that package as Multi-Arch:foreign would make sense or not. Thanks! cheers, josch
signature.asc
Description: signature
