Control: user debian-...@lists.debian.org
Control: usertag -1 - gcc-7-op-mangling
Control: retitle -1 encfs: installs private library in public directory

Hi,

On 15/08/17 22:28, Eduard Bloch wrote:
> Hallo,
> * jcowg...@debian.org [Mon, Aug 07 2017, 03:20:41PM]:
>> Package: encfs
>> Version: 1.9.2-1
>> Severity: serious
>> Tags: sid buster
>> User: debian-...@lists.debian.org
>> Usertags: gcc-7-op-mangling
>>
>> Hi,
>>
>> It appears that your package provides an external symbol that is
>> affected by the recent name mangling changes in GCC 7. See:
>> https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling
> 
> It might be the case, however, the library inside is for internal use
> only. So I think the report and advise are not appropriate here. If you
> agree, please close the bug report and maybe also adjust the scan script
> to consider the hints from lintian overrides, like those:
> 
> $ cat /usr/share/lintian/overrides/encfs
> encfs: non-dev-pkg-with-shlib-symlink usr/lib/libencfs.so.6.0.1 
> usr/lib/libencfs.so
> encfs: no-shlibs-control-file usr/lib/libencfs.so.6.0.1
> encfs: postinst-must-call-ldconfig usr/lib/libencfs.so.6.0.1
> encfs: package-name-doesnt-match-sonames libencfs6

If the library is private, then indeed you do not need to rebuild it
with GCC 7 (since there will be no external rdeps).

However, you are aware that installing a private library in a public
directory is a policy violation (various bits in section 8)? Lintian
overrides doesn't make any difference to ld.so when determining if a
library is public. You should instead be installing it in a private
directory (such as /usr/lib/encfs) and using RUNPATH or RPATH.

Thanks,
James

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to