=== rsalveti_ is now known as rsalveti === salem_ is now known as _salem [08:01] didrocks: in case you have some time: https://code.launchpad.net/~private-ps-quality-team/cupstream2distro-config/add-debian-packaging/+merge/152835 [08:01] my autolanding watchdog branch is blocked by this (and thanks to that I missed that friends/libfriends were not landing due to a bug in the deployment tools) [08:02] mmrazik: yeah, I saw both, having a quick look :) [08:03] didrocks: great. not very urgent,though [08:03] just wasn't sure if you are watching the queue [08:03] mmrazik: I'm, I need to create a dedicated folder as it ends up in the "untriaged" directory which I really skim over :) [08:07] mmrazik: commented [08:30] hey sil2100! how was your day off? [08:49] didrocks: hello! Really nice, thanks, too bad I had to anyway run around and do some tax-related things in the morning anyway [08:50] argh… [08:50] sil2100: once you get some time, it seems that the issue with indicator tests failing are still there [08:52] Even with the workaround? [08:52] Grrrr [08:52] Ok, so, I have another way, more nasty, to take care of this one - I'll look at it in a moment [09:07] didrocks: ok, I see that at least the search test-workaround works and it doesn't fail, but tthose sudden 7 additional failures on indicators worries me - I'll upgrade my system and check what's up ;/ [09:08] sil2100: thanks dude! === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === mmrazik is now known as mmrazik|lunch [11:10] didrocks: strange thing with those failures, I see some old ones re-appearing, and also there was an unity crash on two machines [11:12] sil2100: you don't reproduce them locally? === Pendulum_ is now known as Pendulum === MacSlow is now known as MacSlow|lunch === dandrader is now known as dandrader|afk === popey_ is now known as popey [12:22] didrocks: no, but I'm trying to make one of the failing tests better again, so it doesn't fail so randomly === dandrader|afk is now known as dandrader === mmrazik|lunch is now known as mmrazik === MacSlow|lunch is now known as MacSlow [13:22] hey andyrock! [13:22] andyrock: I saw sam continued to work on bug #1140505 [13:22] bug 1140505 in Compiz "[regression-r3623] Wallpaper bleeds through on top right when a window is opened maximized" [High,In progress] https://launchpad.net/bugs/1140505 [13:23] ajmitch: do you know if it's ready? [13:23] mmm it should be ready for compiz/raring [13:23] need to test it btw [13:23] didrocks, ^^^ [13:24] andyrock: do you mind having a look in the next 2 days? [13:24] starting to get popular :) [13:25] didrocks, sure... next 2 hours should be ok too :) [13:25] \o/ [13:25] thanks andyrock [13:27] I use lvm snapshots a lot, (each sbuild creates a new one) so my launcher at the moment has 9 "disk" icons for each of the lvm snapshot/chroot. [13:27] the available "unlock" / "blacklist" is ok, but it works on UUIDs thus it's hard to prevent it from constantly adding all the new lvm snapshots. [13:28] can I somehow do patter matching and blacklist /dev/mapper/*chroot* pattern for example? [13:28] s/patter/pattern/ [13:37] np [13:51] fginther, the latest nvidia unity jenkins run performed 15 fewer tests than it did yesterday. I can't find obvious faults in the console log after it starts actually running tests (though there are some odd exceptions while its setting everything up, but those are there yesterday too). [13:52] mterry, I'll take a look [13:55] thanks! [14:31] mterry, hey [14:31] mterry, can you get https://code.launchpad.net/~seb128/unity/nautilus-default-launcher-icon/+merge/152382 approved? [14:32] seb128, looking [14:34] seb128, design approved the change I assume? [14:34] mterry, design are the one who requested the change :p [14:34] K [14:35] mterry, I double checked with JohnLea friday [14:35] seb128, do you care about migrating older users? [14:35] mterry, like https://launchpad.net/ubuntu/+source/nautilus/1:3.6.3-0ubuntu8 ? [14:35] ;-) [14:36] seb128, fine then. :) [14:36] mterry, thanks ;-) [14:36] seb128, hey also.. speaking of NoDisplay, why do I have two software centers now in the dash? One is unbranded-software-center.desktop and one is ubuntu- [14:36] Are there missing OnlyShowIn lines or something? [14:37] Maybe that's not a question for you [14:37] seems like a question for dobey === dandrader is now known as dandrader|afk [14:52] mterry: ping [14:52] mterry: available to review two MIRs? bug 1154130 and bug 1154126 [14:52] bug 1154130 in autoconf-archive (Ubuntu) "[MIR] autoconf-archive" [Undecided,New] https://launchpad.net/bugs/1154130 [14:52] bug 1154126 in python-dbusmock (Ubuntu) "[MIR] python-dbusmock" [Undecided,New] https://launchpad.net/bugs/1154126 [14:52] cyphermox_, OK [14:53] they should both link to the bug fixed by a branch we'd like to land [14:53] maybe if you want to give me a second opinion on https://bugs.launchpad.net/indicator-messages/+bug/1154099 ; but it looks to me like bugfix more than feature [14:53] Launchpad bug 1154099 in Messaging Menu "Applications are not unmarked when MessagingMenuApp is unrefed" [Medium,Triaged] [15:02] mterry, I found that unity died during or before unity.tests.test_dash.DashClipboardTests.test_ctrl_a [15:05] mterry, "09:58:23.226 ERROR __init__:55 - Unity doesn't appear to be running, exiting." [15:06] fginther, ah, good find. Seems bad :-/ [15:07] fginther, no core files were found though [15:07] mterry, I don't see any crash files either, some activity is syslog is all === dandrader|afk is now known as dandrader [15:09] During the indicator tests unity died as well [15:09] In build 165 on unity.tests.test_hud.HudBehaviorTests.test_hud_closes_click_outside_geo, because of unknown reasons === mmrazik is now known as mmrazik|otp === mmrazik|otp is now known as mmrazik === mmrazik is now known as mmrazik|afk === mmrazik|afk is now known as mmrazik === mmrazik is now known as mmrazik|afk === mhall119 is now known as mhall119|lunch === mmrazik|afk is now known as mmrazik === mhall119|lunch is now known as mhall119 [18:07] davidcalle: hangout? === maxb_ is now known as maxb [18:11] mhall119, too early for me (we haven't changed time yet here :) ) [18:11] man, I thought google calendar handled that kind of thing for us [18:11] in 45 minutes then? [18:12] mhall119, ok [18:12] cool, thanks [18:12] mhall119, ty [18:36] sil2100, hey, can you look at https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1141079 ? [18:36] Launchpad bug 1141079 in compiz (Ubuntu) "[regression-r3606] Compiz broken with QT menus/floating controls in 13.04" [Undecided,Confirmed] [18:45] mterry, ^ [18:47] hmm [18:57] seb128: looking [18:58] mterry: ok, will be dealing with this ;) [18:59] sil2100, thanks! [19:02] davidcalle: ready? [19:03] mhall119, yep [19:03] davidcalle: https://plus.google.com/hangouts/_/9f2f614038358849e6634c7cdcb68a1a87d5f0dd [19:28] didrocks: still around? [19:28] mmrazik: just back, what's up? [19:28] didrocks: noticed your experimental stack [19:28] yep [19:28] didrocks: just a note -- if you try to create the ci/autolanding jobs it will have unexpected results [19:28] didrocks: right now the job names are constructed from the project name [19:28] didrocks: so libunity would clash e.g. [19:29] mmrazik: I'm just creating the daily release [19:29] didrocks: ok. just in case :) [19:29] mmrazik: I think you will get the request to have upstream merging though [19:29] didrocks: we have been discussing this with fginther todya [19:29] mmrazik: I need the same name though as it's one logical unit [19:30] didrocks: so renaming it to libunity-7.0 is not an option? [19:30] mmrazik: possible, but I would prefer we keep the same name. I designed the dep system on it [19:31] didrocks: mhm... not sure I understand. Wouldn't libunity-7.0 have different deps than lp:libunity? [19:32] mmrazik: I mean that projects have relationship [19:32] mmrazik: like, if libunity is built on the raring (distro) [19:32] mmrazik: this will enabling libunity in the experimental stack [19:34] didrocks, will stack names always be unique? [19:34] fginther: yeah, but some components can move from one stack to another [19:34] like we had from misc -> qa [19:34] ah [19:35] you mean unique between release? [19:35] fginther: I think you will have libunity for raring and one for s, isn't it? [19:35] they will both have the same project name [19:35] btw. I don't get it but I'm drinking beer already. Will try to figure it out tomorrow [19:35] different branches though [19:35] * fginther head explodes [19:36] didrocks, so you could have a qa stack for raring and s, but they will be unique within the release [19:36] * kalenjohnson get's the mop [19:37] fginther: depends in what you call release :p [19:37] raring and s are series [19:37] release is "head", "experimental" [19:37] didrocks, ahhh, so they are [19:37] those names [19:38] so, for instance [19:38] we have libunity in head [19:38] didrocks, I think I understand. Just need to absorb the implications [19:38] * mmrazik is googling what release is [19:38] and experimental [19:38] I thought head=trunk [19:38] they all target the series "raring" [19:38] mmrazik: exactly [19:38] that's the release name [19:39] didrocks: in that case what is experimental? feature branches? [19:39] mmrazik: it's the name for the release [19:39] look at stacks/ [19:39] you have two dir [19:39] each dir is a release [19:39] head/ experimental/ [19:40] they both target the raring series [19:40] (we can change the release terminology, it's not clear IMHO and I didn't choose it) [19:41] I still don't understand what experimental means then... so we will be releasing that stuff into raring? [19:41] not raring [19:41] in a ppa [19:41] it's a collection of feature branches [19:41] for the 100 scopes projects [19:42] okay... so experimental = feature branches [19:42] mmrazik: right [19:42] the triplet (stackname, project, release) is unique [19:42] that's why I create for instance: [19:42] cu2d-100scopes-experimental-1.1prepare-unity [19:42] (1.1prepare is the job name) [19:43] didrocks: but eventually we will have a directory called raring? When all the trunks will be branched for new development and there will be raring branches for maintenance? [19:43] or rather s/rarinring/whatever LTS release/ [19:43] mmrazik: right, that's why it was called "release" before I guess :) [19:43] and head will move to s [19:43] didrocks: ok. understood. [19:44] didrocks: can we make (project, release) unique? [19:44] i.e. project will be unique within stackname [19:44] fginther: ^ [19:44] mmrazik: well, I can imagine the day we have 2 features involving unity [19:44] so experimental/100scopes.cfg [19:44] and experimental/foofeature.cfg [19:44] didrocks: I would prefer different project names there TBH [19:44] both containing the "unity" [19:45] unity-100scopes [19:45] unity-foo [19:45] mmrazik: it's still targetting unity [19:45] mmrazik: and we need to know the relations between projects [19:45] so that if a new upload happen, in the "unity" project in raring [19:45] Can I move the launcher to the left side? [19:45] (in head/ for instance) [19:45] didrocks: I think I'll need to absorb this :) [19:45] I need to relaunch the "unity" projects in experimentals [19:46] didrocks: I think I start to understand, though [19:46] mmrazik: yeah, sorry, this came after a lot of thoughts ;) [19:46] mmrazik: some beers/night will help I guess :) [19:46] * didrocks is out of beer [19:46] didrocks: thats fine. The only issue is that my thoughts have been a bit different so far (and I just started to add some phablet stuff) [19:47] so I need to think about it and make my thoughts fit with yours :) [19:47] mmrazik: yeah, phablet should have its own "release" [19:47] I guess [19:47] so head/ experimental/ phablet/ [19:47] mmrazik: making sense? ^ [19:48] didrocks: yeah... I guess so === kgunn is now known as kgunnAFK