[00:00] <rsalveti> infinity: that's what I'm trying to find out
[00:00] <rsalveti> but yes, cogl-dev should be the one pulling egl here
[00:01] <infinity> rsalveti: (But given our beta timeline, working around it in clutter's build-deps for tonight seems acceptable)
[00:01] <rsalveti> yeah
[00:02] <rsalveti> hehe, libcogl-dev is not depending on any mesa related package
[00:02] <rsalveti> not for gl and not for egl
[00:02] <infinity> Yeah, that seems like a bug to me.
[00:02] <infinity> And probably just unnoticed because clutter is cogl's only consumer that anyone cares about, and it build-deps on gl/egl.
[00:03] <infinity> Or did, until just now. ;)
[00:03] <rsalveti> exactly
[00:05] <kees> infinity: oh, does that eglibc update include my crazy vfprintf fix?
[00:06] <infinity> kees: I don't like it when you use the word crazy.
[00:06] <micahg> can someone please tell me if I need an FFe for this: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/libav.git;a=blob;f=Changelog;h=cb04ee49926d4bf11d9480c2a8cf3092416991f7;hb=HEAD#l15
[00:07] <micahg> oh, nevermind, APIs added, will file an FFe
[00:07] <kees> infinity: sorry, trying again... does that include my fix for crazy vfprintf?
[00:07] <infinity> micahg: Added beats removed at least.
[00:07] <infinity> kees: Your sane fix for a crazy vprintf?  Yes, yes it does.
[00:07] <kees> \o/
[00:07] <infinity> vfprintf, even.
[00:08] <kees> cool, I didn't want precise to miss out on that.
[00:08] <micahg> infinity: indeed :)
[00:08] <infinity> kees: CVE-2012-0864, yes?
[00:08] <ubot2`> infinity: ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0864)
[00:08] <infinity> ubot2`: You're not helpful AT ALL with CVEs, stop trying.
[00:08] <ubot2`> infinity: Error: I am only a bot, please don't think I'm intelligent :)
[00:10] <infinity> kees: Do you know if anyone at mitre has ever discussed actually pulishing CVEs in a timely manner?  I love how they lag disclosure time by, sometimes, months (or years).
[00:12] <infinity> rsalveti: armel still sad.
[00:12] <rsalveti> infinity: let me check
[00:12] <infinity>  /usr/include/cogl/cogl/cogl-defines.h:33:23: fatal error: GLES2/gl2.h: No such file or directory
[00:13] <infinity> Definitely points to missing deps in cogl-dev, at least. :P
[00:13] <rsalveti> infinity: yup, cogl-dev broken
[00:13] <rsalveti> I'm trying to fix it properly there, 1 sec
[00:13] <infinity> Check.
[00:14] <infinity> rsalveti: I've got all night and freeze isn't until tomorrow, let's just do it right and be done with it.
[00:14] <rsalveti> infinity: yeah
[00:19] <kees> infinity: mitre has been getting worse and worse :(
[00:20] <kees> but yeah, that's the CVE
[00:20] <infinity> kees: That's not saying much, given how bad they were back when I used to deal with them a lot.
[00:52] <cjwatson> Sod it, I'd worked out how to fix the lubuntu/xubuntu generic kernel thing so just did it.
[00:53] <micahg> skaet: FYI, there's a new chromium security release coming, idk if it'll be released before Beta freeze, but it should be this week
[00:56] <cjwatson> knome: ^-
[01:19] <micahg> skaet: heh, Chromium was just released, I'll get it in before the freeze
[01:52] <ScottK> broder: If you still need a volunteer for New, I'll do it if it's a sync from Debian.
[02:01] <ajmitch> ScottK: how much longer do you think we'll be allowed to sync new packages & have someone review them? :)
[02:01] <ajmitch> & how much does it cost?
[02:01] <ScottK> If they're syncs, not much.
[02:01] <ScottK> How late depends on why.
[02:02] <infinity> ScottK: Are you trying to talk broder out of baking me cookies?
[02:02] <ScottK> No.  He should do that on general principles.
[02:02] <ajmitch> ScottK: just packages that might be 'nice-to-have'
[02:03] <ScottK> ajmitch: Depends on my mood, I guess.
[02:03] <ajmitch> ok
[02:03] <ajmitch> I'll try & be super-nice to you when I'm ready to ask for them
[02:03] <ScottK> infinity: Is he someone who's cooking you want to eat?  You might be better off with store bought.
[02:03]  * ScottK doesn't know.
[02:04] <infinity> ScottK: He did mention something about "recipes".  That might be a warning sign.
[02:04] <infinity> Even I can make cookies without looking up how.
[02:04] <ScottK> Or a good one.
[02:05] <ScottK> I mean, if you can read you can cook as long as you can do the steps in the right order.
[02:05] <ScottK> Computer people ought to be reasonably capable in that regard.
[02:06] <infinity> Sure, but it relies on you having a good recipe to start with.
[02:06] <infinity> Not all cookies are created equally. :P
[02:06] <ScottK> That's definitely true.
[02:08] <rsalveti> infinity: bug 961798
[02:08] <ubot2`> Launchpad bug 961798 in cogl "libcogl-dev should also depend on gl/gles -dev packages" [High,In progress] https://launchpad.net/bugs/961798
[02:08]  * micahg figures there are at least 300 packages that should probably be sync'd for one reason or another ATM
[02:08] <rsalveti> infinity: https://launchpadlibrarian.net/97809829/cogl_1.10.0-0ubuntu2.debdiff
[02:08] <rsalveti> infinity: with the previous clutter debdiff I posted at the other bug it worked fine now
[02:08] <rsalveti> after pushing this package to the ppa
[02:09] <rsalveti> finished fine for all archs
[02:09] <infinity> rsalveti: Alright, I'll get on that.
[02:12] <infinity> rsalveti: I suppose that also means that clutter no longer needs the GL build-dep on !arm either.
[02:13] <infinity> rsalveti: Unless it has a local, non-cogl reason to need it too, then it's correct as-is.
[02:13] <infinity> (Even if slightly redundant)
[02:13] <ogasawara> skaet, kees: kernel uploaded.  based on previous build times it should finish in time for us to rev and upload linux-backports-modules and linux-meta before the 21:00UTC beta-2 freeze deadline.
[02:13] <rsalveti> infinity: there's a local reason for that, but yeah, redundant
[02:13] <infinity> rsalveti: Local reason's enough for me.  I'll sponsor these as-is.
[02:14] <rsalveti> infinity: great, thanks
[02:14] <ajmitch> micahg: that many?
[02:15] <micahg> ajmitch: yeah, I think so, between really outdated upstreams, dh_python2, RC, FTBFS, and translation updates
[02:15] <infinity> ogasawara: Dangit, you should have warned me.
[02:15] <infinity> ogasawara: I could have aimed the i386 build at a builder that doesn't suck.
[02:16] <ajmitch> micahg: I'll look at the rc list this weekend, I guess I may be filing a few FFes :)
[02:16] <ogasawara> infinity: ahh dammit
[02:17] <infinity> I suppose I still can.
[02:17] <ogasawara> infinity: I think we have enough time even if the builds are slow
[02:18] <infinity> ogasawara: Yeah, but fast doesn't hurt, and we have two quick builders available for x86.
[02:18] <ogasawara> infinity: I won't argue if you move it to a faster machine :)
[02:22] <infinity> ogasawara: There, you have roseapple and allspice for your x86 builds now.
[02:22] <infinity> ogasawara: And PPC should be starting in ~15m.
[02:22] <micahg> infinity: will you be around in ~2hrs for a round of package copies?
[02:23] <infinity> micahg: Maaaaaybe.
[02:23] <micahg> heh, also, can you reset to auto the other buildds :)
[02:24] <infinity> micahg: No.
[02:24] <infinity> (I'd already done it before you asked)
[02:25] <infinity> ogasawara: Is there a ti-omap4 merge in the works to match the changes in -20.32?
[02:25] <micahg> ah, I refreshed like 5 times
[02:26] <ajmitch> micahg: blame LP's caching or something
[02:26] <micahg> infinity: I'll just have the package copies done in the morning, I guess a few hours won't hurt at this point
[02:27] <infinity> micahg: I'm sure I'll be around laterish, if you poke me.
[02:27] <infinity> micahg: And if I'm not, pitti will be up in 3 or 4 hours. :P
[02:27] <micahg> ok, well, I'd prefer to use my AA favors tonight for other things :)
[02:28] <infinity> There isn't a limited number you can use.  It just affects how much of my homework I'll make you do later.
[02:31] <ogasawara> infinity: I suspect ppisati will get to it in the morning.  I wouldn't consider it urgent for arm as the patches only affect amd64/i386.
[02:31] <infinity> ogasawara: Oh, really?  I assumed it was a generic thing, didn't look closely.
[02:31] <infinity> kees: Stop implementing x86-only security features, jerkpants.
[02:32] <ogasawara> heh
[02:36] <micahg> chromium's uploading
[03:02] <nigelb> lol
[03:03] <micahg> finished about 7 minutes ago
[03:08] <stgraber> can someone look at ubuntuone-client in NEW? it's currently breaking upgrades here
[03:08] <stgraber> they apparently introduced ubuntuone-client-proxy
[03:10] <stgraber> FFe is bug 929207
[03:10] <ubot2`> Launchpad bug 929207 in ubuntuone-client/trunk "[FFE] Proxy "tunnel" for syncdaemon" [High,Fix released] https://launchpad.net/bugs/929207
[03:24] <infinity> stgraber: Done.
[03:28] <stgraber> infinity: thanks
[04:36] <infinity> cjwatson: You know, now that iwj isn't around to complain anymore that his mirroring tool from 1996 won't work without it, I wonder if we shouldn't discuss dropping ls-lR.gz from the archive (and the 6 minutes it takes to generate...)
[04:37] <infinity> pitti, slangasek: Thoughts? ---^
[04:47] <rsalveti> infinity: seems clutter is just waiting to hit the archive, then we'll be finally able to trigger clutter-gst
[04:47] <rsalveti> and see if the image is blocked by another package
[04:47] <rsalveti> infinity: are you also able to trigger new image builds?
[04:48] <infinity> rsalveti: I am.
[04:48] <rsalveti> great
[04:48] <infinity> (And I know that we're waiting on clutter to be published, see above about my annoyance with the publisher taking so long) :P
[04:49] <infinity> It overlapped its lock and missed the :33 run, so I have to wait for :03.
[04:49] <rsalveti> yeah, thought it was related :-)
[04:54] <slangasek> infinity: huh.  I know nothing about ls-lR.gz (I had long forgotten it was there), so I defer to the mirrors team.
[04:56] <infinity> slangasek: Well, it wasn't there for a good while after we did the katie->soyuz switch, and no one complained until we hired iwj and he had a fit that his ancient mirroring tool (forget what it was) wouldn't work. :)
[04:57] <slangasek> yes - still, I'd ask the mirroring team since they're the only ones likely to care about it
[04:57]  * infinity nods.
[04:57] <infinity> Fair enough.
[05:13] <kees> infinity: there are detailed instructions on how an architecture can enable it in the HAVE_ARCH_SECCOMP_FILTER Kconfig help :) also, ARM is planned, but after this one is all the way upstream first.
[05:14] <kees> ogasawara: nice!
[05:14] <infinity> kees: I'll show you "all the way upstream".
[05:14] <infinity> Or something.
[05:15] <kees> hehe
[05:15] <kees> my choice of phrasing was intentional there :P
[05:20] <broder> ScottK: oy! my cooking is *just* fine, thank you :-P
[05:50] <infinity> rsalveti: Kicking off new armhf ubuntu-desktop dailies in 3600 seconds.
[05:51] <rsalveti> infinity: awesome
[05:51] <infinity> rsalveti: (As in: sleep 3600 && do stuff)
[05:51] <infinity> Since I won't be around then. ;)
[05:51] <rsalveti> I might be available still
[05:52] <infinity> Well, I'm going out for a bit.
[05:52] <infinity> I'll be back later to check on them.
[05:52] <rsalveti> great, thanks
[05:52] <infinity> But thanks for the clutter fixes.
[05:53] <infinity> Now, if you can convince markos to make gnat go (or maybe put someone like riku on the problem?), I'll love you forever.
[05:54] <rsalveti> yeah, will ping them
[05:54] <pitti> good morning
[05:54] <rsalveti> morning!
[05:54] <pitti> micahg: still need package copies?
[05:54] <infinity> Guten watevertimeofdayitis.
[05:54] <micahg> pitti: no, not ready unfortunately, decided to do stuff for beta 2 instead
[05:55] <pitti> infinity: I don't know of anything which needs ls-lR.gz, it just sounds like something for client-side mirroring?
[05:55] <infinity> pitti: Yeah, it's all about mirroring.
[05:55] <infinity> pitti: As vorlon suggested, I'll ping the mirror people about it sometime and see if anyone actually cares.
[05:56]  * micahg could use someone to look at bug 961873
[05:56] <ubot2`> Launchpad bug 961873 in blueman "FFe: Update to 1.23" [Undecided,New] https://launchpad.net/bugs/961873
[05:57] <infinity> micahg: What there's actually a feature, other than the appindicator bit?
[05:57] <micahg> I think that was it, there's also the new icon, but I guess that would need a UIFe
[05:58] <infinity> micahg: And is the appindicator support smart enough to go either/or on indicator versus systray, or will I end up with two icons? :P
[05:58] <micahg> hmm, not sure, I suppose I should try that :)
[05:58] <infinity> Yeah.
[05:59] <infinity> Cause I have both an indicator tray and a more classic systray on my xubuntu desktop.
[05:59] <pitti> micahg: responded
[05:59] <infinity> Blueman is currently in the latter.
[05:59] <infinity> Would be annoying to have it in both.
[06:00] <micahg> hmm, I think this might be the only machine on precise with xfce and I don't want to reboot into it, care to test for me :)
[06:00] <micahg> xfce and bluetooth that is
[06:00] <infinity> micahg: Do you have PPA packages somewhere?
[06:01] <infinity> And will I have to log out?  I have a ton of crap open...
[06:01] <micahg> infinity: no, but I have a binary I built locally
[06:01] <micahg> oh, hmm, same boat :)
[06:01] <infinity> I imagine just killing it might do the trick.
[06:01] <micahg> infinity: will an amd64 binary work for you?
[06:02] <infinity>  2117 ?        Sl     0:01 /usr/bin/python /usr/bin/blueman-applet
[06:02] <infinity> micahg: Sure.
[06:02] <infinity> I'm guessing just killing the above will DTRT.
[06:02] <infinity> I hope. :P
[06:02] <infinity> (Well, and potentially re-running it)
[06:02] <infinity> Crap, publisher overlapped again.
[06:03]  * infinity changes his sleep on that image build.
[06:04] <infinity> micahg: Quick like a bunny, I have places to be. ;)
[06:04] <micahg> sorry, figured you wanted a signed changes file :0
[06:05] <infinity> Just scp it to lillypilly, and I'll assume it's from you.
[06:05] <infinity> Cause I'm trusting that way.
[06:07] <micahg> infinity: done
[06:08] <infinity> micahg: Okay.  I have only one icon (and it's the right one).
[06:08] <infinity> micahg: But did this disable non-indicator support for people who don't have an indicator panel?
[06:08] <infinity> micahg: Or does it do smart runtime detection?
[06:09] <micahg> infinity: no idea, haven't dug too deep into it
[06:09] <infinity> micahg: I suppose not a massive concern anyway, since the default Xubuntu profile ships with an indicator panel enabled.
[06:10] <micahg> and I have a patch to disable by default in Lubuntu
[06:10] <infinity> micahg: But it looks good to me, and only gave me one icon, so I'm cool with it.
[06:10] <infinity> Does lubuntu not have an indicator tray/panel?
[06:10] <infinity> Irksome.
[06:10] <micahg> it's too heavy to have on by default
[06:10] <infinity> Really?
[06:10] <infinity> *shrug*
[06:10] <infinity> Alright.
[06:11] <infinity> I thought it was one of the cleaner bits of in-house code we'd done.
[06:11] <infinity> Anyhoo.  It gets my Xubuntu nod of approval.  I have no way to test it on lubuntu without serious effort.
[06:13] <infinity> Speaking of indicator icons and UIFes, though, I really need to do something about update-manager's hideous icons.
[06:13] <infinity> They really don't fit in.  At all.
[06:16] <micahg> ok, I really do need to go to sleep, the only thing left for me for beta 2 now is lightdm-gtk-greeter which I'll finish later today
[06:16] <infinity> micahg: http://lucifer.0c3.net/~adconrad/not_pretty.png <-- I can't be the only person that icon bugs, right? :)
[06:17] <micahg> heh, yeah, doesn't seem to size right
[06:17] <micahg> looks fine for me in Xfce and Unity 2d
[06:17] <micahg> (Xfce machine doesn't hae bluetooth)
[06:17] <infinity> Well, my theme is hardly a default setup.
[09:09] <Laney> hardening-buildflags changes like http://anonscm.debian.org/gitweb/?p=pkg-mono/packages/mono.git;a=commitdiff;h=96d7d4a3a91ab204958ff26b9210328c5db82e19;hp=86127dcf508213eac5b50a65c989cf5971b57378 should be OK without FFe?
[09:31] <jamespage> morning all
[09:32] <jamespage> please could the zentyal-* binary packages be accepted into precise
[09:41] <Riddell> jamespage: please nudge steveK who is listed as the day's contact at https://wiki.kubuntu.org/ArchiveAdministration#Archive_days
[09:41] <Riddell> if he doesn't reply then nudge me and I'll do it
[09:42] <jamespage> Riddell, ack
[09:44]  * jamespage goes to look for StevenK
[10:08] <knome> cjwatson, great, thanks :)
[12:23] <rsalveti> \o/ seems we finally have an image for omap4
[12:24] <rsalveti> not yet synced at cdimages but at least last livecd log is looking good again
[12:26] <rsalveti> I wonder when the image will be available at cdimage, so we can finally test it again
[12:27] <rsalveti> ogra_: you might know :-)
[12:31] <cjwatson> cd builds run immediately after livefs builds
[12:32] <rsalveti> hm, ok, so it might just be waiting other livefs builds then
[12:32] <rsalveti> or just in progress
[12:32] <cjwatson> yes
[12:33] <cjwatson> it waits for all the livefs builds in the batch to complete
[12:41] <rsalveti> great, should be available in a few then :-)
[12:41] <rsalveti> at least I know it worked, happy about that already
[12:41] <rsalveti> guess we didn't have a working image for a few days already
[12:41] <rsalveti> for arm I mean
[13:14] <ogra_> rsalveti, we had omap4 since weeks, what was broken for you ?
[13:14] <rsalveti> ogra_: the image was broken for a few days
[13:14] <ogra_> not here
[13:14] <rsalveti> ogra_: the ones at cdimages are just a copy from the last working image
[13:15] <ogra_> some builds were broken due to nautiluzs-empathy and some due to gnome-games, but generally they worked
[13:15] <rsalveti> that's why once I download the one from 17/18 the others matched the md5 perfectly
[13:15] <ogra_> we definitely had a good bunch of working ones the last 14 days
[13:15] <ogra_> the md5 summing is broken since over a month now
[13:15] <ogra_> dont count on md5 sums
[13:16] <rsalveti> let me check the livecd logs
[13:16]  * ogra_ gets mails for every failed arm build 
[13:16] <ogra_> there were a few but there also were many that didnt break
[13:16] <ogra_> infinity is on the md5sum stuff since a few days
[13:16] <ogra_> should be fine soon
[13:17] <rsalveti> http://people.canonical.com/~ubuntu-archive/livefs-build-logs/precise/ubuntu-omap4/20120319/livecd-20120319-armhf.out is the last working one
[13:18] <ogra_> right, 20th had the games issue, 21 and 22 the nautilus-empathy breakage
[13:18] <rsalveti> yup, that got fixed with clutter
[13:18] <ogra_> the latter ?
[13:18] <ogra_> aha
[13:18] <rsalveti> yep
[13:19] <rsalveti> empathy -> clutter-gst -> clutter
[13:19] <Riddell> need new ones built?
[13:19]  * ogra_ didnt dig into that, i would have done that on monday ..... for the installer sprint i only need headless 
[13:19] <rsalveti> Riddell: the last one worked, just not yet at cdimages
[13:19] <rsalveti> so we should be good
[13:20] <rsalveti> ogra_: I noticed because I wanted to test the desktop image for beta-2
[13:20] <ogra_> thats still a week t go :)
[13:21] <rsalveti> sure, but beta freeze is today I guess
[13:21] <ogra_> should be on monday
[13:21] <ogra_> not sure though
[13:22] <rsalveti> and there are still some annoying issues =\
[13:22] <ogra_> ah, no, its tomorrow
[13:22] <rsalveti> perf is broken, kernel is unstable with 4460, lightdm is incredibly slow
[13:22] <rsalveti> and a few other minor ones
[13:22] <ogra_> well, release is still a month out
[13:23] <ogra_> no worries ;)
[13:23] <rsalveti> :-)
[13:23] <ogra_> i see your xorg fix made it in already ?
[13:24] <ogra_> so you only need sponsoring for the pvr driver ?
[13:24] <rsalveti> ogra_: yup
[13:24] <ogra_> k
[13:24] <Riddell> cjwatson, pitti: you guys onto the release minus 10 and 7 days tasks?
[13:26] <cjwatson> guess I ought to be
[13:26]  * cjwatson will clear out some installer work first though
[13:27] <pitti> I'm constantly monitoring NBS, c-m, and uninstallability, but haven't gotten around the other bits yet TBH
[13:27] <Riddell> I expect skaet will do the various e-mails it needs when she wakes up
[13:28] <cjwatson> the ubiquity warning message is already gone from beta-1; checked that yesterday
[14:05]  * skaet wakes up,  sips coffee and starts on the backscroll ;)
[14:05] <skaet> Riddell,  yup, will start on those messages this morning.
[14:06] <ara> skaet, hello
[14:06] <ara> skaet, cr3 made the needed changes in LP results for the API stgraber was asking for
[14:07] <ara> skaet, the deployment is blocked on RT #51666
[14:07] <ara> in case you want to talk to IS ;-)
[14:07] <skaet> ara,  thanks for flagging.  :)
[14:08] <ara> skaet, I already raised priority, but the more stakeholders, the better, I guess :)
[14:10] <skaet> ara,  yup.  :)
[14:20] <Riddell> kubuntu live images are all under 700MB but alternates are well over, if I can't track that down do we have a way to just remove packages from only alternates?
[14:20] <cjwatson> Depends.  It's easy if they're in the ship seed.
[14:21] <cjwatson> If they're within desktop, not really.
[14:45] <stgraber> can I get an Edubuntu respin, it failed yesterday because of lxc's postinst (fixed now)?
[14:49] <cjwatson> stgraber: running
[14:49] <stgraber> cjwatson: thanks
[14:51]  * skaet went to go start and noticed....
[14:51] <skaet> thanks cjwatson
[15:02] <ogra_> skaet, when do youplan to call out the freeze tomorrow ? rather in your morning or in your evening ?
[15:03]  * skaet gives ogra_ points for a good try to get the freeze moved ;)
[15:03] <ogra_> huh ?
[15:03] <skaet> freeze is at 2100 UTC today.
[15:03] <ogra_> the schedule say 23rd
[15:03] <seb128> ogra_, not it doesn't?
[15:03] <skaet> ogra_,  link please
[15:03] <seb128> ogra_, it says week 23
[15:04] <seb128> it's confusing :p
[15:04] <seb128> 23 march 22nd
[15:04] <seb128> I got bitten by that in the past as well :p
[15:04] <skaet> ogra_,  its been in the weekly agenda, and I post it at the start of each week's meeting too...
[15:05] <seb128> it would probably help if the first column on https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule was in a different color
[15:05] <seb128> it's easy to take the week number as a day as it is now
[15:05] <skaet> seb128,  if I forget please remind me at UDS as one of the improvements for Q...
[15:05] <ogra_> seb128, argh, yeah
[15:05] <seb128> skaet, will do!
[15:06] <seb128> ogra_, hehe, you are not the first one to fall into it ;-)
[15:06] <ogra_> well, instead of adding 23 there make it W23
[15:06] <ogra_> that clearly identifies it as not being a date
[15:06] <seb128> ogra_, but well, freeze have never been on friday, you should have stopped on that ;-)
[15:07] <ogra_> seb128, i was doing the installer vsprint until yesterday and left some bits slip due to well, seeing the freeze on 23rd
[15:08] <ogra_> i'll survive though :)
[15:32] <knome> skaet, i suppose you will be pretty much around until beta2 release?
[15:33] <skaet> knome, myself, pitti, and cjwatson will be focusing on getting it out.   We do need to sleep, eat, etc.  though ;)
[15:34] <knome> skaet, overrated. it's going to take us until 19UTC to get to uploading the bugs filed yesterday. and we might need andother ACK to fix the plymouth theme (all messages show now, but on one line, and not all of it fits in in a small resolution)
[15:35] <skaet> knome,  I'll be around until beta 2 freeze at 2100.
[15:35] <knome> skaet, thanks. i'll get back to you :)
[16:04] <micahg> ScottK: re: cairo-dock-plug-ins> a few things looked like features like:    - Enable GVFS if detected,     + Enabling threads on the Python Interface
[16:05] <ScottK> micahg: OK.  I was relying on the statement that it was a bug fix release.
[16:05] <ScottK> Enabling threads might be a bit sporting.
[16:05] <ScottK> Would you please follow-up in the bug.
[16:05] <micahg> sure
[16:06] <micahg> you want -release resubscribed?
[16:07] <ScottK> Sounds like it would be a good idea.
[16:07] <skaet> pitti, https://bugs.launchpad.net/ubuntu/+bug/959032 - is there even the option to put checkbox-gtk on the disk in a reasonable way for just beta2 or is this clearly not going to be able to happen for this release?
[16:07] <ubot2`> Launchpad bug 959032 in ubuntu "[needs-packaging] Checkbox-app-testing" [Wishlist,New]
[16:07] <pitti> skaet: option yes, but it seems that the checkbox guys didn't really fully make up their mind yet?
[16:07] <pitti> I don't feel I'm able to make a decision which one is better
[16:11] <skaet> ara, ^
[16:12] <skaet> what is the recommendation?
[16:12] <ara> skaet, we have checkbox-qt in the CD and that's the one that should stay there
[16:12] <ara> skaet, from 0.13.5 is ffeature complete
[16:13] <ara> skaet, but this is a different thing, isnt't it?
[16:14] <pitti> it seems it broke the test format, so that Nicholas' tests now ceased to work
[16:14] <pitti> see bug 959032
[16:14] <ubot2`> Launchpad bug 959032 in ubuntu "[needs-packaging] Checkbox-app-testing" [Wishlist,New] https://launchpad.net/bugs/959032
[16:14] <ara> pitti, ah, OK, because we use a mark up language to format the tests
[16:14] <pitti> so it seems we shoudl defer this ^ and get the tests converted?
[16:15] <ara> balloons, how long would it take to convert your tests?
[16:16] <balloons> hey :-)
[16:16] <balloons> I was just asking the team this morning about checkbox-qt.. there was a bug marc was working on that was critical for me also
[16:17] <ara> balloons, which bug?
[16:17] <balloons> on the test conversion, it's nontrivial.. however, I was going to offer to try and do it, assuming the app worked for me now
[16:17] <balloons> https://bugs.launchpad.net/checkbox/+bug/959463
[16:17] <ubot2`> Launchpad bug 959463 in checkbox "Apport should prompt when failing a test during development" [High,Fix released]
[16:18] <balloons> I haven't had success getting the tests to run even under the new format, so it's not been an option honestly
[16:18] <ara> balloons, that bug is now fixed in Precise
[16:20] <balloons> hmm.. I get another error, but maybe it's just me :-(
[16:20] <balloons> regardless, I filed the ffe hoping the cd had space to ship checkbox-gtk as well as I know my package is working and stable as is
[16:21] <ara> balloons, what error do you  get?
[16:21] <balloons> on the apport thing? "Cannot connect to crash database, please check your Internet connection.
[16:21] <balloons> <urlopen error [Errno -2] Name or service not known>"
[16:23] <balloons> I just pulled the version roadmr says is shipping in precise.. The bigger issue than that bug (although it looks better despite failing on my box), is the test format change. And me not have success getting my tests to run even after changing them over
[16:25] <sladen> doesn't look like the wallpapers are going to turn up at this rate
[16:25] <sladen> so those might appear after unfreeze instead
[16:29] <Laney> why is it so late?
[16:33] <sladen> wallpapers.  They always go in last ;-)
[16:33] <Riddell> make sure you get docs team to give the ok on that
[16:35] <brendand> Daviey, hey
[16:40]  * pitti cleans up NBS
[16:45] <Laney> it's not really on
[16:49] <cjwatson> Thoughts on bug 958430?
[16:49] <ubot2`> Launchpad bug 958430 in openssl "[FFe] Please merge openssl 1.0.1 from Debian unstable" [High,Triaged] https://launchpad.net/bugs/958430
[16:52] <cjwatson> (maybe I shouldn't have marked that Triaged)
[16:57] <adam_g> hi all, sorry to spam here for a handout but are there any archive admins around who might be able to help get the nova upload nudged through the queue, or is there anything i can do to help get things moving? the last upload introduced a new binary package (nova-consoleauth) which consists of a script previously packaged in nova-console, plus an upstart job + man page
[17:01] <stgraber> pitti: will we have refreshed langpacks for beta2? (just wondering, couldn't find an upload schedule for these)
[17:01] <ScottK> cjwatson: I agree updating to the new release is better than cherrypicking changes.
[17:01]  * ScottK is inclined to think it's a good idea, but reluctant to get tagged as the guy that said it was OK.
[17:02] <pitti> stgraber: yes, we should; I'll deal with them tomorrow
[17:02] <cjwatson> ScottK: heh, yeah, understood
[17:02] <stgraber> pitti: cool, thanks. Hopefully that'll be the first Edubuntu milestone where everything supports translations (took a while...) :)
[17:02]  * cjwatson attaches build logs and such for form's sake
[17:03]  * ScottK thinks slangasek should approve it.
[17:03] <slangasek> which?
[17:03] <ScottK> openssl FFe
[17:03] <slangasek> openssl?
[17:03] <ScottK> Yes
[17:03] <Riddell> adam_g: steveK is on duty today have you pinged him?
[17:03] <slangasek> yeah, I can look at that one
[17:03] <ScottK> Excellent.
[17:05] <micahg> Riddell: it's the middle of the night for stevenk :)
[17:07] <Riddell> micahg: that's no excuse for shirking off from your duties!
[17:07] <adam_g> Riddell: i haven't, is there somewhere that i can find the schedule of whos on duty / who to bother?
[17:08] <Riddell> adam_g: https://wiki.kubuntu.org/ArchiveAdministration#Archive_days
[17:08] <adam_g> Riddell: thanks!
[17:08] <Laney> I am under the impression that those archive days haven't been happening for some time
[17:08] <Laney> maybe I'm wrong
[17:08] <cjwatson> you're generally correct
[17:10] <cjwatson> just double-checking with the security team about the qrt failure there
[17:10] <Riddell> Laney: I'm back on mine now
[17:15] <jdstrand> Laney: I was off last friday
[17:15] <sladen> Laney: re: ^^ I'm inclined to agree.  But also as predictable as the tides and seasons of the sea
[17:16] <jdstrand> Laney: but people have been tending to focus on specific areas. eg, I typically spend my time on NEW, +1 maintenance works on many of the others
[17:16] <Laney> jdstrand: Riddell: I just thought that it had become more task-driven rather than time-driven.
[17:16] <jdstrand> Laney: it is moving towards that
[17:16] <Laney> sladen: yes. So how can we fix this for next time?
[17:17] <Laney> Reject the UIFe? ;-)
[17:17] <cjwatson> adam_g: looking
[17:18] <cjwatson> adam_g: This breaks upgrades.  It needs Breaks: nova-console (<< 2012.1~rc1-0ubuntu1) and Replaces: nova-console (<< 2012.1~rc1-0ubuntu1)
[17:18] <cjwatson> adam_g: rejecting, sorry.  Please upload a new source package that fixes this
[17:18] <adam_g> cjwatson: 10-4, thanks for the input
[17:19] <Daviey> brendand: hey
[17:19] <cjwatson> adam_g: also, should nova-console have some kind of dependency relationship on nova-consoleauth so that it doesn't vanish on people?
[17:19] <cjwatson> adam_g: or do you have a reason to avoid that?
[17:21] <cjwatson> adam_g: it also seems odd that nova-consoleauth's long description (as opposed to the one-line short description) is identical to that of nova-console
[17:22] <cjwatson> adam_g: FWIW, citation for the need for Breaks/Replaces when you move files around: http://www.debian.org/doc/debian-policy/ch-relationships.html#s7.6.1
[17:24] <cjwatson> adam_g: oh, and the nova-console package here still ships /usr/bin/nova-consoleauth - so please remove that and bump the Breaks/Replaces to (<< 2012.1~rc1-0ubuntu2)
[17:25] <adam_g> cjwatson: thanks. the console + consoleauth components were apparently packaged together in error, the latter without any init script or upstart job. ill see about getting a new upload together as this one seems botched
[17:27] <cjwatson> ok - feel free to transfer all this into a bug or whatever if that helps
[17:27] <cjwatson> and also to ask me to review the next upload in the queue so that another admin doesn't need to start from scratch
[17:36] <skaet> cjwatson, there's a new quantum upload in the queue now,  could you take a pass and confirm that the blockers you noticed have been handled?
[17:40] <slangasek> cjwatson: which way should I be reading these openssl speed numbers in the FFe bug?
[17:41] <slangasek> 'k' as a suffix would've suggested to me that larger == better, but you interpret the numbers as saying the new aes code is slower on your machine in 64-bit mode and I don't see that
[17:42] <cjwatson> slangasek: bigger is better.  sorry, I was unclear, it's faster for small block sizes and slower for large block sizes
[17:43] <slangasek> ohh, there it is
[17:43] <slangasek> right, I missed that when eyeballing because there's an extra digit :)
[17:44] <cjwatson> it's only for aes-128, and newer hardware doesn't show the same symptoms, so I'm not regarding it as a big deal, but I wasn't going to edit the data :)
[17:45] <slangasek> yep, exactly
[17:46] <slangasek> cjwatson: ffe appproved
[17:47] <ScottK> You should've made cjwatson approve the upstart one first ...
[17:48] <cjwatson> skaet: yes, this looks better now within the limits of my ability to review at the moment; accepted
[17:48] <skaet> thanks cjwatson. :)
[17:48] <cjwatson> ScottK: hey, I was reviewing server packaging, I'm sure my karma must be adequately stocked
[17:48] <skaet> Daviey, ^
[17:49] <cyphermox> ScottK: updated the FFE for bluez, sorry, this was indeed a little confusing
[17:56] <Daviey> cjwatson: Keep this up, and you should apply for server set upload access :)
[18:03] <cjwatson> ha ha bonk
[18:05]  * cjwatson uploads openssl and crosses fingers
[18:16] <slangasek> ScottK: I was going to ask you to approve the upstart one :P
[18:17]  * ScottK steps away
[18:18] <infinity> rsalveti: All your work yesterday paid off, BTW, we have fresh ARM images.
[18:18] <rsalveti> infinity: great, need to check that
[18:19] <infinity> Now to figure out how I managed to fix md5sums for all the *gz images, but the stupid ac100 bootimg is still wrong.
[18:20]  * infinity is inclined to blame ogra_ for that.
[18:29] <infinity> rsalveti: Oh, I'd almost forgotten the whole point of this exercise (other than fixing things for beta) was to figure out WTF the slideshow wasn't there, wasn't it? :P
[18:29] <rsalveti> infinity: haha, yup, doing that now
[18:29] <infinity> rsalveti: And it's still not.  I guess I get to investigate now.
[18:29] <rsalveti> oh, you validated already
[18:29] <rsalveti> great then
[18:29] <ogra_> did you fix get lost or so ?
[18:29] <infinity> rsalveti: Well, I just checked the build log to see if the package was being installed, and it's not.
[18:30] <ogra_> iirc you fixed that in oneiric and it worked
[18:30] <infinity> ogra_: No, my fallback fix is there, the package literally isn't being installed at all.
[18:30] <ogra_> with some seed magic
[18:30] <ogra_> oh
[18:30] <ogra_> weird, since it worked fine in oneiric, i remember seeing the slideshow after your fix
[18:31] <infinity> ogra_: Yeah.  The slideshow is still in the ubuntu-live task.  But not being installed.  I'm a bit puzzled, but looking.
[18:32] <infinity> Oh.
[18:32] <infinity> That looks suspiciously like my code.
[18:32] <infinity> if [ "$PREINSTALLED" != "true" ]; then
[18:32] <infinity>         add_task live "$LIVE_TASK"
[18:32] <infinity> fi
[18:32] <infinity> When did I do that, he asks bzr blame...
[18:33] <ogra_> != true ?
[18:33] <ubot2`> Factoid 'true ?' not found
[18:33] <infinity> Yeah, totally my fault.
[18:34] <infinity> I dropped LIVE_TASK (for good reason), but completely forgot the slideshow was coming from there.
[18:34] <ogra_> ah
[18:34]  * infinity fiddles.
[18:34] <ogra_> oh, i remember
[18:34] <ogra_> the kde bits etc
[18:34] <infinity> Well, lots of bits.
[18:34] <ogra_> right
[18:35] <ogra_> but that explains why it worked in oeniric
[18:35] <infinity> oem-config doesn't remove the desktop/live delta the way ubiquity does, so it left cruft.
[18:35] <infinity> Anyhow.  rsalveti was right, adding the slideshow manually is the way to go for now (though he got the package name wrong, that's all)
[18:39] <ogra_> effectively we should look into oem-config and fix it there though
[18:40] <infinity> ogra_: Fix what?
[18:40] <ogra_> the handling of the live task
[18:40] <ogra_> something for Q though
[18:40] <infinity> ogra_: That would mean shipping manifests on the filesystem.
[18:41] <ogra_> we shouldnt need workarounds but have a switch to make oem-config use the same routine
[18:41] <infinity> ogra_: And oem-config really isn't meant to do any of this. :P
[18:41] <ogra_> same goes for things like apt-setup (and i'm sure there are more)
[18:42] <ogra_> oem-config supresses a good bunch of ubiquity bits we should make switchable imho
[18:43] <infinity> We mostly just provide preinstalled images as fun tech preview toys anyway, until that changes, I'm not sure how much more effort I want to put into making oem-config an installer (when it's really not).
[18:43] <ogra_> well, then we should probably switch back to live images :)
[18:44] <infinity> At some point, we should.
[18:44] <ogra_> with the known drawbacks indeed
[18:44] <infinity> But probably not while 99% of our developer base is using glorified cell phones as their hardware platform.
[18:45] <ogra_> heh, yeah
[19:02] <infinity> rsalveti: I'll spin another set of images once that livecd-rootfs is built.
[19:03] <rsalveti> infinity: great, thanks
[19:22] <stgraber> can someone from -release review bug 950157?
[19:22] <ubot2`> Launchpad bug 950157 in ldm-ubuntu-themes "[UIFe] Lubuntu LDM Theme" [Low,Confirmed] https://launchpad.net/bugs/950157
[19:22] <stgraber> it's been approved by gilir already
[19:27] <knome> skaet, just a heads up, we're still working for another patch to fix the problems in bug #961546
[19:27] <ubot2`> Launchpad bug 961546 in xubuntu-artwork "Xubuntu Plymouth theme shows cut messages" [Undecided,Fix released] https://launchpad.net/bugs/961546
[19:28] <skaet> knome,  gotcha
[19:28] <knome> and, still waiting for mr_pouit to get home and upload a few other ack'd Fe's ;)
[19:29] <kees> skaet: I've got a (hopefully) quick FFe for the release team: bug 962431
[19:29] <ubot2`> Launchpad bug 962431 in manpages "[FFe] update to manpages 3.35" [Undecided,Confirmed] https://launchpad.net/bugs/962431
[19:30] <stgraber> kees: didn't two release team members already approve it? :)
[19:31] <kees> stgraber: oh! I didn't reload! hah.
[19:31] <pitti> heh, ScottK and I raced :)
[19:31] <pitti> hey kees
[19:31] <kees> sweet! hi pitti!
[19:31] <kees> okay, uploading. :)
[19:31] <kees> ta-da.
[19:32] <skaet> kees,  looks like there was a collision between ScottK and Martin before I got to it.
[19:32] <kees> yay, now "man 7 capabilities" will list CAP_SYSLOG :)
[19:32] <skaet> pitti,  isn't approved state -> Triaged?
[19:32] <pitti> "confirmed" usually
[19:32] <kees> skaet: yeah, thanks! ScottK and pitti were all over it before I even noticed :)
[19:33] <skaet> kees,  :)
[19:33] <pitti> but the state is not always unanimous, it usually takes a check through the comments to be 100% sure
[19:33] <pitti> i. e. for "fix committed", when it's fixed upstream, but not yet in the distro, and needs an exception
[19:34] <skaet> hmm... we need to update some docs then..   What I'm seeing is:
[19:34] <skaet> https://wiki.ubuntu.com/FreezeExceptionProcess
[19:34] <skaet> Once the Feature Freeze Exception has been ACK'd by a member of the Release Team, the status will be changed to TRIAGED. You can then either upload the package (in case you're in motu or ubuntu-core-dev), or follow the SponsorshipProcess. Please close the bug from the upload, where possible.
[19:35] <pitti> skaet: oh, right
[19:35] <pitti> ok, I'll update my mental model accordingly, sorry
[19:35] <skaet> :)  thanks pitti
[19:36] <kees> whoops, I didn't close the bug with the upload. I'll handle that manually.
[19:37] <stgraber> highvoltage, gilir: new ldm-ubuntu-themes uploaded. It'll need to wait for an archive admin to process the new binary package though
[19:42] <highvoltage> stgraber: great, alkis will be pleased
[19:44] <micahg> pitti: I don't have time to do what I wanted with lightdm-gtk-greeter, so I'm going to upload the version that mr_pouit made as soon as I run some final checks on it
[19:54] <cyphermox> ScottK: sorry for the trouble.
[19:57] <micahg> umm, do I need an FFe for lightdm-gtk-greeter before I upload since it's already in the archive, just a new source?
[19:59] <infinity> micahg: I'm not sure I understood the question.
[19:59] <slangasek> micahg: if it's just the package splitting, then no
[20:00] <infinity> micahg: You need an FFe if it has new features.
[20:00] <slangasek> infinity: lightdm dropped the greeter, !ubuntu flavors still depend on it
[20:00] <micahg> well, new binaries need an FFe, was wondering if a new source technically did as well :)
[20:00] <slangasek> (and are meant to do so - which means the source needs reintroduced)
[20:00] <infinity> (A package split is a new feature, in that you could do it wrong WRT to dependencies and transition and such)
[20:00] <slangasek> it's only a new source package, not a new binary package; I don't see any new feature here per se
[20:01] <infinity> But if it's just reintroducing a binary that was previously dropped, I see no reason for the FFe.
[20:01] <infinity> Yeah.
[20:01] <micahg> this is just for technical reasons, I know I have the ok to upload, just wanted all the i's dotted and t's crossed :)
[20:01] <infinity> micahg: More importantly, freeze is in an hour, upload fast.
[20:01] <micahg> heh, here it goes
[20:01] <infinity> Get out and push, if you have to.
[20:01] <infinity> MASSAGE THE PHONE LINE.
[20:02] <slangasek> wat
[20:02] <infinity> slangasek: Helps squeeze the bits through.
[20:02] <slangasek> how about acupuncture
[20:02]  * infinity wonders if he's been doing it wrong all these years.
[20:03] <infinity> I also lubricate the wall jacks.
[20:03] <infinity> Just in case.
[20:06]  * skaet thinks acupuncture could be counter productive in this case ;)
[20:07] <infinity> Yeah, the bits will spill out.
[20:07] <infinity> You'll have upload all over the floor.
[20:07] <infinity> Bad scene.
[20:08] <skaet> lol
[20:13] <infinity> micahg: Does this need to be in main for anyone, or is universe fine?
[20:14] <knome> skaet, #961546 has a new patch, can you ACK?
[20:14] <micahg> infinity: I think universe is fine as that's where the current binary is
[20:15]  * infinity grabs the source for a cursory review.
[20:16] <brendand> Daviey - hey. sorry for the well late pingback. i was trying to gather logs for bug 906311 but apport-collect seems to be failing when i run it
[20:16] <ubot2`> Launchpad bug 906311 in openquake "jredis error on gemsun03" [High,Fix committed] https://launchpad.net/bugs/906311
[20:16] <brendand> err bug 960311
[20:16] <ubot2`> Launchpad bug 960311 in linux "Networking on Dell PowerEdge R300 with Broadcom Corporation NetXtreme BCM5722 Gigabit Ethernet PCI Express is not functional" [High,Incomplete] https://launchpad.net/bugs/960311
[20:16] <brendand> Daviey, but it's not because the network isn't working :)
[20:17] <infinity> micahg: I know it's not a widely-used thing, but shouldn't "Recommends: lightdm" be "Enhances: lightdm"? :P
[20:17] <infinity> micahg: Also, if the postinst calls binaries provided by lightdm, that's just a hard depend.
[20:18] <skaet> knome,  done.  it was showing fixed release,  have changed it back to in progress..
[20:18] <smoser> hey, can i get a SRU team member to help please?
[20:18] <micahg> infinity: looking
[20:18] <smoser> https://launchpad.net/ubuntu/oneiric/+queue?queue_state=1&queue_text=cloud-init
[20:18] <smoser> oops
[20:18] <knome> thanks, we will upload ASAP
[20:18] <smoser> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/948461
[20:18] <ubot2`> Launchpad bug 948461 in apt "apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly" [High,Confirmed]
[20:18] <pitti> skaet: FWIW, not really happy about bug 961606, but it's a sabdfl thing; and we now have a compromise of only adding a tiny installer shim instead of landscape itself, so the impact is as small as we can make it
[20:18] <ubot2`> Launchpad bug 961606 in ubuntu-meta "[FFE] landscape-client-ui-install package needs to be installed by default on desktop release" [High,Triaged] https://launchpad.net/bugs/961606
[20:18] <smoser> that needs archive -proposed approval, and every day we don't get it is one day we have to delay the cutting over to S3 mirrors in EC2.
[20:18] <infinity> micahg: Well, the postinst guards the /usr/lib/lightdm/lightdm-set-defaults call in a -x, but I'd consider that a bit of a bug/misfeature, since it means that package installation order will change if the greeter is enabled.
[20:19] <infinity> micahg: non-deterministic installation results don't seem like a good idea.
[20:19] <pitti> skaet: doing the changes now, the package-to-be-uploaded is good enough now (i18n etc.)
[20:19] <micahg> infinity: right, well, I think it was a recommends rather than a depends so as not to create circular dependencies
[20:20] <micahg> enhances is a good idea though, I can add that
[20:20] <infinity> micahg: (ie: without a hard dependency, the greeter could installed before lightdm, the postinst won't fire set-defaults, and it's delivered stillborn)
[20:20] <infinity> micahg: Where would the circular dep be, if lightdm doesn't depend on it?
[20:20] <pitti> skaet: for coordination, do you handle the freeze announcement and pinging IS to freeze?
[20:20] <pitti> skaet: (I'm going to crash soon, long 'nuff day)_
[20:20] <skaet> pitti,  understood (not happy, but no good options)  thanks for minimizing impact.
[20:21] <infinity> micahg: Nevermind Enhances.  That made more sense before I looked at what it does.  It really should be a dependency in this case.
[20:21] <skaet> pitti,  yeah,  I'll put the checklist up on the pad, with what I've done,  and let you double check a few other things.
[20:21] <infinity> micahg: Or your postinst is non-deterministic.
[20:21] <micahg> infinity: oh, doesn't exist anymore since lightdm only recommends the greeter, I can make that a hard dependency I guess
[20:21] <skaet> I'll handle the email, LOSA ping, etc.
[20:21] <micahg> infinity: wanna reject and I'll fix?
[20:22] <skaet> some folk that I need to double check some things with are offline, so when you get up.
[20:22] <infinity> Hrm.  I wonder if unity-greeter has this same postinst issue.
[20:22] <micahg> infinity: do you think it should still set-defaults command should still be guarded?
[20:22] <infinity> micahg: No need to guard it if there's a hard dep there.
[20:22] <micahg> infinity: yes, I think it was C/P from whoever had it first :)
[20:22] <infinity> micahg: The one in postrm still needs to be guarded, though.
[20:24]  * infinity considers this a miracle that it works at all.
[20:25] <infinity> Or maybe it only "works" because most systems don't have both installed, and lightdm DTRT with only one installed?
[20:26] <micahg> well, once lightdm is installed, it'll work fine
[20:28] <micahg> infinity: ok, ready with another upload if you like
[20:28] <knome> skaet, the fix for bug #961546 will be in the next 15-20 minutes :]
[20:28] <ubot2`> Launchpad bug 961546 in xubuntu-artwork "Xubuntu Plymouth theme shows cut messages" [Undecided,In progress] https://launchpad.net/bugs/961546
[20:29] <knome> *will be uploaded
[20:30] <zul> can someone reject the last nova uploaded i just did
[20:31] <brendand> Daviey, so sorry. lost my connection
[20:32]  * skaet watches knome to see him skate right up to the wire.... ;)
[20:33] <stgraber> zul: the archive isn't frozzen yet, so if you uploaded something, it's too late (unless it gets into binary NEW)
[20:33] <smoser> SpamapS, pitti slangasek ... if someone could look at approving -proposed for https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/948461 i would really appreciate it.
[20:33] <ubot2`> Launchpad bug 948461 in apt "apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly" [High,Confirmed]
[20:36] <SpamapS> smoser: sorry juju has preempted you for 3 days now. :-P
[20:37] <knome> skaet, that's not even close! you should see me in action ;)
[20:37] <micahg> so, I've got an ubuntustudio package which added a new wallpaper, but the only proof of licensing is an e-mail, do we need a copy of the e-mail in the copyright file or is just the license itself being documented sufficient?
[20:38] <SpamapS> incoming FFE https://bugs.launchpad.net/ubuntu/+source/juju/+bug/962507
[20:38] <ubot2`> Launchpad bug 962507 in juju "[FFE] Latest juju snapshot enables maas provider" [Undecided,New]
[20:44] <SpamapS> Daviey: awake?
[20:44] <Daviey> SpamapS: always baby
[20:44] <SpamapS> Daviey: ^^ FFE for juju+maas
[20:45] <ScottK> pitti: Thanks to LP growing the ability to automatically make bugs confirmed, it wasn't very useful as a state to represent 'approved' anymore.
[20:46] <pitti> ScottK: right
[20:46] <pitti> somehow I seem to have forgotten/missed the policy of setting them to "triaged" now
[20:46] <Daviey> SpamapS: Great.. will review that in a few moments....
[20:46] <slangasek> smoser: I don't see bug #948461 mentioned in the changelog of the cloud-init uploaded to lucid-proposed, and the changelog also clobbers the previously-uploaded 0.5.10-0ubuntu1.6 which is still in -proposed
[20:46] <ubot2`> Launchpad bug 948461 in apt "apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly" [High,Confirmed] https://launchpad.net/bugs/948461
[20:48] <smoser> slangasek, the second part of that is by design.
[20:48] <smoser> the first part... let me check.
[20:49] <smoser> the bug number is wrong, slangasek in the changelog.
[20:49] <smoser> :-(
[20:49] <smoser> it was in the precise upload and then just copied.
[20:50] <smoser> should i re-upload each ?
[20:50] <slangasek> smoser: deliberate> why is that?  is it because the fix for bug #615545 is unnecessary if you're turning up the S3 mirror?
[20:50] <Daviey> SpamapS:"  merge fix-charm-upgrade "
[20:50] <ubot2`> Launchpad bug 615545 in cloud-init "Instances launched in a VPC cannot access ec2.archive.ubuntu.com" [Undecided,Fix committed] https://launchpad.net/bugs/615545
[20:50] <slangasek> smoser: yeah, we'll want a reupload with the right bug #, sorry
[20:50] <smoser> slangasek, i can do that. no problem.
[20:50] <slangasek> smoser: rejecting the current uploads
[20:50] <smoser> regardin ghte othe rbug.
[20:50] <smoser> amazon has since changed omse things, and the previous fix that was in -proposed no longer actually fixes anything
[20:51] <smoser> so i dropped it.
[20:51] <slangasek> ok
[20:51] <pitti> good night everyone
[20:51] <micahg> anyone see my licensing question about?
[20:51] <micahg> *above
[20:51] <slangasek> night, pitti!
[20:51] <SpamapS> Daviey: https://code.launchpad.net/~fwereade/juju/fix-charm-upgrade
[20:51] <Daviey> micahg: You might get better answers tomorrow TBH
[20:51] <slangasek> micahg: license itself being documented should be sufficient
[20:52] <slangasek> micahg: I generally don't bother with attaching emails unless there's *conflicting* licensing information in the upstream tarball
[20:52] <micahg> ok ,thanks
[20:53] <micahg> Daviey: tomorrow doesn't help me upload before the freeze :)
[20:53] <Daviey> SpamapS: can you confirm if bootstrap still pulls from lp:juju?
[20:54] <SpamapS> Daviey: bootstrap has never pulled from lp:juju unless you say 'juju-branch: lp:juju'
[20:54] <Daviey> SpamapS: hmm, i thought it was a default behaviour whilst things were being stagged.
[20:54] <Daviey> Is that not the case?
[20:54] <skaet> good night pitti,  sleep well.
[20:55] <Daviey> SpamapS: please upload
[20:55] <infinity> skaet: When are you disabling the crontab?
[20:55] <skaet> infinity,  we'll leave it going tonight unless you have a compelling reason otherwise.
[20:55] <skaet> decide on it tomorrow.
[20:56] <infinity> skaet: Nope, I'm just not going to do a manual arm test-run if cron will do it for me overnight.
[20:56] <skaet> infinity,  exactly.
[20:56] <smoser> slangasek, thank you for looking. will upload shortly.
[20:57] <SpamapS> Daviey: have to add one more commit, the test suite was broken
[20:58] <infinity> micahg: So, yeah, I suspect the only reason the ubiquity-greeter postinst works as intended (and the gtk-greeter one used to) is because they were probably both installed in the same run, so unpack;unpack;configure;configure.  If that weren't the case, things wouldn't end so well.
[20:58] <infinity> micahg: Err, unity-greeter, I mean.
[20:58] <infinity> micahg: I think I'll file a bug on unity-greeter pointing this out.
[21:00] <Daviey> SpamapS: ok
[21:00] <SpamapS> Daviey: test build is running
[21:00] <infinity> micahg: Though, this seems to be standard practice for all of lightdm-*-greeter.  Silly.
[21:00] <micahg> infinity: like I said copy/paste error
[21:00] <micahg> skaet: I need another minute or two for the ubuntustudio-meta
[21:00] <infinity> micahg: Yeah.  I wonder where it started before it cascaded.
[21:02] <skaet> micahg,  I've put the request in now,  will have to get manually escorted through now I'm afraid.
[21:02] <micahg> that's fine :)
[21:03] <jdstrand> skaet: so, I am building and testing an apparmor package that is needed for LXC beta-2. I apologize for the tardiness. it has been verified upstream and I just need to build and do the distro readiness tests. it should be within the hour
[21:04] <infinity> jdstrand: This will go on your permanent record.
[21:04] <jdstrand> heh
[21:05] <skaet> stgraber,  can you turn on the bot?
[21:07] <stgraber> skaet: you were saying? :)
[21:07] <skaet> thanks stgraber :)
[21:08] <skaet> jdstrand, ack.  will keep eye out.
[21:08] <skaet> builds will be starting at the normal cron job times, so bits landing before then will be picked up.
[21:09] <phillw> skaet: will tomorrows builds have the finals of the Ubiquity sprint?
[21:10] <slangasek> phillw: today's do already
[21:10] <skaet> phillw,  yes
[21:10] <skaet> :)
[21:10] <skaet> what slangasek says....  :)
[21:11] <phillw> slangasek: hmm, http://pad.ubuntu.com/ubuntu-installer-sprint does not have a listing of which ones were closed for today?
[21:11] <slangasek> phillw: ah, nobody closed out the pad; let me see what I can do about that
[21:11] <phillw> thanks :)
[21:11] <smoser> slangasek, 4 new uploads.
[21:11] <smoser> thank you for reviewing.
[21:12] <stgraber> phillw: https://launchpad.net/ubuntu/+source/ubiquity/+changelog
[21:12] <SpamapS> Daviey: looks like the test suite doesn't pass on build.. will have to push past freeze. :-P
[21:12] <stgraber> phillw: 2.9.32 + 2.9.33 is what we had in today's dailies
[21:12] <stgraber> phillw: 2.10.0 will be in tomorrow's
[21:12] <Daviey> SpamapS: it's a bug fix, right?
[21:13] <phillw> stgraber: thanks.
[21:15] <slangasek> phillw: documented the upload on the pad now
[21:15] <adam_g> cjwatson: i imagine its past your EOD but theres a new nova in the queue whenever you get a moment..
[21:16] <ScottK> I guess that answers my question if I uploaded in time.
[21:16] <phillw> thanks
[21:17] <infinity> ScottK: We'll pretend you did.
[21:17] <ScottK> It's a pretty trivial change.
[21:18] <ScottK> Thanks.
[21:29] <SpamapS> Daviey: sorry, internet cut out on me
[21:30] <SpamapS> Daviey: yes bugs need to be fixed in the test suite
[21:31] <Daviey> SpamapS: okay, thanks for raising them.  I imagine bugs from hereon tracking issues would be great :)
[21:32] <SpamapS> Daviey: indeed
[21:56] <Daviey> Please can maas-enlist and cobbler be accepted.  They are both simple changes.
[21:56] <Daviey> .. and wanted on the iso tomorrow.
[21:57] <slangasek> smoser: out of curiosity, why can cloud-init's maintainer script not call "cloud-init-cfg apt-pipelining once-per-instance" in the case where /var/lib/cloud/data/cache/obj.pkl doesn't exist?
[21:58] <slangasek> smoser: also, it's better form to have a package version check, so that if the user deletes /etc/apt/apt.conf.d/90cloud-init-pipelining locally, a package upgrade doesn't re-add it
[22:00] <slangasek> -db_input high maas-enlist/warning-note || true
[22:00] <slangasek> -db_go
[22:00] <slangasek> +#db_input high maas-enlist/warning-note || true
[22:00] <slangasek> +#db_go
[22:00] <slangasek> Daviey: ^^ surely those lines should have been deleted instead?
[22:00] <slangasek> (maas-enlist)
[22:00] <Daviey> slangasek: They will be reintroduced before release.
[22:01] <slangasek> hmm
[22:03] <slangasek> Daviey: well, not pertinent to the current upload, so approved - but it's generally bad form to use debconf 'note' types
[22:03] <slangasek> (i.e., they've been considered deprecated for 5 years or so)
[22:03] <Daviey> slangasek: really?  I didn't know that...
[22:04] <Daviey> slangasek: do you know that the reboot warning at the end of the installer is of type note?
[22:04] <Daviey> slangasek: What was it superseeded with?
[22:04] <slangasek> yes; maybe there are exceptions for the installer, which cjwatson could speak to, but in general you're not supposed to flash pages of text at the user unless you're actually giving them choices
[22:04] <slangasek> *or* if there's an error condition
[22:05] <slangasek> Daviey: type: error :)
[22:06] <Daviey> slangasek: I knew it was not liked, by merrit of http://lintian.debian.org/tags/possible-debconf-note-abuse.html .. but i didn't know it was deprecated
[22:07] <slangasek> the reasoning is that, if what you're doing is unconditionally displaying a message to the user, there's probably a better way to do that
[22:07] <slangasek> without interrupting the flow of installation
[22:08] <Daviey> slangasek: Okay.. i agree with deb maintainer scripts.. but i'd not heard of that in udeb's.. learn every day.
[22:09] <slangasek> as I said, perhaps exceptions are made for the installer
[22:10] <Daviey> slangasek: For general packages, where did you read they were deprecated ? http://manpages.ubuntu.com/manpages/precise/man7/debconf-devel.7.html .. suggests they are still OK if it's an urgent matter
[22:13] <slangasek> Daviey: the manpage words it much less strongly than joeyh did on the mailing list at the time 'error' was introduced :)
[22:13] <Daviey> slangasek: ah!
[22:16] <slangasek> Daviey: cobbler> no one's going to be annoyed by you changing this? :)
[22:16] <slangasek> (accepted)
[22:22] <Daviey> slangasek: We've left it until now.. As we are comfortable that it's not the largest part of the thing :)
[22:34] <SpamapS> syncpackage ok for universe unseeded packages?
[22:36] <slangasek> yes
[22:37] <SpamapS> slangasek: danke
[22:37] <SpamapS> or rather
[22:37] <SpamapS> dekojume moc :)
[22:37] <SpamapS> dekujume even ;)
[22:37] <SpamapS> even in czech, I cannot type :-P
[22:38]  * skaet figures SpamapS gets the sentiment across ...  ;)
[22:38] <slangasek> není zač
[22:39] <jdstrand> skaet: a half an hour later than I said, but apparmor is uploaded
[22:43] <skaet> jdstrand,  :)   that seems to be the trend today,  I think all the folks in the US wish they weren't on DST right now... ;)
[22:51] <skaet> jdstrand,  there's a copyright in there that looks a bit suspect, but know we want to get it in the builds tonight.   Could you please double check apparmor-2.7.102/utils/aa-exec tomorrow, and update if appropriate to 2012.
[22:52]  * infinity loves how apt-get dist-upgrade on freeze days brings in so many more upgrades than usual. :P
[22:59] <skaet> infinity, could you look at: xserver-xorg-video-vmware,  fix landed just landed, and bug just opened, so not sure how well integrated it really is.  looks like something that could impact widely though.
[23:06] <infinity> skaet: The changelog looks sane, except that I'm not actually seeing the patch being dropped in the diff...
[23:07] <infinity> Oh, cause the diff is against Debian?  Thanks, Launchpad.
[23:07]  * infinity checks locally.
[23:08] <infinity> Oh, I see.
[23:09] <infinity> It was synced when it shouldn't have been, and this is the cleanup.
[23:10] <jdstrand> skaet: done and fixed
[23:10] <infinity> skaet: Looks reasonable to me.
[23:11] <skaet> thanks jdstrand,  infinity.  :)
[23:11] <infinity> Accepted curl as well.
[23:11]  * skaet --> dinner
[23:12] <Laney> oh, -proposed pre-release works now?
[23:43] <ajmitch> Laney: apparantly it works during pre-release freezes, so yes