Comment 3 for bug 1477299

or the fix which is in the experimental branch for this issue for 2+ months now… ;)
353c135e45d3b76dbecc1ba1b2bd9266601181ee

I don't think the virtual package handling CacheSetHelperAPTGet provides is really needed (nor even wanted) for download or changelog, so we can just use the default helper – as before without a crazy non-sense std::ostream to bool conversion.

The auto_ptr think keeps being a warning for now, right? I am happily using c++11 features in (currently unreleased) patches, but I have my doubts if I should really force c++11 upon the reverse dependencies just now (as the auto_ptr gcc is warning about here is in a public header). Even through std=c++11 is the new default, right? Well, we will see after the gcc5 transition is done.

There are some more issues with apt build with gcc5 and running with the new libstdc++6, namely that some code pieces assume std::string to have copy-on-write behavior, which it doesn't have in c++11 mode anymore which can be observed by the integration tests – not run at buildtime, but by autopkgtest. Patches for that are in the experimental branch, too, for a while as they break the abi, but the step to gcc5 does break abi anyhow so who cares. ;)

mvo said he isn't around for a while, so I will try to polish up the sid-gcc5 branch he created and follow up at debbug#790979 then I am done hopefully later this weekend.