Bug#968525: lintian: breakout-link reported for /usr/lib/$(DEB_HOST_MULTIARCH) -> /lib/$(DEB_HOST_MULTIARCH) symlinks
Hi,
On 2021-09-19 16:18, Felix Lechner wrote:
> Hi,
>
> On Sun, Sep 19, 2021 at 3:11 PM Aurelien Jarno <aurel32@debian.org> wrote:
> >
> > Now in the same spirit as in #993955, I am not sure you actually want to
> > push maintainers to move libraries from /lib to /usr/lib
>
> The purpose of this tag was never to push people toward usr-merge. It
> only looks like that to glibc and libgpg-error-dev because the
> packages use mixed installation paths.
>
> Furthermore, the comparison with Bug#993955 is not appropriate. Filed
> at the extraordinary 'serious' level by a member of the release team,
> it was based on the filer's misunderstanding of what the tag does and
> when it was implemented: Introduced seven months ago as a
> classification tag [1] it was never shown to users. The purpose was to
> aid in the collection of statistics [2] that became then immediately
> available via the JSON interface on the Lintian website. [3] The
> description, too, was gentle boilerplate [4] and in line with
> conventional wisdom at the time. Most significantly, the tag predated
> the "considered harmful" thread on -devel [5] that commenced on July
> 15 by almost half a year.
>
> Lintian's packaging hints never contradicted the consensus now
> emerging—if that is what we have—either in that tag or in the
> 'breakout-link' tag being discussed here.
Don't get me wrong, I never said it was a way to push for usr-merge.
That said the only way to get rid of this warning is to move libraries
from /lib to /usr/lib, and as maintainers are encouraged to get their
packages lintian, this goes against the consensus.
This is therefore definitely not your intention, but the result is that
it still goes in that direction that we want to avoid until there is a
clear usr-merge plan for bookworm.
> Maybe 'breakout-link' is not useful and we should get rid of it, but
> it looks to me like we found an issue in the way libgpg-error or
> Pkg-config invoke Libtool.
Please do not rewrite the history. libgpg-error was working pretty fine
before the maintainer tried to get rid of this lintian warning,
obviously in the wrong way. Lintian didn't detect anything, it just
pushed for the maintainer to do a mistake.
In addition putting the library in /lib and the .so symlink in /usr/lib
is something done by all libraries that were need to boot the system
before we stopped supporting a separate /usr directory. Therefore it's
much more than libc6-dev and libgpg-error-dev as you imply. Here is the
current list:
comerr-dev
libaudit-dev
libauparse-dev
libbind-export-dev
libbrlapi-dev
libbz2-dev
libc6-dev
libcap-dev
libcap-ng-dev
libcgroup-dev
libdevmapper-dev
libeditreadline-dev
libeinfo-dev
libexpat1-dev
libext2fs-dev
libfuse3-dev
libfuse-dev
libgpg-error-dev
libiw-dev
libkeyutils-dev
liblvm2-dev
liblzma-dev
liblzo2-dev
libncurses-dev
libnfsidmap1
libnfsidmap-dev
libnss-ldap
libnutclient-dev
libnutscan-dev
libpam0g-dev
libparted-dev
libpcre3-dev
libprocps-dev
librc-dev
libreadline-dev
libselinux1-dev
libsepol1-dev
libsepol-dev
libtirpc-dev
libupsclient-dev
libzfslinux-dev
ntfs-3g-dev
ss-dev
zlib1g-dev
Regards,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: