=== jbicha is now known as Guest92929 === Guest92929 is now known as jbicha_ === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk [06:17] Looks like nodejs can be synced. That would fix installability of node-resolve. [06:17] Oops, wrong channel. [06:23] Release Team: When will 12.04.3 builds start appearing in http://iso.qa.ubuntu.com/qatracker ? [08:16] slangasek: heya. I'm about to jump on a plane and disappear for 9 hours or so. I created the 12.04.3 milestone on the ISO tracker and checked that nusakan is properly configured for it (first auto-publish + self-rebuild milestone for precise) [08:16] slangasek: everything looks good, so once you're ready and have cron turned off, go to http://iso.qa.ubuntu.com/admin/config/services/qatracker/milestones/301/edit and tick "Automatically publish builds listed in the series manifest", then save the milestone [08:17] slangasek: from that point on, any build being pushed to the tracker for precise which is listed on http://iso.qa.ubuntu.com/admin/config/services/qatracker/series/1/manifest will automatically show up as part of 12.04.3 [08:19] slangasek: I'm currently planning on setting up the paperwork (release notes + announcement) tomorrow (wednesday) morning. If you think we should have those earlier, ping me and I'll try to get them done when I arrive home [09:21] slangasek: -proposed kernels all pushed to -updates, and the matching d-i has been released too. === smartboyhw_ is now known as smartboyhw === doko_ is now known as doko === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === alecu_ is now known as alecu [15:21] Could somebody approve libgksu2-0 in the raring -proposed queue for me? === Ursinha-afk is now known as Ursinha [16:06] bdmurray: accepted [16:29] infinity: ping [17:33] slangasek: pong. :P [17:36] infinity: pacman [17:37] slangasek: Ms PacMan was way better. [17:48] plars: finally got everything in order, first candidate images should be rolling off the line within the hour [17:48] infinity: oh, I didn't copy pciutils over before I started; I don't think that's worth stopping for now fwiw [17:55] slangasek: Yeah, no pciutils should be fine. PCI DBs are a purely cosmetic thing anyway. [17:55] (Though it makes the ISO less pleasant as a debugging tool, but that's a bit of a *shrug*) [17:57] rtg: *poke* [17:57] infinity, ? [17:57] pciutils ? [17:57] rtg: I noticed that intel-microcode SRU of yours claims (at least, according to upstream) to be a scurity fix. Can you coordinate with mdeslaur or someone to make that happen as a security release instead of an SRU? [17:57] rtg: And I'll reject the SRUs. [17:58] mdeslaur: ^ [17:58] infinity, there was no CVE allocated, plus its a multiverse package. is it really worth it ? [17:58] rtg: I'd rather not push security fixes only to -updates, personally. Even for weird multiverse thingees. [17:59] plars: alternate images already available now [17:59] jdstrand, mdeslaur: Opinions? [18:00] do we have any idea what the "important security fix" is in that? [18:01] slangasek: awesome, thanks for the heads up [18:01] psivaa: ^ [18:01] infinity, mdeslaur: there is no changelog on the ucode download page [18:04] mdeslaur: You missed "very". A "very important security fix". Whatever that means. :P [18:04] slangasek: according to http://iso.qa.ubuntu.com/qatracker/milestones/301/builds/51817/testcases - the alternate images are oversized [18:04] plars: nominally; we've agreed to raise the limit rather than try to get them back down to CD size, as that's a lost battle [18:04] infinity: oh! that's changes _everything_ :) [18:04] sarnold: could you please handle rtg 's packages ^ [18:05] mdeslaur: yes [18:07] rtg: ^-- That would have been rejected anyway, due to the version clash. [18:08] sarnold: Bug's https://bugs.launchpad.net/intel/+bug/1212497 [18:08] Launchpad bug 1212497 in intel "[Feature] update microcode to 20130807 version" [High,New] [18:08] rtg: can you provide me with the debdiffs? that's my easiest way forward :) [18:08] thanks infinity [18:08] sarnold: debdiffs of binary blobs don't end well. [18:09] infinity: ah. makes sense. [18:10] sarnold, infinity: so I'm a little confused here. what do you want done with those uploades (aside from fixing the quantal version) ? [18:11] rtg: Just hand them to sarnold and let him sort it through the kernel PPA and release them. [18:11] rtg: I'd like to rebuild the packages in the security ppa and unembargo them through the usual process [18:12] Err... The security PPA. [18:12] I can't brain this morning. Need sugar. [18:12] sarnold, ok, lemme get them prepped. [18:12] rtg: thanks [18:12] sarnold, rtg: Thanks. [18:14] slangasek: Bleh, yeah, the whole world is still a tiny bit oversized. Did we reach a conclusion on carefactor there? [18:14] infinity: pretty sure the consensus was to accept defeat on this front [18:15] * infinity nods. [18:15] slangasek: We could drop unity from the images instead. [18:16] Anyone who needs more than glibc, gcc, and perl is probably using their computer wrong anyway. [18:16] we could drop acid instead; both are about as helpful for getting us to a point release [18:17] slangasek: I suppose if we were going to accept defeat, we could have added some langpacks back, but oh well. There's always .4 [18:42] sarnold, http://kernel.ubuntu.com/~rtg/intel-microcode for p/q/r [18:46] rtg: thanks [18:46] sarlemme know if I've borked the versions [18:46] sarnold, ^^ (damn tab completion) [18:54] infinity: how was the linux update in raring released? [18:54] infinity: I mean with what tool? [18:55] bdmurray: With sru-release, hacked up to remove the bug twiddling because of races. We need to sort that. :/ [18:56] bdmurray: With copies being much (MUCH) faster now, the bug twiddling collides with launchpad's auto-closures and sru-release backtraces itself into oblivion, so I've had to do that. [18:56] bdmurray: (I assume the complaint is that I didn't unsub all the teams, as the tool would have done) [18:56] infinity: okay, well the phased-update-percentage was set (I have a fix for that) but you want to use change-override to set it to 100% in -updates [18:57] bdmurray: Oh. This is about PUP? Check. Is that meant to be set by tools or by LP? [18:57] I may be a bit out of date on my u-a-t branch. [18:57] Ahh, no. No changes to sru-release. [18:57] infinity: I meant I'm working on the fix right now, mp forthcoming [18:58] bdmurray: Is the intent to have sru-release do it, or LP do it? Having it happen in the copy seems saner and less racy. [18:58] sru-release sets it initially to 10% but should for security updates [18:59] s/should/shouldn't/ [18:59] er should not [18:59] right [18:59] bdmurray: Will that be wrong in both pockets? [18:59] * infinity looks. [18:59] no [19:00] https://code.launchpad.net/~brian-murray/ubuntu-archive-tools/no-phase-security/+merge/181129 [19:00] Ahh, no. It's 100 in security, so at least people are getting their updates. Just from a poor, overloaded server. [19:00] * infinity overrides the world. [19:02] bdmurray: I assume dep resolution works fine if something at 100% depends on something at 10%? [19:02] (Not that I'm creating that situation, just curious) [19:03] infinity: that's my understanding [19:03] Alright, linux, linux-ppc, linux-lowlatency, and matching signed/meta stuff all bumped to 100% [19:04] thanks [19:04] We do need to have a bit of a think about the bug twiddling races. Very annoying to have to noop that part of the tool right now. [19:05] Exponential backoff, I suppose. [20:12] stgraber, slangasek: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1214563 [20:12] Launchpad bug 1214563 in ltsp (Ubuntu) "ltsp-client-builder: Unable to locate package linux-image-generic-lts-quantal" [Undecided,New] [20:13] plars: well then! [20:13] how about I fix that [20:15] slangasek: sounds good :) [20:16] slangasek: on the plus side, all the other tests I had been doing on alternate looked good so far [20:17] cool [20:18] so interestingly, wherever the lts-quantal bit lives, it's not in the ltsp source itself [20:18] stgraber: ^^ home yet? Do you know what we've missed wrt ltsp and enablement stacks? [20:40] slangasek: just arrived in Canada but not quite home yet (on my phone). IIRC there's a patch in debian/patches for lts kernels in the precise LTSP source. Extending this to cover the new backport stack should be enough. [20:40] slangasek: if you don't have the time to look at it, I should be able to do it in 2-3 hours [20:41] stgraber: oh... I saw there was no branch for precise-updates and assumed that meant there was no package either, wah :( [20:41] stgraber: ok, I've got it then [21:27] infinity, stgraber: ^^ please review/accept ltsp [21:29] slangasek: could you merge https://code.launchpad.net/~brian-murray/ubuntu-archive-tools/no-phase-security/+merge/181129? [21:34] bdmurray: done [21:36] 2> /dev/null > /dev/null [21:36] Curious construct. [21:37] slangasek: That patch looks a bit fragile and strangely non-deterministic, but I guess you didn't make it any worse than it already was. [21:40] infinity: thanks; I'll respin {k,x,}ubuntu alternates + kubuntu dvd + ubuntu-server once that publishes [21:41] oh, except we've already disabled -proposed [21:41] infinity: how would you like to play this? test rebuild with -proposed, or slam it straight into -updates? [21:42] slangasek: Let me give it a better review (like, a second set of eyes grepping the whole source package), but if it's as obviously correct as it looks, slamming it straight into updates seems fine. [21:43] slangasek: Yeah, that looks Obviously Correct(tm) to me on a review of the full source. I say we just let it build and release it. [21:43] okie [22:02] slangasek: iz copied. [22:13] infinity: ta [22:18] slangasek: And now published to ftpmaster. [22:18] infinity: and wait-for-package trigger set [22:44] plars: 12.04.3 ubuntu/alternate respin imminent [22:47] slangasek: ok [23:19] hmm, server too [23:19] ok