Re: s390 not currently projected releasable (was: Re: Dropping from mirror network vs dropping from tier-1)

2005-03-16 Thread Stephen Frost
* Thomas Bushnell BSG ([EMAIL PROTECTED]) wrote: Blars Blarson [EMAIL PROTECTED] writes: Another architecure that isn't keeping up to the 98% mark has a buildd mainainter who insists (to the point of threating) that I don't build and upload packages to help the build with its backlog and

Re: s390 not currently projected releasable (was: Re: Dropping from mirror network vs dropping from tier-1)

2005-03-16 Thread Thomas Bushnell BSG
Stephen Frost [EMAIL PROTECTED] writes: Well, that's not *necessairly* true. If the buildd maintainer is also part of DSA/ftpmasters (as seems to often be the case, and might even be required by some unwritten law) then it'd be possible for them to disable the account doing the uploading. I

s390 not currently projected releasable (was: Re: Dropping from mirror network vs dropping from tier-1)

2005-03-15 Thread David Schmitt
On Tuesday 15 March 2005 12:08, Frank Küster wrote: (exactly because of arches like s390 who should be able to reach tier-1 easily, but really have no reason to be on the mirror network). But it does *not* say that s390 is likely to be among the released architectures. And I do not

Re: s390 not currently projected releasable (was: Re: Dropping from mirror network vs dropping from tier-1)

2005-03-15 Thread Bastian Blank
On Tue, Mar 15, 2005 at 04:12:51PM +0100, David Schmitt wrote: Looking at the stats[1], the amount of compiled packages seems to be a blocker: 250-300 need-build packages. At approximatly 9000 source packages, around 8820 must be built to satisfy the 98% barrier. Looking at longer timeframe

Re: s390 not currently projected releasable (was: Re: Dropping from mirror network vs dropping from tier-1)

2005-03-15 Thread Thomas Bushnell BSG
Bastian Blank [EMAIL PROTECTED] writes: On Tue, Mar 15, 2005 at 04:12:51PM +0100, David Schmitt wrote: Looking at the stats[1], the amount of compiled packages seems to be a blocker: 250-300 need-build packages. At approximatly 9000 source packages, around 8820 must be built to satisfy

Re: s390 not currently projected releasable (was: Re: Dropping from mirror network vs dropping from tier-1)

2005-03-15 Thread Bastian Blank
On Tue, Mar 15, 2005 at 11:17:23AM -0800, Thomas Bushnell BSG wrote: Yes, it was a broken autobuilder, the only autobuilder, the others are blocked by the w-b admins. Why don't you start building packages yourselves? You do have access to the hardware, right? It's supposed to be blindingly

Re: s390 not currently projected releasable (was: Re: Dropping from mirror network vs dropping from tier-1)

2005-03-15 Thread Thomas Bushnell BSG
Bastian Blank [EMAIL PROTECTED] writes: On Tue, Mar 15, 2005 at 11:17:23AM -0800, Thomas Bushnell BSG wrote: Yes, it was a broken autobuilder, the only autobuilder, the others are blocked by the w-b admins. Why don't you start building packages yourselves? You do have access to the

Re: s390 not currently projected releasable (was: Re: Dropping from mirror network vs dropping from tier-1)

2005-03-15 Thread Blars Blarson
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes: Bastian Blank [EMAIL PROTECTED] writes: Why don't you start building packages yourselves? You do have access to the hardware, right? It's supposed to be blindingly fast, right? Another architecure that isn't keeping up to the 98% mark has a

Re: s390 not currently projected releasable (was: Re: Dropping from mirror network vs dropping from tier-1)

2005-03-15 Thread Thomas Bushnell BSG
Blars Blarson [EMAIL PROTECTED] writes: Another architecure that isn't keeping up to the 98% mark has a buildd mainainter who insists (to the point of threating) that I don't build and upload packages to help the build with its backlog and lack of requeueing. So? A buildd maintainer doesn't