[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] !testers [00:16] Help is needed in #kubuntu-devel. Please ping Riddell, yofel, soee, Tm_T, shadeslayer, BluesKaj, James147, Quintasan, lordievader, shrini, tester56, parad1se, mamarley, alket, SourBlues, sgclark, neo31, vip, mparillo, wxl, DarinMiller, tsimonq2 for information [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] ^ 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] 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] 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] wxl: Thanks for the re-building heads up. [00:52] 32-bit live worked fine with the previously reported problem that I needed to enter my WEP password twice [00:53] 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/ [01:13] !info tellico [01:13] 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] !info tellico [01:34] tellico (source: tellico): Collection manager for books, videos, music, etc. In component universe, is optional. Version 2.3.9+dfsg.1-1.1 (zesty), package size 1057 kB, installed size 4167 kB [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/ === absynthesyne is now known as nauticalnexus [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] https://www.kde.org/announcements/plasma-5.8.6.php [03:40] 5.8.6 out@ [03:49] !info plasma-desktop [03:49] plasma-desktop (source: plasma-desktop): Tools and widgets for the desktop. In component universe, is optional. Version 4:5.9.2-0ubuntu1 (zesty), package size 1767 kB, installed size 8922 kB [03:49] so we have 5.9.2 in zesty [03:50] should update this then: https://community.kde.org/Plasma/Live_Images === santa is now known as Guest76026 [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] Good morning [11:07] wxl: I have the latest iso now. shall do a couple of test cases later === Guest76026 is now known as santa_ [12:25] Hi folks [12:30] clivejo: damn. did not occur to me that calligra on s390x would produce weirdly version depends on GCC :/ [12:30] I just checked the deps on a few other archs [12:30] good morning everyone [12:31] good santa_ :) [12:32] it's PM here but I didn't eat yet, so it's "morning" :) [12:32] http://gpul.grupos.udc.es/buildstatus_ubuntu-exp2/ubuntu-exp2_status_applications.html [12:33] ↑ we have several autopkgtests failures [12:35] randomly picking one.... [12:35] acc FAIL non-zero exit status 6 [12:35] which is that known issue with GCC and the headers [12:36] presumably anyway from that exit status [12:37] santa_: does your setup collate failure reasons anywhere in any form? or just a manual pick through? [12:39] not sure what you mean [12:39] but anyway, let me explain [12:39] is there a summary page say, with just test failure reasons on each package? [12:40] ah, well no [12:40] that page is automatically generated with a fork of ppa-build-status [12:41] but it was modified to support the autopkgtests [12:41] so when you click on show/hide you would see the part of the autopkgtests [12:41] ooh. the show/hide expands the results, so that is partly doin that anyway. [12:41] 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] yep. just found it [12:42] + it would be marked on red if it has failing autopkgtests failures [12:43] by the way, the code to generate the staus webpages is very awful [12:43] I would like to rework it in the iron hand and use a templating system such as jinja [12:44] and of course have a separate class to parse build logs [12:44] so that way it would be easier to maintain and debug [12:46] well, as long as it's not in ruby :P [12:53] 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] 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] BBL [13:04] 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] but the annoying thing is he won't provide any feedback as to what the problem might be [13:14] so impossible to help him, when he won't even help himself [13:24] did anyone catch up with Darin last night? [13:26] 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] maybe we should just push ahead [13:28] Im sure another example of symbols will come up soon enough [13:29] if PIM is going to drop in 17.04, we need to get them in pronto [13:37] well, it's the other symbols issues which may take some time. but fair point [13:46] I didn't see him yesterday [13:47] clivejo, acheronuk: fyi fixing the acc tests inlining issue now, I will re-schedule the autopkgtesting @ tritemio [13:47] santa_: ack [14:04] santa_: nice one, thanks [14:08] yw [14:09] wrt autopkgtests I have added some initial info here https://phabricator.kde.org/w/kubuntu/autopkgtests/autopkgtests_in_kubuntu/ [14:09] in the testsuite section we could add some general tricks to fix the thing [14:10] 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/ === DalekSec_ is now known as DalekSec [14:45] hi DarinMiller [14:46] hi clivejo [14:47] acheronuk: have you an easy way of spliting PIM out of apps? [14:47] like we did before? [14:49] Am I too late for the symbols fix? [14:55] DarinMiller: nope [14:56] 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] 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] DarinMiller: in ~ 15 minutes then? [14:57] perfect [14:57] 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] I think we are in for a drowning [15:18] * DarinMiller throws clivejo a float ring http://imgur.com/a/mVZjt [15:19] Storm headed your way? [15:19] think so [15:22] the frogs are on the move [15:27] brb [15:31] ok, I'm back with some intel: https://phabricator.kde.org/w/kubuntu/packaging/symbols-files/ [15:32] DarinMiller: whenever you are on the keyboard again just ping me, so I can guide you with the thing [15:38] I am back [15:41] * DarinMiller is reaading the phab links posted by santa_ [15:42] 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] ok, sure [15:42] first of all, are you familiar with C or C++ programming? [15:43] not really. I have written a C "hello world" but that's about it. [15:43] I am familar with Java (but sitll fairly new) [15:44] ok, that would be - hopefully - enough for now [15:44] so let's start with the basic ideas [15:44] you probably know what's the API of a library, correct? [15:45] Yes, I have read the debian definition of api and abi, so I have a general idea.... [15:46] allright so you also know about the ABI, that's great [15:46] do you know what's an ABI breakage? [15:46] vaguely. [15:47] but probably have a clear idea of what's breaking the API of a library [15:48] Yes, I think so. [15:48] ok, well breaking the ABI is something similar, but at the binary level [15:49] API breakage is when the developer changes the way methods interact with a class? [15:49] for instance [15:49] yes [15:49] when a symbol is removed from the ABI, that's an ABI break. that simple [15:50] Oh, ok [15:50] and you can do that, for instance, changing the number or type of parameters of a public function [15:51] an API breakage in a C++ library would also produce an ABI breakage [15:52] 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] nope [15:52] assumes^ [15:53] 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] so the symbols files are, indeed, maintained by us [15:54] oh, oh, oh that makes sense [15:54] I presume you are not familiar yet with the symbols files, hence why we are having this conversation [15:55] correct [15:55] * acheronuk lurks [15:55] ok, so the questions are: ¿what are the symbols files? and ¿what's the point of having them? [15:56] the answer for the first one is, in short: they are files listing all the binary symbols exported by a library [15:57] From what I understand, they are an intermeidate build of "stuff" that is needed to build a package. [15:57] what you mean by intermediate? [15:58] I assume they require extra time to generate and thus the reason they are not regenerated with every build (guessing here). [15:58] it's a bit more complicated [15:59] the answer to ¿what's the point of having them? will reply to that [16:00] the primary purpose of having symbols files is creating versioned dependencies automatically [16:00] 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] so now, let me go a bit deeper with these 2 things [16:01] so we know when thing are broken, but auto fixing is difficult? [16:02] auto fixing shouldn't be done, because we need to check when the ABI breaks [16:02] and if so, do something about it [16:02] that something could be [16:02] a) patching the thing to restore the ABI [16:02] or [16:03] b) using the debian abi manager to handle the situation [16:03] that's explained in the last 2 sections of this: https://phabricator.kde.org/w/kubuntu/packaging/symbols-files/ [16:05] 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] that version is the package version where the symbol appeared in the library [16:06] 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] that is done at build time by dh_shlibdeps if I recall correctly [16:08] dh_shlibdeps expands the ${shlibs:Depends} [16:08] so since you are seeing that symbol file.... [16:09] DarinMiller: pick the first symbol and try this: [16:09] makes sense [16:09] $ c++filt _ZN21KVersionControlPlugin11infoMessageERK7QString [16:09] KVersionControlPlugin::infoMessage(QString const&) [16:10] c++filt translates the thing into C++ [16:10] so now, let's say we have a program linking against that library [16:10] Output: KVersionControlPlugin::infoMessage(QString const&) [16:11] as expected [16:13] so if we have a program using that function, its package would have a dependency against libdolphinvcs5 (>= 4:15.07.90) [16:14] DarinMiller: now supose that that function is gone, what would happen? [16:14] I suspect the builder process would be quite angry. [16:15] the first thing would be that the dolphin source package would fail to build [16:16] that in the first place [16:17] 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] and you can also see a diff [16:19] and the word MISSING [16:19] as an exercise, can you tell me which C++ function is gone in that library? [16:19] see it [16:20] MISSING: 4:16.12.2-0ubuntu1~ubuntu17.04~ppa1# _ZNK7Akonadi12CalendarBase15childIncidencesERKx@Base 15.07.90 [16:20] + 4 others [16:20] I'm seeing just one [16:20] the other stuff is the diff context [16:21] so to sum up that diff [16:21] oh, + _ZNK7Akonadi12CalendarBase15childIncidencesEx@Base 4:16.12.2-0ubuntu1~ubuntu17.04~ppa1 [16:21] +#MISSING: 4:16.12.2-0ubuntu1~ubuntu17.04~ppa1# _ZNK7Akonadi12CalendarBase15childIncidencesERKx@Base 15.07.90 [16:21] ↑ this one is gone [16:21] he wants you to lookup the C function [16:22] + _ZNK7Akonadi12CalendarBase15childIncidencesEx@Base 4:16.12.2-0ubuntu1~ubuntu17.04~ppa1 [16:22] ↑ this one is new [16:22] DarinMiller: so, like clive says, which c++ functions are those? [16:25] Akonadi::CalendarBase::childIncidences(long long const&) const [16:26] so thats the old function, whats the new one? [16:28] Akonadi::CalendarBase::childIncidences(long long) const [16:28] no cont in the new one [16:29] do you see whats changed there? [16:29] const& [16:29] yep [16:29] so that's probably an ABI break [16:29] I will try to explain later why I say 'probably' [16:30] so going back to what I was explaining later [16:30] possible "optional" param? [16:31] ok [16:31] we will see that [16:31] * so going back to what I was explaining earlier [16:31] what happens now? [16:31] 1. the package is failing to build [16:32] 2. if you update the symbols file and you remove that symbol from the file the package will build BUT [16:32] BUT [16:33] santa_: sorry to interupt but would there not be a third or c) option to check for a so bump? [16:33] so remove _ZNK7Akonadi12CalendarBase15childIncidencesERKx and replace with _ZNK7Akonadi12CalendarBase15childIncidencesEx? [16:33] clivejo: if there's an soname bump we would have to do more than that to get the package building again [16:34] clivejo: because the file naming would be different so it would fail @ dh_install [16:35] 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] DarinMiller: nope. that's exactly what I wanted to explain [16:36] if you do that the package will build [16:36] BUT [16:36] any existing binary using it would crash, probably [16:37] oh, Ok. [16:37] you would need to rebuild them to fix that [16:37] DarinMiller: so, the correct solution for this case is [16:37] 1. check if this is an ABI break [16:38] 2. if so, use the debian ABI manager [16:39] about the 1. you have to check the previous package [16:39] locate the funxtion in question [16:39] * function [16:39] you can do this with the excellent 'ack' program [16:40] then you have to confirm that it's indeed a public function [16:40] and if so, check if the header where it is [16:40] and check if that header is installed [16:41] thx acheronuk :) [16:41] beucase if the header is not installed, that would make the function effectively private [16:41] * because [16:42] I already did all of this and I think I can confirm it's an ABI break [16:42] can you show how to use ack? [16:42] pardon my greeness: where do I find the ack program? [16:42] of course, 1 sec [16:42] I looked in ka and in repos.. [16:42] all I see is ack-grep [16:43] yep, pkgname is ack-grep [16:43] !info ack [16:43] installing now.. [16:43] ack (source: ack): grep-like program specifically for large source trees. In component universe, is optional. Version 2.14-5 (zesty), package size 58 kB, installed size 196 kB [16:44] what does that do that grep doesn't? [16:44] the program name is either 'ack-grep' (alias) or 'ack' for yakkety [16:44] I think in zesty they dropped the alias [16:44] so I'm executing it as 'ack' [16:44] wxl: shows context and you don't have to feed in it the list of files to search [16:45] well grep can show context [16:45] hmm not sure about the context let me check [16:45] santa_: so you would grab the source package from the archive and use ack on that? [16:46] ok running plasma 5.9.2 Zesty beta1, all seems well so far, after doing a complete clean install [16:46] clivejo: yep [16:46] BluesKaj: did you mark the test case successfully completed? [16:46] you just have to type ack 'string', and that's it [16:47] couldn't save my messed up config files [16:47] do you have a script to do that? [16:47] or just do it manually? [16:47] in the previous try ...my /home die was the culprit [16:47] dir [16:47] I usually do it manually, but we could add something in ka [16:48] wxi where to do that? [16:48] clivejo: but more often, I just browse my ~/kde-ftp dir [16:48] because I would have the upstream tarballs there already [16:49] so I just have to check what's the latest version with LP [16:49] just trying to allow Darin to follow this himself [16:49] k [16:49] so do a "apt-get source akonadi-calendar" to grab the source? [16:50] 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] I think he is [16:51] DarinMiller: uscan would download the latest stable version [16:51] which would be 16.12 [16:51] we have to check the 16.04.x [16:51] current box is zesty, so apt-get'ing now.... [16:52] !info akonadi-calendar [16:52] Package akonadi-calendar does not exist in zesty [16:52] ditto [16:53] BluesKaj: on the iso tracker. that's where all the testing is recorded [16:53] BluesKaj: http://iso.qa.ubuntu.com/qatracker/milestones/373/builds [16:53] its a lib [16:53] !info libkf5akonadicalendar-dev [16:53] libkf5akonadicalendar-dev (source: akonadi-calendar): akonadi-calendar - development files. In component universe, is optional. Version 4:16.04.3-0ubuntu1 (zesty), package size 23 kB, installed size 164 kB [16:53] built from the akonadi-calendar source package [16:54] I guess the bot doesn't work with source package names [16:54] nope, wish it would though! [16:54] https://launchpad.net/ubuntu/+source/akonadi-calendar [16:55] ok i see why ack is better [16:55] apt-get source libkf5akonadicalendar-dev produces: [16:55] Picking 'akonadi-calendar' as source package instead of 'libkf5akonadicalendar-dev' [16:55] E: Unable to find a source package for akonadi-calendar [16:55] DarinMiller: apt-get source akonadi-calendar should work [16:56] DarinMiller: do you have the deb-src lines enabled in your sources? [16:56] uh, just sec.... [16:56] just thought of that :) [16:58] * DarinMiller is waiting for the entire internet to download.... [16:58] that's better, source dl'd [16:58] 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] git clone kde:akonadi-calendar; cd akonadi-calendar; git checkout v16.04.3 [17:00] s/;/&&/ [17:00] ^^ would get KDE repo's src [17:00] 16.04.3 is the version in zesty currently [17:00] or alternatively dget https://launchpad.net/ubuntu/+archive/primary/+files/akonadi-calendar_16.04.3-0ubuntu1.dsc [17:01] you can do it any way you prefer [17:01] ^^ i prefer that since the subsequent commands only execute if the previous command succeeds [17:01] wxl: point taken [17:01] 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] wxi , mucking about ubuntu one is a pita :/ [17:04] BluesKaj: yeah well once you have it set up you're pretty much good to go :) [17:04] https://paste.kde.org/pmtqtldug [17:05] ↑ if you do that yourself you would see a nice colored output probably [17:05] and you can limit by type too, which is nice [17:05] yes, that is slick [17:06] have upstream been informed of this break? [17:06] clivejo: nope [17:06] I think with these apps libs we could just go ahead with the abi manager [17:07] if it were from frameworks, that would be a different story [17:07] santa_: is there any way to find what calls that publicially? [17:07] mine ack looks different: https://paste.ubuntu.com/24047516/ [17:08] you have the full source, including debain packaging [17:09] DarinMiller: probably because santa_ has an .ackrc [17:09] so its picking up the symbols [17:09] or that :) [17:09] nah, I did with the source package [17:09] .ackrc then? [17:09] but I think they are the same contents, in different order [17:10] 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] ah possibly [17:10] or there's different default options [17:10] yeah, maybe [17:11] there is --sort-files [17:11] anyway, the whole point of this is [17:11] src/calendarbase.h [17:11] 101: KCalCore::Incidence::List childIncidences(const QString &parentUid) const; [17:11] 108: KCalCore::Incidence::List childIncidences(const Akonadi::Item::Id &parentId) const; [17:12] Akonadi::CalendarBase::childIncidences(long long const&) const [17:12] so it's in calendarbase.h, which is also the obvious file name [17:13] for comparison [17:14] acheronuk: that must be in the new 16.12 package [17:14] 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] DarinMiller: if you had started at them long enough you would have figured it out :) [17:16] so, now to find out if the *.h file is installed a possible way is doing this @ zesty: [17:16] $ apt-file show libkf5akonadicalendar-dev | grep calendarbase.h [17:16] libkf5akonadicalendar-dev: /usr/include/KF5/akonadi/calendar/calendarbase.h [17:17] ↑ to get that working you must install apt-file [17:17] + doing apt-file update once installed [17:18] alternatively you can check the build logs on launchpad; there's a file listing for each binary package [17:18] santa_: 'for comparison' with the 16.12.2 buildlog. sorry to confuse [17:18] apt-file installed (must of been part of some dev package set) [17:18] acheronuk: ah, ok :) [17:19] so now we can confirm this is indeed an ABI break [17:19] clivejo, acheronuk: so let's just use the debian abi manager, any objections? [17:20] fine here. I have notes from when we did it on prison ages ago, but a new iteration is great [17:22] "offtopic": while we speak I'm seeing here in the other monitor some akonadi unit tests hanging like hell :( [17:24] acheronuk: you were incarcerated? :) [17:24] 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] just a few extra symbols when I tried in my ppa [17:25] yes, in the official ppa too [17:25] I ddin''t push the changes yet, btw [17:26] wxl: yes. here. on this channel. I've not escaped yet! :P [17:26] santa_: ah. right. I got emails about the build failure, but not the success as those don't happen. [17:26] acheronuk: just like clivejo and he even formally stated he was leaving ;) [17:27] wxl: clive who? [17:27] XD [17:27] * acheronuk looks around. [17:27] it's difficult to leave [17:27] ** ghosties ** [17:27] 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] 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] I found that manual only makes sense once you've used it. sort of the wrong way around, but there you go [17:29] I will give it a shot... [17:30] k, just try to follow that README and if you can't just give us a shout so we can help you [17:30] will do [17:31] hint: you will have to use that X-CMake-Target thing [17:31] unfortunately the autodetection for that is kind of broken since frameworks === santa is now known as Guest19945 === Guest19945 is now known as santa_ [17:48] acheronuk: wrt kwallet-kf5/gpgme this is what I have here https://paste.kde.org/pcaln0ces [17:48] the new symbols seem to be just leaks [17:49] thefore I think we won't need to rebuild anything against a new kwallet package with gpgme enabled again [17:49] * therefore [17:50] santa_: libgpgme11-dev is not in v1.8 ? [17:51] 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] santa_: forget that [17:56] I forgot that they added.... [17:56] Provides: [17:56] libgpgme11-dev (= ${binary:Version}) [17:56] to libgpgme11 [17:57] so either will do, and still get the new version [17:57] santa_: so yes, that is likely what I would get if I ran symbolshelper [18:10] 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] santa_: that is what I added on my build, yes [18:56] 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] these 2 = knotifications, ktextwidgets [18:58] man that freaking blank screen bug ugh [18:59] santa_: does adding qttexttospeech add new features? [18:59] add/enable etc [18:59] acheronuk: according to cmake it should. concerned if that goes against the freeze? [19:00] santa_: yep. [19:01] acheronuk: maybe we should ask in -release/ file an ffe? [19:02] 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] 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] 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] probably [19:10] feel free to go ahead with that [19:10] * santa_ looks @ the other pim fatbfs'ing libs instead.... [19:15] 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] 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] clivejo: very very very very very SLOWLY FTBFS I would imagine [19:18] bit like a car crash i shown in slow motion...... [19:27] acheronuk: let me guess: the F4 key doesn't respond [19:28] wxl: yes, does nothing in ubiquity as booted normally [19:29] 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] wxl: hah. the test case is unclear in so many ways. so yes/no [19:33] I'll try again in a min in the way I guess they mean [19:33] acheronuk: and it's a general test case, too >:( [19:33] DarinMiller was supposed to make us a kubuntu specific one..\ [19:44] 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] acheronuk: that was my experience, too, but others have tested on real hardware with no probs [19:46] 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] acheronuk: add it as a fail with a comment as mparillo did [19:51] done [19:51]