[00:00] <yofel> nothing. the epoch is never part of the filenames.
[00:01] <clivejo> it seems to have been a few days ago :/
[00:01] <yofel> no, the accept messages print the package version, the reject messages tell the change filename
[00:02] <yofel> those are 2 different things
[00:02] <clivejo> ah
[00:02] <clivejo> there was an email about the source code of ark being updated
[00:02] <clivejo> maybe thats why its rejected?
[00:03] <yofel> well, the email content tells you why it's rejected
[00:03] <clivejo> Hi Albert, any chance to have a respin for the Ark tarball? We need to
[00:03] <clivejo> > include this commit [1] in order to have a functioning Ark on Plasma
[00:03] <clivejo> > 5.7
[00:04] <clivejo> what should I version the respun orig tarball?
[00:04] <clivejo> a?
[00:04] <yofel> yep
[00:05]  * yofel fixed the docker deployment be reshuffling code whose oder shouldn't matter at all.........
[00:06] <yofel> I'll put the CI in production mode again
[00:06] <yofel> or maybe not......
[00:07] <yofel> oh conflicts, that's ok
[00:08] <clivejo> why does it always blame me :(
[00:08] <clivejo> Yippppe [~kubuntu-ppa/ubuntu/staging-kdeapplications/yakkety] ark 4:16.04.3a-0ubuntu1~ubuntu16.10~ppa1 (Accepted)
[00:09] <clivejo> see the epochs in that filename
[00:09] <clivejo> weirdness
[00:10] <yofel> that is not a filename ^^
[00:10] <clivejo> and you uploaded ffmpegthumbs to yakkety, so dont need to worry about it being missing
[00:10] <yofel> yep
[00:11] <clivejo> so its just kde4libs and kde-110n need looking at now
[00:14] <clivejo> kde4libs you did manually last time
[00:14] <clivejo> ?
[00:15] <yofel> yes
[00:15] <yofel> to get that as part of the auto run you have to set the correct version somewhere
[00:21] <clivejo> you didnt backport it?  Is it ok to do that?
[00:21] <clivejo> create the branch etc
[00:22] <clivejo> yofel: ^
[00:22] <clivejo> eakk kubuntu-ci left us!
[00:23] <yofel> hm, changing a global setting seems to reset the bot
[00:23] <yofel> clivejo: well, it should get backported. I didn't have it finished though
[00:24] <clivejo> Ill leave it then
[00:24] <tsimonq2> o/
[00:24] <tsimonq2> how are you all?
[00:24] <clivejo> but Ill create the branch
[00:24] <clivejo> hi Simon
[00:25] <yofel> o/
[00:25] <clivejo> we are having fun, breaking stuff
[00:25] <yofel> tired :P
[00:25] <clivejo> yofel has killed and brought KCI back to live a few times now
[00:25] <yofel> well, I *think* I have it down now. But we'll see when the build jobs start running
[00:26] <tsimonq2> hey clivejo, can you give me something more to do than fix build errors? :D
[00:26] <clivejo> Im afraid fixing build errors is the main job at the moment!
[00:28] <yofel> ok, LVM survived the forkbomb of launching 40 builds at once
[00:28] <tsimonq2> clivejo: alright :)(
[00:28] <tsimonq2> *:)
[00:28]  * clivejo cheers and pours himself a drink in celebration
[00:28] <tsimonq2> anything specific I can do at the moment or should I just go nuts? :)
[00:29] <clivejo> well yofel and I wont be about for much longer I reckon
[00:29] <clivejo> getting very near bed time
[00:29] <tsimonq2> I understand
[00:30] <clivejo> what does Rejected:'Description' mean
[00:31] <clivejo> on a LP email
[00:31] <yofel> uh, no idea o.O
[00:31] <clivejo> [~kubuntu-ppa/ubuntu/staging-kdeapplications] cantor_16.04.3-0ubuntu1~ubuntu16.10~ppa10_i386.changes (Rejected)
[00:31] <clivejo> weird emails
[00:33] <clivejo> yet the actual build looks fine to me - https://launchpadlibrarian.net/274724546/buildlog_ubuntu-yakkety-i386.cantor_4%3A16.04.3-0ubuntu1~ubuntu16.10~ppa10_BUILDING.txt.gz
[00:33] <clivejo> oh thats much better :P
[00:34] <tsimonq2> :P
[00:34] <tsimonq2> lol
[00:34] <yofel> 00:30:56 Host key verification failed.
[00:34] <yofel> 00:30:56 
[00:34] <yofel> 00:30:56 Unable to connect to SSH host ppa.launchpad.net; EOF during negotiation
[00:34] <yofel> what?!?
[00:38] <yofel> actually, why are we using dput over sftp...
[00:39] <clivejo> for me regular ftp stalls out on large files :/
[00:40] <yofel> hm, there is that, true
[00:41] <clivejo> like breeze
[00:42] <clivejo> calligra
[00:46] <tsimonq2> finally, I no longer have a red screen :P
[00:46] <clivejo> theres time yet
[00:48] <yofel> now with more executors you can have even larger red screens than before!
[00:49] <clivejo> 32 at once!
[00:49] <clivejo> thats fun!
[00:49] <clivejo> put it full screen and it gives the illusion of falling into a pit of doom
[00:51] <clivejo> yofel: whats it trying to do?
[00:51] <tsimonq2> XD yofel 
[00:51] <clivejo> does it dput the build to LP if it builds ok?
[00:52] <yofel> it dputs the source. And it tries that twice and fails then
[00:52] <yofel> I think we need a couple more tries with longer sleeps in between
[00:53] <clivejo> ive noticed with mass uploads LP sometimes ignores some of them :/
[00:53] <tsimonq2> yofel: wth? bug queue and there's IDLE builders?
[00:53] <tsimonq2> lol
[00:54] <clivejo> you increased linode executors to 40?
[00:54] <yofel> tsimonq2: the builds are ordered to prevent depwait / dep mismatch as possible. So e-c-m waits on the current jobs, and everything else waits on e-c-m as that's the frameworks root
[00:55] <tsimonq2> I see yofel 
[00:55] <clivejo> they gonna love us!
[00:55] <tsimonq2> yofel: just giving you a hard time ;)
[00:55] <yofel> clivejo: well, it survided launching most of those at once. So that'll stay like that
[00:56] <clivejo> is it ok to max the resources out on it?
[00:56] <yofel> that's not max resources, just high peak I/O. But it could probably handle even more
[00:57] <yofel> I think memory wise it used 3G at most, now using ~1G 
[00:57] <clivejo> CPU?
[00:58] <yofel> peaks occasionally at 100% when it's building lots of sources. But as the builders spent most of the time waiting for launchpad, average cpu usage is like 10% or so
[00:58] <clivejo> oh, its not actually building on the Linode machine?
[00:59] <yofel> it's building the sources, not the binaries
[00:59] <clivejo> ah
[00:59] <yofel> binaries are built in the PPA
[00:59] <clivejo> I thought it was building binaries too
[00:59] <yofel> building those would require a considerable amount of CPU power
[01:02] <clivejo> have you solved the LP not available messages?
[01:02] <yofel> no
[01:02] <clivejo> need a retry/sleep 
[01:03] <yofel> hm....
[01:03] <clivejo> did kde4libs build for you?
[01:03] <yofel> failed on symbols
[01:04] <clivejo> same here
[01:05] <clivejo> was there a problem with the symbols?
[01:05] <clivejo> or will a batchpatch fix it?
[01:06] <yofel> I think it's fine, but there was something fishy about it so I wanted to check it later
[01:09] <clivejo> #MISSING: 4:4.14.22# _ZTIN6Strigi14BufferedStreamIcEE@Base 4:4.14.16
[01:09] <clivejo> looks fishy to me
[01:12] <yofel> I think it's fine in practice because we haven't been using strigi in a long time, but that's a bit tricky to guarantee
[01:12] <clivejo> Ive removed them and will upload again
[01:24] <valorie> weeeee
[01:24] <valorie> so much work going on!
[01:24] <valorie> \o/
[01:25] <tsimonq2> o/ valorie :)
[01:27] <valorie> greetings
[01:28] <valorie> gosh if we get things fixed so quickly early, release will be a breeze
[01:28] <valorie> instead of a nail-biter
[01:28] <valorie> knock on wood.....
[01:29] <tsimonq2> valorie: when's the next release?
[01:29] <tsimonq2> and what are we releasing? lol
[01:30] <tsimonq2> s/we/the Kubuntu team/
[01:30] <valorie> !releases
[01:30] <valorie> oh dear, the wiki.....
[01:30] <tsimonq2> oh you mean like Yakkety and Xenial
[01:30] <tsimonq2> I see
[01:31] <valorie> https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule
[01:31] <yofel> applications beta 16.08 (16.07.80) was released yesterday I think. But for that 16.04.3 needs to be done, and we need a plan what we do with kdepim without qtwebengine
[01:31] <valorie> right, we just released 16.04.1 the other day
[01:31] <valorie> but that was just bugfixes
[01:32] <valorie> yofel: we've given up on qtwebengine?
[01:32] <valorie> sgclark started it, but didn't get far enough that someone can finish it?
[01:33] <yofel> valorie: from what I gathered on oftc, hefee might be taking another shot at that. But that might not be in time for us
[01:33] <valorie> does hefee have the work sgclark did?
[01:33] <yofel> yes, at least what's in git
[01:33] <valorie> good
[01:34] <valorie> well, I guess we can decide at some point before feature freeze
[01:34] <valorie> aug. 18
[01:34] <valorie> coming pretty soon
[01:34] <valorie> :(
[01:35] <valorie> there is another mail client
[01:35] <valorie> but it's no PIM
[01:35] <valorie> trojita
[01:35] <valorie> !info trojita
[01:36] <valorie> hmmm
[01:36] <valorie> I wonder why that isn't in the archive
[01:37] <clivejo> noone has packaged it yet?
[01:39] <valorie> right
[01:39] <valorie> lol
[01:39] <valorie> we might consider packaging that if PIM can't be provided
[01:40] <clivejo> theres a nightly for xenial here - https://launchpad.net/~lubuntu-dev/+archive/ubuntu/lubuntu-daily/+packages?field.name_filter=trojita&field.status_filter=published&field.series_filter=
[01:41] <valorie> looks like the last build failed.....
[01:42] <valorie> no, all green check marks, right?
[01:42] <valorie> but trojita-nightly - 0.7.0+201607230446~ubuntu16.04.1, none for 16.10
[01:43] <clivejo> nope, but that shouldnt be a huge problem
[01:43] <clivejo> how does it render the emails
[01:44] <clivejo> might also use qtwebengine
[01:44] <yofel> hm...
[01:45] <clivejo> oh dear
[01:46] <clivejo> failing to dput again
[01:48] <clivejo> oh its a KDE project - git://anongit.kde.org/trojita
[01:48] <yofel> yes, but like, why?!?
[01:48] <yofel> http://kci.pangea.pub/view/yakkety%20FIX/job/xenial_unstable_kplotting/192/console -> works
[01:48] <yofel> http://kci.pangea.pub/job/xenial_unstable_ki18n/204/console -> fails
[01:48] <clivejo> End of File of course
[01:48] <yofel> both linode
[01:50] <yofel> and now all the ones I look at work
[01:51] <yofel> and master is crapping out again
[01:51] <clivejo> 01:49:29 make: *** Cannot allocate memory.  Stop.
[01:54] <valorie> yes, trojita has been a KDE project for quite awhile
[02:00] <clivejo> my internet is sooooo slow
[02:01] <clivejo> and LP is soooooo slow
[02:03] <yofel> meh, and my slave permissions are soooooo wrong
[02:07] <clivejo> well kde4libs finally build and Im poked rebuilds, so on that note Im going to zzzzZZZZZzzzzzZZZZzzzzZZZ
[02:08] <yofel> nini
[02:08] <clivejo> and Ive downloaded 16.04.1 to install on a Windows 10 laptop sometime in the next few days!
[02:08] <clivejo> only took 2 hours!
[02:10] <clivejo> BTW do you mind if I create a LP git repo for trojita? I might look at that tomorrow if I get a chance
[02:10] <yofel> go ahead
[02:10] <yofel> ok, I think I worked around the permissions...
[02:11] <clivejo> would you mind putting that epoch email out?
[02:12] <yofel> opened up a new mail window with a subject. I'll write the rest in a bit
[02:39]  * tsimonq2 fixes problems
[03:00] <tsimonq2> where do I go to report a bug in a package in that Plasma Staging PPA?
[03:52] <tsimonq2> sorry I couldn't work on more today, I was out of the house, but at least I got to a fix for xenial_unstable_discover
[04:01] <tsimonq2> PR here if anyone wants to take a look: https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-plasma-discover/+merge/300983
[04:02] <tsimonq2> I'm off for the day
[04:02] <tsimonq2> o/
[07:08] <tsimonq2> hey hey hey I spot a acheronuk merging my MPs! :D
[07:08]  * tsimonq2 couldn't sleep
[07:09] <ahoneybun> I just saw the email
[07:09] <ahoneybun> damn Verizon phone hacking
[07:09] <tsimonq2> hey it's night owl ahoneybun :D
[07:09] <ahoneybun> heyo
[07:09] <tsimonq2> yeah :(
[07:09] <ahoneybun> trying to break into a phone atm
[07:09] <ahoneybun> or was about to sleep
[07:09] <tsimonq2> oh jeez
[07:09] <tsimonq2> you were going to sleep?
[07:09] <tsimonq2> :P
[07:09] <tsimonq2> and...
[07:09] <ahoneybun> the people made the phone go into FRP
[07:10] <tsimonq2> your phone got hacked?!?!?!?!?
[07:10] <tsimonq2> :(
[07:10] <ahoneybun> well not mine
[07:10] <ahoneybun> my dad bougt one off somepeople
[07:10] <ahoneybun> *bought
[07:10] <tsimonq2> oh okay
[07:14] <acheronuk> morning :)
[07:14] <tsimonq2> acheronuk: how are you? :)
[07:15] <acheronuk> tsimonq2: I would say that commit message was a bit long..
[07:15] <acheronuk> but that is my pref
[07:15] <acheronuk> tsimonq2: good thanks. :)
[07:19] <tsimonq2> wow long
[07:19] <tsimonq2> acheronuk: I literally copied the message I put in debian/changelog lol
[07:23] <acheronuk> tsimonq2: yes, for readability on that, a little less is more IYSWIM
[07:23] <tsimonq2> acheronuk: I see
[07:24] <tsimonq2> acheronuk: I'll make it more basic in the future
[07:24] <tsimonq2> so acheronuk, I see you're a ninja?
[07:25] <acheronuk> tsimonq2: yes, I got ambushed with that
[07:25] <acheronuk> or was a nice surprises a week or 2 ago I should say
[07:26] <tsimonq2> acheronuk: is it sort of like Ubuntu Membership where you have to show significant and sustained contribution, or is it like yellow belts, where I just had to convince ahoneybun I knew what I was talking about (I do, but all I had to do was talk to him)
[07:26] <tsimonq2> :P
[07:26] <tsimonq2> lol
[07:26] <acheronuk> tsimonq2: I still owe in bribes for it though. 
[07:26] <tsimonq2> lol
[07:27] <tsimonq2> acheronuk: I mean, what experience did you have beforehand?
[07:27] <acheronuk> tsimonq2: see https://community.kde.org/Kubuntu/Policies#.7Ekubuntu-ninjas
[07:28] <tsimonq2> acheronuk: I'm aware of that, I'm just wondering what *your* experience was :)
[07:28] <acheronuk> tsimonq2: I had been helping on here testing things for a few months, then submitting packaging fixes as you are doing. just generally helping out
[07:29] <tsimonq2> alright
[07:29] <tsimonq2> acheronuk: how long did you submit packaging fixes?
[07:30] <tsimonq2> (before becoming a ninja)
[07:30]  * acheronuk looks at irc logs
[07:32] <acheronuk> ummm... hard to find. lol
[07:33] <tsimonq2> acheronuk: do you have just a casual estimate, I don't need exact dates :)
[07:33] <acheronuk> tsimonq2: weeks/month or so rather than many months anyway
[07:33] <tsimonq2> acheronuk: month being singular?
[07:34] <acheronuk> tsimonq2: month and a bit? maybe?
[07:34] <tsimonq2> great thanks :)
[07:34] <acheronuk> tsimonq2: point is there is going to be no set time. you could be quicker. depends when the powers that be think you are ready
[07:34] <ahoneybun> seeing as ninjas have access to the PPA's we should trust them enough
[07:35] <ahoneybun> also we need 2 developers to vouch
[07:35] <acheronuk> ^^^ exactly
[07:35] <ahoneybun> as that page that acheronuk links to kinda explains
[07:35] <tsimonq2> yep :)
[07:35] <ahoneybun> at least with the 2 developer part
[07:36] <tsimonq2> I think I can do that :)
[07:36] <ahoneybun> since the PPAs also include the backports too
[07:36] <tsimonq2> I see
[07:36] <ahoneybun> not sure we have 2 official devs right now
[07:36] <acheronuk> I was a bit caught by surprise being added to that!
[07:37] <ahoneybun> the dev list or PPA?
[07:37] <tsimonq2> if I'm reading this description right, my best bet would be to work on something other than just yakkety/xenial failures :P
[07:37] <acheronuk> If yofel asks "Are you evil?.... then"
[07:37] <acheronuk> ahoneybun: ninjas
[07:37] <acheronuk> ahoneybun: all of it
[07:38] <ahoneybun> well the 2 devs left are yofel and scarlett
[07:38] <ahoneybun> and scarlett is on a break atm
[07:39] <ahoneybun> I would say that yofel would want a KC vote on it as a backup maybe
[07:39] <ahoneybun> which I think is fair as well
[07:39] <acheronuk> tsimonq2: yep, broaden it. help test iso when needed, how new releases in ppas etc upgrade, report bugs we find in LP or upstream, and on and on
[07:39] <ahoneybun> *not putting words into yofel's mouth here
[07:40] <ahoneybun> I can upload to the PPA's as a KC member I believe
[07:40] <ahoneybun> or Documentation :)
[07:40] <acheronuk> plenty to do
[07:40] <tsimonq2> alright acheronuk 
[07:40] <tsimonq2> acheronuk: fixing a merge right now
[07:41] <ahoneybun> since he knows the deb packaging maybe once he get's a KDE Identity account he can help with: https://notes.kde.org/p/kubuntu-packaging
[07:43]  * acheronuk goes looking for coffee
[07:47] <acheronuk> that's better :)
[07:51] <ahoneybun> valorie: what;s up with this: https://trello.com/c/uvJp5i9t/126-add-content-to-the-blank-wiki-pages-for-upgrades-to-xenial
[07:51] <ahoneybun> since you got me on trello
[07:52] <ahoneybun> mm I'll look at it tomorrow/today
[07:52] <ahoneybun> need sleep
[07:52] <tsimonq2> o/ ahoneybun 
[07:52] <ahoneybun> night tsimonq2 and acheronuk
[07:52] <valorie> well, I made the pages and asked for feedback but never got any
[07:53] <valorie> my fault for not adding you to the card I guess
[07:53] <acheronuk> ahoneybun: night :)
[07:53] <ahoneybun> since I'm on the card 
[07:53] <valorie> niters ah
[07:53] <ahoneybun> my bad
[07:53] <acheronuk> I'm just waking up!
[07:53] <tsimonq2> weird, ark's merge seems to be clean yet it's reporting an error
[07:53] <valorie> since my dad died I find a lot of details have sort of slipped through my fingers
[07:53] <ahoneybun> well it's 4am here
[07:54] <tsimonq2> acheronuk: do ninjas have access to rebuild on Jenkins?
[07:54] <tsimonq2> valorie: :(
[07:54] <acheronuk> tsimonq2: can retrigger a build, yes
[07:54] <tsimonq2> acheronuk: if so, could you rebuild the ark merger?
[07:54] <tsimonq2> \o/
[07:54] <valorie> tsimonq2: he was 89, so it was expected
[07:55] <valorie> but it still changed things
[07:55] <tsimonq2> I see valorie 
[07:55] <acheronuk> tsimonq2: let me look whats going on
[07:55] <tsimonq2> acheronuk: well the thing that's puzzling me is when I do it locally, I'm not getting the same errors as CI
[07:55]  * tsimonq2 does it command-by-command
[07:56] <acheronuk> tsimonq2: what is the difference
[07:57] <valorie> eyes are glazing over here too
[07:57] <valorie> niters all
[07:57] <tsimonq2> acheronuk: that's what I'm trying to find out, I can't see it
[07:57] <tsimonq2> o/ valorie 
[07:58] <tsimonq2> yofel: it was started by you, what's up?
[07:58] <acheronuk> tsimonq2: I mean what error do you get that KCI doesn't, or vice vera?
[07:58] <acheronuk> *versa
[07:59] <tsimonq2> [I] merger: Merging kubuntu_stable into kubuntu_unstable.
[07:59] <tsimonq2> /var/lib/jenkins/.rvm/gems/ruby-2.2.0@merger/gems/git-1.3.0/lib/git/lib.rb:937:in `command': git '--git-dir=/var/lib/jenkins/workspace/merger_ark/.git' '--work-tree=/tmp/KCIMerger20160724-5086-1tmzfgr' merge '-m' 'Merging kubuntu_stable into kubuntu_unstable.' 'kubuntu_stable'  2>&1:Auto-merging debian/changelog (Git::GitExecuteError)
[07:59] <tsimonq2> CONFLICT (content): Merge conflict in debian/changelog
[07:59] <tsimonq2> Automatic merge failed; fix conflicts and then commit the result.
[07:59] <tsimonq2> I get a clean merge
[08:00] <acheronuk> oh, an actual merge!
[08:00] <tsimonq2> http://paste.ubuntu.com/20716960/
[08:00] <tsimonq2> that's my output ^
[08:01] <tsimonq2> yeah, http://kci.pangea.pub/job/merger_ark/lastFailedBuild/consoleFull
[08:01] <acheronuk> I thought you meant a build triggered by a merge request you did
[08:01] <tsimonq2> no no no
[08:01] <tsimonq2> acheronuk: I'm expanding my skills ;)
[08:02] <tsimonq2> wait I think I'm doing it wrong locally, hold on here
[08:02]  * tsimonq2 checks the commits in the logs
[08:04] <acheronuk> tsimonq2: https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/ark/+ref/kubuntu_unstable
[08:04] <tsimonq2> acheronuk: it did the merge, I know
[08:06] <tsimonq2> acheronuk: I just don't know why the merge failed because it was already successful
[08:08] <tsimonq2> acheronuk: from all the merges I'm seeing, it's global
[08:08] <tsimonq2> acheronuk: which really makes me wonder what's up
[08:11] <acheronuk> tsimonq2: well, yofel's comment in this channel in response to the failure message last night was "oh conflicts, that's ok"
[08:11] <tsimonq2> alright, then I'll stop trying to fix it ;)
[08:14] <acheronuk> KCI was being "adjusted/fixed" a lot again last night it seems
[08:16] <tsimonq2> acheronuk: can you do a rebuild of yakkety_unstable_modemmanager-qt please? there's no code changes and it's failing because of running out of memory
[08:17] <tsimonq2> yakkety_unstable_sddm-kcm needs a rebuild, Launchpad error
[08:17] <tsimonq2> yakkety_unstable_polkit-kde-agent-1 needs a rebuild, Launchpad error
[08:18] <tsimonq2> yakkety_unstable_libkeduvocdocument needs a rebuild, Launchpad error
[08:18] <tsimonq2> yakkety_unstable_libkexiv2 needs a rebuild, Launchpad error
[08:19] <tsimonq2> same with yakkety_unstable_bluez-qt
[08:19] <soee> hiho
[08:19] <tsimonq2> o/ soee 
[08:19] <tsimonq2> same with yakkety_unstable_baloo
[08:20] <tsimonq2> memory error on yakkety_unstable_bovo , needs rebuild
[08:21] <acheronuk> last one was already queued
[08:21] <tsimonq2> alright thanks acheronuk 
[08:27] <tsimonq2> acheronuk: what
[08:27] <tsimonq2> *what's the deal with https://launchpadlibrarian.net/274322048/buildlog_ubuntu-xenial-amd64.kdepimlibs_4%3A16.04.3+p16.04+git20160721.1704-0_BUILDING.txt.gz ?
[08:27] <tsimonq2> sorry
[08:27] <acheronuk> needs the dev files for Qt5WebEngine
[08:28] <acheronuk> which is not even packaged in debian yet, let alone in our KCI
[08:28] <tsimonq2> acheronuk: what work has been done so far to fix it?
[08:28] <acheronuk> that is an ongoing thorny problem
[08:29] <tsimonq2> what work is going on to package Qt5WebEngine then?
[08:30] <acheronuk> tsimonq2: from last night http://paste.ubuntu.com/20719203/
[08:31] <tsimonq2> alright cool
[08:31] <acheronuk> scarlett is packaging it here for debian https://anonscm.debian.org/cgit/pkg-kde/qt/qtwebengine.git/
[08:32] <acheronuk> but she has a new job (or 2) and I don't think really has the time
[08:34] <tsimonq2> acheronuk: hmm, does this take the tarball from the PPA mentioned?
[08:35] <tsimonq2> seems like it
[08:36] <tsimonq2> wait no, nevermind
[08:37]  * tsimonq2 rambles to himself now
[08:37] <acheronuk> huh?
[08:38] <acheronuk> oh. lol
[09:13] <yofel> acheronuk, tsimonq2: My 'conflicts, ok' was related to me thinking I had broken the slave again
[09:13] <yofel> everything on http://kci.pangea.pub/view/merge%20FIX/ should get fixed, except oxygen-fonts, that's obsolete I think
[09:13] <tsimonq2> \o/
[09:14] <yofel> and for you not getting conflicts. The merger does a merge cascade, so you need to do the same to get the conflicts
[09:14] <tsimonq2> yofel: how does it do that?
[09:15] <acheronuk> I must admit, I had not looked that closely at what it does with those 
[09:16] <yofel> lets take http://kci.pangea.pub/job/merger_rocs/475/console for an example
[09:16] <yofel> the green merges are the ones actually executed
[09:16] <yofel> xenial is not the problem so we can ignore that
[09:17] <yofel> but it then merged kubuntu_yakkety_archive into kubuntu_stable, *and then* kubuntu_stable into kubuntu_unstable. So the actual conflict is probably from the indirect kubuntu_yakkety_archive -> kubuntu_unstable merge
[09:17]  * tsimonq2 takes a look
[09:17] <tsimonq2> yofel: that should really be more verbose
[09:18] <yofel> true, I also tend to wonder what it really does. sitter_ made is a bit too short..
[09:18] <yofel> *this
[09:18] <acheronuk> lookign at it, that does make sense
[09:18] <tsimonq2> yofel: is the source code for the build process public?
[09:19] <acheronuk> tooling is on github?
[09:19] <yofel> not anymore
[09:19] <yofel> tsimonq2: https://git.launchpad.net/~kubuntu-ci-admins/kubuntu-ci/+git/pangea-tooling/tree/kci/merger.rb
[09:20] <tsimonq2> thanks
[09:20] <tsimonq2> oh I see the issue, at least with rocs
[09:21] <tsimonq2> yofel: do I make an MP for the conflict resolution on kubuntu_yakkety_archive or kubuntu_unstable?
[09:21] <tsimonq2> the former I'm assuming?
[09:21] <yofel> kubuntu_unstable
[09:22] <tsimonq2> oh okay
[09:22] <yofel> you're getting a conflict because _unstable has changes that are not yet in _archive, and shouldn't yet be
[09:23] <tsimonq2> yofel: so I shouldn't fix it?
[09:23] <tsimonq2> or should I?
[09:24] <yofel> you should
[09:24] <tsimonq2> okay
[09:24] <yofel> otherwise _unstable won't get any fixes from _archive
[09:24] <tsimonq2> yeah
[09:25] <acheronuk> conflict != undesired changes?
[09:25] <tsimonq2> yofel: should I make a dch entry as well>?
[09:25] <tsimonq2> s/>//
[09:25] <acheronuk> just conflicting ones..
[09:26] <yofel> tsimonq2: rather not
[09:26] <tsimonq2> alright yofel 
[09:26] <yofel> try to edit the changelog in _unstable only for important changes
[09:26] <tsimonq2> okay
[09:26]  * tsimonq2 does a test rebuild and remerge locally
[09:26] <yofel> the changelog is *the* biggest source for merge conflicts
[09:27]  * acheronuk git skills still need polish
[09:28] <acheronuk> I am winging it a bit on git, but getting there.
[09:28] <tsimonq2> acheronuk: rtfm https://git-scm.com/book/en/v2/ :D
[09:29] <acheronuk> tsimonq2: most git guides seem only marginally better than the debian policy manual
[09:29] <acheronuk> zzzzzzzz
[09:29] <acheronuk> and ?????
[09:30] <tsimonq2> :P
[09:33] <tsimonq2> just deleted created PR because I forgot a few things, sorry for the mail
[09:39] <tsimonq2> yofel: so I just submitted the commit
[09:40] <tsimonq2> yofel: but it also includes the changes from the kubuntu_archive_yakkety branch
[09:40] <tsimonq2> yofel: is that bad?
[09:40] <yofel> no, that's fine, because that's what the merger was supposed to od
[09:40] <yofel> *do
[09:40] <tsimonq2> alright then, PR submitted
[09:40] <tsimonq2> thanks for explaining
[09:42] <acheronuk> helpful for me as well :)
[09:43] <acheronuk> tsimonq2: you are asking questions I hadn't thought to, or got around to, yet
[09:44] <tsimonq2> \o/ acheronuk :)
[09:44]  * tsimonq2 does lame ninja dance that acheronuk will never see ;)
[09:48] <tsimonq2> yofel: I've never read Ruby before, where does the script do the Git stuff?
[09:50] <yofel> tsimonq2: see line 131ff
[09:50] <tsimonq2> thanks yofel 
[09:53] <tsimonq2> why am I having such a hard time reading this?
[09:54] <tsimonq2> yofel: basically I want to know if it does anything more in the kubuntu_stable -> kubuntu_unstable step than kubuntu_stable and kubuntu_yakkety_archive ?
[09:59] <yofel> tsimonq2: it doesn't
[09:59] <tsimonq2> yofel: weird, ok, thanks
[09:59] <yofel> the merge cascade starts at run(), but I'm not exactly sure how some of those pieces work either
[10:00] <tsimonq2> yofel: maybe rebuild the ark merger? it runs right locally
[10:01] <yofel> lets see
[10:02] <acheronuk> hmmm...
[10:02] <tsimonq2> really weird
[10:02] <tsimonq2> yofel: can you also confirm that it works fine?
[10:02] <tsimonq2> (locally)
[10:02] <acheronuk> bbl. I read back in an hr of so if you work that out!!
[10:03] <yofel> I get a conflict
[10:03] <tsimonq2> yofel: what exact steps are you doing?
[10:03] <tsimonq2> because obviously I missed something
[10:04] <yofel> $ git checkout kubuntu_stable
[10:04] <yofel> $ git merge kubuntu_yakkety_archive
[10:04] <yofel> Fast-forward
[10:04] <yofel> $ git checkout kubuntu_unstable
[10:04] <yofel> $ git merge kubuntu_stable
[10:04] <yofel> CONFLICT (content): Merge conflict in debian/changelog
[10:04] <tsimonq2> oh so it merges that FIRST?
[10:04] <tsimonq2> that would have been good to know lol
[10:04] <tsimonq2> yofel: thank you, PR coming soon
[10:05] <yofel> well, it does say that:
[10:05] <yofel> [I] merger: Merging remotes/origin/kubuntu_yakkety_archive into kubuntu_stable.
[10:05] <yofel> [I] merger: Merging kubuntu_stable into kubuntu_unstable.
[10:05] <yofel> -> boom
[10:06] <tsimonq2> wth, it works fine...
[10:06]  * tsimonq2 does it over
[10:08] <tsimonq2> yofel: can you try those exact steps with a fresh ark clone please?
[10:08] <tsimonq2> that's what I've been doing
[10:08] <tsimonq2> *sigj*
[10:08] <yofel> I just did a fresh ark clone
[10:08] <tsimonq2> **sigh*
[10:21] <yofel> 10:16:34 make: *** Cannot allocate memory.  Stop.
[10:22] <yofel> great, I already reduced the builder count on master to 4... it's not like I can turn it off
[10:30] <acheronuk> That ECM change for the default appdata path is a pain!
[10:51] <tsimonq2> yofel: can you pastebin your debian/changelog file that it wants you to resolve merge conflicts for please?
[10:51] <clivejo> yofel: I think that memory error is due to something else
[10:52] <yofel> tsimonq2: http://sprunge.us/RWAi
[10:52] <tsimonq2> thanks yofel 
[10:52] <yofel> clivejo: I think it's a docker bug, but I hoped that reducing the amount of concurrent containers would help
[10:52] <clivejo> its only started recently
[10:53] <clivejo> tsimonq2: remember to resolve the merge conflict
[10:53] <tsimonq2> clivejo: well I'm actually not getting it locally
[10:53] <clivejo> ark will be a trick one
[10:53] <clivejo> tricky one
[10:53] <tsimonq2> how so?
[10:53] <clivejo> needs a bit of thought ;)
[10:54] <acheronuk> oooh. approved on wiki editors team
[10:54] <clivejo> you have two UNRELEASED entries
[10:54] <tsimonq2> I'm this close >< to just merging with the pastebin he gave me 
[10:54] <tsimonq2> oh okay
[10:54] <tsimonq2> I see
[10:54] <tsimonq2> but it actually merges fine locally
[10:55] <acheronuk> morning clivejo :)
[10:55] <clivejo> good morning
[10:55] <tsimonq2> looks like it's supposed it
[10:55] <tsimonq2> *to
[10:55] <clivejo> cant actually stay long :(
[10:56] <acheronuk> I probably won't be long here either. Grand prix, Sunday meal, and a little wine, and I may not much use on IRC
[10:58] <tsimonq2> yofel: does this look right? https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-ark/+merge/300988
[10:59] <tsimonq2> lol did my local merge actually fix things? :F
[10:59] <tsimonq2> *:D
[11:00] <yofel> tsimonq2: do you have any special changelog merge settings other than dpkg-mergechangelogs?
[11:00] <tsimonq2> yofel: how do I check that?
[11:00] <yofel> but that does look right
[11:01] <yofel> ~/.gitconfig probably?
[11:01] <tsimonq2> well lol my git is special XD
[11:01] <tsimonq2> yofel: my .gitconfig: http://paste.ubuntu.com/20731324/
[11:02] <yofel> hm, then you NOT using dpkg-mergechangelogs probably explains that
[11:02] <tsimonq2> huh? what's that?
[11:03] <yofel> [merge "dpkg-mergechangelogs"]
[11:03] <yofel>     name = debian/changelog merge driver
[11:03] <yofel>     driver = dpkg-mergechangelogs -m %O %A %B %A
[11:03] <tsimonq2> but I think my merge fixes it, right?
[11:03] <acheronuk> god. I forgot about that! duh
[11:03] <yofel> yeah, the merge looks good
[11:03] <tsimonq2> \o/
[11:03] <tsimonq2> well then I'm hesitant to install that if my git is magical :P
[11:03] <acheronuk> http://manpages.ubuntu.com/manpages/xenial/man1/dpkg-mergechangelogs.1.html
[11:04] <tsimonq2> RTFM? :P
[11:06] <acheronuk> not really. clivejo had to point me to that
[11:07] <clivejo> acheronuk: some of my ramblings are trying to teach you stuff :P
[11:08] <acheronuk> clivejo: they've served me well so far. just have to not forget!
[11:10] <tsimonq2> akonadi PR incoming!
[11:10] <acheronuk> I really need to get my head around the automation tools, but so much of it looks a leap in the dark
[11:10] <tsimonq2> acheronuk: what kind of patches did you submit to become a ninja?
[11:10] <tsimonq2> s/to become/before you became/
[11:11] <acheronuk> fixing files, fixing symbols, manpage changes, changes in /rules, etc etc
[11:12] <acheronuk> bit of most things, but there are still holes in what I can do with confidence
[11:13] <tsimonq2> clivejo, yofel: it annoys me that these Standards-versions are outdated, can I update them? :P
[11:13] <acheronuk> tsimonq2: for example https://launchpadlibrarian.net/274580284/buildlog_ubuntu-yakkety-amd64.kwidgetsaddons_5.24.0+p16.10+git20160723.0238-0_BUILDING.txt.gz
[11:14] <yofel> tsimonq2: well, we usually simply don't bother. But if you do, please check https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt
[11:14] <tsimonq2> thanks yofel :D
[11:14] <tsimonq2> yofel: well it bothers ME :P
[11:14] <yofel> you're not around long enough yet :P
[11:15] <tsimonq2> XD
[11:15]  * acheronuk thinks tsimonq2 will be writing the policy manual with that attitude, if it remains
[11:15] <yofel> I wonder if we have an example of symbol changes somewhere that's not fixed yet
[11:15] <tsimonq2> hahahahahahah
[11:15] <acheronuk> yofel: see link I just posted
[11:15] <yofel> because otherwise, I'm happy with what you did so far, and the evil question isn't necessary as it's covered by your ubuntu membership
[11:16] <tsimonq2> yofel: heheheheh
[11:16] <tsimonq2> wait...
[11:17] <tsimonq2> you didn't ask me if I was evil but you mentioned it...
[11:17] <tsimonq2> hmmmmm
[11:17] <tsimonq2> XD
[11:17] <yofel> I'll leave that up to you imagination :P
[11:17] <acheronuk> tsimonq2: I came from a cold start. You had 80-90% of it there already
[11:17] <yofel> *your
[11:18] <tsimonq2> yofel: are you suggesting what I think you are suggesting? :)
[11:18] <acheronuk> tsimonq2: which is why I ummmm'd on your questions of timing this morning
[11:18] <yofel> I'm only suggesting that ubuntu is evil, so who cares
[11:19] <tsimonq2> well as long as you don't think Lubuntu is evil, then I'm not evil :P
[11:19] <yofel> good enough ;)
[11:19] <acheronuk> everything tends towards being evil in the end. It's like entropy increasing in any closed system
[11:20] <acheronuk> \o/
[11:20] <tsimonq2> yofel: Lubuntu people trust me with administrative things, I can be trusted with administrative things
[11:20] <tsimonq2> :P
[11:20] <acheronuk> eek! there will be no stopping him!
[11:20]  * tsimonq2 suggests :P
[11:21] <yofel> uhmmmm
[11:21]  * tsimonq2 backs off a hair and goes back to fixing things
[11:21] <yofel> do you *want* me to have second thoughts about this? XD
[11:21] <tsimonq2> s/hair/little/
[11:21] <tsimonq2> nope
[11:21] <tsimonq2> nuh uh
[11:21] <yofel> heh
[11:22] <acheronuk> *** just do it ***
[11:22] <acheronuk> is that a song or advert?
[11:22] <tsimonq2> I even know the rule of if I feel unsure about some code, I make a PR
[11:22] <yofel> so yeah, how about acheronuk tells you how to fix kwidgetaddons?
[11:22] <yofel> (good find)
[11:22] <tsimonq2> ooh tell me! :D
[11:23] <acheronuk> conveniently I have to go now. :P
[11:23] <acheronuk> but I did do it in pbuilder yesterday
[11:23] <acheronuk> honest!
[11:26] <tsimonq2> \o/ ark fixed
[11:27] <acheronuk> tsimonq2: on the symbols https://pkg-kde.alioth.debian.org/symbolfiles.html
[11:28] <tsimonq2> ok thanks a lot acheronuk 
[11:28] <acheronuk> there are MISSING in that build-log ;)
[11:28] <tsimonq2> before I do that
[11:28] <tsimonq2> working on a cantor fix
[11:28] <tsimonq2> then I'll jump right on it
[11:29] <acheronuk> oh, and beware of marble. that needs a hell of a lot more fixing than you might think at first glance
[11:30]  * tsimonq2 stays away from it
[11:30] <tsimonq2> thanks for warning me acheronuk 
[11:30] <acheronuk> tsimonq2: not saying stay away, but you'll open a can of worms if you try!
[11:30] <tsimonq2> alright
[11:30] <acheronuk> think that may be why it's stayed unfixed for ages
[11:31] <tsimonq2> I'll be sure to clear my schedule :)
[11:31] <tsimonq2> ...my already empty one :( :P
[11:31] <acheronuk> right I HAVE to go!
[11:31] <acheronuk> have fun
[11:31] <tsimonq2> o/ acheronuk 
[11:33] <tsimonq2> cantor PR incoming!
[11:56] <tsimonq2> wow acheronuk you really stuck me with a complicated one
[11:56] <tsimonq2> jeez
[11:57] <tsimonq2> this documentation doesn't work well for these packages
[11:58] <tsimonq2> yofel: what modifications do I have to make for the steps in https://pkg-kde.alioth.debian.org/symbolfiles.html to work?
[11:59] <yofel> tsimonq2: the recommended prodedure for updating files is to fetch all buildlogs, make sure they're all uncompressed, then run batchpatch over them
[12:00] <yofel> tsimonq2: do you know what symbol files are for?
[12:00] <tsimonq2> I hate to admit this, but no clue
[12:00] <yofel> are you familiar with how linux shared objects (libs) work?
[12:01] <tsimonq2> no
[12:03] <yofel> ok, so for a binary to know which code block in a library it needs to use for a function, the compiler translates the code function names into machine readable symbols (the one you see here), and puts them into a symbol table together with a binary address of the relevant code block of that function
[12:04] <yofel> if you run nm -C on some lib, you can see the table, nm -DC will tell you the original function names
[12:04] <yofel> for c++ like here, c++filt <symbol> can tell you the function name of that symbol if you ever need to find that in code
[12:05] <tsimonq2> oh I see
[12:05] <tsimonq2> so when the code changes, so do the symbols
[12:05] <yofel> the symbol files then assiociate symbol with the first package version they appeared in, so that dpkg-shlibdeps can generate appropriately versioned dependencies on symbols
[12:05] <tsimonq2> right?
[12:05] <tsimonq2> alright
[12:05] <yofel> if the function names or parameter (types) change, the symbols change
[12:06] <yofel> the symbol files *also* tell us whether a symbol goes missing
[12:06] <yofel> which is then called a BIC - binary incompatible change
[12:07] <tsimonq2> I see
[12:07] <yofel> if an external user of the library was using a function that went missing in a new version of that lib, using the app with the new version will cause a "Symbol lookup error"
[12:08] <acheronuk> tsimonq2: just popping for 30s. yes, I stuck you with that, but for good reason ;)
[12:08] <tsimonq2> alright, I hope that I'll see what it is acheronuk ;)
[12:08] <tsimonq2> yofel: so how do you update these tables?
[12:08] <yofel> to still allow people to remove deprected stuff, we have SONAMEs, that's the library name + its SO version. That's why libs are e.g. called libfoo2, libbar34 and so on
[12:09] <tsimonq2> okay
[12:09] <acheronuk> tsimonq2: it 'IS' because there will be plenty more over time!
[12:09] <yofel> that correspons to the versioned librar filename on the system, e.g. libKF5Something.7 -> libkf5something7
[12:09] <yofel> wait, libKF5Something.so.7
[12:09]  * acheronuk shuts up and lets yofel teach
[12:10] <yofel> so, when symbols are MISSING, that's a warning from dpkg-gensymbols that something *might* be wrong
[12:10] <yofel> I say might, because you have private and public symbols
[12:11] <yofel> only the public ones are covered by the so version, as those are the only ones that an external application could possibly use
[12:11] <yofel> in this case, we have MISSING private library symbols that are only used internally, so we can just update the symbol file, remove the MISSING markers, and go on with out life
[12:12] <yofel> if you ever find MISSING public symbols, without a so version (ABI version) change in a new lib release, please scream at the developer ;)
[12:13] <yofel> so, that's the short background story. The page acheronuk linked to how we and debian handle c++ symbols, https://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html is a great read on how library packaging works, but you can read that another time
[12:14] <yofel> tsimonq2: still with me? ^^
[12:17] <yofel> the dpkg-gensymbols manpage explains the syntax of symbol files and what all the tags in it are for. Good read, but not something you need unless you get to a point where you have to hand-edit them
[12:48] <yofel> oh great, now kde is crapping out
[12:57] <acheronuk> kde git?
[13:06] <acheronuk> oh. yes
[13:24] <tsimonq2> yofel: sorry, I had to talk with dad
[13:24] <tsimonq2> yofel: back now
[13:26] <tsimonq2> alright, I understand :)
[13:28] <tsimonq2> yofel: so in that package, it adds symbols too
[13:28] <tsimonq2> yofel: do I just add the symbols in the symbols file and be done?
[13:29] <tsimonq2> yofel: or is it more complicated than that?
[13:29] <yofel> yes, please use pkgkde-symbolshelper to do that
[13:29] <yofel> that does a bit of symbol mangling as c++ is a bit annoying with types accross architectures
[13:30] <yofel> and no, all you'll have to do later is remove the MISSING lines from the files by hand
[13:31] <tsimonq2> yofel: no to?
[13:31] <yofel> being more complicated ^^
[13:31] <tsimonq2> alright
[13:39] <tsimonq2> yofel: PR on it's way! \o/
[13:39] <tsimonq2> thanks! :)
[13:40] <tsimonq2> that was easy :P
[13:42] <tsimonq2> https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-kwidgetsaddons/+merge/300994
[13:45] <yofel> ok, now that went wrong
[13:45] <yofel> come to think of it, i386 isn't being built, so that buildlog is useless
[13:46] <clivejo> also a good idea to add a change-log entry for other people benefit 
[13:46] <yofel> tsimonq2: what *exactly* did you run?
[13:46] <yofel> clivejo: for CI I would recommend not to do that
[13:47] <clivejo> oh sorry
[13:47] <tsimonq2> wget https://launchpadlibrarian.net/274580284/buildlog_ubuntu-yakkety-amd64.kwidgetsaddons_5.24.0+p16.10+git20160723.0238-0_BUILDING.txt.gz && gunzip buildlog_ubuntu-yakkety-amd64.kwidgetsaddons_5.24.0+p16.10+git20160723.0238-0_BUILDING.txt.gz && pkgkde-symbolshelper batchpatch -v 5.24.0 buildlog_ubuntu-yakkety-amd64.kwidgetsaddons_5.24.0+p16.10+git20160723.0238-0_BUILDING.txt
[13:47] <tsimonq2> yofel: note the amd64
[13:48] <yofel> hm, I wonder why I kept those i386 symbols then
[13:48] <yofel> aaaaaaah
[13:48] <yofel> the version is wrong
[13:48] <yofel> should've been 5.24.0+p16.10+git20160723.0238 in this case
[13:48] <tsimonq2> gosh darnit
[13:48] <tsimonq2> working on it now
[13:49] <tsimonq2> yofel: nice catch :P
[13:49] <clivejo> are we going to forget about i386 for unstable, pick any problems up at staging
[13:50] <tsimonq2> running this now: wget https://launchpadlibrarian.net/274580284/buildlog_ubuntu-yakkety-amd64.kwidgetsaddons_5.24.0+p16.10+git20160723.0238-0_BUILDING.txt.gz && gunzip buildlog_ubuntu-yakkety-amd64.kwidgetsaddons_5.24.0+p16.10+git20160723.0238-0_BUILDING.txt.gz && pkgkde-symbolshelper batchpatch -v 5.24.0+p16.10+git20160723.0238 buildlog_ubuntu-yakkety-amd64.kwidgetsaddons_5.24.0+p16.10+git20160723
[13:50] <tsimonq2> .0238-0_BUILDING.txt
[13:50] <yofel> there should be very little of those i386 issues, and having i386 enabled for the CI like quadruples the build complexity
[13:51] <yofel> but yeah, architecure mismatches we'll have to fix in staging
[13:51] <tsimonq2> yofel: fixed
[13:51] <yofel> tsimonq2: please remove the 3 lines saying #MISSING:
[13:51] <tsimonq2> alright
[13:52] <tsimonq2> yofel: done
[13:52] <yofel> yep, good now
[13:53] <tsimonq2> yofel: thanks for taking the time to explain this to me and work with me :)
[13:53] <clivejo> grrrrr libkgeomap maps to libkf5kgeomap
[13:54] <yofel> np, it's a compex topic. But like a third of our packages are libs
[13:55] <tsimonq2> also, could I please get eyes on https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-akonadi/+merge/300989 ?
[13:56] <tsimonq2> and https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-cantor/+merge/300990 ?
[13:57] <yofel> clivejo: ^
[13:57]  * yofel is off making dinner
[13:58] <tsimonq2> also, https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-artikulate/+merge/300933 never got merged?
[14:01] <tsimonq2> kalgebra PR incoming
[14:05] <tsimonq2> \o/
[14:05] <tsimonq2> khelpcenter PR incoming
[14:06] <clivejo> something strange going on with cantor
[14:07] <tsimonq2> hmm
[14:07]  * tsimonq2 looks into it
[14:09] <clivejo> hummmm how did that get into the archive branch
[14:09] <clivejo> that would be why its failing in staging
[14:09] <clivejo> wow
[14:09] <clivejo> thats is NOT good!
[14:10] <tsimonq2> clivejo: I'll fix in the archive branch then
[14:10] <tsimonq2> clivejo: alright?
[14:10] <tsimonq2> I was just about to say something
[14:11] <tsimonq2> sorry I didn't initially look closer for that sort of thing
[14:11] <clivejo> no please dont touch archive branchs
[14:11] <soee> clivejo: where are we with 5.7 + Qt 5.6 backports? What needs to be done with it ?
[14:11] <tsimonq2> alright
[14:11]  * tsimonq2 puts hands off
[14:11] <clivejo> not your fault Simon
[14:11] <tsimonq2> clivejo: I mean, it looks like an easy thing to fix
[14:11] <clivejo> script I run went haywire
[14:12] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/cantor/commit/?h=kubuntu_yakkety_archive&id=7422c21fb75cfe3d3ea3e162e01cb099632b81a3
[14:12] <tsimonq2> I have the diff right here, I could just restore it?
[14:12] <tsimonq2> ruh roh
[14:12] <clivejo> The script is only supposed to bump the build dep's but its removed the package description
[14:12] <clivejo> thats a MAJOR bug!
[14:13] <tsimonq2> clivejo: not saying you should want to do this, but if you accept my code, all you have to do then is update the stable branch and let it sync down
[14:14] <tsimonq2> (potentially stupid, but your choice :P)
[14:14] <clivejo> yofel: why on earth did bump-build-dep-versions do this - https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/cantor/commit/?h=kubuntu_yakkety_archive&id=7422c21fb75cfe3d3ea3e162e01cb099632b81a3
[14:14] <clivejo> tsimonq2: theres more to it
[14:14] <clivejo> yakkety branch is mirroring what we have in staging-apps
[14:15] <clivejo> http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.3_yakkety.html
[14:15] <clivejo> and is the reason why it is red on the page
[14:15] <ari-tczew> hi
[14:15] <ari-tczew> I'm working on new konversation merge. hope that I'm not duplicating someone else's work...
[14:16] <clivejo> I need to fix it and upload to staging
[14:16] <clivejo> soee: with Plasma 5.7?
[14:16] <tsimonq2> clivejo: when it's ready, let me know what I need to do to fix my PR :)
[14:17] <clivejo> tsimonq2: I need to do this myself from my end
[14:17] <tsimonq2> clivejo: I mean when it's all synced down, let me know so I can fix my PR
[14:17] <clivejo> tsimonq2: it should do it itself
[14:18] <tsimonq2> oh okay
[14:18] <tsimonq2> aha that's right
[14:18] <soee> clivejo: yes, what still needs to be done so we can put it into backports ppa.
[14:18] <Sho_> ari-tczew: thanks, appreciated (konvi maintainer)
[14:18] <clivejo> Qt5.6.1 and Plasma 5.7.2 are in staging-plasma for XX and YY
[14:19] <soee> clivejo: when moving to landing?
[14:19] <clivejo> I need a few test installs as some stuff needs no change rebuilds
[14:19] <clivejo> when it installs without trying to remove packages we need!
[14:24] <ari-tczew> ^ Repository '~kubuntu-packagers/kubuntu-packaging/launchpadgit/cantor/diff/debian/control' not found.
[14:25] <clivejo> ari-tczew: sorry?
[14:25] <tsimonq2> \o/ kwidgetsaddons is fixed!
[14:25] <yofel> clivejo: looks like yet another bug in python-debian :(
[14:25] <tsimonq2> two more PRs hurling your way!
[14:25] <ari-tczew> clivejo: go to the mentioned above my last message
[14:26] <tsimonq2> (kldap and kturle)
[14:26] <tsimonq2> *kturtle
[14:26] <ari-tczew> link mentioned
[14:26] <ari-tczew> clivejo: there is:     Fixing a weird mess caused by the bump-build-dep-versions script (detail / cgit)
[14:26] <ari-tczew> clivejo: you can click on the link on details or chit
[14:26] <ari-tczew> cgit*
[14:27] <tsimonq2> https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-rocs/+merge/300987 still needs looking at
[14:27] <clivejo> I am soooo confused
[14:27] <ari-tczew> clivejo: both don't work outputting the error like was in my paste
[14:27] <clivejo> slow down!
[14:27] <ari-tczew> ok, take deep breath and wait 10 sec.
[14:27] <ari-tczew> :)
[14:27] <tsimonq2> otherwise, besides merger_oxygen-fonts, that's all of 'em!
[14:27] <tsimonq2> (besides cantor :P)
[14:27] <yofel> hm, I see the error
[14:27] <yofel> I wonder where that's set..
[14:27] <clivejo> tsimonq2: https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-artikulate/+merge/300933 this was merged
[14:29] <tsimonq2> clivejo: then it didn't fix it :(
[14:29] <tsimonq2> wait no
[14:29] <tsimonq2> I'm dumb
[14:29] <tsimonq2> I'm mixing up my other fix PRs with the merge ones
[14:29] <tsimonq2> sorry clivejo 
[14:33] <tsimonq2> \o/
[14:33] <clivejo> tsimonq2: can you fix cantor now
[14:34]  * clivejo giggles to himself
[14:34] <mparillo> Regarding the e-mail from yofel regarding kubuntu-ppa/staging-kdeapplications, is that for YY, XX, or both?
[14:34] <tsimonq2> sure I will clivejo, if you look at my new artikulate PR :D
[14:34]  * tsimonq2 giggles to himself
[14:34] <tsimonq2> :P
[14:34] <clivejo> mparillo: yes both
[14:35] <clivejo> there where epoch added which shouldnt have been
[14:35] <mparillo> TY
[14:35] <clivejo> Ive actually purged the entire staging-apps PA and rebuilding all again
[14:36] <clivejo> still on YY
[14:36] <clivejo> but those packages will have to be forced to downgrade
[14:36] <clivejo> otherwise you will stuck with them
[14:37] <tsimonq2> clivejo: LOL
[14:38] <tsimonq2> clivejo: thanks for merging my PR bud XD
[14:40] <tsimonq2> clivejo: all of my PRs literally resolve all but merger_oxygen-fonts! :D
[14:40] <tsimonq2> (in mergers)
[14:41] <tsimonq2> \o/
[14:42] <ari-tczew> Sho_: done, https://launchpad.net/ubuntu/+source/konversation/1.6.1-1ubuntu1
[14:43] <tsimonq2> \o/
[14:43] <clivejo> tsimonq2: https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-kldap/+merge/300998
[14:44] <clivejo> its removing some debuild deps
[14:44] <clivejo> kdoctools-dev and kio-dev
[14:45] <tsimonq2> fixing
[14:46] <tsimonq2> sorry
[14:46] <clivejo> it might be right, just needs looked at
[14:47] <tsimonq2> clivejo: pushed
[14:47]  * tsimonq2 looks it over
[14:48] <clivejo> its actually right
[14:48] <tsimonq2> alright, reverting adding them back :P
[14:48] <tsimonq2> unless?
[14:48] <clivejo> but you need to be aware of what the merge is doing
[14:49] <tsimonq2> well kio-dev is 5.22 in Yakkety and we don't have anything in the CI PPA
[14:49] <tsimonq2> so removing it is justified for now, I think
[14:50] <tsimonq2> wait a minute
[14:50] <tsimonq2> we have Kio...
[14:50] <tsimonq2> good
[14:50] <clivejo> yes, a lot of packages need kio
[14:50] <clivejo> when it breaks its a nightmare on KCI
[14:50] <tsimonq2> clivejo: how it currently is is correct, we have both of those packages in the PPA
[14:51] <clivejo> we have the packages
[14:51] <tsimonq2> sorry for not looking more closely, I'll pay more attention in the future to that sort of thing
[14:51] <clivejo> but are they needed for the package to build
[14:51] <tsimonq2> clivejo: well I reverted removing those packages
[14:51] <tsimonq2> so it's fine
[14:52] <tsimonq2> all good I think ;)
[14:52] <clivejo> so basically I checked to see if the yakkety package built without those
[14:52] <clivejo> http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.3_yakkety.html
[14:52] <clivejo> and it does
[14:52] <clivejo> then I double checked with Debian
[14:53] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/applications/kldap.git/tree/debian/control
[14:53] <clivejo> and they are missing there
[14:54] <clivejo> so we dont need them
[14:54] <tsimonq2> alright
[14:54] <tsimonq2> what's the story with kdoctools?
[14:54] <clivejo> must have been needed by that package in the past
[14:54] <clivejo> !info kdoctools-dev
[14:55] <clivejo> its a framework
[14:55] <tsimonq2> but it's 5.24 in the PPA
[14:55] <clivejo> yup
[14:55] <clivejo> thats the lastest version
[14:55] <tsimonq2> so it's good to keep in?
[14:55] <clivejo> but its not needed for this package
[14:56] <clivejo> so we can remove it
[14:56] <tsimonq2> alright, fixing code
[14:56] <clivejo> not needed for the current release of this package
[14:56] <clivejo> it was probably needed in the past
[14:57] <BluesKaj> Hi all
[14:57] <clivejo> but when you look at the git dif and see something like that being removed you need to look into why
[14:58] <tsimonq2> clivejo: will do
[14:58] <clivejo> check with debian and neon to see what they are doing
[14:58] <tsimonq2> good to go then
[14:59] <tsimonq2> alright
[15:00] <tsimonq2> \o/
[15:04] <tsimonq2> \o/
[15:04] <tsimonq2> clivejo: regarding https://launchpadlibrarian.net/274776586/buildlog_ubuntu-yakkety-amd64.kate_4%3A16.04.3+p16.10+git20160724.1018-0_BUILDING.txt.gz , what do I do about usr/share/kxmlgui5/katexmltools/ui.rc ?
[15:04] <tsimonq2> clivejo: how do you find if the file still exists somewhere?
[15:04] <tsimonq2> or would it show up as uninstalled?
[15:05] <tsimonq2> \o/
[15:07] <clivejo> The buildlog shows you a list of all the files it installed
[15:07] <clivejo> heres the new path to -- Installing: /«BUILDDIR»/kate-16.04.3+p16.10+git20160724.1018/debian/tmp/usr/share/metainfo/org.kde.kate.appdata.xml
[15:08] <clivejo> but ui.rc doesnt seem to be being installed and should probably be removed from the kate5-data.install file
[15:08] <tsimonq2> that makes sense
[15:08] <tsimonq2> thanks for pointing that out
[15:08] <tsimonq2> fix will be coming soon
[15:11] <tsimonq2> clivejo: if the install files are different but there's a common directory that hosts both files, can I put the directory in one or the other or both?
[15:12] <clivejo> usually we like to include the full path
[15:12] <tsimonq2> alright
[15:13] <clivejo> it just allows us to see changes that happen
[15:13] <tsimonq2> yeah
[15:16] <tsimonq2> clivejo: I did it! \o/ http://kci.pangea.pub/view/merge%20FIX/
[15:17] <clivejo> !info qtquick1-5-dev
[15:17] <clivejo> tsimonq2: congrats
[15:17] <tsimonq2> clivejo: what's up with merger_oxygen-fonts ?
[15:18] <clivejo> I think its an old package
[15:18] <clivejo> I dont recognise it
[15:18] <clivejo> legacy maybe?
[15:18] <tsimonq2> I thought yofel said something about it earlier
[15:18] <clivejo> yofel: ^ could that be removed?
[15:19] <tsimonq2> clivejo: https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-kate/+merge/301003
[15:20] <clivejo> tsimonq2: did you run this through a chroot?
[15:20]  * tsimonq2 does that quick
[15:22] <tsimonq2> wait you merged, I'll still do the test build though
[15:22] <clivejo> Im impatient
[15:22] <clivejo> LOL
[15:22] <tsimonq2> me too
[15:23] <tsimonq2> :P
[15:23] <tsimonq2> I'm really tired anyways
[15:23] <tsimonq2> been up for 22 hours
[15:23] <clivejo> just got a feeling that there might be missing files
[15:23] <tsimonq2> so I think I'm gonna hit the hay
[15:23] <clivejo> we'll soon see!
[15:23] <clivejo> dont burn yourself out
[15:23] <tsimonq2> I'll address the problems later if there are any, o/
[16:38] <clivejo> yofel: kde4libs isnt built by KCI?
[17:02] <acheronuk> wow busy!
[17:02] <clivejo> yofel: I copied Debian repo for libdrumstick into LP.  However when I do a git-buildpackage-ppa on it, it correctly finds the source, but  downloads it as drumstick-1.0.2.tar.gz yet the script wants it as drumstick_1.0.2.orig.tar.xz
[17:02] <clivejo> is there any way to use it as gz or convert it on the fly?
[17:03] <acheronuk> sybols, I assumed i386 would have to be ironed out later. not wrong?
[17:04] <clivejo> acheronuk: yes, probably during staging when it builds i386
[17:05] <acheronuk> well, if not done that way with CI being just amd64, then we'd end up with stuff never building in CI
[17:05] <clivejo> acheronuk: any ideas why this is failing - https://launchpadlibrarian.net/274800056/buildlog_ubuntu-yakkety-amd64.kdepim-runtime_4%3A16.04.3-0ubuntu1~ubuntu16.10~ppa10_BUILDING.txt.gz
[17:06] <acheronuk> Depends: qtquick1-5-dev (>= 5.4.0~) but it is not going to be installed
[17:06] <acheronuk> ???????????
[17:06] <clivejo> indeed
[17:07] <clivejo> what is qtquick!
[17:07] <acheronuk> I'd have to load that up in build and start doing so dep resovling
[17:07] <ahoneybun> for making stuff
[17:07] <clivejo> Im assuming its a Qt5.6.1 issue
[17:09] <clivejo> https://launchpad.net/ubuntu/+archive/test-rebuild-20160701/+build/10276885
[17:09] <acheronuk> Qt qml api I thought?
[17:10] <clivejo> !info  qtquick1-5-dev
[17:10] <acheronuk> clivejo: could be. I did a rather naive backport and assumed there would be some problems
[17:10] <clivejo> very informative!
[17:11] <acheronuk> clivejo: I slighly amazed there has not been more hassle than there has been
[17:11] <acheronuk> clivejo: points to debian maintainers for that, as it's not my doing!
[17:12] <acheronuk> I shall look into it when I'm not stuffed with Sunday lunch and wine.....
[17:12] <clivejo> I dont think its part of what you done
[17:13] <acheronuk> ye/no, but looks related
[17:13] <clivejo> but the old one probably needs rebuilt or upgraded to newest version to work with QT5.6.1
[17:13] <Mirv> it looks like the Qt 5.6.1 would be stuck in proposed (if landed there) because of unfinished transitions. anyone planning to work on eg http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#extra-cmake-modules ?
[17:14] <Mirv> but I guess I can't assume everything will be green pre-landing, so when the landing time comes I will ignore some of that and assume they will be handled in the proposed pocket
[17:14] <Mirv> (I'm test running autopkgtests currently on the Qt 5.6.1 PPA)
[17:15] <clivejo> Mirv: ECM 5.24 has been built on acheronuk's version of Qt5.6.1
[17:16] <acheronuk> Mirv: yofle said he would do a trasition tracker for our qt5.6.1 builds. Not sure what happened to that aim? 
[17:16] <clivejo> https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-frameworks/+packages?field.name_filter=extra-cmake-modules&field.status_filter=published&field.series_filter=yakkety
[17:16] <acheronuk> *yofel
[17:17] <clivejo> we been waiting for Qt5.6.1 to officially be uploaded 
[17:17] <Mirv> clivejo: I don't mean it wouldn't build, I mean it's stuck in proposed since May and therefore also Qt 5.6.1 would be stuck in proposed if it would be published to proposed
[17:17] <acheronuk> Mirv: has been busy here and short handed
[17:17] <Mirv> clivejo: right, so that's what I meant, I assume you'll like it better when Qt 5.6.1 is actually in proposed. ok!
[17:18] <Mirv> it's possible to happen next week, but I'll wait on these autopkgtests a bit to see if anything surprising (not these) is found there.
[17:18] <clivejo> we been working with acheronuk's build to keep up with the development cycle
[17:18] <Mirv> and I'll land the new Qt Creator and associated changes tomorrow first separately
[17:19] <Mirv> clivejo: yeah, it's probably going to be good, just needs following the transition when the time is here
[17:19] <clivejo> Mirv: do you have an updated version of Qt Quick?
[17:19] <Mirv> clivejo: the PPA is now complete in terms of packages, yes https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-024/+packages
[17:19] <acheronuk> Mirv: sooner the better we can pull Qt from the YY archives (even proposed)
[17:20] <Mirv> acheronuk: ack.
[17:21] <clivejo> Mirv: thanks :)
[17:21] <clivejo> Ill copy that over to apps, hopefully get these last few to build!
[17:21] <Mirv> yw
[17:22] <acheronuk> yep, I was always winging it slighly with those QT builds
[17:22] <clivejo> acheronuk: you done a really good job!
[17:23] <acheronuk> when the first one worked and yofel said "do the rest" it was a bit ohhhhhhhhhh ummmmmmmmmm
[17:24] <acheronuk> as said, probably more points to debian maintainer that me!
[17:24] <clivejo> Im running Yakkety, Qt5.6.1, Frameworks 5.24 and Plasma 5.7.2, all due to you :P
[17:25] <clivejo> apps are a bit unstable, but once I finish them and install the Qt5.6.1 based ones, things should be a lot better
[17:25] <acheronuk> nope. you would have done it quite easiuly if I hadn't
[17:25]  * clivejo shakes head
[17:25] <acheronuk> but thanks for the thanks
[17:26] <acheronuk> oh well. it is what it is. hopefully it has got us moving when things were stalled a bit
[17:26] <clivejo> Mirv: I guess you wont be doing an official backport to Xenial?
[17:29] <clivejo> do any of you guys know how to change the source tarball?  its looking for tar.xz but the upstream only provides tar.gz
[17:30] <acheronuk> I thought it looked for .gz .bz2 or .xy
[17:30] <acheronuk> i.e any would do?
[17:30] <clivejo> I think you can set it somehwere
[17:31] <acheronuk> *.xz
[17:32] <clivejo> I have to convert is manually before
[17:32] <Mirv> clivejo: no, no official. an eventual copy (once all phone affecting bugs are fixed to enough extent) to the phone-overlay PPA, and probably another copy to some permanent home to upgrade Qt only for xenial users
[17:32] <clivejo> but there much be a way to just use tar.gz
[17:32] <acheronuk> What is "it"? something that checks tarball sigs or not?
[17:32] <clivejo> acheronuk: fancy backporting qtquick ?
[17:33] <acheronuk> linky?
[17:33] <Mirv> clivejo: I think it should find regardless of gz/xz/bz2 suffix, but it'll need the package-name_5.6.7.orig.tar.xz naming instead of package-name-5.6.7.tar.xz from upstream
[17:34] <clivejo> doesnt want to play ball with the gz version
[17:34] <Mirv> hmm :(
[17:34] <clivejo> acheronuk: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-024/+packages?field.name_filter=qtquick&field.status_filter=published&field.series_filter=
[17:35] <Mirv> I've noticed xz has been more and more the default, not sure if would be mandated already
[17:35] <acheronuk> odd if the name is right. is there some weird depreciation towards .gz?
[17:35] <acheronuk> that would be nuts
[17:35] <Mirv> oh by the way Debian already removed qtquick1-opensource-src from their archives, we should do the same but I didn't want to bring that up to this Qt 5.6 transition since it was possible to keep it compiling still
[17:35] <clivejo> I think you can set the source format somewhere
[17:36] <Mirv> Ubuntu has some more qtquick1 dependencies if I remember correctly so maybe for yakkety+1
[17:36] <acheronuk> pull-debian-source qtquickcontrols-opensource-src
[17:36] <acheronuk> gives a .xz
[17:38]  * clivejo goes away for a while, need to get some tea
[17:39] <acheronuk> oh. wrong package
[17:40] <acheronuk> no debian on the other, so yes looks dropped as Mirv said and was beyond doubt right
[17:56] <acheronuk> clivejo: is xenial apps staging going to be with Qt 5.6 from now on?
[17:57] <acheronuk> is so then I'll drop back to the stock packages until I decide what to do with this machine
[17:58] <acheronuk> need to force downgrade yoflls list anyway
[19:12] <clivejo> acheronuk: probably
[19:14] <acheronuk> thats fine. I'm just being a wuss on upgrading
[19:54] <clivejo> anyone know anything about the KDE Kiosk tool
[19:57] <clivejo> and is it something we need to package
[19:58] <soee> inst it something mobile plasma related ?
[19:59] <clivejo> no, its a tool for deploying Plasma in a multi seat environment
[19:59] <clivejo> like in a uni or workplace
[20:00] <clivejo> to lock Plasma down 
[20:02] <clivejo> soee: https://www.kde.org/applications/system/kioskadmintool/
[20:03] <clivejo> https://websvn.kde.org/trunk/extragear/sysadmin/kiosktool/
[20:39] <soee> clivejo: i'll start testing Plasma 5.7 for Xenial tomorrow 
[20:40] <clivejo> why tomorrow? why not now?
[20:41] <soee> need some sleep, have to go to office tomorrow @ 6:00
[20:41] <ahoneybun> mm need to find a way to use these two monitors with one laptop
[20:42] <soee> what monitors ? :D
[20:42] <ahoneybun> mm?
[20:43] <soee> i bought this and do not use laptop screen anymore http://www.ceneo.pl/39815125
[20:43] <ahoneybun> holy
[20:44] <clivejo> what currency is that?
[20:45] <soee> clivejo: polish Złoty
[20:45] <clivejo> you dont use yoyos?
[20:45] <soee> hers $ https://www.amazon.com/LG-29UC97C-B-UltraWide-2560X1080-Display/dp/B010PLPARG
[20:45] <ahoneybun> that so sounds made up
[20:46] <soee> i bought it for one year and than i will switch to 34'' when they get cheaper
[20:54] <clivejo> yofel: ^ kdewebdev seems to be dead?
[21:06] <valorie> wow so much work today!
[21:06] <valorie> you guys have been having some serious fun
[21:16] <jimarvan> hi guys
[21:17] <clivejo> hi jimbo !
[21:18] <jimarvan> hey clive
[21:18] <jimarvan> you feel good? :)
[21:19] <yofel> clivejo: kde4libs, no, I thought we didn't need it, but now that I think about it we have versioned deps on it probably...
[21:19] <yofel> and right, kdewebdev is dead, why did I add that....
[21:20] <clivejo> can I delete it and its merger?
[21:20] <yofel> go ahead
[21:20] <clivejo> where did you get the package list that included that?
[21:20] <yofel> apps
[21:21] <yofel> 16.04 still ships it
[21:21] <valorie> it seems like I researched kdewebdev and found out that it is now included in Kdevelop as a plugin
[21:21] <clivejo> oh
[21:21] <yofel> but I remember there being talk on release about killing it
[21:21] <valorie> killing > morphing
[21:21] <valorie> same with Quanta
[21:21] <clivejo> can I delete oxygen-fonts merger too?
[21:22] <yofel> hm, might as well, I disabled that
[21:23] <clivejo> do we need it?
[21:23] <yofel> probably not
[21:23] <yofel> hm, apps 16.08 also ships kdewebdev
[21:24] <clivejo> its annoying Simon :P
[21:24] <yofel> well, I don't get annoyed as fast
[21:24] <clivejo> has the git changed
[21:24] <yofel> no, it was a thing, but then kde switch to noto fonts or how they're called
[21:25] <clivejo> sorry I meant kdewebdev
[21:25] <clivejo> the job on KCI couldnt find the KDE git repo
[21:25] <yofel> hm..... is that by chance still in svn?
[21:26] <clivejo> I didnt look that hard to be honest
[21:26] <yofel> it is...
[21:26] <yofel> https://websvn.kde.org/trunk/KDE/
[21:26] <yofel> ok, lets forget about that
[21:26] <clivejo> thought I heard the project was dead/unmaintained 
[21:27] <clivejo> yofel: did you see my question about xz and gz source tarballs?tarball
[21:27] <yofel> clivejo: uscan will download whatever is supported by the watch file
[21:28] <clivejo> it does
[21:28] <clivejo> but the git-buildpackage-ppa seems to look for a xz 
[21:28] <clivejo> and fails
[21:29] <yofel> true, it hardcodes xz
[21:29] <yofel> :/
[21:29] <yofel> adding kde4libs to ci in the meantime
[21:30] <clivejo> I moved kde4libs YY to KCI unstable earlier today
[21:30] <clivejo> and restarted builds that needed them, hence the green above 
[21:30] <yofel> adding it anyway
[21:30] <clivejo> oh you mean as a job
[21:30] <clivejo> good idea
[21:30] <yofel> now all that's intentionally not on CI is kdewebdev and the strigi analyzers
[21:33] <valorie> yofel: you mean from plasma, frameworks and applications?
[21:33] <yofel> yes
[21:34] <valorie> imo there are other things we don't package/check like apps from extragear
[21:34] <valorie> right?
[21:34] <yofel> nothing out of the offical release set is on CI
[21:34] <yofel> not that we couldn't add something
[21:37] <valorie> !info gcompris
[21:37] <valorie> !info kstars
[21:37] <valorie> !info konversation
[21:37] <clivejo> why does the tooling want an epoch on libexiv2-dev 
[21:37] <yofel> although, I would first like to make the CI builds meaningful again. Currently yakkety unstable are the only branch that have meaning
[21:38] <valorie> !info minuet
[21:38] <yofel> minuet is in apps
[21:38] <valorie> I'm not pushing, just clarifying
[21:40] <clivejo> yofel: another epoch package which shouldnt be :(
[21:40] <yofel> hm?
[21:40] <clivejo> libexiv2
[21:42] <yofel> hm, true, I missed that...
[21:45] <clivejo> is that all the places it needs changed - https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/commit/?id=de6f8c01c716c55fbb49688e7f81799b407148d4
[21:46] <yofel> should be
[21:47] <yofel> oh
[21:47] <yofel> right, kde4libs is that exception of exceptions in our workflow
[21:47]  * clivejo nods
[21:47] <clivejo> can KCI deal with it?
[21:48] <valorie> more and more stuff gets ported away from it, so eventually it will disappear.....
[21:49] <clivejo> valorie: unfortunately that doesn’t look like any time soon :(
[21:49] <clivejo> still a lot of packages wanting it
[21:49] <valorie> well, we'll have to support it for LTS for a long time
[21:49] <yofel> fixed it by hand for now, but this needs manual reconfiguring every time I refresh the CI configs
[21:49] <yofel> so... I need a different solution for this
[21:52] <yofel> o.O
[21:52] <yofel> something for tomorrow..
[21:53] <clivejo> is there a quick way to convert gz to xz?
[21:53]  * valorie goes out in the sun while it still shines
[21:54] <yofel> gunzip && xz ?
[22:00] <clivejo> grrrr
[22:00] <clivejo> it downloads the gz
[22:01] <clivejo> the complaints gbp:error: Multiple orig tarballs found.
[22:37]  * clivejo kicks stuff
[22:37] <clivejo> why the *beeping* *beep* has libkf5kface still got an epoch
[22:59] <clivejo> who looks after konversation_1.6.1-1ubuntu1_amd64.deb, Im getting an error
[22:59] <clivejo> trying to overwrite '/usr/share/kservices5/konvirc.protocol', which is also in package konversation-data 1.6-0ubuntu1
[23:44] <clivejo> how do you change the wallpaper in Plasma 5.7.2?
[23:57] <DarinMiller> clivejo: right click on desktop and select desktop settings.
[23:58] <clivejo> Ive lost the wallpaper on one of my screens
[23:58] <clivejo> thats weird