[ Note: This is now fixed in unstable, it was a lot easier than I expected ]
On Sat, 6 Aug 2016, Matthias Klose wrote: > Control: severity -1 serious > > > I don't know how to fix this, so I just made a QA upload that makes > > the package to use GCC 5. This should make the bug not to be RC for > > stretch. > > no, gcc-5 is targeted for removal for stretch. Ok, removing gcc-4.9 and gcc-5 is in your roadmap as I read here: https://lists.debian.org/debian-devel-announce/2016/06/msg00007.html But then, I'm curious: Why do you still update gcc-4.9 in unstable? (Like the recent 4.9.4 release). For snapshot.debian.org? For Debian derivatives? Thanks.