Bug#833909: RFS: xml-security-c/1.7.3-3~bpo7+1 [BPO]

[Gianfranco Costamagna <locutusofborg@debian.org>]

control: owner -1 !
control: tags -1 moreinfo


>to wheezy-backports-sloppy as a first step to backporting other



1) really? what about don't care to wheezy anymore?
Did you get in touch with the maintainers? they seems active, one of them
is a DM, and might be able to upload it for you if needed

>libxml-security-c-dev - C++ library for XML Digital Signatures
>(development)
>libxml-security-c17v5 - C++ library for XML Digital Signatures (runtime)
>xml-security-c-utils - C++ library for XML Digital Signatures (utilities
>)


2)

this looks wrong to me.
the library has been renamed and conflicting with the non-v5 version, because
of the libstdc++ transition.

backporting to jessie and wheezy (where the transition didn't happen), means
you have to revert that change, because otherwise the package will be uninstallable
with all of the reverse dependencies, because of:
Package: libxml-security-c17v5

Conflicts:
libxml-security-c17,
Replaces:
libxml-security-c17,


in this case, oldstable has the library with a different soname (c16), so
I'm not sure if the rename is worth the effort or not, please ask on -mentors, -devel
or wherever you find more appropriate.

(I would call it c17 without the v5, to avoid bad installations with apt-pinned packages from
Stretch, avoiding runtime failures and segfaults, but I have no strong opinion)


3)

also, can the new patch be added to the package in unstable too?
-  * [aba87f7] New patch Remove-PKG_INSTALLDIR-to-build-with-older-pkg-config.patch


is it a breaking and non-compatible with new pkg-config change?
4)
dpkg-source: warning: failed to verify signature on /tmp/xml-security-c_1.7.3-3~bpo7+1.dsc

dpkg-source: error: file /tmp/xml-security-c_1.7.3.orig.tar.gz has size 909320 instead of expected 897454


please use the right orig tarball, thanks.


it should be all for now.

cheers,

G.