[07:18] <cjwatson> ScottK: done, thanks
[07:37] <darkxst> anyone able to review mozjs17 in the new queue? its really quite important for gnome-shell
[10:35] <knome> hmm, why isn't ubuntu showing up in status.ubuntu.com? https://blueprints.launchpad.net/ubuntu/+spec/topic-saucy-flavor-xubuntu is the blueprint (and i can rename to -s- if that's needed)
[10:35] <knome> *xubuntu
[10:53] <jdstrand> apparmor 2.8.0-0ubuntu16 seems stuck in sauncy-proposed. everthing is built with nothing in NEW and I don't see anything listed in http://people.canonical.com/~ubuntu-archive/testing/saucy-proposed_probs.html. where else should I look to see what is going on?
[10:55] <Laney> jdstrand: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[10:55] <Laney> blocked for alpha 1 preparation
[10:55] <jdstrand> thanks!
[10:55]  * jdstrand jots down url
[10:56] <jdstrand> Laney: I haven't been keeping up with that-- when will alpha 1 be done?
[10:57] <jdstrand> Laney: (ballpark is fine)
[10:57] <Laney> jdstrand: some time today; not sure exactly when
[10:57] <jdstrand> ok, thanks :)
[10:59] <xnox> jdstrand: i'd jot down just http://people.canonical.com/~ubuntu-archive/proposed-migration/ as one sometimes need to look into "update_output.txt" if something is a "valid candidate" but otherwise doesn't migrate.
[11:04] <jdstrand> xnox: cool, thanks
[11:19] <seb128> jdstrand, hey, have you seen my comment on https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1186553 (no hurry for the MIR, just trying to get an estimate for when it will be reviewed)
[11:19] <ubot2`> Ubuntu bug 1186553 in libwebp (Ubuntu) "[MIR] libwebp" [Undecided,New]
[15:03] <cjwatson> ^- rename of click-package.  Sorry.  Not my idea.
[15:03] <stgraber> cjwatson: I'll take a look
[15:12] <stgraber> cjwatson: ^ looks good. I'm assuming you'll take care of removing the old source+binaries?
[15:12] <cjwatson> Yeah
[15:12] <cjwatson> Thanks
[15:25] <skaet> stgraber,  ubuntukylin, ubuntu-gnome are both ready for publishing,   kubuntu should be finished in next couple of hours.  Still waiting to hear back from lubuntu though.
[15:25] <stgraber> ok
[15:26] <stgraber> ideally I'd like to do them all at once to avoid confusing people wrt to whether a1 is released or not (we don't have pre-publishing for those flavours so if I run the script they'll show up on cdimage immediately)
[15:29] <skaet> stgraber,  fair enough.   Lets group kubuntu, ubuntukylin, ubuntu-gnome to start publishing in 2 hours from now.   We'll decide then what to do about lubuntu if we haven't heard back.
[15:29] <skaet> phillw, ^
[15:30] <skaet> Riddell, JackYu, jbicha, darkxst - ^
[15:34] <skaet> stgraber, just heard from phillw,  looks like they'll be ready in 2 hours time as well.
[15:34] <stgraber> ok
[15:40] <phillw> ahh, I was just about to say I've updated the area with what we're releasing :) Desktop PPC is not going to be released and no-one has tested arm.
[15:59] <jbicha> I think arb needs manual hinting since armhf & powerpc have been dropped
[16:00]  * cjwatson looks
[16:00] <cjwatson> I'll just remove the !x86 binaries, probably
[16:00] <phillw> i've just been informed that the alternate PPC is also a no-go.
[16:02] <cjwatson> jbicha: removed, should migrate after next publisher run
[16:58] <stgraber> skaet: looks like all the products that will be part of a1 are ready to publish. Do you know if everyone's ready to push their announcements too? if so, I'll start publishing now, so with the usual delay caused by bittorrent, we should be done in the next 30-45min
[17:02] <skaet> stgraber,   I've set the expectation for 30 minutes for now for it to start, based on the earlier feedback.
[17:03] <skaet> Not heard any push back on that schedule, so lets let the last set of tests results come in.
[17:03] <stgraber> skaet: well, lubuntu said they wouldn't release arm or powerpc and those are the only non-ready products on the tracker
[17:04] <stgraber> anyway, I can wait 30min before publishing, but somebody else will have to monitor bittorrent then because I have a meeting in an hour and I doubt bittorrent will be done by then
[17:11] <phillw> skaet: It's feeding time here, I'll get the release notes updated for lubuntu after food.
[17:12] <skaet> phillw, ack.  let me know when you're done please in this channel.   thanks.
[17:30] <stgraber> starting to publish now
[17:31] <stgraber> note, ubuntu-gnome and ubuntu-kylin are both oversized, publishing anyway but you'll want to fix that by release or have us increase your image size
[17:33] <stgraber> cjwatson: "for-project ubuntu publish-release source current src no alpha-1" is failing with "cdimage.tree.PublishReleaseException: No source daily for saucy on current!"
[17:34] <stgraber> rest looks good, pushing to cdimage now
[17:39] <jbicha> stgraber: UG saucy is actually about 80MB less than raring was and we should cut a few more 10s of MBs tomorrow :)
[17:43] <skaet> thanks stgraber
[17:44] <stgraber> rsync is done, please check that cdimage.ubuntu.com looks good
[17:45] <skaet> Riddell, JackYu, phillw, jibcha, darkxst ^^
[17:50] <phillw> skaet: https://wiki.ubuntu.com/SaucySalamander/Alpha1/Lubuntu :)
[17:50] <skaet> stgraber,  links are all working to the Alpha 1 pages for me.
[17:50] <skaet> Thanks phillw,  good timing.  :-)
[17:53] <phillw> stgraber: lubuntu looks good :)
[17:55] <jbicha> skaet: stgraber: thanks
[17:57] <stgraber> I'm monitoring the torrents, so far none of them works, hopefully that'll change in the next 15min or so, if not I'll poke IS after my meeting in an hour or so
[17:58] <skaet> stgraber,  ok, let me know what it looks like in 15 minutes
[18:21] <skaet> stgraber,  removed those entries not marked as ready from the iso tracker,  and have closed the milestone now.
[18:26] <stgraber> skaet: half the images are available on bittorent, looks like we need to wait a bit longer for the rest
[18:27] <skaet> stgraber, ack.
[18:29] <jbicha> cjwatson: arb is still stuck
[18:36] <infinity> jbicha: Looking.
[18:36] <infinity> jbicha: Looks like NBS in -proposed, poking this theory.
[18:39] <jbicha> I see med-bio depends on arb but it's arch:all
[18:44] <stgraber> skaet: they all started downloading now, so bittorrent is ready
[18:44] <skaet> woot
[18:44] <stgraber> that's all from my side, so just send the announcement when you're ready
[18:45]  * skaet hits send on the announce
[18:45]  * stgraber re-enables cron
[18:45] <skaet> cjwatson, infinity - can you change the header on #ubuntu-release channel
[18:45] <skaet> ?
[18:47] <skaet> heh,  looks like the message is being held in moderator approval.... cjwatson, slangasek, infinity - can you oblige...
[18:48] <skaet> ?
[18:48] <slangasek> looking
[18:48] <skaet> thanks infinity
[18:48] <slangasek> approved
[18:49] <infinity> jbicha: I'm not sure I understand why the arch-restriction for arb was put in place in the first place.
[18:50] <infinity> jbicha: Oh, raxml.  I see.
[18:50] <jbicha> infinity: the latest arb depends on raxml which has an arch-restriction which prevented it from migrating
[18:51] <infinity> jbicha: Okay, better question, does raxml really need to be arch-restricted? :P
[18:53] <jbicha> infinity: the Debian changelog points to bug 791321
[18:53] <infinity> jbicha: Anyhow, stale armhf/powerpc binaries removed.
[18:53] <ubot2`> Launchpad bug 791321 in raxml (Ubuntu) "raxml version 7.2.6-1 failed to build on armel" [Undecided,Fix released] https://launchpad.net/bugs/791321
[18:54] <infinity> jbicha: Erm.  lolwut?  Arch-restricting because someone has -msse in their CFLAGS seems wrong. :P
[18:55] <infinity> jbicha: Given that -msse means it also won't run on all i386 either.
[18:55] <infinity> Oh, unless it absolutely NEEDS SSE.
[18:55] <infinity> In which case, meh.
[19:17] <Laney> all releasey and shizzle?
[19:17]  * Laney removes the megablock
[19:26] <Laney> Riddell: you might want to remove yours too
[20:08] <cjwatson> stgraber: you need to build them first.  cron.source
[20:10] <stgraber> cjwatson: ah good point, I apparently wrongly assumed we had those generated regularly. Doing a run now and will publish those under alpha1 once done.
[20:13] <infinity> stgraber: We don't do them automagically because, except in a freeze, there's no sane way to guarantee that they match all the images from that day anyway, so it's really just a waste of resources.
[20:13] <infinity> (This is likely true for soft-freeze milestones too, but meh, they get close enough)
[20:38] <skaet> cjwatson, infinity, stgraber - normally we'd close a milestone after the release went out (as documented in the MilestoneProcess), but with it being now 13.06 - and it not being end of month.  its ambigous.  thoughts about whether to close or not?
[20:39] <skaet> I did go in and close 13.05 as a target,  which was still open.
[20:39] <stgraber> skaet: we'll just wait till end of month
[20:40] <stgraber> cjwatson: so cron.source worked but the tree under www/full/source looks rather weird (it published under full/source/source/20130627/source), are there any environment variables or arguments I'm supposed to pass to have it publish to the right place?
[20:41] <skaet> stgraber,   ok,  who? and where documented?   (since 13.05 was still open,  probably something needs to be written down ;-) )
[20:42] <infinity> It should be done around the end of a month but, on the other hand, if people target things to the past, I suppose they get to keep that result. :P
[20:42] <infinity> Writing it down will only help if it's a document someone reads.
[20:42] <stgraber> was just about to say that ;)
[20:42] <stgraber> it's not something we can tie to our milestone process so it's just something that people who have rights to do so should check every so often
[20:43] <stgraber> it's not a big deal if a milestone isn't disabled for a few weeks, so long as it's all done by release time
[20:43] <stgraber> (I usually tend to notice when targeting bugs, if I spot an expired milestone in the list I tend to go and disable it)
[20:47] <skaet> stgraber, infinity - ok.  MilestoneProcess has been updated to remove the reference.
[21:19] <stgraber> ^ I'll take that one
[21:28] <bdmurray> although bug 1100586 has not been positively verified, I am inclined to release it as there are no regressions and it is a minimal patch
[21:28] <ubot2`> Launchpad bug 1100586 in xserver-xorg-input-synaptics (Ubuntu Quantal) "unable to use Apple Wireless Trackpad" [High,Fix committed] https://launchpad.net/bugs/1100586
[21:36] <ScottK> Just got rid of Riddell's Alpha 1 mega block.
[21:40] <infinity> ScottK: Lovely.  The kernel team will be happy to hear that. :)
[21:57] <Ursinha> infinity, StevenK, wgrant, are we meeting today? :)
[22:00] <infinity> Ursinha: Yep.
[22:01] <cjwatson> stgraber: I think it's just odd like that
[22:34] <stgraber> cjwatson: well, publish-release fails to find it there so something's wrong somewhere
[22:43] <Ursinha> !@!@#&*$#&*
[22:43] <Ursinha> wgrant, StevenK, infinity, gah
[22:44] <Ursinha> I'm sorry guys, I don't know wtf is going on
[22:49] <Ursinha> sigh
[22:49] <Ursinha> wgrant, what's the bug number?
[22:50] <wgrant> Ursinha: https://bugs.launchpad.net/launchpad/+bug/1064895
[22:50] <ubot2`> Ubuntu bug 1064895 in Launchpad itself "Translations processed in-band by the publisher" [Low,Triaged]
[22:56] <Ursinha> thanks wgrant :)
[23:17] <tumbleweed> what makes it onto the new source images? seeded packages?
[23:24] <infinity> tumbleweed: Source images should be (barring bugs) the combination of all sources for all binaries found on all images.
[23:25] <tumbleweed> ok, I assumed something like that from the size
[23:25]  * tumbleweed teaches seeded-in-ubuntu not to fall over them