Dear Lucas and everybody, the recent archive rebuild uncovered a large number of GCC 4.6 build failures (that could been already forseen from Launchpad). In the long run, I find very impressive the contribution from the major Linux distribution to their upstreams for keeping them up to date with recent toolchains.
However, given my experience of repetitive patching cycles with earlier GCC updates, it would be pointless to spend a lot of energy updating our packages now if it is only to realise in few weeks that the next GCC update would require yet another header. So can we have some perspectives and gross time frame, sent on debian-devel-announce@l.d.o, that we could also use as a reference when we will forward the issue to our upstreams ? For the packages I maintain, I would prefer to see – and help – these bugs fixed by new upstream release rather than by patch. Have a nice day, -- Charles Plessy Illkirch-Graffenstaden, Alsace, France -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110503093212.gb12...@merveille.plessy.net
