[07:33] <sil2100> didrocks: why did some merges get inside unity?
[07:33] <sil2100> (hi)
[07:34] <sil2100> didrocks: hi, aren't we in a freeze in unity? ;)
[07:35] <didrocks> sil2100: we are
[07:35] <sil2100> didrocks: since, hm, we'll have to re-do the tests again, since 4 new commits are in :)
[07:36] <didrocks> sil2100: I know :( but they UNBLOCK them
[07:36] <didrocks> sil2100: well, TBH, when it's tests only, that's fine, no need to
[07:36] <didrocks> sil2100: but for the 2 others, yeah :/
[07:36] <sil2100> didrocks: two of them fix actual bugs...
[07:36] <sil2100> didrocks: the problem is, I should be on holiday now ;)
[07:36] <didrocks> oh?
[07:37] <didrocks> bank holiday or real holidays?
[07:37] <sil2100> didrocks: yes, I just thought that I'll log in, roll-out the tarball and done
[07:37] <sil2100> didrocks: it's my holiday week, I booked it some time ago ;p
[07:38] <didrocks> sil2100: well, blame PS upstream… :/
[07:38] <didrocks> they should ask you for UNBLOCKING
[07:38] <didrocks> sil2100: the armhf FTBFS isn't important btw, seems to have been transiant
[07:38] <didrocks> as the next commit built successfully
[07:38] <didrocks> in case you wondered :)
[07:52] <didrocks> sil2100: btw, you should look at
[07:52] <didrocks> https://code.launchpad.net/~sil2100/unity-2d/bump_new_nux_libunity/+merge/113563
[07:52] <didrocks> as well
[07:54] <sil2100> didrocks: hm, he can't find nux-3.0?
[07:54] <seb128> sil2100, popey: there are 3 bugs on the compiz SRU that didn't get verified, would be nice to get them verified so it can move to -updates...
[07:54] <seb128> sil2100, popey: but probably not for sil2100 if he's supposed to be on holidays
[07:55] <sil2100> seb128: we'll check that
[07:55] <didrocks> sil2100: yeah, seems a packaging issue as the package isn't merged :)
[07:55] <seb128> sil2100, enjoy your holidays btw ;-)
[07:55] <davidcalle> sil2100, hi, quick question about Unity 6. I'm reviewing packaging changes for third party lenses: gir1.2-unity-5.0 -> 6.0 , and a new path for those depending on Unity icons, right?
[07:55] <didrocks> davidcalle: yeah, you need to change both of those
[07:55] <sil2100> davidcalle: yes
[07:55] <sil2100> seb128: thanks, I will :)
[07:56] <davidcalle> didrocks, sil2100 thanks.
[08:03] <popey> seb128, roger that
[08:03] <popey> (morning btw)
[08:36] <MCR> smspillaz: Hi. It will take a while until I get to testing the Experimental PPA...
[08:36] <MCR> smspillaz: Which IDE do you recommend to hack on Compiz/Unity ?
[08:37] <smspillaz> MCR: Qt Creator
[08:37] <smspillaz> MCR: don't worry too much about it, there are many things that are still broken :)
[08:37] <MCR> smspillaz: Thx 4 the fast answer - I will try that :)
[08:38] <smspillaz> MCR: Some people use Sublime Text too, but I've never been able to get it to work just right
[08:38] <MCR> smspillaz: Just wanted to let you know I have not forgotten my promise ;)
[08:38] <smspillaz> :)
[08:38] <smspillaz> thanks in advance
[08:38] <smspillaz> I need more caffiene
[08:39] <MCR> np, I am honored to help.
[08:40] <MCR> me too ;)
[08:46] <MCR> smspillaz: There are some weird things regarding the keyconfig happening in recent 0.9.8 versions. For example it is impossible to have Alt+RightMousebutton toggle window maximize, like I had here for ages - it will always show the window menu here. Any idea what change might have caused this ?
[08:50] <smspillaz> MCR: not off the top of my head sorry
[08:54] <MCR> np, I know your priority is OpenGL ES now. I will try to file comprehensive bug reports to detail the situation.
[08:54] <MCR> But I think it might be related to Unizy/Compiz not sharing all information about shortcuts, like is happening with Ctrl+Tab for example, which is already in fixed use by Unity, but CCSM does not know about it.
[08:55] <hyperair> could be unity. unity's keyboard shortcut handling is scary
[08:55] <MCR> It has to be unified with Compiz/CCSM or otherwise it will be chaos
[08:56] <MCR> like it is now, when Unity assigns keys Compiz does not know about...
[08:56] <hyperair> well to my knowledge, unity only really inteferes with super keybindings
[08:56] <MCR> All keycombis regarding Unity should be configurable in the Unity plug-in, none should be hardcoded imho
[08:57] <MCR> otherwise Compiz does not know and will not warn if the same hardcoded keycombis are assigned to other tasks in CCSM
[09:01] <MCR> bug 1017539 for example - Could someone tell me where the keycombinations are assogned in the Unity/Compiz code ? Then I could probably work on fixing that issue with Ctrl+Tab and maybe others...
[10:03] <MCR> unityshell.cpp, line 348ff: ubus_manager_.RegisterInterest(UBUS_LAUNCHER_START_KEY_SWTICHER, ?
[10:03] <MCR> line 354: ubus_manager_.RegisterInterest(UBUS_LAUNCHER_END_KEY_SWTICHER,
[10:04] <MCR> line 357: ubus_manager_.RegisterInterest(UBUS_SWITCHER_START,
[10:49] <MCR> smspillaz: Qt Creator is very nice - I am already getting used to it - Is there a project file for the Compiz/Unity project available somewhere also ?
[10:54] <MCR> btw, I found the cause of a quite big problem in the Unity plug-in. A lot of shortcuts for Unity are hardcoded and exactly those shortcuts are not recognized by Compiz and the CCSM, so you can easily double-bind them leading to strange behavior...
[10:55] <MCR> in unityshell.cpp 2990ff you can find the hardcoded options which are completely "invisible" for the check in CCSM
[10:57] <MCR> Combinations like Ctrl+Tab, Alt + Space, Ctrl+Alt+Num are hardcoded there. Is there a reason to do that ?
[12:19] <MCR> StandaloneShortcuts.cpp in line 78 says:
[12:20] <MCR>   // I don't know std::shared_ptr<shortcut::AbstractHint>(if it is really hardcoded, but I can't find where this option is stored.
[12:20] <MCR>   hints.push_back(std::shared_ptr<shortcut::AbstractHint>(new shortcut::MockHint(_("Windows"), "", "", _("Open window accessibility menu."), shortcut::HARDCODED_OPTION, "Alt+Space")));
[12:21] <MCR> ^^ this option is stored in General Compiz Options, Key Bindings !
[12:27] <MCR> smspillaz: Could you confirm that this will most likely produce problems ? ^^
[12:53] <MCR> hyperair: Reading more of the code makes me agree - scary indeed :)
[13:11] <didrocks> popey: any news on the unity release?
[13:12] <popey> didrocks, we're on a call about it now.
[13:13] <popey> didrocks, doing some confirmation checkbox tests
[13:13] <popey> should be good
[13:13] <didrocks> sweet! :)
[13:26] <sil2100> didrocks: we're finishing tests, all green up until now
[13:26] <sil2100> https://docs.google.com/a/canonical.com/document/d/1YE7rQa4xxpU176Uth41lnFX8Et-8BG6UKBqelbapLyU/edit#
[13:28] <didrocks> sil2100: really, after the release, send to the PS ML the status of failing autopilot tests which works manually, that would be valuable to fix them
[13:28] <didrocks> and less time consuming :)
[13:30] <sil2100> didrocks: will do for sure... ;)
[13:31] <sil2100> Since grepping for test descriptions all the time is really test consuming
[13:31] <didrocks> sil2100: yeah, I know :/
[13:36] <sil2100> didrocks: if anything, popey and Mirv are taking care of the release right now - but all the packaging/source branches are prepared
[13:37] <sil2100> didrocks: Mirv has the list of those
[13:37] <didrocks> sweet :)
[13:37] <didrocks> bugs are targeted?
[13:37] <sil2100> didrocks: I even pushed the unity branch for ubuntu, but without the proper changelog (waiting for that for your unify ;) )
[13:37] <sil2100> didrocks: yes :)
[13:37] <didrocks> great :)
[13:37] <sil2100> Ah, wait, I'll check the 2 new bugs!
[13:37] <sil2100> THe ones that were fixed today
[13:37] <didrocks> so they will do the merge-upstream in the packaging branch, the new tarball?
[13:38] <didrocks> or will you do that now? I didn't follow :)
[13:38] <didrocks> also, tell me when you want me to run unify
[13:38] <sil2100> didrocks: I already did merge-upstream for unity with the new tarball, but didn't have the changelog yet
[13:39] <sil2100> So the changelog modification needs to be made yet
[13:39] <didrocks> ah, so just that
[13:39] <didrocks> yep
[13:39] <sil2100> https://code.launchpad.net/~sil2100/unity/ubuntu_quantal
[13:39] <sil2100> Here it is
[13:40] <didrocks> sil2100: looks good at first sight
[13:40] <didrocks> can you pastebin all the branches url, already?
[13:40] <sil2100> Mirv knows where I put the tarballs, he'll send you them later when needed
[13:40] <sil2100> Ok
[13:40] <didrocks> sil2100: when will he send me that? it's not ready for releasing now?
[13:40] <sil2100> (since I put them on chinstrap, since that was the fastest way)
[13:40] <sil2100> I can give you the chinstrap url ;p
[13:40] <didrocks> he should put them on LP :)
[13:40] <sil2100> On priv
[13:41] <didrocks> rather
[13:41] <didrocks> and mark new upstreams as released
[13:41] <sil2100> Do we have permission for that? We didn't do that yet since the tests are not finished
[13:41] <didrocks> or I can do it for speeding up the process, but next time, it will be your turn
[13:42] <didrocks> ah ok, I thought they were done
[13:42] <didrocks> sil2100: still, give me the tarball, I'll build that there to ensure we can release quickly once I have the definitive green flag
[13:42] <didrocks> so branches and tarballs
[13:42] <Mirv> we're running the checkbox tests now
[13:44] <sil2100> didrocks: aye aye
[13:44] <sil2100> didrocks: branches http://paste.ubuntu.com/1082762/
[13:45] <didrocks> thanks
[13:45] <sil2100> Ok, I need to pop out for a little while, I'll be back later
[13:46] <sil2100> See you guys a bit later
[14:03] <Mirv> ok, running the most crucial test (quicklist, all of dash, all of hud) done, fginther will run more. earlier today I re-ran manual tests.
[14:04] <Mirv> I need to leave now, will be back 9.30pm (4.5 hours)
[15:05] <didrocks> popey: so it means no release today?
[15:10] <MCR> Here the fixes for minor typos I found: https://code.launchpad.net/~mc-return/unity/unity.merge-fix-typos/+merge/113987
[15:33] <om26er> does it make sense to still keep unity-2d "feature bugs" ?
[15:34] <om26er> I guess new features won't be added to -2d right?
[15:39] <didrocks> om26er: indeed
[15:39] <didrocks> maintenance only
[15:40] <om26er> didrocks, ok, thanks. I'll close a few of them if they come along the way.
[15:40] <seb128> popey, still there?
[15:40] <didrocks> ok :)
[15:41] <popey> on the phone..
[15:42] <seb128> popey, what's the status of the updates?
[15:42] <seb128> popey, we need to get the SRUs out this week, and for that we need to get the quantal updates out first
[15:42] <didrocks> davidcalle: hey, did sil2100 updated unity-scope-video-remote as well?
[15:42] <didrocks> davidcalle: for the path
[15:43] <davidcalle> didrocks, no path issue in this one. Icons are provided by the lens.
[15:43] <didrocks> davidcalle: ah good :)
[16:06] <MCR> Some proofreading would be nice, as
[16:06]  * MCR is no native English speaking person either ;) : https://code.launchpad.net/~mc-return/unity/unity.merge-fix-typos/+merge/113987
[16:08] <popey> didrocks, sorry, been on the phone most of the afternoon, I understood you had the release. what do you need from us now?
[16:08] <didrocks> popey: hum?
[16:08] <didrocks> popey: no, I didn't have any release
[16:08] <didrocks> seems that sil2100 told all the tests are not finished
[16:08] <didrocks> and Mirv left for the day
[16:08] <didrocks> until 9pm
[16:08] <didrocks> so it means no release
[16:09] <didrocks> popey: btw, it's been an hour I'm fixing some packaging issues (in addition to all the other I fixed already)
[16:09] <didrocks> some stuff like making a diff of configure.ac,in, CMakeLists.txt that I repeated numerous times already :p
[16:09] <mhr3> didrocks, speaking about icons, seems like noone really complained about getting rid of the version numbers
[16:10] <mhr3> so let's do it?!
[16:10] <didrocks> mhr3: yeah, just after the release :)
[16:10] <mhr3> sure
[16:10] <didrocks> let's try to get some tarballs out
[16:10] <didrocks> but still blocking in PS here :/
[16:10] <mhr3> i didn't want to do it right away
[16:11] <didrocks> mhr3: but agreed, let's do that just after it, will be a breath :)
[16:11] <mhr3> we'll see about that :)
[16:13] <didrocks> popey: please keep me posted
[16:13] <popey> will do
[16:14] <didrocks> thanks
[16:16] <didrocks> popey: btw, if people merge anything again to trunk, all has to be redone, maybe you want to ask them to merge and UNBLOCK no branch on the ML?
[16:16] <didrocks> popey: as it seems we won't have a release today :/
[17:22] <didrocks> popey: ? ^
[17:22]  * didrocks would like to have a followed discussion :/
[17:38] <sil2100> Hi
[17:39] <sil2100> didrocks: did Timo ask you to run unify?
[17:39] <didrocks> sil2100: no, he didn't finish the tests apparently
[17:39] <sil2100> didrocks: are all the branches OK?
[17:39] <didrocks> sil2100: I had to change quite a few things
[17:40] <sil2100> Sorry about that, but I thought I did all the things you pointed out last time
[17:40] <didrocks> missing removed dependencies (you didn't bzr diff CmakeLists.txt in unity :/) and other Breaks: and removing transitional packages missing
[17:40] <didrocks> all is updated
[17:40] <didrocks> also, I don't have the nux trunk branch
[17:40] <sil2100> Ah, nux trunk, wait
[17:40] <didrocks> but anyway, the biggest blocker is to not have all tests done
[17:40] <sil2100> didrocks: I'm using the nux trunk
[17:41] <sil2100> didrocks: no new commits
[17:41] <didrocks> sil2100: you didn't tag the release?
[17:41] <sil2100> didrocks: since the version got bumped by Jay's merge already...
[17:41] <sil2100> didrocks: what should I tag? make dist doesn't tag in nux
[17:42] <sil2100> didrocks: and there was no 'release commit' needed, since I have nothing to bump there
[17:42] <didrocks> sil2100: well, you have to do it manually when it's not done automatically
[17:42] <didrocks> sil2100: bzr tag latest version then
[17:42] <sil2100> Since everything had been bumped already :/ So I'll just tag the last commit
[17:42] <didrocks> so that dev knows which version is which
[17:42] <didrocks> and then bzr push
[17:43] <sil2100> Doing
[17:44] <didrocks> thanks :)
[17:44] <didrocks> not a biggie, the branch history won't juts get cleaned
[17:45] <sil2100> https://code.launchpad.net/~sil2100/nux/nux_3.0 <- could you ACK?
[17:45] <sil2100> I'm trying to reach Francis if he finished the tests
[17:45] <sil2100> But maybe he's on lunch or something...
[17:45] <didrocks> sil2100: juts bzr push :)
[17:45] <didrocks> to trunk
[17:46] <didrocks> sil2100: anyway, I'm working for more than 12 hours now, I won't push that today
[17:46] <didrocks> sil2100: you need to send an email to ensure that the PS team won't UNBLOCK anything tonight
[17:46] <didrocks> even tests, it will screw the branches
[17:46] <sil2100> didrocks: ok... will do that, thanks! :)
[17:46] <sil2100> Have a nice rest :)
[17:46] <sil2100> btw. did you push the 6.0 tag to unity yet?
[17:47] <sil2100> Can I push it as well?
[17:47] <didrocks> sil2100: you can push it if the tests are fine
[17:47] <sil2100> didrocks: ACK
[17:57] <sil2100> didrocks: it seems only multimonitor tests are left to do \o/
[17:58] <didrocks> sil2100: well, not your fault, but I would have expected those to be done by now
[17:58] <didrocks> anyway, will be tomorrow, you did your max on an off day :)
[17:58] <didrocks> let's hope next one will be more efficient ;)
[17:58] <sil2100> I hope so too! Since I learned a lot during this release
[17:58] <didrocks> sil2100: enjoy your holidays ;)
[17:59] <didrocks> and send that email please :)
[17:59] <sil2100> Will do, if you need me in the next days:
[17:59] <sil2100> Just ping Alan and he'll ping me through phone or other medium
[17:59] <sil2100> And if I'll be able, I'll pop up somehow :)
[17:59] <sil2100> didrocks: have a nice rest-of-the-day!
[17:59] <didrocks> sil2100: good, hoping it won't be needed!
[17:59] <didrocks> sil2100: thanks :)
[18:01] <jaytaoko1> sil2100: ping
[18:01] <jaytaoko1> sil2100: hello
[18:01] <jaytaoko1> didrocks: hello
[18:02] <didrocks> jaytaoko1: hey
[18:03]  * didrocks will never be able to sign off…
[18:03] <jaytaoko1> didrocks: :-D I don't have a question for you. was just saying hi!
[18:04] <didrocks> jaytaoko1: oh, I was getting frightned! I'm running as long as I can then ;)
[18:04] <didrocks> jaytaoko1: see you tomorrow! :)
[18:04] <jaytaoko1> didrocks: cheers
[18:07] <smspillaz> MCR: we don't expose options if we can avoid it
[18:09] <MCR> smspillaz: It is wrong that CCSM is not aware of hardcoded Unity shortcuts at all...
[18:10] <MCR> smspillaz: So no warning is displayed when using these keycombis for other shortcuts (Ctrl+Space, Ctrl+Tab for example)
[18:11] <MCR> smspillaz: Also there are the same shortcuts available in CCSM, which are already hardcoded in Unity, which ofc leads to conflicts
[18:13] <smspillaz> MCR: changing options in ccsm is not exaclty a supported usecase in unity
[18:13] <smspillaz> there's no technical reason for that, it just isn't
[18:14] <MCR> smspillaz: example: You are unable to change the shortcut for the Window Menu (Alt+Space), although the option is there in CCSM <- that is not professional
[18:14] <MCR> smspillaz: It feels like a bad bug when Unity and CCSM do not work together
[18:14] <smspillaz> I suppose some integration there makes sense
[18:19] <sil2100> jaytaoko1: hi!
[18:20] <Mirv> back again
[18:29] <sil2100> jaytaoko1: we're ready for release \o/
[18:29] <sil2100> jaytaoko1: could you help making sure that no one unblocks any merges till Didier gets back and rolls out the release? :)
[18:32] <MCR> smspillaz: I think the main problem is that there exist these "hardcoded" keys, which sometimes (like in the case of the "iron" Alt+Space combi) are double-binded (by CCSM also)
[18:32] <jaytaoko1> sil2100: great! I am sending an email to warn everyone
[18:33] <smspillaz> MCR: we can make them register as readonly options
[18:33] <smspillaz> so that there will be no conflicts
[18:34] <MCR> smspillaz: In that case you would remove functionality from Compiz in the case Unity is turned on ?
[18:35] <smspillaz> MCR: its not removed functionality, it just avoids conflicts
[18:36] <MCR> smspillaz: Imho the correct solution would be to keep sane defaults, but make them fully adjustable via Unity plug-in (like the Alt shortcut for the HUD already has been made)
[18:36] <MCR> smspillaz: no ?
[18:38] <MCR> smspillaz: Otherwise you would have to remove old functionality from Compiz, because you would not be able to use those Unity shortcuts for anything else anymore and it would not be possible to avoid conflicts with software using the same shortcuts by simply changing them in CCSM or elsewhere...
[18:46] <Mirv> seb128: so is the plan to get feedback for the fix committed bugs in https://launchpad.net/unity/+milestone/5.14.0 from the quantal's 6.0 release first?
[18:47] <seb128> Mirv, that's one of the reason we update fixes to the current devel distro first yes
[18:47] <MCR> smspillaz: If we make them read-only Alt+Space would be fixed to show the window menu forever and you could not assign Alt+Button3 (Mouse) to anything else either and you would not be able to use any program that uses Alt+Space in any form (e.g. a game) normally, because it would always bring up the window menu, no matter what...
[18:47] <seb128> but not a blocker
[18:47] <seb128> i.e we don't need to wait on the feedback to start on the SRU
[18:47] <seb128> the feedback will come during the SRU verification time
[18:50] <Mirv> right
[18:51] <smspillaz> MCR: I think making alt-space configurable makes sense considering that it needs to be consistent with the compiz option
[18:52] <smspillaz> MCR: in the other cases the keybinding conflicts are usualy not too bad - the mechanisms in X11 give applications ways to handle that
[18:53] <MCR> smspillaz: Great you agree  :) - if there is no technical reason to have different key options all shortcut::HARDCODED_OPTION should imho be converted to shortcut::COMPIZ_KEY_OPTION (are not that many) - The problem with the hardcoded shortcut is also that it somehow overrides the mouse shortcut as well...
[18:54] <MCR> which means, when Alt+Space is hardcoded, Alt+Button3 (right mousebutton) is also hardcoded for this option somehow - so we would fix multiple problems by getting rid of the hardcoded stuff
[21:51] <MCR> smspillaz: I've tried to create a comprehensive bug report detailing the issue without getting into how to best fix it codewise, but just describing the problems: bug 1022743