=== bjf[afk] is now known as bjf
=== bjf is now known as bjf[afk]
[02:46] <lamont> slangasek: looking at build logs, wow.  I think I'll roll new maverick chroot tarballs tomorrow
[02:46] <lamont> and pygobject vs sparc?  fail
[02:46]  * lamont files a bug
[02:55] <ScottK> lamont: Anything beyond saying "sparc" was redundant there.
[03:00] <lamont> heh.
[03:01] <lamont> ScottK: bug 591990
[03:01] <ubot4> Launchpad bug 591990 in pygobject (Ubuntu) (and 1 other project) "pygobject hates sparc, kills it (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/591990
[03:02] <ScottK> lamont: I think it's a mercy killing at this point.
[03:05] <lamont> yeah, but I had to file the bug anyway, so I could kill it harder
[03:05] <ScottK> ;-)
[06:33] <slangasek> lamont: new chroot> was that in reference to the coreutils thing?
[06:33] <slangasek> lamont: because I can reproduce this ad absurdum on armel here
[12:20] <lamont> slangasek: nah - that was in reference to how big the dist-upgrade at the start of builds has grown - so new chroot tarballs coming today at some point
=== bjf[afk] is now known as bjf
[16:58] <slangasek> lamont: ah, ok
[16:58]  * lamont wonders what context that was in
[17:01] <slangasek> a chrooted context :)
=== pgraner is now known as pgraner-afk
=== bjf is now known as bjf[afk]
=== bjf[afk] is now known as bjf
[23:43] <lamont> slangasek: ah.  so... if  you're around, wanna kick off a maverick livecd fs build on cardamom(i386) and kapok(amd64) to verify that you can trigger such things?