-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Dienstag, 4. M�rz 2003 23:52 schrieb Chris Cheney: > For a package to go into sarge it has to have less RC bugs than the > current version in sarge and have been in sid for a certain amount of > days depending on its severity of upload (time to see if new RC bugs > crop up). Rebuilding the version for upload to sarge against sarge > would be a hassle and possibly not work, also it could possibly > introduce new bugs that weren't seen in the sid version, since it would > be built against different versions of libraries. If the bugs in libc6 > could get resolved the issue would just go away though.
Well, that's why sarge != stable. What you say is that every update of a core lib like libc6, even a minor version change, would be a major pain. I doubt the usefulness of this. OTOH, packages that break thing drop down (e.g kde-i18n-de-3.1 which really sucks with the KDE2.2.2 in sarge and breaks lots of strings, there). Thus, translation packages should probably be bound to a range of valid binary pacakges. I know that this can cause problems but the current setting do the above with sarge :-/ 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+ZTzjzvr6q9zCwcERAsKTAJ4lzjYnfRgP+WsxH7TjHlrA0gJjPQCfVbtf Us8R+8YxiJXetrJifFwwFJA= =yoxX -----END PGP SIGNATURE-----
