[08:41] <tseliot> hi, can an admin reject fglrx-installer-updates (precise-proposed), please?
[08:44] <RAOF> tseliot: Done.
[08:44] <tseliot> RAOF: thanks a lot
[08:44] <RAOF> tseliot: You should also have all the prime stuff available in precise-proposed now, too.
[08:45] <tseliot> RAOF: this is great news. Thanks a lot for all your help :)
[09:52] <doko> please can somebody unblock ido?
[09:52] <doko> RAOF, ^^^
[09:53] <doko> and libappindicator
[09:53] <RAOF> doko: From where?
[09:53] <doko> RAOF, trusty-proposed
[09:54] <RAOF> Ah, sorry. You'll need to find an actual release-team member.
[09:54] <doko> ok
[10:05] <tumbleweed> doko: there's an alpha releasing today, why does it need to be unblocked?
[10:11] <xnox> tumbleweed: to get 1/6 of ubuntu going. porters work, fixing ftbfs.
[10:32] <cjwatson> doko: I've just stuffed ido into the bootstrap archive for the moment
[10:32] <cjwatson> doko: there's no libappindicator in -proposed
[10:32] <cjwatson> (but I can do the same for it)
[11:16] <tumbleweed> xnox: fixing FTBFS doesn't require migration
[11:17] <xnox> tumbleweed: sure it does, if it never build-before and is needed to be installable on images.
[11:17] <tumbleweed> we're doing ppc64le images in alpha1?
[11:17] <xnox> tumbleweed: it's a low risk change, not affecting alpha1 images.
[11:20] <tumbleweed> erm, it seems to be seeded. anyway, this discussion appears to be pointless because I'm not paying attention enough to be aware of exactly what our alpha1 status is, and wouldn't do the unblock
[11:21] <cjwatson> copying into bootstrap is lower-risk for alpha1 (although I think the migrations in question would be low-risk to start with) so I've just done that.  it's moot.
[14:08] <arges> slangasek: hey yesterday I mentioned that iproute needed to get rejected. What I meant was that iproute_20111117-1ubuntu2.1 (in proposed) needs to be rejected, is there a way to do this? I just pulled it and I still see it there. thanks
[14:08]  * arges realizes this could be very early for you, so ping whenever.
[14:54] <skaet_> darkxst,   is there an ETA on when ubuntu GNOME will have finished the testing?
[14:59] <skaet_> knome, ^ any input on when Xubuntu will be marking the images as ready?
[14:59] <knome> skaet_, i'll get to that later today, i must run now
[14:59] <knome> skaet_, thanks for the reminder
[15:36] <skaet_> slangasek,   looks Edubuntu and UbuntuKylin are marked as ready,   Kubuntu and Xubuntu are still testing, and I've not heard back from ubuntuGNOME folk about their readiness.   Looks like it will be a late in the day release,  will this be a problem?
[15:40] <stgraber> thankfully your release engineer is in the US pacific timezone, so I guess an early release would have been more problematic ;)
[15:41] <skaet_> stgraber,  indeed.  :)
[15:53] <highvoltage> skaet_: is there a technical notes page that needs to be updated?
[15:55] <skaet_> highvoltage,  wasn't sure if you were going to follow the pattern from prior releases of using http://www.edubuntu.org/news/14.04-alpha1 as the site for it,  or you wanted to use a template linked to from Alpha1 like the other flavors
[15:56] <skaet_> I can work up a template for you if you want Edubuntu's notes to be from the WIKI this time around.    Your call.
[15:59] <highvoltage> skaet_: we don't have a lot to share for this alpha, and since it's not intended at all for any kind of end user we feel that it might not be ideal to announce it on the edubuntu website
[16:00] <skaet_> highvoltage, ok,  I'm in a meeting right now with work, but will ping you as soon as I have a template ready.
[16:01] <xnox> highvoltage: well, you need to have a url that you want ubiquity to point to ahead of time, and pass it onto webteam via any releasy/canonical people. Otherwise ubiquity url redirector will keep on using the default fallback which last time i checked was www.ubuntu.com unless otherwise set for a release.
[16:01] <highvoltage> skaet_: ok, no problem/rush/etc.
[16:02] <xnox> highvoltage: e.g. if you want to create 14.04 url already, you can. or better create urls for all the planned milestones, and i can get them updated in the redirector such that you'll be all set for the whole release.
[16:02] <highvoltage> xnox: ah right. I suppose the ubuntu.com redirector can redirect to the wiki page for the alphas.
[16:02] <xnox> highvoltage: typically a wiki page is used, which stays same for all milestones and just content is updated.
[16:02] <highvoltage> xnox: ok, good call
[16:02] <xnox> highvoltage: yeah, wiki page is best.
[16:03] <xnox> highvoltage: and preferably, like not changing names per-milestones. have them at per-release name. typically they are either under TrustyTahr/Flavour/ReleaseNotes, or inverse Flavour/TrustyTahr/ReleaseNotes there seems to be both patterns present.
[16:26] <slangasek> arges: ah, so you need iproute removed from -proposed - yeah, sorry, I misunderstood
[16:26] <arges> slangasek: yup. no problem
[16:27] <slangasek> skaet_: later in the day is fine; I have a hard cutoff at 5pm my time today, but I assume things won't go quite that late?
[16:29] <Riddell> slangasek: what's that is real money?
[16:30] <Riddell> (UTC)
[16:31] <slangasek> UTC-7
[16:31] <slangasek> er, no, UTC_8
[17:00] <skaet_> slangasek, lets make the cutoff for testing input for 3pm your time then.   That will give a couple of hours for any  publishing glitches to get sorted if needed.
[17:00] <skaet_> ok?
[17:01] <skaet_> we'll go with the ones marked ready on the iso tracker then.
[17:02] <slangasek> yep, seems fine
[17:03] <skaet_> xnox,  see the locations for the flavour's release notes from https://wiki.ubuntu.com/TrustyTahr/Alpha1/
[17:03] <skaet_> (am updating Edubuntu's to follow the same WIKI template as the rest though this time - so that will change.)
[17:04] <skaet_> slangasek, can you check the publishing links I've got on https://wiki.ubuntu.com/TrustyTahr/Alpha1/Announce are accurate (for the ones there), and no surprises with the content?
[17:25] <xnox> skaet_: all of them are wrong =) the links shouldn't encode milestone name, as ubiquity only looks up by flavour & version number, and really there is no need to have archive of old release notes and most of them should be carried over to next milestone.
[17:25] <xnox> skaet_: if history is needed, one can easily check wiki page history.
[17:26] <xnox> skaet_: i'll fix those up, and add wiki redirects.
[17:26] <xnox> skaet_: also this whole alpha1 page looks a bit pointless. The contacts, participation and the URL links to the actual images are all on the iso tracker?
[17:27] <xnox> skaet_: as the contacts that matter, are those that are authorised on iso tracker to self-service the respin.
[17:28] <xnox> skaet_: since common infrastructure, is in fact ubuntu/ubuntu core that should be already part of the ubuntu release notes.
[18:40] <infinity> ^-- Wasn't there just a discussion about removing that because it doesn't have a guaranteed stable interface or some such?
[18:41] <cjwatson> hmm, it seems to have been removed and then auto-synced back in, which shouldn't have happened
[18:41] <cjwatson> (then crimsun build-fixed it)
[18:42] <cjwatson> oh, I know
[18:42] <cjwatson> slangasek removed it from the release pocket, but didn't notice that there was already an unmigrated version in -proposed
[18:42] <cjwatson> so when crimsun fixed its build, it remigrated
[18:42] <cjwatson> slangasek: you might want to redo the removal?
[18:46] <slangasek> bitcoin? yeah, will do
[18:50] <skaet_> xnox,  we've been following that pattern with the alpha and beta notes for last 2 releases, since some of the flavors want to do things differently.   Lets discuss after this release is out,  than change right now.
[18:52] <slangasek> skaet_: which flavors have said they want to do things differently?  This pattern is broken, and not changing it now makes more work for the release team later because we have to waste time pushing pages around between different urls
[18:54] <slangasek> if someone else is going to do the work to push the data around, then I guess that's their choice, but going forward I'm going to ignore those extra wiki pages
[18:55] <skaet_> slangasek,  there is a release notes page per flavor, as they want to highlight certain things.   They share common infrastructure bugs and kernel versions.   Flavors are not asking to do things differently, but rather its continuing with the pattern.
[18:55] <slangasek> skaet_: "since some of the flavors want to do things differently." those were your words
[19:00] <skaet_> slangasek, https://wiki.ubuntu.com/SaucySalamander/Beta1 - look at where edubuntu's release notes are.
[19:00] <slangasek> you mean, where they aren't, because that's a dead URL
[19:01] <skaet_> slangasek, it was a live URL at the time
[19:01] <slangasek> yes, and the fact that it isn't now goes to my point that the milestone shouldn't be in the page name
[19:02] <skaet_> slangasek,  xnox - who deleleted the https://wiki.ubuntu.com/RaringRingtail/Alpha* pages?
[19:20] <skaet_> slangasek,  Lets talk about how we want the release notes structured on the mail list for the rest of the release on the ubuntu-release list, rather than just in the channel here.   More may want to participate.
[19:21] <slangasek> funny, I don't remember any mailing list discussion when this was changed to be the way it is now
[19:22] <skaet_> slangasek, it was discussed at connect in Copenhagen.  You stated you didn't want the common infrastructure section in the notes, but were ok with the bugs being shared between the teams.
[19:23] <skaet_> I updated the templates after that, and they have been used that way for the last two releases.
[19:24] <skaet_> if others want the structure to change, fine, just would appreciate not having pages deleted without discussion.
[19:24] <slangasek> I thought we were discussing the fact that a separate release notes page is being created for each milestone, not the use of the include for bugs
[19:24] <slangasek> that was never discussed/agreed
[19:28] <xnox> skaet_: i didn't delete anything.
[19:30] <xnox> skaet_: all common bugs should be on the TrustyTahr/ReleaseNotes, removed/edited/appended as appropriate throughout the release.
[19:32] <skaet_> slangasek, the pattern of copy/paste per milestone, happened for last two organically based on who was doing the notes for the release at the time, from what I can tell.  Especially as it was an opt-in release, and different flavours participated at different times.   I can see merits in switching back to not doing needless copying, but rather evolving a page per flavor over time.    Since Ubuntu hasn't been parti
[19:32] <skaet_> cipating in the opt-in alphas and beta, the centralized focus around release notes wasn't there.
[19:32]  * slangasek nods
[19:33] <skaet_> xnox,  ok, thanks.
[19:33] <slangasek> if it's useful to the flavors that are opting in, I see no reason that TrustyTahr/ReleaseNotes can't be used for the alphas, even without Ubuntu participating
[19:33] <skaet_> slangasek, ok,  lets get this one out the door, and I'll mail out a proposal for the structure going forward to the mail list,  and then over the holidays will do the changes.
[19:34] <slangasek> ok, thanks
[19:35] <skaet_> slangasek,  any comments on the Announce draft?
[19:36] <xnox> skaet_: hm, i don't see there is a need to have any discussions what's so ever. trustytahr is lacking typical releasenotes pages, once created, all others should be setup as redirect (to preserve backwards compat), jobs done and next milestone around release team is suppose to point to where all issues and features are expected to be written up.
[19:36] <slangasek> the edubuntu blurb probably needs word wrapped
[19:37] <xnox> skaet_: it's a release team responsibility to gather stuff together. not forcing flavours to create their own, nor stipulating them to do so by asking "what's your release note page for this milestone?"
[19:37] <xnox> anyway, too late for this milestone =)
[19:37] <xnox> let's push it out the door ;-)
[19:39] <skaet_> xnox,  have been doing the common gather parts, and setting up templates to include them.   The teams are in the best position to highlight what is important for the release from their perpective, so the current system lets them do it.  But revisiting is useful.   :-)
[19:41] <xnox> skaet_: and i totally agree with that. it's just it should be one wiki page, per flavour, per release. alpha/beta notes are irrelevant once a next milestone is release, and milestone images are removed / no-longer available.
[20:15] <Riddell> slangasek: skaet_: I'm stilling running upgrade test but I've had someone say they work fine (and not mark it in iso tracker) so I'm calling kubuntu good for alpha 1
[20:15] <Riddell> release page at https://wiki.kubuntu.org/TrustyTahr/Alpha1/Kubuntu
[20:18] <slangasek> Riddell: ok, shall I mark it ready in the tracker?
[20:21] <highvoltage> skaet_: fixed line-width for edubuntu blurb, made some slight updates to the wiki release page, don't have much else to change there
[20:24] <Riddell> slangasek: I marked kubuntu as ready
[20:24] <slangasek> ok
[20:49] <skaet_> thanks Riddell, highvoltage
[20:51] <knome> xubuntu is ready
[20:51] <knome> skaet_, you should also have mail re: that
[21:03] <skaet_> Thanks knome
[21:03] <knome> np
[21:04] <knome> let me know if you need something else
[21:09] <skaet_> knome,  just checking,  you'll be putting will the release note content on http://xubuntu.org/news/xubuntu-14-04-alpha-1/ after we start publishing,  and not using the WIKI this time around.  yes?
[21:19] <knome> skaet_, yes
[21:19] <skaet_> :) thanks
[21:24] <skaet_> darkxst,  not seeing updates on ubuntu GNOME - will it be going out with Alpha 1?
[21:25] <darkxst> skaet_, sorry bad timezone here
[21:25] <darkxst> I think its ready
[21:28] <skaet_> thanks darkxst, let us know as soon as possible,  we'll have a hard stop.
[21:28] <skaet_> thanks darkxst!   Are the release notes ready?
[21:28] <darkxst> skaet_, let me check, not idea what happened to Ali, he should have been doing this
[21:29] <skaet_> darkxst, yes I haven't seen him either.
[21:31] <skaet_> thanks
[21:48] <skaet_> slangasek, can you start the publishing off now.   All the participants in this alpha have indicated that their images are ready.
[21:49] <skaet_> The release notes are still being update/scrubbed, but that can go on in parallel.
[21:49] <slangasek> skaet_: ok, looking
[21:51] <slangasek> publish-image-set doesn't like me, says 'Current milestone is not marked as "Testing"'; debugging
[21:51]  * skaet_ nods
[21:53] <slangasek> apparently, the 'default milestone' hasn't been updated since quantal :P
[21:55] <slangasek> ok, so I pass the milestone name and it fails saying it doesn't know how to handle Ubuntu Kylin Desktop
[21:55] <slangasek> this is all very sketchy
[21:56] <slangasek> how did publish-image-set stop working?
[21:56] <skaet_> slangasek, am wondering if you're looking in the right place, and something else has replaced it, but the documentation didn't get update.
[21:57]  * skaet_ notes that the milestone page is overdue for a good scrub now as well.
[21:57] <slangasek> oh, this is because of the requested name change from UbuntuKylin to Ubuntu Kylin
[22:00] <slangasek> would really be nice to get back to having proper knowledge in the system of the target sizes of the various images, instead of continuing to ignore oversized indiscriminately
[22:03] <skaet_> Topic for next vUDS?
[22:03] <skaet_> or mail list I guess
[22:03] <slangasek> it doesn't need a discussion, it just needs someone to research what the agreed answers were and do it
[22:05] <skaet_> agreed.  just a question of who.
[22:11] <slangasek> ok, publishing
[22:22] <darkxst> skaet_, release notes done now
[22:22] <skaet_> thanks darkxst.  :)
[23:22] <skaet_> slangasek,  am finding all the images now, and have cross checked the links from the announce and release notes.   Are the torrents ok?
[23:24] <slangasek> skaet_: yes
[23:36] <skaet_> knome,  go ahead and post up the release notes for Xubuntu,  main announce is queued up to be published now.
[23:44] <knome> skaet_, cheers
[23:44] <skaet_> slangasek, would you mind doing the honors to update the topics on #ubuntu-devel and #ubuntu-release?
[23:45] <slangasek> done
[23:46] <Riddell> knome: http://xubuntu.org/news/xubuntu-14-04-alpha-1/ isn't working
[23:46] <Riddell> Page Not Found
[23:46] <knome> is now
[23:48] <skaet_> Thanks slangasek,  cron  jobs all back on?   I've updated the milestone on the tracker as released now.
[23:49] <skaet_> Does anything need to be done to unblock the soft freeze?
[23:53] <doko> infinity, jibel, could you have a look at dh-python's failing autopkgtest?
[23:53] <slangasek> cronjobs on, soft freeze unblocked
[23:54] <skaet_> Thanks slangasek.  :)   And thanks to Riddell, knome, darkxst, highvoltage, stgraber (and others who I've been talking to on other channels) for your help with getting Alpha 1 out the door.  :-)
[23:54] <doko> the tests all pass, or is this just the output to stderr?
[23:54] <slangasek> doko: output to stderr is considered a failure unless you set a flag to explicitly mark it as allowed
[23:55]  * skaet_ breaks for dinner...
[23:55] <knome> thanks skaet_, slangasek, others :)
[23:55] <bdmurray> Riddell: some of the kubuntu uploads for bug 1247235 ftbfs, should the ones that didn't be released piece meal or something else?
[23:55] <ubot2`> Launchpad bug 1247235 in kde4libs (Ubuntu Saucy) "SRU tracking bug for KDE SC 4.11.3" [Undecided,Fix committed] https://launchpad.net/bugs/1247235
[23:59] <Riddell> bdmurray: oh? what didn't build?