Bug#735442: libthrust: Why Multi-Arch allowed?
osamu at debian.org
Wed Jan 15 12:51:06 UTC 2014
I was learning Multi-Arch thing and looked around the sid archive :-)
libthrust-dev was the solo package claiming strange combination.
As I see the package, it is header file only (No static library.)
Although many other -dev packages are M-A: same since they have *.a
files in them, but this one is completely header only. So why not.
The header files seems to be not arch specific. (Which I expect it to be.)
(autotools-dev is an example of Multi-Arch: foreign)
I\s there any occasion same is required?
This "allowed" is claimed by few other packages (actually python* and cpp)
but they are "Architecture: any". (See below.)
Are you sure this Multi-Arch: is intentional one?
It does not make sense. (python and cpp seems to have reasons.)
PS: list of other MA: allowed packages:
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
More information about the pkg-nvidia-devel