[07:56] <spbox> hi, testing kdepim from staging-kdeapplications: kmail shows no mailheaders without kdepim-addons: https://bugs.kde.org/show_bug.cgi?id=364929
[07:57] <soee> you should not use staging :-)
[08:01] <spbox> I thought staging on XX needs testing?
[08:09] <acheronuk> https://plus.google.com/u/0/110954078302330754910/posts/Hjb1mVJT7Vg
[08:30] <acheronuk> spbox: also see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826746
[08:39] <acheronuk> clivejo: do we update our PIM with the changes made since May here? https://anonscm.debian.org/cgit/pkg-kde/applications/kdepim.git/log/
[08:40] <acheronuk> or cherry pick some like the adding of a recommends on kdepim-addons?
[08:45] <acheronuk> spbox: thank you for pointing that out :)
[09:06] <yofel> acheronuk: I would recommend a merge. If it's not too much work
[09:07] <acheronuk> yofel: ok. I'll do that later
[09:12] <acheronuk> yofel: is that literally a merge using git, then fixing the conflicts? or just do the changes as you would other things, and call that a merge?
[09:13] <yofel> acheronuk: I do either one depending on the situation. Here I would just do a git merge, but you'll need to read through the whole debian/ubuntu diff after that to check if there's duplicate or obsolete changes.
[09:13] <yofel> if you think that would take too long, do cherry-picks
[09:16] <acheronuk> I may do via git locally 1st then, and see what the result looks like
[09:17] <acheronuk> I need practice with git
 Actually I noticed the email header thing too
[09:40] <yofel> o.O
[09:40] <yofel> Clifford: can you think of a reason why staging konsole did not merge kubuntu_unstable into kubuntu_yakkety_archive?
[09:40] <yofel> oh wait
[09:41] <yofel> that only happens for unstable releases I think?
 Yeah it seemed to be merging stable
 And saying nothing to do
[09:48] <yofel> right, I think you need to explicitly tell it to use unstable
[09:49] <yofel> 16.08 beta is on the 21st, so we can try it out then ^^
 I can't get this tagging script to work
[09:53] <yofel> then I'll do it, what needs tagging again?
[09:58] <soee> https://www.kde.org/announcements/kde-frameworks-5.24.0.php
[10:01] <yofel> debfx: are you still using ftpubuntu for your depot access?
[10:06] <debfx> yofel: haven't used it in years
[10:10] <yofel> debfx: ok if I remove you?
[10:11] <debfx> sure
[10:15] <acheronuk> if I merge from debian, do I need to detail the changes (e.g new recommends) in the changelog, even though as a result it already mentioned due to the merge earlier on? 
[10:15] <soee> !info kdegraphics-thumbnailers
[10:15] <acheronuk> or would I just stick with the terse "Merged with debian" or similar and leave it at that?
[10:15] <yofel> acheronuk: no, that should already be in the changelog?
[10:16] <acheronuk> yes, that's why I asked. 
[10:17] <acheronuk> I think I knew the answer, but for now I'm just double checking things like that.....
[10:17] <yofel> I tend to stick to "Merge with debian git", and then list all the changes I had to do to fix the merge
[10:18] <yofel> for non-vcs merges you usually write "merge with debian unstable", then list the full diff between debian and ubuntu. But as we use git I see little value in that
[10:18] <acheronuk> yep. got it.
[10:18] <acheronuk> seems the merge was clean and doesn't need fixing!
[10:19] <yofel> then all you need to check if it builds and whether anything was changed that we didn't want changed
[10:19] <acheronuk> it's running in pbuilder right now
[10:20] <yofel> a warning about git merge: as maxy occasionally uses changes from us, a 'git merge' on his side + any changes he does will not cause any conflicts if we do a 'git merge' again, even if we don't want any of those changes
[10:20] <yofel> not an issue most of the time, just something to be aware of
[10:21] <yofel> which is why I said to review the whole diff again after the merge
[10:21] <yofel> and also the diff of the merge commit itself
[10:21] <acheronuk> I went through it and it seems sane to me
[10:21] <yofel> (that's why merging takes so much time for me at least :/ )
[10:21] <yofel> ok, thanks
[10:23] <acheronuk> It was not very complicated in the end, but I can see how it could be v time consuming in in some cases
[10:23] <acheronuk> or perhaps most cases
[10:25] <yofel> make that some. Most of the smaller packages are almost identical with debian
[10:25] <yofel> or litirally are (with an ubuntu version)
[10:25] <yofel> *literally
[10:27] <acheronuk> is it git amend to add my changelog entry after the merge, as the merge auto-commited?
[10:29] <yofel> not sure, I just do another commit
[10:30] <acheronuk> oh. I've just done it, so I'll double check the diff again
[10:31] <acheronuk> that worked
[10:43] <acheronuk> yofel clivejo: so that went into yakkety_archive. do I need to merge that elsewhere somehow?
[10:44] <clivejo> is it working?
[10:44] <yofel> no, the CI is supposed to auto-merge _archive into _stable and _unstable
[10:44] <acheronuk> clivejo: is what working?
[10:45] <clivejo> the package you are working on
[10:45] <acheronuk> it built with no probs if that is what you are asking?
[10:45] <acheronuk> in pbuilder
[10:45] <clivejo> yup and does it fix the original problem?
[10:47] <acheronuk> I will check, as I don't use kmail
[10:47] <clivejo> well is the code there to fix the issue
[10:48] <clivejo> the dep on kdepim-addons
[10:49] <clivejo> yes I see it
[10:49] <acheronuk> the recommends is in there, so should do?
[10:49] <clivejo> ok so do a git-buildpackage-pppa
[10:50] <clivejo> current version is ppa1
[10:50] <clivejo> so you need to create a ppa2 version
[10:51] <clivejo> so "git-buildpackage-ppa -s 2"
[10:51] <acheronuk> that is all?
[10:51] <clivejo> in the package git directory
[10:52] <clivejo> it will go grab the source, and build the source ready for upload to LP
[10:52] <clivejo> the move into ../build-area 
[10:53] <clivejo> dput the *.ppa2*.changes file to apps staging
[10:53] <acheronuk> kdepim_16.04.3-0ubuntu1~ubuntu16.10~ppa2 is there
[10:54] <acheronuk> done
[10:54] <clivejo> :)
[10:54] <acheronuk> :D
[10:56] <clivejo> if the problems it fixes closes LP bugs, you can close them down via the changelog
[10:57] <sheytan> Heya!
[10:57] <sheytan> Any news about nvidia and sddm problems?
[10:57] <acheronuk> clivejo: ah yes, I read that the other day
[10:57] <sheytan> is stuff solved yet?
[10:58] <clivejo> but git-buildpackage-ppa is a great wee tool
[10:58] <acheronuk> it is indeed! 
[10:59] <acheronuk> sheytan: specific or general problem? I have a nvidia card here and it works fine
[10:59] <clivejo> did you get time to look at ffmpedthumbs?
[11:00] <acheronuk> ffmpegthumbs id tha same prob as before is it not? kde release tarballs do not have that fix for ffmeg 2.9 in them 
[11:00] <acheronuk> *is the
[11:01] <acheronuk> you fixed before by using the KCI source?
[11:01] <clivejo> yofel: is this worth fixing?  Ive copied over a version from KCI which fixes the problem
[11:02] <clivejo> yakkety wont be frozen for a while yet
[11:02] <clivejo> so the fix has time to filter down from upstream
[11:02] <yofel> ffmpegthumbs is apps?
[11:02] <yofel> then no
[11:03] <yofel> actually no in any case, as we want the next version of everything
[11:03] <clivejo> I kinda feel like making and applying a patch would be a waste of time and effort
[11:04] <clivejo> yeah its apps 16.04.3
[11:06] <sheytan> acheronuk: SDDM wasn't starting up after i installed nvidia driver, but it was before i did clean intall kubuntu 16.04. Now I'm running on noveau, afraid of breaking up my OS when i install nvidia
[11:09] <yofel> sheytan: works fine on my desktop with nvidia-364 at least
[11:09] <yofel> if it does break, you should be able to get a shell through the recovery mode where removing the package should bring nouveau back
[11:10] <sheytan> yeah, i know. Do you have optimus (nvidia + intel), too?
[11:10] <yofel> (the card is reported as GK107 [GT 740])
[11:10] <yofel> not on my desktop, but on my notebook. There is just use intel
[11:10] <sheytan> mine is 525m
[11:11] <yofel> GM108M [940m] / Intel HD Graphics 5500
[11:11] <sheytan> and it does work with nvidia driver, too?
[11:12] <yofel> it theoretically does, with all the optimus issues, so I set prime to intel
[11:12] <sheytan> yofel: how do you do that?
[11:13] <yofel> sudo prime-select intel
[11:13] <yofel> prime-select query will tell you what it's currently set to
[11:14] <sheytan> k, thank you
[12:32] <clivejo> wow
[12:32] <clivejo> email headers are back
[12:32] <clivejo> thanks acheronuk
[12:34] <acheronuk> clivejo: I find it odd they put the support for that in a separate package and repo
[12:40] <clivejo> lot of packages I find odd!
[12:44] <acheronuk> person asking about it this morning was actually trying the XX statging of 16.04.2. so does fix have to go into the git for that? or will it just get merged down when/if 16.04.3 gets staged for XX? 
[13:50] <BluesKaj_> Hiyas all
[14:05] <acheronuk> yofel clivejo: konsole is failing in unstable as an alternative to the debian-T-addition.diff was proposed by HS and adopted upstream
[14:05] <yofel> ah, kill the patch then
[14:06] <acheronuk> yofel: removing patch doesn't work as the upstream needs http://doc.qt.io/qt-5/qcommandlineoption.html#setHidden
[14:06] <acheronuk> introduced in qt t5.6
[14:06] <yofel> how would it build without that?
[14:07] <yofel> upstream requires qt 5.6 anyway, so we need to put that into the CI PPA to fix some of the jobs
[14:07] <acheronuk> yes, that was what I was coming to, as fixing it would only be a short term thing, and not the real solution
[14:08] <acheronuk> building with QT 5.5.1 fails anyway, as I tried
[16:07] <ScottK> yofel: FYI, I've removed my ssh key from the ftpubuntu account on depot.k.o (I'm on Debian's so I still have access).
[17:37] <sick_rimmit> I can see that Plasma Workspace is failing to build, because the patch to CMakeLists file is failing, and then dpkg-buildpackage errors
[17:44] <acheronuk> sick_rimmit: looks like another patch now applied upstream https://quickgit.kde.org/?p=plasma-workspace.git&a=blobdiff&h=70dd71d1557aea65e5f232bcafeb8750dec4474c&hp=bdbaa13cf9167348480b3bcb2c373a54383a1246&hb=1a39a51e2e36576ca97f5b88af0969687796e7b4&f=CMakeLists.txt
[17:57] <sick_rimmit> Oooo cheers acheronuk
[17:57] <sick_rimmit> I will take a look
[17:58] <yofel> ScottK: ok, thanks for the heads up
[18:18] <sick_rimmit> So it looks like the upstream commit, has added 3 extra lines into the CMakeLists.txt file. This means that the install_missing_headers in /debian/patches doesn't work because Patch has Fuzz which it can not resolve
[18:18] <sick_rimmit> I think we could change
[18:18] <sick_rimmit> @@ -103,7 +103,10 @@ include_directories("${CMAKE_CURRENT_BINARY_DIR}") 
[18:18] <sick_rimmit> to read
[18:18] <sick_rimmit> @@ -105,7 +105,10 @@ include_directories("${CMAKE_CURRENT_BINARY_DIR}") 
[18:19] <sick_rimmit> in that patch and it would fix it
[19:13] <acheronuk> may need some expert opinion on some MISSING symbols?
[19:14] <acheronuk> after fixing build of akonadi for KCI in pbuilder now get these MISSING http://paste.ubuntu.com/18910668/
[19:18] <yofel> acheronuk: looks like another case of 'ok for kci, not ok for 16.08 release'
[19:18] <acheronuk> this commit? http://quickgit.kde.org/?p=akonadi.git&a=commit&h=381acbc294dcecb0d4beb63721080d231e4bca38
[19:20] <yofel> yes, that one
[19:20] <acheronuk> yofel: so I can leave those for now and see how it pans out?
[19:21] <yofel> yes
[19:22] <acheronuk> ok. 
[19:23] <acheronuk> that makes sense. 1st instinct on seeing that though is "OMG, I need to fix that!"
[19:24]  * yofel 's is "OMG, not... oh, that's pim, nvm"
[19:26] <acheronuk> LOL
[19:26]  * clivejo is liking PIM again
[19:27] <acheronuk> I don't like it and don't use it (apart from akregator)
[19:32] <yofel> it's not like it's that bad, it just accumulated lots of bad karma
[19:34] <clivejo> *hugs PIM and covers its ears*
[19:34] <clivejo> dont listen to these mean people
[19:36] <acheronuk> It's probably OK. I'm just too used to using other apps now.
[19:36]  * clivejo is playing with an IP camera he picked up in Lidl today
[19:37] <clivejo> dunno what to make of it
[19:41] <clivejo> Its obviously punching a hole in my firewall to allow me to connect to the camera from outside, but how its doing that worries me
[19:41] <clivejo> I need to know more!
[19:44] <acheronuk> order a 240GB SSD yesterday. hopefully I will know what to make of that
[19:45]  * clivejo tries to suppress the green eyed monster
[19:46] <acheronuk> reminds me. any progress with linode?
[19:46] <clivejo> yeah we have accounts now
[19:47] <acheronuk> you do?
[19:47] <clivejo> not me
[19:47] <clivejo> aaron and yofel
[19:48] <acheronuk> fair enough. just curious, rather than impatient
[19:48] <clivejo> Im still trying to tag FW and Plasma
[19:48] <clivejo> and not getting anywhere!
[19:49] <acheronuk> not an app (script) for that?
[19:49] <yofel> people can get containers on request
[19:49] <clivejo> can we get a shared container
[19:49] <clivejo> where multiple people can log in at once
[19:50] <yofel> sure, that's the default setting. You just need to add the relevant ssh keys
[19:51] <yofel> you should be able to access the container that aaron tried to set up for you now
[19:51] <clivejo> how does one get a container?
[19:51] <yofel> ask me and aaron currently
[19:51] <yofel> s/and/or/
[19:52] <acheronuk> what happens with signing packages over ssh?
[19:53] <yofel> remote signing should work fine..
[19:53] <acheronuk> yes? I had a feeling that was tricky, but would prefer to be wrong
[19:54] <yofel> hm, it is a bit.. but then again, I rarely use it
[19:59] <acheronuk> I looked the other day and found a few things like this: http://code.v.igoro.us/posts/2015/11/remote-gpg-agent.html
[20:02] <yofel> clivejo: I added an account for you on the host. I put a howto to create containers at the bottom of the ninjas notepad
[20:03] <yofel> please only use that account for container management
[20:04] <clivejo> ok!
[23:45]  * mamarley does soee's job: https://www.kde.org/announcements/kde-frameworks-5.24.0.php
 Read the logs... :)
[23:46] <mamarley> Oh, did I miss it?  Sorry. :(
 <soee> https://www.kde.org/announcements/kde-frameworks-5.24.0.php