[00:46] <jdstrand> infinity: could someone review the FFe in bug #1229449? it isn't needed for beta (it is only on touch), but I'd like to get the FFe handled so I can go through the landings process
[00:46] <jdstrand> infinity: oh, I don't mean that someone to be you specifically
[00:46]  * jdstrand forgot to backspace
[00:46] <infinity> jdstrand: That someone can be me. :P
[00:46] <jdstrand> if anyone wants to look at that ^, that would work for me
[00:47] <infinity> Can I deny it due to poor grammar?
[00:47] <infinity> "This bug is to fixes a deficiency..."
[00:48] <infinity> jdstrand: If this only touches click-apparmor, I'd consider that covered by the general touch FFe anyway.
[00:49] <infinity> jdstrand: But what is this friggin' madness with mucking around in /var/lib/dpkg/info?
[00:50] <jdstrand> infinity: I'm not mucking around in it-- I am copying from it :)
[00:50] <infinity> Tomayto, tomahto.
[00:50] <infinity> The dpkg database should be treated as an opaque thing, not something you accidentally understand the internals of.
[00:50] <JackYu> infinity: could you review the FFe request at bug #1227197? we hope it could be upgraded to the final beta:)
[00:50] <jdstrand> infinity: basically, aa-clickhook -f adds more than a second to boot
[00:51] <jdstrand> infinity: so we don't want to run it unless we have to
[00:51] <jdstrand> infinity: so I wanted it to run only when it needed to. that is when system policy changes, whick I can detect if those files change
[00:51] <infinity> jdstrand: Why not just drop a /var/lib/apparmor/click.upgraded semaphore, and check and delete that?
[00:52] <jdstrand> infinity: that doesn't work because on a read-only image, that file would be created on the server
[00:52] <jdstrand> infinity: but that directory is rw on the ro image
[00:52] <infinity> Oh.  Right.  System image updates.
[00:52] <jdstrand> its a fun problem with a creative solution :)
[00:53] <infinity> jdstrand: Well, FFe granted for the feature, reservations registered about the vomitous implementation. :P
[00:53] <infinity> (And I reserve the right to change the dpkg database format out from under you)
[00:53] <jdstrand> infinity: I agree it is not ideal, but there were some interesting constraints
[00:54] <infinity> jdstrand: I can't help thinking there must be a better way, but I'm also not in a mood to come up with one.  So, meh. :)
[00:55] <jdstrand> I too will be thinking about it
[00:55] <infinity> jdstrand: Wait, if this is only on system image updates, where isn't there some system image post-update.d that things can drop snippets into?
[00:55] <infinity> jdstrand: Seems this might be a general problem looking for a general solution.
[00:55] <infinity> jdstrand: (Much like Android rebuilds its bytecompile cache after major upgrades)
[00:56] <infinity> jdstrand: Maybe this needs a talk with other interested parties like stgraber to sort out a general "we just updated" hook system.
[00:58] <infinity> jdstrand: Dropped the above in the bug as well for posterity.
[00:58] <infinity> Typos and all...
[00:59] <jdstrand> infinity: right, there is a bug for that actually. but that requires a possibly larger FFe and he seems to be busy atm (I asked about it yesterday)
[00:59] <jdstrand> infinity: rather, earlier today
[00:59] <infinity> jdstrand: He's not at work today, AFAIK.
[01:00] <jdstrand> (that's fine, but its been open for awhile-- I'm not criticizing, I'm just saying I need this in place). depending on what he does, I plan to hook into it in some manner, even if I keep this job (that would allow me to get rid of the dpkg stuff)
[01:01] <infinity> jdstrand: Sure, the awful hack works for now, so long as you make note of its awful hackiness and help push something saner through later.
[01:01] <infinity> (The latter bit being important, cause I do hate revisiting 3-year-old "temporary hacks")
[01:02] <infinity> *cough*ddebs*cough*
[01:03] <jdstrand> sure, I'm well aware of the hackiness. I plan to revisit policy load in generall after release
[01:03] <jdstrand> (for apparmor as well as click-apparmor)
[01:05] <jdstrand> infinity: in fact, I intentionally did not close the lxc-android-confing task for click-apparmor so I could revisit this going forward
[01:05]  * infinity nods.
[01:12] <jdstrand> infinity: thank you for the review btw :) have a nice evening
[01:13] <infinity> jdstrand: I'll give it my best.  You too.
[01:13] <jdstrand> heh
[01:14] <JackYu> infinity, hi, are you free to review our FFe request:)?
[01:15] <infinity> JackYu: Has anyone from kylin built this, and tested it locally to be sane and working?
[01:16] <infinity> JackYu: Looks like a pretty major update, but it also only affects your image, so if you guys are happy with it, I'm alright letting it slide in.
[01:16] <JackYu> infinity, yes, we tested it:)
[01:17] <infinity> JackYu: Alright.  Well, upload away, and if it's in the archive in time for another respin, let's let it into your final beta images, otherwise it'll make it into final.
[01:18] <infinity> JackYu: And close the FFe bug in the upload changelog, please.
[01:18] <JackYu> infinity, thanks. happyaron will upload it. a
[01:18] <infinity> happyaron: ^ see above.
[01:18] <happyaron> infinity: ok
[01:19] <JackYu> infinity, would you please unlock this package?
[01:20] <JackYu> infinity, sorry, unblock:)
[01:22] <infinity> JackYu: When it's uploaded and built, I'll unblock it for the next build of your image.
[01:22] <JackYu> infinity, sure, thanks.
[01:27] <happyaron> infinity: do I need to bump the release version, or reuse the version number that is already in -proposed?
[01:28] <infinity> There isn't one in proposed...
[01:28] <infinity> https://launchpad.net/ubuntu/+source/youker-assistant
[01:28] <infinity> ^-- Only 0.1.6-0ubuntu1  there.
[01:29] <happyaron> ah, I meant for ubuntukylin-default-settings, got online just now and was dealing that with JackYu last night...
[01:30] <happyaron> yesterday I was told the package needs to be reworked and uploaded again.
[01:31] <infinity> Oh, I know nothing of what's happening with ubuntukylin-default-settings...
[01:32] <happyaron> so my question could be simplified to that, if a version in -proposed is not accepted by release team and I was asked to uploaded a new one, which version number should I use?
[01:32] <infinity> happyaron: You'd need to bump the version, yes.  Once a package is accepted, the version is used up.
[01:32] <happyaron> reused the old one already in -proposed, or increase it?
[01:32] <infinity> happyaron: Only things we reject from a queue can be reused.
[01:32] <happyaron> I see, thanks.
[01:34] <happyaron> I was once heard from debian-devel list that a package will only be accepted when it build successfully on at least one arch in -propose, get a bit confused.
[01:35] <infinity> Sounds like you were misled. :)
[01:35] <happyaron> :)
[01:35] <infinity> Even in Debian, that's not really true, except for the part where they do binary uploads, so one arch has always succeeded by the time they upload.
[01:36] <happyaron> you mean arch:source?
[01:36] <happyaron> for ubuntu
[01:36]  * happyaron is still confused..
[01:37] <infinity> happyaron: I meant for Debian.  For Ubuntu, all uploads are source-only, yes.
[01:37] <infinity> happyaron: (You mentioned debian-devel...)
[01:37] <happyaron> ok
[01:37] <infinity> happyaron: Anyhow, there could also be confusion about "accepted" versus "propomoted".  Things can't make it from proposed to release without passing certain criteria.
[01:38] <infinity> happyaron: But once it's ACCEPTED into the archive (and proposed counts), it's accepted, the version is used, can't be used again.
[01:38] <happyaron> I see.
[01:39] <happyaron> thanks for the explaination, :)
[06:13] <cjwatson> FYI: all archive jobs on lillypilly disabled, switch to snakefruit in progress
[06:14] <cjwatson> (rsyncing, don't actually try to use snakefruit yet)
[06:15] <JackYu> cjwatson, we have just adjusted the ubuntukylin-default-settings according your comments. happyaron will upload it soon. Hope you will be happy with this version:)
[06:15] <cjwatson> Hope so, thanks :)
[06:26] <infinity> Oh, I wish I'd read that before I respun kylin for the other change I pushed through for them.
[06:26] <infinity> Oh well.  Can spin again. :P
[06:26] <infinity> I need to sleep first.
[06:27] <happyaron> infinity: can you unblock youker-assistant first, if you are still on line...
[06:27] <infinity> happyaron: It's already in saucy, that's what I'm rebuilding for.
[06:27] <happyaron> ok
[06:27] <happyaron> thanks
[06:27] <infinity> https://launchpad.net/ubuntu/+source/youker-assistant/0.2.1-0ubuntu1/+publishinghistory
[06:29] <JackYu> infinity, thanks. I think you should go to sleep:).
[08:01] <ogra_> could some archive admin please let gst-plugins-bad1.0 1.1.4-2ubuntu2 out of binary NEW ? (we urgently need the -hybris package to move forward with phone multimedia)
[08:07] <ogra_> seb is back \o/
[08:08] <xnox> plars: are installer bugs linked on the iso tracker? can start looking through those for obvious things. Let me sync up images and reinstall my spare laptop.
[08:12] <cjwatson> Archive jobs should be mostly back up and running now.
[08:37] <JackYu> cjwatson, we uploaded the new version of ubuntukylin-default-settings, would you review and unblock it?
[09:29] <lool> pushed my first unblock hint; hopefully I dont break anything
[09:29] <ogra_> lool, if you didnt, could you try gstreamer1.0-hybris ?
[09:29] <ogra_> (too)
[09:29] <Laney> that isn't blocked
[09:29] <lool> gtg
[09:29] <cjwatson> lool: looks fine
[09:29] <lool> will look at that when I'm back
[09:30] <lool> Cool
[09:30] <Laney> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#gst-plugins-bad1.0
[09:30] <Laney> ogra_:
[09:30] <lool> bbiab
[09:30] <ogra_> Laney, well, its still in proposed, slangasek told me he would let it through NEW
[09:30] <Laney> "still in proposed" isn't the same as "package is blocked"
[09:30] <Laney> always check excuses
[09:30] <ogra_> Valid Candidate ?
[09:31] <cjwatson> why is upstart-app-launch blocked, anyway?
[09:31] <ogra_> why does it say that if it isnt valid
[09:31] <cjwatson> I don't think it's on images
[09:31] <cjwatson> ogra_: that's only the first pass.  RTFM
[09:31] <cjwatson> the M is linked from the top of the page
[09:31] <ogra_> k
[09:31] <Laney> Anyway, you're not supposed to have that Depends
[09:31] <Laney> please to remove it
[09:31] <ogra_> hmm, i thought ricardo did
[09:32] <cjwatson> and indeed there's nothing gstreamer-related in NEW
[09:32] <cjwatson> so this isn't archive admins getting in your way, it's wrong packaging
[09:33] <ogra_> fixed then ...
[09:33] <ogra_> sorry for the noise
[09:34] <psivaa> cjwatson: infinity: (not so urgent for me but just in case it hasn't been noticed) we dont have i386 images for precise since the 20th in cdimage
[09:34] <Laney> upstart-app-launch is because http://qa.ubuntuwire.org/ubuntu-seeded-packages/seeded.json.gz says it is on edubuntu
[09:34] <cjwatson> psivaa: maybe I shouldn't have commented those out pending saucy beta
[09:34] <Laney> although seeded-in-ubuntu doesn't don't know why that is
[09:34] <cjwatson> psivaa: uncommented, they'll trickle back in as cron jobs fires
[09:34] <cjwatson> *fire
[09:35] <cjwatson> psivaa: (they also got bitten by the i386 livefs buildd being down, but that's fixed now)
[09:35] <psivaa> cjwatson: ack, thanks
[09:36] <Laney> tumbleweed: ^ seeded-in-ubuntu bug?
[09:36] <Laney> I should have put some punctuation after "doesn't"
[10:05] <tumbleweed> Laney: hrm, let's have a look
[10:08] <lool> re
[10:16] <tumbleweed> Laney: it's in the manifest
[10:17] <tumbleweed> hrm, I never added ubuntu-touch
[10:18] <Laney> tumbleweed: it is
[10:18] <Laney> but s-i-u doesn't show it as on edubuntu
[10:18] <Laney> Probably you need to strip off the :arch
[10:19] <tumbleweed> sounds likely
[10:22] <cjwatson> ogra_: You need to fix gstreamer1.0-plugins-bad-dbg too
[10:22] <ogra_> bah crap ... blind me
[10:22] <Laney> my beautiful gstreamer package
[10:52] <smartboyhw> Please unblock ubuntustudio-lightdm-theme from saucy-proposed, Riddell didn't unblock it for us while he did the -default-settings unblock:(
[10:54] <Laney> ok
[10:55] <Laney> smartboyhw: done
[10:56] <Laney> wait, Riddell did do it
[10:56] <Laney> Unblock request by jriddell ignored due to version mismatch: 0.49
[10:56]  * Laney fixes that instead
[10:57] <Laney> smartboyhw: worth checking http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html always
[11:07] <JackYu> cjwatson, do you have time to review the ubuntukylin-default-settings 1.0.8? we need someone unblock it and rebuild our beta 2 iso.
[11:14] <smartboyhw> Laney, OK
[11:14] <smartboyhw> Thanks:)
[11:15] <smartboyhw> JackYu, <cjwatson> BTW, please move away from the model where you have a single preferred contact point - I'm not always around :P
[11:17] <JackYu> smartboyhw, yes. But cjwatson gave some comments on this package, so I ask him to review for respecting him:)
[11:18] <smartboyhw> JackYu, :)
[11:18] <JackYu> Laney, Could you please unblock ubuntukylin-default-settings as well?
[12:20] <psivaa> stgraber: ubuntu upgrade tests have not been added to the iso tracker yet for saucy beta. any idea if/when they will be added
[12:20] <psivaa> ?
[12:34] <tjaalton> join #ubuntu-hardened
[12:34] <tjaalton> uh
[12:37] <mdeslaur> yes, everyone should join! :)
[12:54] <attente> hi, can i request an unblock of indicator-keyboard? this bug was recently fixed: https://bugs.launchpad.net/indicator-keyboard/+bug/1228489
[13:02] <plars> xnox: yes, they are linked on the tracker
[14:23] <doko> cjwatson, do you know why both emacs23 and emacs24 are seeded? can we drop emacs23?
[14:24] <cjwatson> no idea, <-- vim user :-)
[14:26] <Laney> doko: bzr blame shows you who added 24
[14:26] <xnox> doko: i don't think we made 24 the default yet & havent rebuild/ported all the r-deps. So I don't think we can switch to 24 now. Something for t-cycle.
[15:35] <plars> xnox: any ideas on some of those installer bugs?
[16:11] <apw> should we have a saucy-updates milestone already?  it seems we are in the realm that we might want to be pushing things out to after released but i cannot as yet see the milestone
[16:12] <stgraber> sounds reasonable, yes, let me create that one and cleanup the others a bit
[16:12] <cjwatson> apw: added
[16:12] <cjwatson> stgraber: beat you ;-)
[16:12] <cjwatson> stgraber: (only to the addition, feel free to do cleanup ...)
[16:13] <stgraber> cjwatson: haha, just got an error back from LP telling me someone beat me to it :)
[16:14] <Laney> OOPS-TOO-SLOW-OLD-MAN
[16:14] <apw> cjwatson, thanks
[16:15]  * infinity notes that LP lied to him about who could create them.
[16:15] <stgraber> alright, all old milestones are now marked as inactive (only keeping 13.09, 13.10 and saucy-updates), I'll also move the bugs of all old milestones to 13.09
[16:15] <cjwatson> thanks
[16:16] <infinity> Or I'm a moron and can't find how?
[16:16] <infinity> "Milestones belong to a series and can be created from the series page by a project owner or series release manager."
[16:16] <infinity> Pretty sure the latter half is a lie.
[16:16] <stgraber> infinity: launchpad.net/ubuntu/saucy lists them and has an add milestone link there
[16:17] <Laney> I can't see it
[16:17] <infinity> stgraber: Yeah, only for TB.  Point made.
[16:18] <stgraber> and all bugs have been moved
[16:58] <lool> hinted telepathy-mission-control-5/1:5.14.1-1ubuntu6 for a bug fix that Jamie tested
[17:03] <cyphermox> Laney: do I need to do anything special to block NM for now, given the beta freeze?
[17:03] <Laney> it should be blocked already
[17:03] <infinity> cyphermox: It should be blocked automagically.
[17:03] <cyphermox> ack
[17:04] <cyphermox> just making sure
[17:04] <Laney> :wq
[17:04] <Laney> NO
[17:04] <infinity> lool: Can we avoid people outside ~ubuntu-release hinting things that affect all images while we're in the middle of a beta?
[17:04] <cyphermox> you guys used a block-all hint, basically
[17:04] <infinity> cyphermox: Much uglier than block-all. :P
[17:04] <cyphermox> infinity: :)
[17:05] <infinity> cyphermox: But anything seeded on any images should be blocked.
[17:07] <Laney> Speaking of blocks, someone please check my last britney2 commit makes sense
[17:07] <Laney> Setting up the role account
[17:08] <lool> infinity: Sorry
[17:09] <lool> I tried to revert the hint, but too late
[17:09] <cjwatson> lool: seeded-in-ubuntu is your friend
[17:09] <cjwatson> please use it
[17:09] <infinity> Laney: Seems reasonable.
[17:10] <Laney> infinity: k. pushing the hint now.
[17:10] <lool> cjwatson: noted
[17:10] <cjwatson> Laney: yep, looks right
[17:12] <infinity> cjwatson: Speaking of reviews, I note you made no comment on my britney1 commit the other week.  Was it so hideous that you developed temporary amnesia, or were you just siding with me on the pragmatism > elegance front?
[17:13] <cjwatson> the latter
[17:13] <cjwatson> we can nuke it from orbit later
[17:33] <chilicuil> buenos dias o/
[18:11] <plars> infinity: do you know if anyone is looking into the ubiquity issues on desktop beta?
[18:12] <plars> infinity: xnox mentioned them this morning, but haven't heard any news since
[18:13] <infinity> plars: I know less than xnox on that front.  Bug number(s)?
[18:14] <plars> infinity: there are lots, they are linked on http://iso.qa.ubuntu.com/qatracker/milestones/303/builds - note the abundance of black cockroaches under desktop
[18:16] <infinity> plars: Lovely.  I thought we had people testing these things on some sort of cadence. :P
[18:21] <infinity> plars: Okay, so some of these are probably eratta we can ship a beta with (though none of them look like something we'd want to ship final with).
[18:22] <infinity> plars: But chasing down the ugly panels and maybe the partitioning issue would be nice.
[21:19] <tkamppeter> jdstrand, the fixed CUPS package is in -proposed now.
[21:20] <jdstrand> tkamppeter: nice, thanks! :)
[23:33] <JackYu> hi, release team, please unblock the  ubuntukylin-default-setting package. We are waiting it to re-spin our iso:(.
[23:41] <infinity> JackYu: Did this upload address all of cjwatson's concerns from yesterday?
[23:43] <infinity> Certainly looks saner...
[23:44] <cjwatson> Oh, that arrived while I was napping earlier.
[23:45] <cjwatson> Yes, that definitely makes me less unhappy.  I'm not sure I ever got an answer to my question of whether you really intended to drop gnome-tweak-tool and chromium-browser, but I guess that's your problem.