[00:15] -kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-thumbnailers build #83: FAILURE in 40 sec: http://kci.pangea.pub/job/merger_kdesdk-thumbnailers/83/
[00:16] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #592: FAILURE in 18 sec: http://kci.pangea.pub/job/merger_kdiamond/592/
[00:37] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #679: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/mgmt_merger/679/
[00:37] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #660: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/mgmt_progenitor/660/
[00:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #75: STILL FAILING in 4 min 36 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/75/
[00:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #92: STILL FAILING in 8 min 33 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/92/
[00:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kapptemplate build #76: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kapptemplate/76/
[00:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #273: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/273/
[00:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #156: STILL FAILING in 11 min: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/156/
[01:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #157: STILL FAILING in 6 min 9 sec: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/157/
[01:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #91: STILL FAILING in 1 hr 13 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/91/
[01:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kactivitymanagerd build #110: STILL FAILING in 1 hr 15 min: http://kci.pangea.pub/job/yakkety_unstable_kactivitymanagerd/110/
[01:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #68: STILL UNSTABLE in 1 hr 15 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/68/
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #67: STILL UNSTABLE in 1 hr 5 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/67/
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #169: STILL FAILING in 1 hr 13 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/169/
[01:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcddb build #50: FIXED in 53 min: http://kci.pangea.pub/job/xenial_unstable_libkcddb/50/
[01:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #175: STILL FAILING in 1 hr 13 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/175/
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop-pg-qt build #32: STILL UNSTABLE in 1 hr 14 min: http://kci.pangea.pub/job/xenial_unstable_kdevelop-pg-qt/32/
[01:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcddb build #58: FIXED in 53 min: http://kci.pangea.pub/job/yakkety_unstable_libkcddb/58/
[01:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #47: STILL UNSTABLE in 1 hr 12 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/47/
[01:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #28: STILL UNSTABLE in 1 hr 15 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/28/
[01:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #71: STILL UNSTABLE in 1 hr 6 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/71/
[01:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #107: STILL FAILING in 1 hr 16 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/107/
[01:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #70: STILL UNSTABLE in 1 hr 6 min: http://kci.pangea.pub/job/xenial_unstable_kopete/70/
[01:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #81: STILL UNSTABLE in 1 hr 6 min: http://kci.pangea.pub/job/yakkety_unstable_okular/81/
[01:58] <santa_> Project yakkety_unstable_libkcddb build #58: FIXED
[01:58] <santa_> https://www.youtube.com/watch?v=04854XqcfCY
[01:59] <tsimonq2> :DDDDDDDDDDD
[01:59] <tsimonq2> valorie: GREEN
[02:00] <santa_> but they are still things to do in that package
[02:00] <santa_> tsimonq2: btw I made a small script in ka to create orig tarballs from git
[02:01] <santa_> because I presume you are sometimes testing with sbuild things before pushing to kubuntu_unstable
[02:01] <santa_> (like me, so I wrote the script to build the source and feed it into sbuild)
[02:20] <tsimonq2> ooh
[02:20] <tsimonq2> :D
[02:20] <tsimonq2> thanks santa_ :D
[02:29] <santa_> tsimonq2: it's get-kci-tarball you must execute it inside the packaging git repository, you will get it in "../build-area", and then you can execute gbp-ppa, move to the build area and sbuild <whatever> file.dsc
[02:30] <santa_> maybe there is a better wowrkflow to do this, but it's the first one I figured out today
[02:46] <tsimonq2> awesome :)
[02:46] <tsimonq2> santa_: now the real question is, did you check it twice?
[02:46]  * tsimonq2 runs
[02:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #274: STILL FAILING in 9 min 9 sec: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/274/
[03:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #176: STILL FAILING in 1 hr 28 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/176/
[03:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #170: STILL FAILING in 1 hr 29 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/170/
[03:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #140: UNSTABLE in 1 hr 28 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/140/
[03:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #142: STILL UNSTABLE in 1 hr 28 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/142/
[03:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kidletime build #265: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/xenial_unstable_kidletime/265/
[04:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #264: UNSTABLE in 46 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/264/
[04:30] <tsimonq2> acheronuk, clivejo, santa_: looking into some of the regressions on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html , some of them are appdata -> metainfo and will most likely be fixed when we upload 16.04.3
[04:30] <tsimonq2> acheronuk, clivejo, santa_: do we fix them now or do we have them overridden?
[05:00] <tsimonq2> night o/
[05:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kapptemplate build #203: STILL FAILING in 5 min 18 sec: http://kci.pangea.pub/job/xenial_unstable_kapptemplate/203/
[05:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kapptemplate build #204: STILL FAILING in 5 min 16 sec: http://kci.pangea.pub/job/xenial_unstable_kapptemplate/204/
[06:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kactivitymanagerd build #110: STILL FAILING in 26 min: http://kci.pangea.pub/job/xenial_unstable_kactivitymanagerd/110/
[06:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kapptemplate build #77: STILL FAILING in 6 min 14 sec: http://kci.pangea.pub/job/yakkety_unstable_kapptemplate/77/
[07:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kactivitymanagerd build #111: STILL FAILING in 44 min: http://kci.pangea.pub/job/xenial_unstable_kactivitymanagerd/111/
[07:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kactivitymanagerd build #111: STILL FAILING in 51 min: http://kci.pangea.pub/job/yakkety_unstable_kactivitymanagerd/111/
[07:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #88: STILL FAILING in 51 min: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/88/
[07:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #75: STILL UNSTABLE in 50 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/75/
[07:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #87: STILL FAILING in 2 min 15 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/87/
[07:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #88: STILL FAILING in 38 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/88/
[07:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #245: STILL UNSTABLE in 1 hr 1 min: http://kci.pangea.pub/job/xenial_unstable_kstars/245/
[07:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #175: STILL FAILING in 34 min: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/175/
[07:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #93: STILL FAILING in 49 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/93/
[07:56] <lordievader> Good morning.
[08:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #92: STILL FAILING in 1 hr 7 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/92/
[08:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #196: STILL UNSTABLE in 1 hr 7 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/196/
[08:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #89: STILL FAILING in 1 hr 4 min: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/89/
[08:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #190: STILL FAILING in 1 hr 8 min: http://kci.pangea.pub/job/xenial_unstable_cantor/190/
[08:18] <acheronuk> https://bugs.launchpad.net/ubuntu/+source/kscd/+bug/1600047
[08:19] <acheronuk> ^^^^ needs sorting even if we don't get apps in
[08:29] <acheronuk> tsimonq2: yes, I saw that. I did wonder if we could just update say a few key apps. konsole, ark, dolphin etc. without breaking other parts of kde apps
[08:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #176: STILL FAILING in 1 hr 0 min: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/176/
[08:56] <acheronuk> tsimonq2: http://paste.ubuntu.com/23250241/
[09:09] <acheronuk> from ubuntu devel
[09:10] <acheronuk> [10:00] <Mirv> acheronuk: it totally depends on how grumpy they are :) but yes, possible.
[09:10] <acheronuk> [10:00] * marcusto_ (~marcustom@169-0-166-142.ip.afrihost.co.za) has joined
[09:10] <acheronuk> [10:03] <Mirv> acheronuk: the more Kubuntu people can evaluate the situation yourselves the better - I mean, the autopkgtests are being run anyway and take days, the results should mean something. if it's mostly green, the red ones could be quickly glanced through to see if anything scary. if it's mostly red, then maybe there's something really problematic.
[09:10] <acheronuk> [10:07] <acheronuk> Mirv: ok. not sure any of us who are available have a great deal of a clue how to decide what is serious on those or not, but I guess if a couple of days or so we can put a case together as best we can
[09:10] <acheronuk> asking if the release team could be persuaded to do the same again ^^^
[09:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #24: STILL UNSTABLE in 1 hr 1 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/24/
[09:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #170: STILL UNSTABLE in 1 hr 3 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/170/
[09:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #213: STILL FAILING in 1 hr 2 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/213/
[09:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #191: STILL FAILING in 58 min: http://kci.pangea.pub/job/xenial_unstable_cantor/191/
[09:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #123: STILL UNSTABLE in 1 hr 3 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/123/
[09:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #108: STILL FAILING in 32 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/108/
[09:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #49: STILL FAILING in 6 min 14 sec: http://kci.pangea.pub/job/xenial_unstable_discover/49/
[09:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #50: STILL FAILING in 5 min 57 sec: http://kci.pangea.pub/job/xenial_unstable_discover/50/
[09:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #124: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/124/
[10:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #99: STILL FAILING in 1 hr 2 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/99/
[10:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #103: STILL FAILING in 1 hr 2 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/103/
[10:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #214: STILL FAILING in 58 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/214/
[10:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #241: STILL UNSTABLE in 1 hr 4 min: http://kci.pangea.pub/job/xenial_unstable_kwin/241/
[10:27] <ghostcube> https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet  just for the fun 
[10:28] <clivejo> acheronuk: you about?
[10:28] <acheronuk> clivejo: for a short while
[10:28] <clivejo> still got Neon installed?
[10:28] <acheronuk> on my laptop and in a VM
[10:28] <clivejo> can  you apt install kdevelop please
[10:31] <acheronuk> clivejo: yes. 
[10:32] <acheronuk> http://paste.ubuntu.com/23250578/
[10:33] <clivejo> does it install kdevelop-data
[10:34] <acheronuk> yes, no errors
[10:35] <clivejo> must be our outdated apps :(
[10:36] <acheronuk> I will uninstall it, update Neon, then try again
[10:37] <clivejo> its fine
[10:37] <clivejo> know what the issue is
[10:37] <clivejo> http://packages.ubuntu.com/yakkety/kapptemplate contains the same file as kdevelop-data
[10:37] <acheronuk> I still have kdevelop from blazes ppa updated to latest that seems ok
[10:38] <acheronuk> oh. right
[10:38] <clivejo> how to deal with that is another question :(
[10:38] <acheronuk> what file?
[10:38] <clivejo> trying to overwrite '/usr/share/kdevappwizard/templates/cmake_qt5guiapp.tar.bz2', which is also in package kapptemplate 4:15.12.3-0ubuntu1
[10:39] <acheronuk> ouch!
[10:39] <clivejo> indeed
[10:40] <acheronuk> presumably new apps don't clash...
[10:40] <clivejo> nope
[10:40] <clivejo> https://launchpadlibrarian.net/285157426/buildlog_ubuntu-yakkety-amd64.kapptemplate_4%3A16.04.3-0ubuntu1~ubuntu16.10~ppa60_BUILDING.txt.gz
[10:40] <clivejo> not installed here
[10:41] <acheronuk> hmm.....
[10:41] <acheronuk> bbl, I'm afraid
[10:58]  * clivejo is reading shadeslayer's dev meeting and runs away
[10:59] <clivejo> ar archive containing a text file, control.tar and data.tar
[11:01] <clivejo> :/
[11:06] <acheronuk> clivejo: yep. that is what is actually inside the deb if you unpack it with an unpack app/util
[11:07] <clivejo> cant say Ive ever felt the need to do that!
[11:08] <acheronuk> I occasionally do that to to have a look at what was built
[11:08] <clivejo> acheronuk you should do the meeting on my behalf!
[11:09] <acheronuk> not really. I think we would just struggle in different areas.
[11:09] <acheronuk> :P
[11:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #275: STILL FAILING in 5 min 25 sec: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/275/
[11:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #158: STILL FAILING in 5 min 26 sec: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/158/
[11:32] <tsimonq2> clivejo: link to shadeslayer's dev meeting? :O
[11:32] <tsimonq2> acheronuk: ack, let's do what we can ;)
[11:33] <clivejo> https://irclogs.ubuntu.com/2012/03/16/%23kubuntu-devel.html
[11:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #276: STILL FAILING in 4 min 5 sec: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/276/
[11:34] <tsimonq2> ooh, fun bus reading
[11:34] <tsimonq2> :P
[11:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #159: STILL FAILING in 6 min 50 sec: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/159/
[11:39] <shadeslayer> oh noes :(
[11:39] <shadeslayer> I was so young and impressionable back then :
[11:39] <shadeslayer> :P
[11:39] <clivejo> back in the days this was fun!
 And it'll be more funer again soon clivejo
 :P
[11:43] <clivejo> I hope so!
 I've been working with Debian to see if we can get all of the up to date everything in Debian so when Z development cycle starts we just have to merge
 It'll be a lot more fun
 Because hopefully we can do all the work upstream until we can't sync again
[11:53] <acheronuk> debian merges in git for 400+ packages. whoo!
 I was thinking about that
[11:54] <acheronuk> shadeslayer: I have links to yofels and fabo's -dev meetings as well I think... :P
 We should set up KCI to merge from the archive to kubuntu_yakkety_archive during *_merge
 Theoretically it's a simple job
 If we have working code for that, then all we would have to do is fix merge failures
 Which is typically my job anyways :P
 acheronuk thoughts? ^
[11:58] <acheronuk> yes, I was thinking what to have for dinner
[12:00] <clivejo> ditto
 Come on guys, give me SOMETHING! :P
[12:02] <clivejo> @tsimonq2 as said before, Im not thinking about ZZ until it gets a name
[12:02] <clivejo> we ahve more than enough problems to deal with in XX and YY
 :/
 valorie: how about you? :P
[12:05] <acheronuk> spicy chicken stir-fry I think \o/ :)
 santa_?
[12:09] <shadeslayer> mmmmhh spicy
 (Photo, 720x1280) https://irc-attachments.kde.org/meeC6GCN/file_629.jpg
 Ooooh
[12:14] <acheronuk> shadeslayer: spicy :) ^^^
[12:16] <shadeslayer> :D
[12:16] <shadeslayer> you don't want to mess with me on spicy though :P
 :D
 Oh? High tolerance or low shadeslayer?
[12:16] <shadeslayer> unless you want me pulling out the 2 whole boxes of chillies I have in my fridge
[12:17] <shadeslayer> tsimonq2: very high
 Lol
[12:17] <shadeslayer> I actually found really good ones in the supermarket finally :D
[12:17]  * acheronuk thinks it's dinner at shadeslayer's for all the team at some point
[12:17] <shadeslayer> sure :P
[12:18] <shadeslayer> when are you in Barcelona ? ;)
[12:19] <acheronuk> maybe you should cook at akademy or some other conference/workshop then
 shadeslayer: what do YOU think about my plan?
 Lol
[12:20] <acheronuk> see how much chilli Harald can stand.....
 +1 acheronuk lol
 OK I'm off o/
[12:21] <shadeslayer> oh
[12:21] <shadeslayer> we did that already
[12:21] <shadeslayer> he was dying after Ade and I put in lots of chilli
[12:22] <acheronuk> oh. too late for that idea. damn
[12:22] <acheronuk> clivejo: you like chilli?
[12:22] <clivejo> nooooo
[12:23] <clivejo> hate spice, heat or curry
[12:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #104: STILL FAILING in 1 hr 8 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/104/
[12:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #50: STILL UNSTABLE in 1 hr 8 min: http://kci.pangea.pub/job/yakkety_unstable_discover/50/
[12:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #100: STILL FAILING in 1 hr 8 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/100/
[12:28] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kapptemplate build #78: FIXED in 1 hr 8 min: http://kci.pangea.pub/job/yakkety_unstable_kapptemplate/78/
[12:28] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kapptemplate build #205: FIXED in 1 hr 9 min: http://kci.pangea.pub/job/xenial_unstable_kapptemplate/205/
[12:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #58: STILL FAILING in 41 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/58/
[12:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #245: FAILURE in 1 hr 9 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/245/
[12:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #76: STILL FAILING in 1 min 10 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/76/
[12:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #83: STILL UNSTABLE in 1 hr 9 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/83/
[12:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #59: STILL FAILING in 38 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/59/
[13:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #277: STILL FAILING in 5 min 10 sec: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/277/
[13:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #160: STILL FAILING in 6 min 12 sec: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/160/
[13:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #278: STILL FAILING in 5 min 2 sec: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/278/
[13:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #161: STILL FAILING in 6 min 11 sec: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/161/
[13:32] <BluesKaj> Hi folks
[13:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #246: STILL FAILING in 1 hr 4 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/246/
[14:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop-pg-qt build #33: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_kdevelop-pg-qt/33/
[14:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #6: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/6/
[14:54] <acheronuk> hmmm. I can no longer switch to a VT on YY. just all blank if I try, and monitor decides there is no output
[14:54] <mamarley> acheronuk: Which GPU?
 Hmmmmmm
 Weird
[14:59] <acheronuk> Nvidia
[15:01] <mamarley> acheronuk: I don't have an NVIDIA system in front of me, but I can check when I get off work today.
[15:01] <tsimonq2> shadeslayer: you around?
[15:01] <shadeslayer> yus
[15:04] <tsimonq2> shadeslayer: hey, this fix has already been okayed by multiple MOTUS/release team members, and I see that you're a MOTU. Could you please upload the fix detailed in https://lists.ubuntu.com/archives/lubuntu-devel/2016-September/000824.html ?
[15:04] <tsimonq2> shadeslayer: nobody has uploaded
[15:04]  * tsimonq2 will pay beverage of choice :D
[15:04] <shadeslayer> where are the other acks?
[15:05] <tsimonq2> the email has the two people I worked with, and pitti also acked
[15:05] <tsimonq2> (over IRC)
[15:06] <shadeslayer> tsimonq2: I'll look over it tomorrow if that's alright?
[15:06] <tsimonq2> shadeslayer: that's fine :)
[15:06] <shadeslayer> cool
[15:07] <shadeslayer> let me put down a note
[15:07] <tsimonq2> shadeslayer: thank you :)
[15:07] <acheronuk> mamarley: thanks. going to try the old 4.4 kernel for now. see if that helps
[15:07] <tsimonq2> (only Lubuntu FTBFS left shadeslayer ;) )
[15:08] <shadeslayer> heh :)
[15:08] <tsimonq2> I wear many hats
[15:08] <tsimonq2> not as much as him though: https://youtu.be/TwArZLW3wbQ
[15:09] <tsimonq2> :P
[15:12] <acheronuk> old kernel did not help :/
 What PPAs?
 What *exact* graphics card do you have?
 Does it work with Neon?
 Does it work with KDE on Debian?
 Is everything fully migrated yet? That could be it.
 There's a lot of different variables there @acheronuk
[15:15] <acheronuk> I know, and I'm going through some of them one by one
[15:15] <mamarley> I can say that I just tried VT-switching on a fully up-to-date yakkety-proposed system (but with intel-drm-nightly kernel) and it worked.
[15:21] <acheronuk> not desktop dependant, and it occurs on lxqt and xfce4
[15:22] <soee> weee !!!!
[15:22] <soee> "Seven years after Warhammer 40,000: Dawn of War II launched on Windows, the game is rolling out today to Linux along with Chaos Rising and Retribution. " :D
[15:22] <soee> only 7 years ... :-)
[15:34] <santa_> shadeslayer: I think we still need a couple of uploads for frameworks/plasma, are you available to do that?
[15:34] <shadeslayer> maybe tomorrow
[15:35] <shadeslayer> santa_: send me a link of what to upload and I'll see when I can fit them in
[15:35] <shadeslayer> preferably with what changed
[15:36] <santa_> shadeslayer: dsc + diff in a web server is ok?
[15:36] <shadeslayer> yeah
[15:36] <santa_> ok, I will set it up later, thanks!
[16:18] <santa_> acheronuk: are you arenound?
[16:18] <santa_> * around
 Who broke ark? :P
 Aaaaaha!
[16:19] <santa_> indeed, tsimonq2 it's a test rebuild to test that the package is no longer buildable as it is
 Know how to fix that santa_?
[16:20] <santa_> yes, but I would like to know external thing what triggered that
[16:20] <santa_> also I have in my area 51 a test rebuild with the same results
[16:20] <santa_> http://gpul.grupos.udc.es/buildstatus_ubuntu-exp3/ubuntu-exp3_status_not-built.html
[16:21] <santa_> ↑ it was meant to be a rebuild to test my latest KA changes
[16:21] <santa_> but obbiously the problem is not KA, but the packages themselves
[16:32] <acheronuk> santa_: yes?
[16:33] <santa_> acheronuk: I wanted to discuss the isse that simon mentioned yesterday, current situation: 1. I have re-uploaded ark as it is to the staging ppa, it's failing to build because the path of the xml metainfo changed 2. I still don't know what is triggering this
[16:34] <santa_> the obvious "fix" would be changing the "*.install" files, but I would like to know what is triggering this first
[16:35] <acheronuk> ECM sets the appdata path
[16:35] <santa_> yeah
[16:35] <santa_> that's something I'm checking, if it's extra-cmake-modules 5.24 VS 5.26
[16:36] <acheronuk> that would be my 1st guess
[16:36] <santa_> I'm building ark in my ppa (where it should get 5.24)
[16:37] <acheronuk> santa_: https://quickgit.kde.org/?p=extra-cmake-modules.git&a=commit&h=5d10e167854af172b785b5d1f6b50baa09ddb87b
[16:38] <acheronuk> https://www.kde.org/announcements/kde-frameworks-5.25.0.php
[16:39] <acheronuk> "Appstream data changed its preferred location"
[16:39] <santa_> acheronuk: thank you very very much
[16:40] <santa_> wow
[16:40] <santa_> ximion: ping?
[16:40] <ximion> santa_: pong, eating right now, but write anyway
[16:40]  * ximion will reply later
[16:42] <santa_> since you are the author of appstream, this was changed in extra-cmake-modules https://quickgit.kde.org/?p=extra-cmake-modules.git&a=commit&h=5d10e167854af172b785b5d1f6b50baa09ddb87b
[16:43] <santa_> this change wasn't in e-c-m 5.24 but it is in 5.26 (if I'm not mistaken)
[16:44] <santa_> so my question is: let's say we have a package installing the metainfo file in the old location i.e. /usr/share/appdata/whatever.xml
[16:45] <santa_> does this break your appstream thing? or it's just that /usr/share/metainfo is "better"/preferred over the old path?
[16:55] <ximion> santa_: you will get a validator hint/warning, but the file will be processed
[16:55] <ximion> it doesn't break things (would be bad if it did ^^)
[16:55] <ximion> if you can, use the new location though
[16:56] <santa_> allright
[16:56] <santa_> so now, let me explain the situation here in kubuntu
[16:57] <santa_> with the new extra-cmake-modules we are getting some regressions reported by britney
[16:58] <santa_> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[16:58] <santa_> we wanted to get fw 5.26 in yakkety
[16:59] <santa_> but we may not be able to get apps 16.04.3 in
[16:59] <santa_> so this is what I'm planning to do
[17:01] <santa_> 1. fixing the install files of our current packaging in git for apps 16.04.3 so the location (old or new) won't trigger any ftbfs
[17:01] <ximion> choose the new location please :)
[17:02] <ximion> (will avoid unnecessary validator noise)
[17:02] <ximion> if you do that, there will be no issue at all
[17:02] <santa_> 2. if we can't get apps 16.04.3 as a *temporary* solution revert the change in e-c-m
[17:03] <santa_> ximion: we will get there with time, it's just that the ubuntu freeze right now is very inconvenient
[17:03] <santa_> the point 1. goes in that direction
[17:03] <santa_> the point 2. goes in the opposite, but we will do that if it's *unavoidable*
[17:04] <santa_> (only if it's unavoidable)
[17:04] <santa_> I'm all for updating apps in yakety and go for the new location, of course
[17:06] <ximion> santa_: depending on what's more effort, you could also apply the change in e-c-m as a patch to the older version and ensure the new location is always used
[17:06] <ximion> but whatever you do, it won't break AppStream :)
[17:06] <santa_> well, that's true
[17:06] <ximion> with older app versions you might have less metadata, which isn't nice, but also not a blocker
[17:07] <santa_> however if we patch 5.24 to use the new location we will make many apps fail to build
[17:08] <santa_> so let's say we are allowed by the release team to upload a patched 5.24 e-c-m
[17:08] <santa_> we would also need to upload a fair number of apps, because they would fail to build with the new location
[17:09] <santa_> ximion: so that's it, I guess I will discuss it with the release team and we will see if we can avoid 2. (I want very much to aboid it), thank you very much for your advice
[17:11] <santa_> acheronuk: I'm going to fix the apps, keep in mind that this invalidates the tarball you sent to potential sponsors
[17:16] <acheronuk> santa_: ack
 So santa_
 When I was training to be a ninja, a lot of the PRs I did was that transition
 I can help you if you want
 Or someone can just upload apps 16.04.3 already and we can just get that in first ;)
 Because I think our packaging for that fixes it?
[17:27] <tsimonq2> acheronuk: we should prep apps
[17:27] <tsimonq2> shadeslayer: are you willing to upload apps tomorrow?
[17:27] <shadeslayer> sure
[17:28] <tsimonq2> thanks a bunch shadeslayer :D
[17:28] <shadeslayer> np
[17:28] <tsimonq2> acheronuk: so we have an uploader. let's get it prepped! :D
[17:28] <acheronuk> shadeslayer: thankyou. for some reason I thought you were unable to do those
[17:29]  * tsimonq2 hops into linode
[17:30] <tsimonq2> acheronuk: gonna use my container to prep apps or someplace else?
[17:31] <acheronuk> your container doesn't talk to launchpad api for some reason
[17:31] <tsimonq2> oh?
[17:31] <acheronuk> or it didn't before anyway
[17:32] <santa_> keep in mind that we have to fix apps before uploading them, otherwise they are going to fail like ark
[17:32] <acheronuk> santa_: indeed
[17:32] <santa_> acheronuk, tsimonq2: do you want to collaborate with me in this effort?
[17:33] <tsimonq2> we need to trigger a no-change rebuild of all packages in staging-apps so we know what needs to be fixed
[17:33] <tsimonq2> santa_: totally, but in like 3 hours?
[17:33] <santa_> we can be a bit faster
[17:34] <tsimonq2> hm?
[17:34] <santa_> http://gpul.grupos.udc.es/buildstatus_ubuntu-exp3/ubuntu-exp3_status_not-built.html
[17:34] <tsimonq2> I'm home from school in 3 hours
[17:34] <santa_> ↑ I already did so we have a list of some packages which are going to build
[17:35] <santa_> so I can re-upload all apps to staging-kdeapps
[17:35] <santa_> and at the same time fix the build failures reported by my build box, because it's going to be ahead of the official ppa
[17:35] <santa_> .... or
[17:36] <santa_> we can fix now the apps failing in my build box and re-upload to the staging ppa to check that everything is fine
[17:36] <acheronuk> tsimonq2: can you enter keyring pw on your linode pls
[17:37] <santa_> let me fix ark before anything so we have an example
[17:38] <tsimonq2> acheronuk: argh, sorry
[17:38] <tsimonq2> would if I could
[17:40] <acheronuk> that is why I did the last lot of apps here on this machine
[17:40] <tsimonq2> then do it there ;)
[17:41] -kubuntu-ci:#kubuntu-devel- Project merger_ark build #464: FAILURE in 15 sec: http://kci.pangea.pub/job/merger_ark/464/
[17:41]  * tsimonq2 cracks whip
[17:41] <tsimonq2> lol
[17:41] <tsimonq2> more things o
[17:41] <tsimonq2> *to fixz
[17:41] <tsimonq2> *fix
[17:41] <tsimonq2> argh lol
[17:42] <santa_> yeah, we might break kubuntu_unstable but that can wait
[17:42] <tsimonq2> ok
[17:42] <santa_> right now it's very urgent to get the apps ready
[17:42] <tsimonq2> I agree
[17:42] <acheronuk> tsimonq2 santa: I am off to do things for 2-3 hrs at least shortly
[17:43] <tsimonq2> clivejo, acheronuk: in KCI shouldn't somebody eventually bump the changelogs for All The Things?
[17:43] <tsimonq2> cosas buenas acheronuk 
[17:43] <santa_> tsimonq2: what you mean bump?
[17:44] <acheronuk> tsimonq2: they get bumped in line with the yakkety_archive
[17:45] <acheronuk> so versioning will always be a bit behind at that +git*****
[17:45] <tsimonq2> what if there is a delay between a release of KDE * and when we get it in the archive?
[17:46] <tsimonq2> oh ok makes sense then
[17:47] <acheronuk> we need 'stable' branch build really
[17:48] <tsimonq2> yes we do
[17:48] <tsimonq2> yes siree
[17:48]  * acheronuk still ponders why he can't VT switch :/
[17:49] <acheronuk> santa_: I will be back in 2-3 hrs, I hope? ok?
[17:50] <tsimonq2> o/ acheronuk 
[17:51] <santa_> acheronuk: I will fix some things in the meantime
[17:51] <santa_> so, ok
[17:51] <tsimonq2> santa_: I'll be gone for about the same amount of time in like 15 mins
[17:52] <santa_> tsimonq2: ok, I will update you both with the progress done
[17:52] <tsimonq2> thanks again santa_, we really appreciate it ;)
[18:02] <acheronuk> santa_: are the apps that got sync'd from debian affected?
[18:03] <santa_> acheronuk: maybe they were a couple, but wheter they are or not we will get everything fixed in git and ready to upload
[18:05] <acheronuk> it skipped preparing those on the old upload script, which is why I asked
[18:06] <acheronuk> damn. gotta go. o/
[19:23] <valorie> santa_: this makes me so happy!
[19:23] <valorie> thanks for making the ask so well in -release
[22:02] <tsimonq2> acheronuk: are you even a little bit Irish?
[22:02] <valorie> everybody is a little bit Irish
[22:02] <valorie> at least on Saint Patrick's Day
[22:02]  * clivejo rolls eyes
[22:03] -kubuntu-ci:#kubuntu-devel- Project merger_dolphin build #468: FAILURE in 16 sec: http://kci.pangea.pub/job/merger_dolphin/468/
[22:03] -kubuntu-ci:#kubuntu-devel- Project merger_kate build #790: FAILURE in 20 sec: http://kci.pangea.pub/job/merger_kate/790/
[22:03] <tsimonq2> clivejo: me and valorie are talking in a PM
[22:04] <valorie> clivejo: he's threatening to visit you
[22:04] <valorie> lol
[22:04] <valorie> so watch out
[22:04] <clivejo> who is?
[22:04] <valorie> tsimonq2
[22:04] <clivejo> that could be interesting
 horrorific
[22:05] -kubuntu-ci:#kubuntu-devel- Project merger_kiriki build #427: FAILURE in 20 sec: http://kci.pangea.pub/job/merger_kiriki/427/
 lol
[22:06] -kubuntu-ci:#kubuntu-devel- Project merger_konsole build #770: FAILURE in 20 sec: http://kci.pangea.pub/job/merger_konsole/770/
[22:06] <clivejo> well considering he cant drive yet
[22:06] -kubuntu-ci:#kubuntu-devel- Project merger_picmi build #422: FAILURE in 13 sec: http://kci.pangea.pub/job/merger_picmi/422/
[22:06] <clivejo> and I live in the backside of nowhere
[22:06] -kubuntu-ci:#kubuntu-devel- Project merger_rocs build #554: FAILURE in 19 sec: http://kci.pangea.pub/job/merger_rocs/554/
[22:06] -kubuntu-ci:#kubuntu-devel- Project merger_umbrello build #84: FAILURE in 13 sec: http://kci.pangea.pub/job/merger_umbrello/84/
[22:07] -kubuntu-ci:#kubuntu-devel- Project merger_discover build #111: FAILURE in 19 sec: http://kci.pangea.pub/job/merger_discover/111/
[22:07] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-sdk build #593: FAILURE in 16 sec: http://kci.pangea.pub/job/merger_plasma-sdk/593/
[22:07] <tsimonq2> ahhhhhhhhhhhhhhhhhhhhhhhhhhhh
[22:08] <clivejo> tsimonq2: is that your doing?
[22:10] <tsimonq2> clivejo: nope
[22:10]  * tsimonq2 points at santa
[22:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #51: STILL FAILING in 5 min 57 sec: http://kci.pangea.pub/job/xenial_unstable_discover/51/
[22:21] <tsimonq2> acheronuk, santa_, clivejo: ¡Necesitamos preparar aplicaciónes ir a archivo rápidamente!
[22:21] <santa_> * para subir al archivo rápidamente
[22:22] <santa_> it's almost done, I think
[22:22] <tsimonq2> whoops, my grammar isn't the best yet ;)
[22:22] <santa_> at least the list of those which are failing to build with fw 5.26 for sure
[22:22] <clivejo> I dont speak whatever you are speaking
[22:23] <santa_> he said we need to prepare applications to upload them asap
[22:23] <tsimonq2> clivejo: ¡Español!
[22:23] <santa_> we got a few unexpected build failures
[22:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #52: STILL FAILING in 5 min 54 sec: http://kci.pangea.pub/job/xenial_unstable_discover/52/
[22:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #109: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/109/
 @tsimonq2, If anyone has a good environment to prepare them, go ahead. I sadly can't now until the morning.
[22:34] <tsimonq2> what do I have to do to prepare them then?
[22:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #51: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_discover/51/
[22:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #215: STILL FAILING in 27 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/215/
[22:39] <santa_> tsimonq2: I have to finish the fixes first
[22:39] <santa_> it's almost done
[22:40] <tsimonq2> ok let me know when
[23:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #76: STILL UNSTABLE in 53 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/76/
[23:12] <tsimonq2> santa_: how's it coming along?
[23:13] <santa_> tsimonq2: so far very well
[23:13] <tsimonq2> what's left?
[23:20] <santa_> tsimonq2: plasma-desktop + check that the packages I uploaded build fine in the official staging ppa
[23:21] <santa_> plasma-desktop is building here (it took a long time due to its epic memory usage when building certain *.cpp file)
[23:21] <tsimonq2> oh ok
[23:22] <santa_> once it finishes I'll push the change to git + upload to the official ppa
[23:22] <valorie> hey santa, if you have a few mins, it would be cool to write an email to the -devel list so everyone knows what's going on
[23:23] <tsimonq2> good idea valorie 
[23:24] <tsimonq2> santa_: you got eyes on plasma-discover ?
[23:24] <santa_> yes
[23:24] <tsimonq2> cool
[23:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #216: STILL FAILING in 45 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/216/
[23:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #110: STILL FAILING in 47 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/110/
[23:26] <santa_> https://imagebin.ca/v/2wnNJ57Sqq1l
[23:26] <santa_> plasma-desktop just a few minutes ago
[23:27] <tsimonq2> santa_: getting kde-cli-tools migrated from Proposed has now become a LOT more urgent
[23:27] <tsimonq2> santa_: comes with a security fix
[23:28] <tsimonq2> santa_: please be superhero ;)
[23:28]  * tsimonq2 is preparing a patch for Xenial
 @santa_, what is up with plasma-desktop?
[23:43] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-desktop build #867: FAILURE in 14 sec: http://kci.pangea.pub/job/merger_plasma-desktop/867/
[23:43] <santa_> tsimonq2: it fails to build like other because of the appstream data paths, so it's part of this "crusade" too
[23:44] <tsimonq2> pl
[23:44] <tsimonq2> *ok
[23:44] <tsimonq2> lol
 @tsimonq2, LOL
 @santa_, makes sense
[23:45] <tsimonq2> and we now have a security vulnerability to fix
[23:45] <tsimonq2> in Xenial