On Tue, Mar 04, 2003 at 11:08:53PM +0100, Hendrik Sattler wrote: > 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
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. Chris