Bug#743817: libpoppler-dev: Multi-arch -dev packages

2014-04-06 Thread Marc Glisse
On Sun, 6 Apr 2014, Pino Toscano wrote: What's the use case for marking libpoppler-dev as m-a: same? Uh, so I can cross-compile stuff? (aka "gcc -m32" in the simplest case) Alone it has no value in being so. Even with libpoppler-private-dev? Some dependencies may not be multiarch yet (qt

Bug#743817: libpoppler-dev: Multi-arch -dev packages

2014-04-06 Thread Pino Toscano
severity 743817 wishlist thanks Hi, On 2014-04-06 21:13, Marc Glisse wrote: Package: libpoppler-dev Version: 0.24.5-3 Severity: normal Dear Maintainer, it is good that libpoppler44 is Multi-Arch: same (thanks), but it would be even better if the -dev packages were as well. libpoppler-dev has

Bug#743817: libpoppler-dev: Multi-arch -dev packages

2014-04-06 Thread Marc Glisse
Package: libpoppler-dev Version: 0.24.5-3 Severity: normal Dear Maintainer, it is good that libpoppler44 is Multi-Arch: same (thanks), but it would be even better if the -dev packages were as well. libpoppler-dev has all its content in /usr/lib/$arch (except for changelog and copyright), so it se