-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Dienstag, 4. März 2003 21:00 schrieb Chris Cheney: > On Tue, Mar 04, 2003 at 08:49:10AM -0400, Derek Broughton wrote: > -snip- > > > I would argue that you have absolutely no need to be using sid (which > > doesn't mean you shouldn't, just that it's not necessary). I have been > > known to download the odd thing from sid, but sarge does the job with the > > simple addition > > I would suggest that no one run sarge at least until the libc6 blockage > fixes itself. Notice that nothing (or at least almost nothing) has gone > into sarge in over 6 months including security fixes. Make your own > conclusions from that. :\
Hmm, that's not fully correct. Some things dropped down and surely with sarge, one has to follow the security list (e.g. cupsys) and recompile from sid which _always_ worked for me. What I mostly do not understand in this issue: what the f**k do applications (e.g. cupsys) have to do with glibc version? Almost all of them surely build and run just fine with glibc-2.2.5. But even when having no bugs, they do not drop down! This makes ABSOLUTELY NO SENSE because they would get rebuild for sarge then and leaving any compiler/glibc issues away from sarge. Instead, many rather go for sid, although they probably shouldn't. The release manager definitely defeat the reasons for have sarge at all. Or maybe I did not get the point here... HS - -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+ZSP1zvr6q9zCwcERAj0WAKC6YCiAsuVpUxfNJHwmJ4LtBiYmcgCgkPuF tZdnwPFkwMj7VAKBeExori8= =dmGr -----END PGP SIGNATURE-----
