[11:47] <zul> can someone review python-jsonschema please its sitting in binary new, and its blocking glance
[12:00] <cjwatson> zul: Sorry for the delay.  For main inclusion, I expect that the MIR team will want (a) a watch file and (b) for the package to run its test suite at build time (e.g. 'python -m unittest discover').  Neither of these block acceptance into the archive, though, so accepted.  Thanks
[12:00] <zul> cjwatson: cool...ill get to that today, thanks
[12:02] <cjwatson> zul: Hmm, why does python-jsonschema seem to install into /usr/lib/python2.7/dist-packages/ directly rather than as a symlink into /usr/share/pyshared/?  Am I hallucinating?
[12:02] <zul> cjwatson: im not sure but ill take another look at it
[12:08] <cjwatson> Not a big deal since there'll be no python2.8, but it's a bit weird
[12:14] <pitti> cjwatson, zul: I think that's completely expected
[12:14] <pitti> dh_python2 just does that now, it seems the /pyshared/ approach has been dropped
[12:15] <pitti> i. e. it affects all python packages now
[12:15] <pitti> not just -jsonschema
[12:15] <cjwatson> Oh, huh
[12:15] <cjwatson> Surprising
[12:16] <pitti> NB I'm not saying that it really should be like that, just that it's not package specific, but a changed behaviour from dh_python2 apparently
[12:16] <cjwatson> Yeah, I see that now
[14:19] <ScottK> pitti and cjwatson: The change doko made in dh_python2 in Ubuntu is uncoordinated with Debian and gratuitously breaks packages.  It should be reverted.
[14:21] <ScottK> The relevant bug is Bug 1001912
[14:21] <ubot2> Launchpad bug 1001912 in python-defaults "dh_python2: revert pyshared removal in 2.7.3-0ubuntu3" [High,Confirmed] https://launchpad.net/bugs/1001912
[15:18] <slangasek> ScottK: doko is currently away so you shouldn't expect a quick response from him; I think you should go ahead and revert it for now as the safer option
[15:18] <ScottK> slangasek: Thanks.
[15:19] <ScottK> slangasek: Would you mind saying so on ubuntu-devel ML too (so I can point to it when he gets back)?
[15:19] <Laney> well, he has been replying on the bug
[15:19] <slangasek> I mind saying on ubuntu-devel that he's away, yes :)
[15:20] <ScottK> slangasek: Right, I mean that I should go ahead.
[15:20] <ScottK> I don't mind leaving the reason out.
[15:20] <highvoltage> I guess inside canonical you have some kind of free/busy calendar.
[15:20] <highvoltage> it would actually be nice if there were somewhere where anyone could mark themselves as temporarily away.
[15:20] <slangasek> ScottK: sure
[15:20] <highvoltage> (sorry I'm just thinking out aloud)
[15:48] <Daviey> cjwatson: Hey, what changes do i need to make on nusakan to start using a livefs?
[15:50]  * ogra_ wonders if you actually need any code changes 
[15:51] <ogra_> theoretically you might be able to just use the right cmdline
[15:52] <cjwatson> Daviey: mail me the details of what you're doing and I can advise and/or sort it out
[15:52] <Daviey> cjwatson: Does it really need a mail?  'make ubuntu server use live-installer'
[15:53]  * ogra_ thinks theoretically teh following might just work ... : buildlive ubuntu-server daily-live && for-project ubuntu-server cron.daily-live
[15:54] <ogra_> but you will likely need ubiquity adjustments or do you plan to run under X ?
[15:55] <Daviey> ogra_: We've tested with d-i net installs, using live-installer udeb, not ubiquty.
[15:56] <cjwatson> Daviey: please mail me :)
[15:56] <cjwatson> I don't have a lot of spare brain
[15:56] <cjwatson> and I need to know what if anything you've done to livecd-rootfs so far
[15:57] <cjwatson> also you guys owe me two live-installer bug reports from UDS
[15:57] <skaet> cjwatson, can you add me to the response.   Would like to understand this.
[15:57] <cjwatson> Daviey: ^-
[15:58] <Daviey> cjwatson: were they not reported.. *sigh*.. Sorry... Well, we can't switch until they are fixed.. So, i'll shelve this, pending those bugs.
[15:59] <cjwatson> Daviey: have you done anything to livecd-rootfs?
[16:08] <Daviey> cjwatson: nein
[16:18] <cjwatson> Daviey: here, I have one of the bugs fixed locally already (missing kernel).  do you remember off the top of your head what the other one was?
[16:20] <Daviey> cjwatson: One was kernel not being installed if outside the squashfs.. and the other was a debconf value for remote retrieval of squashfs
[16:20] <cjwatson> oh, that one
[16:20] <cjwatson> hm, not sure how to do those two simultaneously, mind :)
[16:20] <cjwatson> maybe it would be easier to disable the kernel hack in server squashfs generation for now
[16:21]  * cjwatson also notes that live-installer doesn't seem to update the initramfs, at least from code inspection
[16:21] <Daviey> well.. if you are netinstalling, you don't have the kernel on the filesystem, do you?
[16:21] <Daviey> which means they need additional retrieval, unless bundled into the quashfs (yucky)
[16:22] <cjwatson> bundling it into the squashfs isn't particularly yucky
[16:22] <cjwatson> it's a removal of an Ubuntu-specific optimisation *shrug*
[16:22] <ogra_> all other squashfses carry it
[16:22] <Daviey> well, it means for cd image, the kernel is shipped twice?
[16:22] <cjwatson> Yes
[16:22] <cjwatson> Not the end of the worl
[16:22] <cjwatson> d
[16:22] <Daviey> no.
[16:22] <cjwatson> It makes some difference for space, but we got by without it for quite a while
[16:23] <cjwatson> update-initramfs> Ah, never mind, it'll remove casper and then update-initramfs, now that I look at it
[16:24] <Daviey> cjwatson: okay, bundling seems reasonable, and satisfies cd and netinst.
[16:24] <cjwatson> I've fixed live-installer to cope with unbundling (I think) anyway
[16:28] <skaet> https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule
[16:28] <Daviey> oo, thanks
[16:28] <skaet> has been updated, based on the interlock.
[16:29] <skaet> if anyone spots any glitches,  please flag.  :)
[16:29] <skaet> https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock
[16:29] <skaet> has all the key events in it now as well.
[16:30] <skaet> (getting a few more details added from Linaro though...)
[16:36] <cjwatson> Daviey: and you have network image support as well, assuming I didn't screw it up.  can't easily test it until we have images.
[16:45] <ScottK> Is the chroot problem on nihal known?  See https://launchpad.net/ubuntu/+source/python-defaults/2.7.3-0ubuntu4/+build/3509558
[16:47] <cjwatson> I got ops to fix that, but didn't go through and retry stuff.  Oh, but that's more recent.  Not again.
[16:48] <cjwatson> reported
[16:55] <ScottK> Thanks.
[16:56] <cjwatson> Hope those boxes get upgraded to precise/armhf soon ...
[16:58]  * ogra_ hopes for highbank instead :) 
[17:05] <stgraber> ogra_: you should have put that calxeda server in your bag while there weren't looking ;)
[17:05] <ogra_> damned, now you tell me !
[17:06] <ogra_> though i would have been to sick to carry it i guess
[17:25] <ogra_> geez
[17:25] <ogra_> ubuntu-server-dove/quantal/armel+dove failed to build
[17:26] <ogra_> i wouldnt have thought i'd ever seee such a message again :)
[17:26] <highvoltage> ogra_: awesome!!!
[17:26] <ogra_> heh
[17:26] <ogra_> i doubt building dove was intentional :)
[17:26] <highvoltage> ogra_: that's going straight to google+!
[17:40] <cjwatson> ogra_: wasn't intentional, I was experimenting but not with that; I'll fix it up in a bit
[22:07] <Laney> best. process improvement. ever.
[22:08] <slangasek> ?
[22:08] <Laney> oh, you've ignored queuebot :P
[22:08] <slangasek> ;)
[22:08] <Laney> backports DIY + queuebot = fast acceptance
[22:08] <slangasek> so was that sarcasm? :)
[22:08] <slangasek> ah
[22:09] <slangasek> the queuebot should just send to twitter
[22:10] <stgraber> that's certainly easy to implement ;)
[22:10] <tumbleweed> that was a very fast backport!
[22:12] <Laney> still binary NEW to go!
[22:12]  * Laney whips ubuntu-archive
[22:13] <ScottK> Laney: That's not the proper backports versioning.
[22:14] <ScottK> Should be 1.9.9-1~precise1
[22:14] <Laney> it is what broder and cjwatson came up with at UDS
[22:14] <ScottK> Sigh.
[22:14] <ScottK> Any particular reason to change or are we just changing for changes sake?
[22:14] <tumbleweed> to work around the zaney zebra wrap-around
[22:14] <Daviey> I thought there was a concerted effort to try to reduce the use of codenames post release?
[22:14] <cjwatson> We're about to wrap round the alphabet.
[22:14] <cjwatson> FSVO "about".
[22:15] <cjwatson> We need to stop assuming that codenames sort.
[22:15] <ScottK> OK.
[22:15] <ScottK> Backports is approximately the last place we need to assume that though.
[22:15] <ScottK> err .. stop assuming that.
[22:15] <cjwatson> Indeed.  But why wait? :-)
[22:16] <cjwatson> It's also one of the few places that was assuming it in the first place.
[22:16] <ScottK> It's certainly a change there should be some communication about.
[22:16] <ScottK> OK.
[22:16] <Daviey> well, i would hope that there would be a newer upstream version of software come wrap-around time for the backports usecase..
[22:16] <Daviey> but yes, it's a race regardless.
[22:16] <ScottK> I mind the surprise more than I mind the change.
[22:16] <cjwatson> I was hoping broder would send mail about it ;-)
[22:17] <Laney> hm, the process page doesn't mention versioning at all any more
[22:17]  * cjwatson eyes openlp and wonders if he can get the local primary school to stop using Powerpoint for projecting hymns ...
[22:18] <Laney> the modern age... back in my day we made good with OHP
[22:19] <Daviey> hand written lyrics no less.
[22:19] <Laney> of course
[22:20] <Daviey> kids today, don't know they are born, eh Laney ?
[22:21]  * Laney shares a Werthers with Daviey