Comment 5 for bug 1486061

The patchset applied in ubuntu for the gcc5 transition wasn't complete; I thought that it would have been synced back by now, but it seems not… – I had added a few more changes on top of Michaels changes (including the one Kiwinote referred to) to make it not only build, but also build something passing our testcases (as the only partly working Translation-* trashes our testcases). That is also the cause for other recent bugreport like #1497534 here I would guess.

It is probably not the worst idea to think about applying 8965b2f8 (the one mentioned above) – even if it is technically an abibreak, in practice only libapt itself is using (and is actually able to use) the symbol which is why in newer libapt versions the symbol isn't even exported anymore. 130f34b7 should be applied as well for entirely different reasons (even through it isn't a security fix in any way, it should be dealt with as one). No idea where Ubuntu is in the release cycle frankly as I have other things to worry about at the moment, but instead of cherry-picking these it might be better to use the entire release. They are well tested by now and bugfix only…

Feel free to ask me for more details if need be, but expect delays as I read mail between two grape presses at the Most (pun intended, even through mostly a my-region-only pun).

And a, btw mc3man: I wouldn't advice to install the Debian version directly on Ubuntu – it depends on the wrong archive-keyring for example. At the very least, you should recompile it, then the buildsystem will take care of setting the right things.