[00:08] <ahoneybun> ovidiu-florin: https://github.com/ahoneybun/kubuntu-manual/issues/1
[00:08] <ahoneybun> :_
[00:08] <ahoneybun> :)
[00:16] <valorie> ahoneybun: why github??????????? I hate it more every day
[00:17] <ahoneybun> valorie: because that's where I put it?
[00:17] <valorie> why not git on launchpad at least?
[00:17] <valorie> I mean, I know lp is a pain
[00:17] <valorie> but 
[00:17] <valorie> github is a closed-source business
[00:19] <ahoneybun> why is it such a huge deal?
[00:19] <ahoneybun> it works fine
[00:19] <ahoneybun> it is on lp, I just need to update it
[00:23] <valorie> well, github isn't Free
[00:23] <valorie> not a huge deal
[00:23] <valorie> but .....
[08:45] <lordievader> Good morning.
[09:30] <nluxton> Hi there - is there a Kubuntu repo browser I can use to look at commit logs and trees?
[09:31] <nluxton> Trying to determine if a particular commit from upstream KDE has been merged already before trying to figure out how/when to get it merged
[09:36] <yofel> nluxton: that depends on the package.. a couple extra packages are in bzr on launchpad owned by ~kubuntu-packagers. KDE applications, plasma and frameworks are in the kubuntu_${release}_archive branch in debian git
[09:37] <yofel> you'll want to look for debian/patches/ folders in the tree
[09:39] <yofel> nluxton: if you run apt-cache showsrc $source, you should see a Vcs-Browser field that should point you to the right location
[09:52] <nluxton> yofel: that's really helpful, thank you!
[10:11] <nluxton> OK, so it looks like this particular fix hasn't been merged yet. Is there a way I can find out if/when this will be merged into the current release as an update?
[10:11] <nluxton> I guess I should ask the package maintainer?
[10:11] <nluxton> (the next question, then, would be how I get an email address for said package maintainer :) )
[10:17] <yofel> nluxton: it would help to know what the package in question is..
[10:18] <yofel> if the package has bugfix releases, you will likely get the fix with that. Otherwise it's up to the maintainer
[10:19] <nluxton> Sorry, it's plasma-workspace
[10:19] <nluxton> I'm pretty much completely new to the way this all works (in terms of process etc)
[10:19] <nluxton> OK, so I could check if the upstream package is set to release a bugfix release?
[10:20] <yofel> right, so bugfix release it is if the version of plasma is still getting those, otherwise an SRU is in order
[10:21] <nluxton> the patch seems to have been applied 4 weeks ago, and the last tag was 5 weeks ago. Sorry, what's an SRU?
[10:21] <yofel> !sru
[10:21] <yofel> is that about plasma 5.4 ?
[10:22] <yofel> regarding the maintainer for plasma-workspace, that's us, so you're at the right place (if IRC is unresponsive feel free to mail kubuntu-devel@lists.ubuntu.com)
[10:23] <nluxton> Yeah, 5.4
[10:23] <nluxton> OK awesome
[10:24] <nluxton> Essentially this commit introduced a bug (https://quickgit.kde.org/?p=plasma-workspace.git&a=commit&h=2870b5e69bf892c3d08df2d8ee11491542e0d796) and this commit fixes it (https://quickgit.kde.org/?p=plasma-workspace.git&a=commit&h=f869daca8244131f6b452e2c15b4dee5903ff768)
[10:25] <nluxton> It breaks my environment which sucks and I have applied the patch manually at the moment to get it working, but would like to know if/when this update will make it into Kubuntu 15.10 updates
[10:25] <yofel> right, so that's part of 5.4.3, which is on our todo list. As we're overloaded as usual I would say that'll take 2-3 weeks to end up in -updates
[10:26] <nluxton> OK cool
[10:27] <nluxton> Is there anything I could do to help? Not necessarily with this specific issue, but in general, to help with the overloaded-ness
[10:27] <nluxton> (I realise that's quite a broad question...!)
[10:29] <yofel> nluxton: plenty! The more readable todo list is at https://trello.com/b/lAVvKdKF/16-04
[10:30] <yofel> best look for an area that you would find fun to work on, then we can see what's to be done and who you should talk to
[10:34] <nluxton> I guess the websites interest me but also packaging (interests me because I know very little about how it's done / what's involved)
[10:35] <nluxton> I've been interested in contributing somehow for a long time but have been reticent, mostly because I don't really know anything about how any of the process works, etc
[10:35] <nluxton> The "getting started" part of it feels a bit overwhelming
[10:38] <nluxton> I can also do some sysadmin stuff - I am a "devops" (is that still a word?) and a lot of what I do at work is both managing server infrastructure and doing things like configuring CI servers, issue trackers, code review tools and so on
[10:38] <yofel> right, best stay around in here to see what's going on, then you'll get a feeling what we're doing. For the website you'll want to talk to ovidiu-florin, packaging would be me and sgclark
[10:38] <yofel> we have a "devop" person in my office here, so it seems so ^^
[10:39] <nluxton> Haha
[10:40] <yofel> talking about CI, we do have our own one for packaging, but that's currently moving so we'll need to set up our own one, every help with that would be appreciated
[10:41] <nluxton> OK
[10:42] <nluxton> I'm not claiming to be an expert, but I do have a bit of experience, so anything I can help with, I'd be glad to
[10:43] <yofel> well, no need to be one. We have people here that started packaging with no packaging experience at all, same in other fields. 
[10:43] <yofel> Most important thing is that you find something that you enjoy working on
[10:43] <nluxton> :)
[10:46] <nluxton> I guess it would be a good idea to look at the mailing list
[10:47] <yofel> right, also make sure to subscribe to it if you plan to stay around (otherwise your mails will end up in the moderation queue, which will add delay)
[10:51] <nluxton> OK I'll do that
[11:20] <yofel> ovidiu-florin: you coming to https://wiki.debian.org/BSP/2015/11/Munich or too short notice?
[12:00] <BluesKaj> Hey all
[12:20] <nluxton> Does anybody know if the "Log notification to file" feature in KDE is broken at the moment? It doesn't seem to work for me. I'm trying to get KDE connect notifications to be logged to a file to display them in my dzen2 bar
[14:43] <clivejo> yofel: ping
[14:43]  * yofel listens to the echo....
[14:43] <clivejo> :)
[14:44] <yofel> ximion: coming to munich?
[14:44] <clivejo> I would like to stage frameworks for xenial, is that ok?
[14:45] <yofel> uhm, well, you can try. But make sure you don't push as I'm not sure what the old tooling does when branches are missing
[14:45] <ximion> yofel: would be nice, but I have to hold a seminar at that very weekend (yes, university is taking weekends now too!)
[14:45] <yofel> eeeeeeh?
[14:45] <yofel> bummer
[14:46]  * ximion currently thinks about attending FOSDEM - still enough time to plan for that ^^
[14:46] <clivejo> yofel: you seem to have created new kubuntu_xenial_archive branches already?
[14:46] <yofel> riight..
[14:46] <yofel> clivejo: I created the ones I needed. probably some missing
[14:47] <clivejo> how so?
[14:47] <yofel> well, when I fixed the autopkgtests, I only pushed the branches that actually had commits
[14:49] <clivejo> so like http://anonscm.debian.org/cgit/pkg-kde/frameworks/extra-cmake-modules.git/ it doesnt have a xenial branch yet?
[14:52] <yofel> yep
[14:53] <yofel> so, what I did initially, was clone all repositories in the same folder. Then I scripted checking out the wily_archive branch, then scripted "checkout -b kubuntu_xenial_archive" for all repositories.
[14:53] <yofel> With that you get correctly set up xenial branches in all repositories. If you then push every repo you should be good to go
[14:55] <clivejo> how did extra-cmake-modules get missed?
[14:55] <yofel> as I said, I didn't make branches if there was no point in making one
[14:56] <yofel> you don't make branches just for the fun of it, because delaying the branch creation makes sure that you get the up-to-date state of wily when you branch off
[14:56] <yofel> you will get errors from the repos that already have the xenial branch, ignore that.
[14:58] <clivejo> I dont understand that.  Is the wily_archive branch not locked now, since its been released?
[14:59] <yofel> no, _archive also covers wily-updates
[15:00] <yofel> unless I misunderstood something?
[15:00] <clivejo> no, Im just slow on the uptake
[15:02] <clivejo> I wanted to make a start on staging frameworks with the old tooling and try fixing any problems  
[15:03] <yofel> well, do it. But as I said, make sure that the branches are correct and that you don't push your first run until you verified that everything's alright
[15:06] <yofel> (remember that the stage script defaults to pushing immediately, so disable that)
[15:09] <mck182___> I have many packages "kept back" with kubuntu ci, is that intended? it's mostly frameworks and plasma
[15:17] <BluesKaj> mck182___, sudo apt dist-upgrade will install them
[15:17] <mck182___> BluesKaj: nope, in fact
[15:17] <mck182___> BluesKaj: https://paste.kde.org/p1lrpm4hr
[15:19] <BluesKaj> mck182___, make sure you update and upgrade first 
[15:19] <mck182___> I did
[15:20] <yofel> wily?
[15:24] <BluesKaj> mck182___, those kept packages need the other packages to be installed first 
[15:38] <yofel> mck182___: "kubuntu-ci/unstable" upgrades fine here with indi and Qt ppa's
[15:42] <sitter> pretty sure you should copy things into the ppa rather than make the ppa depend on other bits
[15:43] <sitter> latter is not communicated to users, so that's some serious vodoo as far as non-devs are concerned xD
[15:43] <yofel> I wonder who added the deps then
[15:43] <sitter> wasn't me
[15:43] <yofel> but yeah, I would assume that qt5.5 would be the source of the mess
[15:44] <sitter> it literally coudl be any member xD
[15:44] <yofel> true
[15:44] <sitter> maybe we should change the control structure
[15:44] <sitter> currently all members are member of kubuntu-ci as with all other teams
[15:44] <sitter> might be wroth revisting that choice :P
[15:45] <sitter> it surely happened with all the best intentions, alas, that doesn't improve upon the situation I fear
[15:45] <yofel> you could limit it to ninjas at least. Might not solve everything, but would sound more appropriate
[15:46]  * yofel wonders why all the teams have random owners..
[15:47] <mck182___> yofel: I see...I sure don't have qt5
[15:47] <mck182___> .5
[15:48] <yofel> mck182___: quickfix: add-apt-repository ppa:canonical-qt5-edgers/backup-qt551
[15:48] <mck182___> ooh
[15:48] <yofel> but we'll copy the packages over too
[15:48] <mck182___> woah, now I have even more packages held back tho
[15:49] <mck182___> fwiw, here's apt-cache policy on one of the held back things https://paste.kde.org/pgowhk9eu
[15:50] <mck182___> all of them have the same thing
[15:52] <mck182___> yofel: does that tell you anything useful?
[15:52] <yofel> not particulary.. well, it tells me the breakage was introduced recently..
[15:53] <yofel> mck182___: the output of apt-get -o debug::pkgproblemresolver=1 dist-upgrade would be handy
[15:54] <mck182___> yofel: https://paste.kde.org/prurloqod
[15:54] <mck182___> though now dist-upgrade wants to remove only kwin-wayland \o/
[15:54] <mck182___> progress
[15:54] <yofel> right, sounds like a missing rebuild
[15:55] <yofel> well, kwin be FTBFS, so hardly surprising
[16:14] <shadeslayer> yofel: FWIW upstream says 1514491 is unfixable on our end
[16:16] <yofel> shadeslayer: all of it? The description says that the xubuntu folks did *something* at least
[16:16] <yofel> the button order is probably fixed though
[16:17] <yofel> talking about xubuntu, we need to burn orion with fire
[16:23] <mck182___> mhh...the plasma-workspace build is one month old anyway :O
[16:24] <shadeslayer> yofel: I think most of it
[16:24] <shadeslayer> since GTK3+ is all CSS
[16:25] <yofel> meh, well. I still haven't seen gtk3+ with breeze, so I'll leave it open for now
[16:32] <mck182___> is the plasma-workspace build failure cause of the missing qt5?
[16:33] <yofel> the last successful plasma-workspace build supposedly was 2 days ago
[16:34] <yofel> after that there seem to be a lot of dependency issues, haven't looked at it yet
[16:35] <mck182___> yofel: really? apt shows me the last available as 4:5.4.2+git20151014.0237+15.10-0
[16:36] <mck182___> which is almost a month ago
[16:36] <yofel> which ppa is that?
[16:36] <mck182___> kubuntu-ci-unstable
[16:36] <mck182___> for wily
[16:36] <yofel> *facepalm* I was looking at the wrong page
[16:37] <yofel> right, 29 days ago
[16:37] <yofel> kscreenlocker is missing in the build
[16:39] <yofel> shadeslayer: you packaged that for DCI?
[16:39] <shadeslayer> yofel: I haven't yet
[16:39] <shadeslayer> I pushed a initial thing
[16:40] <yofel> ok
[16:40] <shadeslayer> debian:plasma/kscreenlocker
[16:41] <yofel> right, I found the dummy
[16:43] <shadeslayer> dummy?
[16:44] <yofel> well, your packaging so far without descriptions and whatever
[16:44] <shadeslayer> ah yeah :P
[16:45] <mck182___> do you guys think the plasma-workspace could be rebuilt soon? I don't mean to be pushy but I just need it for work
[16:45] <mck182___> and screenshots for the release announcement ^^
[17:06] <yofel> properly, probably not. But I guess we can just upload a snaphost of rohans packaging and live off that
[17:18] <clivejo> yofel: https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/ is master the old automation tools?
[17:18] <yofel> yes
[17:18] <yofel> it's also the "current" until we've merged the new ones
[17:19] <clivejo> are the ng ones ready to try yet?
[17:43] <yofel> clivejo: not on the branch on lp
[17:43] <yofel> the github repo probably has the up-to-date branch for that
[18:04] <Riddell> angry e-mail du jour https://paste.kde.org/pwem72uq9
[18:12] <sgclark> Kubuntu updates firmware now? my we have grown
[18:13] <Riddell> it's done by the driver-manager thing same as nvidia drivers
[18:13] <sgclark> yes my desktop is fubar atm. Untimely reboot on unstable CI = bad
[18:16] <sgclark> driver manager that no one claims maintainership? lovely.
[18:19] <Riddell> in theory ubuntu foundations team maintain the actual installation of bits
[18:19] <Riddell> but y'know, they also maintain usb-creator
[18:28] <mamarley> Riddell: They are probably referencing the intel-microcode/iucode-tool packages, which together update the microcode of the CPU.  However, such microcode updates are transient and disappear with a reboot, so if I were a betting person I would bet that his fan issues are unrelated.
[18:35] <sgclark> so I am reading this Kubuntu Brasil email. We were seriously expected to fix that load of extremely vague issues within less than 24 hours? Something tells me even if by miracle we succeeded there, it was going to be revoked.
[18:36] <sgclark> on a Sunday no less. Total setup for failure. gosh people are great.
[18:42] <yofel> something is very wrong in the power management stack in wily. My notebooks randomly wake up from sleep by themselves
[18:43] <yofel> very, VERY bad if they're in a bag when they do that
[18:43] <sgclark> ouch
[18:44] <sgclark> well rebooting back to vivid as I currently have a non functional plasmashell and it makes for getting anything done difficult.
[19:14] <sgclark> yofel: were you able to deal with kscreenlocker? I have to setup a wily chroot before I can be productive.
[19:17] <yofel> no, I'm trying to figure out how to easily keep out packageset updated
[19:18] <sgclark> ahh. very useful.
[19:19] <sgclark> I seem to be having a bad day, not sure I will get it done either.
[19:32] <sgclark> sitter: I have created kubuntu_unstable for kscreenlocker. Any other magic needed to get this on the CI?
[19:41] <sick_rimmit> Hi people
[19:42] <clivejo> hi sick_rimmit
[19:42] <sick_rimmit> Hi clivejo
[19:43] <clivejo> how are you sick_rimmit?
[19:48] <clivejo> bad network connection it seems
[19:49] <sgclark> hiyas
[21:15] <shadeslayer> sgclark: fyi you can book at motel one without paying anything upfront right now
[21:15] <shadeslayer> and you can cancel for free till the 20th
[21:17] <sgclark> shadeslayer: ok thanks
[21:18] <pursuivant> muon (master) v5.4.2-177-g6e3f1aa * Matthias Klumpp:  (7 files in 2 dirs)
[21:18] <pursuivant> trivial: Drop some code only used by Discover
[21:18] <pursuivant> http://commits.kde.org/muon/6e3f1aa391fc0d3c6f075fd13ca3be65c362a44e
[21:46] <pursuivant> muon (master) v5.4.2-178-g528a6b7 * Matthias Klumpp: CMakeLists.txt
[21:46] <pursuivant> Drop dead option from CMakeLists
[21:46] <pursuivant> http://commits.kde.org/muon/528a6b782c2ffc5d3d00e44b8a99a63708cb07c8
[21:58] <valorie> Riddell: I used to get notice of that update in 15.04 all the time as well
[21:58] <valorie> it never seemed to do anything though