Re: Multi-Arch and debian/control
* Thomas Schmitt <scdbackup@gmx.net>, 2015-09-21, 12:45:
while preparing the correction for a buildd failure on Debian
GNU/kFreeBSD i got a lintian complaint from kfreebsd-i386 7.9 (the
current "stable"):
E: libburn4: missing-pre-dependency-on-multiarch-support
I found
https://wiki.debian.org/Multiarch/Implementation#dh.281.29_and_autotools
This page seems to be recent, as it talks of "debhelper (>= 9)".
It prescribes to add to multi-arch dynamic library packages
Pre-Depends: ${misc:Pre-Depends}
Multi-Arch: same
Is this still a valid prescription ?
"Pre-Depends: ${misc:Pre-Depends}" was necessary to squeeze->wheezy
upgrades; it is no longer required. In fact, debhelper (>= 9.20150501)
won't populate this substvar.
(Why then is amd64 Sid lintian silent about it ?)
This tag was removed in lintian 2.5.13.
I came to debian-policy, "8.2 Shared library support files":
"If your package contains files whose names do not change with each
change in the library shared object version, you must not put them in
the shared library package."
But inherited from my many predecessors i have some doc stuff in the
runtime library package:
$ apt-file list libburn4
libburn4: /usr/lib/x86_64-linux-gnu/libburn.so.4
libburn4: /usr/lib/x86_64-linux-gnu/libburn.so.4.93.0
libburn4: /usr/share/doc/libburn4/AUTHORS
libburn4: /usr/share/doc/libburn4/NEWS.gz
libburn4: /usr/share/doc/libburn4/README.gz
libburn4: /usr/share/doc/libburn4/changelog.Debian.gz
libburn4: /usr/share/doc/libburn4/changelog.gz
libburn4: /usr/share/doc/libburn4/copyright
Each of these pathnames contains the shared object version ("4"), so
everything is in order here.
What to do with the other packages from libburn ?
The Multiarch page prescribes to add the Pre-Depends line to each
package which provides a shared library.
libburn-dbg seems to modify libburn.so.4.X.0 .
Um, "modify"?
libburn-dev installs a link libburn.so to libburn.so.4.X.0 .
Do they need multi-arch headers in debian/control ?
libburn-dbg and libburn-dev are not shared library packages, so they
wouldn't have needed Pre-Depends even in times of wheezy.
--
Jakub Wilk
Reply to: