On Thursday 20 August 2015 16:08:22 Sune Vuorela wrote:
> Hi Release Team, hi pkg-kde (and a couple of BCC's just as a FYI)
> (not subscribed to -release, please CC me)

Same for me.

> After having spent quite some time today looking at the current kdecoration2
> mess (tracked at https://bugs.kde.org/show_bug.cgi?id=350964 ,  at
> debian:796194, debian:796184 and probably many more)
> The crash happens around when a std::function (a c++11 feature) is passed
> across a library boundary and some parts of it is built with gcc5 and others
> with 4.9.

Matthias: is there any chance to make this simbol part of the new ABI? In this 
way stuff will not migrate to testing as it happened for us.
> According to Matthias Klose, upstream actually gives no guarantees for for
> their abi for c++11, so I guess the steps forward should be:
> 1) Immediately binNMU src:kdecoration2 in testing, then when that is done,
> binNMU src:kwin, src:oxygen and src:breeze all in testing. (that's for
> release team)

I don't know if we can binNMU something in testing with a testing chroot. I 
think it needs a sourcefull upload to t-p-u. RT, please confirm.

> 2) At the same time, do a library transition for libkdecoration2-5 and
> rename it to libkdecoration2-5v5 and binNMU the rdeps (the same as
> mentioned above)

I can do this if the RT ACKs it (all B-Ds are ready).
> 3) And add std::function to the list of types in interfaces to be careful
> about when looking if a package should be renamed or not.

Right, this is part of what I wrote to Matthias above.

Kinds regards, Lisandro.


Lisandro Damián Nicanor Pérez Meyer

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply via email to