/srv/irclogs.ubuntu.com/2017/02/22/#kubuntu-devel.txt

-kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #805: SUCCESS in 7 min 4 sec: http://kci.pangea.pub/job/mgmt_merger/805/00:07
-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!testers00:16
ubottuHelp 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 information00: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:16
wxl^ we're rebuilding beta 1 to get the new frameworks and plasma in there. it could use all the testing we can get00: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
wxltsimonq2: make sure to update kubuntu-devel plz00: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:17
tsimonq2wxl: kthx00:18
-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:19
-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:20
-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:26
-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:40
-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:41
-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
mparillowxl: Thanks for the re-building heads up.00:51
mparillo32-bit live worked fine with the previously reported problem that I needed to enter my WEP password twice00:52
mparillo32-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.00:53
-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:03
-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:04
IrcsomeBot<CliffordTheBigRedDoggie> !info tellico01:13
IrcsomeBot<CliffordTheBigRedDoggie> I guess bots don't work on telegram :/01:13
-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:15
-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:16
krytarik!info tellico01:34
ubottutellico (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 kB01:34
-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:18
-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:30
-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:38
-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:39
-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:40
-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:41
-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:45
-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:46
-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
=== absynthesyne is now known as nauticalnexus
-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/02:50
-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:02
-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:03
-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:04
-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:16
-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:17
-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:18
-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:28
-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:31
-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:38
-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:39
ahoneybunhttps://www.kde.org/announcements/plasma-5.8.6.php03:40
ahoneybun5.8.6 out@03:40
ahoneybun!info plasma-desktop03:49
ubottuplasma-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 kB03:49
ahoneybunso we have 5.9.2 in zesty03:49
ahoneybunshould update this then: https://community.kde.org/Plasma/Live_Images03:50
=== santa is now known as Guest76026
-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:02
-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:03
-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:14
-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:22
-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:34
-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:43
-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/05:44
-kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #111: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/111/06:11
-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:05
-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:15
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #395: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/395/07:22
lordievaderGood morning08:56
acheronukwxl: I have the latest iso now. shall do a couple of test cases later11:07
=== Guest76026 is now known as santa_
BluesKajHi folks12:25
acheronukclivejo: damn. did not occur to me that calligra on s390x would produce weirdly version depends on GCC :/12:30
acheronukI just checked the deps on a few other archs12:30
santa_good morning everyone12:30
acheronukgood <insert am/pm/evening here> santa_ :)12:31
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.html12:32
santa_↑ we have several autopkgtests failures12:33
acheronukrandomly picking one....12:35
acheronukacc                  FAIL non-zero exit status 612:35
acheronukwhich is that known issue with GCC and the headers12:35
acheronukpresumably anyway from that exit status12:36
acheronuksanta_: does your setup collate failure reasons anywhere in any form? or just a manual pick through?12:37
santa_not sure what you mean12:39
santa_but anyway, let me explain12:39
acheronukis there a summary page say, with just test failure reasons on each package?12:39
santa_ah, well no12:40
santa_that page is automatically generated with a fork of ppa-build-status12:40
santa_but it was modified to support the autopkgtests12:41
santa_so when you click on show/hide you would see the part of the autopkgtests12:41
acheronukooh. the show/hide expands the results, so that is partly doin that anyway.12:41
BluesKajZesty 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
acheronukyep. just found it12:41
santa_+ it would be marked on red if it has failing autopkgtests failures12:42
santa_by the way, the code to generate the staus webpages is very awful12:43
santa_I would like to rework it in the iron hand and use a templating system such as jinja12:43
santa_and of course have a separate class to parse build logs12:44
santa_so that way it would be easier to maintain and debug12:44
acheronukwell, as long as it's not in ruby :P12:46
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 apps12:53
BluesKajdon'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:56
BluesKajBBL12:57
acheronukhmmm... 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:04
clivejobut the annoying thing is he won't provide any feedback as to what the problem might be13:13
clivejoso impossible to help him, when he won't even help himself13:14
clivejodid anyone catch up with Darin last night?13:24
acheronukclivejo: he was about late afternoon, but not evening that I saw. I was not staying up late though after staging until 2:30am previous night13:26
clivejomaybe we should just push ahead13:27
clivejoIm sure another example of symbols will come up soon enough13:28
clivejoif PIM is going to drop in 17.04, we need to get them in pronto13:29
acheronukwell, it's the other symbols issues which may take some time. but fair point13:37
santa_I didn't see him yesterday13:46
santa_clivejo, acheronuk: fyi fixing the acc tests inlining issue now, I will re-schedule the autopkgtesting @ tritemio13:47
acheronuksanta_: ack13:47
clivejosanta_: nice one, thanks14:04
santa_yw14:08
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 thing14:09
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:10
-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:23
=== DalekSec_ is now known as DalekSec
clivejohi DarinMiller14:45
DarinMillerhi clivejo14:46
clivejoacheronuk: have you an easy way of spliting PIM out of apps?14:47
clivejolike we did before?14:47
DarinMillerAm I too late for the symbols fix?14:49
santa_DarinMiller: nope14:55
santa_DarinMiller: so whenever you are around and have time just ping me so I can explain you what's the deal with symbols files14:56
DarinMillerExcellent! 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
DarinMillerperfect14:57
santa_so I can gather some intel :)14:57
-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/14:59
* clivejo shakes head15:12
clivejoI think we are in for a drowning15:12
* DarinMiller throws clivejo a float ring http://imgur.com/a/mVZjt15:18
DarinMillerStorm headed your way?15:19
clivejothink so15:19
clivejothe frogs are on the move15:22
DarinMillerbrb15:27
santa_ok, I'm back with some intel: https://phabricator.kde.org/w/kubuntu/packaging/symbols-files/15:31
santa_DarinMiller: whenever you are on the keyboard again just ping me, so I can guide you with the thing15:32
DarinMillerI am back15:38
* DarinMiller is reaading the phab links posted by santa_15:41
santa_DarinMiller: yes, before doing that, because there's a myriad of things to read there I would like to give you a summary15:42
DarinMillerok, sure15:42
santa_first of all, are you familiar with C or C++ programming?15:42
DarinMillernot really.  I have written a C "hello world" but that's about it.15:43
DarinMillerI am familar with Java (but sitll fairly new)15:43
santa_ok, that would be - hopefully - enough for now15:44
santa_so let's start with the basic ideas15:44
santa_you probably know what's the API of a library, correct?15:44
DarinMillerYes, I have read the debian definition of api and abi, so I have a general idea....15:45
santa_allright so you also know about the ABI, that's great15:46
santa_do you know what's an ABI breakage?15:46
DarinMillervaguely.15:46
santa_but probably have a clear idea of what's breaking the API of a library15:47
DarinMillerYes, I think so.15:48
santa_ok, well breaking the ABI is something similar, but at the binary level15:48
DarinMillerAPI breakage is when the developer changes the way methods interact with a class?15:49
santa_for instance15:49
santa_yes15:49
santa_when a symbol is removed from the ABI, that's an ABI break. that simple15:49
DarinMillerOh, ok15:50
santa_and you can do that, for instance, changing the number or type of parameters of a public function15:50
santa_an API breakage in a C++ library would also produce an ABI breakage15:51
santa_however, you can keep API compatibility and break the ABI15:52
* DarinMiller assumea that symbols are not auto generated when packages built, and thus the issue...15:52
santa_nope15:52
DarinMillerassumes^15:52
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 ABI15:53
santa_so the symbols files are, indeed, maintained by us15:53
DarinMilleroh, oh, oh that makes sense15:54
santa_I presume you are not familiar yet with the symbols files, hence why we are having this conversation15:54
DarinMillercorrect15:55
* acheronuk lurks15:55
santa_ok, so the questions are: ¿what are the symbols files? and ¿what's the point of having them?15:55
santa_the answer for the first one is, in short: they are files listing all the binary symbols exported by a library15:56
DarinMillerFrom 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:57
DarinMillerI 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 complicated15:58
santa_the answer to ¿what's the point of having them? will reply to that15:59
santa_the primary purpose of having symbols files is creating versioned dependencies automatically16:00
santa_and there's a secondary purpose and it's checking that the ABI wasn't broken since the previous version of the library16:00
santa_so now, let me go a bit deeper with these 2 things16:01
DarinMillerso we know when thing are broken, but auto fixing is difficult?16:01
santa_auto fixing shouldn't be done, because we need to check when the ABI breaks16:02
santa_and if so, do something about it16:02
santa_that something could be16:02
santa_a) patching the thing to restore the ABI16:02
santa_or16:02
santa_b) using the debian abi manager to handle the situation16:03
santa_that's explained in the last 2 sections of this: https://phabricator.kde.org/w/kubuntu/packaging/symbols-files/16:03
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 version16:05
santa_that version is the package version where the symbol appeared in the library16:05
santa_so when you build a package against that library, it would have a dependency on the corresponding library version16:06
* DarinMiller is reviewing dophins symbol list...16:06
santa_that is done at build time by dh_shlibdeps if I recall correctly16:06
santa_dh_shlibdeps expands the ${shlibs:Depends}16:08
santa_so since you are seeing that symbol file....16:08
santa_DarinMiller: pick the first symbol and try this:16:09
DarinMillermakes sense16:09
santa_$ c++filt _ZN21KVersionControlPlugin11infoMessageERK7QString16:09
santa_KVersionControlPlugin::infoMessage(QString const&)16:09
santa_c++filt translates the thing into C++16:10
santa_so now, let's say we have a program linking against that library16:10
DarinMillerOutput: KVersionControlPlugin::infoMessage(QString const&)16:10
santa_as expected16:11
santa_so if we have a program using that function, its package would have a dependency against libdolphinvcs5 (>= 4:15.07.90)16:13
santa_DarinMiller: now supose that that function is gone, what would happen?16:14
DarinMillerI suspect the builder process would be quite angry.16:14
santa_the first thing would be that the dolphin source package would fail to build16:15
santa_that in the first place16:16
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.gz16:17
* DarinMiller sees dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below16:18
santa_and you can also see a diff16:18
santa_and the word MISSING16:19
santa_as an exercise, can you tell me which C++ function is gone in that library?16:19
DarinMillersee it16:19
DarinMillerMISSING: 4:16.12.2-0ubuntu1~ubuntu17.04~ppa1# _ZNK7Akonadi12CalendarBase15childIncidencesERKx@Base 15.07.9016:20
DarinMiller+ 4 others16:20
santa_I'm seeing just one16:20
santa_the other stuff is the diff context16:20
santa_so to sum up that diff16:21
DarinMilleroh, + _ZNK7Akonadi12CalendarBase15childIncidencesEx@Base 4:16.12.2-0ubuntu1~ubuntu17.04~ppa116:21
santa_+#MISSING: 4:16.12.2-0ubuntu1~ubuntu17.04~ppa1# _ZNK7Akonadi12CalendarBase15childIncidencesERKx@Base 15.07.9016:21
santa_↑ this one is gone16:21
clivejohe wants you to lookup the C function16:21
santa_+ _ZNK7Akonadi12CalendarBase15childIncidencesEx@Base 4:16.12.2-0ubuntu1~ubuntu17.04~ppa116:22
santa_↑ this one is new16:22
santa_DarinMiller: so, like clive says, which c++ functions are those?16:22
DarinMillerAkonadi::CalendarBase::childIncidences(long long const&) const16:25
clivejoso thats the old function, whats the new one?16:26
DarinMillerAkonadi::CalendarBase::childIncidences(long long) const16:28
DarinMillerno cont in the new one16:28
clivejodo you see whats changed there?16:29
DarinMillerconst&16:29
santa_yep16:29
santa_so that's probably an ABI break16:29
santa_I will try to explain later why I say 'probably'16:29
santa_so going back to what I was explaining later16:30
DarinMillerpossible "optional" param?16:30
DarinMillerok16:31
santa_we will see that16:31
santa_* so going back to what I was explaining earlier16:31
santa_what happens now?16:31
santa_1. the package is failing to build16:31
santa_2. if you update the symbols file and you remove that symbol from the file the package will build BUT16:32
santa_BUT16:32
clivejosanta_: sorry to interupt but would there not be a third or c) option to check for a so bump?16:33
DarinMillerso 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 again16:33
santa_clivejo: because the file naming would be different so it would fail @ dh_install16:34
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:35
santa_DarinMiller: nope. that's exactly what I wanted to explain16:36
santa_if you do that the package will build16:36
santa_BUT16:36
santa_any existing binary using it would crash, probably16:36
DarinMilleroh, Ok.16:37
santa_you would need to rebuild them to fix that16:37
santa_DarinMiller: so, the correct solution for this case is16:37
santa_1. check if this is an ABI break16:37
santa_2. if so, use the debian ABI manager16:38
santa_about the 1. you have to check the previous package16:39
santa_locate the funxtion in question16:39
santa_* function16:39
santa_you can do this with the excellent 'ack' program16:39
santa_then you have to confirm that it's indeed a public function16:40
santa_and if so, check if the header where it is16:40
santa_and check if that header is installed16:40
wxlthx acheronuk :)16:41
santa_beucase if the header is not installed, that would make the function effectively private16:41
santa_* because16:41
santa_I already did all of this and I think I can confirm it's an ABI break16:42
clivejocan you show how to use ack?16:42
DarinMillerpardon my greeness: where do I find the ack program?16:42
santa_of course, 1 sec16:42
DarinMillerI looked in ka and in repos..16:42
DarinMillerall I see is ack-grep16:42
santa_yep, pkgname is ack-grep16:43
clivejo!info ack16:43
DarinMillerinstalling now..16:43
ubottuack (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 kB16:43
wxlwhat does that do that grep doesn't?16:44
santa_the program name is either 'ack-grep' (alias) or 'ack' for yakkety16:44
santa_I think in zesty they dropped the alias16: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 search16:44
wxlwell grep can show context16:45
santa_hmm not sure about the context let me check16:45
clivejosanta_: so you would grab the source package from the archive and use ack on that?16:45
BluesKajok running plasma 5.9.2 Zesty beta1, all seems well so far, after doing a complete clean install 16:46
santa_clivejo: yep16:46
wxlBluesKaj: did you mark the test case successfully completed?16:46
santa_you just have to type ack 'string', and that's it16:46
BluesKajcouldn't save my messed up config files 16:47
clivejodo you have a script to do that?16:47
clivejoor just do it manually?16:47
BluesKajin the previous try ...my /home die was the culprit16:47
BluesKajdir16:47
santa_I usually do it manually, but we could add something in ka16:47
BluesKajwxi where to do that?16:48
santa_clivejo: but more often, I just browse my ~/kde-ftp dir16:48
santa_because I would have the upstream tarballs there already16:48
santa_so I just have to check what's the latest version with LP16:49
clivejojust trying to allow Darin to follow this himself16:49
santa_k16:49
clivejoso do a "apt-get source akonadi-calendar" to grab the source?16:49
santa_sure, you can do that if you are on zesty16:50
* DarinMiller darin is trying to follow, wonder why apt-get source and not uscan....16:50
clivejoI think he is16:50
santa_DarinMiller: uscan would download the latest stable version16:51
santa_which would be 16.1216:51
santa_we have to check the 16.04.x16:51
DarinMillercurrent box is zesty,  so apt-get'ing now....16:51
clivejo!info akonadi-calendar16:52
ubottuPackage akonadi-calendar does not exist in zesty16:52
DarinMillerditto16:52
wxlBluesKaj: on the iso tracker. that's where all the testing is recorded16:53
wxlBluesKaj: http://iso.qa.ubuntu.com/qatracker/milestones/373/builds16:53
clivejoits a lib16:53
clivejo!info libkf5akonadicalendar-dev16:53
ubottulibkf5akonadicalendar-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 kB16:53
clivejobuilt from the akonadi-calendar source package16:53
santa_I guess the bot doesn't work with source package names16:54
clivejonope, wish it would though!16:54
santa_https://launchpad.net/ubuntu/+source/akonadi-calendar16:54
wxlok i see why ack is better16:55
DarinMillerapt-get source libkf5akonadicalendar-dev produces:16:55
DarinMillerPicking 'akonadi-calendar' as source package instead of 'libkf5akonadicalendar-dev'16:55
DarinMillerE: Unable to find a source package for akonadi-calendar16:55
clivejoDarinMiller: apt-get source akonadi-calendar should work16:55
santa_DarinMiller: do you have the deb-src lines enabled in your sources?16:56
DarinMilleruh, just sec....16:56
DarinMillerjust thought of that :)16:56
* DarinMiller is waiting for the entire internet to download....16:58
DarinMillerthat's better, source dl'd16:58
wxlBluesKaj: you grok all that or you have questions?16:58
* DarinMiller thinks he needs to enable staging to pull down 16.12.2 as 16.04 was dl'd17:00
acheronukgit clone kde:akonadi-calendar; cd akonadi-calendar; git checkout v16.04.317:00
wxls/;/&&/17:00
acheronuk^^ would get KDE repo's src17:00
clivejo16.04.3 is the version in zesty currently17:00
santa_or alternatively dget https://launchpad.net/ubuntu/+archive/primary/+files/akonadi-calendar_16.04.3-0ubuntu1.dsc17:00
santa_you can do it any way you prefer17:01
wxl^^ i prefer that since the subsequent commands only execute if the previous command succeeds17:01
acheronukwxl: point taken17:01
santa_that's up to you17:01
* acheronuk goes back to lurking and playing with 'ack'17:02
* DarinMiller nm, realizes v16.04 is what failed...17:03
BluesKajwxi , mucking about ubuntu one is a pita :/17:03
wxlBluesKaj: yeah well once you have it set up you're pretty much good to go :)17:04
santa_https://paste.kde.org/pmtqtldug17:04
santa_↑ if you do that yourself you would see a nice colored output probably17:05
wxland you can limit by type too, which is nice17:05
DarinMilleryes, that is slick17:05
clivejohave upstream been informed of this break?17:06
santa_clivejo: nope17:06
santa_I think with these apps libs we could just go ahead with the abi manager17:06
santa_if it were from frameworks, that would be a different story17:07
clivejosanta_: is there any way to find what calls that publicially?17:07
DarinMillermine ack looks different: https://paste.ubuntu.com/24047516/17:07
clivejoyou have the full source, including debain packaging17:08
wxlDarinMiller: probably because santa_ has an .ackrc17:09
clivejoso its picking up the symbols17:09
wxlor that :)17:09
santa_nah, I did with the source package17:09
wxl.ackrc then?17:09
santa_but I think they are the same contents, in different order17:09
santa_wxl: I'm on yakkety he is on zesty, so probably the file order is kind of random and different for each one17:10
wxlah possibly17:10
wxlor there's different default options17:10
santa_yeah, maybe17:10
wxlthere is --sort-files17:11
santa_anyway, the whole point of this is17:11
santa_src/calendarbase.h17: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:11
acheronuk Akonadi::CalendarBase::childIncidences(long long const&) const17:12
santa_so it's in calendarbase.h, which is also the obvious file name17:12
acheronukfor comparison17:13
santa_acheronuk: that must be in the new 16.12 package17:14
santa_or are you @ 16.04 source?17:14
* 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-file17:15
wxlDarinMiller: if you had started at them long enough you would have figured it out :)17:15
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.h17:16
santa_libkf5akonadicalendar-dev: /usr/include/KF5/akonadi/calendar/calendarbase.h17:16
santa_↑ to get that working you must install apt-file17:17
santa_+ doing apt-file update once installed17:17
santa_alternatively you can check the build logs on launchpad; there's a file listing for each binary package17:18
acheronuksanta_: 'for comparison' with the 16.12.2 buildlog. sorry to confuse 17:18
DarinMillerapt-file installed (must of been part of some dev package set)17:18
santa_acheronuk: ah, ok :)17:18
santa_so now we can confirm this is indeed an ABI break17:19
santa_clivejo, acheronuk: so let's just use the debian abi manager, any objections?17:19
acheronukfine here. I have notes from when we did it on prison ages ago, but a new iteration is great17:20
santa_"offtopic": while we speak I'm seeing here in the other monitor some akonadi unit tests hanging like hell :(17:22
wxlacheronuk: you were incarcerated? :)17:24
acheronuksanta_: BTW kwallet in FW builds with the new gpgme. just a different -dev name to add to the deps. I saw you tried it yesterday17:24
acheronukjust a few extra symbols when I tried in my ppa17:24
santa_yes, in the official ppa too17:25
santa_I ddin''t push the changes yet, btw17:25
acheronukwxl: yes. here. on this channel. I've not escaped yet! :P17:26
acheronuksanta_: ah. right. I got emails about the build failure, but not the success as those don't happen.17:26
wxlacheronuk: just like clivejo and he even formally stated he was leaving ;)17:26
acheronukwxl: clive who?17:27
wxlXD17:27
* acheronuk looks around.17:27
santa_it's difficult to leave17: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 here17:27
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:28
acheronukI found that manual only makes sense once you've used it. sort of the wrong way around, but there you go17:29
DarinMillerI will give it a shot...17:29
santa_k, just try to follow that README and if you can't just give us a shout so we can help you17:30
DarinMillerwill do17:30
santa_hint: you will have to use that X-CMake-Target thing17:31
santa_unfortunately the autodetection for that is kind of broken since frameworks17:31
=== santa is now known as Guest19945
=== Guest19945 is now known as santa_
santa_acheronuk: wrt kwallet-kf5/gpgme this is what I have here https://paste.kde.org/pcaln0ces17:48
santa_the new symbols seem to be just leaks17:48
santa_thefore I think we won't need to rebuild anything against a new kwallet package with gpgme enabled again17:49
santa_* therefore17:49
acheronuksanta_: libgpgme11-dev is not in v1.8 ?17:50
acheronuksanta_: so is your build grabbing one -dev file from v1.7 in release and another from v1.8 in proposed or the ppa?17:51
* acheronuk goes to look17:52
acheronuksanta_: forget that17:56
acheronukI forgot that they added....17:56
acheronukProvides:17:56
acheronuk libgpgme11-dev (= ${binary:Version})17:56
acheronukto libgpgme1117:56
acheronukso either will do, and still get the new version17:57
acheronuksanta_: so yes, that is likely what I would get if I ran symbolshelper17:57
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:10
acheronuksanta_: that is what I added on my build, yes18:11
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:56
santa_these 2 = knotifications, ktextwidgets18:57
wxlman that freaking blank screen bug ugh18:58
acheronuksanta_: does adding qttexttospeech add new features?18:59
acheronukadd/enable etc18:59
santa_acheronuk: according to cmake it should. concerned if that goes against the freeze?18:59
acheronuksanta_: yep.19:00
santa_acheronuk: maybe we should ask in -release/ file an ffe?19:01
acheronuksanta_: 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 burn19:02
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-brainer19:06
acheronukmaybe 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 stack19:09
santa_probably19:10
santa_feel free to go ahead with that19:10
* santa_ looks @ the other pim fatbfs'ing libs instead....19:10
acheronukclivejo: that GCC build??? "Started 1 day, 2 hours, 42 minutes, 20.4 seconds ago."19:15
* clivejo wonders what it is doing19:17
acheronukwxl: is testing OEM install ok from the grub menu? on Vbox I cant trigger it in the way the test case asks 19:17
acheronukclivejo: very very very very very SLOWLY FTBFS I would imagine19:18
acheronukbit like a car crash i shown in slow motion......19:18
wxlacheronuk: let me guess: the F4 key doesn't respond19:27
acheronukwxl: yes, does nothing in ubiquity as booted normally19:28
wxlyou mean you can't get to the grub menu? the testcase is lacking the instruction to hold down shift at boot19:29
-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:31
acheronukwxl: hah. the test case is unclear in so many ways. so yes/no19:32
acheronukI'll try again in a min in the way I guess they mean19:33
wxlacheronuk: and it's a general test case, too >:(19:33
wxlDarinMiller was supposed to make us a kubuntu specific one..\19:33
acheronukwxl: OEM is a fail for me in VBox. just goes to a black screen at the finish. even after a forced reboot19:44
wxlacheronuk: that was my experience, too, but others have tested on real hardware with no probs19:45
acheronukwxl: 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
wxlacheronuk: add it as a fail with a comment as mparillo did19:46
acheronukdone19:51
wxlthx19:51
* santa_ is trying to fix pimcommon...20:02
wxlmaybe we should make OEM mode optional as xubuntu does20:07
wxlyou're on vbox right acheronuk ?20:09
acheronukwxl: for this sort of testing, yes20:10
ahoneybununixstickers is having a sale on the KDE sticker kit20:10
wxlacheronuk: would you mind testing that in kvm?20:12
wxlacheronuk: that = kvm btw20:13
wxlOOH THEY HAVE TMUX STICKERS20:13
wxlwe need kubuntu shirts on there20:15
geniiMy Kubuntu polo shirt has tears in it now :(20:16
IrcsomeBot<ahoneybun> do we really?20:16
IrcsomeBot<ahoneybun> https://www.hellotux.com/kubuntu20:17
IrcsomeBot<ahoneybun> @wxl2320:17
IrcsomeBot<ahoneybun> I like the Mate one better: https://www.hellotux.com/ubuntu_mate_polo_shirt_green20:18
geniiI don't see any blue ones20:19
wxli don't love polos20:20
IrcsomeBot<ahoneybun> not saying I do either but still20:21
wxlso true https://www.unixstickers.com/stickers/coding_stickers/java-hispter-jhipster-shaped-sticker20:21
acheronukwxl: kvm doesn't want to work here. changes the permissions on the .iso, then complains it can't read it due to wrong permissions20:23
wxlacheronuk: bah, shoot.20:23
wxlanyone got a kvm up and running?20:24
santa_wxl: me. qemu/kvm with virt-manager here20:24
wxlsanta_: could you test the OEM install of beta1?20:25
santa_wxl: sure, link?20:25
wxlsanta_: amd64 i assume?20:25
santa_wxl: yep20:25
acheronukwxl: hmm. copying to a different drive seemed to help. weird20:25
wxlsanta_: http://iso.qa.ubuntu.com/qatracker/milestones/373/builds/143162/testcases/1305/results20:25
wxlso do we get a discount on thsoe?20:28
wxlif not maybe we should take advantage of the sale and order a bunch20:28
wxl$89 gets us $5 off shipping, too20:29
acheronukok. and that boots to a black screen. there ends my patience with kvm. sorry20:29
wxl^^ that might be good to request of kubuntu fundage20:29
wxlacheronuk: initial boot?20:30
santa_wxl: downloading, thanks for taking care of the isos20:30
wxlsanta_: np20:30
acheronukwxl: well, I have a panel. nothing else20:34
wxlacheronuk: yeah well thanks for trying. santa_ will have to take care of it :) meanwhile, you working on the other cases?20:35
santa_regarding the complaints of perms, are you using virt-manager too acheronuk?20:38
acheronuksanta_: I was20:39
santa_but not anymore? why?20:39
acheronuktrying other stuff for now. never like that very much anyway20:41
wxlsanta_: fwiw flocculant of xubuntu fame says he has had no problem recently with kvm20:42
santa_aha20:42
santa_for me it's working better than ever20:42
wxlsanta_: so if you can confirm that, then i'll just assume it's a vbox issue20:43
santa_virtualbox. on the other hand, is giving me black screens20:43
wxlanyone capable of testing on real hardware?20:43
DarinMillerwxl: Fixing the Kubuntu OEM setup guidelines now and a saw the black screen for the first time.20:43
wxlDarinMiller: real hardware or vbox?20:43
DarinMillerwxl: it's just plasma...20:43
DarinMillervbox20:43
wxlphew20:43
santa_wxl: btw virtualbox precisely is giving me black screens with20:43
santa_* yakkety iso20:44
santa_* plasma 5.920:44
santa_(at least)20:44
wxlsanta_: yeah actually i had problems with the yakkety install on vbox20:44
santa_so I switched to virt-manager recently20:44
DarinMillerresize the window to see the bottom panel or use krunner to launch the terminal.  The killall plasmashell && plasmashell &20:44
santa_as I said is working very well since QXL is the default for the spice monitors20:45
wxlDarinMiller: resize the window? with a blank screen? XD20:45
DarinMillerthe vt window20:45
DarinMillervbox window20:45
wxloh interesting20:46
DarinMilleronce 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
acheronukare none of these test cases actually up to date for current ubiqity? sigh.......20:47
wxlDarinMiller: that's because our default is not folder view20:48
wxli.e. kde-specific problem20:48
wxlacheronuk: well they are general ones, possibly appropriate for ubuntu ubiquity20:48
acheronukand the folder containment overlapping the desktop toolbox in the live session is getting on my nerves :P20:49
DarinMillerlive sessions shoud have desktop folder displayed (but understood regarding default views postinstalls).20:49
wxlpersonally i think folder view makes a lot more sense20:49
wxlto be clear, how do you resize the window?20:51
DarinMillerthe vbox window?20:51
wxlyeah20:51
DarinMillerI used my mouse.20:52
DarinMillernormal window resize.20:52
wxlnot making any difference for me20:52
DarinMillerno black background with a panel at the bottom?20:53
wxlno, i just have everything black20:53
wxlplasmashell ain't running20:53
DarinMillerfor grins, try to lauch krunner (alt-spacebar) when the vbox window has focus.20:53
wxli tried a bunch of things and no go20:53
DarinMillerok my "black screen" is different than yours.20:54
wxli guess so20:54
ahoneybunwxl: https://code.launchpad.net/~aaronhoneycutt/ubiquity-slideshow-ubuntu/zesty20:59
ahoneybunupdating the kubuntu-slideshow.py to PyQt520:59
wxlooooh :)20:59
ahoneybungot it to open and run but no slides20:59
wxlno slides like you haven't made the slides or it simply didn't work?21:00
acheronukahoneybun: where are those kubuntu stickers?21:00
ahoneybunwxl: the slides are there21:00
ahoneybunjust not loading21:00
ahoneybunacheronuk: stickers?21:00
acheronukahoneybun: oh. KDE. not kubuntu21:00
ahoneybunacheronuk: KDE yep21:01
ahoneybunvalorie has some Kubuntu ones21:01
acheronukhah. there is nothing kubuntu at all on there. they must think we are dead.21:01
wxlahoneybun: have you tried checking in at #ubuntu-installer?21:01
wxlacheronuk: more likely we haven't reached out to them21:01
ahoneybunI'm in there wxl21:01
ahoneybunwell Ubuntu just got some stickers on unixstickers21:02
wxlbrb tacos are calling my name21:02
ahoneybunwxl: 21:12
ahoneybunhttp://imgur.com/a/Rj3OA21:12
ahoneybunusing the test-slideshow.sh21:12
ahoneybunhttp://bazaar.launchpad.net/~aaronhoneycutt/ubiquity-slideshow-ubuntu/zesty/revision/76221:19
wxlahoneybun: i'm not ubiquity dev fwiw :)21:50
IrcsomeBot<tsimonq2> And I start training to be one on Saturday :P21:51
IrcsomeBot<acheronuk> @tsimonq2, if there *anything* you're not trying to be?21:52
IrcsomeBot<acheronuk> *is21:52
IrcsomeBot<tsimonq2> Oh be quiet21:53
wxldoes anyone know how to directly call the settings for a particular panel? one of my two panels shows it and immediately makes it disappear21:53
IrcsomeBot<acheronuk> just joking. :P21:53
wxlor maybe there's a config file i could just edit to my liking?21:54
wxlrestarting plasma did the trick21:56
IrcsomeBot<ahoneybun> I know wxl21:58
IrcsomeBot<ahoneybun> You were just asking about the number thing21:58
IrcsomeBot<ahoneybun> Version numbrr21:58
clivejoanyone ever experienced this bug - https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/99720022:02
ubottuLaunchpad bug 997200 in update-manager (Ubuntu) "[FFe] Add NetworkManager connectivity config package" [High,Confirmed]22:02
wxlright right22:05
-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
DarinMillerwxl: I created "Kubuntu specific" OEM update mangaer checklist, but I have no idea how to do a bzr mp.22:32
-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
wxlDarinMiller: you can do it all through the web gui if you want. just push it to your personal repo to begin22:33
clivejoDarinMiller: https://packaging.neon.kde.org/applications/libkgapi.git/commit/?h=Neon/unstable&id=5f436b6fe6601410e5b9538491a0d0b3a93bf21322:33
DarinMillerclivejo: so they even renamed the -dev and -data references also.  Everything else was very similar to what I had proposed.22:37
clivejoI personally would have kept libkf5gapi-dev.install22:38
clivejoand installed those kf5 named cmake files there22:38
clivejosanta_: what would you do?22:40
clivejoDarinMiller: you wanna generate a MP for that now?22:43
santa_clivejo: I would need a bit more of context, this package isn't in apps 16.12 yet, correct?22:44
clivejocorrect22:44
clivejoits currently a stand alone package22:45
santa_so you are working on it for the kci?22:45
clivejo!info libkf5gapi-dev22:45
ubottulibkf5gapi-dev (source: libkgapi): Google API library for KDE -- development files. In component universe, is optional. Version 5.1.0-2 (zesty), package size 49 kB, installed size 635 kB22:45
clivejoyes22:45
clivejoupstream are moving in into applications22:45
clivejoand have renamed the libs22:46
clivejoI asked Darin to have a look at it22:46
santa_ok, let me check debian22:46
clivejoKDE Neon made this commit - https://packaging.neon.kde.org/applications/libkgapi.git/commit/?h=Neon/unstable&id=5f436b6fe6601410e5b9538491a0d0b3a93bf21322:47
santa_allright22:47
santa_https://packages.qa.debian.org/libk/libkgapi.html22:47
santa_https://anonscm.debian.org/git/pkg-kde/kde-extras/libkgapi.git22:47
santa_https://anonscm.debian.org/git/pkg-kde/kde-extras/libkgapi.git/commit/?id=5f436b6fe6601410e5b9538491a0d0b3a93bf21322:47
santa_clivejo: I would merge with the debian master branch22:48
clivejodue to moving into apps they have renamed the libs from libKF5GAPIBlogger > libKPimGAPIBlogger22:48
santa_aha22:49
clivejomost of it I agree with22:49
santa_so, yes, I would follow neon/debian22:49
clivejobar the transitional cmake files in the new -dev package22:49
clivejousr/lib/*/cmake/KF5GAPI/KF5GAPIConfig.cmake etc22:49
DarinMillerwxl: I have no idea how go from:   bzr branch lp:ubuntu-manual-tests to   dput -f ppa:darinsmiller/kubuntu-docs <something?>22:50
clivejoin my attempt at this I kept libkf5gapi-dev.install with usr/lib/*/cmake/KF5GAPI/22:50
DarinMillerwxl: nor do I know how or where the to upload via the web.22:50
wxlDarinMiller: if it was git, you'd git push, right? same deal. :)22:51
wxldput is for package uploads22:51
wxlassumedly you shouldn't have a full package, but simply a bit of code22:51
DarinMillerjust a modified text file22:52
DarinMillerActually a brand new file as I did not want to stomp on the old one.22:52
wxlyes that's correct22:52
DarinMillerI did the bzr add and commit but then realizied I did not know where to push if for an mp.22:52
wxlso bzr push lp:darinsmiller/something-or-other22:53
wxland then go to the page in your code and propose for merging22:53
clivejomy logical is that our old stuff will have build dep on libkf5gapi-dev22:53
wxlsorry lp:~darinsmiller22:53
clivejowhich can be removed once everything is using the new lib names22:54
wxlsorry lp:~darinsmiller/ubuntu-manual-tests would make the most sense of course :)22:54
wxlas 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-details22:54
santa_<clivejo> my logical is that our old stuff will have build dep on libkf5gapi-dev22:55
wxlmy logical's bigger than yous22:55
clivejologic22:55
santa_you have to add some dummy transitional packagers22:55
santa_* packages22:55
santa_we have enough dummy packagers! XD22:56
santa_clivejo: so the minimal thing would be a transitional package for the -dev I think22:56
santa_that, at least22:57
DarinMillerwxl: I used bzr push lp:~darinsmiller/kubuntu-docs/ubuntu-manual23:03
DarinMillerwhich:  Created new stacked branch referring to /+branch-id/72443723:04
DarinMillerBut I cannot find new packages on my lp page.23:05
wxloh boy23:05
DarinMillernm Found it23:06
DarinMillerhttps://code.launchpad.net/~darinsmiller/kubuntu-docs/ubuntu-manual-tests23:06
wxlkubuntu-docs was a strange place but there ya go :)23:06
DarinMillerI always forget about the bazillion little hidden clicks to find everything...23:06
DarinMillerso proceed with mp from here?23:07
wxlyep yep23:08
wxlhttps://code.launchpad.net/~darinsmiller/kubuntu-docs/ubuntu-manual-tests/+register-merge23:08
wxlmake sure to select the right target :)23:08
wxlalso make sure to make me a reviewer23:09
DarinMillertarget = ubuntu-manual-tests ?23:09
wxlyes23:10
wxlbtw have i mentioned how much i love !lp and !lpbug in ddg?23:10
valoriebtw, still have loads of kubuntu stickers23:14
valorienobody requested any from me23:14
DarinMillerwxl: ubuntu-manual-tests is an invalid target.23:15
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 akademy23:21
wxlDarinMiller: ~ubuntu-testcase/ubuntu-manual-tests/trunk23:26
acheronukI would like a few, but equally in no hurry23:27
acheronukstickers ^^^23:27
=== santa is now known as Guest19974
=== Guest19974 is now known as santa_
DarinMillerwxl: New error: This branch is not mergeable into lp:ubuntu-manual-tests23:33
wxlwhaaaaaa?23:34
DarinMiller akonoaki-calendar23:34
* clivejo is confused23:34
wxlDarinMiller: did you see above i said to use lp:~ubuntu-testcase/ubuntu-manual-tests?23:35
valorieakademy is coming right up!23:40
valorieat least I hope so23:41
clivejoits months away23:41
acheronuk7 months?23:41
valorieno date yet23:42
valorieno place for sure yet23:42
acheronuksomewhere with good beer23:43
valorieI think it's Munich vs southern Spain23:45
valorieboth of which sound great to me23:45
acheronukheh: http://www.oktoberfest.de/en/23:47
acheronukMunich Oktoberfest23:47
acheronuk(09/16/17 - 10/03/17)23:47
=== himcesjf is now known as Guest56107
acheronukclivejo: wow https://launchpad.net/ubuntu/+source/gcc-6/6.3.0-8ubuntu1/+build/1204049223:57
acheronukit actually built!23:58
acheronuk(took 1 day, 7 hours, 8 minutes, 11.0 seconds) 23:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!