Package: libgwenhywfar-core-dev Version: 4.20.0-5 Severity: important User: helm...@debian.org Usertags: rebootstrap File: /usr/bin/gwenhywfar-config Control: affects -1 + src:libaqbanking
After installing libgwenhywfar-core-dev:i386 on an amd64 system, I get: $ gwenhywfar-config --libraries Package gwenhywfar was not found in the pkg-config search path. Perhaps you should add the directory containing `gwenhywfar.pc' to the PKG_CONFIG_PATH environment variable No package 'gwenhywfar' found $ echo $? 0 $ This is not useful. In earlier versions, gwenhywfar-config used to work. The regression is caused by debian/patches/multiarch_support_in_gwenhywfar-config_script.patch. The patch looks useful from the outset, because it enables marking libgwenhywfar-core-dev Multi-Arch: same in theory. Think further though. The purpose of Multi-Arch: same is to be able to install the package for multiple architectures. Given that there is only one native architecture at any one time, it will be installed for some foreign architecture when Multi-Arch: same is being useful. And that is precisely the case that is now broken. So before the patch, you could install libgwenhywfar-core-dev for any single architecture and it would work. After the patch, you can install it for as many architectures as you want, but it only works for the native one. I think this is a strict regression. Please revert the patch (and yes, that means removing Multi-Arch: same). If you really want Multi-Arch: same, the *only* option is to remove gwenhywfar-config. Other packages (e.g. libgpg-error-dev) are not Multi-Arch: same for the very same reason. That's not perfect, but good enough for the vast majority of cases. The consequence is that cross building libaqbanking is broken at the moment. Helmut
