[12:20] <doko> seb128, pitti, Riddell, ScottK: are any major changes planned before alpha2 during the soft-freeze?
[12:20] <seb128> doko, nothing "major" from the GNOME side
[12:21] <doko> seb128, and no upload which lead to temporary non-installability?
[12:22] <seb128> doko, that I don't know
[12:22] <seb128> we might have a gtk upload
[12:22] <seb128> which usually leads to few hours installability issues
[12:23] <doko> seb128, please could you make sure that things stay installable? we have a test rebuild scheduled during the release according the release schedule
[12:23] <seb128> doko, I've little control on arch all,any delays, but I will make sure to not create issues if that can be avoided yes
[12:29] <doko> thanks
[13:06] <Riddell> doko: no changes, I'd like to see if anything needs done to calligra but that's not on CDs, I'd like to see if I should be worried about oversizing but I won't be able to solve that in time even if I should, I'd like to double check the pyqt binary compatibility issue is fixed and I'm hearing lots of things about X crashing when videos are played
[13:32] <cjwatson> pitti: Would you care to review release-upgrader-{apt,python-apt} in lucid-proposed (I think they landed in NEW, but they're in lucid-updates)?
[13:33] <pitti> cjwatson: sure, doing now
[13:35] <cjwatson> I'm putting together similar apt changes for lucid-proposed and oneiric-proposed too
[13:39] <pitti> cjwatson: accepted
[13:40] <cjwatson> Thanks!  What did we do last time about the aging period for release-upgrader-*?  It doesn't get ordinary testing in -proposed, and update-manager doesn't currently have a way to opt into it
[13:40] <cjwatson> The way you test it is to install the packages before starting update-manager / do-release-upgrade / whatever
[13:41] <mvo> cjwatson: last time (because it was the first time) I moved the upgrade to use -propesed directly but before I ran the entire auto-upgrade-tester suite using the upgrader package (by modifiying the local bzr)
[13:42] <cjwatson> jibel: would it be possible to adjust jenkins to do this temporarily, once these builds land in -proposed?
[13:43] <cjwatson> that might be the most effective way to test this
[13:43] <cjwatson> I could change update-manager but then that affects all users
[13:49] <pitti> yes, I agree; once it's through a successful lts-upgrade autotest, I'm fine with moving them to -updates
[13:51] <jibel> cjwatson, yes, it is possible. I can do that today when the new builds are available.
[13:58] <cjwatson> excellent.  maybe it'll be in time for alpha 2 after all.
[15:05] <stgraber> skaet: good morning!
[15:05] <skaet> stgraber,  good morning!  :)
[15:06] <stgraber> skaet, jibel: So I was wondering what we wanted to do for Alpha 2 on the tracker. Should we hide the Daily milestone during Alpha 2 testing and redirect the automated upgrade testing to the milestone?
[15:07] <skaet> stgraber,  hiding the daily, and redirecting the automated upgrade testing seems reasonable to me.
[15:08]  * skaet curious about jibel's opinion though
[15:13] <jibel> stgraber, I agree with skaet. and displaying daily and a2 would be confusing.
[15:14] <stgraber> jibel: cool, so they'll see Alpha 1 as released and Alpha 2 as testing on the frontpage (want to get them used to seeing more than one thing there) and daily will re-appear post-alpha2.
[15:15] <skaet> stgraber,  sounds good.   Tomorrow's dailies will be the first A2 images.
[15:16] <jibel> stgraber, yes, sounds good.
[15:16] <stgraber> which reminds me, I need to start poking some people, mythbuntu and xubuntu all failed to upgrade yesterday and edubuntu i386 failed too
[15:16] <stgraber> mythbuntu and xubuntu because of unity-greeter crashing. Edubuntu i386 because of gnome-settings-daemon crashing
[15:56] <cjwatson> pitti: would you mind NEWing release-upgrader-apt in lucid-proposed?  I probably ought not to do it myself
[16:09] <Riddell> cjwatson: looking
[16:10] <cjwatson> PS should go to main
[16:11] <Riddell> cjwatson: PS?
[16:11] <cjwatson> postscript
[16:11] <Riddell> I see libapt-inst1.4 and libapt-pkg4.12
[16:11] <cjwatson> in the sense of "an addition to my previous message"
[16:12] <cjwatson> all of libapt-inst1.4, libapt-pkg4.12, and release-upgrader-libapt-pkg-dev should be overridden to main, to roughly match lucid-updates
[16:13] <Riddell> yes, doing
[16:14] <pitti> thanks Riddell
[17:35] <cjwatson> pitti,Riddell: release-upgrader-python-apt now needs binary NEWing in lucid-proposed as well
[17:35] <cjwatson> I've preemptively overridden it to main
[17:39] <slangasek> \o/
[17:40] <jibel> cjwatson, I installed the new packages manually and upgraded lucid desktop i386 and it passes.
[17:40] <slangasek> progress
[17:41] <cjwatson> excellent
[17:41] <cjwatson> jibel: did you pick release-upgrader-python-apt out of LP?
[17:41] <jibel> cjwatson, I did
[17:41] <cjwatson> right, cool
[17:42] <cjwatson> we can probably move that straight to updates once it's in the archive, then
[17:42] <cjwatson> although I guess it might be good to run the whole suite
[17:42] <cjwatson> I'd definitely like to know whether universe passes
[17:43] <cjwatson> or gets further
[17:44] <jibel> cjwatson, the upgrade failed but for another reason: "dpkg: error processing dpkg (--configure): package dpkg is already installed and configured" :(
[17:45] <cjwatson> that's some kind of trigger failure; it's apt's fault, but I'm not convinced it could be related to that resolver change
[17:45] <cjwatson> mvo may be able to work it out?
[17:45] <cjwatson> well, it's *probably* apt's fault
[17:45] <cjwatson> IMO if it gets past the resolver it's a progression
[17:45]  * cjwatson has another go at building lucid DVDs
[17:46] <cjwatson> this time with -proposed switched on
[17:47] <jibel> I'll try again and see if it reproduces
[17:52] <cjwatson> skaet: I've done steps 2-6 from "Release minus 1 month" on https://wiki.ubuntu.com/PointReleaseProcess
[17:52] <cjwatson> skaet: only just asked Evan for the updated build so I expect he might not get back to me until tomorrow
[17:58] <skaet> cjwatson, thanks
[17:59] <cjwatson> (updated build> wubi that is)
[18:01] <skaet> in terms of the A2 release,  slangasek,  I've done steps 2 and 5 from release minus 6 days.  (steveedwards will be the contact, and have put the request in to mvo).
[18:07] <Riddell> cjwatson: is this binary New?  why does it not have a capital N to mark it? http://paste.kde.org/196940/
[18:10] <skaet> https://launchpad.net/ubuntu/r-series and https://launchpad.net/ubuntu/s-series have now been created as future series in launchpad.
[18:10] <skaet> cjwatson, slangasek, Riddell, pitti, and others interested... ^^
[18:11] <Riddell> those are boring codenames :)
[18:11] <skaet> :)  indeed,  however I'm sure they will be made more interesting at the appropriate time,  lol
[19:17] <cjwatson> Riddell: Soyuz gets a bit confused by packages that don't currently exist in the pocket they were uploaded to (or in its ancestry; basically lucid in this case) but that do exist somewhere else in the archive
[19:17] <cjwatson> Riddell: in the new republic^W^W^W^Wwhen I get round to reimplementing this in the API it will look more sensible :-)
[19:17] <Riddell> cjwatson: I see that explains it, I accepted it
[19:18] <cjwatson> thanks
[20:54] <micahg> skaet: I might miss the freeze by a few minutes for some Ubuntu Studio specific packages I'm sponsoring (no impact on anything else)
[20:55] <skaet> micahg,  thanks.  images will be generated by the cron job tonight.
[21:00] <astraljava> skaet: micahg: Thanks guys!
[21:50] <micahg> astraljava: I"m going to do the -meta later tonight, I don't believe your images get spun until 18:00 UTC tomorrow anyways
[21:51] <micahg> skaet: ^^ is that ok, I'm uploading the other packages now for Ubuntu Studio
[21:55] <skaet> micahg, prefer it be done earlier rather than waiting until the wire.   Don't want to have to be special casing it if it misses deadline.
[21:56]  * skaet goes to look at the crontab...   thought it was earlier...
[21:56] <micahg> ok, let me see if I can finish it now then
[21:57] <skaet> micahg, thanks!
[21:57] <astraljava> skaet: Different time than dailies?
[22:02] <cjwatson> we have to spread builds out through the day otherwise they collide too much
[22:04] <astraljava> Yeah I understand. I just didn't know, that's all. :)
[22:11] <micahg> ok, meta uploaded
[22:11] <micahg> for ubuntustudio that is :)
[22:12] <skaet> thanks!
[22:12]  * ScottK just uploaded meta for Kubuntu too.