[02:21] can I build unity8 on utopic, or does it require vivid? [02:21] unity8-build-deps is trying to install newer versions of packages than I have [02:46] mhall119: I believe you *should* be able to build on utopic (as long as you also have the various deps-from-source, such as Mir), but vivid's a better bet. [03:02] RAOF: well I'm certainly getting an error on a clean branch === charles_ is now known as charles [08:39] pstolowski: did you get time to produce the fields i need to implement the review modification stuff? [08:48] tsdgeos, not yet, sorry, will get them soonish [09:23] cimi: can you do https://code.launchpad.net/~aacid/unity8/noComponentsInGeneratedCardCreatorCode/+merge/258252 ? [09:23] mzanetti: can you do https://code.launchpad.net/~aacid/unity8/fixtestMainNavigation/+merge/258173 ? [09:23] yep [09:23] and i'll also need a volunteer for https://code.launchpad.net/~aacid/unity8/fallbackImage/+merge/258399 [09:24] tsdgeos, you 100% we don't need components in the cards? [09:24] carousel and such... (just asking weird cases) [09:25] cimi: the component is per category, so no, the card should never need it, we can generate the code based on the component contents [09:25] same for template btw [09:25] generated code should not depend on template because we can know that on compile time [09:43] MacSlow: https://code.launchpad.net/~fboucault/unity8/notifications_icon_respect_ratio/+merge/258069 for you! [09:48] tsdgeos, thx for pointing that out... I've been looking up and down my inbox and don't see any email notification regarding this [10:17] tsdgeos, running make testDashContent gives me this: http://paste.ubuntu.com/11007513/ [10:18] tsdgeos, make xvfbtestDashContent passes fine though [10:18] I don't think it's related to that branch [10:18] just as a FXI [10:18] FYI [10:18] mzanetti: hmmm, really? damnit, i had that whole test running for 2 hours here :/ [10:18] mzanetti: that's with or without my branch? [10:18] on that above branch [10:19] but the failing line doesn't seem to be the one you touched [10:19] sure, but the thing is making it all more stable :/ [10:19] not just one [10:19] mzanetti: you have it failing all the time? [10:19] 2 out of 2 failing with testDashContent [10:19] 2 out of 2 passing with xvfbtestDashContent [10:21] tsdgeos, tried a third time, failed again [10:21] :/ [10:21] not here [10:22] does runnig it standalone makes it fail too? [10:22] * mzanetti tries [10:22] yep. still failing [10:22] make testDashContent FUNCTION="DashContent::test_show_header_on_list_movement" [10:23] hmmm [10:23] let me give you a patch to try to see what's happening [10:24] now that's interesting... it's passing with GRID_UNIT_PX=16 here [10:24] but with the default of 8 it fails [10:24] probably still just timing [10:26] mzanetti: do you actually see some animation happening? [10:26] mzanetti: can you try http://paste.ubuntu.com/11007606/ and paste the output [10:27] i wonder if the animation is simply not happening for you [10:28] tsdgeos, qml: 120 112 [10:28] repeatedly [10:28] not sure what animation I should see [10:28] mzanetti: the header coming down [10:28] i guess you don't :D [10:30] does replacing the units.gu(2) by 4 in the touchFlick help? [10:30] tsdgeos, yeah. not animating [10:31] probably not but let's make sure [10:31] tsdgeos, yes, passing with units.gu(4) [10:31] ok [10:31] weird [10:31] i guess we can increase that [10:31] it's just to trigger a "horizontal move" [10:31] so it doesn't matter the actual number [10:32] just weird you need it and not me [10:32] indeed... [10:32] pushed anyawy [10:32] * mzanetti reverts and pulla [10:32] pulls [10:34] ack. passing now [10:37] * tsdgeos shurgs [10:38] tx for the review :) === MacSlow is now known as MacSlow|lunch [11:25] mzanetti, are wily repos already open? [11:25] ie, can we release stuff? :) [11:25] dandrader_, not that I know of [11:30] dandrader_, mzanetti, there are silos targeting wily at least http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu%2Flanding-014 [11:31] http://people.canonical.com/~platform/citrain_dashboard/#?q=wily [11:31] yeah, just saw that too [11:31] I just asked sil, he said the system is ready but the higher-ups didn't formally open it yet, as it usually seems to happen [11:31] so I guess we can start preparing silos targettting it [11:32] tsdgeos, I need to start using Ubuntu Components 1.3, but this spits out dozens of new deprecated debug messages [11:33] tsdgeos, shall I first fix those, then in a later branch do the feature? [11:33] pete-woods, you might want to look at lp:unity8 for a refactored QmlPlugins.cmake [11:33] more than dozen, fundreds :D [11:33] hundreds [11:33] Saviq: that's where I stole it from [11:34] cimi: can we just introduce it in the file you need it? [11:34] pete-woods, yeah, but it doesn't look current? [11:34] pete-woods, ah wait, it is [11:34] pete-woods, but [11:34] pete-woods, qmake foo will break cross-building [11:34] Saviq: you're right, it's not quite current [11:34] will pull updates [11:36] Saviq: from the looks of it I just need to delete a few buts [11:38] tsdgeos, yeah but I think it complains for others... [11:38] tsdgeos, I receive ton of debug messages, but the debug messages aren't clear [11:39] tsdgeos, : QML UCDeprecatedTheme: Theme.palette is deprecated. Use ThemeSettings instead [11:39] unknown file :/ [11:40] cimi, grep -r Theme.palette ;) [11:40] Saviq, did, MANY files :) [11:42] Saviq: I take it that QMLPLUGIN_DESTINATION is magically set by Qt now? [11:43] pete-woods, no [11:43] pete-woods, but you shouldn't use qmake either, that won't work in cross-building [11:44] Saviq: well I just stole your macro :p [11:44] pete-woods, my macro never called qmake ;) [11:44] pete-woods, because we don't install in the public dir [11:44] Saviq: ah, that explains that then [11:45] I can just set it to usr/lib/ARCH/… [11:45] pete-woods, that's the only way right now [11:45] works for me! [11:46] pete-woods, just a note, those macros (should actually be functions...) are meant to be wrapped [11:46] so they're generic [11:46] pete-woods, http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/plugins/CMakeLists.txt [11:46] there is a wrapper function right at the bottom [11:46] Saviq: yeah, I stole that function [11:47] pete-woods, good, I just saw that export_* was installing to QT_INSTALL_QML by default, don't do that :) [11:48] pete-woods, on that note, you might want to have a look at https://code.launchpad.net/~unity-team/unity8/refactor-qmltests/+merge/257835 [11:50] Saviq: will do :) [11:53] pete-woods, we need tests in cmake-extras btw.. [11:53] pete-woods, and re: QT_INSTALL_QML, QTBUG: https://bugreports.qt.io/browse/QTBUG-29987 - but seems they just punted it [11:59] tsdgeos, some warning might not be ours, since I grep for some of those warnings and they are not in unity8 [11:59] Saviq: yeah, I'm using a landing of indicator-network which uses most of the macros as a sort of test at the moment [11:59] tsdgeos, might be sdk broken somewhere [11:59] Saviq: but yeah, need to come up with a proper testing structure [12:00] wow, marked as invalid [12:00] nice === alan_g is now known as alan_g|lunch [12:01] it's amazing how difficult we are able to make each other's lives [12:02] pete-woods, yeah... [testing] totally, I'm quite scared to rely on this for all our builds with no tests... refactoring this thing was a mess [12:03] pete-woods, sure, unity8 is a good testing ground for it, but would rather... you know ;) [12:04] well it looks like your refactoring only significantly touches the QmlTest.cmake [12:04] pete-woods, oh yeah, that's just for this [12:05] pete-woods, but QmlTest.cmake should make it into cmake-extras at some poitn [12:05] *point [12:06] Saviq: sure, but that file is big and scary! [12:06] patches welcome! :p [12:06] ;) [12:06] once it actually gets ACKed, we'll see how it goes [12:07] Saviq: do you remember the cmake variable for arch triplet, btw? [12:07] I always forget the thing, and have to scour all my projects for it [12:07] pete-woods, is there one? :D /me asked gcc -dumpmachine ;) [12:13] Saviq: CMAKE_LIBRARY_ARCHITECTURE [12:13] * Saviq fixes qmltest [12:15] pete-woods, hum hum, isn't that going to be arm for x-building? [12:16] that's probably good for this, not good for my use... [12:16] OTOH we're not running those tests when x-building... [12:17] Saviq: tbh I thought it pretty much did what you said, i.e. parse gcc -somethingorother [12:17] pete-woods, yeah, but when cross, gcc is not gcc ;) [12:17] anyway [12:18] you don't want to run tests on build arch if it != host arch anyway [12:18] true, dat! [12:27] [12:34] cimi: well not broken but updated no [12:34] ? [12:35] tsdgeos, yeah, but if I write a patch that deprecates something, I make sure I don't have deprecates in my own code :) [12:42] cimi: oh well === MacSlow|lunch is now known as MacSlow === alan_g|lunch is now known as alan_g === dandrader_ is now known as dandrader|afk === dandrader|afk is now known as dandrader === dandrader is now known as dandrader|lunch === alan_g is now known as alan_g|EOD === dandrader|lunch is now known as dandrader === dandrader is now known as dandrader|afk [18:29] greyback, Apparently it's already done for bug 1416096 [18:29] bug 1416096 in ubuntu-system-settings (Ubuntu RTM) "expose battery charging state on the bus" [Medium,Fix released] https://launchpad.net/bugs/1416096 [18:29] greyback, You should be able to use the same value [18:29] * tedg is sad that he didn't find an action item for charles [18:29] tedg: sweet [18:30] currently it's a string; you could test for "plugged_in = (state=='charging') || (state=='fully-charged')" === dandrader|afk is now known as dandrader [19:12] elopio_: do you want to review this, or should I get someone from unity? https://code.launchpad.net/~josharenson/unity8/qa_helpers/+merge/258435 [22:47] elopio_: re qa_helper... How do you feel about making _is_greeter_active() public so that process_helpers can assert that the greeter was visible before calling unlock? I'm not sure its necessary, but that's how it was before. [22:53] elopio_: I guess the wait_for_greeter call would fail actually so there is no reason... I like the logic all contained in the module better anyway [22:54] josharenson: yes, I thougth that wait will raise the exception. But as you prefer, both sound good to me.