[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: glibc and abi-compliance-checker break multiple KDE autopkgtests


On 06-09-18 11:53, Samuel Thibault wrote:
> Samuel Thibault, le jeu. 06 sept. 2018 11:44:45 +0200, a ecrit:
>> Paul Gevers, le jeu. 06 sept. 2018 11:22:46 +0200, a ecrit:
>>> On 06-09-18 11:19, Samuel Thibault wrote:
>>>> It'd be useful for the abi-compliance-checker test to actually output
>>>> error messages,
>>>> https://ci.debian.net/data/autopkgtest/testing/amd64/k/kf5-kdepim-apps-libs/944759/log.gz
>>>> it not very talkative :)
>>> I agree, but I found that there are more logs in the artifacts.
>> Ah, right. They seem to only point at c++ headers, so it'd rather be a
>> g++ issue?
> All the passed artifacts I can find have libc++-dev 6.0.1-1, not
> libc++-8-dev 1:8~svn340819-1.

Does this mean that libc++-8-dev is breaking the ABI of the Qt/KDE
packages? Luckily libc++-8-dev will not migrate to testing due to
https://bugs.debian.org/714686 Does it need a "Breaks" then?

Does anybody know why libc++-8-dev is installed when glibc or
abi-compliance-checker come from unstable? It seems that package is
providing something that in testing is provided by libc++-dev (Or
somewhere else in the dependency chain this goes "wrong" and leads to
this outcome).

This is maybe also the reason why the autopkgtest of these packages fail
already longer in unstable. Apparently the wrong libc++*-dev package
gets installed.


PS to all: if we determine how this goes wrong and if I can't get the CI
framework to do the right thing and this is outside of glibc and
abi-compliance-checker, I'll ask the migration software to ignore these

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: