Re: Attempted "testing propagation status" report

2003-11-19 Thread Martin Schulze
Roland Mas wrote: > I'm told (on IRC) that the mipsel build has been ongoing for a few > days already. And mips has perl in its "Not-for-us" list, whatever > that means (I'm a buildd newbie). So I'm currently building perl > 5.8.2-2 by hand on casals.debian.org "by hand". Do tell me if it's > no

Re: Attempted "testing propagation status" report

2003-11-19 Thread Roland Mas
Roland Mas, 2003-11-19 14:30:26 +0100 : > Steve Langasek, 2003-11-18 08:00:13 +0100 : > >> On Tue, Nov 18, 2003 at 12:29:28AM -0500, Nathanael Nerode wrote: > > [...] > >>> perl: Just waiting for its wait time to go. >> >> It's specifically waiting for uploads on mips and mipsel. > > I'm told (on

Re: Attempted "testing propagation status" report

2003-11-19 Thread Roland Mas
Steve Langasek, 2003-11-18 08:00:13 +0100 : > On Tue, Nov 18, 2003 at 12:29:28AM -0500, Nathanael Nerode wrote: [...] >> perl: Just waiting for its wait time to go. > > It's specifically waiting for uploads on mips and mipsel. I'm told (on IRC) that the mipsel build has been ongoing for a few d

Re: Attempted "testing propagation status" report

2003-11-19 Thread Andreas Metzler
On Tue, Nov 18, 2003 at 10:41:02PM -0700, Andre Lehovich wrote: > On Tue, 18 Nov 2003, Andreas Metzler wrote: >> Your point being? > That Nathanael's list is missing one important subsystem. I see, I did not get it because of the nullquote. > > From reading debian-x I got the firm impression tha

Re: Attempted "testing propagation status" report

2003-11-18 Thread Andre Lehovich
On Tue, 18 Nov 2003, Andreas Metzler wrote: > Your point being? That Nathanael's list is missing one important subsystem. > From reading debian-x I got the firm impression that we'll have 4.3.0 > in sarge (unless our time estimates are completely off and sarge wil > be released in June). Is it

Re: Attempted "testing propagation status" report

2003-11-18 Thread Andreas Metzler
On Tue, Nov 18, 2003 at 10:15:25AM -0700, Andre Lehovich wrote: > xfree86 4.1.3: still in experimental, adds support for a > bunch of important video chipsets, including most new > laptops. Upstream 4.1.4 is advertised to release 15 > December. Your point being? From reading debian-x I got the

Re: Attempted "testing propagation status" report

2003-11-18 Thread Björn Stenberg
Neil Schemenauer wrote: > Say 'A' depends on 'B' with a matching version number. In testing > we have: > > A_1 B_1 > > and in unstable: > > A_1 B_2 > > We can't move B into testing since it's waiting for A. Now someone > uploads a new version of B, > > A_1 B_3 > > and shortly af

Re: Attempted "testing propagation status" report

2003-11-18 Thread Andre Lehovich
xfree86 4.1.3: still in experimental, adds support for a bunch of important video chipsets, including most new laptops. Upstream 4.1.4 is advertised to release 15 December. --Andre, raining on the parade

Re: Attempted "testing propagation status" report

2003-11-18 Thread Neil Schemenauer
On Tue, Nov 18, 2003 at 09:40:35AM +0100, Matthias Klose wrote: > do we have a period in the release cycle, where no new versions enter > unstable, so that packages depending on other packages can catch up? > something like a bug fixing upload period only? I had another idea. In my spare time I'v

Re: Attempted "testing propagation status" report

2003-11-18 Thread Matthias Klose
Steve Langasek writes: > Oh, well, I think there are at least a few people who would mind if we > released with a completely broken set of php4 packages. But this is > trivial to fix once perl is in. do we have a period in the release cycle, where no new versions enter unstable, so that packages

Re: Attempted "testing propagation status" report

2003-11-18 Thread Steve Langasek
On Tue, Nov 18, 2003 at 12:29:28AM -0500, Nathanael Nerode wrote: > GNOME 2: All the libraries need to pass their 10-day wait times, and then > most of it should go in at once, probably leaving only a couple of packages > to fix. orbit2, libbonobo, it looks like. So this should be ready to go i

Attempted "testing propagation status" report

2003-11-17 Thread Nathanael Nerode
So, things look pretty good actually. KDE 3: Frustratingly slow. * Still waiting for kdebase 3.1.4 upload which is fully installable (including kdebase-dev, and therefore ksysguard). This is probably keeping other kde packages out indirectly; when their -dev Build-Dependencies are uninstallable,