[05:20] <TheMuso> Trevinho: Re the new shutdown/restart dialog in raring thats rendered by unity... Can that be disabled with a gsettings key?
[07:22] <mmrazik> didrocks: regarding https://code.launchpad.net/~private-ps-quality-team/cupstream2distro-config/ubuntu-phone-coreapps/+merge/152757
[07:22] <mmrazik> didrocks: it is not about the phablet stuff we talked about yesterday
[07:22] <mmrazik> didrocks: those are community driven projects running on separate jenkins: http://91.189.93.125:8080/
[07:22] <didrocks> mmrazik: they are still not in ubuntu and rely on the phablet infra?
[07:23] <didrocks> mmrazik: for me, they are part of the same "set" of things to land
[07:23] <mmrazik> didrocks: ok. I wanted to have them a bit separated so somebody doesn't deploy them on wrong jenkins by accident
[07:23] <mmrazik> but we can workaround that, I guess
[07:24] <didrocks> mmrazik: yeah, I think it will be good to keep them in a separate stack
[07:24] <didrocks> but still part of the "phablet" project
[07:24] <didrocks> until we move to head
[07:24] <didrocks> which is still unsure for raring
[07:24] <mmrazik> didrocks: ok
[07:25] <mmrazik> didrocks: btw. phablet dir already exists
[07:25] <mmrazik> created it this morning
[07:25] <didrocks> mmrazik: oh excellent! :-)
[07:25] <mmrazik> the project names are still different, though (unity-phablet)
[07:25] <didrocks> mmrazik: no worry for you if we move the stack name in the near future?
[07:26] <didrocks> mmrazik: yeah, that's someting I can help you (but only next week) to fix
[07:27] <mmrazik> didrocks: re. renaming the stacks -- I don't mind. Just let me know. I will need to fix the job which is triggering the ci/autolanding jobs (right I'm not triggering all stacks as not all are migrated to cupstream2distro-config)
[07:27] <didrocks> ok
[08:48] <didrocks> davidcalle: salut!
[08:48] <didrocks> ça va?
[08:49] <davidcalle> didrocks, hey, bien et toi ?
[08:49] <didrocks> ça va :)
[13:04] <cyphermox> good morning!
[13:04] <didrocks> hey cyphermox
[13:04] <cyphermox> didrocks: so if I understand well, publish indicators+misc, rerun/with ppa oif, then publisch that too?
[13:05] <cyphermox> actually, assuming all is well re: feature freeze
[13:05] <didrocks> cyphermox: why rerunning oif?
[13:05] <didrocks> cyphermox: assuming -> you know from the MP ;)
[13:05] <cyphermox> yeah that's what I mean
[13:06] <cyphermox> still it's not obvious from the dashboard
[13:06] <cyphermox> oif> 2013-03-13 02:02:54,219 WARNING qa (head) failed to publish. Possible cause are:
[13:06] <cyphermox> just being thorough
[13:06] <cyphermox> looks like it was timing
[13:06] <didrocks> cyphermox: oif is telling that the qa tooling failed. But the test results are good
[13:06] <didrocks> cyphermox: no, the qa failed because of the "prepare" yesterday
[13:06] <didrocks> then I reran with the fix the qa stack this morning
[13:06] <didrocks> just didn't rerun oif
[13:06] <cyphermox> that's what I mean
[13:06] <didrocks> cyphermox: you can rerun oif if you want, but it's not mandatory
[13:07] <cyphermox> nah
[13:07] <didrocks> we know we can publish for sure
[13:07] <didrocks> in that case
[13:07] <didrocks> (because it's qa which failed, not a really important rdepends)
[13:07] <didrocks> makes sense?
[13:07] <cyphermox> oh yeah, I was just saying, before noticing it's actually a "timing" issue, that it possibly could just be re-tested
[13:08] <didrocks> cyphermox: as you prefer :)
[13:32] <mmrazik> didrocks: I have a problem with project names :-/ Consider this: http://pastebin.ubuntu.com/5610669/
[13:32] <mmrazik> there are a lot of phablet-extras/$something branches
[13:32] <mmrazik> so all the projects should be called phablet-extras
[13:32] <mmrazik> which is not going to work
[13:32] <mmrazik> (I agree that the project setup is just wrong but thats what we have)
[13:33] <didrocks> mmrazik: on those, I don't care about the mapping, they are transiant components that will be removed
[13:33] <didrocks> mmrazik: and project name for me doesn't necessarily map with the launchpad project (but they should)
[13:34] <mmrazik> didrocks: ok.. I'll just go with the names I have there now
[13:34] <didrocks> yep
[13:43]  * davidcalle wonders if the ctrl, c and v keys on didrocks keyboard will still work tonight. :P
[14:37] <didrocks> davidcalle: it's crazy! I'm blaming you :)
[14:37] <didrocks> davidcalle: we should really prepare in advance those kinds of features from start
[14:37] <didrocks> davidcalle: btw, a lot of tests are failing when building the scopes
[14:37] <didrocks> I'll make the list and fw it to thomas
[14:39] <davidcalle> didrocks, hmm, if you are building without libunity7, they should fail, but if you are, that's worrying...
[14:39] <didrocks> davidcalle: no, I'm with libunity7
[14:39] <didrocks> davidcalle: some keyerror
[14:39] <didrocks> or wrong diff (in case of launchpad)
[14:40] <didrocks> davidcalle: seeing how much the packaging was working, you never used bzr bd, isn't it?
[14:40] <didrocks> davidcalle: like the missing svg files ;)
[14:41] <davidcalle> didrocks, I don't have a system wide libunity7, a first package was made by someone experimented I won't name and it was all copied from here ;)
[14:42] <didrocks> davidcalle: I don't mention libunity7, but the scopes ;)
[14:42] <davidcalle> didrocks, missing svgs are totally my fault, by dismissing the fact, in templates, that scopes using local sources wouldn't have these icons.
[14:42] <didrocks> davidcalle: yeah, so nobody used the package (like bzr bd) to build it?
[14:42] <didrocks> davidcalle: you will have a look at the tests?
[14:42] <didrocks> on my list of failing, I have:
[14:42] <mterry> cyphermox, it looks like you've manually published indicators and misc.   what about the oif stack?  is that yours?
[14:43] <cyphermox> yeah
[14:43] <didrocks> calculator, zotero, github, yelp, launchpad, tomboy, weather
[14:43] <didrocks> davidcalle: ^
[14:43] <cyphermox> didn't seem to me to have anything to publish though
[14:43] <cyphermox> (ie. no changes files in the directory on magners)
[14:44] <davidcalle> didrocks, thanks. I see what the issue is with a few of these, but not all. Looking  at it.
[14:44] <mterry> cyphermox, oh, OK.  So I'll publish unity then
[14:57] <mterry> w000, reduced unity stack's allowed-failure threshold to 16 from 20.  We'll get to zero eventually
[15:15] <seb128> davidcalle, hey
[15:16] <seb128> davidcalle, is unity-scope-musique supposed to replace the music lens or is that a different service?
[15:16] <davidcalle> hey seb128
[15:16] <davidcalle> seb128, it's the "Musique" music player.
[15:17] <seb128> oh, ok
[15:17] <seb128> I didn't know there was a player named musique :p
[15:18] <davidcalle> seb128, me neither, this is a niche scope :p
[15:18] <seb128> davidcalle, quite some of those new lenses fail to build on broken tests, I guess that's a known issue? (some miss the .svg in their vcs as well which breaks install)
[15:19] <davidcalle> seb128, calculator, zotero, github, yelp, launchpad, tomboy, openweathermap? Do you have the same broken tests list?
[15:20] <didrocks> davidcalle: my broken one is merged from mine and seb128's one :)
[15:20] <davidcalle> seb128, missing svgs are my fault: scopes relying on local services don't have one, and I forgot that while doing the setup/packaging script.
[15:20] <seb128> davidcalle, yes ;-)
[15:22] <seb128> davidcalle, oh, manpages as well
[15:22] <seb128> for the failing tests
[15:23] <davidcalle> seb128, didrocks: I'm on it, from what I can see, errors go from a simple missing depend to no mock data at all for the test, or even crazy things. eg, for Openweathermap, I'm realizing that the passing of the test depends on the time of the day :)
[15:24] <seb128> yeah, the weather one is fun :p
[15:26] <didrocks> davidcalle: for missing depends, normally we check them
[15:27] <didrocks> davidcalle: but if we missed some, ensure the dep is in main please :)
[15:29] <seb128> davidcalle, those (at least) have the missing icon issue: zotero tomboy texdoc music
[15:31] <davidcalle> didrocks, I know that at least one dep is still in universe ( python3-feedparser), but that's not an issue, right mterry? :)
[15:32] <didrocks> no, it's not, python-feedparser is in main
[15:32] <mterry> davidcalle, probably not...  it looks like python-feedparser is in main already
[15:33] <davidcalle> seb128, thanks. Commenting it out like you did is probably the way to go for these. I'll ping Design for more icons (eg zotero). Sorry again about that.
[15:33] <davidcalle> mterry, thanks
[15:34] <seb128> davidcalle, no worry, thanks
[15:34] <seb128> davidcalle, mterry: right, python3-feedparser is a binary promotion, no MIR needed
[15:55] <seb128> davidcalle, googlenews tests fail in a pbuilder
[15:55] <seb128>     LOC = locale.getlocale(locale.LC_MESSAGES)[0].split(".")[0].lower()
[15:55] <seb128> AttributeError: 'NoneType' object has no attribute 'split'
[15:55] <seb128> LC_MESSAGES is not defined there
[15:56] <davidcalle> seb128, ok. I'll make it optional in a moment.
[15:57] <seb128> davidcalle, no hurry, just pointed issues I cross ... I can open bugs if there is a bug tracker and that's the preferred way
[16:23] <didrocks> mterry: reverting my WI? :/
[16:26] <mterry> didrocks, oh crap, what did I do?
[16:27] <mterry> did I forget to refresh the page?  darn it
[16:27] <mterry> it should intercept such things
[16:27] <didrocks> mterry: seems so :)
[16:27] <mterry> didrocks, I'll fix, sorry
[16:27] <didrocks> mterry: I'm sure you are just mean and it's on purpose!
[16:27] <didrocks> thanks mterry :-)
[16:41] <Esokrates> is there a special reason the maximal number of arrows displayed in the launchers is set to 3?
[16:43] <Esokrates> there would be place for more, without producing clutter ...
[16:44] <Esokrates> is it for the "readability"? I have thought the average human is capable of seeing the number of at least 7 objects in a row without counting at one glance?
[16:46] <Esokrates> it is obvious that there has to be a maximum, but I doubt that 3 is the optimum
[17:32] <didrocks> tedg: do you mind just making your changes
[17:32] <didrocks> tedg: and save once?
[17:32] <didrocks> getting 20 emails just because you save the blueprint after each character :/
[17:32] <tedg> didrocks, No, we're working together in a room so that we can all see it.
[17:33] <didrocks> tedg: I don't see why it's preventing you using gedit :)
[17:33] <didrocks> or etherpad
[17:33] <tedg> didrocks, No one has rewritten it in QML yet.
[17:33] <tedg> :-)
[17:33] <didrocks> pfffff :p
[17:33] <didrocks> come on, you have the guys for that
[17:33] <didrocks> :)
[17:35] <tedg> didrocks, Yes, the problem is that they're French, so on strike today :-)
[17:35] <didrocks> tedg: well, London is a nice city to be on strike, thinking about it :)
[17:36] <tedg> didrocks, Heh, it actually just started snowing pretty good.
[17:36] <didrocks> mmrazik: hey! so the 100scopes experimental should be good for deploying upstream merger
[17:36] <didrocks> davidcalle: mhr3: pstolowski: ^
[17:36] <didrocks> tedg: oh, lovely, enjoy :) (well, you will enjoy that less on Saturday)
[17:38] <mmrazik> didrocks: is it fine if I deploy tomorrow?
[17:38] <mmrazik> didrocks: also... right now we don't allow non-canonical people to run stuff on jenkins (unless its approved by somebody from canonical)
[17:38] <mmrazik> and there are couple non-canonical people
[17:38] <didrocks> mmrazik: I guess tomorrow is fine
[17:38] <mmrazik> so it might happen that a MP will be ignored
[17:38] <davidcalle> didrocks, awesome! Does it mean, we are now on mandatory mp for each scope branch? (not that it's not already the case *cough*)
[17:38] <mmrazik> (e.g. if created and approved by non-canonical people)
[17:39] <mmrazik> davidcalle: the system doesn't enforce it, but yes
[17:39] <didrocks> mmrazik: well, I think davidcalle will know who to bribe :)
[17:39] <didrocks> davidcalle: yeah ;)
[17:39] <didrocks> now that the packaging is set
[17:39] <didrocks> daily release to a ppa starts
[17:39] <didrocks> and upstream merging on the way :)
[17:40] <Esokrates>  is there a special reason the maximal number of arrows displayed in the launchers is set to 3?
[17:43] <davidcalle> Thanks didrocks, mmrazik. I have tiny fixes (install paths and broken tests) for a large number of branches. I'll try to have everything mp asap, but on which team should I put this review load? :)
[17:43] <didrocks> davidcalle: just ping directly mhr3, pstolowski  I guess
[17:44] <mmrazik> let me deploy the upstream merger then...
[17:44] <didrocks> or bregma, maybe you can help ^
[17:44] <mmrazik> I just don't like to do this sort of stuff at the end of my day when I have no chance to fix things :)
[17:44] <mmrazik> didrocks: oh...
[17:44] <mmrazik> didrocks: project names is a problem in that config
[17:44] <mmrazik> didrocks: we have a conclusion with fginther on how to do it but not implemented yet
[17:45] <mmrazik> postponing the deployment to tomorrow...
[17:46] <davidcalle> mmrazik, does it mean I can push some of these directly tonight and it won't affect the merging process?
[17:46] <didrocks> mmrazik: sure, I think that can wait tomorrow :)
[17:46] <mmrazik> davidcalle: ack
[17:46] <mmrazik> davidcalle: in matter of fact you can push directly even after this stuff is deployed. its just strongly discouraged :)
[17:48] <davidcalle> mmrazik, sure, but we are two on the project, both non canonical. I'm happy to have these changes reviewed, but I don't want anything to be blocked on changing an install path.
[17:49] <mmrazik> davidcalle: ack
[19:38] <sil2100> mterry: hi! I'm still doing some experiments regarding #1141079
[19:38] <sil2100> mterry: but if tomorrow evening I won't have it working, I'll try reverting the fix then