[00:34] <jose> Riddell, ovidiu-florin: I think we want to move the new articles to the new site too?
[01:12] <dodger> Riddell: I think it just needs to be accepted by someone
[03:40] <dodger> so, i've got a small app for mounting ecryptfs file systems because i got tired of mounting via terminal everytime; I'm writing the passphrase from user input to a file in /tmp, then calling mount with passphrase_passwd_file, and deleting that file immediately after the mount is complete; does that sound acceptable?
[03:42] <dodger> might be the wrong place for this, but i figured I'd ask anyway ;)
[06:10] <jussi> Riddell: apachelogger ScottK shadeslayer etc etc, any thoughts about http://perezmeyer.blogspot.fi/2014/05/call-for-help-from-kde-team.html ? 
[06:11] <ScottK> I think we're already working with them.
[06:11] <ScottK> I'm sure they'd like us to do more, but I don't see how it's feasible.
[06:14] <valorie> it seems like everybody is understaffed
[06:15] <valorie> no matter where you look
[06:16] <jussi> what are their main issues? just packaging?
[06:16] <valorie> bug triage too
[06:16] <valorie> and getting patches upstreamed
[06:16] <valorie> gosh, I thought that was just us
[06:17] <valorie> Sune got his Muon GSoC student, which is cool
[06:22] <valorie> I wonder if they have thought about joining in GCi through the KDE team, and clearing some of the backlog
[06:22] <valorie> training kids to deal with bug reports, testing patches, and even learning packaging
[06:23] <valorie> I think I'll comment on the blogpost even though I speak only english
[06:40] <lordievader> Good morning.
[06:41] <valorie> done
[07:22] <apachelogger> jussi: uh uh uh, I totally have thoughts on that: stop tracking bugs that aren't your own \o/
[07:22] <apachelogger> I hear kubuntu has a policy for that :P
[07:22] <jussi> heh...
[07:26] <apachelogger> seriously tho... not tracking bugs that aren't caused by $project eliminates sore spot 1 and 2, 3 is taken care of by actually creating fixes upstream and then cherrypickering and by doing those two things 5 autoresolves because suddenly the bugs that were not your own have a 300 times wider possible audience
[07:27] <apachelogger> (random rage comment on no 5 tho: the notion that random bugs reported on $distro's random $bts makes 
[07:27] <apachelogger> brrr)
[07:27] <valorie> are you commenting on the blog?
[07:27] <apachelogger> yuz
[07:27] <valorie> <3
[07:29] <apachelogger> it wasn't their bugs to begin with, but they feel the need to fix em because they were reported on their BTS (which obviously makes them not more or less important than say a bug reported on the upstream BTS) deserve patchery simply because they were reported there is making me squint a lot
[07:33] <apachelogger> that is a case of choosing to filter perception ... "what you do not know about you can not consider important", so you can conveniently get to the point where you feel responsible for what was explicitly asked of you (i.e. fixing a bug that potential is not your own) and you do not question that situation
[07:34] <valorie> agreed
[07:34] <apachelogger> alas, that is actually applicable to a lot more cases than bugs... people tend to be too nice feeling responsible for things that they should not feel responsible for
[07:34] <valorie> getting jammed up sometimes is good; it forces you to focus on what's most important
[07:35] <valorie> this has happened a few times in my life, and every time it was good
[07:35] <valorie> in retrospect
[07:35] <apachelogger> oh, and one last word, those comments are not necessarily about debian, it's a general problem distributions choose to have, and even with a policy in place we still tend to get that from time to time
[07:35] <valorie> agreed
[07:35] <valorie> to many people doing the same work, the *exact same work* over and over
[07:36] <apachelogger> yes
[08:40] <Riddell> hmm, someone using gpg in and upgrading to 4.13 not happy it doesn't work now
[08:41] <Riddell> surprising we havn't had anyone using 14.04 complain about that
[08:54] <apachelogger> Riddell: there was
[08:55] <Riddell> ah
[09:48] <Riddell> any thoughts on how translations should work in plasma next?  the files will overlap those of kde sc
[09:49] <Riddell> which will happen with everything that is in kde sc as it gets ported to kf5
[09:49] <apachelogger> rename all of it
[09:49] <apachelogger> alternatively ... install to a different path
[09:49] <apachelogger> since we pass stuff through klocalizedstring we can really set any arbitrary search path in there I think
[09:50] <Riddell> that needs renaming everything in kde sc (although I'm not sure what the current thinking is on how to release those, if any)
[09:50] <Riddell> we can yes
[09:50] <apachelogger> Riddell: I meant rename it in plasma next, not the SC
[09:50] <Riddell> right, but then everything else in kde sc needs renamed as it gets ported to kf5
[09:50] <apachelogger> but really, I think a different dir seems more appropriate
[09:50] <apachelogger> and more in line with the rest of the world
[09:51] <Riddell> which rest of the world installs to a different directory?
[09:51] <apachelogger> share/applications/
[09:51] <apachelogger> or did we drop the subdir there?
[09:51] <apachelogger> because then I fear we have a set of conflicts for kf6 coming up :P
[09:51] <Riddell> we have /usr/share/locale-langpack/
[09:52] <apachelogger> Riddell: from an upstream POV I meant
[09:52] <Riddell> which we patch in to be read
[09:52] <Riddell> it only conflicts becuse the release setup is changing, from kde sc into separate bits
[09:52] <Riddell> kf5 have renamed all their .po files
[09:53] <Riddell> I guess the options are 1) install to different dir and patch klocalizedstring  2) rename all .po files  3) tell distros to patch out kde-l10n from shipping the relevant files
[09:54] <apachelogger> well
[09:54] <apachelogger> the thing is
[09:54] <apachelogger> Riddell: does the workspace need to be cooinstallable?
[09:54] <Riddell> no
[09:54] <apachelogger> because I'd rather think not
[09:54] <BluesKaj> Howdy folks
[09:54] <apachelogger> Riddell: right then just leave them conflicting? ;)
[09:55] <Riddell> but it needs to be co-installable with kde-l10n-xx from KDE4
[09:55] <apachelogger> aaaaah
[09:55] <apachelogger> now I get it
[09:55] <Riddell> which includes .po files from kde-workspace
[09:55] <Riddell> I actually think 3) might be the best option
[09:55] <apachelogger> Riddell: subdir kdesc would be the way to go IMHO
[09:56] <apachelogger> that's plenty cheap really
[09:56] <Riddell> ah move old stuff to new dir, hmm
[09:56] <Riddell> and patch kde4libs
[09:56] <apachelogger> yeah
[09:56] <apachelogger> moving forward the kf5 separation of bits is the saner thing
[09:56] <apachelogger> so I'd move the kde4 files out of the way rather than adjust kf5
[09:57] <Riddell> thanks, I'll suggest that to packagers and see if they scream in horror or mumble acceptance
[11:15] <sgclark> Riddell: good morning, please let me know if there is anything that needs working on.
[11:16] <Riddell> morning sgclark 
[11:17] <Riddell> sgclark: always more merges
[11:17] <Riddell> qt4 if you want a serious challenge, that's a mega big package
[11:17] <Riddell> pkg-kde-tools https://merges.ubuntu.com/main.html
[11:18] <sgclark> qt4 for merge or packaging?
[11:18] <Riddell> sgclark: merge
[11:19] <Riddell> debian has 4.8.6
[11:19] <Riddell> so the merge will include an update to that newer version
[11:21] <Riddell> sgclark: good old shadeslayer merged it at the start of this year so there's not much to work out
[11:22] <Riddell> sgclark: just add back all the differences which are nearly listed in the changelog
[11:22] <Riddell> sgclark: think you can take it on?
[11:25] <sgclark> Riddell: so sorry, this wifi seems to be very unstable lately. I would like to give qt4 a shot.
[12:38] <sgclark> Riddell: help please http://paste.ubuntu.com/7379301/
[12:46] <Quintasan> sgclark: Check the changelog for MIPS, maybe it has anything to say about this
[12:47] <Riddell> sgclark: what file is that in?
[12:48] <Riddell> sgclark: you probably want to keep the ubuntu change, ubuntu builds on arm64 which I don't think debian does.  debian builds on mips64 which we do not.
[12:48] <sgclark>   C  src/3rdparty/webkit/Source/JavaScriptCore/wtf/Platform.h
[12:48] <sgclark> ok
[12:50] <ScottK> Debian has an arm64 port, it's just not very mature. If we have a fix for arm64, it should be sent to Debian. 
[12:51] <Riddell> sgclark: but you shouldn't be changing files in the qt source, only in the debian/ directory
[12:51] <sgclark> Riddell: grab-merge did this
[12:52] <Riddell> sgclark: it's why I don't like tools like grab-merge :)
[12:52] <Riddell> sgclark: it might be an upstream change between 4.8.5 and 4.8.6 or more likely it's from a patch in debian/patches
[12:53] <Riddell> sgclark: yes it'll be in aarch64_fix_jsc.patch or aarch64.patch
[12:54] <Riddell> sgclark: so just make sure you keep all the patches from the ubuntu package
[12:54] <sgclark> Riddell: ok
[12:59] <sgclark> Riddell: last one, rules file http://paste.ubuntu.com/7379383/
[13:03] <Riddell> sgclark: the last merge changelog says "Build with -no-pch on powerpc"
[13:03] <Riddell> but looks like debian also has that
[13:03] <Riddell> so keep debian line
[13:04] <sgclark> ok
[13:20] <Riddell> doctorpepper_: has the indexer finished indexing?
[13:20] <doctorpepper_> yes
[13:21] <doctorpepper_> i actually had to delete the baloo database and restart  the indexing
[13:22] <Riddell> hmm
[13:48] <shadeslayer> ScottK: Could you accept libkpeople now?
[14:15] <dodger> Riddell: I just tried GPG encryption and signing in KMail on Trusty here, and it works for me
[14:19] <doctorpepper_> which package provides these two files :  KFileMetaDataConfig.cmake  kfilemetadata-config.cmake
[14:21] <yofel> doctorpepper_: dpkg -S <filename>    will tell you
[14:21] <yofel> well, when installed
[14:21] <yofel> let me check
[14:22] <yofel> doctorpepper_: libkfilemetadata-dev
[14:23] <doctorpepper_> thanks
[14:23] <doctorpepper_> i dont know why dpkg  didnt show this result
[14:24] <yofel> as I said, it only works when already installed. apt-file find can help too (doesn't work with PPAs though)
[14:28] <Riddell> dodger: use packages.ubuntu.com to answer questions like that
[14:29] <dodger> Riddell: I'm confused - questions like what?
[14:30] <Riddell> oh sorry that was to doctorpepper_ ↑
[14:30] <dodger> ah, ok :)
[14:32] <shadeslayer> kubotu: newversion homerun 1.2.3
[14:32] <shadeslayer> derp
[14:32] <kubotu> https://bugs.launchpad.net/bugs/1315405
[16:00] <kubotu> ::workspace-bugs:: [1313082] Screensaver-Process does not terminate @ https://bugs.launchpad.net/bugs/1313082 (by Ralph Scharpf)
[19:03] <ScottK> shadeslayer: Both in now.
[22:09] <dodger> I just updated from proposed on trusty, and with the new kpeople the ktp contact list is now fixed. Thanks!
[23:50] <ScottK> dodger: please say so in the bug.