[08:02] <dholbach> good morning!
[15:10] <nigelb> bdmurray: ping :)
[15:11] <nigelb> dholbach: What happened to the plan about putting the packaging guide in an LP project?
[15:11] <nigelb> (at UDS-M)
[15:11] <dholbach> nigelb, in -N we'll make it happen
[15:11] <nigelb> \o/
[15:11] <dholbach> we're investigating and preparing the discussion right now
[15:11] <dholbach> to me it looks very doable
[15:11] <nigelb> Awesome, what format are we using? latex?
[15:12] <dholbach> that's not 100% decided yet
[15:12] <dholbach> the strong contender for me is ReStructured text
[15:12] <nigelb> anything that supports translations easily is +1 I suppose
[15:13] <dholbach> that's part of it, yes
[15:13] <nigelb> Ok, I'm all for ReStrured text, its much simpler than latex
[15:13] <nigelb> at least looks so to contributers :)
[15:13] <nigelb> Probably more and more like wiki :)
[15:39] <nigelb> bdmurray: I was wondering if we could run another script that would blindly unsubscribe the linux package, because whatever we do, its popping it :/
[15:39] <nigelb> s/it/in
[15:39] <nigelb> and that's a lot of bugs wth linux package
[16:20] <bdmurray> nigelb: could you give me an example of what's wrong?


[06:11] <soee> good morning
[06:52] <soee> http://mjg59.dreamwidth.org/37113.html
[07:32] <lordievader> Good morning.
[07:40] <soee> hiho lordievader
[07:41] <lordievader> o/
[08:17] <sitter> Riddell: please fix konsole stable CI and okteata stable CI
[08:17] <sitter> Riddell: please fix purpose unstable CI
[08:18] <sitter> Riddell: please fix rocs unstable CI
[08:20] <lordievader> I.e. please fix everything?
[08:20] <sitter> no, i.e. please fix everything you broke
[08:20] <lordievader> :P
[08:21] <sitter> shadeslayer: please fix ark unstable CI
[08:23] <Riddell> sitter: gotcha
[08:31] <sitter> Riddell: you didn't merge for 15.08 final yet, did you?
[08:43] <Riddell> sitter: no not yet
[08:43] <Riddell> still on marble and the ones you say above
[08:44]  * sitter fixes dolphin
[09:08] <sitter> wra
[09:08] <sitter> wrong window!
[09:08] <sitter> Riddell: do you want to be mentioned as orig-maintainer in kdebugsettings? currently you are maintainer, I am going to change to the team
[09:09] <Riddell> sitter: didn't clivejo package that?
[09:09] <sitter> -Maintainer: Jonathan Riddell<EMAIL_ADDRESS>[09:09] <Riddell> or was it aaron
[09:09] <sitter>  -- Aaron Honeycutt<EMAIL_ADDRESS>Wed, 12 Aug 2015 14:44:12 +0000
[09:09] <Riddell> yeah stick him down
[09:09] <Riddell> he's just too modest and let me take he credit
[09:19] <sitter>  * Qt5XmlPatterns (required version >= 5.5.1) , Qt5 XmlPatterns Module , <http://qt.io/>
[09:20] <sitter> one day upstreams will make reasonable version requirements I am sure of it
[09:23] <Riddell> yofel: how come you dropped marble-qt?
[09:24] <yofel> what's the point of a qt-only marble in a kf5 world? (or what was the point of kf5 again?)
[09:24] <yofel> I mean, keep it if you want. You'll have to double-build marble though
[09:27] <Riddell> it builds it as part of the normal build, and indeed there's not much  point but I expect upstream will complain if we don't ship it
[09:30] <yofel> it is? keep it then I guess
[09:30] <yofel> I never got as far as having a fully working kf5 build to check that
[09:54] <sitter> Riddell: ping
[09:54] <Riddell> hi sitter
[09:54] <sitter> Riddell: http://anonscm.debian.org/cgit/pkg-kde/applications/kmailtransport.git/tree/debian/libkf5mailtransport5.install?h=kubuntu_stable
[09:54] <sitter> do you think we should leave the kcm_.so in the lib package?
[09:55] <Riddell> hmm that feels wrong
[09:55] <sitter> other option would be a separate package with a recommends, while that makes the lib package more compliant it will however end up loosing the kcm should the so get a bump
[09:56] <sitter> so it's naughty packaging vs. users possibly loosing the kcm (iff the so version gets a change)
[09:57] <Riddell> why would the kcm get lost? it would just be updated and link against the new package
[09:58] <sitter> Riddell: in a perfect world it would, in an imperfect world unless there is a hard dependency on the KCM somewhere in the stack it will get removed if there is an upgrade path that does not entail changing mailtransport
[09:58] <sitter> as we have seen with baloo, albeit in a more complicated scenario
[09:58] <Riddell> mm
[09:59] <sitter> I am fine with splitting it though
[09:59] <Riddell> yeah me too
[10:05] <Riddell> ovidiu-florin: ahoneybun: do you still need this ec2?
[10:12] <shadeslayer> sitter: I thought I did yesterday
[10:12] <shadeslayer> brrr
[10:12] <shadeslayer> dafuq
[10:15] <sitter> Riddell: ping
[10:15] <Riddell> hi sitter
[10:15] <sitter> Riddell: more questions .. kdepimlibs has presently man libs that eventually might get split I hear. should I make independent data packages or one big bundling all data?
[10:16] <sitter> I am content to go with latter for now as most libs that have data have only a kcfg file and maybe a mime file
[10:16] <Riddell> yeah one big one seems fine, if we faff around with small ones they'll only be likely to change later
[10:17] <shadeslayer> sitter: fixed
[10:18] <sitter> どうも
[10:44] <sitter> Riddell: so what do we do witht he missing dep http://kci.pangea.pub/job/wily_stable_oxygen/21/parsed_console/job/wily_stable_oxygen/21/parsed_console/log_content.html#WARNING1
[10:44] <sitter> ignore or fix?
[10:45] <Riddell> KCI-W :: Missing Dep: KDE4Workspace (required version >= 4.9.80)  that doesn't exist any more does it?
[10:45] <sitter> Riddell: you killed it
[10:45] <sitter> apparently upstream thinks it should exist?
[10:45] <sitter> actually
[10:45] <sitter> Riddell: this needs taking upstraem
[10:45] <Riddell> right
[10:45] <sitter> kde-workspace is EOL this month
[10:45] <sitter> so it makes no sense to look for it in oxygen 5.4
[10:46] <sitter> Riddell: I am throwing together a quick mail
[10:46] <snele> still no dolphin 15.08 update for wily, but for exmp i got gwenview 15.08 update yesterday. where is dolphin update? i want to test it :)
[11:04] <sitter> Riddell: kgapi needs packaging. currently it is a full source repo. shoudl we fork the repo?
[11:04] <Riddell> sitter: yeah do it
[11:05] <sitter> what name?
[11:05] <sitter> could just make a kubuntu folder maybe?
[11:05] <sitter> i.e. kde-extras/libkgapi becomes kubuntu/libkgapi?
[11:06] <Riddell> hmm inelegant but I guess so is forking an existing repo
[11:06] <Riddell> so sure
[11:23] <BluesKaj> Hey folks
[11:28]  * Riddell uploads marble
[11:31] <BluesKaj> feature freeze tomorrow, then it'll be a good day to do other things
[11:40] <Riddell> snele: dolphin passed new now
[11:50] <sitter> Riddell: if you have time revu needed for port http://anonscm.debian.org/cgit/pkg-kde/kubuntu/libkgapi.git/log/?h=kubuntu_unstable
[12:03] <sebas> Riddell: are there 5.4 beta packages for 15.04?
[12:05] <Riddell> sebas: I'm afraid not
[12:05] <sebas> there will be backports once it's stable I suppose?
[12:08] <Riddell> sebas: scarlett seems to do backports readily, she just happens to be away this week
[12:08] <sebas> ok, no worries ... was just wondering if I could already upgrade my desktop with packages
[12:12] <sitter> transition for kgapi seems clearly only kdepim rdeps
[12:12] <sitter> same for libkolab(xml)
[12:23] <sitter> Riddell: please fix ktnef stable, ktnef unstable, kontactinterface stable, kontactinterface unstable, kmime stable, kmime unstable, kldap unstable, kldap stable, kholidays stable, kholidays unstable
[12:24] <sitter> Riddell: please also fix kdebugsettings stable and unstable
[12:25] <sitter> Riddell: please also fix gpgmepp stable and unstable
[12:47] <soee> when can we expect this to be fixed: libstreamanalyzer0 : Depends: libclucene-core1 (>= <IP_ADDRESS>) but it is not installable ? :)
[12:49] <sitter> at some point between now and release
[12:51] <soee> :-(
[12:52] <sitter> Riddell: please also fix kpimtextedit unstable and stable, kcontacts unstable and stable, kcalcore unstable and stable
[12:52] <Riddell> sitter: gotcha, some of these will have to keep their epoch alas
[12:54] <sitter> also kmbox
[15:12] <clivejo> hummm
[15:13] <clivejo> anyone running Kontact 15.07.90 in wily?
[15:48]  * Riddell pushes lots to git packaging
[15:49] <clivejo> Riddell: anything I can work on?
[15:53] <Riddell> clivejo: there is applications 15.08 final
[15:53] <Riddell> clivejo: that involves using the kubuntu-automation scripts to upload them to the PPA
[15:54] <Riddell> clivejo: you could give that a try on the ec2 I have set up for ovidiu-florin and ahoneybun but which they don't seem to have used
[15:55] <ahoneybun> we used it
[15:56] <Riddell> ahoneybun: then you didn't tell me if I could shut it off :)
[15:56] <Riddell> clivejo: ssh<EMAIL_ADDRESS>[15:56] <ahoneybun> I did
[15:56] <clivejo> poor credit card
[15:56] <Riddell> ahoneybun: I didn't hear you
[15:56] <clivejo> Riddell: I have to go for an hour or so
[15:56] <clivejo> you be about later?
[15:57] <clivejo> with the freeze tomorrow, will 15.08 make it in?
[15:57] <Riddell> clivejo: maybe, I'm not sure what my plans are
[15:57] <Riddell> clivejo: yes, it's got no new features
[15:57] <Riddell> only new features are the issue
[15:58] <clivejo> hope this kontact bug is fixed
[15:58] <clivejo> well two are fixed
[15:58] <clivejo> both are annoying
[19:30] <ovidiu-florin> ahoneybun: I've tested digikam
[19:30] <ovidiu-florin> it works awesome
[19:31] <ovidiu-florin> it's faaaaaaar more fluid and snappy than before
[19:31] <ahoneybun> sweet
[19:31]  * clivejo cheers and yodels
[19:31] <ovidiu-florin> If it get's promoted to an official ppa, please let me know
[19:31] <ovidiu-florin> or if you want to delete the ppa from your account
[19:32] <ovidiu-florin> I'm going to keep using it from your ppa until then
[19:32] <ahoneybun> it'll be on the backports PPA
[19:32] <ahoneybun> once it gets more QA
[19:32] <ovidiu-florin> + they've added a few more extreeeemly usefull buttons :D
[19:32] <ahoneybun> I'll keep it up for you
[19:32] <ovidiu-florin> thank you
[19:32]  * ovidiu-florin >:D< ahoneybun
[19:32] <ahoneybun> I mean LP is hosting lol
[19:33] <ovidiu-florin> ahoneybun: yes, but your account has a limit AFAIK
[19:33] <ahoneybun> of course
[19:34] <clivejo> and digikam is big :/
[19:37] <ovidiu-florin> https://bugs.kde.org/show_bug.cgi?id=350930 is solved
[19:46] <TJ-> LP PPA limits can be increased; you just have to request it
[19:46] <mamarley> Also, size limits are not respected when copying packages between PPAs.
[19:47] <clivejo> nope
[21:06] <[Relic]> Wow, that is truely sad.  Not one person seems to even have the slightest clue if sessions save and restore properly in 15.04.  Since 14.10 only had a 9month cycle would be great to know.  Are that few people using 15.x that no one knows if open applications show up on the assigned virtual desktops when starting or restarting the system after a shutdown or reboot?
[22:22] <clivejo> [Relic]: this is the devel channel, which is development of Wily 15.10
[22:23] <clivejo> have you tried asking in the #kubuntu channel
[22:33] <yofel> [Relic]: FWIW, dolphin and quassel restore fine in plasma5 on 15.04 with backports here. Haven't tried other applications, and I only have them on desktop1


[08:13] <Saviq> Mirv, morning, can you please drop shadow and libqtdbustest from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-041 for us? thanks
[08:13] <Saviq> Mirv, oh, and ubuntu-settings-components, too
[08:14] <Saviq> oh they're not there any more - then shadow, only :)
[08:15] <Saviq> owait
[08:15] <Saviq> why's it not in stable phone overlay :S
[08:39] <morphis> Saviq: I think I can do that too if you still need it
[08:40] <Saviq> morphis, nah, need to clear things up first, thanks
[08:40] <morphis> Saviq: aye, just ping me
[08:46] <Mirv> Saviq: yeah just ping again when you know if you want something changed
[08:54] <morphis> sil2100: ping
[08:54] <sil2100> morphis: pong
[08:55] <morphis> sil2100: any idea why https://requests.ci-train.ubuntu.com/#/ticket/1097 is not getting an automated sign-off run?
[08:57] <sil2100> morphis: I think one of the reason is that the train sees the packages as dep-waiting
[08:58] <morphis> sil2100: so a rebuild might help?
[08:58] <sil2100> morphis: if you check the archive (xenial for instance), you'll see that unity-system-compositor is built for all architectures
[08:58] <sil2100> morphis: in your silo it's not built for some archs, so the train treats that as an issue
[08:59] <morphis> sil2100: so that is a requirement before we can continue with any QA, I see
[08:59] <sil2100> Not sure if a rebuild will help since it clearly doesn't build on the few archs (like arm64, s390x)
[08:59] <morphis> but let me check with the unity-system-compositor guys
[08:59] <sil2100> In most cases that's a requirement, since we usually want it to build on all archs it was building before
[09:13] <Mirv> michi_: Elleo is our OSK guy but your problems described on the mailing list are so severe I'm not sure how to even debug that other than say "hardware is broken". but if the screen otherwise responds to touch, gestures, web browsing etc ok then I guess it should be tried to be debugged somehow.
[09:54] <Saviq> rvr, jibel, do you have any pointers about how to reproduce the freezes with silo 41? none of us were able to repro :/
[09:55] <Saviq> mzanetti's been dogfooding the phone with 41 for a few days now and nothing
[09:55] <rvr> Saviq: I think jibel had some steps, usually checking system settings
[09:56] <mzanetti> yeah... the instance I installed on friday on my krillin and I've ran through the OOBE... still the same boot running
[09:57] <jibel> Saviq, mterry reproduced it. Install silo 13 on top of latest rc-proposed on krillin, reset the phone, go through the wizard, open system-settings and play with it until it freezes
[09:57] <jibel> Saviq, it happens only on first boot
[09:58] <Saviq> hmm what's silo 13 ¿?
[09:58] <jibel> Saviq, 41 should probably be abandoned in favor of 13.
[09:59] <jibel> Saviq, it's the clone mterry created + some fixes
[09:59] <Saviq> ack
[09:59] <jibel> clone of 41
[09:59] <jibel> but confirm with him first
[09:59] <davmor2> Saviq: it's all your fault damn you ;)
[09:59] <koza> trainguards, Hi. I would need permissions to finish the landing of pulseaudio [already in silo 80]. Right now I cannot even comment on the request.
[10:02] <sil2100> koza: hey! Let me add you to the train users then
[10:02] <sil2100> koza: what's your LP username?
[10:02] <koza> sil2100, it is kzapalowicz
[10:03] <sil2100> koza: done
[10:03] <sil2100> koza: I suppose you know the CI Train usage basics already?
[10:04] <koza> sil2100, thanks.
[10:05] <koza> sil2100, do have a LandingProcess wiki and support from HWE team so I should be good however if in doubts I will ping you guys here.
[10:20] <abeato> trainguards, can you remove ofono package from silo 42 ? It is not needed anymore (ticket is https://requests.ci-train.ubuntu.com/#/ticket/1045)
[10:20] <Mirv> abeato: ok
[10:20] <abeato> Mirv, thanks
[10:20] <Mirv> koza: welcome to landers!
[10:21] <Mirv> abeato: done
[10:21] <abeato> great :)
[10:25] <koza> Mirv, thanks!
[11:03] <oSoMoN> jibel, https://trello.com/c/lZG2pxEX/2927-1122-ubuntu-landing-021-webbrowser-app-osomon should be removed from the "Needs QA Sign-off" queue for now, I’m rebuilding it and I’ve noticed that there is another webbrowser-app silo awaiting verification with higher priority anyway
[11:09] <jibel> oSoMoN, all right. We didn't plan to land it this week anyway since none of the bugs it fixes are for OTA10
[11:10] <oSoMoN> jibel, I’ve just added a fix for OTA 10 to that silo, and the fix for bug #1531583 would also be good to have in OTA10 (others can wait indeed), would you prefer if I removed all non-necessary fixes from the silo and have it targetted at OTA10 ?
[11:12] <jibel> oSoMoN, yeah, even if landings of the webbrowser are usually pretty safe, I'd rather split OTA10/non-OTA10 fixes in different silos
[11:13] <oSoMoN> jibel, sure thing, doing that now
[11:14] <oSoMoN> jibel, would you mind targetting bug #1531583 at OTA 10 ?
[11:15] <jibel> oSoMoN, done
[11:15] <oSoMoN> thanks
[11:16] <oSoMoN> jibel, I’ve updated silo 21, it’s now rebuilding with only the two bug fixes that are for ota10
[13:04] <alex_abreu> rvr, do you think you could check https://requests.ci-train.ubuntu.com/#/ticket/1144 ?
[13:05] <rvr> alex_abreu: It's next on the list
[13:18] <Mirv> 7w 22
[13:18] <Mirv> hmm
[13:46] <abeato> trainguards, could somebody publish https://requests.ci-train.ubuntu.com/#/ticket/1141 ?
[13:47] <Mirv> abeato: yeah I was looking at it already
[13:47] <abeato> cool
[14:11]  * sil2100 was battling keys in s-i
[14:11] <sil2100> Back to trainguard duty
[14:14] <jgdx> sil2100, silo 61 is the one needing a string freeze exception
[14:17] <sil2100> jgdx: ok, let me comment on the silo then - exception granted, we'll need the same for the big OOBE silo as well actually...
[14:18] <jgdx> sil2100, thank you
[14:26] <jhodapp> sil2100, any idea why this qtubuntu-camera build keeps failing for me on vivid? https://launchpadlibrarian.net/249409170/buildlog_ubuntu-vivid-armhf.qtubuntu-camera_0.3.3+15.04.20160321.1-0ubuntu1_BUILDING.txt.gz
[14:27] <jhodapp> sil2100, I've been assured that qtubuntu-camera should be dual landable
[14:29] <sil2100> jhodapp: hmm... interesting, just checked that qtubuntu-camera was always dual landable until now as we have the same version on both xenial and the overlay
[14:30] <jhodapp> sil2100, yeah thanks for checking, based on that output I'm just not sure why it's failing
[14:30] <sil2100> aalimagecapturecontrol.cpp:54:33: error: ‘AlertRole’ is not a member of ‘QMediaPlayer’
[14:31] <sil2100> This seems to be the failure causing the FTBFS, is that part of the new change?
[14:31] <sil2100> Strange if it builds for xenial though
[14:31] <jhodapp> sil2100, oh nice catch
[14:31] <sil2100> Maybe different dependencies?
[14:31] <jhodapp> I didn't catch that, I know how to fix that
[14:31] <jhodapp> sil2100, thanks!
[15:03] <jibel> Saviq, mzanetti do you know what are the autopkgtest failures in 27?
[15:03] <mzanetti> no way :D
[15:03] <mzanetti> I ran it actually last week
[15:03]  * mzanetti checks
[15:05] <Saviq> jibel, those are old runs for whatever reason
[15:06] <Saviq> jibel, britney didn't re-run them today
[15:06] <Saviq> jibel, I ran them this morning on the silo https://unity8-jenkins.ubuntu.com/job/test-ppa-autopkgtest/46/ and it was fine
[15:07] <Saviq> jibel, ah, that's likely because the tested ones in silo are the ones from archive (see it passed for the ones from silo)
[15:07] <Saviq> 0318 vs. 0318.1
[15:08] <jibel> Saviq, okay so does the silo needs a rebuild or something before publication?
[15:08] <Saviq> jibel, no, publish is good
[15:10] <jibel> Saviq, as soon as you publish it and in the overlay, sil2100  will respin an image
[15:12] <Saviq> ack
[15:12] <sil2100> Ok
[15:12] <sil2100> I trust your word on this one
[15:21] <Saviq> sil2100, published
[15:21] <sil2100> Saviq: ok, waiting for it to fully publish in the PPA and building a new image
[15:22] <mzanetti> sil2100, ok... I just tried here... it seems to run fine
[15:31] <jgdx> sil2100, ^ silo 61 is now in the capable hands of QA. In the mean time, how can I obtain the names of the translators I need to contact?
[15:33] <sil2100> jgdx: hey! There's no real list I'm afraid, the only thing one can do is reach out to the ubuntu-translators@ mailing list
[15:33] <sil2100> jibel, Saviq: image building
[15:34] <jgdx> sil2100, okay, I'll do that then. Thanks!
[15:34] <sil2100> jgdx: yw and thanks!
[15:42] <popey> jibel: who is testing unav? Noticing crashing on rc-proposed here. Seems to trigger whenever an app asks for location. (google maps in a browser crashes the browser)
[15:48]  * sil2100 needs to jump out now for a bit
[15:51] <Saviq> trainguards, can you please force-merge https://requests.ci-train.ubuntu.com/#/ticket/1115, thanks!
[16:34] <Mirv> Saviq: in progress ^
[16:35] <Saviq> Mirv, thanks
[16:37] <Saviq> Mirv, can you please drop ubuntu-settings-components from silo 13? thanks
[16:38] <Mirv> Saviq: done
[16:41] <Saviq> Mirv, thank you
[16:48] <Mirv> Saviq: dednick ^ somewhat sad conflict again, QA had just gone through it
[16:48] <Mirv> although it's translation update only so should be fast to retry, right?
[16:52] <Saviq> Mirv, which one? /me lost in queuebot's msgs
[16:52] <dednick> yeah... .i can't see anything :/
[16:53] <Mirv> Saviq: the 1143 ubuntu-settings-components was just approved, while your 027 landed and was now merged
[16:53] <Mirv> dednick: ^ so please rebuild 1143
[16:53] <Saviq> ah
[16:53] <Saviq> dednick, Mirv,  kicked a rebuild now
[16:53] <dednick> Saviq: ta
[16:53] <Mirv> Saviq: thanks, so jgdx dednick can re-approve it then after it has built, to get it back to QA look
[16:54] <Saviq> ack
[19:26] <popey> jibel: fyi, unav .55 is in the store
[19:26] <jhodapp> robru, what's going on with the builds atm?
[19:27] <jhodapp> robru, is something down?
[19:27] <robru> jhodapp: first I've heard of it. what are you seeing?
[19:27] <jibel> popey, okay
[19:27] <jhodapp> see the recent queuebot messages, and this specifically for my silo: https://ci-train.ubuntu.com/job/ubuntu-landing-053-1-build/21/consoleFull
[19:27] <jibel> popey, did you reproduce the crash when no gps bug?
[19:28] <popey> I have seen it multiple times
[19:28] <robru> jhodapp: wow that doesn't even make sense because we push with --overwrite
[19:28] <jibel> popey, I didn't, is there anything special to do it?
[19:28] <robru> jhodapp: the errors look like something is wrong with launchpad
[19:29] <jhodapp> robru, yeah I've never seen that before
[19:29] <popey> jibel: no, reboot, open unav, press the location circle
[19:29] <popey> jibel: beginning to think my very old e4.5 needs re-flashing clean at some point
[19:30] <jibel> popey, even if there is old or corrupted data it shouldn't bring the system or the app down
[19:30] <popey> indeed
[19:31] <robru> jhodapp: try again I guess? train itself appears online so not much I can do. I just asked in #is-outage
[19:31] <jibel> popey, no problem with your steps, it doesnt' crash
[19:31] <jhodapp> robru, saw that thanks, I'll try the build again
[19:31] <robru> yw
[19:35] <popey> jibel: probably my device then :)
[19:36] <jibel> popey, I'll try on krillin, it was an arale
[19:41] <jhodapp> robru, it's definitely not working...keep getting the same error
[19:44] <jhodapp> robru, something I did wrong with my MR by chance?
[19:52] <robru> jhodapp: what branch is it?
[19:53] <jhodapp> robru, https://code.launchpad.net/~phablet-team/telephony-service/audio-role/+merge/289700 is the MR
[19:53] <robru> jhodapp: I mean I can't imaging your branch doing anything wrong, the train just has a special place it pushes it's code to, you wouldn't have any power over that. unless you somehow managed to delete the .bzr directory from your source tree or something, post-mege
[19:53] <jhodapp> robru, just did the normal process
[19:55] <jhodapp> robru, is it truly still building? https://requests.ci-train.ubuntu.com/#/ticket/939
[19:55] <robru> jhodapp: yeah your MP looks totally innocuous
[19:55] <jhodapp> robru, great
[19:56] <robru> jhodapp: yes it is still building in the ppa: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-053/+packages
[19:57] <jhodapp> robru, ok I'll let that finish and if necessary try again when it's done


[04:55] <ejat> 2016-05-08 04:15:09 INFO install However the following packages replace it:
[04:55] <ejat> 2016-05-08 04:15:09 INFO install   mysql-testsuite-5.7 mysql-server-core-5.7 mysql-client-5.7
[04:55] <ejat> 2016-05-08 04:15:09 INFO install   mariadb-server-core-10.0 mariadb-client-10.0
[04:55] <ejat> 2016-05-08 04:15:09 INFO install
[04:55] <ejat> 2016-05-08 04:15:09 INFO install E: Package 'mysql-client-5.6' has no installation candidate
[04:55] <ejat> 2016-05-08 04:15:09 INFO install Traceback (most recent call last):
[09:18] <mup> Bug #1579051 changed: Race in juju/controller/destroy and TestDestroyCommandConfirmation <blocker> <ci> <race-condition> <regression> <juju-core:Invalid> <https://launchpad.net/bugs/1579051>
[14:27] <jackweirdy> Is there any documentation on how to create a docker provider?


[05:40] <jhesketh> Hi There. Is this a good place to ask a few questions about the flow through ubiquity -> lightdm -> unity?
[08:29] <sil2100> Anyone here running most recent precise, unity 3D with a free moment of time to perform 2 small manual tests?
[08:30] <MCR1> sil2100: sry, on quantal already...
[08:31] <sil2100> MCR1: hm, quantal normal or quantal-proposed?
[08:31] <MCR1> normal with additional ppas
[08:31] <MCR1> I fear proposed ;)
[08:31] <sil2100> MCR1: but unity is from quantal, yes?
[08:31] <MCR1> no, from the staging PPA
[08:31] <sil2100> MCR1: good that you do! quantal-proposed is a risky game!
[08:32] <sil2100> MCR1: what version of unity is it?
[08:32] <MCR1> sil2100: 5.12+bzr2470ubuntu0+724
[08:33] <sil2100> MCR1: thanks, well, I need someone with a smaller version
[08:33] <sil2100> seb128: do you have a spare minute?
[08:33] <sil2100> seb128: (hi btw.)
[08:34] <seb128> sil2100, hey, yes
[08:34] <sil2100> seb128: you're running precise, yes?
[08:35] <sil2100> seb128: since I need 2 tests confirmed from someone running 5.12 - could you open the HUD, press Alt+F1 and tell me if you enter navigation mode on the Launcher?
[08:36] <didrocks> sil2100: it doesn't
[08:36] <didrocks> sil2100: there is a merge in trunk which is supposed to fix it :)
[08:37] <didrocks> (and a AP test as well IIRC)
[08:37] <sil2100> didrocks: it doesn't enter?
[08:37] <didrocks> yep
[08:37] <sil2100> didrocks: what's the desirable effect?
[08:37] <didrocks> entering the launcher keyboard navigation mode I think
[08:37] <didrocks> which is what the branch was supposed to do
[08:38] <sil2100> didrocks: since we have an autopilot test failing (both in AP and in manual-testing) which says it SHOULDN'T, but does
[08:38] <didrocks> hum?
[08:38] <sil2100> """Pressing Alt+F1 when the HUD is open must not start keyboard navigation mode."""
[08:38] <didrocks> ah HUD
[08:38] <didrocks> not dash
[08:38] <sil2100> This is the comment on the autopilot test
[08:38] <didrocks> sil2100: ok, then, please check with them
[08:39] <didrocks> it doesn't in dash and HUD on previous version
[08:39] <didrocks> I misread the merge then and thought the opposite was wanted
[08:39] <sil2100> So it's an regression?
[08:39] <didrocks> yeah
[08:41] <seb128> sil2100, it doesn't go in navigation mode
[08:42] <seb128> it seems weird that the hud and dash are supposed to behave differently
[08:42] <seb128> could be worth checking with design?
[08:43] <MCR1> Anyone an idea how we could fix that one: bug 1017550 ?
[08:43] <sil2100> seb128: I have some strange autopilot tests here... so keynav mode should work when dash is opened?
[08:45] <sil2100> JohnLea: hello, are you around?
[08:47] <seb128> sil2100, I'm not sure, best to check with JohnLea
[08:54] <JohnLea> sil2100, seb128 ; hi, I'm back, what's the question?
[08:55] <sil2100> JohnLea: hi, I'd like to ask a bit about the keynav behavior during dash and HUD
[08:55] <sil2100> JohnLea: when the HUD or the Dash are opened, what should Alt+F1 do?
[08:55] <sil2100> By design?
[08:57] <JohnLea> sil2100, seb128; close the Dash/HUD and open the Launcher keyboard navigation I think
[08:58] <sil2100> JohnLea: oh, that would actually make sense - but we have some autopilot tests in unity that say that it should be the opposite
[08:58] <sil2100> And that it shouldn't start keynav mode when in dash or HUD
[08:58] <JohnLea> sil2100; strange, I don't think that request came from us in design
[08:59] <didrocks> http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/2457
[08:59] <sil2100> JohnLea: ok, thanks - I'll try to find the person who made the AP and ask why they added this
[08:59] <JohnLea> sil2100; I think the tests are bugby ;-)
[08:59] <didrocks>         """This test when Alt+F1 is activated it must close the dash."""
[08:59] <didrocks> so the dash is fine, it was the MR I was referring to
[08:59] <sil2100> didrocks: ok
[09:00] <didrocks> sil2100: you mean, there is an opposite one for the HUD?
[09:00] <sil2100> didrocks: still need to bzr blame the person who added: """Pressing Alt+F1 when the HUD is open must not start keyboard navigation mode."""
[09:00] <didrocks> sil2100: yeah ;)
[09:00] <sil2100> didrocks: test called test_disabled_alt_f1 in test_hud.py
[09:00] <sil2100> didrocks: the same for test: """When switching from the hud to the dash alt+f1 is disabled."""
[09:00] <didrocks> sil2100: so basically, bother (HUD/dash) enters navigation mode, right?
[09:01] <didrocks> sil2100: it seems only the test has to be fixed for the HUD to test the fact that you enter navigation mode?
[09:01] <sil2100> didrocks: yes, both enter keynav mode
[09:01] <sil2100> didrocks: so the tests are probably invalid
[09:01] <didrocks> yeah, seems so
[09:01] <sil2100> didrocks: since alt+f1 for both dash and HUD in unity 6.0 enter keynav mode
[09:01] <didrocks> which is what is wanted, good, yeah bzr blame is your friend here :)
[09:01] <sil2100> didrocks: when in HUD, well, the hud is not hidden, but keynav mode works!
[09:02] <didrocks> sil2100: hum
[09:02] <sil2100> didrocks: so it's partially fixed ;p
[09:02] <didrocks> sil2100: it should do the same for both
[09:02] <didrocks> otherwise, it's confusing :)
[09:02] <sil2100> didrocks: yes, I presume ;)
[09:03] <sil2100> It seems as if brandon added this test..?
[09:03] <sil2100> Will have to discuss this with him when he's online
[09:04] <didrocks> yep
[09:24] <MCR1> smspillaz: Hi :) Is it more or less safe to use your new experimental Compiz PPA or is it rather not recommended to use it ?
[09:42] <smspillaz> MCR1: I'm still trying to get it building
[09:42] <smspillaz> MCR1: lots of things will be broken, there are a lot of plugins which have not been (and will not be in the near future) ported to the new API
[09:43] <smspillaz> when I say "lots of things" I mean "lots of things" if you extend beyond the default ubuntu usecase
[09:45] <MCR1> smspillaz: Thx 4 the info. I think I understand.
[09:45]  * MCR1 is removing the PPA from the sources...
[10:01] <smspillaz> MCR1: that being said, if you're feeling adventerous and want to help development, you can test whats in https://code.launchpad.net/~smspillaz/+archive/compiz-experimental/ and report bugs (tagged with 'gles')
[10:01] <smspillaz> I haven't been able to test it yet myself
[10:08] <MCR1> smspillaz: I just downgraded ;), but ofc. I will help with testing and reporting bugs, but not today anymore (not enough time)...
[10:10] <sil2100> didrocks: remember the problem I had with merge-upstream in libunity? (and why essentially I had to remove your unreleased version to re-add it later)?
[10:10] <sil2100> didrocks: the thing with merge-upstream throwing a python error that revision is not found
[10:10] <sil2100> didrocks: it seems to be the case because libunity ubuntu branch is in a bit of a mess-state
[10:11] <sil2100> The 5.90.0 version (UNRELEASED) wasn't properly imported with merge-upstream
[10:11] <sil2100> So, in fact, the lp:ubuntu/libunity tree doesn't have the upstream-5.90.0 tag pointing anywhere
[10:12] <sil2100> Because there is no merge for it
[10:13] <sil2100> didrocks: so when I try importing a new tarball, bzr merge-upstream wants to have a starting point from the last tarball import (5.90.0) - but can't find the revision there
[10:13] <sil2100> didrocks: since upstream-5.90.0 = ?
[10:14] <sil2100> didrocks: you can even see that through bzr vis that something's _wrong_
[10:16] <smspillaz> MCR1: sure np
[10:17] <MCR1> smspillaz: I guess it would be best to test this with some standard config, yes ? I mean without all the additional Compiz stuff I have up and running here ?
[10:18] <smspillaz> MCR1: it will work fine, but some things just won't work that's all
[10:19] <smspillaz> I don't *think* it will try and load anything built against the old abi
[10:20] <MCR1> smspillaz: Ok, since I often had the problem of Compiz not even starting when using my config... (Compiz updates keep me nervous all the time until the new boot is finished)
[10:21] <MCR1> smspillaz: Probably it would be wise to have a fresh Quantal installation on some partition just for tests of that kind...
[10:23] <smspillaz> MCR1: you'll need Quantal for this anwyays
[10:23] <smspillaz> *anyways
[10:23] <smspillaz> unity is depending on nux 3.0
[10:24] <sil2100> ...after the unity 6.0 release is done!
[10:24] <sil2100> :)
[10:26]  * smspillaz twiddles thumbs waiting for unity to build on the buildbots
[10:26] <MCR1> smspillaz: Sure, I will setup a new installation of Quantal and run the (manual) tests then - I will do it on Monday... (weekend==girlfriend&&partyparty) ;)
[10:26] <smspillaz> no problem have fun
[10:27] <c10ud> smspillaz, MCR1, as i was discussing with didrocks yesterday, nux3 and unity6 is possible in Precise
[10:27] <c10ud> ofcoure it is unsupported and such stuff, but still possible
[10:27] <c10ud> i have a few issues getting unity to build in a ppa, but locally it built and it's all good
[10:28] <smspillaz> c10ud: it might be. I think unity 6.0 and nux 3.0 are depending on boost1.49
[10:28] <smspillaz> but they might just be using functionality shared by boost1.46
[10:28] <c10ud> looks like they do, i'm running them right now
[10:28] <smspillaz> figures
[10:29] <smspillaz> I wouldn't be able to tell on my precise installation since I build a lot of things from source
[10:29] <c10ud> heh
[10:29] <smspillaz> glib, Xorg, kernel, unity, compiz, gnome, mesa etc
[10:30] <smspillaz> its hardly stable but who cares about /that/
[10:37] <didrocks> smspillaz: you need to use -r -1
[10:37] <didrocks> as I typed on the example :)
[10:38] <didrocks> sil2100: yeah, libunity case is different, right :)
[10:38] <didrocks> sil2100: please still get a real changelog :)
[10:38] <smspillaz> didrocks: -r -1 ?
[10:38] <smspillaz> didrocks: was this about the automerger ?
[10:38] <didrocks> oupss, it was for sil2100 :)
[10:38] <smspillaz> oh ok
[10:38] <smspillaz> didrocks: while you're here ...
[10:38] <sil2100> didrocks: will do! But I'll still have to, sadly, remove the last changelog entry and re-add it with the new version (but with the proper committer ;p)
[10:38] <smspillaz> didrocks: is compiz in freeze? automerger seems to be doing nothing
[10:39] <didrocks> smspillaz: yep :)
[10:39] <didrocks> smspillaz: yeah
[10:39] <smspillaz> kk
[10:39] <didrocks> smspillaz: see the email about the freeze, even if sil2100 never confirmed it was frozen on the ML
[10:39] <smspillaz> yeah I thought we were doing compiz a little later. oh well
[10:40]  * didrocks takes a shower now that the running-under-the-rain is done :)
[10:40] <smspillaz> heh
[10:40] <didrocks> smspillaz: you should UNBLOCK the test for gsettings
[10:40] <didrocks> and all changes related to it
[10:40] <didrocks> Mirv will have to redo the packaging anyway
[10:40] <sil2100> Well, I only wanted to freeze the unity trunk, without compiz!
[10:40] <didrocks> because he didn't go to all merge request to see that some tests were missing :)
[10:40] <sil2100> I think Mirv asked for a compiz freeze ;)
[10:41] <didrocks> always ensuring that the criterias are met is a must :)
[10:41] <didrocks> or you would make rick and distro unhappy ;)
[10:41] <didrocks> real shower now, really needed ;)
[10:55] <sil2100> mhr3_: in the new libunity you guys removed some symbols, mostly related to previews
[10:55] <sil2100> mhr3_: this was the cause of an ABI break that we had recently?
[10:56] <sil2100> hm, wait, actually I see those symbols were only in 5.90.0
[10:56] <sil2100> Which wasn't released
[10:56] <sil2100> didrocks: what should I write in the changelog in this case?
[10:57] <sil2100> didrocks: some symbols got removed, but only symbols with 5.90.0 version number - which didn't get 'officially' released
[10:57] <didrocks> sil2100: no, it's fine, previews were never released
[10:57] <sil2100> didrocks: should I note that some symbols from 5.90.0 got removed?
[10:57] <didrocks> so fine :)
[10:57] <didrocks> juts updated symbols
[10:58] <didrocks> that's it
[10:58] <sil2100> didrocks: ok, thanks
[10:58] <didrocks> nothing else :)
[10:58] <didrocks> yw
[11:01] <MCR1> gotta go. c ya. :)
[11:07] <sil2100> didrocks: for lenses, I should also use the Breaks: tag pointing to new unity?
[11:07] <sil2100> I mean, to old unity
[11:07] <didrocks> sil2100: indeed
[11:07] <didrocks> well << newversion
[11:07] <didrocks> as I did
[11:07] <sil2100> didrocks: ACK :)
[11:09] <sil2100> didrocks: actually, in unity packaging you did << 6.0.0, but actually we're not releasing 6.0.0 versions for the application and files lens
[11:09] <sil2100> The video lens also has different versioning
[11:09] <sil2100> didrocks: is that still correct?
[11:10] <Mirv> compiz would be working with the gsettings backend and testable via https://launchpad.net/~timo-jyrinki/+archive/prerelease-unity60/+packages
[11:10] <Mirv> if it will be unfrozen for adding tests (?) then fine, but the bzr3278 is now testable
[11:10] <didrocks> sil2100: oh? I gues you were
[11:11] <didrocks> guess*
[11:11] <didrocks> didn't we standardize in version 6 for everything?
[11:11] <didrocks> including lenses
[11:11] <didrocks> oh we backport them, right :)
[11:11] <didrocks> sil2100: for those we do backport, please fix the versionning
[11:11] <didrocks> Mirv: we will need to snapshot a newer version
[11:12] <didrocks> Mirv: keeping the freeze but UNBLOCK the merges for tests
[11:12] <didrocks> as we can't release without that
[11:12] <sil2100> didrocks: ACK, I'll fix that up
[11:12] <didrocks> thanks sil2100
[11:13] <Mirv> didrocks: ok, so waiting for the merge to trunk and then I'll rework the packaging accordingly
[11:14] <didrocks> yep :)
[11:14] <didrocks> Mirv: you are doing a tarball for the snapshot, right?
[11:16] <Mirv> didrocks: yes
[11:16] <sil2100> didrocks: oh! And I even see the thing you were talking about during the sprint - the unity-lens-applications package has Breaks: ula (<< 0.4.0), but we can remove that right? Since quantal doesn't offer smaller versions than 5.12, right ;)?
[11:16] <sil2100> So I can remove the Replaces and Breaks parts for ula previous? ;)
[11:17] <sil2100> (or, so called unity-place-applications)
[11:18] <didrocks> sil2100: yeah, you can clean that now
[11:18] <didrocks> as place doesn't exist anymore
[12:01] <sil2100> didrocks: I'm fixing up unity-2d for the new release now - in dependencies, should I add something like 'libunity-core-5.0 OR libunity-core-6.0' or just enforce using 6.0?
[12:01] <Klap-in> hi people! for bug 904205 the fix is merged in devel, what's the way to get it in precise?
[12:02] <didrocks> sil2100: no, just use 6.0
[12:02] <didrocks> Klap-in: we will backport important fixes in compiz trunk to precise next week
[12:04] <sil2100> didrocks: ok, done - I'll also push it upstream as a MRQ, since upstream needs to rebuild against the new nux and unity as well
[12:05] <didrocks> yep
[12:07] <Klap-in> ok, so at that moment also inclusion of that fix will be reviewed? or is it also helpfull to propose it somewhere in the sytem?
[12:07] <didrocks> Klap-in: no, we will review all commits in trunk
[12:08] <didrocks> and see if it's safe enough to backport it to precise or not
[12:11] <Klap-in> ok, nice. Then i will look forward to the review.
[12:38] <c10ud> new unity really brings an uber speedup
[12:38] <c10ud> never been able to get 60fps in a wine-gl game
[12:49] <sil2100> didrocks: hm, should we add a Replaces: libunity-core-5.0-5 for libunity-core-6.0-5 in debian/control?
[12:49] <didrocks> sil2100: why would we need that?
[12:50] <didrocks> c10ud: yeah, the last commit makes a clear difference in speed :)
[12:50] <sil2100> Since hm, now we can have both libunity-core-5.0-5 and libunity-core-6.0-5 installed in a system, right?
[12:50] <didrocks> sil2100: comes back to the conflicts/replaces definition
[12:51] <didrocks> first, do you have files that are common between the 2 packages?
[12:51] <didrocks> the answer is no
[12:51] <didrocks> so no need for replaces
[12:51] <sil2100> ACK ;)
[12:51] <didrocks> then, can't we install libunity-core-5.0-5 and libunity-core-6.0-5 on the same system?
[12:51] <didrocks> yes, we can if we want to :)
[12:51] <didrocks> so no need for conflicts :)
[12:52] <didrocks> sil2100: don't apply magic recipe, it's all about logic :)
[12:52] <didrocks> sil2100: dee needs it because it ships a common override files that isn't different between soname though :/
[13:03] <sil2100> Trevinho, andyrock: you here?
[14:35] <sil2100> andyrock: Trevinho: could you guys look at this one when you're around? https://bugs.launchpad.net/unity/+bug/1021327
[14:46] <Mirv> hmm, compiz_discover_tests got into compiz trunk, the gsettings branch apparently still brewing until tomorrow
[15:09] <didrocks> sil2100: I just saw your email, fixing those 2 regressions are not enough
[15:10] <didrocks> there are more issues and fixes needed :)
[15:10] <didrocks> I presented them in the detail of the sprint and entitled them as blocking release issue, can you find it on the document?
[15:11] <didrocks> (I'm just telling you them now to not block trunks more than now, normally, I should just check that once everything is green)
[15:17] <popey> didrocks, can you be more specific?
[15:17] <didrocks> popey: well, I would prefer you guys going back to your note and the release wiki page to find what's missing and what you didn't check
[15:18] <didrocks> popey: I told you it at least 6 times in the past 2 weeks as a hint of something missing and told you exactly what it was during the sprint, so if you don't look at little bit, I'm not sure you will have the reflex later to look at that
[15:28] <andyrock> sil2100, ping
[15:28] <didrocks> of course, if you don't find at all, I can help, but I would prefer you to find what's missing :)
[15:28] <popey> trust me we are looking
[15:28] <sil2100> andyrock: hi! Could you look at the unity release e-mail I sent?
[15:29] <sil2100> andyrock: there are 2 bugs that might need your help ;)
[15:29] <sil2100> (from Q)
[15:29] <andyrock> sil2100, perfect let me check the email
[15:30] <andyrock> sil2100, keynav mode inside dash?
[15:30] <sil2100> andyrock: that too - but the drag issue also is a bit annoying
[15:31] <andyrock> sil2100, i can reproduce the drag issue
[15:31] <sil2100> andyrock: and it seems to be a trunk regression
[15:31] <andyrock> sil2100, also dragging nautilus icon over the launcher
[15:51] <popey> didrocks, notes scoured, what have we missed?
[15:52] <didrocks> popey: so, something really important is to check that the new release passed the distro criterias
[15:53] <didrocks> one of them is that all commits matches the criterias
[15:53] <didrocks> that's why I constantly repeat "you should look at all merge requests"
[15:53] <didrocks> 2 commits don't have tests where they should have
[15:53] <popey> erk
[15:53] <didrocks> during the sprint, I showed you this link: https://docs.google.com/a/canonical.com/document/d/1kiVPg0U7VJpHt21y-Qm9VtnLxsTmKHfBmA2B16yLGzc/edit#
[15:54] <didrocks> where I post when I see a merge which doesn't (IMHO), match the criterais
[15:54] <didrocks> criterias
[15:54] <didrocks> so a discussion with upstream should be opened to know if this can be tested
[15:54] <didrocks> (those 2 ones were only noted and I told you, "we can't release now because of this")
[15:54] <didrocks> so, this is the first point
[15:55] <didrocks> the second, is that unity doesn't build an armfh for 3 weeks: https://launchpad.net/~unity-team/+archive/staging
[15:55] <didrocks> I told it during the sprint, I think Mirv was looking at it :)
[15:55] <didrocks> but we can't release as long as all the platform we support doesn't build
[15:58] <popey> thank you
[15:58] <didrocks> yw