On Thu, Feb 12, 2009 at 5:53 PM, Sascha Silbe < sascha-debian-bugs-suga...@silbe.org> wrote:
> On Tue, Jan 20, 2009 at 11:51:02PM +0100, Jonas Smedegaard wrote: > > [unsigned packages] > >> I claim (through this signed email) that I myself compiled all packages >> offered at debian.jones.dk in clean (or least-possible-unclean[1]) build >> environments. >> > If I somehow suggested your packages are of minor quality or something like > that just because they're not signed, I apologize. > I'm sensitive regarding unsigned packages because I have good reasons _not_ > to trust the university network (i.e. my internet uplink). > Understandable, it's usually never a good policy to trust *any* pipe routed through several anonymous nodes which may be in less than kind countries. (ie. any internet connection) My Lenny packages has been compiled against libraries in Lenny. >> Sid packages has been compiled against libraries in Sid. >> > OK, seems like I misunderstood how testing works. Until now, I thought > packages are always uploaded to sid and automatically enter testing if no > bug is filed against the new version within a certain period (one week?). > Do you have a quick pointer to some documentation explaining how it > actually works? > http://www.debian.org/devel/testing explains the restirctions on migrating to testing. (it's 10 days for "low" priority fixes) See http://release.debian.org/migration/testing.pl?package=sugar for a more specific explanation of why Sugar isn't allowed in. The "sugar" package, along with (almost all of) the rest of *testing* is currently in a deep "freeze" to avoid regressions and enable exhaustive testing pending the release of *lenny*, the next version of Debian (which has been delayed a few times already for good reason). -- Luke Faraone http://luke.faraone.cc
