[Debian-med-packaging] backporting libssw - autopkgtest fails on jessie

[Sascha Steinbiss]

Hi Afif,
>>> 
>>> I: libssw changes: backports-changes-missing
>>> W: libssw source:unknown-architecture any-x32
>>> I: libssw0: no-symbols-control-file usr/lib/x86_64-linux-gnu/libssw.so.0
>>> W: libssw0: maintscript-calls-ldconfig postinst
>>> E: libssw0: package-must-activate-ldconfig-trigger
>>> usr/lib/x86_64-linux-gnu/libssw.so.0
>>> W: libssw0: maintscript-calls-ldconfig postrm
>>> I: libssw-dev: static-library-has-unneeded-section
>>> usr/lib/x86_64-linux-gnu/libssw.a(ssw.o) .comment
>>> I: libssw-dev: static-library-has-unneeded-section
>>> usr/lib/x86_64-linux-gnu/libssw.a(ssw_cpp.o) .comment
>>> I: ssw-align: hardening-no-pie usr/bin/ssw-align
>> 
>> No, I for sure I don’t have any errors. I have fixed the unknown-architecture warning in the meantime though. The rest seems to be concerned with ldconfig calls - IIRC this is not needed to be done manually?
>> 
> 
> So the lintian error and related warnings were resolved by using a newer
> debhelper than Jessie's native version. I bumped the minimum debhelper
> version in debian/jessie-backports and cherry-picked it to master. More
> details are in my commit message.

OK, cool :)

> Now that everything looks great on Jessie, I've uploaded the backport.

Thanks. I think for unstable I will wait for upstream’s comments before making a potentially ABI relevant change, which they might want to solve differently.

Cheers
Sascha
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20160723/b60a8bb6/attachment-0001.sig>