[00:02] <bjf> slangasek: looks like i have another biosdevname issue on a different server. it has biosdevname 0.4.1-0ubuntu2 installed on it. would you like a new bug or for me to add a new set of logs to the existing bug?
[00:02] <cjwatson> new bug please
[00:02] <bjf> cjwatson: ack
[00:05] <cjwatson> your previous bug was very definitely just "biosdevname incorrectly not installed"
[00:06] <cjwatson> bjf: oh, that said, we need a new debian-installer upload to incorporate my biosdevname fix
[00:06] <cjwatson> bjf: so it might be worth holding off until that's in place just in case ...
[00:07] <cjwatson> I'll sort out that upload before I go to bed
[00:08] <cjwatson> shadeslayer: figured out that "isohybrid: binary.hybrid.iso: boot loader does not have an isolinux.bin hybrid signature" bug - it's a curious misbuild of syslinux-themes-ubuntu
[00:10] <bjf> cjwatson: ack, i'll hold off
[00:13] <bjf> cjwatson: i had added biosdevname to my preseed and i was getting the latest version. should i still wait for d-i changes?
[00:20] <cjwatson> bjf: briefly, at what point are things failing?
[00:21] <bjf> cjwatson: i just reprovisioned a system, ifconfig -a says it has em1, em2, em3, em4 but "rename3" is in /etc/network/interfaces
[00:21] <cjwatson> bjf: ok, go ahead and file that separately
[00:22] <bjf> cjwatson: ack
[00:25] <cjwatson> infinity: could you please push your last d-i upload to bzr?
[00:26] <infinity> I so did.
[00:26] <infinity> I blame the network here.
[00:26]  * infinity gets out and pushes harder.
[00:27] <infinity> Also, CIA is buggered.
[00:28] <cjwatson> Yeah, server-side so can't do much about it
[00:29] <cjwatson> I've been ignoring the giant tracebacks which are the client's response to the server ignoring it
[00:29] <infinity> cjwatson: Committed and tagged, sorry about that.
[00:29] <cjwatson> ta
[00:30] <infinity> cjwatson: I suppose we could at least make cia-clients fail gracefully with a "remote is having a sad" message, instead of taking three weeks thinking before spewing a backtrace of doom.
[00:31] <infinity> Or I could just un-cia all my checkouts.
[00:32] <cjwatson> Or hack the client locally to be a no-op, which is probably better than unconfiguring a load of stuff one by one.
[00:32] <cjwatson> I agree the current behaviour is suboptimal.
[02:47] <Logan_> jelmer: it works now :)
[03:24] <darkxst> jbicha, which GTK theme will you be using?
[03:27] <darkxst> I have noticed that with the ambiance theme, the volume popup is now white
[03:27] <darkxst> however I don't know if this is a bug or intentional on ubuntu's part
[18:50] <pillarsdotnet> Packaging question: How can I make an amd64 package depend on libjpeg62:i386 ? https://bugs.launchpad.net/ubuntu/+bug/502920
[19:05] <penguin42> any tags to use for 'permanently bricks machine' bugs? bug 1040557
[23:57] <nandersson_> Hi, I am setting up Ubuntu Core in a qcow2-filesystem that I now have mounted and chrooted. My final  steps would be to install the kernel (vmlinuz) and setup the bootloader. What would be best practise to pupulate /boot with vmlinuz? Should I do it by doing "apt-get install linux-generic" from within my chrooted environment, or should I copy vmlinuz, initrd and /lib/modules/$(uname -r) from my host?