[03:09] <ahoneybun> when someone gets around to it can you tell me what is old and out of date other then the screenshots on this page: https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting. I'll be working on it during lunch break tomorrow
[03:09]  * ahoneybun sleeps
[05:13] <ovidiu-florin> ahoneybun: Plasma-desktop
[05:13] <ovidiu-florin> This seems outdated 
[05:17] <ovidiu-florin> ahoneybun: that page is for intermediate to advanced users 
[05:18] <ovidiu-florin> Do we have something for new users? Beginners? Non technical people? 
[09:25] <Riddell> micahg: Mirv: who knows why we have a hardcoded plugin path? https://mail.kde.org/pipermail/plasma-devel/2015-May/041692.html
[09:33]  * mitya57 looks
[09:34] <mitya57> Riddell: we pass '-plugindir "/usr/lib/$(DEB_HOST_MULTIARCH)/qt5/plugins"' to Qt's configure so that *our* own plugins are installed there. But I think that env variable should still work.
[09:35] <mitya57> I.e. in some packages we set QT_PLUGIN_PATH=$(CURDIR)/plugins when running tests, and that seems to work.
[09:35] <mitya57> qtsensors is an examples
[09:36] <mitya57> *example
[09:38] <Mirv> yes, env var should be working, I think it's used in a couple of packages run build time tests
[09:56] <Riddell> sitter: no kubuntu_wily_archive branches for frameworks?
[09:58] <sitter> not created yet
[09:58] <sitter> Riddell: https://github.com/apachelogger/kubuntu-repo-merge
[09:58] <sitter> Riddell: are you doing 5.10
[09:58] <sitter> ?
[09:59] <Riddell> sitter: I was thinking about it
[09:59] <Riddell> should I?
[09:59] <sitter> just asking because of the command :P
[09:59] <sitter> if you are doing 5.10 -> ./merge.rb -o kubuntu_unstable -t kubuntu_wily_archive frameworks
[09:59] <sitter> if not ./merge.rb -o kubuntu_vivid_backports -o kubuntu_vivid_archive -t kubuntu_wily_archive frameworks
[10:00] <sitter> former derives the branch from unstable, latter derives it from vivid_backports or if that doesn't exist from vivid_archive
[10:01] <Riddell> sitter: what about merging in debian's master branch ?
[10:01] <sitter> Riddell: that should happen via CI
[10:02] <Riddell> sitter: does it?
[10:02] <sitter> someone needs to step up and resolve the conflicts
[10:02] <Riddell> sitter: right, so it needs a manual merge first then CI an do it magically?
[10:03] <sitter> depends
[10:04] <sitter> I'd have CI merge into unstable/stable and then land that into a release branch once a new upstream release comes out
[10:04] <sitter> which would be a merge through CI with manual intervention being needed when there is a conflict
[10:05] <sitter> the other option is to use the merge tool to merge master into a release branch (such as kubuntu_wily_archive) and the release branch then gets merged into CI
[10:05] <sitter> there's no real difference between the two as far as work is concerned
[10:05] <sitter> what needs to happen is someone telling me that master or exermpeintal was merged into branch foobar such that I can enable automatic merges using CI moving forward
[10:05] <sitter> so we don't have to do these batch merges anymore
[10:13] <Riddell> sitter: it's not happy with something https://paste.kde.org/pfacotuih
[10:15] <sitter> Oo
[10:15] <sitter> Riddell: did you run bundle install?
[10:15] <Riddell> ah no good point
[10:16] <Riddell> however some documentation saying what this script does would be useful
[10:17] <sitter> Riddell: --help not clear enough?
[10:17] <Riddell> still no luck https://paste.kde.org/p7bjdbcq9
[10:21] <sitter> that makes no sense, bundle gives you exactly the same versions as I have
[10:21] <sitter> Riddell: bundle show git; ruby -v
[10:22] <Riddell> jr@gallus:~/src/frameworks/kubuntu-repo-merge (master)>bundle show git; ruby -v
[10:22] <Riddell> /var/lib/gems/2.1.0/gems/git-1.2.9.1
[10:22] <Riddell> ruby 2.1.2p95 (2014-05-08) [x86_64-linux-gnu]
[10:23] <Riddell> ooh works if I  apt remove ruby-git
[10:23] <Riddell> silly apt package
[10:24] <sitter> I wonder if maybe I should just change the instructions to bundle into the directory
[10:24] <sitter> bundler is really neat. you can basically make it put the dependencies inside the directory itself and then simply call the script through bundler so it always picks the right versions of the gems regardless of whatever else is available in the system
[10:26] <sitter> anyway
[10:26] <sitter> expanded readme a bit
[10:48] <Riddell> pushing wily branches for frameworks
[10:48] <sgclark> morning
[10:53] <Riddell> wow there's lots to merge when merging in debian's master branch
[10:57] <Riddell> sitter: not dealing too well with conflicts? https://paste.kde.org/p3ljhmbvj
[11:00] <sitter> Riddell: go into the repo, merge manually, then run script again
[11:00] <sitter> and push after merge mind you
[11:02] <sitter> the workflow is a bit meh as it cannot pick up where it left off, though tbh the code is mostly meant to end up in some KCI job and resuming is not a thing there ;)
[11:02] <sitter> wgrant: https://answers.launchpad.net/launchpad/+question/267111
[11:03] <Riddell> ug, pesky debian adding in patches without dep3 headers or even changelog entries
[11:03] <Riddell> "New patch: renamed_header"  ug renaming headers?
[11:03] <sitter> >.<
[11:03] <sitter> \o/
[11:04] <sitter> Riddell: it occurs to me that is an upstream bug
[11:05] <sitter> libkf5dnssd-dev: /usr/include/KF5/KDNSSD/dnssd/domainbrowser.h
[11:05] <sitter> so this probably wouldn't ever work -#include <kdnssd/domainbrowser.h>
[11:07] <sitter> incomplete_header probably also should go upstream as it appears to remove headers that do not actually go anywhere because their underlying thingies were removed (such as Solid/AudioInterface)
[11:18] <yossarianuk> hi - found a bug with 'ubuntu-bug' / apport-kde - it crashes 100% of the time in 15.04 if you choose certain options
[11:18] <yossarianuk> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1456579
[11:23] <Riddell> ug more patches in kio with no indication of their origin
[11:23] <Riddell> yossarianuk: I'm pretty sure that's a known bug in pyqt , check release announcement for 15.04, sorry I'm too lacking in energy to investigate
[11:23] <sitter> Riddell: tell maxy to dep3 and upstream ^^
[11:25] <yossarianuk> Riddell: thanks - this appears different to this one (which I also raised) 
[11:25] <yossarianuk> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1437803
[12:04] <BluesKaj> Howdy folks
[12:04] <KDDA> hi BluesKaj
[12:05] <BluesKaj> hi KDDA
[13:02] <Riddell> sitter: pushing kubuntu_wily_archive with merges from master for frameworks
[13:03] <sitter> bummer
[13:03] <sitter> Riddell: you didn't pause integration
[13:03] <Riddell> oh hmm, does that mean I just broke the world?
[13:03] <sitter> http://kci.pangea.pub/ pointless red :'<
[13:04] <sitter> not too bad actually
[13:04] <sitter> the odd thing is
[13:04] <sitter> only part of the repos triggered a build Oo
[13:27] <sitter> ah uh oh
[13:27] <sitter> Riddell: there are some legit build failures
[13:27] <sitter> http://kci.pangea.pub/job/wily_unstable_kwindowsystem/5/console failing patch for example
[13:27] <sitter> I think it'd be good to go through all the red willys
[13:28] <sitter> hm
[13:30] <sitter> Riddell: so the reason not all jobs triggered was because most repos had nothing to push (e.g. ECM's master is from november)
[13:30] <sitter> I am not sure that is correct
[13:30] <sitter> ah
[13:31] <sitter> Riddell: ECM for example still has its changes in the experimental branch
[13:31] <sitter> I think you should talk to maxy about which stuff needs merging
[13:34] <sitter> Mirv, mitya57: since sebas asked me about it ... do we have any plans on getting qtwebengine?
[13:35] <sitter> I understand lisandro isn't too happy with it
[13:35] <Mirv> sitter: no plans. Ubuntu uses Oxide-qt which is also chromium based but with constant security updates.
[13:36] <Mirv> which means there's no pressure on the Unity side of things to get qtwebengine
[13:36] <sitter> hm
[13:37] <sebas> qtwebengine also gets constant security updates, btw (sounded a bit like qtwebengine doesn't while oxide does)
[13:37] <sebas> oxide is entirely tied to Unity though, it's really useless for anything non unity
[13:37] <sebas> I'd personally trust Qt more to maintain a chromium fork in their package
[13:37] <Mirv> sebas: ah, ok. my impression was that at least release wise upstream only releases it when doing 5.x/5.x.x releases, not when CVE:s are filed.
[13:38] <sitter> I trust no one to maintain a fork of anything :P
[13:38] <sebas> Mirv: I doubt that's practical
[13:38] <sebas> sitter: fair enough :)
[13:40] <Mirv> sebas: I'm not that familiar with Oxide myself, but I didn't know it'd be tied to Unity? looking at the build deps at least it seems all standard libraries aside from one armhf-only dependency that's probably not really optimally implemented that way
[13:40] <Mirv> both the library and QML module seem pretty standard too
[13:40] <sebas> Mirv: I tried to build it a few months ago, there's unity specifics everywhere I looked, I gave up eventually
[13:42] <Mirv> sebas: it should be just bzr bd with nothing Unity needed on x86 http://bazaar.launchpad.net/~oxide-developers/oxide/packaging.vivid/view/head:/debian/control
[13:42] <Mirv> they have a funny way of having packaging outside of the main lp:oxide though
[13:42] <sebas> Mirv: yes, I tried to build it on Debian
[13:43] <sebas> it's already a few months back, maybe things have changed, perhaps I don't remember it well enough
[13:43] <Mirv> sebas: ok, interesting that you hit blockers with that list of build deps. although chromium is never fun, I don't want to even look at those ;)
[13:43] <sebas> yes, chromium is horrible to build
[13:44] <sebas> I think the wider usecase of qtwebengine serves us a bit better mid-term
[13:44] <sitter> that makes me wonder whether steam also forked chromium for their inapp browser o_O
[13:44] <sitter> or perhaps they used the gecko
[13:44] <sebas> or webkit
[13:44] <swizgard> hi. what is the best place to start reading about compiling/packaging kdepim?
[13:44] <sitter> someone should make a gecko fork for qt
[13:45] <sitter> swizgard: google. unless you can ask a more concrete question 
[13:46] <sitter> depending on what you want to do you'll want to read up on general debian packaging and using cmake at the very least
[13:47] <swizgard> sitter: i'm suffering from a bug in how kdepim handles recurrence-ids in ics-files and i want to see if i can make some crude fixes to investigate the problem further
[13:48] <swizgard> and then i want to run my own package until fixes in master trickle down to kubuntu stable
[13:49] <sitter> swizgard: http://paste.ubuntu.com/11225592/
[13:50] <swizgard> ok. but when i want to pull in git master it gets complicated, doesn't it?
[13:50] <sitter> assuming you simply want to create or apply a patch (which is what I would suggest) you want to read up on a tool called 'quilt' and possibly on the general subject of 'dpkg-source patches'
[13:50] <Mirv> sitter: well there's Jolla's https://github.com/tmeshkova/qtmozembed ...
[13:51] <sitter> swizgard: yeah, with master in the picture it gets lots more complicated
[13:51] <swizgard> ok. then maybe i will leave that for now (-: thank you!
[13:51] <sitter> swizgard: general outline is clone -> copy debian/ from existing package -> use a tool called dch to manipulate the changelog -> use that dpkg-buildpackage line I pasted to build binaries
[13:52] <sitter> depending on how far diverged master it this can be all that is necessary or but the beginning
[13:52] <sitter> swizgard: I would probably suggest that you find the exact commit that fixes your problem and import it as a single patch into the packaging
[13:53] <sitter> this would then also allow the change to be applied to official the official packages
[13:53] <sitter> Mirv: oh my xD
[13:53] <swizgard> thank you again (-:
[14:03] <Mirv> sebas: I tried to build the wily proposed Oxide in Debian. I don't see any Unity dependencies, and it starts the build, but I'm hitting some python problem. on sid.
[14:04] <Mirv> anyway if someone wants to play with it chrisccoulson on #ubuntu-devel can help understanding what's needed on Debian
[14:04] <Mirv> since I noticed it, I'll file a bug against Oxide to not use the transitional qml module packages, Debian already dropped them while we carry them until 16.04 LTS
[14:05]  * sitter still would like something better to handle qml dependencies :|
[14:10] <sebas> Mirv: thanks for that ... I've moved on by now though, so don't spend too much time on it for my sake
[14:31] <Mirv> yeah, I was just curious
[14:31] <sebas> Mirv: aye :)
[14:35] <BluesKaj> shadeslayer, did you file a bug about dolphin places ? I didn't get the chance to so and I checked this morning and someone already had filed one.
[14:39] <shadeslayer> BluesKaj: didn't you see the bug link from yesterday
[14:39] <shadeslayer> BluesKaj: https://bugs.launchpad.net/hundredpapercuts/+bug/1422469/comments/55
[14:40] <BluesKaj> !bug 347893
[14:41] <shadeslayer> what?
[14:41] <BluesKaj> not launchpad , kde-bugs
[14:41] <shadeslayer> kde bug 347893
[14:41] <BluesKaj> the bot has it wromg
[14:41] <shadeslayer> BluesKaj: there's a fix in vivid-proposed
[14:41] <shadeslayer> please test it out
[14:41] <shadeslayer> and report with results on 1422469
[14:42] <BluesKaj> hmm proposed eh , I'm on Wily already
[14:42] <shadeslayer> sitter: ^^ wasn't pushed to wily right
[14:46] <BluesKaj> I could switch over to the Vivid install and check it out 
[14:46] <shadeslayer> would be nice
[14:46] <BluesKaj> bbiab
[15:08] <sitter> shadeslayer: twas not because I've been ignoring all the notifiers that told me to upload
[15:09] <shadeslayer> :)
[15:14] <BluesKaj> ok what's the proposed ppa url? not finding it on launchpad or anywhere else
[15:16] <BluesKaj> for vivid
[15:35] <sitter> Riddell: please be fixing that frameworks stuff
[15:40] <BluesKaj> actually Wily is performing better wirh plsama5 and 4 integration than Vivid
[17:29] <Etriaph> Riddell: ping
[17:29] <Riddell> hi Etriaph
[17:29] <Etriaph> Riddell: Can I query you with a quick question?
[17:29] <Riddell> you can try
[18:02] <Etriaph> Congratulations to the winners!
[18:04] <KDDA> winners?
[18:07] <Etriaph> KDDA: Council election winners; it's on both the mailing lists.
[18:07] <KDDA> ah
[18:10] <yofel> \o/
[18:12] <Etriaph> So is there any thing else that has to be wrapped up prior to tomorrow with respect to the election?
[18:12] <Etriaph> I can't change the council details on Launchpad, I'm assuming someone with take care of that?
[18:13] <yofel> I just did that
[18:13] <Etriaph> Excellent.  :D
[18:14] <sgclark> congrats winners :)
[18:16] <KDDA> who are the winners?
[18:17] <Etriaph> Rohan, Phillip and Valorie
[18:20]  * genii throws a bunch of confetti in the air and goes to make a fresh pot of coffee
[18:28] <KDDA> what do the council do?
[18:30] <Etriaph> Package furiously?  :D
[18:30] <KDDA> sounds like amzing fun!
[18:31] <sgclark> don't have to develop as council, they make decisions on direction and such
[18:31] <KDDA> is jonathan head of the council?
[18:32] <yofel> not officially, but we treat him as such
[18:32] <sgclark> I think he like a more equal rights heiarchy
[18:32] <KDDA> big chair and a crown ;)
[18:34] <KDDA> I need to book an appointment to get more lessons!
[18:35] <yofel> KDDA: really all we do is approve membership applications and we more or less have the last word in discussions. Most of the time we're invisible
[18:38] <KDDA> how does one package for different distro, say I have a CentOS RPM package, how does that transfer to Ubuntu with its different paths etc?
[18:40] <yofel> the paths shouldn't be different, the biggest issue would be translating the packaging.
[18:40] <yofel> There is "alien" which can attempt that on a binary package if you're desperate
[18:41] <yofel> For sources, you would really have to repackage
[18:42] <yofel> how much work that is depends on how you later build the packages, e.g. launchpad requires pretty much proper debian sources, the opensuse build service can also build debs from a bit simplier packaging
[18:42] <yofel> KDDA: how far did you get with digikam?
[18:43] <KDDA> havent got any further, waiting for another session with Riddell
[18:46] <soee> hiho
[18:48] <BluesKaj> ok gents , what's the proposed ppa url for the dolphin places patch ?
[18:54] <soee> BluesKaj: wasnt it fixed in apps ?
[18:54] <Etriaph> BluesKaj: Check 'Pre-released updates' while configuring software sources in Muon
[18:54] <soee> 15.04.1 maybe ?
[18:54] <Etriaph> soee: It's fixed in 15.04.1
[18:55] <Etriaph> soee: But there was a patch in proposed that didn't work (at least for me)
[18:55] <soee> yeah so wait for 15.04.1 backport :)
[18:55]  * Etriaph nods.
[18:55] <Etriaph> Do we have a timeline on 15.04.1 backport for 15.04?
[18:56] <Etriaph> (out of curiosity)
[18:56] <BluesKaj> yeah I'll wait for the backport. I'm on my Wily HDD atm and don't feel like switching
[18:57] <soee> Etriaph: probably not, packages are ready for Willy
[18:57] <soee> so we need some packager to backport them :)
[18:58] <Etriaph> What volume of information would I need to learn to begin that?
[19:01] <KDDA> how do I test on wily?
[19:16] <soee> KDDA: its in ppa https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/next-stage2/+packages
[19:17] <KDDA> you mean the "Packages in “Kubuntu Next Stage 2 (DON'T USE)”" one?
[19:26] <soee> yes
[19:30] <BluesKaj> KDDA, I changed my sources.list with this: sudo sed -i 's/vivid/wily/g' /etc/apt/sources.list , then update and upgrade. Of course you'll need to backup your data 
[19:31] <KDDA> I have wily installed
[19:31] <soee> i would say: wait for alpha :)
[19:31] <KDDA> I want to learn how to package
[19:31] <soee> Riddell: ^ :)
[19:32] <BluesKaj> that's my method of upgrading to Wily ... it's working fine , just don't use it on a critical pc 
[19:32] <soee> KDDA: i want to tbh
[19:32] <soee> but my time is limited atm
[19:32] <KDDA> BluesKaj: there was an appeal to test KApps
[19:32] <KDDA> but the PPA says do not use
[19:33] <KDDA> in capital letters!
[19:33] <BluesKaj> that's true KDDA , but if you're a brave tester then ignore warnings :-)
[19:34] <KDDA> but its capital letters, thats shouting!
[19:34] <soee> KDDA: those packages that are ready to test must land somewhere
[19:34] <soee> so we are using thise ppas
[19:34] <soee> iv been testing a lot of releases from them
[19:35] <soee> you can always ppa-purge it if you get some critical errors
[19:37] <KDDA> any major bugs so far?
[19:45]  * BluesKaj takes the plunge with ppa:kubuntu-ppa/next-stage2
[20:46] <BluesKaj> well ,so far so good with the ppa:kubuntu-ppa/next-stage2
[20:46] <soee> ;]
[20:48] <ahoneybun> congrats to valorie shadeslayer and yofel 
[20:58] <shadeslayer> ahoneybun: thanks! :)
[20:58] <shadeslayer> ahoneybun: and thanks for running!
[21:00] <yofel> ahoneybun: thanks :)
[21:00] <ahoneybun> np shadeslayer and yofel
[21:01] <yofel> your next chance is in a year, make yourself famous till then ;)
[21:01] <ahoneybun> have anyone of you use a ISO to fix Windows EFI bootloader?
[21:02] <soee> what did just happend ?
[21:06] <yofel> soee: council elections ended
[21:06] <soee> oh and i missed it :(
[21:06] <yofel> soee: nothing changed ;P
[21:06] <soee> anyway congrats to to new council members :)
[21:22] <KDDA> do they get new company cars and benifits?
[21:23] <shadeslayer> I wish
[21:23]  * shadeslayer wants a BMW M4
[21:23] <shadeslayer> the performance model :P
[21:26]  * yofel wants a tesla model X when it's out
[21:28] <KDDA> anyone know why shutdown sometimes fails from within my session?
[21:30] <shadeslayer> yofel: meh @ suv's
[21:30] <shadeslayer> though those gull wing doors :3
[21:31] <yofel> shadeslayer: usually I agree, but that's the only one I could settle wiith ;)
[21:31] <shadeslayer> I'm willing to settle for a Electric DMC 12
[21:31] <shadeslayer> one that goes upto 88 KMPH
[21:31] <yofel> hehehe
[21:33] <shadeslayer> yofel: http://delorean.com/dmcev/
[21:33] <shadeslayer> what a lovely car
[21:33] <yofel> that slogan XD
[21:34] <yofel> just perfect
[21:34] <shadeslayer> xD
[21:35] <shadeslayer> I don't think they're making new chassis for those anymore
[21:35] <shadeslayer> which is sad
[21:35] <shadeslayer> so they only have pre owned ones http://delorean.com/for-sale/
[21:36] <shadeslayer> only slightly unreasonable prices :P
[21:36] <shadeslayer> I was expecting them to be upwards of 60K USD
[21:36] <KDDA> they dont need gas, they need petrol
[21:55] <mparillo> I am running Plasma 5.2.2, with oxygen yellow cursor theme, but otherwise pretty stock Kubuntu. When I mouse down to reveal the panel, my cursor goes black on one laptop (15.04) but not the other (15.10). (1) Can anybody replicate? (2) If so, can anybody guess the component to file a bug report (I assume at bugs.kde.org).
[23:29] <valorie> wow, used Deloreans cost more than my nifty new hybrid Subaru
[23:29] <valorie> also, thank you to all who ran for the Council, and Etriaph for running the election!
[23:41] <Etriaph> yw!
[23:48]  * ahoneybun yells at silly UEFI