[00:04] <infinity> cjwatson: Now that we've migrated d-i and switched precise images to -updates, any qualms about me letting the kernel SRU PPA->proposed process carry on as usual?
[00:04] <infinity> cjwatson: (Obviously won't be promoting anything to updates until post-.2)
[00:04] <cjwatson> Hmm - I think that's fine, if we need to rebuild d-i we can turn off -proposed in it
[00:05] <infinity> Shouldn't need to anyway.
[00:05] <infinity> Should we?
[00:05] <cjwatson> Shouldn't.  But it's possible
[00:05] <infinity> d-i doesn't pull in metapackages, and the kernels are addressed by strict ABI.
[00:05] <cjwatson> Oh ISWYM
[00:05] <cjwatson> Yeah
[00:06] <infinity> Right, I'll turn the crank, then and unblock their process.
[09:17] <psivaa> cjwatson: Thanks for the fix for the precise d-i kernel mismatch. Raring server images have similar issues today :)
[09:19] <cjwatson> I guess they would.  Will look
[09:43] <infinity> psivaa: Was just transient.  Bad luck on migration timing.
[09:44] <cjwatson> infinity: you forgot to update the seeds too ...
[09:44] <cjwatson> psivaa: should be happier now
[09:44] <infinity> Oh, bah.
[09:44] <cjwatson> (I updated the seeds and respun)
[09:44] <infinity> As noted, crap night here at casa del finity.
[09:45] <cjwatson> *nod* go sleep.
[09:45] <cjwatson> not that that ever works when people tell me that.
[09:46] <infinity> I'll give it a good effort.
[09:46] <psivaa> infinity: cjwatson: ok thanks, in any case i have had a bug opened to account the failure in the dashboard. I'll close it when the tests start passing
[10:17] <cjwatson> OK, precise builds from here on in should (hopefully) be posted to the .2 milestone on the trackers
[10:18] <cjwatson> localized-iso.qa already had such a milestone with a weird name - didn't notice until after creating the iso.qa one so they're inconsistent, but *shrug*
[10:25] <cjwatson> jdstrand: If you have any security updates for precise between now and next Thursday, please consult with me first - I need to know about them for image preparation.
[10:25] <cjwatson> jdstrand: I've left copy-report enabled for now
[10:58] <ev> Wubi for 12.04.2 is in place but unsigned. RT 59244 will fix that.
[12:28] <Laney> ISTR a file somewhere that shows the size difference between consecutive image builds — where is it?
[12:32] <seb128> Laney, there is a iso-deb-size-compare in ubuntu-archive-tools
[12:32] <seb128> by then pitti was running it somewhere in the CD to look at those things IIRC
[12:33] <seb128> but I'm probably not the best placed to reply to that question
[12:36] <Laney> fair
[12:37]  * Laney prods around nusakan
[12:50] <jdstrand> cjwatson: ok, I'll pass that along to the team as well
[12:51] <jdstrand> cjwatson: openjdk-6 and qt4-x11 are two
[12:52] <didrocks> jdstrand: wait for qt4-x11, there is a subsequent upload coming once kde finished to build on powerpc
[12:53] <jdstrand> didrocks: for precise?
[12:53] <didrocks> jdstrand: oh sorry, I thought you were talking about the NEW raring queue
[12:53] <didrocks> ignore me then ;)
[12:55] <jdstrand> cjwatson: oh, and postgresql-9.1
[12:55] <jdstrand> cjwatson: mdeslaur is handling qt4-x11 and postgresql
[12:56] <jdstrand> cjwatson: I'm handling openjdk-6
[12:56] <jdstrand> I was planning to push openjdk-6 on monday (late)
[12:57] <cjwatson> I need to check what images those are on before you push anything
[12:57] <mdeslaur> I was planning on pushing qt4-x11 and postgresql monday also
[12:59] <cjwatson> openjdk-6 is on Ubuntu server
[12:59] <cjwatson> qt4-x11 is on practically everything
[12:59] <jdstrand> cjwatson: iiuc, this won't actually hurt the images becuase while we might pull during the install, it is by hitting the archive, but adobe-flashplugin/flashplugin-nonfree should be getting an update today
[12:59] <cjwatson> postgresql-9.1 is on Ubuntu server
[13:00] <cjwatson> flashplugin isn't a problem
[13:00] <jdstrand> cjwatson: same for acroread?
[13:00] <cjwatson> yes
[13:00] <jdstrand> k
[13:01] <cjwatson> any chance of deferring qt4-x11/postgresql-9.1/openjdk-6 to Tuesday?  thing is I'm on leave on Monday but I would really like to take a view on what the state of image testing is just before you push them
[13:01] <cjwatson> otherwise I guess I could stop propagation from precise-security to precise-updates and if need be I can build images without -security
[13:01] <mdeslaur> I have no issue with deferring until tuesday
[13:02] <cjwatson> not hugely comfortable with that as a last-minute measure though
[13:02] <cjwatson> I basically just don't want to risk introducing regressions if we have to respin
[13:03] <jdstrand> cjwatson: openjdk-6 is a pretty bit update with 35+ CVEs fixed in it. I won't be done with testing til late monday (local), so I could wait until tuesday (early-midday). would that help?
[13:03] <jdstrand> s/bit/big/
[13:03] <cjwatson> it would, yes, thanks
[13:03] <jdstrand> ok
[13:03] <cjwatson> I should have a pretty clear idea of things by then
[13:03] <jdstrand> cjwatson: I'll still ping you before I do anything
[13:04] <cjwatson> BTW Kubuntu folks it's probably worth starting some 12.04.2 testing now
[13:04] <cjwatson> Riddell,ScottK: ^-
[13:04] <cjwatson> jdstrand: thanks
[13:04] <Riddell> I've got my ninjas onto it
[13:09]  * cjwatson starts work on the 12.04.2 change summary
[14:19] <smartboyhw> cjwatson, where is the changes summary for Ubuntu Studio 12.04.2 LTS?
[14:38] <cjwatson> smartboyhw: I'm writing the full changes summary for everyone at the moment; as for Ubuntu Studio release notes, it's the Ubuntu Studio developers' job to write them, not mine
[14:38] <cjwatson> https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuStudio ← fill them in here as needed; see https://lists.ubuntu.com/archives/ubuntu-devel-announce/2013-February/001011.html for general guidance
[14:51] <stgraber> cjwatson: hey, just noticed something wrong on the tracker, the precise dailies are only publishing in 12.04.2 and not in daily, so my guess is that isotracker.conf is wrong on nusakan
[14:52] <stgraber> (they should all be posted to the Daily milestone and the tracker will automatically copy those to 12.04.2 if they're in the manifst)
[14:52] <stgraber> *manifest
[14:53] <cjwatson> Oh really?  It had been posting them to the daily up to now
[14:53] <cjwatson> Ah, but I only just created the milestone
[14:54] <cjwatson> stgraber: Go ahead and fix, then, sorry about that
[14:55] <stgraber> cjwatson: fixed
[14:55] <cjwatson> (Somebody has it open so I assume that's you)
[14:55]  * cjwatson lands https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/ChangeSummary/12.04.2 on the wiki with a giant thud
[14:56] <stgraber> yeah, basically we always push to Daily, then if any active milestone has the copy-based-on-manifest flag set and matches the series, any product in the manifest gets copied to that milestone.
[14:56] <stgraber> I'll do a quick grep on the wiki, might be that we still say to edit isotracker.conf on there
[14:56] <cjwatson> I think I just misunderstood your earlier comments, but feel free
[15:30] <stgraber> cjwatson: hey, we just noticed that qemu isn't in the server packageset. I just added it by hand now but can you make sure it sticks?
[15:35] <cjwatson> stgraber: it's in core - I've added an exception
[15:36] <cjwatson> so removed from core now
[15:36] <ScottK> cjwatson: Thanks.
[15:40] <stgraber> cjwatson: thanks
[16:06] <skaet> mvo, can you trigger the  GnomeAppInstallDesktopDatabaseUpdate for raring?  so things are right for Edubuntu and Kubuntu next week.
[16:09] <skaet> hmm..   not seeing mvo on line.
[16:10] <skaet> slangasek, cjwatson - are either of you able to trigger the App Database Update for Raring?
[16:15] <cjwatson> no, needs access to rookery.  bdmurray might be able to do it
[16:15] <cjwatson> (mvo doesn't have such access any more)
[16:15] <stgraber> was just about to mention that ;)
[16:15] <skaet> ah,  we'll need to update the process page then.
[16:15] <skaet> bdmurray,  can you help?
[16:16] <skaet> thanks cjwatson, stgraber
[16:21] <bdmurray> skaet: I don't know anything about that and looking around on bignay (which used to be rookery) I don't see anything obvious.
[16:21] <skaet> thanks for looking bdmurray
[16:22] <skaet> slangasek,  any ideas on how we can get this happening now?
[16:22]  * skaet sees that slangasek is down to be working on Raring Alpha 2 a well..  ;)
[16:26]  * xnox had a session booked with mvo about Appinstall data stuff but missed pinging him about having a chat about that.
[16:34] <slangasek> skaet: I know nothing more about it than bdmurray does; I think we'll need to ask mvo
[16:34] <slangasek> xnox: will you follow up with mvo, then?
[16:35] <xnox> slangasek: yeah. will try to catch up with him over weekend / on monday. Same timezone helps.
[16:36] <skaet> thanks xnox,    please let us now if there's going to be a problem with having this done on monday for the alpha 2 image?
[16:38] <xnox> ack.
[16:39] <slangasek> are there any alpha2 images being released that use it?
[16:39] <cjwatson> there's no reason for it to block images if it doesn't happen
[16:39] <cjwatson> milestones are a convenient point to remember to update it every so often, that's all
[16:40] <stgraber> slangasek: I guess Edubuntu does but we don't particularly care about it being a bit outdated
[16:40]  * slangasek nods
[16:40] <antarus> for a minute I thought you meant Ubuntu for alpha arch
[16:40] <antarus> I have not yet had my coffee :x
[16:40]  * antarus might have an alpha in his closet somewhere
[16:41] <slangasek> antarus: you're looking for NCommander
[16:41] <antarus> :)
[16:41] <antarus> slangasek: weird arches fell out of favor with me long ago ;p
[16:44] <NCommander> slangasek, :-P
[16:45]  * NCommander might someday make the threat of  a Ubuntu/m68k port a reality
[16:48] <stgraber> I may still have some old Palm PDA around with a m68k-ish (dragonball) cpu ;)
[16:49] <antarus> most of the Gentoo ports are done by vapier and armin76
[16:49] <antarus> I lost interest after learning that compiling anything on a 143mhz ultra 1 takes *forever*
[16:50] <stgraber> imagine on a 8Mhz m68k ;)
[16:50] <antarus> qemu? ;p
[18:18] <psivaa> cjwatson: bdmurray: the verification of 1066347 with apt-clone 0.2.2ubuntu3 failed on precise. (have reported a new one, bug 1119621 just in case)
[18:18] <ubot2> Launchpad bug 1119621 in ubiquity (Ubuntu) " KeyError: "filename './etc/apt/sources.list' not found" during precise desktop installation on a system that already had precise installed." [Undecided,New] https://launchpad.net/bugs/1119621
[18:19] <xnox> psivaa: how did you verify?
[18:20] <xnox> psivaa: precise images were switched to using -updates only and that package in in -proposed only. So verifying that using a daily is tricky and involves in place upgrade of apt-file.
[18:21] <psivaa> xnox: i verified using  0.2.2ubuntu3 from precise-proposed
[18:21] <cjwatson> yeah, that bug has missed the boat for 12.04.2 now in any event
[19:16] <psivaa> cjwatson: ok :)
[19:33] <mdeslaur> cjwatson: can I release a cfingerd security update? It's in universe, shouldn't have any impact I would imagine.
[19:43] <infinity> mdeslaur: Go nuts.
[19:43] <mdeslaur> infinity: thanks
[19:43] <infinity> mdeslaur: Oh crap, I still need to get sssd out of your PPA.
[19:43]  * infinity does that.
[20:14] <cjwatson> mdeslaur: yeah, stuff that isn't on any images is fine
[20:15] <mdeslaur> cjwatson: thanks
[21:08] <ScottK> Whoever accepted opendkim, would you please accept powerpc too?
[21:08] <infinity> I can.
[21:09] <ScottK> Thanks.
[21:12] <cjwatson> Yeah, I was just hammering on new-binary-debian-universe :)
[21:19] <stgraber> can someone please reject lxc in both precise-proposed and quantal-proposed? hallyn just spotted a bug in my dnsmasq fix which I'll now push to raring and re-upload both SRus
[21:20] <infinity> stgraber: Done.
[21:20] <stgraber> infinity: thanks
[21:29] <stgraber> and lxc re-uploaded everywhere
[21:32] <stgraber> (ignore queuebot for precise, it's confused by the precise-backports lxc ;))
[23:11] <bdmurray> psivaa: your traceback has code and line numbers that indicate it was not the version of apt-clone from -proposed but rather from -updates
[23:33] <phillw> bdmurray: soz to ping, but a real quick question... is the grub2 in raring going to remove old kernels once it has ~3 / 5 already on the system? I'm not sure if I saw it do it on my ubuntu system or when I was on my CentOS system and some has just queried why they have 26 old kernels :)
[23:33] <cjwatson> grub2 has nothing to do with removing old kernels
[23:34] <cjwatson> apt in raring has arrangements to remove old kernels if you use 'apt-get autoremove'
[23:34] <antarus> afaik we are working on a open source pruner
[23:34] <cjwatson> we have one, it's in apt-get autoremove :)
[23:34] <antarus> did it exist in lucid?
[23:34] <cjwatson> no
[23:34] <antarus> ahh
[23:34] <antarus> that would be why then
[23:35] <antarus> how smart is it in terms of not removing the running kernel, or the kernel that grub has selected to run next?
[23:35] <antarus> I will totally ditch ours to use yours, if it works ;p
[23:35] <cjwatson> /etc/kernel/postinst.d/apt-auto-removal
[23:35] <cjwatson> pretty smart
[23:35] <antarus> thx
[23:35] <phillw> cjwatson: thanks.. and that is going to be new to raring? I'd like to tell him and also update the wiki areas on 'how to remove old kernels'.
[23:35] <cjwatson> it's in raring, yes
[23:36] <antarus> cjwatson: ah, raring but not P
[23:36] <antarus> ?
[23:36] <infinity> Oh balls, I didn't upload that for precise.
[23:36] <phillw> i know centos keeps the most recent 3 by default, but they still use grub 0.9..
[23:36] <infinity> cjwatson: I'm totally too late for you, aren't I?
[23:36] <cjwatson> infinity: too late now I think :-/
[23:36] <infinity> phillw: grub doesn't relate at all.
[23:36] <cjwatson> I kept meaning to remind you ...
[23:36] <antarus> infinity: for us, we will backport it internally if needed
[23:37] <cjwatson> grub2 moves old kernels off into a submenu, but it has nothing to do with actually removing them from the system and it never will.
[23:37] <infinity> phillw: Also, RHEL/Cent very rarely bump ABI, so the problem appears less pronounced.
[23:37] <antarus> infinity: wehre can I find teh source?
[23:37] <phillw> infinity: my fault, it is a clean-up in apt?
[23:37] <cjwatson> antarus: it does rely on you being generally able to run apt-get autoremove
[23:37] <antarus> cjwatson: safe to run in pkg.postinst?
[23:37] <antarus> or unsafe?
[23:37] <cjwatson> hell no
[23:37] <infinity> cjwatson: Well, I can upload it today regardless, and we can just not let it in.
[23:37] <antarus> I figured not
[23:37] <antarus> cron it is then ;)
[23:37] <cjwatson> probably impossible to run in a postinst due to reentrancy
[23:37] <cjwatson> infinity: it can be in -proposed at least
[23:38] <cjwatson> and we'll see how validation looks
[23:38] <infinity> cjwatson: Right, that's what I meant.
[23:38] <infinity> cjwatson: Let me do the backport now, so we can point antarus to it.
[23:38] <antarus> thank you