[00:03] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:03] -kubuntu-ci:#kubuntu-devel- Project merger_kdesignerplugin build #884: FIXED in 2 min 42 sec: https://kci.pangea.pub/job/merger_kdesignerplugin/884/
[00:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevplatform build #185: UNSTABLE in 30 min: https://kci.pangea.pub/job/xenial_unstable_kdevplatform/185/
[00:04] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:04] -kubuntu-ci:#kubuntu-devel- Project merger_kqtquickcharts build #238: FIXED in 1 min 37 sec: https://kci.pangea.pub/job/merger_kqtquickcharts/238/
[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #829: FIXED in 7 min 17 sec: https://kci.pangea.pub/job/mgmt_merger/829/
[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #809: FIXED in 7 min 20 sec: https://kci.pangea.pub/job/mgmt_progenitor/809/
[00:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop build #133: STILL FAILING in 4 min 29 sec: https://kci.pangea.pub/job/xenial_unstable_kdevelop/133/
[00:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #126: FAILURE in 10 min: https://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/126/
[00:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmailtransport build #129: STILL FAILING in 15 min: https://kci.pangea.pub/job/zesty_unstable_kmailtransport/129/
[00:25] <mamarley> acheronUK: Yep, I saw it was building earlier today.  Just a minute and I will install it.
[00:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #407: FAILURE in 1 min 56 sec: https://kci.pangea.pub/job/xenial_unstable_kstars/407/
[00:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdesdk-kioslaves build #84: FAILURE in 16 min: https://kci.pangea.pub/job/zesty_unstable_kdesdk-kioslaves/84/
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #236: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_spectacle/236/
[00:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #77: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_kproperty/77/
[00:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-pa build #370: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_plasma-pa/370/
[00:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-dev-utils build #101: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/zesty_unstable_kde-dev-utils/101/
[00:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pimcommon build #105: STILL FAILING in 24 min: https://kci.pangea.pub/job/zesty_unstable_pimcommon/105/
[00:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #141: FAILURE in 1 min 51 sec: https://kci.pangea.pub/job/zesty_unstable_kstars/141/
[00:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeconnect-kde build #109: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/zesty_unstable_kdeconnect-kde/109/
[00:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #109: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/zesty_unstable_cantor/109/
[00:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #77: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/xenial_unstable_kdb/77/
[00:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #271: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/271/
[00:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #105: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/xenial_unstable_kdiagram/105/
[00:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-dev-utils build #150: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/xenial_unstable_kde-dev-utils/150/
[00:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ark build #129: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/zesty_unstable_ark/129/
[00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-python build #104: STILL FAILING in 11 min: https://kci.pangea.pub/job/xenial_unstable_kdev-python/104/
[00:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #142: STILL FAILING in 3 min 13 sec: https://kci.pangea.pub/job/zesty_unstable_kstars/142/
[00:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #408: STILL FAILING in 4 min 7 sec: https://kci.pangea.pub/job/xenial_unstable_kstars/408/
[00:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #127: STILL FAILING in 4 min 35 sec: https://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/127/
[00:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdesdk-kioslaves build #85: STILL FAILING in 4 min 49 sec: https://kci.pangea.pub/job/zesty_unstable_kdesdk-kioslaves/85/
[00:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #160: FAILURE in 4 min 50 sec: https://kci.pangea.pub/job/xenial_unstable_discover/160/
[00:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #142: STILL FAILING in 43 min: https://kci.pangea.pub/job/zesty_unstable_marble/142/
[00:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_mailimporter build #52: STILL FAILING in 19 min: https://kci.pangea.pub/job/zesty_unstable_mailimporter/52/
[00:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_minuet build #128: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/xenial_unstable_minuet/128/
[00:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-extras build #126: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/zesty_unstable_kio-extras/126/
[00:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-python build #105: STILL FAILING in 4 min 36 sec: https://kci.pangea.pub/job/xenial_unstable_kdev-python/105/
[00:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #161: STILL FAILING in 3 min 56 sec: https://kci.pangea.pub/job/xenial_unstable_discover/161/
[00:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop build #134: STILL FAILING in 2 min 45 sec: https://kci.pangea.pub/job/xenial_unstable_kdevelop/134/
[00:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_frameworkintegration build #412: FAILURE in 4 min 40 sec: https://kci.pangea.pub/job/xenial_unstable_frameworkintegration/412/
[01:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmailtransport build #130: STILL FAILING in 20 min: https://kci.pangea.pub/job/zesty_unstable_kmailtransport/130/
[01:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #82: STILL UNSTABLE in 29 min: https://kci.pangea.pub/job/zesty_unstable_kalzium/82/
[01:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #202: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/202/
[01:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #59: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/xenial_unstable_k3b/59/
[01:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pimcommon build #106: STILL FAILING in 21 min: https://kci.pangea.pub/job/zesty_unstable_pimcommon/106/
[01:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #106: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/zesty_unstable_kdiagram/106/
[01:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop build #135: STILL FAILING in 5 min 43 sec: https://kci.pangea.pub/job/xenial_unstable_kdevelop/135/
[01:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_k3b build #55: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/zesty_unstable_k3b/55/
[01:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_mailimporter build #53: STILL FAILING in 14 min: https://kci.pangea.pub/job/zesty_unstable_mailimporter/53/
[01:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_frameworkintegration build #413: STILL FAILING in 7 min 0 sec: https://kci.pangea.pub/job/xenial_unstable_frameworkintegration/413/
[01:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #72: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/xenial_unstable_trojita/72/
[01:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #131: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/xenial_unstable_marble/131/
[01:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-extras build #330: STILL UNSTABLE in 17 min: https://kci.pangea.pub/job/xenial_unstable_kio-extras/330/
[01:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #308: STILL UNSTABLE in 17 min: https://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/308/
[01:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ark build #444: STILL UNSTABLE in 17 min: https://kci.pangea.pub/job/xenial_unstable_ark/444/
[01:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #182: STILL UNSTABLE in 17 min: https://kci.pangea.pub/job/xenial_unstable_kalzium/182/
[01:29]  * tsimonq2 just figured out that acheronUK changed his nick :P
[01:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #93: STILL UNSTABLE in 1 hr 10 min: https://kci.pangea.pub/job/xenial_unstable_krita/93/
[01:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevplatform build #186: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/xenial_unstable_kdevplatform/186/
[01:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #143: STILL FAILING in 37 min: https://kci.pangea.pub/job/zesty_unstable_marble/143/
[01:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #246: STILL UNSTABLE in 13 min: https://kci.pangea.pub/job/xenial_unstable_kpimtextedit/246/
[01:48] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #120: STILL UNSTABLE in 1 hr 24 min: https://kci.pangea.pub/job/zesty_unstable_krita/120/
[01:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libksieve build #143: STILL UNSTABLE in 13 min: https://kci.pangea.pub/job/xenial_unstable_libksieve/143/
[01:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_incidenceeditor build #89: STILL UNSTABLE in 15 min: https://kci.pangea.pub/job/zesty_unstable_incidenceeditor/89/
[02:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_korganizer build #94: STILL UNSTABLE in 15 min: https://kci.pangea.pub/job/xenial_unstable_korganizer/94/
[03:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #106: STILL UNSTABLE in 1 hr 38 min: https://kci.pangea.pub/job/xenial_unstable_calligra/106/
[03:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #91: STILL UNSTABLE in 1 hr 33 min: https://kci.pangea.pub/job/zesty_unstable_calligra/91/
[03:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #128: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/zesty_unstable_kdbusaddons/128/
[03:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #131: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/131/
[03:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemviews build #121: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/zesty_unstable_kitemviews/121/
[03:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcoreaddons build #102: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/zesty_unstable_kcoreaddons/102/
[03:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kguiaddons build #397: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/xenial_unstable_kguiaddons/397/
[03:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdbusaddons build #424: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/xenial_unstable_kdbusaddons/424/
[03:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcodecs build #400: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/xenial_unstable_kcodecs/400/
[03:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #419: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/xenial_unstable_ki18n/419/
[03:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfig build #435: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/xenial_unstable_kconfig/435/
[03:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemviews build #391: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/xenial_unstable_kitemviews/391/
[04:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjobwidgets build #122: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/zesty_unstable_kjobwidgets/122/
[04:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfigwidgets build #85: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/zesty_unstable_kconfigwidgets/85/
[04:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #392: STILL UNSTABLE in 12 min: https://kci.pangea.pub/job/xenial_unstable_kcoreaddons/392/
[07:08] <lordievader> Good morning.
[09:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1380: SUCCESS in 1 min 4 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1380/
[09:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1380: SUCCESS in 1 min 29 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1380/
[09:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1380: SUCCESS in 3 min 0 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1380/
[09:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1380: SUCCESS in 3 min 14 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1380/
[10:26] <BluesKaj> HI folks
[11:29] <clivejo> anyone here know python?
[11:45] <lordievader> clivejo: Yes?
[11:46] <clivejo> may I PM?
[11:46] <lordievader> Sure
[13:19] <marco-parillo> acheronUK: You mentioned Plasma 5.9.4? sudo add-apt-repository ppa:kubuntu-ppa/staging-plasma ?
[13:21] <acheronUK> marco-parillo: correct. staged for zesty. hopefully to upload once the beta and it's freeze are done
[13:23] <BluesKaj> marco-parillo, installed beta 2 yesterday and all is well so far ...haven't added any ppas yet
[13:23] <marco-parillo> acheronUK: Thank you. Since no new Beta 2 images for ZZ came this morning (http://iso.qa.ubuntu.com/qatracker/milestones/374/builds), I will add the PPA to yesterday's beta image and smoke test in a VM.
[13:40] <marco-parillo> Upgrading 83 packages.
[13:58] <marco-parillo> The upgrade appeared successful. Re-booted my VM, and kinfocenter reports 5.9.4
[14:04] <mamarley> It works fine on all my systems too, good job! :)
[14:07] <marco-parillo> Discover, Dolphin, FF, Kate, Konversation, System Monitor, and System Settings all pass an initial sanity test.
[14:07] <mamarley> Most of that stuff is either Applications or non-KDE entirely.
[14:09] <marco-parillo> And in a perfectly architected system, they should continue to work because the layers are completely decoupled.
[14:12] <marco-parillo> Well, Discover did crash when I tried to uncheck the box for staging-plasma.
[14:19] <acheronUK> Discover crashes whenever it feels like it!
[14:19] <acheronUK> mparillo: great testing so far. thanks :)
[14:21] <marco-parillo> I suppose there is zero chance to get it into a new spin for Beta 2?
[14:21] <acheronUK> mparillo: yes, unless it get's respun to fix issues, the beta is basically yesterday's image. 
[14:21] <acheronUK> marco-parillo: you I mean
[14:22] <acheronUK> mparillo: nope. beta freeze was monday. 5.9.4 was released yesterday. just too late to go in :/
[14:23] <acheronUK> urgh. the two similar nicks confuse. lol
[14:23] <marco-parillo> Sorry it is confusing. mparillo is my KDE ID, which I use for the bouncer. But at work, IRC is blocked (I presume at the port level), so I need to use web-chat, so for that I use my launchpad ID.
[14:23] <acheronUK> no problem :)
[14:38] <tsimonq2> clivejo: I know Python
[14:48] <marco-parillo> BluesKaj: Thank you for testing Beta 2. Would you be able to add a completion to: http://iso.qa.ubuntu.com/qatracker/milestones/374/builds ? Even if it is a duplicate of one I passed, all my testing is in VMs, so a separate passing result on HW would be a good vote of confidence.
[14:51] <marco-parillo> !testers
[14:52] <shadeslayer> ubottu: !testers is Help is needed in #kubuntu-devel. Please ping Riddell, yofel, soee, Tm_T, BluesKaj, James147, Quintasan, lordievader, shrini, tester56, parad1se, mamarley, alket, SourBlues, sgclark, neo31, vip, mparillo, wxl, DarinMiller, tsimonq2 for information
[14:52] <shadeslayer> oh noes :(
[14:52] <marco-parillo> You can test Beta 2 http://iso.qa.ubuntu.com/qatracker/milestones/374/builds or help acheronUK test Plasma 5.9.5, ideally on Beta 2.
[14:52] <tsimonq2> shadeslayer: What?
[14:53] <shadeslayer> tsimonq2: I'm trying to remove my highlight
[14:53] <tsimonq2> shadeslayer: Ok gotcha
[14:53] <shadeslayer> should I simply go !testers is .....
[14:56] <shadeslayer> oh heh, edit request forwarded 
[14:56] <shadeslayer> ok
[14:59] <acheronUK> ubottu: testers is <reply>  Help is needed in #kubuntu-devel. Please ping Riddell, yofel, soee, Tm_T, BluesKaj, James147, Quintasan, lordievader, shrini, tester56, parad1se, mamarley, alket, SourBlues, sgclark, neo31, vip, mparillo, wxl, DarinMiller, tsimonq2 for information
[14:59] <acheronUK> would be that I think? ^^^
[15:00] <acheronUK> if I had permission to change it, which I don't...
[15:00] <shadeslayer> yeah I think you need permissions
[15:00] <shadeslayer> ubottu said my request was forwarded to people who do have permissions
[15:00] <acheronUK> lol
[15:00] <shadeslayer> I believed in you ubottu!
[15:01] <acheronUK> !cookies
[15:01] <acheronUK> still has cookies at least :)
[15:01] <yofel> !yum
[15:01] <yofel> !apt
[15:01] <yofel> meh
[15:01] <tsimonq2> !beer
[15:02] <tsimonq2> !cookie
[15:02] <tsimonq2> THERE we go :P
[15:02] <tsimonq2> !cookie | acheronUK 
[15:02] <tsimonq2> Hahahahahahahaha
[15:02] <yofel> lol
[15:02] <yofel> cheapstake :D
[15:02] <acheronUK> mean with the cookies :/
[15:02] <tsimonq2> Let's make it not do that, hold on :P
[15:03] <tsimonq2> !beer
[15:03] <tsimonq2> !cookies | acheronUK 
[15:03] <tsimonq2> :D
[15:03] <tsimonq2> ENough playing, I have to get this to build... :P
[15:03] <tsimonq2> *Enough
[15:03] <yofel> hm, I remember asking someone if there's any remains of kubotu somewhere... who was that -.-
[15:04] <clivejo> yofel: gonna give it the kiss of life?
[15:04] <tsimonq2> Riddell: Where is kubotu? :O
[15:05] <yofel> harald was maintaining that on some ubuntu server I think... which is why I got pointed to someone - that never got back to me IIRC
[15:05] <clivejo> tsimonq2: ok, you know python, whats it complaining about here - https://launchpadlibrarian.net/311879162/buildlog_ubuntu-zesty-amd64.mycroft-core_0.8.7-0ubuntu1~ubuntu17.04~ppa5_BUILDING.txt.gz
[15:07] <yofel> hm, why is it running virtualenv?
[15:08] <yofel> but you're getting an error because you're trying to install python packages from a remote repostiory. The launchpad buildds have no internet access
[15:09] <clivejo> yofel: WWYD
[15:09] <tsimonq2> ^^^^^
[15:11] <yofel> not sure, I'm no python packaging expert and the last thing I touched was like 3 years ago. I didn't even know dh_virtualenv was a thing...
[15:11] <yofel> why do you need that anyway? The package should be operating just fine in the system env
[15:12] <davmor2> try on #launchpad explain what you are trying to do and see if they have a suggestion
[15:13] <yofel> clivejo: our 'kajongg' package is python, tried setting it up like that?
[15:14] <clivejo> they are missing some modules 
[15:14] <clivejo> so they been injecting them in via the packaging
[15:14] <clivejo> which Im trying to strip out
[15:18] <yofel> if they're embedded in the source, that's not nice, but technically allowed. Otherwise you'll have to package them as well if they're not yet in the archive as installing over pip won't work on the buildds
[15:21] <clivejo> how do I tell it not to use pip?
[15:21] <yofel> virtualenv has a --system-site-packages option, which should make it recognise the system setuptools at least...
[15:21] <yofel> seems like that's dh_virtualenv -S
[15:22] <clivejo> but you said not to use virtualenv?
[15:23] <yofel> well, I'm not sure why you're using it, so I'm working on the assumption that there is some reason? I would try it without that first
[15:24] <tsimonq2> davmor2: He did last night
[15:26] <davmor2> ah
[15:40] <clivejo> I hate python
[15:40] <tsimonq2> clivejo: I love Python
[15:40] <yofel> nah, python's fine. Just be happy that you're not packaging a c# thing
[15:41] <yofel> the old kimono packaging was fun
[15:41] <clivejo> how do I get the darn thing to build
[15:41] <yofel> well, it was still kdebindings back then
[15:41] <tsimonq2> yofel: Or Ruby... *runs*
[15:41] <yofel> mhm
[15:41] <yofel> I don't think that's that different from python?
[15:42] <yofel> packaging wise I mean
[15:42] <yofel> the language is fun D:
[15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1381: SUCCESS in 50 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1381/
[15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1381: SUCCESS in 54 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1381/
[15:47] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1381: SUCCESS in 2 min 35 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1381/
[15:47] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1381: SUCCESS in 2 min 43 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1381/
[16:32] <wxl> yiiiiikes
[16:32] <wxl> oh phew
[16:32] <tsimonq2> wxl: What?
[16:32] <wxl> nevermind
[16:32] <tsimonq2> wxl: What?
[16:32] <wxl> i looked at the qa tracker too quickly
[16:32] <tsimonq2> Now you have to tell us anyways :P
[16:50] <marco-parillo> I am so happy the grammar police are all at the doughnut shop.
[16:51] <acheronUK> ???
[16:51] <mamarley> Wee-ooo-wee-ooo-wee-ooo
[16:51] <mamarley> Somebody called the grammar police?
[20:00] <wxl> hey anyone testing on real hardware?
[20:00] <wxl> especially that has wifi
[20:00] <wxl> cuz bug 1675127 needs some checking
[20:07] <dmj_s76> How does Kubuntu handle hidpi scaling at the moment?
[20:10] <mamarley> dmj_s76: It works pretty well for me.  Most apps seem to scale at least acceptably.  The taskbar is a bit small by default and some root apps don't scale right though.
[20:10] <mamarley> Occasional icons and buttons are too small if they were defined with pixel sizes.
[20:11] <dmj_s76> mamarley: If you change the system scaling factor (I assume there is one) do the applications update without closing and reopening them?
[20:12] <mamarley> dmj_s76: Not sure.  In my case (with the NVIDIA blob) X reads the DPI from the monitor and everything scales appropriately.  I have never tried reconfiguring it manually.
[20:14] <dmj_s76> On vanilla Ubuntu, the scaling factor doesn't seem to take effect until the next time the application starts, so I'm trying to figure out if KDE does something different that could be incorporated.
[20:14] <mamarley> Not sure, sorry.
[20:17] <dmj_s76> mamarley: I suspect that Qt might need some upgrades to handle changing scale factors.
[20:17] <dmj_s76> This tends to be an issue with external monitors with different factors
[20:18] <mamarley> I don't have any systems with different DPIs on different monitors, so I can't comment.
[20:28] <ahoneybun> dmj_s76: KDE apps also all use svg so scaling of graphics is much better 
[20:29] <dmj_s76> ahoneybun: yes, though scaling by integer factors is still important even when your source is an svg
[20:30] <ahoneybun> right
[20:31] <dmj_s76> the real sticking point I'm looking to get fixed is the case of a hidpi laptop being connected to a lowdpi external monitor
[20:33] <dmj_s76> The experience is quite bad unless applications scale at runtime.
 I don't have any hidpi machines to help test
 Only 1080p
[20:38] <genii> !testers
[20:38]  * genii runs away
[20:57]  * clivejo beats python with a big stick
[21:06] <clivejo> it was self defence
[21:19] <clivejo> ah Ive had enough
[21:38] <mparillo> genii: You called for testers? I assume for Beta 2 with hidipi?
[21:41] <genii> mparillo: There was a factoid change request from acheronUK which landed in -ops, made the change and just seeing if it worked .
[21:43] <mparillo> Well, for you penance, can you record a few test results for Beta 2? (http://iso.qa.ubuntu.com/qatracker/milestones/374/builds)
[21:44] <mparillo> s/you/your/
[21:48] <genii> I don't have a machine handy for that today 
[21:49] <genii> Probably add to it tomorrow with 2 different machines though
[21:52] <mparillo> TY. I know all six of my results (all passes BTW) were on VMs. Good news is that the blank screen bug is gone for me. I am not sure if that is Beta 2 or the upgrade to VirtualBox since Beta 1.
[22:22] <wxl> !testers
[22:22] <wxl> um
[22:22] <wxl> well anyways it would be really helpful if we could get those last few testcases done
[22:23] <wxl> novel indeed :)
[22:29]  * acheronuk welcomes ubottu back ^^^
 does discover crash on exit for anyone?
[22:30]  * valorie tries it out
[22:31] <wxl> zesty i'm assuming?
[22:31]  * yofel wonders how the ci tests are working in neon...
[22:31] <acheronuk> doesn't see to for me
[22:32] <valorie> \o/ I'm getting peruse!
[22:32] <acheronuk> are you?
[22:33] <valorie> from discover
[22:33] <valorie> let's see if it actually installed -- since it never asked for my password
[22:33] <valorie> :(
[22:33] <valorie> btw, my computer never froze last night!
[22:33] <valorie> top ran all night with no problem
[22:34] <acheronuk> puruse is in one of the ppas. not in the archive
[22:34] <valorie> well, Discover offered it
[22:34] <wxl> valorie: that sounds like something reasonable to expect :)
[22:34] <valorie> wxl: so one would think
[22:34] <wxl> similarly i'm happy to report that our dovecot did not drop any clients yesterday due to hitting the process limit for imap-logins
[22:34] <acheronuk>  apt-cache policy peruse
[22:34] <acheronuk> peruse:
[22:34] <acheronuk>   Installed: 1.2-0ubuntu1~ubuntu17.04~ppa4
[22:34] <acheronuk>   Candidate: 1.2-0ubuntu1~ubuntu17.04~ppa4
[22:34] <acheronuk>   Version table:
[22:34] <valorie> and yet it has been freezing randomly for weeks
[22:34] <acheronuk>  *** 1.2-0ubuntu1~ubuntu17.04~ppa4 500
[22:35] <acheronuk>         500 http://ppa.launchpad.net/kubuntu-ppa/staging-misc/ubuntu zesty/main amd64 Packages
[22:35] <acheronuk>         100 /var/lib/dpkg/status
[22:35] <wxl> also i'm happy to report that i was able to get a recent version of thunderbird beta from the "official" ppas after months of failed builds
[22:35] <acheronuk> ah, yes. in staging misc. so discover would see it in there I expect
[22:35] <valorie> peruse:
[22:35] <valorie>   Installed: (none)
[22:35] <valorie>   Candidate: (none
[22:35] <wxl> man if life goes any smoother, i don't know what i'll do with myself
[22:35] <valorie> I'm wondering why Discover offered it
[22:36] <valorie> otoh, it did not crash on exit
[22:36] <valorie> wxl: docs, docs, docs!
[22:38] <acheronuk> anyone tested digikam 5.5? in staging-misc ppa
[22:38] <valorie> I tested it on 16.04 awhile ago, for Clive
[22:39] <valorie> not since, and not on zesty
[22:39] <valorie> I don't quite understand how it works
[22:53] <acheronuk> valorie: I don't use it either :/
[22:58] <valorie> huh, doing a routine update && upgrade, system is telling me I should choose a password to be used for turning off secure boot
[22:58] <valorie> or I may not be able to use 3rd party software -- I assume the nvidia blob
[22:59] <valorie> any opinions either way?
[23:03] <acheronuk> not here. I tend to turn off secure boot entirely, wipe the disc and install linux in bios mode. 
[23:03] <mamarley> I always recommend disabling SecureBoot as it is a method invented by Microsoft® to control what you can run on your PC.
[23:03] <mamarley> Do not confuse UEFI and SecureBoot though.
[23:04] <mamarley> SecureBoot requires UEFI to work, but you can (and should) disable SecureBoot without also disabling UEFI.
[23:04] <acheronuk> can, but I would rather
[23:05] <acheronuk> if I was dual booting, that would be different. but I'm not. 
[23:05] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #76: STILL FAILING in 4 min 44 sec: https://kci.pangea.pub/job/mgmt_tooling/76/
[23:05] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Fix cassette usage in deploy upgrade test
[23:05] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Fix missing command on docker create
[23:05] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Update test image series
[23:05] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Update test data cassettes
[23:05] -kubuntu-ci:#kubuntu-devel- Failed tests:
[23:05] -kubuntu-ci:#kubuntu-devel- CI::BuildBinaryTest.test_build_bin_only: https://kci.pangea.pub/job/mgmt_tooling/76/testReport/junit/junit/(root)/CI__BuildBinaryTest/test_build_bin_only
[23:05] -kubuntu-ci:#kubuntu-devel- CI::BuildBinaryTest.test_build_package: https://kci.pangea.pub/job/mgmt_tooling/76/testReport/junit/junit/(root)/CI__BuildBinaryTest/test_build_package
[23:05] -kubuntu-ci:#kubuntu-devel- CI::BuildBinaryTest.test_dep_resolve_bin_only: https://kci.pangea.pub/job/mgmt_tooling/76/testReport/junit/junit/(root)/CI__BuildBinaryTest/test_dep_resolve_bin_only
[23:05] -kubuntu-ci:#kubuntu-devel- CI::OrigSourceBuilderTest.test_existing_builddir: https://kci.pangea.pub/job/mgmt_tooling/76/testReport/junit/junit/(root)/CI__OrigSourceBuilderTest/test_existing_builddir
[23:05] -kubuntu-ci:#kubuntu-devel- CI::OrigSourceBuilderTest.test_run: https://kci.pangea.pub/job/mgmt_tooling/76/testReport/junit/junit/(root)/CI__OrigSourceBuilderTest/test_run
[23:05] -kubuntu-ci:#kubuntu-devel- (39 more)
[23:06] <valorie> well, this is a dual boot
[23:06] <mamarley> If you have already installed the OS in UEFI mode, you cannot disable UEFI or your system won't boot.  You can disable SecureBoot though and both your OSes should still be fine.
[23:06] <acheronuk> can't advice then. as said, I've avoided that in recent years
[23:07] <valorie> ok
[23:07] <valorie> discussing with son as well
[23:07] <valorie> not sure why this all of a sudden popped up
[23:08] <valorie> but I assume I'll have to decide later, if not now
[23:08] <acheronuk> mamarley: yep, I know.
[23:08] <mamarley> Are you upgrading from Yakkety to Zesty or something?
[23:09] <valorie> mamarley: nope
[23:10] <mamarley> I remember hearing about some talk to enforce validation of kernel modules when using SecureBoot, and since the NVIDIA module is compiled locally on your system when you install the driver, it can't be validated in this way.  That's why you are seeing the message, but I can't explain why you are only just seeing it now.
[23:10] <valorie> just doing update && full-upgrade since adding the graphics ppa
[23:10] <valorie> the nvidia blob has been great so far
[23:10] <valorie> I'm going to say no, and give it up though if necessary
[23:11] <valorie> son is advising that otherwise I may have to reinstall
[23:11] <valorie> Do you want to continue? [Y/n] y
[23:12] <valorie> Setting up shim-signed (1.27+0.9+1474479173.6c180c6-1ubuntu1) ...
[23:12] <valorie> Installing for x86_64-efi platform.
[23:12] <valorie> Installation finished. No error reported.
[23:12] <valorie> W: APT had planned for dpkg to do more than it reported back (0 vs 4).
[23:12] <valorie>    Affected packages: shim-signed:amd64
[23:12] <valorie> after saying no
[23:12] <mamarley> If it has been working for you, there probably isn't practical reason to change now.
[23:13] <mamarley> But at some point in the future, the kernel module validation I mentioned might start happening.
[23:13] <valorie> seems like a good time to do another backup
[23:14] <mamarley> Backups never hurt. :)
[23:14] <valorie> yes, they leave me feeling a bit more secure
[23:14] <mamarley> What would probably happen if they did start validating kernel modules is that the NVIDIA module wouldn't load and you would either be stuck on the command line or get a low-resolution recovery environment.
[23:15] <mamarley> In that case, you could probably just disable SecureBoot from the UEFI configuration and it would start working again.
[23:15] <valorie> I never purged nouveau, so it would fall back on that, wouldn't it?
[23:16] <mamarley> I don't think so.  Nouveau is blacklisted when the blob is installed.
[23:17] <valorie> gads, why do these things have to be so complicated?
[23:18] <mamarley> Nouveau, being a KMS driver, has to be loaded very early in the boot process, before NVIDIA would normally load.  If Nouveau loads, NVIDIA cannot load.  Therefore, Nouveau must be blacklisted so it won't load.
[23:19] <mamarley> Really the problem here is Microsoft® and its SecureBoot abomination.  That is what makes it harder/more complicated to run alternative operating systems on one's PC.
[23:21] <dmj_s76> system76
[23:22] <dmj_s76> wrong tab :P
[23:22] <valorie> it is, and I keep considering whether or not it is worthwhile to keep windows installed, in case I have time to test some kde apps in it or so
[23:22] <valorie> otherwise I never use it
[23:23] <mamarley> Disabling SecureBoot won't break Windows.
[23:25] <dmj_s76> Secureboot isn't needed for Windows, and it's not an integral part of UEFI either
[23:26] <dmj_s76> Though it does make life a pain sometimes because you have to consider Secureboot enabled systems
[23:27] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #77: STILL FAILING in 4 min 44 sec: https://kci.pangea.pub/job/mgmt_tooling/77/
[23:27] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Update kci test case values
[23:27] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: More packages required to run the tests
[23:27] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Remove i386 from the ci-tooling tests
[23:27] -kubuntu-ci:#kubuntu-devel- Failed tests:
[23:27] -kubuntu-ci:#kubuntu-devel- Debian::DSCArchTwiddleTest.test_amd64: https://kci.pangea.pub/job/mgmt_tooling/77/testReport/junit/junit/(root)/Debian__DSCArchTwiddleTest/test_amd64
[23:27] -kubuntu-ci:#kubuntu-devel- Debian::DSCArchTwiddleTest.test_amd64_all: https://kci.pangea.pub/job/mgmt_tooling/77/testReport/junit/junit/(root)/Debian__DSCArchTwiddleTest/test_amd64_all
[23:27] -kubuntu-ci:#kubuntu-devel- CI::OrigSourceBuilderTest.test_existing_builddir: https://kci.pangea.pub/job/mgmt_tooling/77/testReport/junit/junit/(root)/CI__OrigSourceBuilderTest/test_existing_builddir
[23:27] -kubuntu-ci:#kubuntu-devel- CI::OrigSourceBuilderTest.test_run: https://kci.pangea.pub/job/mgmt_tooling/77/testReport/junit/junit/(root)/CI__OrigSourceBuilderTest/test_run
[23:27] -kubuntu-ci:#kubuntu-devel- CI::OrigSourceBuilderTest.test_symbols_strip: https://kci.pangea.pub/job/mgmt_tooling/77/testReport/junit/junit/(root)/CI__OrigSourceBuilderTest/test_symbols_strip
[23:27] -kubuntu-ci:#kubuntu-devel- (6 more)
[23:27] <mamarley> Microsoft does require PC manufacturers to enable SecureBoot in order to ship their PCs with Windows though, which is why most PCs come with it enabled.
[23:27] <mamarley> Up through Windows 8.1, they required that the user be able to disable SecureBoot.  With Windows 10, they stopped requiring that.
[23:28] <mamarley> I am afraid that at some point they will start requiring that the user cannot disable SecureBoot.
[23:29] <valorie> :(
[23:29] <dmj_s76> Yeah, that would be worrying for lots of people.
[23:29] <valorie> at some point I will prefer to have more room, rather than a win install I don't use
[23:30] <dmj_s76> ...all the computers around me right now are required to have Secureboot disabled by default (with an option to enable it)
[23:44] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #78: STILL FAILING in 4 min 50 sec: https://kci.pangea.pub/job/mgmt_tooling/78/
[23:44] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Fix the data file for the dsc tests
[23:44] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Set a default value for build stability
[23:44] -kubuntu-ci:#kubuntu-devel- Failed tests:
[23:44] -kubuntu-ci:#kubuntu-devel- KCIBuilderTest.test_update_symbols: https://kci.pangea.pub/job/mgmt_tooling/78/testReport/junit/junit/(root)/KCIBuilderTest/test_update_symbols
[23:44] -kubuntu-ci:#kubuntu-devel- KCITest.test_types: https://kci.pangea.pub/job/mgmt_tooling/78/testReport/junit/junit/(root)/KCITest/test_types
[23:44] -kubuntu-ci:#kubuntu-devel- NCIRepoCleanupTest.test_clean: https://kci.pangea.pub/job/mgmt_tooling/78/testReport/junit/junit/(root)/NCIRepoCleanupTest/test_clean
[23:44] -kubuntu-ci:#kubuntu-devel- PangeaDPutTest.test_run: https://kci.pangea.pub/job/mgmt_tooling/78/testReport/junit/junit/(root)/PangeaDPutTest/test_run
[23:44] -kubuntu-ci:#kubuntu-devel- ProjectsFactoryTest.test_launchpad_from_list: https://kci.pangea.pub/job/mgmt_tooling/78/testReport/junit/junit/(root)/ProjectsFactoryTest/test_launchpad_from_list
[23:52] <acheronuk> wxl: oem still fails in Virtualbox
[23:53] <wxl> yeah i don't know what to say about that
[23:53] <wxl> sigh
[23:53] <wxl> acheronuk: you going to do i386 too? :)
[23:57] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #79: STILL FAILING in 4 min 39 sec: https://kci.pangea.pub/job/mgmt_tooling/79/
[23:57] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Add bzr to the test requirements
[23:57] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Remove the stable build check while those don't exist
[23:57] -kubuntu-ci:#kubuntu-devel- * Philip Muškovac: Document that git is pedantic about user identification
[23:57] -kubuntu-ci:#kubuntu-devel- Failed tests:
[23:57] -kubuntu-ci:#kubuntu-devel- NCIRepoCleanupTest.test_clean: https://kci.pangea.pub/job/mgmt_tooling/79/testReport/junit/junit/(root)/NCIRepoCleanupTest/test_clean
[23:57] -kubuntu-ci:#kubuntu-devel- PangeaDPutTest.test_run: https://kci.pangea.pub/job/mgmt_tooling/79/testReport/junit/junit/(root)/PangeaDPutTest/test_run
[23:58] <acheronuk> wxl: some, maybe
[23:58] <wxl> acheronuk: or coerce someone else to do it :)
[23:58] <wxl> !testers
[23:58] <wxl> go test i386 people!
[23:59] <acheronuk> I've no idea who a lot of those are!
[23:59] <wxl> well i know tsimonq2 is out