[08:31] <doko> there we go ... new boost packages in unstable :-/
[11:42] <lamont> fresh tarballs for everyone
[11:42] <lamont> well, shortly
[12:38] <lamont> all freshened
[12:38] <lamont> (oneiric, precise)
[12:43] <cjwatson> thanks
[20:25]  * slangasek begs for NEW processing of gettext :)
[21:20] <cjwatson> slangasek: done (amd64/armel/i386)
[21:20] <slangasek> ta :)
[21:21] <cjwatson> lamont: firefox/powerpc seems to have faceplanted again
[21:21] <cjwatson> chrisccoulson: ^-
[21:21] <lamont> cjwatson: thedac is dealing with it
[21:21] <cjwatson> ta
[21:21] <lamont> and scoring it through the floor
[21:22] <chrisccoulson> what's up with firefox?
[21:22] <cjwatson> <no filename>:0:allocation size overflow
[21:22] <cjwatson> over and over and over
[21:22] <cjwatson> https://launchpad.net/ubuntu/+source/firefox/8.0~b4+build1-0ubuntu1/+build/2865780
[21:22] <lamont> chrisccoulson: when I looked in on it, the launchpad-buildd (twistd) process was chewing up a CPU.  that was all the machine was doing
[21:23] <cjwatson> it's kind of getting in the way of powerpc catching up, which would be helpful
[21:23] <lamont> and that cputime was probably from capturing stdout
[21:23] <lamont> cjwatson: if you bump the priority on your sulfur ticket, you'll get a third lp-buildd sooner
[21:23] <lamont> OTOH, ppc...
[21:24] <cjwatson> might try that tomorrow
[21:24] <chrisccoulson> can we kill powerpc? ;)
[21:32] <chrisccoulson> lamont, any idea what my powerpc build is doing? ie, what processes are running? is there a firefox process running on there?
[21:33] <chrisccoulson> or xpcshell?
[21:34] <lamont> chrisccoulson: I don't, and didn't save any of it when I was smashing it earlier.
[21:34] <lamont> chrisccoulson: I would recommend a manual build in the precise schroot on davis
[21:35] <chrisccoulson> that's what i'm trying now. but it's quite late here, i'm not sure how far it will get before i go to bed
[21:41] <doko> chrisccoulson, rescored the firefox build to -10000