[01:55] <MajorWedgie> Hi guys quick question then I'll bother you no more.
[01:55] <MajorWedgie> Is Unity free, as in could competing distros use it as their desktop?
[02:02] <MajorWedgie> It's OK I think I sorted it. Thank-you.
[04:20] <Mirv> was there any work/branch yet on bug #1181717 ? (not seeing, just checking) reportedly hurts working on saucy.
[09:39] <nic-doffay> Saviq, getting some new output which I'm not sure the cause of on ./run
[09:39] <nic-doffay> file:///usr/lib/i386-linux-gnu/qt5/qml/Ubuntu/Components/Button.qml:95: Unable to assign [undefined] to QString
[09:39] <nic-doffay> Are you aware of what might be causing this?
[11:29] <veebers> sil2100, didrocks: ping?
[11:30] <didrocks> veebers: pong
[11:30] <veebers> didrocks: Hi, looks like I introduced a couple of 'small' errors in my recent Autopilot update :-\
[11:31] <veebers> didrocks: if I put up a MP could you eyeball it and Ok it please?
[11:31] <didrocks> veebers: argh, you need regressions tests it seems :)
[11:31] <didrocks> veebers: thomi would review it?
[11:31] <veebers> didrocks: it appears the tests that I ran weren't exhastive enough
[11:31] <veebers> didrocks: normally, but that  would have to wait until our morning as I'm sure he's AFK for the night
[11:31] <didrocks> veebers: yeah, better to wait, but first thing tomorrow first
[11:32] <didrocks> for him and you please :)
[11:32] <didrocks> veebers: so that it's picked by daily release
[11:33] <veebers> didrocks: sure thing. Again, sorry :-P
[11:33] <didrocks> no worry, but please have regression tests! :)
[11:33] <sil2100> veebers: pong!
[11:33] <sil2100> veebers: sorry, I'm theoretically on holiday today ;)
[11:34] <veebers> sil2100: oh sorry to bother, I was going to bug you to Ok a MP but didrocks thought that it should wait for thomi :-)
[11:34] <sil2100> veebers: just poke me with a review if you have one, or send me an e-mail and I'll take a look
[11:34] <veebers> sil2100: coolio
[11:35] <sil2100> veebers: it would be generally good if thomi would also review it, as he is the one with much more experience, but no problem for me to take a look ;) Thanks!
[11:45] <didrocks> Trevinho: hey, not the issue I meant the other day, but related on "the marker doesn't do the right thing": http://people.canonical.com/~didrocks/tmp/marquer_in_air.png
[11:46] <Trevinho> didrocks: mh.. are you using daily?
[11:47] <didrocks> Trevinho: no, the version in saucy, which isn't the latest one
[11:47] <didrocks> I saw it in raring too
[11:47] <Trevinho> didrocks: I've made a change just after the raring release that should fix it, but i don't know if it made into saucy yet
[11:48] <didrocks> Trevinho: ah ok, probably not
[11:48] <seb128> we didn't have any landing in saucy yet :/
[11:48] <Trevinho> seb128: not sure, I didn't check.. but we neither have a sru for raring..
[11:48] <didrocks> yeah, thanks to the interleaving of autopilot 1.3
[11:49] <seb128> Trevinho, the SRU is in the queue, infinity said he would review it tomorrow
[11:49] <seb128> Trevinho, btw did the libreoffice menu background issue got fixed in the stable serie?
[11:50] <Trevinho> seb128: 7.0 autolander is not merging...
[11:50] <Trevinho> still
[11:51] <seb128> why not?
[11:51] <Trevinho> still same error:
[11:51] <Trevinho>  /tmp/buildd/unity-7.0.0daily13.05.08~13.04bzr3322pkg0raring16/UnityCore/MusicPreview.cpp:70:66: error: 'unity_protocol_music_preview_play_uri' was not declared in this scope
[11:51] <Trevinho> for all the 7.0 branches, and it's not caused by unity..
[11:51] <seb128> hum?
[11:51] <Trevinho> I think that libunity in 7.0 is messed
[11:52] <Trevinho> but I don't know exactly against what is building
[11:52] <seb128> shrug
[11:52] <seb128> they merged the new scope work without branching
[11:52] <Trevinho> it uses libunity-dev_6.90.2daily13.05.01.1ubuntu.unity.nextbzr224pkg0raring3_amd64.deb
[11:53] <Trevinho> yes, that's the problem I guess
[11:53] <seb128> didrocks, ^ who is in charge of that? sil2100?
[11:53] <didrocks> seb128: yep, sil2100
[11:53] <seb128> sil2100, ^
[11:54]  * Trevinho really would have preferred better communication when the 100 scopes landed...
[11:54] <didrocks> Trevinho: thosrt and pstolowski didn't tell you?
[11:54] <didrocks> come on guys :/
[11:55] <sil2100> Looking
[11:55] <Trevinho> I wasn't aware like most of us
[11:56] <didrocks> Trevinho: I thought bregma and thorst as some communication meeting?
[11:56] <didrocks> if not, seems that it's something they should set up
[11:57] <sil2100> Ok, my fault as well, could have noticed that there's no 'raring' branch for libunity ;/
[11:57] <sil2100> Shit
[11:57] <Trevinho> sil2100: sorry, we were discussiong about this also few days ago, but probably we didn't made our voice to get you...
[11:58] <sil2100> Trevinho: I think we need to prepare a 7.0 branch now actually
[11:58] <didrocks> sil2100: hum, so the stack configuration was done, but not that?
[12:02] <sil2100> didrocks: actually, I see there's libunity/raring
[12:02] <sil2100> So it should be ok
[12:02] <didrocks> I wonder if it's not just the local upstream repo for the upstream merger which is screwed
[12:02] <didrocks> mmrazik: you do separate the repos depending on stack, right?
[12:02] <didrocks> or just depending on releases?
[12:02] <sil2100> Probably, since it's all ok in the config
[12:03] <didrocks> I guess everything is melt in the local package repo for upstream merger
[12:03] <didrocks> Trevinho: you should track with them, I just the ppas, they are good, so it's not at our level ^
[12:04] <Trevinho> didrocks: so are the local 7.0 branches messed?
[12:04] <didrocks> Trevinho: not the branch, nor the ppa, but I guess the upstream merger melt the local repo for merging things
[12:05] <didrocks> which is in the PS QA's team hand
[12:05] <Trevinho> ah
[12:05] <didrocks> seb128: FYI ^
[12:05] <veebers> sil2100: I have this (but if you could hang off OK-ing it for the moment please: https://code.launchpad.net/~veebers/autopilot/fix_cleanup_errors_1185790/+merge/166494
[12:05] <seb128> didrocks, k, thanks
[12:05] <sil2100> Does anyone know how to disable line-wrapping in thunderbird?
[12:06] <sil2100> Since even with mail.wrap_long_lines it's still wrapping lines ;/
[12:08] <sil2100> Ah
[12:08] <mmrazik> didrocks: the local repos?
[12:08] <mmrazik> they are per stack
[12:08] <mmrazik> AFAIK
[12:18] <mhr3> sil2100, i heard that there was some armhf-releated hanging of libunity, could you point me somewhere with a log?
[12:19] <didrocks> mmrazik: are you sure? seems they have a 7.0 branch and tels that it's taking the 100 scopes branches
[12:19] <didrocks> well, I'll let you check with them :)
[12:21] <mmrazik> didrocks: otp. will have a look in a sec
[12:25] <veebers> didrocks: looks like I missed sil2100, I'll leave a note for thomi, he should be on in ~8 hours or so
[12:25] <veebers> (re: the MP)
[12:25] <didrocks> veebers: ok, perfect, thanks!
[12:28] <veebers> didrocks: nw, now i'm off to bed o/
[12:28] <didrocks> veebers: have a good night :)
[12:29] <mmrazik> Trevinho, didrocks: do you have a link to jenkins job failing?
[12:29]  * didrocks let that for Trevinho, you don't need me :)
[13:10] <tedg> pstolowski, So I'm a bit confused.  I thought you guys had a fix for the autopilot failures.
[13:11] <pstolowski> tedg: we identified some failures to be AP bug, but we don't have any conclusion for hud failures
[13:11] <tedg> pstolowski, Hmm, okay.  Can you file bugs so that we can track them?
[13:15] <pstolowski> tedg: i'm in the sprint on IOM and too busy atm to do that.. can you or somebody from your team take a look if these are real HUD failures or some a test/AP problem, and take care of bugs?
[13:16] <tedg> pstolowski, Well, I don't have a team :-)  Triaging phone "emergencies" right now, but I can put it in the queue.
[13:22] <tedg> cyphermox, It seems that we didn't get a daily release of HUD last night.  Do you know where I can check to see what happened?  https://code.launchpad.net/~indicator-applet-developers/hud/trunk.13.10
[13:28] <Mirv> andyrock: anyone looking at bug #1181717 yet? I understood it's hurting the ability to do work (when using unity) in saucy
[13:34] <tsdgeos> greyback: mzanetti: standuping?
[13:34] <tsdgeos> didrocks: nic-doffay: ↑↑
[13:34] <greyback> coming
[13:34] <Mirv> Trevinho: or is that actually bamf bug, not unity, and should be retriaged? ^
[13:35] <kgunn> tsdgeos: i'm on a vendor call atm
[13:35] <tsdgeos> oka
[13:36] <Cimi> dednick, ^
[13:37] <andyrock> Mirv, should not be unity's fault
[13:37] <andyrock> maybe bamf or glib
[13:38] <andyrock> and I can't reproduce building bamf from sources
[13:48] <Mirv> andyrock: infinity suspected that the glib upgrade triggered bugs, but that it's a legimate double-free bug that just surfaced with the glib update
[13:48] <Mirv> that reportedly was found in ubiquity at least with the glib upgrade
[13:49] <andyrock> Mirv, in that case it's bamf
[13:49] <andyrock> Trevinho, ^^^
[13:58] <cyphermox> tedg: my guess is it failed tests...
[13:58] <cyphermox> I can't seem to reach jenkins for now
[13:58] <cyphermox> as soon as I can get to the interface I'll be able to tell you more
[14:01] <tedg> cyphermox, That's impossible, my tests are impervious to failure.  ;-)
[14:01] <tedg> Cool, ping me if you find anything.
[14:03] <cyphermox> hey, your tests were doing great after we fixed autopilot ;)
[14:03] <pstolowski> tedg: sorry for slow response... it would be great if you could just spend a few minutes looking into AP fail logs for hud tests and add comments to the spreadsheet
[14:03] <cyphermox> brb, need to restart to test something
[14:04] <Trevinho> mmrazik: sorry I was out for lunch, one is at https://jenkins.qa.ubuntu.com/job/unity-7.0-raring-amd64-autolanding/16/console
[14:04] <Trevinho> Mirv: about that crash, I've been looking a little, but as andyrock said it's a little tricky as it doesn't fail when building from src.... (nor there are warnings)
[14:06] <mmrazik> Trevinho: mhm.. it seems to be misconfigured
[14:06] <mmrazik> fginther: can you please have a look on the local_archive settings for unity in head and raring?
[14:06] <andyrock> Mirv, Trevinho yeah I don't get it building from src
[14:07] <mmrazik> fginther: AFAIKT they should not be using the same local repo but for some reason they are configured to do so
[14:07] <mmrazik> fginther: so the 100scopes stuff affects landing of unity 7.0 (raring)
[14:14] <fginther> mmrazik, looking
[14:15] <mmrazik> thanks fginther
[14:32] <tedg> Can anyone else get to the internal Jenkins?
[14:32] <didrocks> tedg: no, see the engineering list
[14:33] <tedg> Hmm, okay.
[14:42] <Cimi> bregma, hey stephen, would it be possible to have someone assigned on this? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1181717
[14:43] <bregma> Cimi, several people are already looking at it, it'll get assigned after the discussion is over
[14:44] <Cimi> bregma, good to hear people are looking at it!
[15:05] <tedg> pstolowski, Turned them into bugs here: https://bugs.launchpad.net/hud/+bugs?field.tag=autopilot
[15:11] <pstolowski> tedg: awesome, thanks. whom can I pester to work on them? ;)
[15:16] <tedg> pstolowski, Let me try to figure out who should own them next :-)
[15:16] <tedg> pstolowski, Not sure who to assign Unity 7 ones to.  bregma likes bugs.  :-)
[15:17] <bregma> no no no
[15:28] <didrocks> kenvandine: mind launching webcreds? it couldn't build
[15:28] <cyphermox> tedg: poke
[15:28] <didrocks> kenvandine: mangers is back
[15:28] <didrocks> magners*
[15:28] <tedg> didrocks, How do we know what version of HUD these tests last passed with?  I mean, is Unity the only thing changing here or are we talking about a new HUD version as well?
[15:29] <cyphermox> tedg: hud didn't publish because indicators didn't publish
[15:29] <didrocks> keyou maybe want to look at friends :)
[15:29] <tedg> cyphermox, Mmm, oh, wait, you're not my wife!
[15:29] <cyphermox> is there anything hud needs from the indicators, or the other way around?
[15:29] <cyphermox> I mean, can I independently publish hud safely?
[15:29] <didrocks> kenvandine: ^
[15:29] <tedg> cyphermox, ?
[15:29] <tedg> cyphermox, Yeah, it just pulls from them.
[15:31] <cyphermox> o.O?
[15:31] <kenvandine> yay... jenkins is up :)
[15:31] <cyphermox> I was just making real sure ;)
[15:38] <tedg> cyphermox, Just FYI, we'll be able to unravel the HUD and indicators more next month.  Once we get to using manifest files for them, HUD will just read those.
[15:38] <tedg> There should be no hard dependencies at that point.
[15:41] <kenvandine> didrocks, mind doing a review?
[15:41] <kenvandine> https://code.launchpad.net/~ken-vandine/cupstream2distro-config/settings_uoa_dest/+merge/166537
[15:42] <didrocks> kenvandine: should be ppa: daily-build-next
[15:42]  * kenvandine fixes
[15:42] <didrocks> kenvandine: let's try to keep daily-build-next -> next and daily-build -> distro to not blurry the lines :)
[15:42] <didrocks> (even if that would work)
[15:43] <kenvandine> didrocks, pushed
[15:44] <didrocks> kenvandine: approved, feel free to deploy :)
[15:46] <kenvandine> thx
[15:52] <kenvandine> didrocks, so there has been a manual upload for g-c-c-s to saucy, with a backport from trunk.  would it be better for me to fix the changelog in trunk or just force manual publication and forget about the missing changelog entry?
[15:53] <kenvandine> feels weird to lose a changelog entry, but then again it was already fixed in trunk :)
[16:10] <tedg> charles_, I didn't realize I had an action item here, can I give it to you?  :-)  https://blueprints.launchpad.net/ubuntu/+spec/client-1303-ubuntu-touch-porting
[16:10] <tedg> charles_, I think it makes sense when you're blowing up the power indicator anyway.
[16:17] <tsdgeos> guys there's a problem with run_on_device
[16:17] <tsdgeos> something is installing ninja
[16:17] <tsdgeos> and i can't use run_on_device anymore since cmake complains i'm asking for a different generator than the old time
[16:17] <tsdgeos> or maybe i had crap in there and that's the problem
[16:18] <tsdgeos> now that we keep /home between flashes
[16:29] <tedg> bregma, So this one seems like Unity updating the search string it's giving to HUD (thus it's updating the results) but not updating the visible string.
[16:29] <tedg> https://bugs.launchpad.net/hud/+bug/1185858
[16:29] <tedg> bregma, So I'm thinking that's a Unity bug.
[16:29] <tedg> I don't think we should be checking for visibility of characters in the backend.
[16:50] <didrocks> kenvandine: you have to backport it
[16:50] <didrocks> kenvandine: the changelog commit
[16:50] <kenvandine> ok
[16:50] <didrocks> kenvandine: it's a security and forcing won't be do anything :)
[21:27] <om26er> aha, regression... scrolling over the sound icon while the dash is open, closes it.
[21:27] <om26er> bschaefer, ^
[21:27] <om26er> that's in 13.04
[21:28] <bschaefer> om26er, you mean to change the volume?
[21:28]  * bschaefer hecks
[21:28]  * bschaefer checks*
[21:28] <bschaefer> om26er, well yeah, clicking on it closes it as well
[21:28] <om26er> bschaefer, yes,
[21:29] <om26er> bschaefer, scrolling should not close the dash, that was not happening in 12.10
[21:29] <bschaefer> om26er, could you make a bug and assign me :)
[21:29] <bschaefer> om26er, the problem was I had to do some funky things to the dash cause of the window buttons and launcher icons size changing...
[21:33] <om26er> bschaefer, bug 1186026
[21:33] <bschaefer> om26er, thanks, cause what i do is if the mouse is over the indicators at all, and we get an event we close the dash
[21:34]  * bschaefer didn't think about scrolling...
[21:34] <bschaefer> om26er, thanks for pointing that out!
[21:34] <om26er> bschaefer, np :)