=== amichair is now known as amichair__
[09:16] <cjwatson> bdmurray: ok
[09:17] <cjwatson> bdmurray: hmm, your bug bot seems to be removing apt-clone state tarballs from bugs (e.g. bug 884515) - is that intentional?  I don't know that I much care about the particular bugs in question, but in general apt-clone state is invaluable for debugging upgrade bugs and I didn't think there was anything sensitive in it
[09:17] <ubot2> Launchpad bug 884515 in opendnssec "package opendnssec-enforcer-mysql 1.1.3-3 failed to install/upgrade: ErrorMessage: package opendnssec-enforcer-mysql is not ready for configuration cannot configure (current status `half-installed')" [High,Fix committed] https://launchpad.net/bugs/884515
[09:39] <cjwatson> (ah, I see seb128 asked the same thing in #ubuntu-devel)
[14:54] <bdmurray> cjwatson: its intentional there was a security upload about it
[14:58] <cjwatson> I see, ok
[15:00] <cjwatson> xnox: we should talk about this installer partitioning work before I completely forget about it; mumble?
[15:00] <xnox> cjwatson: ok.
[15:01] <xnox> I just spoke with slangasek about it a bit
[15:25] <NCommander> cjwatson: how would you feel about moving extlinux-update from syslinux to syslinux-common; highbank platform uses extlinux.conf, and implemented extlinux (basically) in uboot. I rather not overly duplicate code in flash-kernel
[15:26] <cjwatson> NCommander: I don't really have any stake in it or knowledge about it; ask Daniel Baumann in Debian?
[15:26] <cjwatson> I do very much like the fact that syslinux is in sync with Debian again - it was a real hassle for a while - so would thank you not to diverge again unless we have a *really* good reason :)
[15:27] <NCommander> cjwatson: I can replicate the extlinux-update script in flash-kernel. Its a bit of code duplication, but I rather not diverage a packageif it can be avoided
[15:27] <NCommander> (didn't realize we got syslinux in sync with Debian \o/)
[15:36] <roadmr> Hi folks! I have a preseed that automates installation, but if I plug in a USB stick and then boot, Ubiquity gets confused and stops to ask me which type of install I want to do. Is there a way to tell Ubiquity that I want to erase everythiing on /dev/sda and install there? should it honor d-i settings? (that seem to work fine when using alternate or server)
[19:49] <eagles0513875> hi guys :)
[19:50] <eagles0513875> anyone want their brains picked
[19:50] <eagles0513875> with two majorly annoying issues?