[00:59]  * greyback__ waves goodnight, may not be online until later than usual tomorrow
[07:30] <mzanetti> Saviq: do you know the release jenkins didn't stop in a week?
[07:33] <mzanetti> sil2100: hi, good morning.
[07:34] <mzanetti> sil2100: do you know why we are still not releasing unity8? I think the issues in our code/dependencies should be resolved
[07:41] <Saviq> mzanetti, it's running now http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity8/
[07:41] <Saviq> mzanetti, but the checks are failing http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity8/job/cu2d-unity8-head-2.2check/
[07:42] <Saviq> mzanetti, but it looks like a failure of the job
[07:43] <mzanetti> Saviq: hmm... I just found an issue... I may have approved a bad commit last week
[07:44] <Saviq> mzanetti, regardless, the containers fail to start in the release jenkins
[07:44] <mzanetti> ok
[07:44] <Saviq> mzanetti, and I've read about that issue somewhere in my emails yesterday
[07:53] <mzanetti> Saviq: ever used this? https://launchpad.net/bzr-bisect
[07:59] <Saviq> mzanetti, yes, but it doesn't work for me
[07:59] <Saviq> mzanetti, not in any useful way at least
[08:00] <Saviq> Last Modified over a year ago :/
[08:00] <mzanetti> the plugin itself seems to work fine still
[08:00] <mzanetti> the problem is that unity8 doesn't build when going back more than 5 revisions because it doesn't match unity-api any more
[08:01] <mzanetti> but found a good revision that still builds... now it should be useful :)
[08:05] <sil2100> mzanetti: hi!
[08:05] <sil2100> mzanetti: I will try to get it released today, we didn't release anything yesterday since we had some hardware/testing issues...
[08:05] <mzanetti> ah ok. thanks
[08:06] <mzanetti> Saviq: found the bad commit. can I just push a revert to trunk
[08:06] <mzanetti> ?
[08:06] <mzanetti> or want me to go the review path for that too?
[08:07] <Saviq> mzanetti, file a MR and we'll fast-track it through
[08:07] <sil2100> mzanetti: sadly, I don't see in my inbox any notice that it got fixed, but maybe it finally is...
[08:07] <sil2100> Although I see the stacks are generally in a baaad state, with hunderets of FTBFS
[08:08] <mzanetti> can anyone tell me what FTBFS means?
[08:08] <Saviq> mzanetti, Failure To Build From Source
[08:08]  * mzanetti knows FTB as Frontline Testing or Bluetooth
[08:08] <mzanetti> for
[08:08] <mzanetti> :D
[08:11] <mzanetti> Saviq: https://code.launchpad.net/~mzanetti/unity8/revert-r-304/+merge/184733
[08:12] <mzanetti> dandrader: already up?
[08:13] <dandrader> mzanetti, yes! :)
[08:13] <mzanetti> dandrader: dude... anyways, that merge is for you ^
[08:13] <dandrader> mzanetti, that revert thing?
[08:13] <mzanetti> yes
[08:13] <mzanetti> it reverts your last commit
[08:13] <dandrader> ouch
[08:14] <mzanetti> if you know where the issue is, feel free to disapprove the revert and file a new one that fixes the crash
[08:14] <mzanetti> dandrader: but it crashes somewhere in LVWPH
[08:14] <mzanetti> so I figured we should get back to a working state and then try to fix it properly
[08:15] <dandrader> mzanetti, you also have to reopen the related bug
[08:15] <dandrader> once it gets merged
[08:15] <Saviq> already merging
[08:17] <dednick> larsu: ping
[08:19] <larsu> dednick: good morning
[08:19] <dandrader> Saviq, is https://bugs.launchpad.net/touch-preview-images/+bug/1193419 really a critical bug. I'm thinking about lowering its importance
[08:20] <dednick> larsu: howdy. any idea why qmenumodel hasn't done a daily release since the UnityMenuAction index change?
[08:20] <Saviq> dandrader, well, it's a regression and breaks user experience :/
[08:20] <dednick> larsu: i can't put through my messaging branch until that's done.
[08:20] <Saviq> dandrader, and we've had it for too long already...
[08:22] <larsu> dednick: a lot of stuff is on manual publish for some reason. seb128 should know more :)
[08:22] <seb128> yeah, things are on manual landing
[08:22] <seb128> and the lxc containers are screwed due to a kernel bug
[08:22] <seb128> fun week...
[08:23] <larsu> seb128: sigh ... we really need qmenumodel to land
[08:23] <larsu> can somebody do that manually or do we have to wait?
[08:23] <seb128> sil2100, Mirv: ^
[08:23] <seb128> larsu, I would prefer us to push on getting the landing unblocked that start landing components manually
[08:24] <seb128> I want system settings to land, indicator need landing as well, as does hud
[08:25] <larsu> seb128: I can understand. It's just that we want dednick's messging menu branch to land as early as possible to get some exposure before the release
[08:25] <larsu> seb128: do you know when this could be unblocked?
[08:25] <seb128> asac, ^
[08:25] <seb128> asac, we need to get stuff to land again...
[08:29] <mzanetti> dandrader: I reopened this merge and commented how to reproduce the crash: https://code.launchpad.net/~dandrader/unity8/runningApps_lp1193419/+merge/177630
[08:30] <larsu> mzanetti: unity8 CI is again failing because of UNSTABLE tests... https://code.launchpad.net/~larsu/unity8/lp1219057/+merge/184622
[08:30]  * mzanetti checks
[08:30] <larsu> oh wait, commit message is missing as well
[08:30] <larsu> *was* missing
[08:31] <mzanetti> larsu: seems this was a temporary failure because something went wrong while testing on mako
[08:32] <sil2100> larsu: which projects would you need to land?
[08:32] <larsu> mzanetti: can you restart it please?
[08:33] <mzanetti> larsu: sure... do you want permissions on jenkins to be able to restart jobs yourself too?
[08:33] <larsu> sil2100: we decided on waiting for everything to unblock, thanks
[08:34] <mzanetti> larsu: I just saw that you do have those permissions already
[08:35] <mzanetti> anyways, I restarted the job
[08:36] <larsu> mzanetti: ya I do, but I don't have my account data anymore :) (I almost never log in)
[08:36] <larsu> mzanetti: if you can reset my password, that would be nice ;)
[08:36] <mzanetti> larsu: ack
[08:38] <Saviq> nic-doffay, hey, when running gallery.sh in https://code.launchpad.net/~nicolas-doffay/ubuntu-ui-toolkit/multi-selectors/+merge/184735, I get "examples/ubuntu-ui-toolkit-gallery/MultiSelectors.qml: File not found"
[08:39] <seb128> Saviq, hey, wb! had good holidays?
[08:39] <Saviq> seb128, thanks, yeah :)
[08:39] <Saviq> seb128, could use another week to actually rest ;)
[08:39] <seb128> hehe
[08:39] <dandrader> Saviq, that's when you know you had good holidays!
[08:39] <Saviq> dandrader, indeed :)
[08:40] <seb128> Saviq, I know the feeling ;-)
[08:41] <seb128> Saviq, not sure if you did email catchup yet or are still working on it, we discussed the "gsetting key by form factor" but it ended up in "we are not sure that's a good idea/to have a valid usecase for it" ... so we need more input from somebody who has examples ;-)
[08:41] <Saviq> seb128, yeah, still unread in my inbox
[08:42] <seb128> Saviq, no hurry, I was just mentioning it in case it got lost in the middle of the flood ;-)
[08:42] <Saviq> seb128, it was actually surprisingly minor - INBOX was at some 75 emails!
[08:42] <Saviq> obviously there was all the other folders, but still
[08:42] <seb128> yeah, that's decent enough
[08:43] <Saviq> nic-doffay, feeling better, btw?
[08:50] <nic-doffay> Saviq, yeah a little. Good enough to be behind a desk.
[08:57] <Saviq> pstolowski, hey, does the trace in bug #1211595 look anything familiar?
[08:57] <Saviq> prolly not...
[09:01] <nic-doffay> Saviq, how was the time off btw?
[09:01] <Saviq> nic-doffay, awesome, thanks
[09:01] <Saviq> nic-doffay, too short, as usual ;)
[09:14] <pstolowski> Saviq: hi! sorry, had a meeting
[09:14] <Saviq> pstolowski, no worries
[09:14] <Saviq> ooh, nice netsplir
[09:14] <Saviq> t
[09:23] <pstolowski> Saviq: haven't seen this bt before, needs investigation
[09:24] <Saviq> pstolowski, yeah, initially I thought it was happening in Nux, but then read it properly...
[09:37] <pstolowski> Saviq: are you up-to-date with the fixes for category reordering that tsdgeos was working on before he started holidays?
[09:37] <Saviq> pstolowski, he sent me an email, not gotten to it yet
[09:45] <pstolowski> Saviq: ah, ok, good he did send it. no worries, I'm totally busy with other stuff, so this one can wait
[10:48] <seb128> hey qt people, I've a question ... I would like to build a model from cpp to display it in qml
[10:48] <seb128> that's basically a list of icons with a "name/icon/value"
[10:48] <seb128> of items*
[10:48] <seb128> what would you use for that as a type on the cpp side?
[10:49] <seb128> QList<QObject*> ?
[10:49] <seb128> QQmlListProperty?
[10:49]  * seb128 is a bit lost in the google suggestions
[10:58] <dandrader> seb128, yes, I think QQmlListProperty is what you want
[11:04] <Saviq> seb128, yeah, QQLP is the "static list" equivalent of QAbstractListModel
[11:05] <seb128> dandrader, Saviq: thanks, I'm going to look a bit more to that
[11:05] <Saviq> seb128, if you only need a single value - QStringListModel's there, too
[11:05] <seb128> ideally I would need a QList<QMap>
[11:05] <seb128> Saviq, no, I need icon/name/value for each item
[11:07] <Saviq> seb128, well, there is a QVariantListModel floating around
[11:07] <Saviq> seb128, that's a QList<QVariant>
[11:07] <Saviq> +wrapper for
[11:07] <Saviq> seb128, we have it in unity8 and it's there in gsettings-qt
[11:08] <Saviq> seb128, we should probably put it somewhere common (or even push to include in Qt)
[11:09] <seb128> Saviq, that would be good, I'm going to have a look to QQmlListProperty meanwhile
[11:09] <seb128> thanks
[11:30] <larsu> mzanetti: still the same issues with that merge request. Looks like the notification tests are failing, but I can't imagine my patch having an influence on that.
[11:30] <larsu> https://code.launchpad.net/~larsu/unity8/lp1219057/+merge/184622
[11:31] <mzanetti> larsu: I've seen them fail with other branches to
[11:31] <mzanetti> o
[11:31] <larsu> okay, I'm hoping someone will review this despite the CI failure ;)
[11:34] <mzanetti> sure
[11:36] <mzanetti> MacSlow|lunch: ^^
[11:36] <mzanetti> MacSlow|lunch: can you see why the notification tests are failing?
[11:59] <kgunn> greyback: joy?
[12:00] <greyback> kgunn: pretty much everything working (aside from OSK on Mir, which we can fix up after most stuff lands)
[12:00] <kgunn> greyback: osk...meaning rotation?
[12:01] <Saviq> kgunn, on screen keyboard
[12:01] <greyback> kgunn: no, it's not appearing at all for the moment. I've still not figured out why
[12:01] <kgunn> Saviq: thanks...i knew the acronym expansion :)
[12:02] <Saviq> kgunn, d'oh sorry ;)
[12:02] <greyback> suspect that maliit coming up before shell has, so maliit has no display server to conenct to and fails
[12:02] <kgunn> greyback: ah...
[12:03] <kgunn> greyback: not sure that can land tho, i mean, how to connect to password wifi
[12:04] <kgunn> greyback: at least the symbol collision tween qtubuntu & platformapi all sorted ?
[12:04] <greyback> kgunn: yes, that's fixed
[12:06] <greyback> kgunn: yes on the OSK, it will be fixed, but would like to land all the other branches first
[12:11] <kgunn> greyback: got it landing all != creating an image for testing
[12:12] <greyback> kgunn: yep. I've the OSK working with Mir. Just upstart needs tweaking to launch things in the correct order for mir. So it's not a big deal
[12:23] <MacSlow> mzanetti, I will take a look
[12:26] <mzanetti> MacSlow: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-saucy/2725/artifact/unity8.shell.tests.test_notifications.InteractiveNotificationBase.test_sd_incoming_call%20%28Desktop%20Nexus%204%29.ogv
[12:26] <mzanetti> MacSlow: weird... the notification just doesn't show up
[12:26] <mzanetti> it passes locally here
[12:37] <MacSlow> mzanetti, it's "one of those just on Jenkins"-things...
[12:37] <MacSlow> mzanetti, oddly the other notification-tests seem to pass
[12:40] <mzanetti> yes
[12:40] <mzanetti> and yes
[12:41] <MacSlow> mzanetti, I'd not be surprised if another run makes them pass again.
[12:41] <MacSlow> mzanetti, in the videos no bubble shows up at all
[12:41] <mzanetti> MacSlow: it failed on about 5 runs in a row now
[12:41] <mzanetti> always those 2
[12:42] <MacSlow> mzanetti, locally I can't test those as I cannot compile current unity8 trunk... still trying to figure out what's missing on the build-side this time
[12:43] <mzanetti> ???
[12:44] <MacSlow> and I can't commit as qsortfilterproxymodeltest fails upon "bzr commit"
[12:45] <MacSlow> ok.... I can't compile... so I can't commit as it is missing some built tests
[12:46] <MacSlow> mzanetti, or do you know about a missing "unity::shell::launcher::LauncherItemInterface::focusedChanged(bool)" in launcheritem.cpp:144 ?
[12:46] <mzanetti> MacSlow: apt-get upgrade
[12:47] <MacSlow> mzanetti, I tried that of course too... but the package-db is messed up...
[12:47] <MacSlow> mzanetti, this is really not my day
[12:50] <mzanetti> Saviq: btw... the fact that our autopilot tests use the mock plugins is... well, dunno how to put it :D
[12:51] <Saviq> mzanetti, wrong? ;)
[12:51] <mzanetti> ok. lets go with that :D
[12:51] <Saviq> mzanetti, but it's only using mocks for lightdm and applications, no?
[12:52] <mzanetti> no... since the refactor for everything I'm afraid
[12:52] <Saviq> mzanetti, nope
[12:52] <Saviq> mzanetti, see the -fake-env package
[12:53] <mzanetti> hmm... indeed... the launcher uses the real backend
[13:03] <Saviq> Mirv, want to speed up qt build *a lot*? https://lists.ubuntu.com/archives/ubuntu-devel/2013-June/037380.html
[13:13] <Saviq> mzanetti, MacSlow related  http://reports.qa.ubuntu.com/smokeng/saucy/image/4122/unity8-autopilot/ ?
[13:13] <mzanetti> yes... exactly those 2
[13:14] <Saviq> here's something that might possibly help http://people.canonical.com/~ogra/touch-image-stats/20130910.changes
[13:14] <Saviq> the difference in the image between SUCCESS and FAILURE
[13:15] <Saviq> obviously might not be related
[13:15] <mzanetti> ah... git1-notify
[13:15] <Saviq> yeah
[13:15] <MacSlow> Saviq, mzanetti: there's too much going on atm... let me finish one thing first then I turn back to that failure...
[13:16] <mzanetti> MacSlow: I'll take care at that failure... just continue with the SIM pin stuff
[13:16] <MacSlow> mzanetti, ok
[13:16] <MacSlow> mzanetti, thx
[13:21] <Saviq> mzanetti, you're still on libnotify 0.7.5?
[13:21] <mzanetti> Saviq: just doing an upgrade right now
[13:21] <Saviq> mzanetti, yeah, /me runs locally, too
[13:21] <mzanetti> but kde 4.11.1 comes in. takes a little bit :D
[13:22] <Saviq> ;)
[13:23] <Saviq> mzanetti, yeah, failure here on 0.7.6
[13:30] <Saviq> mzanetti, https://git.gnome.org/browse/libnotify/log/
[13:30] <Saviq> mzanetti, seems only one commit that could cause it, really
[13:30] <Saviq> mzanetti, https://git.gnome.org/browse/libnotify/commit/?id=2b4ab4d22f42dd264a4ddfa68b02bba0d6c71b0b
[13:31] <mzanetti> the allow-none probably
[13:31] <mzanetti> dammit... I missed the standup
[13:32] <Saviq> greyback, standup
[13:36] <kgunn> mterry: "kind of almost works"...i'm going to use that
[13:37] <mterry> :)
[13:40] <greyback> Saviq: I didn't quite understand what MR you were doing on Albert's work
[13:40] <Saviq> greyback, https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1217924
[13:40] <greyback> Saviq: gotcha
[13:53] <Saviq> mzanetti, in the fix, please catch TypeError on calling with 6 args and only then call with 5 args, if possible
[13:53] <Saviq> mzanetti, i.e. support both, 'cause we need to revert the libnotify fix for a bit
[13:53] <Saviq> but then reintroduce it
[13:53] <mzanetti> ok
[13:54] <mzanetti> anyone knows why unity8 needs 20 secs for starting up lately?
[13:54] <Saviq> mzanetti, sounds like a service is blocking
[13:54] <Saviq> mzanetti, hud?
[13:54] <Saviq> mzanetti, mine starts straight away
[13:55] <mzanetti> yeah... hud sounds reasonable
[13:56] <greyback> yep hud
[13:56] <dandrader> mzanetti, I always had it after I dist-upgraded my desktop and some hud-related thing got updated. rebooting "solved" it
[14:06] <nic-doffay> Saviq, what do you make of the last few comments here? https://code.launchpad.net/~nicolas-doffay/unity8/filter-selector/+merge/183503
[14:06] <nic-doffay> I've been trying to get to the bottom of this issue to no avail.
[14:07] <Saviq> nic-doffay, let me restart the job there
[14:07] <Saviq> ah actually it's 1 hr old
[14:07]  * Saviq looks through
[14:08] <Saviq> nic-doffay, https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-saucy/2728/testReport/junit/unity8.shell.tests.test_notifications/EphemeralNotificationsTests/test_summary_and_body_Desktop_Nexus_4_/ looks weird
[14:10] <Saviq> nic-doffay, and I can reproduce locally
[14:12] <nic-doffay> Saviq, sorry meant to specify not jenkins, the comments about tryCompare.
[14:13] <Saviq> nic-doffay, yeah, but still... where does the Popover failure come from..
[14:13] <Saviq> nic-doffay, ah, you removed "import Ubuntu.Components.Popups 0.1"
[14:14] <Saviq> nic-doffay, I expect one of them to be strins
[14:14] <Saviq> strings
[14:15] <Saviq> nic-doffay, i.e. "true" != true, but print(true) == print("true")
[14:15] <Saviq> nic-doffay, that's why the message isn't helpful
[14:17] <Saviq> nic-doffay, but regardless, I get quite a bit of errors http://pastebin.ubuntu.com/6088153/ and dash doesn't work at all
[14:17] <nic-doffay> Saviq, you're right about that. Still busy with the other issue.
[14:19] <nic-doffay> Saviq, got it, checking out the interactive issue now.
[14:22] <nic-doffay> Saviq, those are fixed. If you don't mind having a look yourself in a while and give your thoughts it would be appreciated.
[14:22] <Saviq> nic-doffay, cheers
[14:23] <nic-doffay> Saviq, still sorting out the tests though.
[14:23] <nic-doffay> But feel free to comment on the rest.
[14:23] <Saviq> nic-doffay, my review might not happen, though, I'm travelling starting Thusrday, back on Monday the 23rd :/
[14:23] <Saviq> nic-doffay, I'll do a functional review, though
[14:24] <Saviq> (for work, that is, not going back on holiday already!)
[14:26] <Saviq> nic-doffay, changing the filters doesn't seem to do anything, that expected?
[14:28] <Saviq> nic-doffay, there's some weird issue with the option selector, too - when I select, the 2nd (or latter) option and reopen the selector, it scrolls up 1/2 of item height
[14:28] <nic-doffay> pstolowski, ^ do you still have an unmerged branch in trunk by any chance?
[14:28] <nic-doffay> Saviq, yeah those issues with the selector have been solved in a branch which landed this morning.
[14:28] <nic-doffay> in the sdk
[14:28] <Saviq> nic-doffay, ah ok, let me try with that, the
[14:28] <Saviq> n
[14:29] <pstolowski> nic-doffay: no, nothing re filters
[14:29] <nic-doffay> pstolowski, any idea about what Saviq mentioned above?
[14:30] <Saviq> nic-doffay, nope, the "scrolls half way up" is still there
[14:30] <Saviq> nic-doffay, it's not visible in the gallery, 'cause the selectors there always show all the items
[14:31] <nic-doffay> Oh Saviq
[14:31] <nic-doffay> The scrolls half way up isn't a bug.
[14:31] <nic-doffay> Design requested that.
[14:31] <pstolowski> nic-doffay: nope.. it worked last time I integrated and tested our branches ~2 weeks ago
[14:31] <nic-doffay> So the user knows you are able to scroll.
[14:31] <Saviq> nic-doffay, yikes...
[14:32] <nic-doffay> pstolowski, mind merging my branch and checking again?
[14:32] <nic-doffay> Saviq, yeah.
[14:32] <pstolowski> nic-doffay: sure, will do
[14:33] <nic-doffay> pstolowski, cheers.
[14:33] <nic-doffay> pstolowski, nothing has changed re that on the UI end which is why I'm confused.
[14:34] <pstolowski> nic-doffay: I see, weird.. but it definately worked at some point after fixing activation issue on my side
[14:35] <pstolowski> nic-doffay: do I still need that experimental sdk branch, or it's all merged?
[14:35] <nic-doffay> pstolowski, 488 on PageHeader is where the action happens.
[14:35] <nic-doffay> I don't think it's changed since we spoke about it last.
[14:35] <nic-doffay> That is PageHeader.qml
[14:38] <mhr3> sil2100, any eta on when libunity & co might land?
[14:38] <mhr3> cc mfisch ^
[14:38] <mfisch> cwayne / ssweeny: this is what we're waiting on ^^^
[14:38] <nic-doffay> pstolowski, I think it's been merged.
[14:39] <ssweeny> mfisch, ack
[14:39] <sil2100> mhr3: hm, once we finally get a working daily-release tick!
[14:42] <mzanetti> dandrader: fixed
[14:42] <Saviq> nic-doffay, my functional comments https://code.launchpad.net/~nicolas-doffay/unity8/filter-selector/+merge/183503/comments/419957
[14:42] <mhr3> sil2100, what's blocking it?
[14:43] <sil2100> mhr3: strange machinery issues - first we had a broken kernel with aufs problems, now we seem to be getting network errors on jenkins on the prepare jobs all the time
[14:43] <dandrader> mzanetti, approved
[14:46] <pstolowski> nic-doffay: I remember I mentioned one bug to you last time we talked, where a string such as "OptionSelector_QMLTYPE_133(0x1ea4120)" was passed to setActive instead of actual option id or index; have you spotted it?
[14:47] <mzanetti> Saviq: can you do that fix please... my python skills are not good enough
[14:47] <Saviq> mzanetti, sure, doing
[14:48] <mzanetti> Saviq: unity8/shell/emulators/create_interactive_notification.py
[14:48] <mzanetti> Saviq: line 91
[14:48] <mzanetti> Saviq: there's a None, but must be some GLib crap
[14:48] <mzanetti> GLib.DestroyNotify
[14:49] <mzanetti> whatever that is
[14:50] <mhr3> sil2100, sounds like fun :P
[14:51] <sil2100> mhr3: it *might* be resolved now, since I checked on one stack and it was fine, so I spinned the machinery now
[14:52] <nic-doffay> Saviq, commented again. Mind elaborating on the expansion pattern going to almost full height?
[14:52] <sil2100> mhr3: btw. ;) libunity changes that you want to release... do you have bugfixes there, or features? Is there an FFe for that? Since the touch FFe sadly doesn't have libunity mentioned
[14:52] <nic-doffay> Saviq, my do you mean the OptionSelector should scroll when it's expanded?
[14:52] <sil2100> And in the end Steve didn't want a discussion about the common desktop-touch components FFe
[14:52] <Saviq> nic-doffay, see what the dash does when you tap on section headers
[14:52] <mhr3> sil2100, we have scope-specific ffe for touch changes
[14:53] <mhr3> sil2100, although it's not linked from the branches
[14:53] <Saviq> nic-doffay, something similar needs to happen with the option selectors, too
[14:54] <mhr3> sil2100, #1215397
[14:54] <nic-doffay> Saviq, it just displays an additional row, correct?
[14:56] <nic-doffay> Saviq, should it scroll the contents to about half way?
[14:56] <Saviq> nic-doffay, not the *content* of the option selector
[14:56] <Saviq> nic-doffay, but the *view* in which the option selector is
[14:56] <Saviq> nic-doffay, should scroll to allow the option selector to expand to maximum needed
[14:57] <Saviq> or start scrolling inside
[14:57] <nic-doffay> Saviq, ah I see.
[14:57] <Saviq> nic-doffay, https://docs.google.com/a/canonical.com/document/d/1_c4029C6Jwll_ng8gqp3SRnF4DgXRA3tR_LL3J-zOD8/edit
[14:57] <Saviq> https://docs.google.com/a/canonical.com/document/d/1XigSp8dsW0gcL8xUkrDytm18qAyiXOXXdSaF3CWtNVg/edit#heading=h.cpfn81n0c0rr
[14:57] <Saviq> nic-doffay, we discussed this earlier - there needs to be a Container and a Expandable base ListItem
[14:58] <Saviq> nic-doffay, that work together to implement that behaviour
[14:58] <Saviq> and OptionSelector would be an Expandable
[14:59] <Saviq> mzanetti, you overengineered ;) https://code.launchpad.net/~saviq/unity8/fix-new-libnotify/+merge/184799
[14:59] <pstolowski> nic-doffay: ok I see the problem
[14:59] <pstolowski> nic-doffay: setActive recieves false all the time when you call it
[15:00] <Saviq> mzanetti, although that fix is actually conflicting with what is said in https://git.gnome.org/browse/libnotify/commit/?id=2b4ab4d22f42dd264a4ddfa68b02bba0d6c71b0b
[15:00] <Saviq> seb128, ↑ says the *count* of arguments didn't change, but their type did
[15:00] <Saviq> seb128, but the error said there was an incorrect number of arguments
[15:01] <Saviq> seb128, and https://code.launchpad.net/~saviq/unity8/fix-new-libnotify/+merge/184799 fixes, but seems in conflict with what the git commit did?
[15:01] <pstolowski> nic-doffay: also, judging from the behavior (options are activated anyway in the ui), it seems that ui is still "disconnected" from the backend, i.e. it keeps track of active option by itself rather than relying on the model as discussed earlier
[15:02] <nic-doffay> pstolowski, see line 18
[15:02] <nic-doffay> http://pastebin.ubuntu.com/6088350/
[15:02] <nic-doffay> !active should access the role.
[15:02] <seb128> Saviq, yeah, I don't understand why the count changed, I'm trying to get hold of pitti but he's in Lexington for the QA sprint and not around
[15:03] <Saviq> seb128, to me it suggests the git commit is wrong, TBH
[15:03] <seb128> Saviq, to me is suggest that gir is <censured> :p
[15:03] <Saviq> seb128, as it will break uses that *do* want callback to destroy user data
[15:04] <seb128> Saviq, anyway, I reverted the commit and intend to keep it this way until I sort it out with pitti, that's likely to create issue for any code using that api
[15:04] <nic-doffay> pstolowski, forget it I think I know what it is.
[15:04] <pstolowski> nic-doffay: hmm, indeed. but I added debug in setActive, and it's definately getting 'false' all the time
[15:04] <Saviq> seb128, ok, I'll put the !fix on hold until then
[15:04] <Saviq> mzanetti, ignore the merge for now
[15:04] <Saviq> mzanetti, seems the issue might be in libunity in the end
[15:04] <pstolowski> nic-doffay: I'll add comments to the MP
[15:04] <mzanetti> Saviq: wait...
[15:05] <Saviq> mzanetti, we reverted libnotify
[15:05] <Saviq> mzanetti, so there's no need to fix it on our side
[15:05] <mzanetti> removing that argument makes it compile?
[15:05] <Saviq> mzanetti, yes, that's the thing
[15:05] <mzanetti> python sucks
[15:05] <Saviq> mzanetti, not python
[15:05] <mzanetti> like really
[15:05] <Saviq> mzanetti, and not compile
[15:05] <nic-doffay> pstolowski, just pushed something.
[15:05] <Saviq> mzanetti, gir
[15:05] <nic-doffay> I think it should work now...
[15:06] <mzanetti> Saviq: anyways... ping me when I should "review"
[15:06] <Saviq> mzanetti, probably never
[15:07] <seb128> Saviq, opened https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1223401 for tracking
[15:08] <Saviq> seb128, thanks
[15:09] <nic-doffay> pstolowski, let me know if the new push sorted it.
[15:11] <nic-doffay> pstolowski, regarding the ui disconnection.
[15:11] <nic-doffay> This is what happens.
[15:11] <nic-doffay> !active is gotten from the role.
[15:11] <nic-doffay> And passed straight into the backend when a delegate is clicked.
[15:11] <nic-doffay> pstolowski, is this incorrect in your opinion?
[15:12] <pstolowski> nic-doffay: yes, this is fine  but still, the option is selected in the ui even though it wasn't selected in the backend
[15:14] <nic-doffay> pstolowski, is there a way to get the selected index from the backend?
[15:14] <nic-doffay> pstolowski, like getActiveIndex or whatever
[15:15] <pstolowski> nic-doffay: it didn't help
[15:15] <nic-doffay> pstolowski, ?
[15:15] <pstolowski> nic-doffay: there isn't. do you need it because of the sdk?
[15:16] <nic-doffay> pstolowski, yeah.
[15:16] <nic-doffay> pstolowski, I'd need to bind it to the selectedIndex.
[15:16] <nic-doffay> of the OptionSelector.
[15:16] <nic-doffay> pstolowski, no clue why that isn't working now.
[15:16] <nic-doffay> What I'm doing is passing the index which is being selected and the !active
[15:17] <nic-doffay> pstolowski, that sounds right?
[15:17] <pstolowski> nic-doffay: indeed, it looks sensible.. but I'm still getting false
[15:19] <nic-doffay> pstolowski, I'll have to do some digging.
[15:23] <Saviq> kgunn, ping
[15:24] <kgunn> Saviq: pong
[15:44] <tedg> mhr3, Do you guys have a plan to port the application lens over to using upstart-app-launch?
[15:45] <mhr3> tedg, apps lens doesn't run apps
[15:45] <mhr3> unity does
[15:45] <Saviq> tedg, unity will do that
[15:45] <tedg> mhr3, ?  What happens when, after install, I click on "Open"?
[15:46] <tedg> I guess that's the click lens
[15:46] <mhr3> right
[15:46] <Saviq> tedg, unity sends the "activate" signal to the scope, and it should come back with *shrug*
[15:46] <mhr3> and it still won't try to run it
[15:46] <Saviq> tedg, and that's when unity takes over again and activates itself via app manager
[15:46] <Saviq> tedg, which, in turn, will use upstart
[15:47] <tedg> Ah, okay.  I didn't realize.
[15:47] <tedg> I thought the scope activated the app at that point.
[15:47] <Saviq> tedg, all the activation stuff moves towards Unity at this point (with some exceptions), as remote scopes can't do zilch
[15:48] <tedg> I think that about remote scopes too :-)
[15:48] <mhr3> of course they can... but on the server
[15:48] <mhr3> which isn't that useful :P
[15:49] <tedg> I just don't see that many publicly available and anonymous sources that I want to search other than Wikipedia/Google
[15:53] <nic-doffay> mzanetti, ping
[16:06] <davmor2> Hey guys who is the best person to talk to about apps in the launcher not launching anything?
[16:08] <mzanetti> hey nic-doffay, what up?
[16:11] <ChrisTownsend> davmor2: For Unity7 or Unity8?
[16:11] <davmor2> ChrisTownsend: Unity7
[16:11] <ChrisTownsend> davmor2: Is this for newly installed apps from the Software Center or just in general?
[16:12] <davmor2> ChrisTownsend: newly installed commercial apps.  They icon appears in the launcher click it nothing,  open the dash search for it there and click it and it launches
[16:13] <nic-doffay> mzanetti, remember the test issue I was having with the filters?
[16:14] <ChrisTownsend> davmor2: Hmm, how is the app being installed?  I'm asking because https://bugs.launchpad.net/software-center/+bug/1221349 is very similar to the behavior you're describing.
[16:15] <mzanetti> nic-doffay: which one? :)
[16:15] <davmor2> ChrisTownsend: yeap that looks like it exactly infact :(
[16:16] <nic-doffay> mzanetti, http://pastebin.ubuntu.com/6088637/
[16:16] <ChrisTownsend> davmor2: Ok, well, we are waiting on an updated Software Center:)
[16:16] <nic-doffay> This still fails.
[16:16] <nic-doffay> When checking for expanded.
[16:16] <mzanetti> right
[16:16] <nic-doffay> mzanetti, any insights as to why?
[16:17] <davmor2> ChrisTownsend: ah okay that I can chase and I know just the man to annoy ;)
[16:17] <ChrisTownsend> davmor2: Great!  Thanks!
[16:21] <mzanetti> nic-doffay: I'm trying to run it but I get a compile error again
[16:22] <mzanetti> nic-doffay: ah ok. it runs now
[16:22] <nic-doffay> mzanetti, what's the compile error?
[16:22] <nic-doffay> nm
[16:23] <cwayne> mzanetti: nic-doffay: so are decided on doing a config file for the infographic colors?
[16:24] <nic-doffay> cwayne, I believe pete-woods was talking to someone about that the other day?
[16:25] <cwayne> there was an email thread, it seemed like the end was to do a config file
[16:25] <nic-doffay> cwayne, unfortunately I've heard nothing about that.
[16:25] <mzanetti> cwayne: I'm not sure about that
[16:26] <mzanetti> cwayne: you're right
[16:38] <veebers> mzanetti: ping?
[16:40] <cwayne> mzanetti: would that be easy to implement?
[16:41] <mzanetti> veebers: 10 mins
[16:41] <veebers> mzanetti: ack
[16:41] <mzanetti> cwayne: I think so, yes
[16:41] <mzanetti> cwayne: check Shell.qml and search for GSettings
[16:46] <mzanetti> nic-doffay: http://paste.kde.org/p0bbdb005
[16:47] <mzanetti> nic-doffay: also, you need to add objectName: "searchHeader" to the Flickable with id "header" in PageHeader.qml
[16:47] <mzanetti> veebers: hi
[16:48] <veebers> mzanetti: hey how are things? o/ I have a question for you
[16:49] <mzanetti> good, thanks
[16:49] <mzanetti> tell me
[16:49] <nic-doffay> mzanetti, ah so it had nothing to do with the searchField then.
[16:49] <mzanetti> nic-doffay: yes it does
[16:49] <veebers> mzanetti:  I want (well I want to help someone) to run this command successful: qmlscene Dash/Apps/AppPreview.qml
[16:49] <mzanetti> nic-doffay: if you start the pageHeader you'll notice that the searchField slides in from the above
[16:50] <mzanetti> nic-doffay: but the thing that actually does the sliding is the Flickable around it
[16:50] <mzanetti> nic-doffay: so I checked that to reach the target position
[16:50] <veebers> mzanetti: is that possible? this is for testing (and mocking maybe required, just feeling that out at the moment)
[16:51] <mzanetti> veebers: ./build && cd builddir && make tryAppPreview
[16:52] <mzanetti> bbi 5 mins
[17:01] <kgunn> mterry: mir-on-mir input working as of a moment ago...growing confidence in killing 3 week claim cycle :)
[17:01] <mterry> kgunn, :)
[17:02] <mzanetti> veebers: does that work for you?
[17:49] <greyback> mzanetti: was there any progress fixing those 2 failing notifications AP tests?
[17:49] <mzanetti> Saviq: ^
[17:49] <veebers> mzanetti: sorry was afk, trying now thanks
[17:50] <Saviq> greyback, mzanetti, the libnotify change is reverted
[17:50] <greyback> ricmm: ^^
[17:50] <mzanetti> :D
[17:50] <Saviq> greyback, mzanetti so assuming it installs https://launchpad.net/ubuntu/+source/libnotify/0.7.6-1ubuntu1
[17:50] <Saviq> all should be good
[17:50] <Saviq> but it might not have propagated yet
[17:50] <greyback> Saviq: yeah, seems it hasn't yet
[17:51] <Saviq> bug #1223401 tracks the issue
[17:52] <ricmm> sil2100: ping
[17:52] <ricmm> sil2100: ^^^ thats causing the mediumtests failures
[17:52] <ricmm> will need latest libnotify in place for it to work
[17:57] <sil2100> libnotify...
[17:57] <sil2100> We're not daily-releasing that now do we
[17:58] <Saviq> sil2100, no
[17:58] <Saviq> sil2100, there was a crasher in it that got fixed upstream
[17:58] <sil2100> Ok, but it's in the archive, so I guess it should be fetchable? Did you do a direct depends on that?
[17:58] <Saviq> sil2100, but that changed GI API
[17:58] <sil2100> On that specific version? greyback ?
[17:59] <Saviq> sil2100, the fixed version isn't there yet (at least not in my archive)
[17:59] <greyback> sil2100: according to Saviq, yes
[17:59] <Saviq> greyback, sil2100, no, we're not depending on the specific version
[17:59] <sil2100> Maybe we should? As otherwise things are broken, at least the tests, right?
[18:00] <greyback> we just want the fixed version being used to run AP tests against
[18:00] <Saviq> sil2100, the fixed one is not available in the archive yet (not from here at least)
[18:00] <Saviq> http://paste.ubuntu.com/6089049/
[18:01] <ricmm> so lets push it to the archive
[18:01] <ricmm> manually or whatever
[18:01] <ricmm> (:
[18:03] <Saviq> ricmm, ;)
[18:03] <Saviq> sil2100, btw, I recommend https://lists.ubuntu.com/archives/ubuntu-devel/2013-June/037380.html
[18:11] <sil2100> Saviq, ricmm: ok, I think I'll have to EOD pretty soon - could you guys make sure that the unity8 merge gets in (i.e. CI allows for it) and drop me an e-mail about that? I will then know what's up and copy the binaries for testing in my UTC morning
[18:11] <sil2100> ricmm: if you could also point to the PPA you wish to use for testing
[18:26] <ricmm> sil2100: right, is there anyone state-side that can help us with that copy or whatever?
[18:26] <ricmm> if its a binary copy from daily-build we can do that ourselves
[18:29] <sil2100> ricmm: yeah, I guess robru or kenvandine might be able to help, they would have to run the unity8 stack and make sure it's built with the merged in change from greyback
[18:31] <sil2100> ricmm: I'll update them just in case, just make sure that merge gets in from your side
[18:32] <ricmm> yup
[18:32] <ricmm> wheres libnotify at, published yet?
[18:35] <greyback> sil2100: thanks. let us know which person we should talk to
[18:35]  * greyback going afk for 45 mins
[18:36] <Saviq> ricmm, it's published, yes, but doesn't seem to have propagated to archives yet
[18:37] <ricmm> Saviq: ok! we'll wait
[18:37] <ricmm> whats the version we are expecting?
[18:43] <Saviq> ricmm, https://launchpad.net/ubuntu/+source/libnotify/0.7.6-1ubuntu1
[18:52] <ricmm> Saviq: I see it now in the archive, will re-run autolanding
[18:53] <ricmm> rerunning ci
[18:57] <Saviq> still 0.7.6-1 here :/
[18:59] <ricmm> Candidate: 0.7.6-1ubuntu1
[18:59] <ricmm> you probably have a weird mirror
[18:59] <ricmm> polishone
[19:33] <ricmm> Saviq: http://10.97.2.10:8080/job/unity-phablet-qmluitests-saucy/1647/console
[19:33] <ricmm> :(
[19:34] <ricmm> not sure what the error there is
[19:35] <ricmm> ah shit
[19:36] <ricmm> why is it running against trunk and not my branch?
[19:41] <Saviq> ricmm, I'm actually using a.u.com, but it might be tricking me into using some mirror instead (or well, I'm using apt-cacher-ng, which might be the cause, too)
[19:42] <ricmm> testShell is failing in jenkins against the branch
[19:42] <ricmm> but it works fine here
[19:42] <ricmm> the failure is the same one that we fixed two nights ago, so I dont know whats going on
[19:42] <ricmm> is it possible thats its picking up the wrong code? gee
[19:43] <ricmm> fginther: can you help me out with this one?
[19:45] <Saviq> ricmm, fails here
[19:45] <ricmm> on your desktop?
[19:46] <Saviq> ricmm, yes
[19:46] <Saviq> make -C builddir testShell yields the exact same failure
[19:47] <Saviq> ricmm, and if you make -C builddir tryShell
[19:47] <Saviq> ricmm, unlock and launch app from launcher, it disappears after 2s or so
[19:47] <ricmm> works just fine for me
[19:48] <ricmm> again, works fine for me
[19:48] <ricmm> and this is the same issue we were seeing before
[19:48] <ricmm> if you read the comments you'll see it and then everyone signin off on it having been fixed
[19:48] <Saviq> ricmm, and where was this fixed?
[19:48] <Saviq> ricmm, in that branch?
[19:48] <ricmm> yes
[19:48] <Saviq> ricmm, or maybe in unity-api?
[19:49] <ricmm> I think it was in this branch
[19:49] <ricmm> but I could be wrong, I rememebr stuff going into unity-api
[19:49] <ricmm> and me having to install it at some point
[19:49] <Saviq> ricmm, https://code.launchpad.net/~unity-team/unity-api/trunk wasn't released yet
[19:49] <Saviq> the last revision there
[19:49] <ricmm> can you build trunk and check if it fixes your thing?
[19:50]  * Saviq builds
[19:56] <Saviq> ricmm, no, same failure
[19:59] <greyback> hey
[19:59] <ricmm> hey
[19:59] <Saviq> greyback, FAIL!  : qmltestrunner::Shell::test_rightEdgeDrag() property visible
[19:59] <Saviq>    Actual   (): true
[19:59] <Saviq>    Expected (): false
[19:59] <Saviq>    Loc: [/home/michal/dev/canonical/unity8/repo/tests/qmltests/tst_Shell.qml(249)]
[19:59] <Saviq> FAIL!  : qmltestrunner::Shell::test_suspend() property visible
[19:59] <Saviq>    Actual   (): true
[19:59] <Saviq>    Expected (): false
[19:59] <Saviq>    Loc: [/home/michal/dev/canonical/unity8/repo/tests/qmltests/tst_Shell.qml(249)]
[19:59] <ricmm> same old error
[20:00] <ricmm> but I just branched and built and ran it and no error
[20:00] <greyback> Saviq: you can repro on your laptop?
[20:00] <Saviq> greyback, yes
[20:00] <Saviq> greyback, just built lp:unity-api trunk, thought it'd help, but same thing
[20:00] <ricmm> was there a pre-req to this?
[20:00] <greyback> Saviq: same error?
[20:00] <Saviq> greyback, yes
[20:01] <greyback> Saviq: did you rebuild unity8 after?
[20:01] <Saviq> greyback, no
[20:01] <Saviq> right
[20:01] <Saviq> doing
[20:02]  * Saviq wonders if we should actually build a lib from unity-api
[20:02] <Saviq> as otherwise that's going to happen
[20:02] <Saviq> unless cmake notices the change? maybe it does...
[20:03] <Saviq> greyback, works
[20:03] <greyback> it wouldn't make a difference. the interface header is defining a Q_ENUM. But moc is only run on that interface header in unity-api/qtubuntu
[20:03] <Saviq> ricmm, yeah, we need to release unity-api
[20:04] <greyback> ricmm: Saviq ok glad that's sorted. unity-api needs release first
[20:05] <ricmm> phew
[20:05] <ricmm> kenvandine: can you help us with this one please?
[20:07] <kenvandine> ricmm, sure
[20:08] <kenvandine> ricmm, so a build of the unity8 stack?
[20:08] <ricmm> need a release of unity-api, that one can go all the way to the archive
[20:08] <ricmm> yes, I guess
[20:08] <ricmm> except that unity-mir and qtubuntu cannot publish to the archive
[20:08] <ricmm> we are holding those for the larger Mir landing strategy
[20:11] <kenvandine> ricmm, i started it
[20:11] <kenvandine> ricmm, however, we can't just publish that one to the archive
[20:11] <kenvandine> but it'll build in the ppa
[20:14] <ricmm> ok, thats good enough
[20:14] <ricmm> all we need is the ci to pass so that unity8 will land
[20:14] <ricmm> we will test from ppa, get the green from asac and publish
[20:15] <Saviq> kenvandine, ricmm well... unity-api is in the unity8 stack... so it should be in the local upstream merger repo, no?
[20:16] <ricmm> it will be yes
[20:16] <Saviq> ricmm, it already should, since it's autolanded?
[20:16] <kenvandine> Saviq, should be
[20:17] <Saviq> but doesn't seem to be:
[20:17] <Saviq> saucy/universe libunity-api-dev amd64 7.80.3+13.10.20130905.2-0ubuntu1
[20:17] <Saviq> unless! qmluitests isn't using the repo?
[20:19] <Saviq> kenvandine, yes, I think that's the case
[20:19] <Saviq> since http://10.97.2.10:8080/job/generic-mediumtests-builder-saucy-i386/3265/consoleFull picked up:
[20:20] <Saviq> libunity-api-dev_7.80.3+13.10.20130905.2bzr103pkg0saucy0_i386.deb
[20:21] <Saviq> hmm D00mbs_archive is in the hooks for qmluitests
[20:23] <Saviq> hmm!
[20:24] <Saviq> mbs_archive does not have amd64 builds
[20:24] <Saviq> and qmluitests is running under amd64
[20:24] <Saviq> fginther, ↑
[20:24] <Saviq> kenvandine, ↑
[20:24] <Saviq> that's our inherent issue, I'd say
[20:26] <dednick> night all!
[20:28] <kenvandine> fginther, ping
[20:30] <kenvandine> Saviq, it looks like it only has a configuration for saucy-armhf
[20:30] <Saviq> kenvandine, it must have for i386, too, as libunity-api-dev_7.80.3+13.10.20130905.2bzr103pkg0saucy0_i386.deb was tjere
[20:30] <Saviq> there
[20:30] <kenvandine> although the ci_default does have i386
[20:31] <ricmm> hmmm
[20:31] <kenvandine> we need fginther to look at it
[20:31] <ricmm> fginther:
[20:31] <ricmm> I'll go ping him in person
[20:31] <ricmm> I tihnk hes still around
[20:31] <ricmm> but I need to drop for a bit
[20:34] <Saviq> kenvandine, ricmm, either way if we run/release the stack now
[20:34] <Saviq> we'll be able to merge the branch in question and rerun/rerelase the stack, as we probably won't put unity-api amd64 in the mbs archive no way
[20:40] <ricmm> Saviq: we cant release the stack, publishing is off
[20:40] <ricmm> francis is fixing the issue, already spotted
[20:40] <ricmm> will be up and re-running soon
[20:40] <ricmm> with a green result
[20:41] <ricmm> and I'll top approve when I get back
[20:41] <ricmm> ok?
[20:41] <Saviq> sure
[20:41] <ricmm> bbiab
[20:41] <kenvandine> great
[20:41] <kenvandine> thx
[20:41] <ricmm> or you can if you see the green jenkins :)
[20:41] <Saviq> ricmm, green daily release?
[20:41] <Saviq> ricmm, or green upstream?
[21:03] <ricmm> Saviq: green autolanding on unity8
[21:03] <greyback_> \o/
[21:03] <ricmm> no I mean when we have a green autolanding
[21:03] <Saviq> greyback_, that wasn't a statement ;)
[21:03] <Saviq> ricmm, nothing is running there, though?
[21:04] <greyback_> gah
[21:04] <ricmm> Saviq: unity8 ci is running right now
[21:04] <Saviq> ricmm, k
[21:04] <ricmm> but I dont care about that CI, will top approve, autolanding runs the same stack
[21:05] <ricmm> because we need to leave the office now
[21:05] <ricmm> traffic
[21:05] <Saviq> o./
[21:12] <cyphermox> greyback_: poke
[21:12] <cyphermox> you watching your merge? seems like there are some test failures
[21:12] <cyphermox> ricmm: ^
[21:12] <greyback_> cyphermox: which one?
[21:12] <kgunn> ug!
[21:12] <cyphermox> https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/1647/testReport/
[21:13] <cyphermox> https://code.launchpad.net/~gerboland/unity8/u8-newAppAPI2/+merge/184194
[21:13] <greyback_> cyphermox: fix for that is an updated unity-api being used.
[21:14] <cyphermox> ok, so it would be ready for a stack rerun then?
[21:19] <greyback_> cyphermox: the newer unity-api has landed in the daily-build ppa, so yes it should be ready. Think a CI run is going on that unity8 branch now
[21:22] <cyphermox> mmkay
[21:22] <cyphermox> what branch is that?
[21:23] <cyphermox> there should be a rerun of faily-release stuff in some 37 minutes or so
[21:23] <greyback_> same branch
[21:35] <fginther> ricmm, Saviq, the rebuild worked
[21:36] <asac> greyback_: hey
[21:37] <greyback_> asac: hi
[21:37] <asac> greyback_: do you know exactly what branches/packages should go in for unity8/mir landing?
[21:37] <greyback_> asac: https://docs.google.com/a/canonical.com/document/d/1wpeC8WLHJ6yn4YCYiJlAhD71HPugBMq80Xnmm99fhCI/edit#
[21:38] <asac> greyback_: so: unity-api, qtubuntu, unity-mir, unity8, [ubuntu-touch-session] ?
[21:38] <greyback_> asac: yes
[21:38] <asac> greyback_: hard to parse that documnet... what do we need to build first?
[21:38] <greyback_> the ubuntu-touch-session update is not critical, but would fix OSK on Mir, so pretty nice
[21:39] <asac> kk
[21:39] <asac> greyback_: so what needs what to build there?
[21:39] <greyback_> asac: we're in phase 1.
[21:39] <asac> ok so we land unity-api and qtubuntu
[21:39] <asac> wait till that is finished
[21:40] <asac> and then build unity8 and unity-mir?
[21:40] <asac> s/land/build/
[21:40] <greyback_> asac: unity-api, unity-mir and qtubuntu have been built and are in the daily-release ppa. unity8 is being built now
[21:40] <asac> greyback_: really?
[21:41] <asac> wow... didrocks believe nothing worked :)
[21:41] <asac> didrocks: ^^
[21:41] <kgunn> :)
[21:41] <greyback_> asac: sorry, I meant daily-build ppa
[21:42] <asac> greyback_: no mir update?
[21:43] <kgunn> asac: mir is already in saucy
[21:43] <greyback_> asac: mir itself, none needed for us
[21:43] <asac> kgunn: the latest?
[21:43] <kgunn> asac: yep all good
[21:43] <asac> didrocks says that its technically not easy to decouple
[21:43] <asac> seems he will sort it :)
[21:43] <asac> robert_ancell: ^^
[21:43] <kgunn> asac: once unity8 finishes...will we then create an image from those ppa's ?
[21:44] <asac> robert_ancell: can you please tell us what exactly what to do
[21:44] <asac> robert_ancell: seems you tlakeda bout something else that you want mir to land for etc.
[21:44] <asac> i would really like to keep this as precise and untangled as possible
[21:44] <kgunn> robert_ancell: context unity8-mir
[21:45] <robert_ancell> Can someone phrase this in a question? Not 100% sure what you're asking from the scrollback
[21:45] <asac> robert_ancell: i want to know the minimal stuff to land to get unity8-mir landed
[21:45] <robert_ancell> asac, the lastest mir?
[21:45] <asac> at best without anything that can cause unrelated sideeffects
[21:45] <greyback_> kgunn: we need more branches to land before an image would have working unity8-on-mir
[21:45] <asac> kgunn: can you help robert_ancell to understand what you want to land :)?
[21:46] <robert_ancell> asac, you can't really - unless you can cherry pick in a commit.
[21:46] <greyback_> asac: the current mir that's published is suffucient for unity8-on-mir
[21:46] <kgunn> robert_ancell: can you confirm mir needs nothing else other than the mir that's in main is needed
[21:46] <kgunn> right...i agree w/ greyback_
[21:46] <didrocks> greyback_: can you give me in addition to the list you tested exactly what version was tested
[21:46] <kgunn> what's in archive should be enough
[21:46] <didrocks> so that I can force those to be in
[21:47] <robert_ancell> kgunn, do you mean xmir / u-s-c?
[21:47] <didrocks> robert_ancell: we are talking about unity8 on Mir
[21:47] <robert_ancell> didrocks, right, and you need a version in main that's ahead of what's there right?
[21:47]  * asac tries to call ricmm
[21:47] <asac> he is of to a stadium
[21:48] <didrocks> robert_ancell: not sure, if greyback_ tested some version already, it means, we have something compatible with Mir in distro
[21:48] <robert_ancell> didrocks, I'm just looking for the commit you probably need..
[21:48] <greyback_> didrocks: of mir, I'm using what is in main
[21:49] <didrocks> greyback_: ok, so which version of each package did you try from the ppa?
[21:49] <didrocks> so that I can only copy those (keeping the Mir in distro we already have)
[21:50] <asac> rihgt. please get us exactly which versions and packages you tested :)
[21:50] <asac> thanks
[21:50] <greyback_> didrocks: we have some more branches to land, before we have packages that will have unity8-on-mir fully functional
[21:50] <greyback_> so they're not yet in the ppa
[21:50] <didrocks> so you didn't test what's staged
[21:50] <robert_ancell> didrocks, the version in main seems up to date
[21:51] <robert_ancell> didrocks, the following changes don't seem to be requires for u8
[21:51] <didrocks> and we are going to have a new Mir as well as there is no ABI compatibility
[21:51] <didrocks> or we need to remove Mir from the ppa
[21:51] <greyback_> didrocks: nope. ricmm will when comes online
[21:51] <didrocks> and don't built it
[21:52] <kgunn> greyback_: maybe it's easire to explain what was used from where....mir, unity-api, qtubuntu, unity-mir, unity8, ubuntu-touch-session
[21:53] <kgunn> either from trunk, from archive or specified-ppa
[21:53] <didrocks> knowing that we want to land the minimal changes
[21:53] <greyback_> from mir, we are using what is in main
[21:53] <didrocks> *just* to have the things that we need to land
[21:54] <greyback_> from unity-api, the only change needed has been built and landed in the daily-build ppa
[21:54] <asac> greyback_: have you tested it with the archive mir? how sure?
[21:54] <kgunn> can we let him finish
[21:55] <asac> ok
[21:55] <kgunn> :)
[21:56] <greyback_> for qtubuntu, we have 2 branches which have been merged and are in ppa
[21:56]  * kgunn has to go get the boy, will return asap
[21:57] <greyback_> for unity-mir, 2 branches have landed, 1 more branch needs to be approved and built
[21:58] <greyback_> for unity8, there are 3 branches that need to each build and land
[21:58] <didrocks> greyback_: when do you think this one will be in trunk?
[21:58] <didrocks> same question for the 3 branches of unity8
[21:58] <greyback_> didrocks: ricmm needs to review it. It's not a big change
[21:59] <greyback_> didrocks: of unity8, 2 branches are approved, so can top approve immediately. 1 branch has small change, want CI to pass before it'll be approved
[21:59] <greyback_> these branches need to land in specific order, hence no top approvals
[22:00] <greyback_> ubuntu-touch-session: 1 branch needs review (ricmm tested it already)
[22:00] <didrocks> I'm not even sure ubuntu-touch-session is daily releasing, do you know?
[22:00]  * didrocks checks
[22:01] <didrocks> it doesn't
[22:01] <didrocks> do you know the process to land that?
[22:01] <didrocks> it seems ogra do manual uploads
[22:02] <greyback_> nope, I don't know the process for that
[22:02] <didrocks> kgunn: robert_ancell: it seems the safer is to backout the Mir version in the ppa
[22:02] <didrocks> rebuild unity-mir with distro Mir
[22:02] <didrocks> and get the rest in
[22:03] <didrocks> (so no latest Mir yet for the unity8 on Mir)
[22:03] <robert_ancell> didrocks, oh, the PPA has a specific version of Mir?
[22:03] <didrocks> robert_ancell: well, it has latest version
[22:03] <didrocks> (it just didn't land to distro)
[22:03] <robert_ancell> k
[22:03] <didrocks> robert_ancell: the manual publication is building all stacks
[22:03] <didrocks> as usual
[22:03] <didrocks> the only thing is that we don't copy to distro automatically
[22:04] <didrocks> but we do tests, etc.
[22:06] <Saviq> greyback_, ricmm, fginther, merged!
[22:07] <Saviq> just in time for faily release
[22:07] <Saviq> cyphermox, ↑
[22:07] <didrocks> Saviq: I hope it was a typo :p
[22:07] <Saviq> didrocks, :D
[22:07] <Saviq> didrocks, cyphermox called it that before me
[22:08] <Saviq>         ↓
[22:08] <Saviq> → cyphermox ←
[22:08] <didrocks> the issue were machine/DNS
[22:08] <Saviq>         ↑
[22:08] <didrocks> not really code :p
[22:08] <didrocks> anyway, let's move on
[22:08] <Saviq> didrocks, you broke my ascii art! :P
[22:09] <mhr3> omg, omg, broken ascii art
[22:09] <mhr3> what are we going to do?
[22:09] <mhr3> stop all the publishers!
[22:10] <mhr3> Saviq, but that's what you get for not letting didrocks sleep i guess
[22:11] <Saviq> mhr3, one for you, then → bug #1211595
[22:11] <Saviq> ;P
[22:12] <mhr3> damn, i should have kept my mouth shut
[22:16]  * greyback_ to bed