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

Re: What do you do if a package is built and not uploaded?

On Sat, 01 Oct 2005, Andreas Barth wrote:
> * Nathanael Nerode (neroden@twcny.rr.com) [051001 22:42]:
> > Thiemo Seufer wrote:
> > > Mailing {alpha,mips,powerpc}@buildd.debian.org is my best guess. There
> > > is usually no reply, but from some cases I conclude the mailboxes are
> > > read. I don't know if those addresses are documented anywhere.
> > They're not.  Perhaps they could be?  :-)  That would be a big help.
> http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-porter-automation

Not good enough.  Please add it to the central place we all go hunting for
buildd issues: buildd.debian.org.

Oh wait, I forgot that buildd.d.o is effectively read-only, as it has
already reached perfection.  Never mind.

The most effective way to do it is IMHO a BTS entry for each ARCH port, to
track down all porting issues with a damn good memory.  THAT's transparency,
and it is much more manageable than trying to contact a number of mailing
lists (which are often quite effective) and email addresses (which aren't
_apparently_).  The PTS takes care of keeping whichever email addresses

And the history we get from the BTS can definately help track which arches
are boggling down the rest of Debian, and how often that happens.

  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Reply to: