Re: [buildd] Action plan to get buildds getting online again
Michael Schmitz dixit:
>With the likely exception of Thorsten, none of us here are. While I've run
>autobuilders in the past, I'm certain the procedures have evolved to a
>point where I do pretty much start from scratch.
Yes well, I can’t get my head wrapped around the buildd thing (yet,
mostly because I invest all my m68k time into building stuff using
a method I know that works and is safe) on the other hand, so I do
appreciate you (and the others) stepping back in for that.
>Looking at anything that fails to build automatically would be appreciated.
>To do that, you'd use the same chroot strategy and tools as the autobuilder
>does - not a huge stretch to give that a try as well.
You can do that with both cowbuilder and sbuild in manual mode.
What I do is:
root@aranym:~ # cat pb-hook/C80shell-jupp
#!/bin/sh
# $MirOS: contrib/hosted/tg/deb/hookdir/C80shell-jupp,v 1.1 2012/01/03 16:28:48 tg Exp $
#-
# Not complicated enough for copyright.
echo
echo Build failed. Trying to invoke a shell.
echo
unset LANGUAGE
LC_ALL=C; export LC_ALL
apt-get -y --force-yes install less mksh ed jupp
ENV=/etc/skel/.mkshrc /bin/mksh -l 0<>/dev/tty >&0 2>&0 || \
/bin/sh 0<>/dev/tty >&0 2>&0
And I’m building with --hookdir=$PWD/pb-hook so, when a build fails,
I’ll end up with a shell *inside* the chroot in which I can debug.
In fact, this has led to:
-rw-r--r-- 1 root root 4849 Nov 25 15:38 qt4-x11_4.8.2+dfsg-3+m68k.2.dsc
(Because I was stupid and forgot something in -3+m68k.1 …)
bye,
//mirabilos
--
Darwinism never[…]applied to wizardkind. There's a more than fair amount of[…]
stupidity in its gene-pool[…]never eradicated[…]magic evens the odds that way.
It's[…]harder to die for us than[…]muggles[…]wonder if, as technology[…]better
[…]same will[…]happen there too. Dursleys' continued existence indicates so.
Reply to: