Re: Results of the meeting in Helsinki about the Vancouver proposal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Olaf van der Spek <olafvdspek@gmail.com> writes:
> On 8/22/05, Steve Langasek <vorlon@debian.org> wrote:
>> In particular, we invariably run into arch-specific problems every time
>> a new version of a toolchain package is uploaded to unstable. Some may
>> remember that the new glibc/gcc blocked non-toolchain progress for
>> months during the beginning of the sarge release cycle, and that the
>> aftermath took months more to be sorted out. So far, etch threatens to
>> be more of the same; in the past month we've had:
>
> I've been wondering, why isn't the new toolchain tested and the
> resulting errors fixed before it's uploaded to unstable or made the
> default?
Andreas Jochens in particular did a lot of hard work in fixing most of
the GCC 4.0 failures and regressions over the last year while porting
for amd64. The fact that many maintainers have not yet applied, or at
least carefully reviewed and applied amended patches, is a pity.
As the bug lists at http://bts.turmzimmer.net show, most of the RC
bugs currently have patches. Grab yours today!
Regards,
Roger
- --
Roger Leigh
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFDCi/wVcFcaSW/uEgRAhYbAKDsNkOH9LUl+bW4uR114cEoBl8ExQCfe2+8
BoV4CLcexBsbxNSH7xvIx6E=
=WS6i
-----END PGP SIGNATURE-----
Reply to: