[08:33] <lordievader> Good morning.
[11:04] <clivejo> hi lordievader
[11:05] <soee_> >_<
[11:07] <clivejo> yofel: you about?
[11:22] <lordievader> Hey clivejo, how are you doing?
[11:23] <lordievader> Relieved some stress from yesterday?
[11:27] <clivejo> not really
[11:28] <clivejo> need help
[11:28] <clivejo> if I could just get a yes or a no whether Im doing these merges correctly
[11:29] <lordievader> Unfortunately I cannot help you with that.
[11:30] <clivejo> so Im just playing about with packaging kolab
[11:37] <yofel> clivejo: pong
[11:38] <clivejo> hi yofel would you check over my merges
[11:43] <yofel> clivejo: I'll probably won't review everything, but I'll look at some of them
[11:44] <clivejo> I need help with kio too
[11:44] <clivejo> Ive really messed it up :(
[11:44] <yofel> saying that, the changelog in knetwalk is wrong
[11:45] <yofel> frameworks kio?
[11:46] <clivejo> yes
[11:47] <yofel> could you push your changes somewhere so I can see them?
[11:49] <clivejo> yofel: there are a few changes
[11:51] <yofel> well, I need to see them *somehow*. You can also git add everything then pastebin the output of git diff HEAD
[11:51] <yofel> that should show all changes
[11:51] <yofel> as long as you didn't commit anything yet
[11:51] <clivejo> Ive only touched the unstable branch
[11:52] <yofel> ok, there we go. Now I know where to look :)
[11:52] <clivejo> but I created a stable branch
[11:53] <clivejo> and thats when things started going haywire :(
[11:53] <clivejo> theres a new lib libkf5kiogui
[11:53] <clivejo> so I added two new packages libkf5kiogui5 and libkf5kiogui5 -dev
[11:54] <clivejo> but somehow I seems to have done a merge of master into unstable
[11:54] <yofel> do frameworks even need a stable branch?
[11:55] <yofel> and remove  libkf5kiogui5 -dev, the content belongs into kio-dev
[11:56] <yofel> http://anonscm.debian.org/cgit/pkg-kde/frameworks/kio.git/diff/debian/libkf5kiogui5.install?h=kubuntu_unstable&id=0e3e08096a4ead8b06a8610277d5f17ceb21d184
[11:56] <yofel> please wildcard the api version away.
[11:57] <clivejo> how do you keep local branches separate?
[11:59] <yofel> I don't quite get your question. Local branches are kept separate by different names. Remote branches are namespaced using their remote by default
[11:59] <yofel> e.g. local kubuntu_unstable trackes remote origin/kubuntu_unstable
[11:59] <clivejo> like if I want to build it locally and make changes to try and fix it
[11:59] <yofel> you commit without pushing?
[11:59] <clivejo> sometimes these "experiental" changes are getting into the branch and being commited
[12:00] <yofel> always read the git diff output before committing
[12:00] <clivejo> Id intended to keep them local
[12:00] <yofel> aah
[12:01] <yofel> you have changes that you only want to keep in your local env
[12:01] <yofel> the thing intended for managing that would be git stash
[12:01] <clivejo> well for example I just pasted in the files here - http://anonscm.debian.org/cgit/pkg-kde/frameworks/kio.git/diff/debian/libkf5kiogui5.install?h=kubuntu_unstable&id=0e3e08096a4ead8b06a8610277d5f17ceb21d184
[12:01] <clivejo> but then changed it locally and build it
[12:02] <clivejo> but it seems to have take my "experimental" changes and commited them
[12:02] <yofel> nothing ever gets committed without you running git commit
[12:03] <yofel> so please explain a bit more detailed what you actually did
[12:03] <clivejo> I use git gui to commit
[12:03] <clivejo> I stage and commit them in git gui
[12:03] <yofel> then you need to be careful about what you stage..
[12:04] <clivejo> then push using git push origin kubuntu_unstable
[12:05] <clivejo> I stage the final version, but sometimes it only stages changes I made a while back
[12:05] <clivejo> its a bit crazy
[12:05] <yofel> well, I haven't used git gui in a long time, so I can't help you with that
[12:06] <yofel> but it's probably a good idea if you run git diff before pushing
[12:06] <yofel> + git status
[12:06] <yofel> just to be sure that what you're pushing is what you want to push
[12:07] <clivejo> so wildcard usr/lib/*/libKF5KIOGui.so.5.* ?
[12:07] <clivejo> is there a way to remove that kubuntu_stable branch?
[12:08] <yofel> yes
[12:08] <yofel> no
[12:09] <clivejo> Ill do that later, have some work to do outside 
[12:09] <yofel> you are not allowed to delete branches on alioth
[12:13] <apol> can somebody take a look at this bug report? https://bugs.kde.org/show_bug.cgi?id=359120
[12:13] <apol> looks like a packaging issue in Kubuntu
[12:16] <shadeslayer> I don't see the log
[12:16] <shadeslayer> ah
[12:16] <shadeslayer> nvm
[12:17] <shadeslayer> installng intel microcode removed packages 0.o
[12:24] <lordievader> Err, wut? Why? What did it remove by the way?
[12:36] <Mirv> FYI I filed FTBFS bug against kblog and ktnef bug #1543093
[13:01] <maxyz> Are you really planning to add a new -dev package in kio for the new favicons thingy?
[13:01] <maxyz> All the other parts are in kio-dev.
[13:03] <blaze> maxyz: i guess no
[13:03] <blaze> clivejo: ^
[13:05] <maxyz> There is a thread about kdeconnect in the list pkg-kde-talk that needs some input from the kubuntu side of things.
[13:05] <BluesKaj> Hey folks
[13:05] <maxyz> And it would be nice is we can consider pkg-kde-talk a list were we can coordinate some things.
[13:12] <blaze> it would be nice to have akonadi-server deps done in a debian way
[13:13] <yofel> there are reasons why mysql is handled the way it is
[13:14] <maxyz> I've recently realized that mysql-server-core was missing in the mysql backend dependencies.
[13:14] <blaze> i know, but still mysql backend is the default one
[13:14] <yofel> unless akonadi learns runtime backend support detection, uninstalling mysql is not an option
[13:16] <maxyz> Also, mysql is the only reasonably supported backend
[13:18] <blaze> hopefully akonadi-nextgen will be ready soon
[13:46] <maxyz> thunderbird works... :)
[13:48] <sitter> maxyz: I am pretty sure the understanding was that all kubuntu people with commit access are to subscribe to pkg-kde-talk so it's more a problem of not reading/answering than not being subscribed (:
[13:54] <maxyz> sitter: Ok, I have an answer in draft, but every time I read I re write it.
[15:04] <sitter> clivejo, yofel: jobs updated. took a bit longer than expected unfortunately
[15:04] <sitter> clivejo: I am pretty sure the job count is broken or something ... notice how the installation count dropped for no apparent reason rather substantially https://wiki.jenkins-ci.org/display/JENKINS/Countjobs+Viewstabbar
[15:04] <clivejo> maxyz: do you have access to delete a branch on alioth?
[15:04] <sitter> I think if you want it back you'll have to file a bug and/or find someone to look into it 
[15:07] <sitter> oh oh, I also ripped out 'discover' to not have confusion there
[15:07] <clivejo> is it plasma-discover now?
[15:09] <sitter> yeah
[15:09] <clivejo> nice :)
[15:12]  * BluesKaj still uses muon
[15:21] <clivejo> yofel: regarding knetwalk, the changelog didnt get staged with my commit
[15:22] <clivejo> I dont understand why this is happening
[15:23] <clivejo> http://paste.ubuntu.com/14993712/
[15:24] <clivejo> how did git-buildpackage-ppa work?
[15:28] <maxyz> clivejo: There is a hook that forbids that, but it can be done, directly or disabling the hook
[15:28] <clivejo> maxyz: apologies, I went a bit crazy over the weekend
[15:29] <maxyz> clivejo: I was planning on updating the hook to forbid the deletion of non merged branches
[15:29] <clivejo> maxyz: for some reason I convinced myself that KCI needed a kubuntu_stable branch to work
[15:30] <clivejo> maxyz: how do you get the information to write a description of a package?
[15:31] <clivejo> for example that kiogui lib, where do you go to find out what it is?
[15:32] <maxyz> clivejo: For libraries the api is usually a good start, the code is in src/gui 1 .h file, so it was easy enough
[15:34] <clivejo> maxyz: https://quickgit.kde.org/?p=kio.git&a=tree&h=b3c4f8d89813c326ecc31ce2f3e8c92901532494&hb=8d016d2950778168a9deb90bd51a1d78f91e7705&f=src%2Fgui
[15:34] <clivejo> where does it say what the lib does?
[15:35] <maxyz> clivejo: The cmakelist lists the source files that are part of the KF5KIOGui library, in this case    faviconrequestjob.cpp
[15:37] <maxyz> The faviconrequestjob.h has a doxygen documentation of the API. which only add a support for faviconrequests. So the name "kiogui" is quite bad.
[15:52] <yofel> clivejo: did you maybe commit but not push? Then git-buildpackage-ppa would work..
[15:53] <clivejo> Im sure I pushed
[15:55] <clivejo> when I do git merge master, if everything goes ok does it autocommit?
[15:56] <clivejo> Merge branch 'master' into kubuntu_xenial_archive that is the automatic generated commit message
[16:13] <sheytan> Guys, can someone tell me how to fix this bug? http://img-9gag-fun.9cache.com/photo/ajA5xwq_460s.jpg
[16:16] <yofel> clivejo: yes
[16:17] <yofel> should also be the commit message for non-automatic merges
[16:17] <clivejo> should I be doing it in two steps?
[16:18] <clivejo> the merge first, commit, then fix the changelog & new release?
[16:20] <clivejo> yofel: why has master got an UNRELEASED in it?
[16:20] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/applications/signon-kwallet-extension.git/tree/debian/changelog
[16:20] <clivejo> line 45
[16:20] <yofel> if you do it like that then it's pointless to split the steps
[16:20] <yofel> merge --no-commit, fix changelog, commit, new release
[16:20] <yofel> is something I tried once. But that's more hassle than it's worth IMO
[16:21] <yofel> looks like we never released it?
[16:21] <clivejo> does that belong in master?
[16:22] <yofel> ah wait master
[16:22] <clivejo> yeah debians master branch
[16:22] <yofel> I guess that was simply merged before we released that. Can probably be removed
[16:22] <yofel> AFTER merging in the new changelog entries
[16:23] <yofel> it's not just us merging in debian, the other way happens too
[16:24] <clivejo> yofel: http://anonscm.debian.org/cgit/pkg-kde/applications/signon-kwallet-extension.git/commit/?h=kubuntu_xenial_archive&id=522030fa0d547ad82834b99f7f17a107f58ccd74
[16:31] <clivejo> I think Im causing more problems than Im fixing with these merges
[16:40] <maxyz> clivejo: I'll fix that in signon-kwallet-extension master branch
[16:41] <clivejo> maxyz: thanks :)
[16:42] <clivejo> maxyz: how do you know which KDE applications have been changed?
[16:42] <clivejo> do you have a script compares the source tarballs or something?
[16:43] <maxyz> clivejo, I check the diff against the previous release tag
[16:43] <clivejo> kde git?
[16:43] <maxyz> I import the tarballs, but kde.git should work.
[16:44] <clivejo> thats clever
[16:45] <clivejo> are you the main KDE packager then?
[16:48] <maxyz> clivejo: for now, yes, I'm trying to replace myself with jenkins or something like that.
[16:49] <clivejo> you cant be replaced!
[16:50] <clivejo> how long have you been packaging?
[16:51] <maxyz> kde, 2 years, or so. Random stuff in Debian, ~10 years.
[16:52] <clivejo> do you have any experience with kolab?
[16:55] <maxyz> At what level? I never used it, but I uploaded some versions of the libs with the help of detrout. heffee works there so he should probably know more about it.
[16:55] <clivejo> Im trying to package it on Launchpad
[16:55] <clivejo> but Im having trouble with the existing packaging
[16:56] <maxyz> I wanted to add the dovecot support to debian some time ago, but I use SOGo, which is ugly, but it works, so it's not really worth the change for me.
[18:58] <BluesKaj> !project neon
[19:00] <genii> BluesKaj: CI now
[19:04] <BluesKaj> genii, yeah, but I read something here the other day about new a project neon
[19:04] <BluesKaj> anew 
[19:05] <acheron88> http://neon.kde.org.uk/
[19:07] <BluesKaj> something about JR announcing it
[19:08] <acheron88> he did at FOSDEM, a week ago on sunday
[19:09] <BluesKaj> it was in the rss feeds https://dot.kde.org/2016/01/30/fosdem-announcing-kde-neon
[19:09] <acheron88> not sure if the video of his talk is there yet?
[19:14] <BluesKaj> asume this a new neon project, separate from the old one
[19:16] <genii> Seems to be no pool/ there
[19:18] <acheron88> genii: the neon repo?
[19:23] <BluesKaj> all this publicity about new plasma desktops but there's is no comprihensive guide for them, for example activities has a whole lot of hype, but I've yet to find any tuts for them that actually help make it work 
[19:23] <genii> Yep
[19:25] <BluesKaj> correction: make them work :-)
[19:26] <acheron88> http://archive.neon.kde.org.uk/unstable/pool/
[19:26] <clivejo> BluesKaj: ask in #kde-neon ?
[19:28] <BluesKaj> looking for a method to assign apps that launch inside anactivity when the activity itself is launched, supposedly there's a method to do that, but the only one i found doesn't do what it claims 
[19:31] <BluesKaj> clivejo, I'm not compaining about neon's apps whatewver they might be, just the activities in plasma 5
[19:32] <clivejo> BluesKaj: I guess my point is that this is Kubuntu development, at the moment we have nothing really to do with Neon and how it operates
[19:34] <lordievader> BluesKaj: It is called KDE Neon, to avoid confusion (a little) with Project Neon.
[19:34] <lordievader> And the video ain't available yet.
[19:34] <BluesKaj> yeah it's only in the sense that KDE/plasma is the Kubuntu desktop
[19:34] <BluesKaj> I'm not bothering with neon , just to clarify :-)
[19:37] <BluesKaj> I have enough desktop freezes happening here of late, I don't need any more
[19:42] <blaze> in a week or so qt5.6rc will arrive, that would be a good sign
[20:13] <clivejo> yofel: would you look at marble please
[20:42] <clivejo> yofel: Debian dropped the epoch in this package http://anonscm.debian.org/cgit/pkg-kde/applications/libkmahjongg.git/commit/?id=f36da2301091ad464370795f81039c7d3291abbd
[20:42] <clivejo> can we rename and do the same?
[22:17] <clivejo> anyone installed kubuntu-desktop on xenial?
[23:05] <valorie> clivejo: I could -- what is the question?
[23:06] <clivejo> does it install?
[23:15] <valorie> I'll start it up and try that
[23:18] <valorie> updating first though
[23:36] <yofel> clivejo: yes, we should do the rename as well
[23:37] <yofel> marble will have to wait for tomorrow
[23:42] <valorie> is the broken installer our problem, or ubuntu's problem?
[23:42] <valorie> someone was asking last night about the daily ISO -- and s/he is among many reporting a broken installer
[23:42] <valorie> we can't release that way...
[23:43] <clivejo> did you install Ubuntu first?
[23:43] <yofel> ours, ubuntu just broke it
[23:44] <yofel> well yeah, but fixing the installer can be done after feature freeze, unless someone really wants to take care of that
[23:44] <clivejo> only two months left :/
[23:44] <clivejo> tick tock
[23:45] <yofel> what 2 months?
[23:45] <yofel> feature freeze is in 1.5 weeks
[23:45] <clivejo> release
[23:46] <clivejo> 16.04?
[23:46] <clivejo> maybe they'll wait til 16.06?
[23:46] <yofel> release yes, but that's not the only milestone we need to pay attention to
[23:46] <yofel> no
[23:48] <clivejo> 16.07?
[23:49] <yofel> now you're just plain delusional :P
[23:49] <valorie> yofel, good point
[23:49] <valorie> having it broken does keep people from testing, though
[23:50] <valorie> darn it, in my xenial upgrade I missed the chance to tell it to use the new configs