[00:32] <ahoneybun> mm so I have to have an phabricator account now?
 thank goodness the CI Bot output is not put in here
 Aaron, if you have a kde identity, you have a phab account
[08:28] <lordievader> Good morning.
[10:53] <yofel> The kdepim users might want to test https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mysql-5.7 (bug 1528583)
[11:05] <sitter> clivejo: http://packaging.neon.kde.org/cgit/plasma/breeze-gtk.git/commit/?h=Neon/unstable&id=94ca3c69b3230c96dedbbe32ebd474437f9a132b
[11:05] <sitter> why are you setting suid?
[11:05] <sitter> why are you doing this at all?
[11:09] <yofel> o.O
[11:23] <Riddell> I think the kubuntu-ci image and kubuntu-plasma5 images here are no longer useful, what do people think to removing them?
[11:23] <Riddell> http://files.kde.org/snapshots/
[11:25] <yofel> with that timestamp: kill it plasma5 is really no longer useful
[11:25] <yofel> the ci image would be nice to bring back eventually, but such an old image is useless
[11:30] <clivejo> sitter: That was an attempt to fix Lintian crying about script not executable.  "clivejo: http://manpages.ubuntu.com/manpages/xenial/man1/dh.1.html in particular you want to read override_dh_fixperms:" 
[11:31] <sitter> you should consult with someone about these things
[11:31] <sitter> that's a nonfix
[11:31] <sitter> firstly because it sets suid which rips a security whole into the system
[11:31] <sitter> secondly because the scripts shouldn't be installed at all
[11:31] <sitter> https://phabricator.kde.org/D1143
[11:32] <clivejo> oh, they are dev files?
[11:32] <sitter> they split the assets svg into multiple pngs for the theme
[11:34] <BluesKaj> Howdy folks
[11:34] <soee> hiho BluesKaj
[11:34] <clivejo> how come they arent in the do not install file
[11:36] <sitter> clivejo: because they are new
[11:36] <sitter> also they do not belong in the do not install file
[11:36] <sitter> this needs to be fixed upstream
[11:37] <BluesKaj> hey soee
[11:39] <BluesKaj> hey clivejo, sitter 
[11:39] <clivejo> sitter: ok, so to fix it rollback the changes I made "git reset --hard 22f2ce9bc8ae9af651807063cb1e04044c97701d" ? 
[11:40] <clivejo> maybe add a lintian override to ignore it and point to upstream bug report?
[11:41] <sitter> clivejo: revert not reset
[11:41] <sitter> and also no override
[11:41] <sitter> you'll simply have to live with the warning until it gets resolved
[11:42] <sitter> there's no point in CIing if you then ignore legit problems :P
[11:56] <clivejo> sitter: the damage was done over 3 commits, do I need to revert them each individually ?  I thought git reset --hard would rollback to Phils commit?
[11:58] <yofel> only on your machine
[11:58] <clivejo> I cant push that state?
[11:59] <yofel> no, you would have to force-push it, which would break every consumer of the repository as the history of the existing branch would change
[12:11] <sitter> clivejo: you only revert the relevant commit you want to revert
[12:12] <sitter> revert really just applies an inverted patch of that commit
[12:12] <clivejo> they are all relevant
[12:13] <clivejo> debuild -S was complaining about 8 spaces
[12:13] <clivejo> when it actually needed to be a tab
[12:14] <clivejo> Ive reverted the 3 commits and rebuilt the package, its uploaded to staging 
[12:22] <clivejo> hi BluesKaj
[12:22] <BluesKaj> hi clivejo
[12:22] <clivejo> sorry about earlier, was in the middle of something and didnt see your greeting 
[12:24] <clivejo> sitter yofel: can you shine some light on this lintian warning "kwin source: dependency-is-not-multi-archified kwin-common depends on libkwin4-effect-builtins1 (multi-arch: no)"
[12:24] <sitter> https://lintian.debian.org/tags/dependency-is-not-multi-archified.html
[12:26] <clivejo> I see JR has this commit in Neon - http://packaging.neon.kde.org/cgit/plasma/kwin.git/commit/?h=Neon/unstable&id=fa27b8bafe8729e2a9543b47d9595a994210a564
[12:26] <BluesKaj> clivejo, np
[12:27] <clivejo> and sitter has wrapped and bloody sorted
[12:41] <clivejo> sitter: ^^ what is wrong with that merger?
[12:41] <clivejo> 'origin/HEAD' did not match any file(s) known to git. ?
[12:43] <clivejo> yofel: what is kubuntu_xenial_mobile ?
[12:43] <sitter> well
[12:43] <sitter> it wants a HEAD but there is none
[12:44] <yofel> clivejo: no idea
[12:44] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/plasma/kwin.git/
[12:44] <yofel> probably something bshah_ is working on
[12:44] <yofel> he was doing some kind of mobile CI IIRC
[12:45] <clivejo> and I moved, deleted the HEAD ?
[13:02] <sitter> clivejo: merger should be good once mgmt_tooling ran
[13:03] <sitter> not entirely sure why the repo has no HEAD ref though
[13:03] <sitter> $ git ls-remote debian:plasma/kwin|grep HEAD
[13:03] <sitter> 4b9c315993b3b33a3a85af3260e429dc9bb23f21        HEAD
[13:03] <sitter> the remote definitely has one
[14:12] <genii> My testing machine is currently doing a full-upgrade from whatever is different since Friday in staging-kdeapplications and staging-plasma, looks like maybe another 5-7 minutes before it's finished
[16:17] <clivejo> oh I do like to be beside the sea side, oh I do like to be beside the sea
[16:26] <marco-parillo> Running today's Xenial upgrades (looks like KDE Frameworks), and it appeared they broke the Application Launcher > Leave > Shutdown sequence. I am trying again in a different VM, but I had to sudo poweroff from the konsole on my other VM.
[16:29] <acheron88> at what point in the sequence did it fail to do anything? 
[16:32] <marco-parillo> After I clicked shutdown (I do not recall if I got the 30-second timer), it gave me a red box with a script error. I just completed the updates in this VM, and will attempt again. I know I get the 30 second timer. This is not a big deal, it has happened to me before on big upgrades, and anybody running a daily build expects some issues..
[16:38] <marco-parillo> This time I shut down cleanly. Maybe one component was still being upgraded.
[16:38] <genii-testing> Some mainstream Ubuntu 16.04 updates just hit, I'll see if that shutdown issue happens here
[16:39] <genii> marco-parillo: Nope, 30 second warn like usual, clean shutdown
[16:39] <marco-parillo> Oh well, thanks. 
[16:40] <genii> Actual hardware here, no VM
[17:08] <yofel> http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160226-xenial.html#kubuntu
[17:08] <yofel> why is nepomuk still a thing in the archive @_@
[18:55] <melodie> hi
[18:55] <melodie> sbeattie just told me to ask for sgclark here? :)
[18:56] <melodie> paste of the words:
[18:56] <melodie> "<sbeattie> melodie: if kubuntu is needed, I'm unsure what the state of kubuntu/xenial is. you might ask sgclark in #kubuntu-devel, as she's been doing a lot of the packaging work for kubuntu."
[19:00] <clivejo> hi melodie
[19:01] <melodie> hi clivejo 
[19:01] <denza242> erm...
[19:01] <denza242> are CI packages for Vivid still broken :x
[19:01] <clivejo> CI for vivid?
[19:01] <denza242> yeah
[19:01] <clivejo> we make those?
[19:02] <melodie> I've got a client who is fond of Kubuntu, and although I'm not too much of a KDE user (except for some of the app suites which I like a lot), I'm trying to get the best info for him
[19:02] <clivejo> melodie: what are you wanting to know?
[19:03] <melodie> two things : if Xenial is now reliable enough to be used in production, and if not, how can I get a good kernel 4.3 or 4.4 for his Skylake brand new processor (new machine, new everything)
[19:03] <denza242> wait no
[19:03] <denza242> not vivid, Wily
[19:04] <clivejo> Xenial is still in devel
[19:04] <clivejo> so shouldnt be used on a production system
[19:04] <clivejo> however saying that, Ive been using Xenial for a while now and had no major problems
[19:05] <melodie> I would not want him to get even minor issues :D
[19:05] <melodie> this would be very bad
[19:06] <clivejo> probably better to wait until release or shortly after it
[19:06] <melodie> for instance, when a panel crashes or if the /var/crash directory has a crash file in it and triggers other crashes
[19:06] <melodie> we install next thursday. can I get the best source for a 4.3 kernel or a 4.4 kernel? :)
[19:07] <melodie> this matters
[19:09] <yofel> If stability matters, you might want to give 14.04 + the HWE stack a try.
[19:09] <yofel> you can get 4.4 on trusty by installing linux-lts-xenial or something similiar
[19:09] <melodie> and not on Wily?
[19:10] <yofel> no, the HWE backports are LTS-only
[19:10] <melodie> do you mean that Trusty is more stable and reliable than Wily can be?
[19:10] <melodie> excuse me yofel what does "HWE" stand for?
[19:11] <melodie> I like your idea... 
[19:11] <yofel> Trusty still runs kde4, which is certainly a lot more tested than plasma5 is. It also doesn't suffer from the partial qt5 application porting
[19:11] <melodie> oh good!
[19:11] <yofel> melodie: HardWare Enablement -> https://wiki.ubuntu.com/Kernel/LTSEnablementStack
[19:12] <melodie> let me look, I wasn't aware about that!
[19:13] <melodie> yofel ok, then later if he is pleased with his 14.04 he can use it at least 2018? (How long does a Kubuntu LTS last ?)
[19:13] <melodie> at least until 2018*
[19:13] <melodie> forgot one word
[19:17] <melodie> yofel I wonder if I could successfully remix a Kubuntu Trusty with the xenial-lts kernel in it (and all updates). I use Customizer, on a remote server… I want to give that a try!
[19:17] <yofel> base OS security support lasts until 2019. The HWE stack I'm not sure as the numbers aren't in the docs yet, but the xenial based one should last a while. The desktop itself will recieve security support until end of the year at least, with possible updates later depending on how much time people have
[19:20] <yofel> making a remix should work fine, 14.04.4 ships with the wily HWE stack out of the box, 14.04.5 will have the xenial one, but that's a couple months away
[19:21] <sbeattie> yofel, melodie: the linux-lts-xenial packages (xenial HWE stack) will be supported for as long as 14.04 is, so until 2019. 
[19:21] <yofel> ah, thanks
[19:22] <melodie> sbeattie beautiful!
[19:23] <melodie> I was reading here : https://fr.wikipedia.org/wiki/Kubuntu too
[19:24] <melodie> sbeattie I'm not sure yet what the HWE stack is, but I'll try to continue reading to find out
[19:25] <sbeattie> HWE == HardWare Enablement; it's intended for this situation, where you have new hardware that is newer than the last LTS release.
[19:31] <melodie> sbeattie and is it only kernel related or does "stack" implies the compilation chain, and firmware free and non free and that kind of packages?
[19:32] <melodie> (I'm French and not fully "in" the English words and kinds of sentences)
[19:37] <melodie> so what sometimes seems obvious to all, isn't always fully obvious to me… 
[19:42] <sbeattie> melodie: no worries. the stack is intended to include things like an X backport as well, but I don't see that for xenial yet.
[19:42] <sbeattie> melodie: it's all rebuilt with the 14.04 toolchain, so as to avoid any conlicting ABI changes.
[19:43] <sbeattie> the linux-firmware package doesn't look to have an lts backport version, but I see that the kernel team does push backported versions into the main linux-firmware package for 14.04, though they haven't done so for xenial yet.
[19:44] <sbeattie> but the changelogs do mention adding/updating for skylake a number of times.
[19:47] <melodie> sbeattie oh? that sounds nice!
[19:47] <melodie> the man will have the 6th version of the Intel Skylake, that's a very very nice processor ! (the one just under the proc for gamers)
[19:47] <melodie> 3.4 Ghz quad core
[19:53] <sbeattie> melodie: obviously, the best way for you to support your user is for your client to purchase one for yourself, too. :)
[19:55] <melodie> sbeattie fortunately I don't have to
[19:55] <melodie> I can't afford the kind of machine he wanted!
[19:55] <melodie> and I don't need it either…
[19:56] <melodie> himself didn't even need a machine that powerful, but he seemed to think he did, and is anxious to have it working the way he wants it to 
[19:56] <melodie> that's to say, super snappy whatever he does (picture editing… :p )
[19:57] <melodie> and this is nice, because he uses Linux/Ubuntu only since many years, and can send me more good clients, and also I'll touch this beautiful computer and see how it looks in his grand screen once done :D
 melodie: obviously, the best way for you to support your user is for your client to purchase one for yourself, too. :) || just realized you said that... that was not part of the contract. XD
[20:11] <melodie> sbeattie just for a minute of pleasure, do you know this one page? http://www.delafond.org/roman_photos/index_en.html
[20:11] <melodie> This is the Linux Photo story
[20:30] <melodie> yofel in Trusty, how to get *now* a kernel 4.3 or 4.4???
[20:36] <mitya57> melodie, there is a 4.4 kernel backport in linux-lts-xenial package: https://launchpad.net/ubuntu/+source/linux-lts-xenial
[20:37] <melodie> hi mitya57 thanks I look
[20:37] <mitya57> (binary package name would be i.e. linux-image-4.4.0-13-generic)
[20:38] <mitya57> that's only in -proposed (probably because it was uploaded only yesterday)
[20:43] <melodie> mitya57 I'm adding " deb http://archive.ubuntu.com/ubuntu/ trusty-proposed restricted main multiverse universe "
[20:44] <melodie> should I do a dist-upgrade with proposed enabled or just install the new 4.4 kernel then? (probably this second option I'd guess?)
[20:45] <mitya57> Just install, if you dist-upgrade you'll get lots of (not yet thoroughly tested) updates which you probably don't want
[20:45] <melodie> there are only linux-lts-xenial-tools and linux-lts-xenial-cloud and the headers, no image?
[20:47] <melodie> or the name isn't the same probably ? " linux-image-4.4.0-13-generic  " I see this one
[20:48] <melodie> argh apt-cache search provides the name, but it does not exist
[20:48] <melodie> E: Package 'linux-lts-xenial-tools' has no installation candidate
[20:49] <melodie> ^^
[20:49]  * soee thinks plasma does not like him :(
[20:52] <melodie> mitya57 what about "linux-signe-image" ? no 4.4.x for it?
[20:52] <melodie> * linux-signed-image *
[20:55] <melodie> oops found it!
[20:55] <melodie> linux-signed-image-4.4.0-13-generic
[20:58]  * clivejo knows firefox doesnt like him
[20:59] <mitya57> I don't know why just linux-image-4.4.0-13-generic isn't there for you (it is in the archive), but -signed should also work.
[21:04] <soee> WoHo: Qt 5.6 Scheduled To Be Released This Week :)
[21:05] <clivejo> who is WoHo?
[21:12] <soee> just woohoo :D 
[21:12] <soee> https://www.youtube.com/watch?v=OhUEbovdM1E
[21:13] <acheron88> mitya57: kernel 4.4.0-13 looks to be in proposed at the moment
[23:30] <melodie> mitya57 I found the 3 packages needed, thanks a lot for your help! now I'm rebuilding Kubuntu Trusty, using customizer and I'll soon know if that is an iso that can boot!
[23:30] <melodie> if it fails, I'll have at least the information to get the right kernel!
[23:30] <melodie> (I mean, after the install will have been done)
[23:36] <clivejo> wow KCI is very behind today, 318 still in the queue
 KCI is always behind lol
[23:38] <clivejo> it sometimes has an hour or two free, but not today!
[23:43] <yofel> I guess scalability of the CI is a todo item next release..
[23:44] <valorie> it seems like all of you three need some time to breathe, and then figure out how to make all of your lives easier
[23:45] <valorie> this scramble has looked exhausting, at least from my view
[23:46] <sgclark> I was suppose to breathe today, but decided blowing up my KDE CI would be much more fun -.-
[23:47] <yofel> well, yeah. Even if it's kind of manageable. Thankfully pitti and Laney have been helping a lot with the proposed migration currently so we're almost green there
[23:47] <sgclark> very cool
[23:47] <sgclark> still have alot to learn there..
[23:47] <sgclark> and everywhere
[23:49] <yofel> cantor/analitza/kalgebra should go through in the next run. The biggest problems are failing autopkgtests in kwin, baloo and kopete
[23:49] <yofel> and me still not understanding how that mind blowing complex ubuntu autopkgtest setup works -.-
[23:49] <sgclark> lol
[23:49] <sgclark> yeah my brain exploded trying to sort that out
[23:50] <sgclark> I will figure it out someday I hope.
[23:51] <yofel> https://lists.ubuntu.com/archives/ubuntu-devel/2015-November/038985.html was the mail that explained it. Except that I either don't understand it or it tries to be helpful but in fact does the opposite
[23:55] <sgclark> oh so it looks like it will use old dependencies in release before proposed? Seems like that (using old build deps) has been our bane this release.
[23:56] <sgclark> debian is one to not bump deps, which hurt us a few builds.
[23:56] <sgclark> though the 3 you list were not necessarily a problem due to that.
[23:56] <yofel> no, a specific test will always use the versions at the time at the first build happened as I understood it. And the version set is specific to the test trigger
[23:57] <yofel> except that I don't understand how britney then associates that to the candidate check
[23:58] <yofel> kwin is an example actually. As you can see that it runs the tests against 2 different versions of plasma-workspace
[23:58] <yofel> *for 2
[23:58] <sgclark> guess I will start by figuring out what a "test trigger" is...
[23:59] <sgclark> that sounds utterly wrong. Why two versions?
[23:59] <yofel> the version that caused the test build - look at e.g. http://autopkgtest.ubuntu.com/packages/p/plasma-workspace/xenial/armhf/