Re: kamp down
On 11 May 2018, at 21:58, Svante Signell <firstname.lastname@example.org> wrote:
> I'm CC:ing this to debian-kbsd too!
> On Sun, 2018-05-06 at 19:31 +0200, Svante Signell wrote:
>> On Sat, 2018-05-05 at 01:45 +0100, James Clarke wrote:
> Pasted from irc, this is becoming a bad story. Do you have anybody who
> can help (or teach me more on how to administer a buildd):
Ask people in #debian-ports; we run a whole load of buildds as a team.
> (10:43:04 PM) srs: jrtc27: I see that you are uploading/signing
> packages right now.
No, I signed them earlier this evening.
> (10:48:55 PM) srs: I really need help configuring the buildd:
> (10:48:55 PM) srs: 1) get rid of the recovery sessions
If there are left-over sessions, just schroot -e -c them?
> (10:48:55 PM) srs: 2) enable build of i386 again
It does get round to i386; some of the packages I signed were i386.
> (10:48:55 PM) srs: 3) update the build chroots: starting with i386
It updates them twice weekly, but that's broken, because it can't debootstrap
them due to build-essential depending on gcc (>= 4:7.3), but the new
gcc-defaults providing that is waiting for gcc-7-base (>= 7.3.0-12).
> (10:48:55 PM) srs: 4) make package build again for experimental:
> missing dependency on libcwidget3v5 for aptitude.
The rebuild of aptitude is (eventually) blocked by ruby2.5 failing to build;
those test suite errors need investigating.
> (10:49:34 PM) srs: If you don't help me I shut down kamp in 24 hours.
> (10:50:43 PM) srs: It is not good policy to have a buildd trying to
> build packages over and over again, not having a chance to succeed :(
> (10:51:05 PM) srs: We will just be laughed at ...
Nobody's laughing, and it does succeed for some packages; the batch I just
signed was 152 packages. It's your choice whether you shut kamp down, but I
don't see what it achieves other than perhaps a small amount of power/heat
Like I said in private, I'm busy writing my master's dissertation right now,
but once I finish I will turn to fixing these issues.