Re: Please reply to buildd mails
Moin,
On Wed, May 08, 2013 at 09:09:58PM +0000, Thorsten Glaser wrote:
> Hi,
>
> there are now 125 packages in state Build-Attempted.
> Dear co-builddadmins, if you get a mail saying log for _attempted_
> build (not ???for failed build???, these get giveback immediately by
> the buildd software), do:
>
> ??? Look through the build log (gzip compressed attachment, or on
> http://buildd.debian-ports.org/status/package.php?p=$pkgname ).
> ??? Scan for a failure reason. If none can be seen, reply to the
> mail, to the buildd, with a mail whose body is just the one
> word ???fail??? on a line of its own, then goto 5. Otherwise,
> $failure be the reason.
> ??? Look whether it???s worth to reportbug against the package. If
> so, mention $reason in the bug, wait until the bug is recorded
> in the BTS, and set $reason = "#123456" where 123456 is the bug
> number in debbugs
> ??? Reply to the mail, to the buildd, with a message body looking
> like "fail\n\n$reason\n". Optionally, if it???s not been reported
> to the BTS and Julien Cristeau is not the maintainer (or any
> other person complaining about ???yay, more debian-ports spam???),
> consider putting the package maintainer on Cc (may want to put
> the buildd on Bcc then)
> ??? Now, and only now, you???re allowed to delete that mail ;-)
> ??? If the package???s reason to FTBFS is that it needs porting, and
> such porting is unlikely to be done in the next upload or other???
> wise RSN, ssh to leda and set the package on the Not-For-Us list:
> $ wanna-build -A m68k -d unstable -n ${Source}_${Source:Version}
> *BEFORE* doing so, make sure that the ???fail??? mail from your buildd
> is processed, by running:
> $ wanna-build -A m68k -d unstable --info ${Source}
Thanks for the detailed explanation, maybe you can help with the problems I
am experiencing here. As I already mentioned, processing an email takes
3-5 minutes on kullervo. Frequently this fails, it always fails if there
are more than two emails in the queue at the same time. Here is the output
when I try to give-back one(!) package, it still has not succeeded:
May 9 13:42:30 buildd-mail[12933]: Log reply from cts@debian.org
Connection closed by 206.12.19.127
May 9 13:45:08 buildd-mail[12933]: wanna-build --info failed with status 255/0
May 9 13:45:08 buildd-mail[12933]: Error: wanna-build --info failed with status 255/0
May 9 13:56:45 buildd-uploader[13879]: Nothing to do for upload
May 9 14:00:05 buildd-mail[13911]: Log reply from cts@debian.org
May 9 14:03:37 buildd-mail[14015]: ruby-sqlite3 has been installed; removing from upload dir:
May 9 14:03:37 buildd-mail[14015]: ruby-sqlite3_1.3.6-2_m68k.deb
ruby-sqlite3_1.3.6-2_m68k.changes ruby-sqlite3_1.3.6-2_m68k.upload Connection closed by 206.12.19.127
May 9 14:05:15 buildd-mail[13911]: wanna-build --info failed with status 255/0
May 9 14:05:15 buildd-mail[13911]: Error: wanna-build --info failed with status 255/0
May 9 14:12:36 buildd-uploader[14587]: Nothing to do for upload
May 9 14:14:19 buildd-mail[14408]: Log reply from cts@debian.org Connection closed by 206.12.19.127
May 9 14:19:48 buildd-mail[14408]: wanna-build --info failed with status 255/0
May 9 14:19:48 buildd-mail[14408]: Error: wanna-build --info failed with status 255/0
Most of the fails are due to intermittant errors, segfaults, ICEs, bus
errors, etc, so I think they should be given back. Is there a way to do this
from a different machine?
You say we should log in to leda, but I do not seem to have an account
there, at least my ssh key does not work. With the key from kullervo, I am
not allowed to start a shell.
Christian
Reply to: