> /usr/lib/*/libzip/include/zipconf.h looks like multiarch file, > is it not the right place?
Indeed. The mentioned header file is platform-specific, so it might not be wise to put it under the general /usr/include directory structure. On the other hand, the libzip-dev package is not a Multi-Arch package, so you wouldn't expect the package to ship Multi-Arch-specific files: glaubitz@z6:~> apt-cache show libzip2:amd64 |grep Multi-Arch glaubitz@z6:~> apt-cache show libzip-dev:amd64 |grep Multi-Arch glaubitz@z6:~> I'm also not sure how sensible it is to ship -dev packages as Multi-Arch files since, as this case proofs, obviously creates more problems than it solves. The advantage of shipping Multi-Arch files in this case would be the possibility to cross-build. Since it is more sensible to build packages in a clean chroot anyway, you don't really win anything by making the -dev package Multi-Arch-capable. I therefore suggest that, at least for the time being, we apply Mateusz' patch and revert the package back to a non-Multi-Arch version such that other packages which build-depend on libzip will no longer FTBFS. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
