[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ppxp build failure



Hello

On Thu, Aug 26, 2004 at 02:03:46AM +0100, Colin Watson wrote:
> On Thu, Aug 26, 2004 at 01:49:59AM +0200, Adeodato Simó wrote:
> > * Luk Claes [Wed, 25 Aug 2004 21:08:15 +0200]:
> > > Thomas Bushnell BSG wrote:
> > > | Luk Claes <luk.claes@ugent.be> writes:
> > > |>I have built the package in a clean pbuilder. It builds fine.
> > 
> > > | So what explains the buildd failure?  Can you upload it in a binary
> > > | NMU so that at least we can get the package into testing?
> > 
> > > I'm no DD yet, but I can try to do a sponsored binary NMU?
> > 
> >   Perhaps the RMs would prefer that to be avoided (CCing -release). I
> >   think I've read that in similar situations.
> 
> I would *very strongly* prefer people not to do sponsored binary
> uploads, ever. At least with sponsored source uploads it's possible to
> audit what the non-developer has done.
> 
> The build failure seems to be on i386. If it's really just a transient
> failure on the autobuilder (and be very sure that this has been fully
> diagnosed before uploading yourself, otherwise we're just setting
> ourselves up for problems the next time there's a sourceful upload),
> surely we can't possibly have a shortage of developers with i386 systems
> to do this build?

I have done such an upload now.

Regards,

// Ola

> Cheers,
> 
> -- 
> Colin Watson                                  [cjwatson@flatline.org.uk]
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-qa-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 

-- 
 --------------------- Ola Lundqvist ---------------------------
/  opal@debian.org                     Annebergsslingan 37      \
|  opal@lysator.liu.se                 654 65 KARLSTAD          |
|  +46 (0)54-10 14 30                  +46 (0)70-332 1551       |
|  http://www.opal.dhs.org             UIN/icq: 4912500         |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---------------------------------------------------------------



Reply to: