[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #805: SUCCESS in 7 min 4 sec: http://kci.pangea.pub/job/mgmt_merger/805/
[00:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_knotes build #92: STILL FAILING in 8 min 41 sec: http://kci.pangea.pub/job/xenial_unstable_knotes/92/
[00:16] <wxl> !testers
[00:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_knotes build #71: STILL FAILING in 8 min 53 sec: http://kci.pangea.pub/job/yakkety_unstable_knotes/71/
[00:17] <wxl> ^ we're rebuilding beta 1 to get the new frameworks and plasma in there. it could use all the testing we can get
[00:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_korganizer build #74: STILL FAILING in 9 min 7 sec: http://kci.pangea.pub/job/yakkety_unstable_korganizer/74/
[00:17] <wxl> tsimonq2: make sure to update kubuntu-devel plz
[00:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail-account-wizard build #47: STILL FAILING in 9 min 17 sec: http://kci.pangea.pub/job/yakkety_unstable_kmail-account-wizard/47/
[00:18] <tsimonq2> wxl: kthx
[00:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkgapi build #19: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_libkgapi/19/
[00:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #336: STILL FAILING in 12 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/336/
[00:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkgapi build #64: STILL FAILING in 12 min: http://kci.pangea.pub/job/zesty_unstable_libkgapi/64/
[00:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #218: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/218/
[00:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #57: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/57/
[00:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #58: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_kdb/58/
[00:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #307: NOW UNSTABLE in 33 min: http://kci.pangea.pub/job/xenial_unstable_cantor/307/
[00:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #64: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/64/
[00:51] <mparillo> wxl: Thanks for the re-building heads up.
[00:52] <mparillo> 32-bit live worked fine with the previously reported problem that I needed to enter my WEP password twice
[00:53] <mparillo> 32-bit auto-resize also worked fine, but the Install Icon in the Desktop container was marked executable, but a dialog box popped up asking what I wanted to do with it.
[01:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #41: STILL UNSTABLE in 54 min: http://kci.pangea.pub/job/yakkety_unstable_k3b/41/
[01:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #52: STILL UNSTABLE in 54 min: http://kci.pangea.pub/job/xenial_unstable_trojita/52/
[01:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #55: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/zesty_unstable_kdb/55/
[01:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #197: NOW UNSTABLE in 56 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/197/
[01:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #86: STILL UNSTABLE in 54 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/86/
 !info tellico
 I guess bots don't work on telegram :/
[01:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kexi build #67: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/yakkety_unstable_kexi/67/
[01:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #103: NOW UNSTABLE in 1 hr 7 min: http://kci.pangea.pub/job/zesty_unstable_cantor/103/
[01:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #101: STILL UNSTABLE in 1 hr 6 min: http://kci.pangea.pub/job/zesty_unstable_kopete/101/
[01:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #85: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_kdiagram/85/
[01:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpimtextedit build #107: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/zesty_unstable_kpimtextedit/107/
[01:34] <krytarik> !info tellico
[02:18] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Zesty Beta 1] has been updated (20170222)
[02:18] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop i386 [Zesty Beta 1] has been updated (20170222)
[02:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_minuet build #115: STILL UNSTABLE in 1 hr 38 min: http://kci.pangea.pub/job/yakkety_unstable_minuet/115/
[02:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #101: STILL UNSTABLE in 1 hr 49 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/101/
[02:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail-account-wizard build #48: STILL FAILING in 7 min 54 sec: http://kci.pangea.pub/job/yakkety_unstable_kmail-account-wizard/48/
[02:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_knotes build #93: STILL FAILING in 8 min 28 sec: http://kci.pangea.pub/job/xenial_unstable_knotes/93/
[02:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_knotes build #72: STILL FAILING in 8 min 57 sec: http://kci.pangea.pub/job/yakkety_unstable_knotes/72/
[02:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_korganizer build #75: STILL FAILING in 9 min 58 sec: http://kci.pangea.pub/job/yakkety_unstable_korganizer/75/
[02:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #219: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/219/
[02:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkgapi build #20: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_libkgapi/20/
[02:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #337: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/337/
[02:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkgapi build #65: STILL FAILING in 15 min: http://kci.pangea.pub/job/zesty_unstable_libkgapi/65/
[02:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #114: STILL UNSTABLE in 1 hr 46 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/114/
[02:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #97: STILL UNSTABLE in 1 hr 46 min: http://kci.pangea.pub/job/zesty_unstable_krita/97/
[02:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #118: STILL UNSTABLE in 1 hr 45 min: http://kci.pangea.pub/job/zesty_unstable_kstars/118/
[02:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #209: STILL UNSTABLE in 55 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/209/
[03:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkgapi build #34: STILL FAILING in 11 min: http://kci.pangea.pub/job/yakkety_unstable_libkgapi/34/
[03:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_minuet build #104: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_minuet/104/
[03:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #71: STILL UNSTABLE in 2 hr 0 min: http://kci.pangea.pub/job/yakkety_unstable_krita/71/
[03:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #252: STILL UNSTABLE in 1 hr 48 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/252/
[03:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #33: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_k3b/33/
[03:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkgapi build #35: STILL FAILING in 8 min 41 sec: http://kci.pangea.pub/job/yakkety_unstable_libkgapi/35/
[03:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-mime build #184: FIXED in 27 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-mime/184/
[03:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #214: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/214/
[03:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #385: STILL UNSTABLE in 47 min: http://kci.pangea.pub/job/xenial_unstable_kstars/385/
[03:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #58: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/58/
[03:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #186: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/186/
[03:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_spectacle build #97: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/zesty_unstable_spectacle/97/
[03:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_korganizer build #66: STILL FAILING in 2 min 37 sec: http://kci.pangea.pub/job/xenial_unstable_korganizer/66/
[03:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #86: STILL UNSTABLE in 57 min: http://kci.pangea.pub/job/xenial_unstable_calligra/86/
[03:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #197: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/197/
[03:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #118: STILL UNSTABLE in 1 hr 0 min: http://kci.pangea.pub/job/zesty_unstable_marble/118/
[03:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #72: STILL UNSTABLE in 1 hr 31 min: http://kci.pangea.pub/job/xenial_unstable_krita/72/
[03:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_korganizer build #67: STILL FAILING in 3 min 49 sec: http://kci.pangea.pub/job/xenial_unstable_korganizer/67/
[03:40] <ahoneybun> https://www.kde.org/announcements/plasma-5.8.6.php
[03:40] <ahoneybun> 5.8.6 out@
[03:49] <ahoneybun> !info plasma-desktop
[03:49] <ahoneybun> so we have 5.9.2 in zesty
[03:50] <ahoneybun> should update this then: https://community.kde.org/Plasma/Live_Images
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #399: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_ki18n/399/
[05:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kguiaddons build #194: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kguiaddons/194/
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kguiaddons build #378: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kguiaddons/378/
[05:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kjobwidgets build #251: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kjobwidgets/251/
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdbusaddons build #405: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kdbusaddons/405/
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemviews build #372: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kitemviews/372/
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcodecs build #381: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kcodecs/381/
[05:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcompletion build #176: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kcompletion/176/
[05:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcodecs build #266: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kcodecs/266/
[05:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdbusaddons build #269: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kdbusaddons/269/
[05:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfig build #415: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kconfig/415/
[05:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcoreaddons build #204: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kcoreaddons/204/
[05:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ki18n build #264: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_ki18n/264/
[05:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwidgetsaddons build #270: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kwidgetsaddons/270/
[05:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #372: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/372/
[05:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kconfigwidgets build #232: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kconfigwidgets/232/
[05:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjobwidgets build #102: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_kjobwidgets/102/
[05:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemviews build #101: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_kitemviews/101/
[05:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #108: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_kdbusaddons/108/
[05:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfigwidgets build #65: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_kconfigwidgets/65/
[06:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #111: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/111/
[07:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfigwidgets build #365: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kconfigwidgets/365/
[07:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwallet build #96: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/zesty_unstable_kwallet/96/
[07:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #395: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/395/
[08:56] <lordievader> Good morning
[11:07] <acheronuk> wxl: I have the latest iso now. shall do a couple of test cases later
[12:25] <BluesKaj> Hi folks
[12:30] <acheronuk> clivejo: damn. did not occur to me that calligra on s390x would produce weirdly version depends on GCC :/
[12:30] <acheronuk> I just checked the deps on a few other archs
[12:30] <santa_> good morning everyone
[12:31] <acheronuk> good <insert am/pm/evening here> santa_ :)
[12:32] <santa_> it's PM here but I didn't eat yet, so it's "morning" :)
[12:32] <santa_> http://gpul.grupos.udc.es/buildstatus_ubuntu-exp2/ubuntu-exp2_status_applications.html
[12:33] <santa_> ↑ we have several autopkgtests failures
[12:35] <acheronuk> randomly picking one....
[12:35] <acheronuk> acc                  FAIL non-zero exit status 6
[12:35] <acheronuk> which is that known issue with GCC and the headers
[12:36] <acheronuk> presumably anyway from that exit status
[12:37] <acheronuk> santa_: does your setup collate failure reasons anywhere in any form? or just a manual pick through?
[12:39] <santa_> not sure what you mean
[12:39] <santa_> but anyway, let me explain
[12:39] <acheronuk> is there a summary page say, with just test failure reasons on each package?
[12:40] <santa_> ah, well no
[12:40] <santa_> that page is automatically generated with a fork of ppa-build-status
[12:41] <santa_> but it was modified to support the autopkgtests
[12:41] <santa_> so when you click on show/hide you would see the part of the autopkgtests
[12:41] <acheronuk> ooh. the show/hide expands the results, so that is partly doin that anyway.
[12:41] <BluesKaj> Zesty beta1 desktop is unusable since it appears below the bottom panel. but beta 1 isn't at fault the previous alpha version was showing the same symptoms on my p[c 
[12:41] <acheronuk> yep. just found it
[12:42] <santa_> + it would be marked on red if it has failing autopkgtests failures
[12:43] <santa_> by the way, the code to generate the staus webpages is very awful
[12:43] <santa_> I would like to rework it in the iron hand and use a templating system such as jinja
[12:44] <santa_> and of course have a separate class to parse build logs
[12:44] <santa_> so that way it would be easier to maintain and debug
[12:46] <acheronuk> well, as long as it's not in ruby :P
[12:53] <santa_> acheronuk: hmm, indeed we had to tweak the gcc flags for the acc tests. we did it for fw and plasma, but not yet for apps
[12:56] <BluesKaj> don't think there's much point testing zesty any longer, obviously there's something seriously wrong with the graphics and I'm kinda fedup with it all 
[12:57] <BluesKaj> BBL
[13:04] <acheronuk> hmmm... BluesKaj seems to always find 'issues' I can't. not sure if that is his hardware, or something else, but no graphics trouble here (Nvidia)
[13:13] <clivejo> but the annoying thing is he won't provide any feedback as to what the problem might be
[13:14] <clivejo> so impossible to help him, when he won't even help himself
[13:24] <clivejo> did anyone catch up with Darin last night?
[13:26] <acheronuk> clivejo: he was about late afternoon, but not evening that I saw. I was not staying up late though after staging until 2:30am previous night
[13:27] <clivejo> maybe we should just push ahead
[13:28] <clivejo> Im sure another example of symbols will come up soon enough
[13:29] <clivejo> if PIM is going to drop in 17.04, we need to get them in pronto
[13:37] <acheronuk> well, it's the other symbols issues which may take some time. but fair point
[13:46] <santa_> I didn't see him yesterday
[13:47] <santa_> clivejo, acheronuk: fyi fixing the acc tests inlining issue now, I will re-schedule the autopkgtesting @ tritemio
[13:47] <acheronuk> santa_: ack
[14:04] <clivejo> santa_: nice one, thanks
[14:08] <santa_> yw
[14:09] <santa_> wrt autopkgtests I have added some initial info here https://phabricator.kde.org/w/kubuntu/autopkgtests/autopkgtests_in_kubuntu/
[14:09] <santa_> in the testsuite section we could add some general tricks to fix the thing
[14:10] <santa_> i.e. "you may need to run the tests with xvfb-run", "you may need to pass this arguments to xvfb-run", ... etc.
[14:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpimtextedit build #108: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/zesty_unstable_kpimtextedit/108/
[14:45] <clivejo> hi DarinMiller
[14:46] <DarinMiller> hi clivejo
[14:47] <clivejo> acheronuk: have you an easy way of spliting PIM out of apps?
[14:47] <clivejo> like we did before?
[14:49] <DarinMiller> Am I too late for the symbols fix?
[14:55] <santa_> DarinMiller: nope
[14:56] <santa_> DarinMiller: so whenever you are around and have time just ping me so I can explain you what's the deal with symbols files
[14:57] <DarinMiller> Excellent! I have about 4+ hours so before I must work on other stuff.  My time to today is flexibile so whenever it works for you.
[14:57] <santa_> DarinMiller: in ~ 15 minutes then?
[14:57] <DarinMiller> perfect
[14:57] <santa_> so I can gather some intel :)
[14:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #119: STILL UNSTABLE in 1 hr 6 min: http://kci.pangea.pub/job/zesty_unstable_marble/119/
[14:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[14:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-search build #86: FIXED in 36 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-search/86/
[15:12]  * clivejo shakes head
[15:12] <clivejo> I think we are in for a drowning
[15:18]  * DarinMiller throws clivejo a float ring http://imgur.com/a/mVZjt
[15:19] <DarinMiller> Storm headed your way?
[15:19] <clivejo> think so
[15:22] <clivejo> the frogs are on the move
[15:27] <DarinMiller> brb
[15:31] <santa_> ok, I'm back with some intel: https://phabricator.kde.org/w/kubuntu/packaging/symbols-files/
[15:32] <santa_> DarinMiller: whenever you are on the keyboard again just ping me, so I can guide you with the thing
[15:38] <DarinMiller> I am back
[15:41]  * DarinMiller is reaading the phab links posted by santa_
[15:42] <santa_> DarinMiller: yes, before doing that, because there's a myriad of things to read there I would like to give you a summary
[15:42] <DarinMiller> ok, sure
[15:42] <santa_> first of all, are you familiar with C or C++ programming?
[15:43] <DarinMiller> not really.  I have written a C "hello world" but that's about it.
[15:43] <DarinMiller> I am familar with Java (but sitll fairly new)
[15:44] <santa_> ok, that would be - hopefully - enough for now
[15:44] <santa_> so let's start with the basic ideas
[15:44] <santa_> you probably know what's the API of a library, correct?
[15:45] <DarinMiller> Yes, I have read the debian definition of api and abi, so I have a general idea....
[15:46] <santa_> allright so you also know about the ABI, that's great
[15:46] <santa_> do you know what's an ABI breakage?
[15:46] <DarinMiller> vaguely.
[15:47] <santa_> but probably have a clear idea of what's breaking the API of a library
[15:48] <DarinMiller> Yes, I think so.
[15:48] <santa_> ok, well breaking the ABI is something similar, but at the binary level
[15:49] <DarinMiller> API breakage is when the developer changes the way methods interact with a class?
[15:49] <santa_> for instance
[15:49] <santa_> yes
[15:49] <santa_> when a symbol is removed from the ABI, that's an ABI break. that simple
[15:50] <DarinMiller> Oh, ok
[15:50] <santa_> and you can do that, for instance, changing the number or type of parameters of a public function
[15:51] <santa_> an API breakage in a C++ library would also produce an ABI breakage
[15:52] <santa_> however, you can keep API compatibility and break the ABI
[15:52]  * DarinMiller assumea that symbols are not auto generated when packages built, and thus the issue...
[15:52] <santa_> nope
[15:52] <DarinMiller> assumes^
[15:53] <santa_> if you have a function that accepts an 'int' as a parameter and then you change it for a 'long' you keep the API but you break the ABI
[15:53] <santa_> so the symbols files are, indeed, maintained by us
[15:54] <DarinMiller> oh, oh, oh that makes sense
[15:54] <santa_> I presume you are not familiar yet with the symbols files, hence why we are having this conversation
[15:55] <DarinMiller> correct
[15:55]  * acheronuk lurks
[15:55] <santa_> ok, so the questions are: ¿what are the symbols files? and ¿what's the point of having them?
[15:56] <santa_> the answer for the first one is, in short: they are files listing all the binary symbols exported by a library
[15:57] <DarinMiller> From what I understand, they are an intermeidate build of "stuff" that is needed to build a package.
[15:57] <santa_> what you mean by intermediate?
[15:58] <DarinMiller> I assume they require extra time to generate and thus the reason they are not regenerated with every build (guessing here).
[15:58] <santa_> it's a bit more complicated
[15:59] <santa_> the answer to ¿what's the point of having them? will reply to that
[16:00] <santa_> the primary purpose of having symbols files is creating versioned dependencies automatically
[16:00] <santa_> and there's a secondary purpose and it's checking that the ABI wasn't broken since the previous version of the library
[16:01] <santa_> so now, let me go a bit deeper with these 2 things
[16:01] <DarinMiller> so we know when thing are broken, but auto fixing is difficult?
[16:02] <santa_> auto fixing shouldn't be done, because we need to check when the ABI breaks
[16:02] <santa_> and if so, do something about it
[16:02] <santa_> that something could be
[16:02] <santa_> a) patching the thing to restore the ABI
[16:02] <santa_> or
[16:03] <santa_> b) using the debian abi manager to handle the situation
[16:03] <santa_> that's explained in the last 2 sections of this: https://phabricator.kde.org/w/kubuntu/packaging/symbols-files/
[16:05] <santa_> going back to the primary purpose of the symbols files, as you can see if you open any symbols files each symbol has a version
[16:05] <santa_> that version is the package version where the symbol appeared in the library
[16:06] <santa_> so when you build a package against that library, it would have a dependency on the corresponding library version
[16:06]  * DarinMiller is reviewing dophins symbol list...
[16:06] <santa_> that is done at build time by dh_shlibdeps if I recall correctly
[16:08] <santa_> dh_shlibdeps expands the ${shlibs:Depends}
[16:08] <santa_> so since you are seeing that symbol file....
[16:09] <santa_> DarinMiller: pick the first symbol and try this:
[16:09] <DarinMiller> makes sense
[16:09] <santa_> $ c++filt _ZN21KVersionControlPlugin11infoMessageERK7QString
[16:09] <santa_> KVersionControlPlugin::infoMessage(QString const&)
[16:10] <santa_> c++filt translates the thing into C++
[16:10] <santa_> so now, let's say we have a program linking against that library
[16:10] <DarinMiller> Output: KVersionControlPlugin::infoMessage(QString const&)
[16:11] <santa_> as expected
[16:13] <santa_> so if we have a program using that function, its package would have a dependency against libdolphinvcs5 (>= 4:15.07.90)
[16:14] <santa_> DarinMiller: now supose that that function is gone, what would happen?
[16:14] <DarinMiller> I suspect the builder process would be quite angry.
[16:15] <santa_> the first thing would be that the dolphin source package would fail to build
[16:16] <santa_> that in the first place
[16:17] <santa_> like this other package: https://launchpadlibrarian.net/307290750/buildlog_ubuntu-zesty-amd64.akonadi-calendar_4%3A16.12.2-0ubuntu1~ubuntu17.04~ppa1_BUILDING.txt.gz
[16:18]  * DarinMiller sees dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below
[16:18] <santa_> and you can also see a diff
[16:19] <santa_> and the word MISSING
[16:19] <santa_> as an exercise, can you tell me which C++ function is gone in that library?
[16:19] <DarinMiller> see it
[16:20] <DarinMiller> MISSING: 4:16.12.2-0ubuntu1~ubuntu17.04~ppa1# _ZNK7Akonadi12CalendarBase15childIncidencesERKx@Base 15.07.90
[16:20] <DarinMiller> + 4 others
[16:20] <santa_> I'm seeing just one
[16:20] <santa_> the other stuff is the diff context
[16:21] <santa_> so to sum up that diff
[16:21] <DarinMiller> oh, + _ZNK7Akonadi12CalendarBase15childIncidencesEx@Base 4:16.12.2-0ubuntu1~ubuntu17.04~ppa1
[16:21] <santa_> +#MISSING: 4:16.12.2-0ubuntu1~ubuntu17.04~ppa1# _ZNK7Akonadi12CalendarBase15childIncidencesERKx@Base 15.07.90
[16:21] <santa_> ↑ this one is gone
[16:21] <clivejo> he wants you to lookup the C function
[16:22] <santa_> + _ZNK7Akonadi12CalendarBase15childIncidencesEx@Base 4:16.12.2-0ubuntu1~ubuntu17.04~ppa1
[16:22] <santa_> ↑ this one is new
[16:22] <santa_> DarinMiller: so, like clive says, which c++ functions are those?
[16:25] <DarinMiller> Akonadi::CalendarBase::childIncidences(long long const&) const
[16:26] <clivejo> so thats the old function, whats the new one?
[16:28] <DarinMiller> Akonadi::CalendarBase::childIncidences(long long) const
[16:28] <DarinMiller> no cont in the new one
[16:29] <clivejo> do you see whats changed there?
[16:29] <DarinMiller> const&
[16:29] <santa_> yep
[16:29] <santa_> so that's probably an ABI break
[16:29] <santa_> I will try to explain later why I say 'probably'
[16:30] <santa_> so going back to what I was explaining later
[16:30] <DarinMiller> possible "optional" param?
[16:31] <DarinMiller> ok
[16:31] <santa_> we will see that
[16:31] <santa_> * so going back to what I was explaining earlier
[16:31] <santa_> what happens now?
[16:31] <santa_> 1. the package is failing to build
[16:32] <santa_> 2. if you update the symbols file and you remove that symbol from the file the package will build BUT
[16:32] <santa_> BUT
[16:33] <clivejo> santa_: sorry to interupt but would there not be a third or c) option to check for a so bump?
[16:33] <DarinMiller> so remove _ZNK7Akonadi12CalendarBase15childIncidencesERKx and replace with  _ZNK7Akonadi12CalendarBase15childIncidencesEx?
[16:33] <santa_> clivejo: if there's an soname bump we would have to do more than that to get the package building again
[16:34] <santa_> clivejo: because the file naming would be different so it would fail @ dh_install
[16:35] <santa_> clivejo: so we would have to rename the package, update install files and finally create a new symbols file (or update the existing one, both approaches are fine)
[16:36] <santa_> DarinMiller: nope. that's exactly what I wanted to explain
[16:36] <santa_> if you do that the package will build
[16:36] <santa_> BUT
[16:36] <santa_> any existing binary using it would crash, probably
[16:37] <DarinMiller> oh, Ok.
[16:37] <santa_> you would need to rebuild them to fix that
[16:37] <santa_> DarinMiller: so, the correct solution for this case is
[16:37] <santa_> 1. check if this is an ABI break
[16:38] <santa_> 2. if so, use the debian ABI manager
[16:39] <santa_> about the 1. you have to check the previous package
[16:39] <santa_> locate the funxtion in question
[16:39] <santa_> * function
[16:39] <santa_> you can do this with the excellent 'ack' program
[16:40] <santa_> then you have to confirm that it's indeed a public function
[16:40] <santa_> and if so, check if the header where it is
[16:40] <santa_> and check if that header is installed
[16:41] <wxl> thx acheronuk :)
[16:41] <santa_> beucase if the header is not installed, that would make the function effectively private
[16:41] <santa_> * because
[16:42] <santa_> I already did all of this and I think I can confirm it's an ABI break
[16:42] <clivejo> can you show how to use ack?
[16:42] <DarinMiller> pardon my greeness: where do I find the ack program?
[16:42] <santa_> of course, 1 sec
[16:42] <DarinMiller> I looked in ka and in repos..
[16:42] <DarinMiller> all I see is ack-grep
[16:43] <santa_> yep, pkgname is ack-grep
[16:43] <clivejo> !info ack
[16:43] <DarinMiller> installing now..
[16:44] <wxl> what does that do that grep doesn't?
[16:44] <santa_> the program name is either 'ack-grep' (alias) or 'ack' for yakkety
[16:44] <santa_> I think in zesty they dropped the alias
[16:44] <santa_> so I'm executing it as 'ack'
[16:44] <santa_> wxl: shows context and you don't have to feed in it the list of files to search
[16:45] <wxl> well grep can show context
[16:45] <santa_> hmm not sure about the context let me check
[16:45] <clivejo> santa_: so you would grab the source package from the archive and use ack on that?
[16:46] <BluesKaj> ok running plasma 5.9.2 Zesty beta1, all seems well so far, after doing a complete clean install 
[16:46] <santa_> clivejo: yep
[16:46] <wxl> BluesKaj: did you mark the test case successfully completed?
[16:46] <santa_> you just have to type ack 'string', and that's it
[16:47] <BluesKaj> couldn't save my messed up config files 
[16:47] <clivejo> do you have a script to do that?
[16:47] <clivejo> or just do it manually?
[16:47] <BluesKaj> in the previous try ...my /home die was the culprit
[16:47] <BluesKaj> dir
[16:47] <santa_> I usually do it manually, but we could add something in ka
[16:48] <BluesKaj> wxi where to do that?
[16:48] <santa_> clivejo: but more often, I just browse my ~/kde-ftp dir
[16:48] <santa_> because I would have the upstream tarballs there already
[16:49] <santa_> so I just have to check what's the latest version with LP
[16:49] <clivejo> just trying to allow Darin to follow this himself
[16:49] <santa_> k
[16:49] <clivejo> so do a "apt-get source akonadi-calendar" to grab the source?
[16:50] <santa_> sure, you can do that if you are on zesty
[16:50]  * DarinMiller darin is trying to follow, wonder why apt-get source and not uscan....
[16:50] <clivejo> I think he is
[16:51] <santa_> DarinMiller: uscan would download the latest stable version
[16:51] <santa_> which would be 16.12
[16:51] <santa_> we have to check the 16.04.x
[16:51] <DarinMiller> current box is zesty,  so apt-get'ing now....
[16:52] <clivejo> !info akonadi-calendar
[16:52] <DarinMiller> ditto
[16:53] <wxl> BluesKaj: on the iso tracker. that's where all the testing is recorded
[16:53] <wxl> BluesKaj: http://iso.qa.ubuntu.com/qatracker/milestones/373/builds
[16:53] <clivejo> its a lib
[16:53] <clivejo> !info libkf5akonadicalendar-dev
[16:53] <clivejo> built from the akonadi-calendar source package
[16:54] <santa_> I guess the bot doesn't work with source package names
[16:54] <clivejo> nope, wish it would though!
[16:54] <santa_> https://launchpad.net/ubuntu/+source/akonadi-calendar
[16:55] <wxl> ok i see why ack is better
[16:55] <DarinMiller> apt-get source libkf5akonadicalendar-dev produces:
[16:55] <DarinMiller> Picking 'akonadi-calendar' as source package instead of 'libkf5akonadicalendar-dev'
[16:55] <DarinMiller> E: Unable to find a source package for akonadi-calendar
[16:55] <clivejo> DarinMiller: apt-get source akonadi-calendar should work
[16:56] <santa_> DarinMiller: do you have the deb-src lines enabled in your sources?
[16:56] <DarinMiller> uh, just sec....
[16:56] <DarinMiller> just thought of that :)
[16:58]  * DarinMiller is waiting for the entire internet to download....
[16:58] <DarinMiller> that's better, source dl'd
[16:58] <wxl> BluesKaj: you grok all that or you have questions?
[17:00]  * DarinMiller thinks he needs to enable staging to pull down 16.12.2 as 16.04 was dl'd
[17:00] <acheronuk> git clone kde:akonadi-calendar; cd akonadi-calendar; git checkout v16.04.3
[17:00] <wxl> s/;/&&/
[17:00] <acheronuk> ^^ would get KDE repo's src
[17:00] <clivejo> 16.04.3 is the version in zesty currently
[17:00] <santa_> or alternatively dget https://launchpad.net/ubuntu/+archive/primary/+files/akonadi-calendar_16.04.3-0ubuntu1.dsc
[17:01] <santa_> you can do it any way you prefer
[17:01] <wxl> ^^ i prefer that since the subsequent commands only execute if the previous command succeeds
[17:01] <acheronuk> wxl: point taken
[17:01] <santa_> that's up to you
[17:02]  * acheronuk goes back to lurking and playing with 'ack'
[17:03]  * DarinMiller nm, realizes v16.04 is what failed...
[17:03] <BluesKaj> wxi , mucking about ubuntu one is a pita :/
[17:04] <wxl> BluesKaj: yeah well once you have it set up you're pretty much good to go :)
[17:04] <santa_> https://paste.kde.org/pmtqtldug
[17:05] <santa_> ↑ if you do that yourself you would see a nice colored output probably
[17:05] <wxl> and you can limit by type too, which is nice
[17:05] <DarinMiller> yes, that is slick
[17:06] <clivejo> have upstream been informed of this break?
[17:06] <santa_> clivejo: nope
[17:06] <santa_> I think with these apps libs we could just go ahead with the abi manager
[17:07] <santa_> if it were from frameworks, that would be a different story
[17:07] <clivejo> santa_: is there any way to find what calls that publicially?
[17:07] <DarinMiller> mine ack looks different: https://paste.ubuntu.com/24047516/
[17:08] <clivejo> you have the full source, including debain packaging
[17:09] <wxl> DarinMiller: probably because santa_ has an .ackrc
[17:09] <clivejo> so its picking up the symbols
[17:09] <wxl> or that :)
[17:09] <santa_> nah, I did with the source package
[17:09] <wxl> .ackrc then?
[17:09] <santa_> but I think they are the same contents, in different order
[17:10] <santa_> wxl: I'm on yakkety he is on zesty, so probably the file order is kind of random and different for each one
[17:10] <wxl> ah possibly
[17:10] <wxl> or there's different default options
[17:10] <santa_> yeah, maybe
[17:11] <wxl> there is --sort-files
[17:11] <santa_> anyway, the whole point of this is
[17:11] <santa_> src/calendarbase.h
[17:11] <santa_> 101:    KCalCore::Incidence::List childIncidences(const QString &parentUid) const;
[17:11] <santa_> 108:    KCalCore::Incidence::List childIncidences(const Akonadi::Item::Id &parentId) const;
[17:12] <acheronuk>  Akonadi::CalendarBase::childIncidences(long long const&) const
[17:12] <santa_> so it's in calendarbase.h, which is also the obvious file name
[17:13] <acheronuk> for comparison
[17:14] <santa_> acheronuk: that must be in the new 16.12 package
[17:14] <santa_> or are you @ 16.04 source?
[17:15]  * DarinMiller did not know .h vs .cpp differences until he read: http://stackoverflow.com/questions/875479/what-is-the-difference-between-a-cpp-file-and-a-h-file
[17:15] <wxl> DarinMiller: if you had started at them long enough you would have figured it out :)
[17:16] <santa_> so, now to find out if the *.h file is installed a possible way is doing this @ zesty:
[17:16] <santa_> $ apt-file show libkf5akonadicalendar-dev | grep calendarbase.h
[17:16] <santa_> libkf5akonadicalendar-dev: /usr/include/KF5/akonadi/calendar/calendarbase.h
[17:17] <santa_> ↑ to get that working you must install apt-file
[17:17] <santa_> + doing apt-file update once installed
[17:18] <santa_> alternatively you can check the build logs on launchpad; there's a file listing for each binary package
[17:18] <acheronuk> santa_: 'for comparison' with the 16.12.2 buildlog. sorry to confuse 
[17:18] <DarinMiller> apt-file installed (must of been part of some dev package set)
[17:18] <santa_> acheronuk: ah, ok :)
[17:19] <santa_> so now we can confirm this is indeed an ABI break
[17:19] <santa_> clivejo, acheronuk: so let's just use the debian abi manager, any objections?
[17:20] <acheronuk> fine here. I have notes from when we did it on prison ages ago, but a new iteration is great
[17:22] <santa_> "offtopic": while we speak I'm seeing here in the other monitor some akonadi unit tests hanging like hell :(
[17:24] <wxl> acheronuk: you were incarcerated? :)
[17:24] <acheronuk> santa_: BTW kwallet in FW builds with the new gpgme. just a different -dev name to add to the deps. I saw you tried it yesterday
[17:24] <acheronuk> just a few extra symbols when I tried in my ppa
[17:25] <santa_> yes, in the official ppa too
[17:25] <santa_> I ddin''t push the changes yet, btw
[17:26] <acheronuk> wxl: yes. here. on this channel. I've not escaped yet! :P
[17:26] <acheronuk> santa_: ah. right. I got emails about the build failure, but not the success as those don't happen.
[17:26] <wxl> acheronuk: just like clivejo and he even formally stated he was leaving ;)
[17:27] <acheronuk> wxl: clive who?
[17:27] <wxl> XD
[17:27]  * acheronuk looks around.
[17:27] <santa_> it's difficult to leave
[17:27] <acheronuk> ** ghosties **
[17:27] <santa_> regarding the usage of the abi manager https://phabricator.kde.org/w/kubuntu/packaging/symbols-files/ there's a couple of notes here
[17:28] <santa_> DarinMiller: so, reading the last 2 sections of the wiki page, do you think you would be able to produce a patch for akonadi-calendar?
[17:29] <acheronuk> I found that manual only makes sense once you've used it. sort of the wrong way around, but there you go
[17:29] <DarinMiller> I will give it a shot...
[17:30] <santa_> k, just try to follow that README and if you can't just give us a shout so we can help you
[17:30] <DarinMiller> will do
[17:31] <santa_> hint: you will have to use that X-CMake-Target thing
[17:31] <santa_> unfortunately the autodetection for that is kind of broken since frameworks
[17:48] <santa_> acheronuk: wrt kwallet-kf5/gpgme this is what I have here https://paste.kde.org/pcaln0ces
[17:48] <santa_> the new symbols seem to be just leaks
[17:49] <santa_> thefore I think we won't need to rebuild anything against a new kwallet package with gpgme enabled again
[17:49] <santa_> * therefore
[17:50] <acheronuk> santa_: libgpgme11-dev is not in v1.8 ?
[17:51] <acheronuk> santa_: so is your build grabbing one -dev file from v1.7 in release and another from v1.8 in proposed or the ppa?
[17:52]  * acheronuk goes to look
[17:56] <acheronuk> santa_: forget that
[17:56] <acheronuk> I forgot that they added....
[17:56] <acheronuk> Provides:
[17:56] <acheronuk>  libgpgme11-dev (= ${binary:Version})
[17:56] <acheronuk> to libgpgme11
[17:57] <acheronuk> so either will do, and still get the new version
[17:57] <acheronuk> santa_: so yes, that is likely what I would get if I ran symbolshelper
[18:10] <santa_> acheronuk: ack, I think I should change the bd fo libgpgme-dev, so doing that and uploading to the ppa to test the changes...
[18:11] <acheronuk> santa_: that is what I added on my build, yes
[18:56] <santa_> acheronuk: changes pushed to git. I have just seen in the status page that we have a couple of packages in orange because of qttexttospeech; maybe we should add the build depend (now that we have qttexttospeech) and upload fixed versions of these 2 to the archive?
[18:57] <santa_> these 2 = knotifications, ktextwidgets
[18:58] <wxl> man that freaking blank screen bug ugh
[18:59] <acheronuk> santa_: does adding qttexttospeech add new features?
[18:59] <acheronuk> add/enable etc
[18:59] <santa_> acheronuk: according to cmake it should. concerned if that goes against the freeze?
[19:00] <acheronuk> santa_: yep.
[19:01] <santa_> acheronuk: maybe we should ask in -release/ file an ffe?
[19:02] <acheronuk> santa_: well, we can try adding it in staging 1st. see what it does, and what exactly it enables. that qttexttospeech build is a Qt 5.8 one from experimental I think, so I'm not even sure it won't just crash and burn
[19:06] <santa_> acheronuk: oh, ok. I wasn't aware of that I will leave that for later since we have more important things to do. I tought it would be a no-brainer
[19:09] <acheronuk> maybe test in KCI builds instead then? I haven't noticed anything lacking/broken not having it, so my conservative instinct says it's something to look at enabling when it's more mature and we are using the rest of the Qt 5.8 stack
[19:10] <santa_> probably
[19:10] <santa_> feel free to go ahead with that
[19:10]  * santa_ looks @ the other pim fatbfs'ing libs instead....
[19:15] <acheronuk> clivejo: that GCC build??? "Started 1 day, 2 hours, 42 minutes, 20.4 seconds ago."
[19:17]  * clivejo wonders what it is doing
[19:17] <acheronuk> wxl: is testing OEM install ok from the grub menu? on Vbox I cant trigger it in the way the test case asks 
[19:18] <acheronuk> clivejo: very very very very very SLOWLY FTBFS I would imagine
[19:18] <acheronuk> bit like a car crash i shown in slow motion......
[19:27] <wxl> acheronuk: let me guess: the F4 key doesn't respond
[19:28] <acheronuk> wxl: yes, does nothing in ubiquity as booted normally
[19:29] <wxl> you mean you can't get to the grub menu? the testcase is lacking the instruction to hold down shift at boot
[19:31] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[19:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #220: FIXED in 40 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/220/
[19:31] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[19:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwallet build #97: FIXED in 41 min: http://kci.pangea.pub/job/zesty_unstable_kwallet/97/
[19:31] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[19:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #396: FIXED in 41 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/396/
[19:32] <acheronuk> wxl: hah. the test case is unclear in so many ways. so yes/no
[19:33] <acheronuk> I'll try again in a min in the way I guess they mean
[19:33] <wxl> acheronuk: and it's a general test case, too >:(
[19:33] <wxl> DarinMiller was supposed to make us a kubuntu specific one..\
[19:44] <acheronuk> wxl: OEM is a fail for me in VBox. just goes to a black screen at the finish. even after a forced reboot
[19:45] <wxl> acheronuk: that was my experience, too, but others have tested on real hardware with no probs
[19:46] <acheronuk> wxl: wnat me to add it as a fail and comment then? or just leave it for someone with real hardware they can test on?
[19:46] <wxl> acheronuk: add it as a fail with a comment as mparillo did
[19:51] <acheronuk> done
[19:51] <wxl> thx
[20:02]  * santa_ is trying to fix pimcommon...
[20:07] <wxl> maybe we should make OEM mode optional as xubuntu does
[20:09] <wxl> you're on vbox right acheronuk ?
[20:10] <acheronuk> wxl: for this sort of testing, yes
[20:10] <ahoneybun> unixstickers is having a sale on the KDE sticker kit
[20:12] <wxl> acheronuk: would you mind testing that in kvm?
[20:13] <wxl> acheronuk: that = kvm btw
[20:13] <wxl> OOH THEY HAVE TMUX STICKERS
[20:15] <wxl> we need kubuntu shirts on there
[20:16] <genii> My Kubuntu polo shirt has tears in it now :(
 do we really?
 https://www.hellotux.com/kubuntu
 @wxl23
 I like the Mate one better: https://www.hellotux.com/ubuntu_mate_polo_shirt_green
[20:19] <genii> I don't see any blue ones
[20:20] <wxl> i don't love polos
 not saying I do either but still
[20:21] <wxl> so true https://www.unixstickers.com/stickers/coding_stickers/java-hispter-jhipster-shaped-sticker
[20:23] <acheronuk> wxl: kvm doesn't want to work here. changes the permissions on the .iso, then complains it can't read it due to wrong permissions
[20:23] <wxl> acheronuk: bah, shoot.
[20:24] <wxl> anyone got a kvm up and running?
[20:24] <santa_> wxl: me. qemu/kvm with virt-manager here
[20:25] <wxl> santa_: could you test the OEM install of beta1?
[20:25] <santa_> wxl: sure, link?
[20:25] <wxl> santa_: amd64 i assume?
[20:25] <santa_> wxl: yep
[20:25] <acheronuk> wxl: hmm. copying to a different drive seemed to help. weird
[20:25] <wxl> santa_: http://iso.qa.ubuntu.com/qatracker/milestones/373/builds/143162/testcases/1305/results
[20:28] <wxl> so do we get a discount on thsoe?
[20:28] <wxl> if not maybe we should take advantage of the sale and order a bunch
[20:29] <wxl> $89 gets us $5 off shipping, too
[20:29] <acheronuk> ok. and that boots to a black screen. there ends my patience with kvm. sorry
[20:29] <wxl> ^^ that might be good to request of kubuntu fundage
[20:30] <wxl> acheronuk: initial boot?
[20:30] <santa_> wxl: downloading, thanks for taking care of the isos
[20:30] <wxl> santa_: np
[20:34] <acheronuk> wxl: well, I have a panel. nothing else
[20:35] <wxl> acheronuk: yeah well thanks for trying. santa_ will have to take care of it :) meanwhile, you working on the other cases?
[20:38] <santa_> regarding the complaints of perms, are you using virt-manager too acheronuk?
[20:39] <acheronuk> santa_: I was
[20:39] <santa_> but not anymore? why?
[20:41] <acheronuk> trying other stuff for now. never like that very much anyway
[20:42] <wxl> santa_: fwiw flocculant of xubuntu fame says he has had no problem recently with kvm
[20:42] <santa_> aha
[20:42] <santa_> for me it's working better than ever
[20:43] <wxl> santa_: so if you can confirm that, then i'll just assume it's a vbox issue
[20:43] <santa_> virtualbox. on the other hand, is giving me black screens
[20:43] <wxl> anyone capable of testing on real hardware?
[20:43] <DarinMiller> wxl: Fixing the Kubuntu OEM setup guidelines now and a saw the black screen for the first time.
[20:43] <wxl> DarinMiller: real hardware or vbox?
[20:43] <DarinMiller> wxl: it's just plasma...
[20:43] <DarinMiller> vbox
[20:43] <wxl> phew
[20:43] <santa_> wxl: btw virtualbox precisely is giving me black screens with
[20:44] <santa_> * yakkety iso
[20:44] <santa_> * plasma 5.9
[20:44] <santa_> (at least)
[20:44] <wxl> santa_: yeah actually i had problems with the yakkety install on vbox
[20:44] <santa_> so I switched to virt-manager recently
[20:44] <DarinMiller> resize the window to see the bottom panel or use krunner to launch the terminal.  The killall plasmashell && plasmashell &
[20:45] <santa_> as I said is working very well since QXL is the default for the spice monitors
[20:45] <wxl> DarinMiller: resize the window? with a blank screen? XD
[20:45] <DarinMiller> the vt window
[20:45] <DarinMiller> vbox window
[20:46] <wxl> oh interesting
[20:47] <DarinMiller> once plasma was restarted on my box, everything was OK except the desktop folder was not displayed (no folder usually happens after 2nd OEM boot...)
[20:47] <acheronuk> are none of these test cases actually up to date for current ubiqity? sigh.......
[20:48] <wxl> DarinMiller: that's because our default is not folder view
[20:48] <wxl> i.e. kde-specific problem
[20:48] <wxl> acheronuk: well they are general ones, possibly appropriate for ubuntu ubiquity
[20:49] <acheronuk> and the folder containment overlapping the desktop toolbox in the live session is getting on my nerves :P
[20:49] <DarinMiller> live sessions shoud have desktop folder displayed (but understood regarding default views postinstalls).
[20:49] <wxl> personally i think folder view makes a lot more sense
[20:51] <wxl> to be clear, how do you resize the window?
[20:51] <DarinMiller> the vbox window?
[20:51] <wxl> yeah
[20:52] <DarinMiller> I used my mouse.
[20:52] <DarinMiller> normal window resize.
[20:52] <wxl> not making any difference for me
[20:53] <DarinMiller> no black background with a panel at the bottom?
[20:53] <wxl> no, i just have everything black
[20:53] <wxl> plasmashell ain't running
[20:53] <DarinMiller> for grins, try to lauch krunner (alt-spacebar) when the vbox window has focus.
[20:53] <wxl> i tried a bunch of things and no go
[20:54] <DarinMiller> ok my "black screen" is different than yours.
[20:54] <wxl> i guess so
[20:59] <ahoneybun> wxl: https://code.launchpad.net/~aaronhoneycutt/ubiquity-slideshow-ubuntu/zesty
[20:59] <ahoneybun> updating the kubuntu-slideshow.py to PyQt5
[20:59] <wxl> ooooh :)
[20:59] <ahoneybun> got it to open and run but no slides
[21:00] <wxl> no slides like you haven't made the slides or it simply didn't work?
[21:00] <acheronuk> ahoneybun: where are those kubuntu stickers?
[21:00] <ahoneybun> wxl: the slides are there
[21:00] <ahoneybun> just not loading
[21:00] <ahoneybun> acheronuk: stickers?
[21:00] <acheronuk> ahoneybun: oh. KDE. not kubuntu
[21:01] <ahoneybun> acheronuk: KDE yep
[21:01] <ahoneybun> valorie has some Kubuntu ones
[21:01] <acheronuk> hah. there is nothing kubuntu at all on there. they must think we are dead.
[21:01] <wxl> ahoneybun: have you tried checking in at #ubuntu-installer?
[21:01] <wxl> acheronuk: more likely we haven't reached out to them
[21:01] <ahoneybun> I'm in there wxl
[21:02] <ahoneybun> well Ubuntu just got some stickers on unixstickers
[21:02] <wxl> brb tacos are calling my name
[21:12] <ahoneybun> wxl: 
[21:12] <ahoneybun> http://imgur.com/a/Rj3OA
[21:12] <ahoneybun> using the test-slideshow.sh
[21:19] <ahoneybun> http://bazaar.launchpad.net/~aaronhoneycutt/ubiquity-slideshow-ubuntu/zesty/revision/762
[21:50] <wxl> ahoneybun: i'm not ubiquity dev fwiw :)
 And I start training to be one on Saturday :P
 @tsimonq2, if there *anything* you're not trying to be?
 *is
 Oh be quiet
[21:53] <wxl> does anyone know how to directly call the settings for a particular panel? one of my two panels shows it and immediately makes it disappear
 just joking. :P
[21:54] <wxl> or maybe there's a config file i could just edit to my liking?
[21:56] <wxl> restarting plasma did the trick
 I know wxl
 You were just asking about the number thing
 Version numbrr
[22:02] <clivejo> anyone ever experienced this bug - https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/997200
[22:05] <wxl> right right
[22:32] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #91: FIXED in 23 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/91/
[22:32] <DarinMiller> wxl: I created "Kubuntu specific" OEM update mangaer checklist, but I have no idea how to do a bzr mp.
[22:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pimcommon build #83: FIXED in 23 min: http://kci.pangea.pub/job/xenial_unstable_pimcommon/83/
[22:33] <wxl> DarinMiller: you can do it all through the web gui if you want. just push it to your personal repo to begin
[22:33] <clivejo> DarinMiller: https://packaging.neon.kde.org/applications/libkgapi.git/commit/?h=Neon/unstable&id=5f436b6fe6601410e5b9538491a0d0b3a93bf213
[22:37] <DarinMiller> clivejo: so they even renamed the -dev and -data references also.  Everything else was very similar to what I had proposed.
[22:38] <clivejo> I personally would have kept libkf5gapi-dev.install
[22:38] <clivejo> and installed those kf5 named cmake files there
[22:40] <clivejo> santa_: what would you do?
[22:43] <clivejo> DarinMiller: you wanna generate a MP for that now?
[22:44] <santa_> clivejo: I would need a bit more of context, this package isn't in apps 16.12 yet, correct?
[22:44] <clivejo> correct
[22:45] <clivejo> its currently a stand alone package
[22:45] <santa_> so you are working on it for the kci?
[22:45] <clivejo> !info libkf5gapi-dev
[22:45] <clivejo> yes
[22:45] <clivejo> upstream are moving in into applications
[22:46] <clivejo> and have renamed the libs
[22:46] <clivejo> I asked Darin to have a look at it
[22:46] <santa_> ok, let me check debian
[22:47] <clivejo> KDE Neon made this commit - https://packaging.neon.kde.org/applications/libkgapi.git/commit/?h=Neon/unstable&id=5f436b6fe6601410e5b9538491a0d0b3a93bf213
[22:47] <santa_> allright
[22:47] <santa_> https://packages.qa.debian.org/libk/libkgapi.html
[22:47] <santa_> https://anonscm.debian.org/git/pkg-kde/kde-extras/libkgapi.git
[22:47] <santa_> https://anonscm.debian.org/git/pkg-kde/kde-extras/libkgapi.git/commit/?id=5f436b6fe6601410e5b9538491a0d0b3a93bf213
[22:48] <santa_> clivejo: I would merge with the debian master branch
[22:48] <clivejo> due to moving into apps they have renamed the libs from libKF5GAPIBlogger > libKPimGAPIBlogger
[22:49] <santa_> aha
[22:49] <clivejo> most of it I agree with
[22:49] <santa_> so, yes, I would follow neon/debian
[22:49] <clivejo> bar the transitional cmake files in the new -dev package
[22:49] <clivejo> usr/lib/*/cmake/KF5GAPI/KF5GAPIConfig.cmake etc
[22:50] <DarinMiller> wxl: I have no idea how go from:   bzr branch lp:ubuntu-manual-tests to   dput -f ppa:darinsmiller/kubuntu-docs <something?>
[22:50] <clivejo> in my attempt at this I kept libkf5gapi-dev.install with usr/lib/*/cmake/KF5GAPI/
[22:50] <DarinMiller> wxl: nor do I know how or where the to upload via the web.
[22:51] <wxl> DarinMiller: if it was git, you'd git push, right? same deal. :)
[22:51] <wxl> dput is for package uploads
[22:51] <wxl> assumedly you shouldn't have a full package, but simply a bit of code
[22:52] <DarinMiller> just a modified text file
[22:52] <DarinMiller> Actually a brand new file as I did not want to stomp on the old one.
[22:52] <wxl> yes that's correct
[22:52] <DarinMiller> I did the bzr add and commit but then realizied I did not know where to push if for an mp.
[22:53] <wxl> so bzr push lp:darinsmiller/something-or-other
[22:53] <wxl> and then go to the page in your code and propose for merging
[22:53] <clivejo> my logical is that our old stuff will have build dep on libkf5gapi-dev
[22:53] <wxl> sorry lp:~darinsmiller
[22:54] <clivejo> which can be removed once everything is using the new lib names
[22:54] <wxl> sorry lp:~darinsmiller/ubuntu-manual-tests would make the most sense of course :)
[22:54] <wxl> as an example, here's the results of a change i made to the loco-team-portal and then requested a merge https://code.launchpad.net/~wxl/loco-team-portal/more-details
 my logical is that our old stuff will have build dep on libkf5gapi-dev
[22:55] <wxl> my logical's bigger than yous
[22:55] <clivejo> logic
[22:55] <santa_> you have to add some dummy transitional packagers
[22:55] <santa_> * packages
[22:56] <santa_> we have enough dummy packagers! XD
[22:56] <santa_> clivejo: so the minimal thing would be a transitional package for the -dev I think
[22:57] <santa_> that, at least
[23:03] <DarinMiller> wxl: I used bzr push lp:~darinsmiller/kubuntu-docs/ubuntu-manual
[23:04] <DarinMiller> which:  Created new stacked branch referring to /+branch-id/724437
[23:05] <DarinMiller> But I cannot find new packages on my lp page.
[23:05] <wxl> oh boy
[23:06] <DarinMiller> nm Found it
[23:06] <DarinMiller> https://code.launchpad.net/~darinsmiller/kubuntu-docs/ubuntu-manual-tests
[23:06] <wxl> kubuntu-docs was a strange place but there ya go :)
[23:06] <DarinMiller> I always forget about the bazillion little hidden clicks to find everything...
[23:07] <DarinMiller> so proceed with mp from here?
[23:08] <wxl> yep yep
[23:08] <wxl> https://code.launchpad.net/~darinsmiller/kubuntu-docs/ubuntu-manual-tests/+register-merge
[23:08] <wxl> make sure to select the right target :)
[23:09] <wxl> also make sure to make me a reviewer
[23:09] <DarinMiller> target = ubuntu-manual-tests ?
[23:10] <wxl> yes
[23:10] <wxl> btw have i mentioned how much i love !lp and !lpbug in ddg?
[23:14] <valorie> btw, still have loads of kubuntu stickers
[23:14] <valorie> nobody requested any from me
[23:15] <DarinMiller> wxl: ubuntu-manual-tests is an invalid target.
[23:21] <santa_> valorie: I might want a few of the small ones, I guess the best strategy would be getting them if we phisically meet @ next akademy
[23:26] <wxl> DarinMiller: ~ubuntu-testcase/ubuntu-manual-tests/trunk
[23:27] <acheronuk> I would like a few, but equally in no hurry
[23:27] <acheronuk> stickers ^^^
[23:33] <DarinMiller> wxl: New error: This branch is not mergeable into lp:ubuntu-manual-tests
[23:34] <wxl> whaaaaaa?
[23:34] <DarinMiller>  akonoaki-calendar
[23:34]  * clivejo is confused
[23:35] <wxl> DarinMiller: did you see above i said to use lp:~ubuntu-testcase/ubuntu-manual-tests?
[23:40] <valorie> akademy is coming right up!
[23:41] <valorie> at least I hope so
[23:41] <clivejo> its months away
[23:41] <acheronuk> 7 months?
[23:42] <valorie> no date yet
[23:42] <valorie> no place for sure yet
[23:43] <acheronuk> somewhere with good beer
[23:45] <valorie> I think it's Munich vs southern Spain
[23:45] <valorie> both of which sound great to me
[23:47] <acheronuk> heh: http://www.oktoberfest.de/en/
[23:47] <acheronuk> Munich Oktoberfest
[23:47] <acheronuk> (09/16/17 - 10/03/17)
[23:57] <acheronuk> clivejo: wow https://launchpad.net/ubuntu/+source/gcc-6/6.3.0-8ubuntu1/+build/12040492
[23:58] <acheronuk> it actually built!
[23:58] <acheronuk> (took 1 day, 7 hours, 8 minutes, 11.0 seconds)