[00:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #801: SUCCESS in 6 min 43 sec: http://kci.pangea.pub/job/mgmt_merger/801/ [00:12] santa_: nice charts [00:13] how recent are they? [00:15] Downloading Kubuntu 16.04.2 Desktop amd64 [00:16] clivejo: they are updated by a cron job every 5 minutes, see the generation date at the top; I have just added to my /etc/crontab a simple script executing ka-iron-hand, also see: https://phabricator.kde.org/w/kubuntu/black-operations/iron-hand/ [00:16] is there any way to colour code the ones that still have tests in progress? [00:16] like the excuses page, colour them blue? [00:17] and flag up the tests with regressions [00:17] maybe, but I would need time to dig into that [00:18] right now, I'm only using the info retrieved from launchpad [00:18] no hurry, just a suggestion that would make it even more helpful [00:18] it would be nice to mark in light green the valid candidates too [00:19] a lot of the regressions need retested but with &all-proposed=1 appended to the URL [00:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #54: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/54/ [00:26] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_powerdevil build #73: FIXED in 19 min: http://kci.pangea.pub/job/yakkety_unstable_powerdevil/73/ [00:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #182: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/182/ [00:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #120: NOW UNSTABLE in 28 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/120/ [00:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #93: NOW UNSTABLE in 29 min: http://kci.pangea.pub/job/zesty_unstable_kopete/93/ [00:27] maybe we could do something about that [00:27] but I'm afraid you are going to have to do that manually for this ongoing proposed migrations [00:27] * these [00:28] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #119: FIXED in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/119/ [00:29] both Rik and I are poking them by the looks of it [00:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #236: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/236/ [00:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #370: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_kstars/370/ [00:30] you are doing a great job [00:30] http://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/view/head:/retry-autopkgtest-regressions [00:30] that can do some automation ^^^ [00:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #101: STILL FAILING in 23 min: http://kci.pangea.pub/job/zesty_unstable_kstars/101/ [00:31] interesting [00:32] retry-autopkgtest-regressions --all-proposed | vipe | xargs -rn1 -P10 wget --load-cookies ~/.cache/autopkgtest.cookie -O- [00:33] can add an extra grep/filter in that before vipe to do some crude picking of tests [00:35] Wait, Adam Conrad is a DIRECT Kubuntu Member? [00:35] :O [00:35] but I guess a something to parse the yaml excuses output in a way more suited to our need would be better [00:37] looks like the only changes affecting the ISOs that we should look out for are related to ffmpeg [00:37] security update snuck in [00:38] https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1664403 [00:38] Launchpad bug 1664403 in ffmpeg (Ubuntu) " FFmpeg security fixes February 2017 (xenial)" [Medium,Fix released] [00:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_powerdevil build #67: FIXED in 29 min: http://kci.pangea.pub/job/xenial_unstable_powerdevil/67/ [00:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kexi build #63: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/yakkety_unstable_kexi/63/ [00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #181: NOW UNSTABLE in 40 min: http://kci.pangea.pub/job/xenial_unstable_kopete/181/ [00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #54: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kdb/54/ [00:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_oxygen build #83: FIXED in 31 min: http://kci.pangea.pub/job/yakkety_unstable_oxygen/83/ [00:40] exit [00:41] :wq [00:42] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #117: FIXED in 34 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/117/ [00:44] santa_ has the best method [00:44] VIM FTW!!! [00:45] you guys are fast three to go [00:50] santa_: looks likes some apps will need a 16.12.2 update done, or fixes cherry picked. e.g. filing rebuilds with FW 5.31 on the tests [00:51] such as for konsole, fix: https://cgit.kde.org/konsole.git/commit/?h=Applications/16.12&id=3a055ea19d5f458ccf06a33c697fbcda7a7f14df [00:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-cli-tools build #219: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kde-cli-tools/219/ [00:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_oxygen build #69: FIXED in 44 min: http://kci.pangea.pub/job/xenial_unstable_oxygen/69/ [00:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #55: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/55/ [00:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #49: STILL UNSTABLE in 43 min: http://kci.pangea.pub/job/xenial_unstable_trojita/49/ [00:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #35: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/yakkety_unstable_k3b/35/ [00:53] acheronuk: ah, indeed, I wanted to get trough apps today but the KA stuff took all my time today. I take note, and let's hope I have some time to help with that tomorrow [00:56] oh, and language pack updates to test in the apps staging ppa as well. no hope of testing all 50+ languages/localisations, but some tested to confirm the script did not produce utterly broken stuff would be good from whoever can test [00:57] Hi DarinMiller [00:57] Updating to the KCI Unstable PPA. [00:58] new 16.04.2 images fyi [00:58] ^ dovber_ [00:58] argh [00:58] ^ DarinMiller [00:58] hi darin , thx for help in my epic failed bug :) turns out some copy error somewhere happend [00:59] i gotta find something else to redeem myself now [00:59] :) [00:59] 1 am here, so night all :) [00:59] night [00:59] night rik [00:59] nite acheronuk [01:00] good night [01:00] santa_: nini [01:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #80: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/zesty_unstable_kdiagram/80/ [01:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #118: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_kalzium/118/ [01:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #180: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/180/ [01:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #189: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/189/ [01:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #59: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/59/ [01:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #51: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/zesty_unstable_kdb/51/ [01:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #95: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/95/ [01:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #202: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/202/ [01:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-cli-tools build #278: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kde-cli-tools/278/ [01:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #102: STILL FAILING in 16 min: http://kci.pangea.pub/job/zesty_unstable_kstars/102/ [01:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #237: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/237/ [01:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #28: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_k3b/28/ [01:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #183: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/183/ [01:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #92: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_cantor/92/ [01:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #106: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/106/ [01:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #371: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_kstars/371/ [01:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #158: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/158/ [01:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #209: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/209/ [01:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_spectacle build #91: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_spectacle/91/ [01:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #122: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/zesty_unstable_okular/122/ [01:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #238: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/238/ [01:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #211: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_okular/211/ [01:51] Hi everyone. [01:51] hey there [01:51] read log your'll see my thanks and conclusion on that er bug [01:51] hey sintre, I see your "possed" PC is finally behaving itself :) [01:52] yes and i feel like i've been looking for my sunglasses all day and all the while on my head lol [01:52] but hey alot learned [01:53] i appciate the time you spent as well as wxl [01:53] we took it to the end :) [01:53] so new install to test. Anyone now what changed with the new 16.04.2 spin? [01:53] Do we need to marathon test again? [01:53] DarinMiller: mostly stuff related to the machinery that builds images. so nothing to worry about [01:54] s/now/know/ [01:54] however [01:54] yes? [01:54] there is a security update of ffmpeg [01:54] so we should really double check thumbnailing in dolphin of a/v files and a/v players/viewers [01:55] bbl [01:56] 16.04.2 or 17.04 w/ staging apps 16.2.1? [01:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #112: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/zesty_unstable_marble/112/ [01:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #284: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/284/ [01:57] * DarinMiller assuming 16.04.2.... [01:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #299: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_cantor/299/ [01:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpimtextedit build #101: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/zesty_unstable_kpimtextedit/101/ [01:57] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [01:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #159: FIXED in 37 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/159/ [01:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #82: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/82/ [02:01] * DarinMiller assuming 16.04.2.... [02:01] * DarinMiller ctrl-z [02:09] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [02:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #194: FIXED in 50 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/194/ [02:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #85: STILL FAILING in 34 min: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/85/ [02:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #68: STILL UNSTABLE in 1 hr 54 min: http://kci.pangea.pub/job/yakkety_unstable_krita/68/ [02:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #231: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/231/ [03:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #92: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/92/ [03:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #93: STILL UNSTABLE in 2 hr 2 min: http://kci.pangea.pub/job/zesty_unstable_krita/93/ [03:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #86: STILL FAILING in 30 min: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/86/ [03:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #396: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_ki18n/396/ [03:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-sieve-editor build #63: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_pim-sieve-editor/63/ [03:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcodecs build #378: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kcodecs/378/ [03:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdbusaddons build #401: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kdbusaddons/401/ [03:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemviews build #369: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kitemviews/369/ [03:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfig build #411: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kconfig/411/ [03:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kguiaddons build #375: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kguiaddons/375/ [03:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_korganizer build #68: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_korganizer/68/ [03:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [03:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #110: FIXED in 13 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/110/ [03:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #369: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/369/ [04:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #74: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/74/ [04:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #193: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/193/ [04:36] * wxl stretches [04:37] here we go zsync here we go [04:39] I zync'd 16.04.2 amd64. What would you like test? [04:39] oh [04:39] there's a couple [04:39] manual and OEM [04:40] i'm going to get going on i386 [04:43] I will test OEM & manual on amd64 unless you think something is more pressing. Any idea what changed since the last tests? [04:44] yeah not much [04:44] https://lists.ubuntu.com/archives/kubuntu-devel/2017-February/011141.html [04:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #82: STILL UNSTABLE in 1 hr 7 min: http://kci.pangea.pub/job/xenial_unstable_calligra/82/ [04:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #103: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/zesty_unstable_kdbusaddons/103/ [05:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemviews build #97: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kitemviews/97/ [05:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #106: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/106/ [05:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #391: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/391/ [05:21] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwallet build #92: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_kwallet/92/ [05:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjobwidgets build #97: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_kjobwidgets/97/ [05:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kguiaddons build #190: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kguiaddons/190/ [05:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kjobwidgets build #248: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kjobwidgets/248/ [05:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcompletion build #173: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kcompletion/173/ [05:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdbusaddons build #265: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kdbusaddons/265/ [05:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcodecs build #262: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kcodecs/262/ [05:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcoreaddons build #201: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kcoreaddons/201/ [05:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ki18n build #261: STILL UNSTABLE in 8 min 48 sec: http://kci.pangea.pub/job/yakkety_unstable_ki18n/261/ [05:39] 16.04.2 ffmpeg testing: Does dragon player use ffmpeg? Dragon player does not play the video of mpg nor mp4 files (audio plays fine). [05:41] DarinMiller: not sure. that may be related to the fact that it's not a free codec. try an oggv or whatever theyr'e called [05:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwidgetsaddons build #267: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kwidgetsaddons/267/ [05:47] kubuntu-restricted extras installed. [05:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kconfigwidgets build #228: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kconfigwidgets/228/ [06:26] dragon player works after installing proprietary NVidia driver. Manual test completed. I will complete the amd64 OEM test in the morning (I have tomorrow off). [06:26] Heading to bed. gn [06:26] nite [06:26] thx for the help [06:27] anytime :) [06:27] i'm about there myself to be frank [08:49] Good morning. [10:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #36: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_k3b/36/ [10:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #29: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_k3b/29/ [10:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_k3b build #31: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/zesty_unstable_k3b/31/ [10:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_k3b build #32: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/zesty_unstable_k3b/32/ [12:17] any feedback from language packs in apps staging ppa for zesty [12:40] acheronuk: Is that a question? [12:59] Hiyas all [13:21] !info libindi-dev [13:21] libindi-dev (source: libindi): Instrument-Neutral Device Interface library -- development files. In component universe, is extra. Version 1.2.0-2~ubuntu4 (zesty), package size 280 kB, installed size 1330 kB [13:21] !info libindi-dev xenial [13:22] libindi-dev (source: libindi): Instrument-Neutral Device Interface library -- development files. In component universe, is extra. Version 1.1.0-1ubuntu1 (xenial), package size 231 kB, installed size 1119 kB [13:24] !info libindi-dev unstable [13:24] libindi-dev (source: libindi): Instrument-Neutral Device Interface library -- development files. In component main, is optional. Version 1.2.0-3 (unstable), package size 288 kB, installed size 1335 kB [13:25] hummm kstars needs version 1.3.1 [14:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #103: STILL FAILING in 5 min 32 sec: http://kci.pangea.pub/job/zesty_unstable_kstars/103/ [14:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #372: STILL FAILING in 5 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_kstars/372/ [14:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #238: STILL FAILING in 5 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_kstars/238/ [14:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #239: STILL FAILING in 3 min 43 sec: http://kci.pangea.pub/job/yakkety_unstable_kstars/239/ [14:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #104: STILL FAILING in 4 min 46 sec: http://kci.pangea.pub/job/zesty_unstable_kstars/104/ [14:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #373: STILL FAILING in 6 min 20 sec: http://kci.pangea.pub/job/xenial_unstable_kstars/373/ [14:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #240: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/240/ [14:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #374: STILL FAILING in 10 min: http://kci.pangea.pub/job/xenial_unstable_kstars/374/ [14:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #105: STILL FAILING in 13 min: http://kci.pangea.pub/job/zesty_unstable_kstars/105/ [14:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #375: STILL FAILING in 8 min 42 sec: http://kci.pangea.pub/job/xenial_unstable_kstars/375/ [14:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #241: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/241/ [14:56] Good . [14:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #106: STILL FAILING in 10 min: http://kci.pangea.pub/job/zesty_unstable_kstars/106/ [15:07] i.e. morning [15:29] tsimonq2: yes, it is a question [15:34] good afternoon everyone [15:34] clive there are dev versions of libindi 1.3.1 in a ppa somewhere, but not sure if they are suitable to grab or have build depends enough in zesty [15:34] clivejo: ^^ [15:59] hi santa_ [15:59] hi [16:00] * DarinMiller was late responding to santa_'s "good afternoon" greeting... [16:02] :9 [16:02] :) [16:05] hi santa_ :) [16:05] acheronuk: hi [16:05] I have managed to install many plasmas in qemu [16:06] I haven't used it before in this laptop and works better than ever [16:07] so I guess I will move away from virtualbox to do my testings [16:07] that's good. [16:07] that being said, I have a couple of things pending [16:07] one is testing the translations you mentioned [16:07] the other one is catching up with apps status [16:07] Vbox works here most of the time Ok, but mileage does vary with that [16:08] acheronuk: so ... status report about apps? [16:09] we have the "complete" thing in staging/proposed don't we? [16:09] meaning "complete" all the source packages uploaded [16:09] we have all packages uploaded there, yes [16:10] building is obviously another issue. though most apart from PIM are ok [16:10] and ... what do we have in the archive? [16:10] 16.04 + 16.12 or just 16.04? [16:11] saying that, what I pointed out past night about build failures would show up now if we did a rebuild of 16.12.1 against new FW [16:11] santa_: in archive it is 16.12.1 for non-pim. and 16.04.3 for PIM [16:11] how did you skipped the kdepim packages ? [16:12] I didn't upload them [16:12] yes, but how did you "separate" ? [16:13] how did you build the list? [16:13] manually? something else? [16:14] santa_: I did a dummy run with kdesrcbuild to identify via it's metadata what is part of the PIM stack and what is not, and then removed the strictly PIM parts from my clone [16:14] seems legit [16:15] more legit than trusting lists on random wiki's etc I hoped [16:16] acheronuk: but at the same time all the kubuntu_zesty_archive branches have the 16.12 versions for evething (including pim), right? [16:17] yep. :/ [16:17] no prob, we can work with that perfectly. slighly inconvenient but nothing more [16:17] ok, more questions [16:18] reasons to hold it? other than the incoming freeze? [16:19] hold what? PIM is particular, or 16.12.2 in general which is out but not staged? [16:19] I mean to keep pim @ 16.04 for a while [16:21] PIM. getting so many split new sources in and approved. Just getting them uploaded is tricky. [16:21] gpgme issue you know of, but we could choose not to care about anything but amd64 amd i386 [16:22] I assume if gpgme never builds on those failing architectures, the AA will let it migrate anyway in the end? [16:22] I don't know [16:22] how affects gpgme being stuck in -proposed ? [16:23] I meant [16:23] how affects pim? [16:23] plus there are some symbol issues that substituting in new gpgme rather than KDE's old gpgmepp seems to throw up. [16:25] ok [16:25] thanks for your time [16:26] so I guess I'm going to retry at least a thing against gpgme [16:26] I was somewhat concerned that uploading may result in some parts of PIM getting build OK and going through, but may end up breakling the 16.04.3 we have if we don't get the lot through [16:26] yep, britney doesn't care about the concept of package suite [16:30] kstars ( 3 - DMSTest (Failed) 4 - TestCachingDms (Failed) ) [16:31] failing on i386 for some reason [16:31] clivejo: https://bugs.kde.org/show_bug.cgi?id=376439 [16:31] KDE bug 376439 in general "Release 16.12.x on i386 tests TestDMS and TestCachingDms fails - other architectures all pass" [Normal,Unconfirmed] [16:32] can the test be disabled for i386 then? [16:33] i386 is seemly not getting the match on those angles it wants. maybe a precision issue [16:34] curious, as armhf is 32bit too [16:34] was meaning to dig into it to see what the mismatch is, but need to work out how to get Qtest or something else to output the actual values [16:35] looks like libindi isnt actually optional in kstars [16:36] clivejo: we could. and was something I was think of as a stopgap. though i386 is used enough that the failure in that calculation is 'concerning' [16:44] can we put #ifndef in there to exclude that test on i386? or I suppose just exit the test with a pass no matter what on i386, if we are just doing a stopgap measure pending an upstream fix. [16:48] if you go for the stop in gap i sugguest you to just comment out the test in question and document it here https://phabricator.kde.org/w/kubuntu/autopkgtests/working_notes/ [16:48] but let me have a look first, I'm preparing a container to check that... [16:49] anyway comparisons with floating point numbers.... [16:49] SRLSY [16:57] santa_: yes, doing an exact comparison on those is asking for trouble. I was slightly bemused that was even done! [17:04] acheronuk, clivejo: try this: http://doc.qt.io/qt-5/qtglobal.html#qFuzzyCompare [17:05] only on the failing lines [17:06] because if you I want to fix it "properly" you will need to rewrite the whole file, which is full of plain QVERIFY's [17:09] seems the rest of it works more by luck than intent! [17:10] takes me back to days of doing finite element stuff in fortran! urgh [17:11] fortran [17:11] dat language [17:11] what were you studying? [17:11] santa_: Attempting to understand the process: so you update the file and submit an mp against kstars? Or would that only be fixed for kubuntu kstars v 16.12.x? [17:12] santa_: physics [17:15] DarinMiller: well, first of all, let's confirm that the solution is good, if it is, I would send a patch to the kde reviewboard, I could commit myself because in kde every kde developer has commit access to everything, but at the same time we are all adults so if we have something to fix in software where we don't maintain we use to check on someone who works on the specific code on a regular basis, since that person will have more clue [17:15] about what's right and wrong [17:15] sorry for the lack of commas XD [17:16] makes sense, thanks [17:21] DarinMiller: I submitted a fix for ksirk via phabricator differential the other day. just a trivial one, to stop FTBFS on some arches we have, but was nice to see that go in :) [17:24] phabricator diff? ksirk has a phabriactor thread(?) for issue reporting? [17:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #376: STILL FAILING in 5 min 34 sec: http://kci.pangea.pub/job/xenial_unstable_kstars/376/ [17:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #242: STILL FAILING in 5 min 35 sec: http://kci.pangea.pub/job/yakkety_unstable_kstars/242/ [17:27] DarinMiller: https://phabricator.kde.org/source/ksirk/repository/master/ [17:27] all/most KDE projects should have one [17:29] https://phabricator.kde.org/R413:8fdc83b20270c5c307c5edda7c21a351bdf44c97 [17:29] Riks patch [17:30] How long have the phab site been in place? Did these used to be on Trello and migrated when the kubuntu stuff migrated? [17:30] They been switching for a while now [17:30] DarinMiller: they used to be in the reviewboard [17:30] the phab is a new thing [17:30] which is why we wanted to move our stuff there [17:31] https://git.reviewboard.kde.org/r/ [17:31] clivejo: I think the wiki is very cool to drop working notes [17:32] better than just the trello [17:32] because many times I'm doing tasks which are part of a bigger plot [17:32] so it's useful to have both [17:32] I do miss some features of trello, but with it being bought out, I dont like my details being sold on [17:32] agreed, I am very impressed with phabricator. [17:33] and its nice to work closer with upstream [17:35] hehe. my tiny patch. trivial, but good for putting my toe in the water so to speak :) === clivejo changed the topic of #kubuntu-devel to: Kubuntu - Friendly computing | Zesty Zapus Beta 1 on the 23rd February | Support in #kubuntu | Plasma 5.8.5 X/Y Backports, Z Archive & Staging 5.9.2 | Apps 16.04.3 X/Y Backports, 16.12.1 (excluding PIM) - Z Archive | FW 5.28 X/Y Backports, Z Archive, 5.31 Z Staging | Trello: https://is.gd/dGbmxV | QA links: https://is.gd/p7kblH | Package Docs (WIP): https://phabricator.kde.org/w/kubuntu [17:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #377: STILL FAILING in 4 min 34 sec: http://kci.pangea.pub/job/xenial_unstable_kstars/377/ [17:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #243: STILL FAILING in 4 min 36 sec: http://kci.pangea.pub/job/yakkety_unstable_kstars/243/ [17:36] stupid publisher! [17:38] acheronuk: I know exactly what you mean. The path from "obsrever" to "contributor" can be much longer and more complicalted than initial expectations. [17:39] DarinMiller: sometimes. sometimes scarily quick. [17:39] DarinMiller: this last time last year I was more or less lurking, and doing some occasional testing of the isos and staging ppas as I was impatient for new plasma [17:40] acheronuk: And you've done an awesome job at it too! Thanks! [17:42] yeah, my first time here was because I run "sudo dolphin" and broke plasma :( [17:42] * acheronuk gasps in horror! [17:42] I know! Dont tell anyone! [17:43] uhoh [17:43] especially Martin [17:46] clivejo: language packs before feature freeze? what do you reckon? assuming santa_ test with his does not reveal horrible breakage? [17:46] who has tested them? [17:47] me with en_GB. maybe yofel? hopefully santa... [17:47] soee_: can you test them? [17:47] not yet [17:47] I didn't [17:47] but I will try to do so [17:47] en_GB is too close to en_US to see issues! [17:48] my desktop now resides below the panel on zesty after some upgrades ..wish I had paid attn during:/ [17:49] teatime [17:51] not desperate to uplaod them, as a bit of a gimme for an FFE if not. just thinking of saving paperwork if enough testing has been achieved. [17:52] yofel: can you foresee any issues with uploading them now before FFE and fix any problems later? [17:52] before FF [18:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #107: NOW UNSTABLE in 48 min: http://kci.pangea.pub/job/zesty_unstable_kstars/107/ [18:11] https://launchpad.net/~panfaust/+archive/ubuntu/gpgme/+sourcepub/7491099/+listing-archive-extra [18:11] https://www.youtube.com/watch?v=04854XqcfCY [18:16] clivejo, acheronuk: indeed changing the thing to fuzzy compare fixes the thing, do you want me to push it to git [18:16] the patch I mean [18:19] santa_: so you set flags the other way, without DEB_BUILD_MAINT_OPTIONS [18:20] santa_: our git? I suppose. lets fix it for now there, as tests on other stuff fail on that kstars one [18:22] acheronuk: [gpgme] as an experiment, I have just pasted all the variables listed by "dpkg-buildflags" in debian sid. with iron balls [18:22] now the idea is nitpicking what it is [18:22] acheronuk: [kstars] ok, going to commit [18:31] acheronuk: done [18:31] -kubuntu-ci:#kubuntu-devel- Project merger_kstars build #760: FAILURE in 10 sec: http://kci.pangea.pub/job/merger_kstars/760/ [18:38] -kubuntu-ci:#kubuntu-devel- Project merger_kstars build #761: STILL FAILING in 7.3 sec: http://kci.pangea.pub/job/merger_kstars/761/ [18:38] -kubuntu-ci:#kubuntu-devel- Project merger_kstars build #762: STILL FAILING in 7.1 sec: http://kci.pangea.pub/job/merger_kstars/762/ [18:51] santa_: uploaded, and sounds like you have green light for proper patch as well :) [18:51] bah [18:51] how does OEM fail on one arch but not the other? [18:52] acheronuk: thank you [18:52] marco-parillo: what hypervisor did you use for that OEM test? [18:53] Virtual Box Win 7 host [18:54] could you attach some info on that about the virtualbox version and the hardware specs of the host? [18:54] If it runs for you on real hw, I would mark it ready, I would assume OEM on a VM guest is nonsensical anyway. I just noticed anybody was trying it. [18:55] Version 5.0.32 r112930 [18:55] marco-parillo: please add it to the comments on the tracker [19:10] Feature Freeze at 21 utc [19:10] So 2 hours [19:20] tsimonq2: thanks. what was expected I think from the wiki [19:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konsole build #77: FAILURE in 47 sec: http://kci.pangea.pub/job/zesty_unstable_konsole/77/ [19:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konsole build #313: FAILURE in 40 sec: http://kci.pangea.pub/job/xenial_unstable_konsole/313/ [19:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konsole build #227: FAILURE in 1 min 8 sec: http://kci.pangea.pub/job/yakkety_unstable_konsole/227/ [19:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konsole build #78: STILL FAILING in 47 sec: http://kci.pangea.pub/job/zesty_unstable_konsole/78/ [19:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konsole build #228: STILL FAILING in 48 sec: http://kci.pangea.pub/job/yakkety_unstable_konsole/228/ [19:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konsole build #314: STILL FAILING in 1 min 11 sec: http://kci.pangea.pub/job/xenial_unstable_konsole/314/ [19:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #93: FAILURE in 39 sec: http://kci.pangea.pub/job/zesty_unstable_cantor/93/ [19:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #190: FAILURE in 55 sec: http://kci.pangea.pub/job/yakkety_unstable_cantor/190/ [19:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #300: FAILURE in 32 sec: http://kci.pangea.pub/job/xenial_unstable_cantor/300/ [19:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #94: STILL FAILING in 35 sec: http://kci.pangea.pub/job/zesty_unstable_cantor/94/ [19:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #301: STILL FAILING in 30 sec: http://kci.pangea.pub/job/xenial_unstable_cantor/301/ [19:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #191: STILL FAILING in 50 sec: http://kci.pangea.pub/job/yakkety_unstable_cantor/191/ [20:04] ~ 55 minutes [20:08] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [20:08] -kubuntu-ci:#kubuntu-devel- Project merger_kstars build #763: FIXED in 12 sec: http://kci.pangea.pub/job/merger_kstars/763/ [20:28] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [20:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konsole build #315: FIXED in 13 min: http://kci.pangea.pub/job/xenial_unstable_konsole/315/ [20:28] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [20:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konsole build #79: FIXED in 14 min: http://kci.pangea.pub/job/zesty_unstable_konsole/79/ [20:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [20:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konsole build #229: FIXED in 23 min: http://kci.pangea.pub/job/yakkety_unstable_konsole/229/ [20:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #244: NOW UNSTABLE in 30 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/244/ [20:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #108: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/zesty_unstable_kstars/108/ [20:39] wxl: I assume you noticed the 16.04 amd64 OEM completed with no major issues. [20:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #302: NOW UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_cantor/302/ [20:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #378: NOW UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kstars/378/ [20:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #95: NOW UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_cantor/95/ [20:39] DarinMiller: yeah did. makes me wonder. you use vbox right? [20:39] also, I looked into updating the test case verbage and noticed it was shared across distros. [20:39] yeah that's what i said before [20:39] wxl: bare metal [20:39] we need to make a kubuntu-specific one [20:39] ah [20:40] so it may be a vbox-specific. can you run a vbox test? [20:40] any vm or vbox specifically? [20:40] vbox please [20:41] one vbox oem64 16.04.2 test coming shortly.... [20:41] danke [20:41] i'm working on i386 [20:51] * DarinMiller thinks using a virutal box for relase testing is cheating, but it sure is fast with newer hw :) [20:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #192: NOW UNSTABLE in 34 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/192/ [20:53] yeah well [20:53] it's one way we can ensure there's not obvious roadblocks [20:53] and besides, there's no way we can test EVERY hardware [20:54] I have seen (Linux) VMs that boot rather significantly faster than the host system. [20:55] yes, minimal BIOS POST [21:00] CLANG! [21:00] ^^^ feature freeze portcullis of doom [21:00] CLANG [21:00] CCCLLLAAANNNGGG [21:04] GCC! [21:04] LLVM! [21:04] haha [21:05] compilers. could be worse. it was animal noises the other night! [21:05] hows testing going [21:05] Hahahahahaha yeah +1 [21:10] @sintre, So so :P [21:13] valorie: how are we doing on release notes for 16.04.2? [21:13] * DarinMiller was a little rusty using vm... [21:13] wxl, pretty much done except for bug update I think? [21:13] same with the news report [21:13] ok good [21:13] just needs a couple of links [21:14] anybody use fish:// in dolphin? Very handy for copying files without setting up full network sharing on new boxes... [21:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #51: UNSTABLE in 22 min: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/51/ [21:14] which is good, because I need to go out and buy a new phone today [21:14] my battery is lasting 4 hours [21:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #112: UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/112/ [21:14] :( [21:14] valorie: ...you can't just get a new battery [21:14] bummer [21:14] ? [21:14] and I leave for india in like 3 weeks [21:14] valorie: DarinMiller and i are finishing the laast tests and we should be good to go [21:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #111: UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/111/ [21:15] genii: it's an HTC one [21:15] 3.5 years old [21:15] I don't think it's worth it [21:15] wxl: videos play in vm just fine amd64 OEM and network connects as it should. Thus, vm's hide issues!!! [21:15] valorie: I just got a battery for my Nexus 4, was like $12 [21:15] DarinMiller: yes, dear. :) [21:16] wxl: amd oem 64 ran fine in vm. Shall I test i386 OEM? [21:16] i'm gonna mark amd64 ready [21:16] DarinMiller: i'm running it albeit slowly [21:17] valorie: please add the following to the known issues of the 16.04.2 release notes: - Dragon player will not play .mp3/mp4 video with default Nouveau driver (even with kubuntu-restricted-extras installed). VLC plays fine with Nouveau driver. (bug filed: 1665385) [21:18] or something to that effect ^ [21:18] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Xenial 16.04.2] has been marked as ready [21:22] * DarinMiller still is blown away by the versatility VM's [21:22] genii: I'll look then [21:25] acheronuk: have you got that retry script to work? [21:28] DarinMiller: fixed [21:28] the images are still broken on that fricken-fracken wiki though [21:37] clivejo: I haven't tried since the other day. what issue do you have with it? [21:37] cant get it to work [21:38] clivejo: what goes wrong? [21:39] * clivejo shrugs [21:40] valorie: thanks :) [21:42] clivejo: well, it is a bit of a faff. hopefully we can build something better [21:46] can you run it? [21:46] clivejo: yes [21:47] when you run it last? [21:48] clivejo: yesterday probably. why? [21:48] can you try now? [21:48] try now on what exactly? [21:54] hi snowhog [21:57] hey clivejo [22:00] Found the IRC link to freenode's IRC on http://kubuntu.org/community (#kubuntu). It's nice to be able to access IRC when I'm on my iMac without having to fire up one of my Linux VMs, and to be able to log in here using my registered username. [22:01] i normally use the wiki client , just out of habbit i guess [22:02] then again i don't have 30 different rooms to manage , if that was the case i'd probally be better off with a regular client [22:03] i'm probably around 60 [22:03] wxl > now thats alot of logs to read [22:03] :) [22:04] i have them prioritized into windows [22:04] there's some i don't really both with the logs on [22:09] nice to see snowhog here [22:11] Hey valorie! Nice to "see" you here too. [22:12] clivejo: just tried it a bit and I think it's working. gave me a lot of aoutput and my name is now on the page of running and queued tests [22:12] hard to say for sure as the system has such lag [22:12] Hi Snowhog :) === keithzg_ is now known as keithzg [22:13] Hey acheronuk. [22:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kajongg build #125: STILL FAILING in 4 min 42 sec: http://kci.pangea.pub/job/xenial_unstable_kajongg/125/ [22:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kajongg build #153: STILL FAILING in 4 min 46 sec: http://kci.pangea.pub/job/yakkety_unstable_kajongg/153/ [22:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kajongg build #115: STILL FAILING in 6 min 15 sec: http://kci.pangea.pub/job/zesty_unstable_kajongg/115/ [22:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kajongg build #126: STILL FAILING in 3 min 41 sec: http://kci.pangea.pub/job/xenial_unstable_kajongg/126/ [22:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kajongg build #154: STILL FAILING in 5 min 7 sec: http://kci.pangea.pub/job/yakkety_unstable_kajongg/154/ [22:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kajongg build #116: STILL FAILING in 5 min 47 sec: http://kci.pangea.pub/job/zesty_unstable_kajongg/116/ [22:28] DarinMiller: you still around? [22:29] anyone around that can boot run the OEM test on i386 real quick? [22:29] i just did it and i actually get the same results on mparillo. of course that's with vbox as well. [22:31] But, is that really a relevant test? I assume the standard use case for OEMs would be real HW (and probably not i386). [22:31] all tests are relevant [22:31] it seems this is the more appropriat ebug https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1638473 [22:31] Launchpad bug 1638473 in oem-config (Ubuntu) "Blank screen after running oem-config" [Undecided,New] [22:32] wxl: still here [22:32] DarinMiller: can you do i386 OEM? i'm getting a fail in virtualbox, consistent with mparillo [22:32] bare metal, yes? [22:33] DarinMiller: yeah for now, that's all i care about. if it doesn't work in a vm oh well. might be nice to try it in something other than virtualbox, tho [22:33] !forums [22:33] The Ubuntu forums can be found at https://ubuntuforums.org. Kubuntu Forums are found at https://www.kubuntuforums.net. There is also a channel on freenode IRC #ubuntuforums [22:33] interesting tho that the bug i mentioned is amd64 and real hardware [22:34] The bug report you found was much newer than the one I found (https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nv/+bug/309482) [22:34] Launchpad bug 309482 in X.Org X server "jaunty: Kubuntu OEM enduser setup fails with black screen (nv driver fails)" [Medium,Fix released] [22:34] Plus, mine is marked Fix released. [22:35] yeah the one you found is ancient and possibly not relevant [22:39] bah well i'm out of good ideas [22:46] Have any bad ones? [23:03] acheronuk, clivejo: Had a random thought, we could probably drastically reduce our image sizes and install sizes etc. if we finally stopped including KDE 4 [23:03] How far are we from switching to KDE 5 only? [23:03] and reduce the number of packages we have to support.. [23:03] wxl: That too ;) [23:04] wxl: You like that idea? :) [23:04] if it's feasible sure [23:04] wxl: Also maybe you should upgrade your work systems to a more recent version :P [23:04] * tsimonq2 runs [23:04] if we can't make ZZ at least making it into the next LTS would be nice [23:05] wxl: STOP IT :P s/ZZ/Zesty Zapus/g [23:05] ZZ [23:05] * wxl does NOT run [23:05] Zesty Zapus [23:05] Zesty Zapus [23:05] Zesty Zapus [23:05] so i can't say USA either, huh? [23:05] wxl: Well that's generally accepted *AHEM* [23:05] i'm sorry but i don't subscribe to your anti-acronym school of thought [23:06] so ZZ it is [23:06] ok i didn't want to comment on somethin , especially after my failed lil bug , but this is kind of a security issue , [23:06] wxl: You're lucky you already told me why you don't capitalize "I" :P [23:06] the important thing in language is to communicate a message [23:06] probally not best time but while its fresh , trying to trouble shoot that lil issue , copy errored iso and then the other ones there is a problem with the wifi network program [23:06] if the message is adequately communicated, the medium doesn't matter, and that includes syntax [23:07] i have a 15 character keypass [23:07] wxl: Bah [23:07] it keeps changing the netwrok but keep the password [23:07] i live around a bunch of people with 15 different networks [23:07] my system picks up [23:08] so when i start to type password to connect , it won't lock and change for somereason to other ones [23:08] so basicly i accidently sent my router pass to other wifi netwrosk [23:08] now the old folks around here problablly don't log into thier routers and check [23:08] i have never had wifi connecting to endpoints i didn't explicitly ask to connect to [23:08] but this could hurt somebody [23:09] it take the password i'm typing [23:09] and changes the network somehow [23:09]