[04:38] <pitti_> Good morning
[04:45] <RAOF> pitti: Good morning!
[04:46] <Mirv> hello
[04:46] <czajkowski> aloha
[04:46] <pitti> bonjour tout le monde !
[04:47]  * TheMuso waves.
[04:48] <czajkowski> Happy Friday :)
[04:49] <TheMuso> Indeed, and happy bug fix day too. ;)
[04:49] <TheMuso> Well, maybe not fix, but workaround.
[04:55] <desrt> friday already?
[04:55] <desrt> dear lord
[04:55]  * desrt needs to go to bed
[05:05] <pitti> night desrt
[06:02] <didrocks> Mirv: hey! how are you?
[06:04] <didrocks> Mirv: small question on qtsystems: you don't handle the transition from the previous version (with binary packaging containing both the library and the qtdeclaratives one) and the new one with separated binary packages? (I'm fine with that, just in case you published those, some people will maybe be surprised by the upgrade)
[06:04] <didrocks> Mirv: otherwise ack on qtsystem, I can sponsor and new it
[06:04] <didrocks> Mirv: do I have anything else in my queue for you?
[06:05] <didrocks> Mirv: FYI, relaunching unity with "check with whole ppa" so that the tests are taking the latest xorg-server for testing
[06:54] <Mirv> didrocks: hello. right, it's not handling PPA version, but realistically not many have used that inofficial module.
[06:54] <Mirv> (or handling so that PPA version users would get the QML modules)
[06:55] <Mirv> didrocks: the other was lp:~kubuntu-packagers/kubuntu-packaging/qtfeedback-opensource-src + https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2/+files/qtfeedback-opensource-src_5.0%7Egit20130529.orig.tar.gz (reviewed by Ken so far)
[06:55] <Mirv> didrocks: and then handling of the ubuntu-html5-theme https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/enable_ubuntu-html5-theme_daily/+merge/172958
[06:56] <Mirv> I think that's it for now, I'm waiting for renato to test the new qtpim snapshot and the qtbase patches I just rebased have not been tested either yet, so those shouldn't be sponsored yet
[06:58] <didrocks> Mirv: ok, so I'm sponsoring qtsystems for now
[06:58] <didrocks> Mirv: then, preNEWing ubuntu-html5-theme
[06:59] <didrocks> if good, approving your branch and letting you deploy
[06:59] <didrocks> finally reviewing qtfeedback
[06:59] <didrocks> Mirv: meanwhile, you are handling the dailies?
[07:00] <jibel> good morning
[07:00] <didrocks> salut jibel!
[07:01] <jibel> Bonjour didrocks
[07:01] <Mirv> didrocks: yes, handling those, I was meaning to ask about unity armhf build failure though, does https://launchpadlibrarian.net/144210298/buildlog_ubuntu-saucy-armhf.unity_7.0.2%2B13.10.20130705-0ubuntu1_FAILEDTOBUILD.txt.gz look random failure since the code should be the same you successfully build yesterday evening?
[07:02] <Mirv> or is it because more X got in and now unity fails because of that
[07:02] <didrocks> Mirv: maybe just retry a build in launchpad? (it seems to be a random one)
[07:02] <Mirv> ok.. right LP build retry is cheap
[07:02] <didrocks> Mirv: then, if you relaunch the stack with "check with whole ppa" or "foo" for package, it won't rebuild it
[07:02] <didrocks> Mirv: just taking into account its status
[07:03] <Mirv> yep, I know
[07:03] <didrocks> Mirv: ubuntu-html5-theme will be used by qtcreator, am I right?
[07:06] <didrocks> Mirv: hum, ubuntu-html5-theme should be LGPL, not LGPL3+
[07:08] <Mirv> didrocks: not directly / necessarily, but yes it's depended by qtcreator-plugin-ubuntu. LGPL to be similarly licensed to the plugin, right?
[07:09] <didrocks> Mirv: yeah, we don't do +
[07:09] <didrocks> Mirv: I'll do a MP shortly
[07:09] <didrocks> there are other changes as well
[07:09] <Mirv> ok.. thank you. one thing I was wondering whether to put some sort of license file separately to the img folder, just a text for example to specify that those are CC-BY-SA, since it's only mentioned in debian/copyright now
[07:10] <didrocks> Mirv: yeah, we generally do that
[07:10] <didrocks> it's not mandatory, but we can
[07:10] <didrocks> I have one handy IIRC, one sec
[07:12] <didrocks> hum, it's a CC:BY-SA 2
[07:12] <didrocks> well, let's forget about it for now
[07:14] <didrocks> hum, interestingly those themes includes jquery
[07:21] <mlankhorst> the waiting is on unity now
[07:21] <Mirv> didrocks: one of the examples only, right?
[07:27] <didrocks> Mirv: yep
[07:28] <didrocks> Mirv: do you have the autopilot tests passing for you?
[07:28] <didrocks> for ubuntu-html5-theme?
[07:28] <Mirv> didrocks: yes, they passed
[07:29] <Mirv> 3 tests OK
[07:29] <didrocks> Mirv: ah, it's a bad dep
[07:29] <didrocks> Mirv: the autopilot ones needs the examples
[07:30]  * didrocks fixes
[07:32] <didrocks> Mirv: there is no upstream merger setup, right?
[07:33] <Mirv> didrocks: there is, https://code.launchpad.net/~ubuntu-html5-theme-devs/ubuntu-html5-theme/ambiance
[07:34] <Mirv> daily builds go to SDK Release PPA
[07:34] <didrocks> oh, it's already in stacks/head/sdk.cfg
[07:34] <didrocks> ok
[07:34] <Mirv> yep. or actually, not going to the PPA it seems, but still already there.
[07:35] <didrocks> Mirv: let me add a bootstrap commit as well so that we don't list every commit from rev 1
[07:37] <Mirv> ok
[07:38] <didrocks> Mirv: here we go: https://code.launchpad.net/~didrocks/ubuntu-html5-theme/clean-package/+merge/173147 :)
[07:39] <didrocks> https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/enable_ubuntu-html5-theme_daily/+merge/172958 approved meanwhile, please deploy once it's merged
[07:39]  * didrocks refreshes the whitelist on the archive admin machine
[07:40] <didrocks> done
[07:40] <Mirv> ok, doing one more rebuild and approving then
[07:40] <didrocks> great :)
[07:40] <didrocks> ok, so now qtfeedback
[07:47] <didrocks> Mirv: qtfeedback5-dev is multiarched
[07:47] <didrocks> it needs I guess:
[07:47] <didrocks> Multi-Arch: same
[07:47] <didrocks> Pre-Depends: ${misc:Pre-Depends}
[07:47] <didrocks> (not the private-dev though)
[07:51] <Mirv> didrocks: ok, fixing
[07:52] <didrocks> Mirv: examples/hapticsquare/hapticbutton.* is LGPL, with blabla, clause, not BSD3 and same for doc/src/snippets/qtfeedbackdocsample/qtfeedbackdocsample.cpp
[07:52] <didrocks> Mirv: apart from that, looks good :)
[07:52] <didrocks> oh sorry
[07:52] <didrocks> one additional stenza in the end :p
[07:52] <Mirv> :)
[07:52] <Mirv> pushed the multiarch change
[07:52] <didrocks> Mirv: perfect then! :)
[07:52]  * didrocks pulls
[07:53] <didrocks> Mirv: thanks! sponsoring as well
[07:53] <Mirv> thanks!
[07:53] <didrocks> (and then NEWing in distro)
[07:56] <seb128> good morning desktopers!
[07:56] <seb128> hey didrocks, Mirv
[07:56] <seb128> qtsystems \o/
[07:56] <didrocks> hey seb128!
[07:56] <didrocks> seb128: and qtfeedback, even if you don't care :p
[07:56] <didrocks> and ubuntu-html5-theme under dailies! :)
[07:56] <seb128> didrocks, don't care about this one :p
[07:56] <Mirv> hey seb128
[07:57] <didrocks> seb128: I preNEWed it FYI, if you see it in NEW
[07:57] <Mirv> seb128: were you planning to sponsor that https://code.launchpad.net/~mitya57/ubuntu/saucy/qtdeclarative-opensource-src/merge/+merge/172054 ?
[07:57] <didrocks> Mirv: maybe we should try just a rebuild of the sdk stack with ubuntu-html5-theme once you deployed the change?
[07:57] <seb128> Mirv, I can do, I didn't have a lock on it but I was planning to if nobody else was beating me to it
[07:57] <Mirv> that looks good, but qtwebkit will probably not go in as is, it probably has the same DPR problem that I had earlier
[07:57] <didrocks> to be done and NEWed before the week-end :)
[07:57] <seb128> Mirv, I will do it this morning
[07:57] <Mirv> didrocks: yes, I will check how it goes
[07:57] <Mirv> seb128: ok, thank you
[07:58] <seb128> didrocks, Mirv: unity tests seem to be happy, that's with the new xorg right?
[07:59] <Mirv> seb128: the tests run yesterday evening were fine, today there was a arm build failure and a rebuild is ongoing in case it was a random failure, at https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/4771564
[07:59] <seb128> looks at http://10.97.0.1:8080/job/autopilot-saucy-daily_release/335/testReport/
[07:59] <seb128> Mirv, ok, thanks
[07:59] <seb128> Mirv, do you have the build log of the build that failed?
[07:59] <Mirv> and then running checks again if the rebuild is fine, after which it can be considered to be published
[08:00] <Mirv> seb128: doh, not anymore, didrocks glanced at it as well
[08:00] <seb128> ok, let's see what the new try gives
[08:00] <lan3y> morning
[08:01] <didrocks> Mirv: it passed this time?
[08:01] <Laney> hrm
[08:01] <Mirv> didrocks: still running
[08:01] <seb128> Laney, good morning ... what was the n3y about? ;-)
[08:01] <seb128> Laney, good morning ... what was the n3y about? ;-)
[08:01] <Laney> must have gotten disconnected overnight
[08:01] <Laney> happy friday!
[08:02] <didrocks> Mirv: ok, maybe we can start the tests meanwhile to not loose time (as i386 is built), mind running with check with whole ppa to dist-upgrade and getting new xorg?
[08:02] <didrocks> happy Friday Laney!
[08:02] <Mirv> didrocks: ok, doing
[08:02] <didrocks> thanks ;)
[08:02] <Mirv> (and makes sense)
[08:02] <didrocks> Mirv: that will be an issue I guess if one day we start running the tests on slower archs to build…
[08:02] <didrocks> (like on the phone, so need to wait for armhf to be available)
[08:03] <seb128> Laney, happy friday! ;-)
[08:03] <didrocks> ok, unity - armhf build seems to have gone further in the build than where it failed
[08:06] <Mirv> didrocks: any idea why ubuntu-html5-theme fails trying to fetch revision 57 (the neweest revision is 56)?
[08:06] <Mirv> and yes, redeployed and issues a run now
[08:07] <Mirv> didrocks: should the bootstrap have been '55' instead of '56'?
[08:07] <Mirv> (the code has last_upstream_rev + 1)
[08:08] <didrocks> oh oh oh, you're rgith
[08:08] <didrocks> right*
[08:08] <didrocks> I should have set 55…
[08:09] <didrocks> Mirv: let me do a dummy commit if you don't mind? (changing the rev would be the same anyway)
[08:11] <Mirv> didrocks: ok!
[08:11] <didrocks> Mirv: ok, you can relaunch now, sorry for that :)
[08:11] <Mirv> thanks, np!
[08:23] <pitti> bonjour didrocks, seb128, et Laney
[08:23] <pitti> hey Mirv
[08:24] <pitti> Laney: hm, I got disconnected as well; perhaps it was freenode and not our proxies then
[08:24] <seb128> pitti, salut, ca va bien ?
[08:24] <Laney> I tend to blame freenode rather than my VPS provider in such situations :P
[08:24] <pitti> seb128: oui, merci
[08:24] <Laney> ps. hey, happy friday!
[08:24] <Laney> got good weekend plans?
[08:24] <pitti> seb128: et toi ? as-tu l'été maintenant ?
[08:24] <Mirv> hei pitti
[08:25] <seb128> pitti, ça va, non ... mais normalement l'été arrive cette après-midi ou demain
[08:25] <seb128> et toi ?
[08:25] <pitti> Laney: aye, a wedding from a friend of mien
[08:25]  * seb128 plans to enjoy the nice weather this w.e (if the forecast is correct)
[08:25] <pitti> seb128: 20 degrees and dry, what more can I ask for..
[08:25] <seb128> oh, maybe try to watch the wimbledon's final on sunday
[08:26] <seb128> (try because I'm not sure they are going to broadcast on public channels here and I'm not subscribed to the privates that have the rights)
[08:27] <Laney> forecast 26 and 27 here(!)
[08:28] <seb128> nice!
[08:28] <seb128> same here ;-)
[08:30] <Laney> bah, what's up with update-apt-xapian-index
[08:32] <Laney> bug #1118888
[08:32] <ubot2`> Launchpad bug 1118888 in apt-xapian-index (Ubuntu) "/usr/sbin/update-apt-xapian-index crashes daily" [Undecided,Confirmed] https://launchpad.net/bugs/1118888
[08:32] <Laney> broke cdimage builds and i got it on dist-upgrade too
[08:33] <darkxst> seb128, hi
[08:33] <seb128> where is mvo? hidding? :p
[08:33] <seb128> darkxst, hey
[08:33] <darkxst> I uploaded g-s-d 3.8 with a slightly patched g-c-c 3.6 to ppa:darkxst/gsd38
[08:34] <darkxst> ibus is disabled and no keyboard indicator
[08:34] <darkxst> lid close actions for power panel are gone
[08:35] <darkxst> otherwise everything else should work like, screenshots, media keys and automount helper
[08:37] <Laney> bug #1038429
[08:37] <ubot2`> Launchpad bug 1038429 in software-center (Ubuntu) "update-software-center crashed with order (MRO) for bases SafeConfigParser, object in __new__()" [Medium,Confirmed] https://launchpad.net/bugs/1038429
[08:38] <Laney> indeed something pulled python-configparser in with this dist-upgrade
[08:42] <seb128> Laney, right, I got that one installed as well
[08:42] <seb128> darkxst, why is the lid action dropped?
[08:43] <darkxst> seb128, I think the settings are dropped from g-s-d
[08:43] <seb128> hum, we need to add them back then
[08:45] <darkxst> seb128, https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=58cb4eee64bbd8ca43111b1f80fdaacde8ad5f12
[08:45] <darkxst> but I suppose there is more than that
[08:46] <Laney> didn't it move to logind?
[08:47] <seb128> Laney, the suspend/hibernate did, but isn't g-s-d supposed to keep inhibitors to prevent suspend in case it's needed?
[08:47] <seb128> or is there equivalent config options for logind?
[08:47] <seb128> pitti, ^
[08:49] <pitti> seb128: sorry, missing the original question
[08:49] <pitti> oh, question from darkxst?
[08:49] <seb128> pitti, in a logind world, can we configure what to do on lid close?
[08:49] <seb128> like suspend if on battery, don't if on a/c
[08:49] <pitti> seb128: sure; didn't I fix that like two weeks ago?
[08:50] <Laney> It's about the 3.8 upstream behaviour
[08:50] <pitti> seb128: the g-c-c UI and gsettings keys are supposed to work
[08:50] <pitti> ah
[08:50] <pitti> does 3.8 remove the lid config behaviour from g-c-c?
[08:50] <pitti> apparently so
[08:51] <seb128> pitti, well, part of the lid config was an Ubuntu patch to start
[08:51] <seb128> but yeah, they removed some of the keys
[08:51] <seb128> e.g https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=58cb4eee64bbd8ca43111b1f80fdaacde8ad5f12
[08:51] <pitti> seb128, darkxst: there's /etc/systemd/logind.conf for its default behaviour for lid switches, but that's not supposed to be for UIs, but for what happens on VTs or if nobody is logged in
[08:57] <darkxst> I disabled the lid close patch from g-c-c 3.6 because the keys don't exist anymore
[08:57] <seb128> Laney, do you watch emails for merge requests or do you prefer IRC pings? ;-) (on system settings)
[08:57] <seb128> darkxst, we should probably revert those changes...
[08:57] <Laney> I do see the emails but I don't always do them straight away
[08:57] <Laney> so every now and again I check lp
[08:58] <seb128> Laney, well, no hurry, I can wait some hours ;-)
[08:58] <Laney> I want to address the review comments on CrossFadeImage first
[08:58] <seb128> Laney, just send one using the newly landed qtsystem to get the disk space
[08:58] <pitti> darkxst: yeah, my patch to 3.6 was because 3.6 doesn't yet get along with the current logind behaviour; it's not needed for 3.8
[08:58] <Laney> cool!
[08:58] <seb128> Laney, wfm, good luck with that ;-)
[08:58] <pitti> darkxst: so it seems gnome 3.8 just dropped teh configurability of that :(
[08:59] <darkxst> pitti, for now just looking g-s-d 3.8 with g-c-c 3.6
[08:59] <pitti> darkxst: hm, then you will have the config panel for that which won't do anything?
[09:00] <pitti> darkxst: doesn't that crash on the missing gsettings keys?
[09:00] <darkxst> pitti, yes
[09:00] <darkxst> pitti, no I disabled the patch
[09:00] <pitti> darkxst: ah, you reverted 58cb4e?
[09:00] <pitti> that'd do it
[09:00] <seb128> he dropped the g-c-c patch that add the config UI rather I think
[09:00] <darkxst> pitti, the ubuntu patch that add lid close boxes
[09:00] <seb128> (those UI are an ubuntu patch)
[09:00] <pitti> aah
[09:00] <pitti> I forgot about that
[09:00] <seb128> but we added the patch for a reason
[09:01] <Laney> so I can see why gnome may have dropped it if they didn't have UI for it
[09:01] <seb128> we want that configurability...
[09:01] <pitti> but yeah, there was some discussion with upstream about making that configurable as our users got angry about removing it
[09:01] <mlankhorst> seb128: but I think the xorg side is ready now, just waiting for unity
[09:01] <seb128> mlankhorst, unity is still building on armhf: https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/4771564
[09:01] <mlankhorst> ok
[09:01] <darkxst> seb128, pitti : so, how do we handle that w/ logind?
[09:02] <pitti> darkxst: what is "that"?
[09:02] <Laney> seb128: Just quickly looking at the diff - surely you can avoid repeating that division so much :P
[09:02] <seb128> mlankhorst, btw looking at our versions page, how come we are behind debian on libx11/libxrandr/libxcb versions?
[09:02] <darkxst> pitti, lid close action
[09:02] <pitti> darkxst: I guess you just disable our g-c-c patch to add configurability for it, and drop the g-s-d patch for inhibiting logind
[09:03] <seb128> Laney, the getFormattedSize function? I just moved that, it was already in :p
[09:03] <pitti> darkxst: with upstream g-s-d 3.8 and current logind it should just work and suspend on lid close
[09:03] <seb128> Laney, I copied the function from the qtsystem example ... but I can change it if wanted ;-)
[09:03] <darkxst> pitti, that is exactly what I have done
[09:03] <Laney> doing / 1000 loads of times on the same value seems like it could be optimised
[09:03] <Mirv> unity autopilot tests failed again, a diff compared to the one run 4 hours ago: http://pastebin.ubuntu.com/5846095/
[09:03] <mlankhorst> seb128: I didn't want to update everything at once, so I mostly waited for new x1.14 first.
[09:03] <seb128> pitti, darkxst: I don't want suspend on lid close!
[09:03] <seb128> mlankhorst, ok
[09:04] <Mirv> seb128: unity AP ^
[09:04] <pitti> seb128: well, it's what gnome 3.8 does, so for ubuntu-gnome that seems right?
[09:04] <Mirv> seem preview navigation related
[09:04] <seb128> Mirv, shrug, seems like an issue with the dash previews :/
[09:04] <pitti> seb128: are we talking about ubuntu-gnome here, or about updating ubuntu's g-s-d to 3.8?
[09:04] <seb128> pitti, updating g-s-d to 3.8 in saucy (which darkxst is working on)
[09:05] <pitti> seb128: aaah -- I assumed we talked about ubuntu-gnome
[09:05] <seb128> pitti, well, Ubuntu GNOME wants the new version and they build from the archive
[09:05] <seb128> so they need it in the archive...
[09:05] <pitti> seb128: well, we certainly do want to forward-port our UI patch then, and revert the g-s-d patches which dropped these keys?
[09:05] <Mirv> didrocks: do you think yet another autopilot run should be tried? http://pastebin.ubuntu.com/5846095/ - compared green run 4:05:34 to this failed one 8:03:06
[09:05] <seb128> pitti, right, the initial question was "is there a new way to do that with logind, or should we revert the drop in g-s-d"
[09:06] <pitti> seb128: logind can't and won't read gsettings
[09:06] <didrocks> Mirv: hum, the failures seem to be on both configuration though? weird that flacky tests are failing the same way at the same time
[09:06] <seb128> pitti, so it's still g-s-d that should "play" with inhibitors?
[09:06] <pitti> seb128: we can globally disable it in logind.conf of course, but otherwise it should be under g-s-d's control
[09:06] <didrocks> Mirv: oh, it can be that the network connexion is suddenly bad in the QA datacenter?
[09:06] <pitti> seb128: yes
[09:06] <didrocks> jibel_: does this sound possible? ^
[09:06] <seb128> ok, makes sense
[09:06] <seb128> pitti, thanks
[09:06] <didrocks> (as it's the previews)
[09:06] <Mirv> ah, the previews are slow when network throttles, true
[09:06] <pitti> seb128: the logind suspend on lid is really supposed to just be a fallback if there is no session running (VT, lightdm)
[09:06] <seb128> didrocks, Mirv: where are the screencasts of those?
[09:07] <pitti> seb128: (same with the power button)
[09:07] <didrocks> seb128: no more screencast by now for unity tests
[09:07] <seb128> didrocks, that's why I couldn't find them yesterday :p
[09:07] <didrocks> seb128: this is what makes the machine exploding (recordmydesktop)
[09:07] <seb128> pitti, alright, that works for me, thanks!!
[09:07] <didrocks> jibel_ looked for better setting than "take 8G of ram)
[09:07] <seb128> darkxst, so we need to revert the feature drop in g-s-d and re-enable the g-c-c patch
[09:08] <didrocks> Mirv: let's wait for jibel's feedback?
[09:08] <Mirv> ok
[09:08] <darkxst> seb128, ok
[09:09] <Mirv> good to know, I was also wondering where the screencasts went
[09:09] <seb128> darkxst, thanks for the work on that btw! ;-)
[09:09] <darkxst> np
[09:09] <didrocks> Mirv: yeah, rdm sucks and fragment all the mem :/
[09:09] <didrocks> that's what made the dbus hang and so on…
[09:09] <didrocks> (it's still enable for other tests)
[09:10] <didrocks> but we need to find better settings than what the QA team picked
[09:10] <didrocks> (in autopilot)
[09:12] <jibel> didrocks, I don't see any connectivity issue in the lab
[09:13] <didrocks> jibel: all the previews failed on both config
[09:13] <didrocks> same build ran previously
[09:13] <didrocks> it can be the server as well
[09:13] <didrocks> Mirv: maybe try relaunching? (you need to stop the build monitoring first)
[09:13] <didrocks> Mirv: and let's blame the server? :p
[09:14] <jibel> didrocks, maybe there was but it is no more
[09:14]  * pitti uploads pkg-create-dbgsym to ignore the transitional unity-2d-dbg and thus produce proper dbgsym again
[09:14] <didrocks> ok, let's see the new run :)
[09:14] <pitti> seb128, didrocks ^ FYI
[09:14] <didrocks> thanks pitti!
[09:14] <pitti> it's a heuristic hack, but *shrug*
[09:15] <pitti> it depends on those packages having "transitional" anywhere in their description
[09:15] <pitti> (as I can't inspect their contents)
[09:16] <Mirv> didrocks: ok
[09:18] <Mirv> here we go again. maybe during this the arm build also finishes.
[09:18] <seb128> pitti, great!
[09:18] <jibel> didrocks, as for OOM, systems have been running for 24h running unity testsuite several time and the state of the systems is good. That confirms recordmydesktop was the problem
[09:19] <seb128> jibel, we miss the recording though, we have no idea what's happening with the previous there :/
[09:20] <pitti> Schroedinger's test!
[09:20] <seb128> hehe
[09:21] <jibel> seb128, I understand that, but using rmd kills the systems, if you know an alternative to rmd that push less pressure on the test host, I'm happy to patch autopilot
[09:21] <seb128> jibel, hum, but I don't... ;-)
[09:22] <Laney> there are alternatives like kazam but I don't know how they stack up
[09:24] <pitti> jibel: is that the giant memory leak you talked about which doesn't ever go away even with module unloading etc?
[09:24] <jibel> pitti, not a leak but memory fragmentation
[09:25]  * didrocks pulled a new version of cupstream2distro, if you see any prepare/publish job failing. (I've patched the existing .project files to be compatible)
[09:25] <didrocks> seb128: Mirv, FYI ^
[09:25] <seb128> didrocks, ok
[09:26] <jibel> pitti, but yes, after a run of unity with rmd enabled there are ~4GB of RAM that are never reallocated
[09:26] <seb128> didrocks, Mirv: unity armhf build worked \o/ (well, it's building the debs)
[09:26] <didrocks> seb128: phew!
[09:26] <seb128> " Built successfully"
[09:26] <seb128> \o/
[09:32] <jibel> a solution could be to run without rmd and when a test fail re-run it with rmd. there is the case of unstable tests but we can either find a way to mark them unstable or just mark them failed.
[09:37] <Mirv> \o/
[09:54] <Riddell> didrocks: don't you love us any more? :(
[09:55] <didrocks> Riddell: too many FTBFS in my inbox from that ppa, and TBH, I don't really use that team perms
[09:55] <didrocks> Riddell: still having access to ~kubuntu-packagers, right?
[09:56] <didrocks> (yep, through core-dev)
[09:56] <Riddell> yeah you're still elite :)
[09:57] <didrocks> ahah :)
[09:58] <seb128> Laney, I opened https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1198116 for info
[09:58] <ubot2`> Ubuntu bug 1198116 in Ubuntu UI Toolkit "[ListItems] Recent update changed the ListItem.Base margins" [Undecided,New]
[09:58] <seb128> Laney, I find the buttons (e.g "Check for updates" in the about panel) a bit too big since the update
[09:59]  * Laney goes blind at the orange buttons
[09:59] <Laney> well noticed
[09:59] <seb128> that as well...
[09:59] <Laney> that's design btw
[09:59] <Laney> I filed a bug on that and it got closed as invalid
[09:59] <seb128> the orange or the margin?
[09:59] <Laney> orange
[09:59] <seb128> :-(
[10:00] <seb128> you combine the small margin and the orange and you get "in your face" buttons :/
[10:50] <Mirv> the dash preview tests still failed :( http://pastebin.ubuntu.com/5846307/ (compared to the last fail)
[10:50] <Mirv> and some new tests as well, pretty random some of them
[10:53] <seb128> Mirv, did you try to run the preview tests locally?
[11:00] <davmor2> Hey guy on Saucy I noticed that recently software updater is only showing it's icon in the launcher for the initial window after it is displaying a python logo instead http://ubuntuone.com/2ou2Mr66aE9feaFUT2UHuF
[11:00] <Mirv> seb128: not yet, have to telco now, will try later with english locale (often useful)
[11:24] <Mirv> seb128: yep, seems to work locally with both the previous build and this one
[11:25] <seb128> so why does it fail on the jenkins :/
[11:26] <Mirv> meanwhile, ubuntu-html5-theme built but autopilot tests fail, I see the problem and trying to fix it shortly
[12:15] <didrocks> Mirv: want me to review your ubuntu-html5-theme branch (for the AP test) if you have any handy?
[12:16] <Mirv> didrocks: not yet, I'll ping if needing (alex is soon awake as well)
[12:18] <didrocks> ok :)
[12:46] <mlankhorst> booo, why are some libs still not m-a: same in saucy
[12:46] <mlankhorst> it makes it hard to coinstall all the gstreamer0.10 plugins
[12:53] <czajkowski> is this her first?
[12:53] <czajkowski> bah
[14:04] <jbicha> mpt: what does "Require my password when switching screen on" mean in the first screenshot of https://wiki.ubuntu.com/SecurityAndPrivacySettings
[14:05] <seb128> jbicha, hey, it's likely "lock on idle"?
[14:05] <seb128> e.g after idle time: turn off the screen and lock it
[14:06] <mpt> jbicha, I actually don't remember
[14:06] <mpt> Maybe it's "Returning from screen saver"?
[14:06] <jbicha> ok, I'm wanting to move the Screen Lock ON|OFF and Lock after _ minutes settings there too since gnome-control-center 3.8 moves those settings to their own privacy panel
[14:08] <mpt> Makes sense
[14:08] <mpt> (so long as screensaver settings themselves are a disaster, at least)
[14:09] <mpt> jbicha, what does "Screen Lock ON|OFF" do?
[14:10] <jbicha> org.gnome.desktop.screensaver lock-enabled
[14:11] <mpt> Is that equivalent to "Require my password when returning from screen saver"?
[14:11] <jbicha> yes I believe so
[14:11] <mpt> Overuse of on/off switches strikes again :-]
[14:13] <jbicha> well you can do nearly whatever you like what panel now since it's independent of gnome-control-center
[14:13] <mpt> right
[14:13] <mpt> So a "Returning from screen saver" checkbox at the bottom of that group would make sense
[14:14] <mpt> And then the time setting below that, perhaps?
[14:14] <mpt> though not indented, since it's not actually dependent
[15:34] <seb128> Laney, https://code.launchpad.net/~seb128/ubuntu-system-settings/serial-not-available/+merge/173229 (fyi)
[15:34] <seb128> kenvandine, you forgot to change the MR status?
[15:35] <Laney> cheers
[15:35] <Laney> that crossfadeimage stuff swallowed most of this day :/
[15:37] <kenvandine> seb128, no i didn't
[15:37] <kenvandine> was waiting for CI
[15:37] <kenvandine> https://code.launchpad.net/~ken-vandine/signon-plugin-oauth2/arches/+merge/173233
[15:37] <kenvandine> seb128, can you review that?
[15:38] <kenvandine> i need that to land so i can unblock cjwatson
[15:38] <Laney> I thought we were letting stuff just fail to build / depwait on ppc
[15:39] <kenvandine> Laney, long story :)
[15:40] <seb128> kenvandine, ok, approved on the basis that I trust you :p
[15:40] <seb128> kenvandine, you need to change the status I can't
[15:41] <jbicha> will there be an updated Unity today or will it wait for Monday?
[15:41] <didrocks> jbicha: we are trying hard to get one passing tests
[15:41] <seb128> jbicha, why?
[15:41] <didrocks> jbicha: but we maybe have a clue that enabling -proposed block things
[15:41] <seb128> jbicha, do you need something?
[15:41] <jodh> desrt: I'm looking at the doc for the d-conf "changed" signal which states, "Appending each item in changes to prefix will give the absolute path of each changed item."
[15:41] <jodh> desrt: presumably, that should say to stick a '/' between the prefix and each changes item right?
[15:41] <jbicha> no, I used -proposed to try the new X and I don't feel like adding a PPA to get Unity back
[15:42] <jbicha> I'm also fine with Unity staying in -proposed over the weekend
[15:42] <seb128> jbicha, it's likely what will happen
[15:45] <Laney> dobey: Did you see the bug I assigned to you? Reckon you'll be able to get to it?
[15:45] <dobey> what bug?
[15:46] <Laney> https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1038429
[15:46] <ubot2`> Ubuntu bug 1038429 in software-center (Ubuntu Saucy) "update-software-center crashed with order (MRO) for bases SafeConfigParser, object in __new__()" [Critical,Confirmed]
[16:17] <seb128> ok, just pushed another mr, and on that note time for some exercice
[16:17] <seb128> be back in an hours to read scrollback/clean emails and stuff and then calling it a week
[16:17] <seb128> having a good w.e for those who will be off by then ;-)
[16:21] <didrocks> see you later seb128!
[16:21] <didrocks> Laney: so, I'm trying now unity + new xorg from proposed without dist-upgrading
[16:21] <didrocks> as we were impacted by this software-center issue
[16:22] <didrocks> I hope to get the results in ~20 minutes
[16:22] <didrocks> if good, I'm going to publish unity into proposed
[16:22] <didrocks> a shame that we lost maybe the whole day of publishing unity due to software-center :/
[16:22] <didrocks> bregma: pstolowski: dednick: FYI ^ (I'll keep you posted)
[16:23] <bregma> sweet
[16:23] <pstolowski> didrocks: thanks
[16:23] <didrocks> the result on intel is promissing
[16:23] <didrocks> 6 failures
[16:23] <Laney> cool
[16:23]  * didrocks waits and stare at ati
[16:23] <Laney> I hope the s-c fix can be done today ...
[16:24]  * didrocks hopes as well, as long as previews are default for the desktop, people will notice :p
[16:25] <Laney> didn't get any confirmation it's being worked though
[16:26] <pstolowski> didrocks: people will notice previews for apps are now super fast and will be happy :)
[16:26] <didrocks> pstolowski: ahah, true! :)
[16:26] <didrocks> bregma: my only positive ":)" with this day for unity lost is that we found brandon's regression that we won't have noticed I guess otherwise…
[16:27] <bregma> he's been sent back to the drawing board on that one
[16:27] <didrocks> heh
[16:30] <didrocks> pstolowski: bregma: ati: 9 failures
[16:30] <didrocks> ok, so publishing unity into proposed
[16:30] <pstolowski> \o/
[16:30] <Laney> on a FRIDAY EVENING!
[16:30] <didrocks> Laney: on a f*** friday evening :)
[16:31] <Laney> funn
[16:31] <Laney> :P
[16:31] <didrocks> Laney: with the amount of run it had, I'm trustful :)
[16:31] <Laney> sounds like we've both had a day of tussles then
[16:31]  * Laney glares at qt/qml
[16:31] <pstolowski> that mean weekend! :) have a nice one and see you!
[16:31] <didrocks> Laney: well, s/day/days/ TBH
[16:32] <didrocks> pstolowski: have a nice one as well :)
[16:46] <didrocks> bregma: Laney: unity published FYI
[16:46] <Laney> great!
[16:46]  * bregma goes to upgrade
[16:46] <didrocks> Laney: not sure if you want to unblock that from proposed
[16:46] <didrocks> bregma: wait for a publisher cycle maybe :p
[16:47] <Laney> I'll test dist-upgrade it and probably just do it if so
[16:47] <mlankhorst> oh finally unblock time then? :P
[16:49] <Laney> muhahah
[16:49] <Laney> grrrrrrrr
[16:49] <Laney> I wonder if it'll be hard to port indicator-applet
[17:01]  * didrocks waves good evening and enjoy a nice week-end!
[18:09] <jbicha> you guys know indicator-datetime is broken right?
[19:07] <seb128> jbicha, no, how so?
[19:08] <jbicha> seb128: bug 1197647
[19:08] <ubot2`> Launchpad bug 1197647 in indicator-datetime (Ubuntu) "Date & Time applet in control center does not start" [High,Confirmed] https://launchpad.net/bugs/1197647
[19:09] <seb128> jbicha, hum, fun
[19:10] <seb128> larsu, ^ friday indicator breakage
[19:11] <kenvandine> we just love friday breakage
[19:13] <seb128> seems so
[19:38] <desrt> jodh: no.  it is written as it is to be read.
[21:43] <larsu> jbicha: indicator-datetime installs the panel into /usr/lib/x86_64
[21:43] <larsu> g-c-c doesn't look there
[21:43] <larsu> and instead thinks "this might be an external panel, let's execute its Exec line"
[21:44] <larsu> which is where it loops
[21:45] <jbicha> larsu: ok but what about the missing clock?
[21:45] <czajkowski> clock is not displayed on default clean install on saucy, didnt notice it til I went and added it there
[21:45] <larsu> jbicha: missing clock?!
[21:46] <larsu> jbicha: ah, the clock in the panel. Don't know, I can investigate that. It's probably a different issue though
[21:48] <Guest17995> the datetime panel (libindicator-datetime.so) used to be installed in /usr/lib/control-center-1/panels
[21:48] <larsu> Guest17995: right, I'm trying to find out since when it doesn't anymore
[21:48] <charles> ya
[21:48] <jbicha> czajkowski: um how do you add the clock?
[21:49] <czajkowski> I went to date and time settings
[21:49] <charles> larsu: it's in /usr/lib/contrl-center-1 in stock 13.04
[21:49] <czajkowski> and added it from there
[21:49] <czajkowski> now I'm stuck in some irritating loop under settings
[21:49] <charles> and Makefile.am hasn't changed...
[21:50] <larsu> charles: right, probably the packaging sets libdir differently
[21:50] <larsu> but I can't find when this would have happened
[21:50] <larsu> cyphermox: any idea? ^^
[21:50] <jbicha> czajkowski: when that happens here, I do sudo /usr/bin/gnome-control-center /usr/bin/gnome-control-center2, kill g-c-c and then move it back
[21:50] <charles> not much churn in debian/ either
[21:51] <cyphermox> what?
[21:51] <cyphermox> no idea
[21:53] <larsu> jbicha: killall gnome-control-center works as well
[21:57] <jbicha> larsu: it looks like the build changed between June 19 and June 28
[21:59]  * jbicha looks suspiciously at rev. 229
[22:00] <charles> that's suspicious because it's the only change to data/Makefile.am
[22:00] <larsu> jbicha: ya, that's it
[22:00] <larsu> charles: using libdir now, where before it used pkg-config
[22:01] <charles> larsu: I don't see how that's related to the panel install, though?
[22:02] <larsu> charles: pkg-config was used for gnome-control-center as well...
[22:02] <larsu> which is wrong, because multiarch
[22:03] <charles> oh, ya of course. I'm looking at data/Makefile.am but the bug is in src/Makefile.am
[22:04] <larsu> yep
[22:04] <larsu> so we have two options:
[22:04] <charles> yeah that's it, the line 3 change in src/Makefile.am r229
[22:04] <larsu> (1) de-multiarch indicator-datetime
[22:04] <larsu> (2) teach g-c-c about multi arch panels
[22:05] <larsu> I guess (2) doesn't make sense until g-c-c itself it multiarch
[22:07] <larsu> charles: (1) will be easier for now :)
[22:08] <charles> hmm
[22:09] <charles> so we would replace $(libdir)/control-center-1/panels/ with... what?
[22:09] <jbicha> charles: https://bazaar.launchpad.net/~indicator-applet-developers/indicator-datetime/trunk.13.10/revision/229
[22:09] <charles> you and seb128 and desrt seemed pretty adamant about removing local-install mode
[22:10] <larsu> charles: leave that as is, we should change the *package* to be single arch
[22:10] <charles> jbicha: right. I meant, do we want to revert it and re-introduce that feature that everyone was against, or is there a different change s.t. we avoid reintroducing it
[22:10] <larsu> charles: a multi-arch package that then installs something into /usr/lib is wrong anyway
[22:11] <larsu> jbicha: how düo I make a package single arch? Change "Architecture: any" to ... what?
[22:14] <jbicha> in this case I think you just need to revert the part of that commit you don't want
[22:14] <larsu> jbicha: no, that code was wrong
[22:15] <larsu> installing into /usr/lib/ is the wrong thing for multiarch
[22:45] <Laney> It's not multiarched
[22:46] <Laney> that's Multi-Arch: something in debian/control
[22:46] <Laney> It's because you have debian/compat set to 9 which does this, from debhelper(7):
[22:46] <Laney> Multiarch support. In particular, dh_auto_configure passes multiarch directories to autoconf in --libdir and --libexecdir.
[22:46] <Laney> larsu: ^
[22:50] <Laney> and this being a thing debhelper wants to do in the face of multiarch makes me feel that g-c-c should look in that directory too
[22:52] <Laney> jbicha: where do you see the missing clock?
[23:18] <jbicha> Laney: I don't have a clock in Unity's top right corner, bug 1197647 says I'm not alone
[23:18] <ubot2`> Launchpad bug 1197647 in indicator-datetime (Ubuntu) "Date & Time applet in control center does not start" [High,Confirmed] https://launchpad.net/bugs/1197647
[23:20] <Laney> ah, in unity - don't know then
[23:20] <Laney> I know that indicator-applet doesn't handle the new-style indicators (yet?)
[23:34] <m4n1sh> mpt: when you are free, can you please check your mail