[05:19] <Mirv> hmm. bug #1219695 and the last comments.
[05:19] <Mirv> ie. it seems the Touch multimedia team would like to have a qtmultimedia fork in with different package names.
[05:21] <Mirv> I start to think it's not related to Qt 5.1.1 FFe as such, but it doesn't sound it would automatically fall under the generic touch FFe either at least without further discussing
[05:22] <Mirv> since it's both Qt 5.1.1, but not really (the upstream 5.0.2 version stays in archives). it's touch specific, but it's a fork of upstream sources.
[05:26] <ScottK> Mirv: I'd suggest ask for a new FFe.  You'll need an archive admin to volunteer to New it in any case.
[05:26] <Mirv> ScottK: ok, sounds sensible
[05:26] <ScottK> Mirv: Would you please mark the 5.1.1 FFe tasks invalid.
[05:27] <Mirv> ScottK: ok
[05:28] <Mirv> ScottK: or won't fix, as you did for qtbase and qtdeclarative?
[05:28] <ScottK> Yes.  That's what I meant.  Sorry.
[05:28] <ScottK> Even more sign I should be sleeping now.
[05:35] <Mirv> (done)
=== forestpi1kie is now known as forestpiskie
[07:24] <Noskcaj> Can someone look at bug 1221913 please?
[09:30] <asac> cjwatson: hi
[09:30] <asac> cjwatson: we have a whole desktop lot in our CI staged
[09:30] <asac> cjwatson: i assume it was supposed to land yesterday and just waits there... can you check the === unity ==== stack changes here: http://people.canonical.com/~platform/cu2d/results
[09:30] <asac> and tell me if you want to reject anything of that?
[09:31] <asac> search for ==== unity ====
[09:36] <cjwatson> asac: It doesn't look like anything there breaks UI freeze, with the possible exception of the unity-scope-mediascanner change - but at worst that looks like a reasonable bug-fix and it's only in a single scope
[09:37] <cjwatson> asac: Do you know of any UI changes I've missed?
[09:37] <cjwatson> (I mean, of the kinds that would show up in screenshots)
[09:39] <asac> ok ... i didnt pay much attention to desktop, so i dont have a good understanding, but i will find someone to tell me
[09:39] <asac> dont worry then
[09:45] <cjwatson> I'm OK with the rest of it
[12:40] <knome> this has been bugging me for a few cycles already, so here's the thing: does anybody think there is any reason to prefer the *visual* formatting in https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule over https://wiki.ubuntu.com/PasiLallinaho/ReleaseScheduleReformatting ?
[12:42] <cjwatson> Not a bad idea; the text towards the bottom of the original gets increasingly hard to read.
[12:42] <knome> exactly
[12:43] <cjwatson> The visited-link colour on the darkest red here actually makes my eyes hurt trying to read it.
[12:44] <knome> if there are other thing you think might make it more legible/useful (visually), feel free to point out
[12:44] <knome> *things
[12:52] <cjwatson> I think you should go ahead and make that change, also to TSeries/ReleaseSchedule
[12:52] <cjwatson> In fact wouldn't hurt to change historical schedules as well
[12:52] <cjwatson> You can put r=cjwatson in the commit message if you like
[12:54] <knome> ok, i'll do that
[12:54] <knome> cheers :)
[12:55] <knome> (btw, we have one UIFe coming... bug 1228098, but that's not completely prepared yet)
[12:55] <Mirv> I've helped the multimedia team to craft FFe of a co-installable alternate qtmultimedia version which would bring GStreamer 1.0 support as long as a released upstrea version does not yet have it https://bugs.launchpad.net/ubuntu/+bug/1227987
[12:55] <Mirv> I will however leave it to sergiusens hands now soon for today
[13:03] <knome> cjwatson, done for S and T
[13:03] <cjwatson> thanks
[13:03] <knome> cjwatson, will go through the historical ones when i have extra time
[13:40] <Laney> Mirv: that's more than just GStreamer 1.0 porting, isn't it?
[13:40] <Laney> otherwise why does it mention mir?
[13:44] <Mirv> sergiusens: ^
[13:44] <sergiusens> Laney, let me get jhodapp on here
[13:45] <Laney> no need, you can reply in the bug
[13:46] <jhodapp> sergiusens, here
[13:46] <sergiusens> jhodapp, Laney just said to reply in the bug for the FFe explaining all the changes in QtMultimedia
[13:46] <sergiusens> wrt to the Mir symbols and such
[13:47] <Laney> ScottK: do you have an opinion about this?
[13:47] <jhodapp> sergiusens, so reply to this one? https://bugs.launchpad.net/ubuntu/+bug/1227987
[13:48] <Laney> jhodapp: It's because I think there might be a bit more than just porting to gst 1.0 APIs
[13:48] <jhodapp> Laney, yes there is more, I added a new renderer control
[13:49] <jhodapp> sergiusens, the package is close...I just tested with it and I get audio playback but no video
[13:50] <sergiusens> jhodapp, awesome, let's go back to #phablet
[13:50] <jhodapp> k
[13:58] <jbicha> please remove the binary for gnome-documents/armhf
=== jhodapp is now known as jhodapp|afk
[16:11] <attente> hello, is there anyone i can talk to about this FFe? https://bugs.launchpad.net/unity-greeter/+bug/1228207
=== Ursinha-afk is now known as Ursinha
[18:24] <knome> cjwatson, oneiric, raring and precise are fixed. quantal was okay with no dark red, so i left it as is.
=== Ursinha is now known as Ursinha-afk
=== jhodapp|afk is now known as jhodapp
[18:36] <cjwatson> knome: thanks
[18:37] <knome> cjwatson, unless stgraber gets to it first, we need bug 1228098 ACK'd (we have an uploader today)
[18:40] <stgraber> knome: approved
[18:40] <stgraber> knome: (as your doc team is fine with that and it won't be a problem there)
[18:40] <knome> cheers :)
[18:40] <cjwatson> heh, in-flight collision
[18:40] <cjwatson> do see my comment though
[18:41] <stgraber> well, at least we agreed :)
[18:41] <stgraber> oh, and good point about ubiquity
[18:42] <infinity> *cough*
[18:44] <knome> yeah, we need to look at ubiquity. thanks for catching that...
[19:00] <knome> cjwatson, we need to change the name in ubiquity as well. UIFe still ACK'd? :)
[19:01] <knome> or stgraber, or infinity...
[19:02] <cjwatson> Yes
[19:02] <knome> also, question: are *new* shortcuts (binding media keys) considered under FFe or not?
[19:02] <knome> or, FF
[19:03] <knome> while we update the our default-settings package, would be good to get those in as well. can file a FFe bug if needed.
[19:03] <stgraber> knome: can you give me the new name?
[19:04] <knome> stgraber, just a sec, i'll confirm that
[19:04] <knome> stgraber, xubuntu-wallpaper.png in the same directory as the previous one.
[19:06] <stgraber> knome: so /usr/share/xfce4/backdrops/xubuntu-wallpaper.png, correct?
[19:08] <infinity> jibel: Want to help me navigate jenkins and divine why the nova tests seem to have been failing?
[19:08] <knome> stgraber, correct. :)
[19:10] <infinity> jibel: Oh, nevermind, I think I found it.
[19:15] <stgraber> knome: I pushed the fix to the ubiquity packaging branch. Let me know once the new wallpaper is in the archive and I'll look into uploading ubiquity.
[19:15] <knome> stgraber, thanks, i'll do that
[19:25] <knome> can anybody confirm my question re: shortcuts a while ago?
[19:48] <ochosi> hi everyone, can someone please take a look at this FFe? https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1228356
[19:51] <ochosi> (and ideally ACK it ;))
[19:51] <ochosi> stgraber: knome is afk, but the xubuntu-artwork pkg with the new wallpaper has just been uploaded
[20:04] <stgraber> ochosi: ok
[20:05] <ochosi> stgraber: thanks for updating ubiquity!
[20:05] <ochosi> this will be the last time this has to be changed, pinky-promise
[20:06] <stgraber> cjwatson: so I see you commited the reiserfs change to ubiquity, should I just refresh the builtin source packages or do we need anything else before that's uploadable?
[20:08] <ochosi> stgraber: maybe that's asking too much, but if you have time to look at the FFe i posted above, we'd have an uploader around tonight (and it should be a trivial FFe)
[20:10] <attente> hello, is there anyone i can talk to about this FFe? https://bugs.launchpad.net/unity-greeter/+bug/1228207
[20:12] <ochosi> attente: are you working on unity-greeter? cause i spotted a small bug...
[20:12] <attente> ochosi, not actively, only for the bug i just posted
[20:12] <ochosi> ah ok
[20:30] <ochosi> stgraber: thanks a lot!!
=== jhodapp is now known as jhodapp|afk