perezme...@gmail.com writes: > On Thursday 09 January 2014 02:14:58 Dima Kogan wrote: >> The previous message included a patch that added multi-arch:same tags to >> 4 packages. I had trouble building these packages, so I added those tags >> to the pre-built packages already in Debian/experimental. I then tried >> to co-install these to make sure that adding those tags was safe. 3 of >> the 4 packages are fine. However in qtbase5-dev there's a conflicting file: >> >> /usr/include/qt5/QtCore/qconfig.h >> >> This is an issue in Ubuntu also, but I don't think they know it yet >> (I'll comment on their bug shortly). > > Hi Dima! As you have just found, there are reasons why this packages aren't > marked as m-a: same: they are not. They vary between archs, so you can't make > them m-a: same. > > You can take a look at, for example, usr/include/qt5/QtCore/qconfig.h from > different archs (I took armhf, amd64 and s390x, for example). > > Making the dev packages m-a: same would be a bug, so I'm closing this report.
Hi Lisandro. Thank you for replying. The bug isn't simply that there are missing tags, but rather that you can't co-install qt5 -dev packages, thus making cross-builds impossible. Does it not make sense to keep this open to keep track of this feature as it is developed? In the spirit of keeping track, are there other roadblocks to multi-arching this? I tried to co-install the 4 packages my patch touched, and this was the only conflicting file. Thanks dima -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8761ptgijh....@secretsauce.net
