Re: What do you do if a package is built and not uploaded?
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
> On Sat, 01 Oct 2005, Andreas Barth wrote:
>> * Nathanael Nerode ([EMAIL PROTECTED]) [051001 22:42]:
>> > Thiemo Seufer wrote:
>> > > Mailing {alpha,mips,[EMAIL PROTECTED] 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.
And to http://www.de.debian.org/intro/organization as well, please.
> 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
> informed.
Seconded.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Re: What do you do if a package is built and not uploaded?
On Sat, 01 Oct 2005, Andreas Barth wrote:
> * Nathanael Nerode ([EMAIL PROTECTED]) [051001 22:42]:
> > Thiemo Seufer wrote:
> > > Mailing {alpha,mips,[EMAIL PROTECTED] 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
informed.
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
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What do you do if a package is built and not uploaded?
Nathanael Nerode <[EMAIL PROTECTED]> writes:
> Thiemo Seufer wrote:
>> Mailing {alpha,mips,[EMAIL PROTECTED] 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.
That makes it request number 324 for that documentation to happen.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What do you do if a package is built and not uploaded?
* Nathanael Nerode ([EMAIL PROTECTED]) [051001 22:42]:
> Thiemo Seufer wrote:
> > Mailing {alpha,mips,[EMAIL PROTECTED] 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
| The buildds admins of each arch can be contacted by the mail address
| [EMAIL PROTECTED]
Cheers,
Andi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What do you do if a package is built and not uploaded?
Thiemo Seufer wrote:
> Mailing {alpha,mips,[EMAIL PROTECTED] 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.
--
Nathanael Nerode <[EMAIL PROTECTED]>
"(Instead, we front-load the flamewars and grudges in
the interest of efficiency.)" --Steve Lanagasek,
http://lists.debian.org/debian-devel/2005/09/msg01056.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What do you do if a package is built and not uploaded?
Petter Reinholdtsen wrote:
> [Nathanael Nerode]
> > I'm thinking of python2.1, which is a key element in some testing
> > transitions.
> > It's out of date on alpha, mips, mipsel, and powerpc -- *yet the buildd logs
> > indicate successful builds on all of them on August 30*. I have already
> > emailed debian-mips@lists.debian.org, and the listed maintainers of the
> > relevant alpha and powerpc buildds.
>
> What to do? Well, you curse the lack of transparecy in the buildd
> maintainence process, and hope the problem will be fixed soon. I've
> not been able to find any other procedure that work better that this
> simple approach. I've tried to emailing Ryan Murray using the address
> listed at the bottom of all the buildd web pages, but do not remember
> if I ever got a reply. I've tried emailing the porters list, but most
> often this is either met with silence or I get a reply saying that the
> buildd admins for the given arhc are not reading the porters list.
> I've tried asking on IRC, and actually once got feedback from someone
> claiming to be the buildd maintainer of the arch in question (no way
> to verify this, have not found the list of maintainers), and some
> times one of the porters are willing to do a manual build.
Mailing {alpha,mips,[EMAIL PROTECTED] 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.
Thiemo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What do you do if a package is built and not uploaded?
[Nathanael Nerode] > I'm thinking of python2.1, which is a key element in some testing transitions. > It's out of date on alpha, mips, mipsel, and powerpc -- *yet the buildd logs > indicate successful builds on all of them on August 30*. I have already > emailed debian-mips@lists.debian.org, and the listed maintainers of the > relevant alpha and powerpc buildds. What to do? Well, you curse the lack of transparecy in the buildd maintainence process, and hope the problem will be fixed soon. I've not been able to find any other procedure that work better that this simple approach. I've tried to emailing Ryan Murray using the address listed at the bottom of all the buildd web pages, but do not remember if I ever got a reply. I've tried emailing the porters list, but most often this is either met with silence or I get a reply saying that the buildd admins for the given arhc are not reading the porters list. I've tried asking on IRC, and actually once got feedback from someone claiming to be the buildd maintainer of the arch in question (no way to verify this, have not found the list of maintainers), and some times one of the porters are willing to do a manual build. So, good luck, I hope your problem will be fixed soon. I'll help you with the cursing, and perhaps the problem is fixed sooner. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
What do you do if a package is built and not uploaded?
I'm thinking of python2.1, which is a key element in some testing transitions. It's out of date on alpha, mips, mipsel, and powerpc -- *yet the buildd logs indicate successful builds on all of them on August 30*. I have already emailed debian-mips@lists.debian.org, and the listed maintainers of the relevant alpha and powerpc buildds. -- Nathanael Nerode <[EMAIL PROTECTED]> [Insert famous quote here] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
