Source: libboost1.55-dev Followup-For: Bug #738538 > No, the -dev package is NOT multi-arch.
Dear Maintainer, is there a particular obstruction to marking it as multi-arch? I was surprised to notice that it wasn't, when that seemed the whole point of splitting a -tools-dev package. Listing the files in this package, it contains only the headers (not autogenerated, so common to all platforms) and an example, which seems quite safe. (Most) other boost -dev packages are in the same situation with an extra .a/.so pair which is safe as well, so I don't think there is anything to do except pasting the multi-arch line many times in the control file. The longest is obviously building and checking that the resulting x86 and x86_64 (at least) packages can be co-installed, and I can understand if you want to wait for the next upstream release to do that. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 armhf powerpc Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org