Bug#797625: Bug#797623: Bug#797625: xmltooling: transition needed for g++-5 ABIs

[Simon McVittie]

On 01/09/15 17:50, Russ Allbery wrote:
> Ferenc Wagner  writes:
>> Anyway, feel free to NMU these packages if that helps
>> unblocking other stuff, just don't be too concerned about the fate of
>> the current versions in unstable, expect new upstream versions after a
>> couple of weeks.
> 
> If you're changing the SONAME anyway, you don't have to do the renaming
> described here.  That's actually an even cleaner solution.

Yes, if the new SONAME is uploaded before the v5 rename, and the new
SONAME compiled with gcc < 5 has never been in Debian, then it makes the
v5 rename unnecessary.

I'm not sure how "a couple of weeks" is going to compare with the point
at which this transition becomes part of the critical path. I'll leave
the Shib stack alone for now, but I'll come back to this and NMU with
the "v5" names if it becomes a blocker for the C++ Transition of
Despair, because this process has taken long enough already.

S

Bug#797623: Bug#797625: xmltooling: transition needed for g++-5 ABIs

[Ferenc Wagner]

Hi,

Thanks for the detailed report.  Right now I'm doing urgent work on HA
packages, but once that's done, I'll package new upstream versions of
the whole Shibboleth stack to fix the outstanding OpenSAML security bug
in unstable.  This will change the SO version of xml-security-c and
probably all other library packages in the stack.  Does this change the
big picture somehow?  I don't understand the interdependencies of this
transition.  Anyway, feel free to NMU these packages if that helps
unblocking other stuff, just don't be too concerned about the fate of
the current versions in unstable, expect new upstream versions after a
couple of weeks.
-- 
Regards,
Feri.

Bug#797623: Bug#797625: xmltooling: transition needed for g++-5 ABIs

[Russ Allbery]

Ferenc Wagner  writes:

> Thanks for the detailed report.  Right now I'm doing urgent work on HA
> packages, but once that's done, I'll package new upstream versions of
> the whole Shibboleth stack to fix the outstanding OpenSAML security bug
> in unstable.  This will change the SO version of xml-security-c and
> probably all other library packages in the stack.  Does this change the
> big picture somehow?  I don't understand the interdependencies of this
> transition.  Anyway, feel free to NMU these packages if that helps
> unblocking other stuff, just don't be too concerned about the fate of
> the current versions in unstable, expect new upstream versions after a
> couple of weeks.

If you're changing the SONAME anyway, you don't have to do the renaming
described here.  That's actually an even cleaner solution.

-- 
Russ Allbery (r...@debian.org)