[00:10] <skaet> slangasek, ping?
[00:22] <cjwatson> lamont: FYI - the trigger's in lp:ubuntu-archive-publishing, and deployed in some path on pepo that "locate ubuntu-archive-publishing" should readily find
[00:23] <cjwatson> anyone in ~ubuntu-archive should be able to merge stuff for you, and anyone with lp_archive@pepo can deploy
[00:24] <cjwatson> by whichever of "bzr pull" and "bzr up" does something
[00:31] <skaet> cjwatson, hiya, would you mind turning on the freeze for alpha 1?  not seeing response from slangasek.
[00:33] <skaet> infinity, ^ you able to help?
[00:33] <cjwatson> sorry, about to go to bed, seriously tired.
[00:33] <skaet> understand,  very late there.
[00:33] <cjwatson> not competent to operate non-trivial machinery :)
[00:34] <skaet> hopefully slangasek will pop back on soon, or inifinity can help then.    sleep well. :-)
[00:35] <skaet> stgraber, you able to help out?
[00:54] <slangasek> skaet: hi, looking now
[00:54] <skaet> thanks slangasek
[01:04] <slangasek> hmm, if someone has a tool for collating the list of packages to block in proposed-migration, I'm not finding it
[01:05] <cjwatson> Laney and ScottK are the people to ask IME
[01:05]  * cjwatson really falls over
[01:05] <slangasek> ScottK: ^^ do you have a standard tool I can use for setting the freeze block?
[01:18] <slangasek> ok, think I managed to figure something out based on the task fields; committed
[01:19] <slangasek> this unfortunately doesn't grab kylin, since it doesn't use seeds... will grab a package list from the latest image and merge
[01:42] <skaet> JackYu, ^ check the backscroll.    Let slangasek know if you spot issues.
[09:04] <Laney> slangasek: I have a script based on the seeded-in-ubuntu data, which comes from manifests
[09:04] <Laney> will update the block
=== doko_ is now known as doko
[09:26] <Laney> done
[09:28] <xnox> Laney: commit it to ~ubuntu-release owned branches? =)
[09:28] <Laney> oh man
[09:28] <Laney> I'd have to give it things like help and options
[09:28] <Laney> you just edit the script to specify which flavours are participating now ... :(
[09:29] <xnox> it's best to spend minutes improving something out there, then to re-invent the wheel each time =)
[09:30] <Laney> you've inspired me
[09:30] <Laney> I'll do it
[09:37] <sil2100> Hello guys
[09:58] <sil2100> We wanted to release a new ubuntu-ui-toolkit for Ubuntu Touch yesterday, but it got blocked in -proposed due to the freeze
[09:59] <sil2100> Is any of the flavours using it in the Alpha? It's a Ubuntu Touch critical component and we would need to be able to land it
[10:01] <Laney> sil2100: qtdeclarative5-ubuntu-ui-toolkit-plugin (from ubuntu-ui-toolkit) is seeded in: edubuntu: dvd ubuntu-touch: daily-preinstalled ubuntu: daily-live ubuntukylin: daily-live
[10:02] <Laney> http://people.canonical.com/~ubuntu-archive/germinate-output/edubuntu.trusty/rdepends/ubuntu-ui-toolkit/qtdeclarative5-ubuntu-ui-toolkit-plugin
[10:02] <highvoltage> ubuntu-touch stuff love creeping into edubuntu :)
[10:03] <Laney> they deliberately got the webbrowser-app into desktop
[10:03] <highvoltage> ah
[10:06]  * sil2100 sighs
[10:07] <sil2100> I would prefer Ubuntu Touch development not being slowed down, so that we can release our stuff normally when needed
[10:07] <sil2100> Laney: is there anything that can be done in this case?
[10:11] <Laney> You can argue that things aren't risky for the alpha on a case-by-case basis
[10:14] <Laney> We made the freezes last only two days to try to get out of the way of everybody else, btw
[10:17] <xnox> sil2100: one can spare between 24h  and 48h of freeze. And the release schedule was published long time ago, with milestone weeks in them. One doesn't get to converge (e.g. webbrowser-app in ubuntu touch, desktop, edubuntu, kylin) without co-ordinating landing.
[10:18] <xnox> sil2100: during milestones it needs to be co-ordinated with all flavours, which is done via ubuntu release team.
[10:18] <xnox> sil2100: as has always been the case in ubuntu.
[10:19] <Laney> Arguing case-by-case is something that everyone else has to do --- which is fair enough IMO as we have taken the first small steps towards convergance by putting webbrowser-app on desktop.
[10:19] <Laney> So, feel free to do that. :-)
[10:19] <xnox> sil2100: $core  gets blocked pretty much all the time by everything =) work / test against -proposed and stage more things there.
[10:20] <xnox> (granted the usual disclaimers and possible transient non-installabilities)
[10:23] <sil2100> I didn't hear anything about UITK being converged already between desktop and touch
[10:23] <sil2100> But maybe Didier did know about this
[10:25] <Laney> https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.trusty/revision/2179
[10:25] <sil2100> ...and so he did
[10:25] <sil2100> ;)
[10:27] <infinity> sil2100: I wish people would stop propagating this myth that blocking proposed migration slows down development or prevents people from working.
[10:27] <infinity> sil2100: If it's that hard to develop or test against proposed, perhaps some processes need to be reexamined.
[10:28] <apw> if it did touch stopping libc migrating for 14 _days_ would have stopped all development for that long
[10:29] <sil2100> infinity: I think used a wrong set of words when saying this - it's not such a big deal, we can surely live without it for now, we're just eager to release a new image with the fixes included there
[10:30] <infinity> sil2100: Sure, and we made the freezes super short so these minimal inconveniences are even more minimal and less inconvenient than before.
[10:30] <infinity> sil2100: In some cases, mind you, we can unblock some stuff if the people whose images it'll land on say they don't mind.
[10:31] <sil2100> Thanks, I guess we'll just be patient
[10:32] <sil2100> The new UITK should be safe, as we tested it on desktops (automated tests through cu2d) and on touch images (manual testing + automated testing made by humans) - but as I said, it's not so urgent so that it *requires* an exception
[10:33] <sil2100> It was more like frustration regarding my lack of knowledge of this happening
[11:35] <stgraber> skaet_: just saw your ping now. I just got off a very unpleasant 6 hours turned into 10 hours flight to Europe and am off today, so if you still need me, wait till tomorrow ;)
[14:32] <plars> cjwatson, infinity: wanted to make sure you saw bug #1622053
[14:33] <plars> sorry, bug #1262053
[14:33] <ubot2`> Launchpad bug 1262053 in Ubuntu CD Images "Precise d-i daily installations fail with kernel version mismatch" [Undecided,New] https://launchpad.net/bugs/1262053
[14:33] <cjwatson> not going to have time to look today, remind me tomorrow if it isn't magically fixed
[14:33] <plars> cjwatson: np
[15:10] <xnox> infinity: cjwatson: doko: boost uploaded with python-paste split into a separate package, targetted at universe. please new it into universe & gccxml can go into universe then as well.
[15:13] <infinity> xnox: You might want to fix that upload.
[15:13] <xnox> infinity: yeah =/
[15:13] <xnox> noticed.
[15:14] <xnox> infinity: didn't do matching mpi upload at all....
[15:14] <infinity> xnox: Well, you failed to split it. :P
[15:15] <infinity> xnox: Anyhow, no need to ping people about stuff like this, component-mismatches will tell us the good news.
=== superm1_ is now known as superm1
=== debfx_ is now known as debfx
[21:04] <arges> hi. can I have a package rejected please? iproute for R/P/Q, I found a _very_ minor regression and I'm working on a proper fix for it.
[21:28] <slangasek> arges: done
[21:30] <arges> slangasek: thanks