On Tue, Dec 30, 2014 at 02:08:38PM +0100, Matthias Klose wrote: > Package: release.debian.org > Tags: sid jessie > > please consider the current versions of gcc-4.8, gcc-4.9, and gcc-defaults for > unstable. gcc-4.8 is updated to the final gcc 4.8.4 release, and gcc-4.9 to a > branch snapshot taken at the time of the gcc 4.8.4 release. > > The only RC fix is #771647, resolving a file conflict in the libphobos > packages > built by gcc-4.8 and gcc-4.9. > > The gcc-4.8 packaging fixes some cross-build related issues. > > The rest of the gcc-4.8 fixes come from upstream and address regressions on > the > 4.8 release branch, compared to earlier gcc release. All upstream changes are > mentioned in the Debian changelog. I checked (on x86_64), that the current > package still builds a glibc and linux package without obvious regressions. > > I don't agree with the severity of gcc-4.9's #764732, however the ARM porters > are quiet about this one.
Hello Matthias and release team. A little bit of context: Bug#764732 is a compiler bug which makes unzip to FTBFS. There is a simple workaround for unzip which is to drop -O2 on armhf, and I will probably have to do that. However, the reason I raised the gcc bug to "serious" is that we don't know how many other packages will also FTBFS because of it. So, IMHO, either we consider the gcc bug as RC, or else we should be ready to rebuild the entire archive with the current gcc on armhf to be sure that there are no other packages affected. Thanks. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141230140310.ga23...@cantor.unex.es
