[00:11] awesome! [00:34] can someone tell me why python-oslo-config isnt in raring yet, it built fine for raring-proposed 4 hours ago? [00:38] zul: it adds a new binary package which has to be manually approved first https://launchpad.net/ubuntu/raring/+queue?queue_state=0 [00:38] k thanks [00:40] zul: since you're here, how do you want to handle the final comment of bug 1140613? [00:40] Launchpad bug 1140613 in python-warlock (Ubuntu) "Merge python-warlock 0.8.1-1 (main) from Debian experimental (main)" [Wishlist,Fix committed] https://launchpad.net/bugs/1140613 [00:40] jbicha: Its already been taking care of [00:42] zul: oh I see, thanks [00:49] can someone please approve python-oslo-config plrease? [01:48] cjwatson: Woo! [01:50] zul: What's the rationale for the oslo-config package rename? [01:51] infinity: https://bugs.launchpad.net/ubuntu/+source/oslo-config/+bug/1130196 [01:51] Launchpad bug 1130196 in oslo-config "[MIR] oslo-config" [High,Fix released] [01:51] zul: Hrm. I was going to check if there was some sort of python naming policy, but I guess there's precedence for the dot-notation in zope.* and z3c.*, etc. [01:54] infinity: cool thanks [02:47] infinity: cheers for the shibroken. === marrusl is now known as marrusl_afk [09:37] hello! is a freeze happening today? [09:39] ara, hey, I guess so [09:39] ara, it would be logical to stick to the schedule until a decision on the next steps is taken [09:40] ara, it doesn't mean we will not change the freeze or other things in a week if a different path is decided [09:41] ara, well, that's my view on the situation, don't take it as an official statement ;-) [09:41] that's my understanding too [09:41] FYI I warned the PS team this morning about it [09:41] indeed [09:41] we should be sure to announce it today [09:41] so normally, we should be safe on their side [09:42] didrocks, good, I wonder if lars & charles had planned to land any indicator work this cycle, they didn't yet [09:42] didrocks, but let's take that to their channel [09:42] seb128: I think this is aborted by now, I don't see them landing that today ;) [09:43] but yeah, let's talk with him once they are around (I sent the email to their manager about the freeze) [09:48] seb128, thanks! [09:48] seb128, exactly what time is it at? we want to upload a package today so it would be good to know [09:48] normally 2100 UTC [09:49] normally it is at 21:00 UTC [09:49] SNAP === mmrazik is now known as mmrazik|lunch === mmrazik|lunch is now known as mmrazik [13:35] oops, themuso and I both sponsored the nvidia-cuda-toolkit SRU to quantal. queue reject -Q unapproved -s quantal-proposed 5297155 , please [13:37] I'm going to reject the one that didn't run update-maintainer. [13:37] even better :) [13:37] (and I'm impressed you diffed it that quickly) [13:42] hmm, regarding the livefs buld logs it looks like we have a dead armhf builder again [13:42] *build [14:29] qscintilla2 is finally done. === mmrazik is now known as mmrazik|afk [14:44] ScottK: I see you gave up on the symbols file of doom. [14:45] Fornow. [14:45] I know how to fix it, I just didn't quit get it to work right. [14:45] qiut/quite [14:45] Meh. I give. [14:45] Yeah, I gave it a short stab before I left for Hong Kong and threw my hands in the air cursing C++ symbols. [14:46] The answer would have been to hand-write it, in my case. [14:47] Basically, take a few examples from varying arches, see how it plays out, and then hand-craft a file that makes sense, since pkgkdesymbolsthingee wasn't doing me any favours. [14:47] It's probably high time someone broke that out of the KDE packaging tools. [14:47] And then made it less crap. [14:49] 8 [14:49] (grr, sorry) [14:49] apw: Didn't you write a quick and dirty symbols parser/generator when you were grumping over some C++ symbols files? [14:52] infinity: The actual problem is using not using the pkgkde-symbolshelper during the actual build (using it to generate the symbols file isn't - in this case - enough). [14:53] The fact that the C++ stuff isn't included in dpkg-gensymbols (or whichever one it is) is unfortunate. === chuck_ is now known as zul [15:07] so are we in feature freeze? [15:08] 2100 UTC [15:08] so 13.04 is still on then? [15:08] yes, until we hear otherwise === marrusl_afk is now known as marrusl [15:13] It's on until it's not. [15:14] I have a new upstream release for KDE Telepathy that I [15:14] er [15:15] *That I'm packaging at the moment, and will probably upload in a day or two [15:15] do I have to file a FFe? [15:15] Riddell: ScottK ^ [15:24] shadeslayer: Yes. [15:24] bah :( [15:25] infinity: Is sagari stuck? If I read the build log right, the "in progress" build finished a long time ago ... [15:40] ScottK: is that arm? [15:40] ppc [15:40] xnox: powerpc [15:40] hm. [15:41] looks like it's shifted now [15:41] So it did. [15:51] ScottK: It appears "stuck" sometimes because its bandwidth sucks, and the final uploading stage can take a while on large packages. [15:51] OK. Thanks. [15:51] ScottK: It's the only buildd in Boston, and there are some network hiccups there that need solving. :P [15:51] Oh. I had no idea. [15:52] That sounds like the sort of response you'd give to "my mother just died", not "there's a computer in Boston", but okay. ;) === mmrazik|afk is now known as mmrazik === mmrazik is now known as mmrazik|afk === mmrazik|afk is now known as mmrazik === mmrazik is now known as mmrazik|afk [18:41] * xnox ponders if stuff in -proposed at freeze will be let through or not ;-) [18:42] It will [18:42] ok good. === mmrazik|afk is now known as mmrazik === ajmitch_ is now known as ajmitch [20:22] infinity: qscintilla2 and friends just migrated, so that's off the list. === Noskcaj is now known as Noskcaj_AFK === Noskcaj_AFK is now known as Noskcaj === mmrazik is now known as mmrazik|eod [20:38] slangasek, cjwatson, other release team members: Someone should announce feature freeze. [20:39] ScottK: yes, I'm going to send out a mail [20:39] slangasek: Great. [20:39] Thanks. [20:43] * micahg is wrestling with the last few uploads, should be done in ~1.5 hours [20:43] if that's ok with the release team [20:44] Depends on how fast slangasek writes his mail. [20:45] * micahg goes and uploads the thing he's least likely to get an exception for before 21:00 [21:04] ubuntu-armhf-nexus7 on celbalrai.buildd starting at 2013-03-07 21:03:47 [21:04] lockfile: Try praying, giving up on "/home/buildd/buildLiveCD.lock" [21:04] infinity, ^^^ mind giving it a kick ? [21:10] slangasek: just spotted a small problem with the packaging of upstart, I think I fixed it now but it'll take me an extra 5-10min to wait for the test build and post-build tests [21:13] stgraber: ok. I'll consider that "close enough" and worthy of an implicit FFe [21:14] no need to incentivize people to upload broken things to avoid the FFe paperwork [21:17] slangasek: uploaded. Now to hope it'll build on powerpc (only arch I couldn't testbuild) [21:19] Hmm... my ubiquity did not go as well =) [21:19] https://launchpadlibrarian.net/133275922/buildlog_ubuntu-raring-amd64.ubiquity_2.13.13_FAILEDTOBUILD.txt.gz [21:19] we have uninstalability in raring-release? [21:21] packages are built against -proposed, not just against release (for reasons that are obvious if you think about it) [21:22] yeah, but there is no libsoup in proposed. [21:22] yeah [21:22] ah, but something else, can be broken because of it. I see. [21:22] but apt also doesn't bother telling you the real source of the uninstallability in such cases :) [21:25] * xnox will wait for ubiquity to be published in -proposed, and then i'll troubleshoot. [21:25] (src that is) [21:25] it's just skew with glib-networking [21:26] which flavors are doing Beta1 next week? [21:27] Laney: oh, ok. Is it in progress? i see that my i386 built fine =) [21:27] sounds even more like skew then ;-) [21:27] https://launchpad.net/ubuntu/+source/glib-networking/2.35.9-1 [22:04] ScottK: you commented earlier about qscintilla2... I currently see it in components-mismatches, is that a phantom or were you referring to something else? [22:06] slangasek: I was referring to getting it out of proposed. [22:06] It's been stuck there for quite some time. [22:11] slangasek: libqsinctilla2-8 is NBS. That's why it hit CM. [22:12] And it looks like 2-9 needs to be put in Main. [22:12] ok [22:13] (done) [22:19] slangasek: Xubuntu is on board for beta 1 [22:19] I have 2 more uploads to do before we're ready though [22:21] ok [23:08] micahg: I have the gimp 2.8.4 update ready, would you prefer that now or after Beta 1? [23:10] jbicha: now's fine if it's bug fix [23:10] actually, now's fine either way, just request FFe if you need it [23:13] ok, Release Team, it builds, installs and runs here, can I get an IRC FFe for gimp 2.8.2>2.8.4? [23:13] https://git.gnome.org/browse/gimp/tree/NEWS?h=gimp-2-8 [23:15] As per slangasek's email. I'm here to beg to get lightdm 1.5.1 into raring as it's just missed feature freeze (lp:~robert-ancell/lightdm/ubuntu-1.5.1) [23:17] While technically it's a major version bump over 1.4.x the changes are bugfixes, patches from Ubuntu upstreamed and new support for Qt5 [23:18] infinity: doko will buy you beer if you accept https://launchpad.net/ubuntu/quantal/+queue?queue_state=1&queue_text=openssl [23:19] * xnox whoops didn't notice that doko is in the room. [23:30] robert_ancell, you should upload in any case ... it will sit in the queue for acceptance then [23:30] ogra_, ok [23:30] (so it doesnt get delayed even more) [23:31] ogra_: No. It won't. [23:32] robert_ancell: ^^^ [23:32] The archive isn't frozen. [23:32] ScottK, um, I just uploaded it - can you put a block on it? [23:33] hmm, why isnt it frozen if we are in a freeze [23:33] Yeah. We can block the transition to the release pocket. [23:33] ScottK, ta [23:33] ogra_: We have never, ever, ever frozen the archive at feature freeze. Why would you think we were now? [23:33] robert_ancell: lightdm, right? [23:33] ScottK, yes [23:34] ScottK, we froze the queue in the past [23:34] Never for feature freeze. ScottK is correct [23:34] ogra_: Yes. For final pre-release freeze and for Beta freezes. [23:34] hm [23:34] sorry for the misinfo then [23:36] ogra_: As penance, maybe you could clarify this on https://wiki.ubuntu.com/FeatureFreeze :) [23:36] Blocked. [23:36] * ScottK departs. [23:39] Daviey, added a note [23:44] * ogra_ better goes to bed before causing more havoc