[00:04] <soee> uhm KTorrent looks strange, not the breeze/qt look
[00:11] <valorie> soee: I don't think the kf5 port of ktorrent has been released
[00:12] <soee> valorie: but still few days ago the interface was ike in other apps now it is something different
[00:12] <valorie> mine looks breezish though
[00:12] <valorie> ah, I've not upgraded this laptop to 5.6.4 yet
[00:12] <soee> :]
[00:12] <valorie> figured I would test backports once they are ready
[00:12] <soee> please do, one more test:)
[00:13] <valorie> I already did on the other laptop -- oh, and is xenial ready to test?
[00:13] <soee> i think what we have now is pretty much what will land in backports
[00:13] <soee> valorie: yes
[00:13] <valorie> just plasma-staging ppa?
[00:14] <soee> well in staging-frameworks there are some updated packages than what we have in staging-plasma and clivejo suggest to add both ppas
[00:14] <valorie> ah
[00:14] <valorie> perhaps after dinner
[00:14] <soee> only problem i found is that kde-spectacle from staging-plasma installs fine, while the one from staging-frameworks not 
[00:14] <valorie> I'm updating some Techbase pages right now
[00:15] <valorie> and would like to finish
[00:16] <sgclark> kactivities-stats rejected everything else seems to be uploading to archive fine
[00:16] <sgclark> he will have to get that one sponsored
[00:17] <sgclark> I will pop a note to devel list
[00:18] <soee> <3
[00:28] <sgclark> was plasma done? maybe I will wait till morning
 Yes
 That is why I asked about apps earlier :)
 Only they left from flat we have now to be packaged
[01:06] <valorie> if the above are the only failures we have, that looks good to me
[01:20] <sgclark> most of those are due to a failure in the CI code itself. It has to do with moving from debian git that uses namespaces and launchpad we do not. 
[01:21] <sgclark> Perhaps some day I will sort out how to fix, ruby is new to me.
[01:21] <sgclark> and sheer lack of time to fiddle with it.
[01:22] <valorie> I see
[01:23] <valorie> I wonder what is different from the above failures from all the rest you already fixed?
[01:23] <sgclark> only stable is affected
[01:24] <sgclark> Harald wrote the code to fetch tarballs using namespaces or some such. The documentation of the code is umm lacking. but it boils down to those are trying to build master with packaging for release...
[01:25] <sgclark> and to save my life I could not get the yaml file to load with coded in namespaces. But I stopped trying after the step back.
[01:26] <valorie> one of these days it might sound fun
[01:26] <valorie> :-)
[01:26]  * valorie crosses fingers
[01:26] <sgclark> he had the code ssh into debian git to get namespace + package and launchpad does not support ssh logins
[01:26] <sgclark> so I tried doing it in the yaml project file and only it barfs.
[01:27] <sgclark> but I did not try for very long. maybe after my life is sorted I will look at it again.
[01:27]  * sgclark it is so easy to fall back into old habits just helping with bits here and there.
[01:28] <valorie> is today your first day of coding for Outreachy?
[01:28] <sgclark> No, that is Monday. I am quickly trying to get out my new DSL for KDE CI
[01:29] <valorie> great!
[01:29] <sgclark> my other hat..
[01:31] <DarinMiller> Hi sgclark and valorie o/
[01:32] <sgclark> I have a bad feeling frameworks will not build until that package gets sponsered :(
[01:32] <sgclark> hi DarinMiller!
[01:33] <sgclark> sponsored ugh. No idea why I insist on butchering that word.
[01:33] <DarinMiller> sgclark: can you point me to one of the scripts that not working.  I don't even know where to look for such an animal but I am curious how extensive they are.  Also, I don't know ruby either....
[01:33] <sgclark> for the CI?
[01:34] <sgclark> or for packaging?
[01:34] <sgclark> for the CI is a problem,, because I am having issue finding the point of failure. they have crammed code into one repo for 5 different CIs :(
[01:34] <DarinMiller> Sure. How many places do these scripts exists.
[01:35] <DarinMiller> ?\
[01:35] <sgclark> lol
[01:35] <valorie> hi DarinMiller
[01:36]  * valorie listens and learns
[01:36] <sgclark> DarinMiller: our automation tools https://code.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation though not sure if stuff is "broken"
[01:36] <sgclark> oh I should push my fix oops
[01:37] <sgclark> CI code I had to fork because I have no commit access to blue-systems https://github.com/ScarlettGatelyClark/pangea-tooling
[01:38] <sgclark> and keep in mind that holds code for 5 other CI systems along with kubuntu and it seems to all be integrated and scary stuff.
[01:39] <sgclark> I was starting to sort it all out before my life got crazy
[01:39] <DarinMiller> wow, ask for a drink of water and get a firehose....
[01:39] <sgclark> and we have a kubuntu-dev-tools somewhere around here
[01:39] <DarinMiller> :)
[01:39] <sgclark> lol
[01:40] <sgclark> ahh yes bzr only https://code.launchpad.net/~kubuntu-packagers/kubuntu-dev-tools/trunk
[01:40] <sgclark> I think that is it..
[01:41] <sgclark> kubuntu-automation is used the most for packaging
[01:41] <DarinMiller> wow and just wow.  
[01:44] <valorie> some documentation on that stuff might be useful
[01:44] <sgclark> yes I use the README everytime haha
[01:45] <sgclark> most of it is still useful
[01:45] <sgclark> if it is not in the packaging docs, it should be
[01:46] <valorie> nothing specific about that stuff
[01:46] <valorie> otoh, having things in more than one place means that part is always out-of-date
[01:46] <sgclark> mmhmm
[01:46] <valorie> link to the README would be useful
[01:47] <valorie> and a lil outline or so
[08:00] <yofel> sgclark: you should be able to get the repository names from the launchpad API, like I did in the script that moved the repositories. Dunno how to do that in ruby though
[10:37] <sitter> clivejo: is kacitvites-stats up yet?
[10:58] <BluesKaj> Hiyas all
[11:14] <sgclark> yofel: ok ty
[11:16] <sgclark> sitter if by up you mean in proposed? no he needs a sponsor I cannot upload NEW (kactivities-stats)
[11:21] <sitter> someone get me a dsc then :P
[11:21] <sitter> sgclark: ^ plz 
[11:22] <sgclark> sitter: sure
[11:26] <sitter>   Uploading kactivities-stats_5.22.0-0ubuntu1_source.changes: done.
[11:26] <sitter> Successfully uploaded packages.
[11:26] <sgclark> thanks sitter
[11:27] <soee> ~.~
[11:29] <soee> yofel: what is the diff in kde-spectacle in staging-frameworks and staging-plasma ?
[11:30] <yofel> soee: none
[11:31] <soee> yofel: http://paste.ubuntu.com/16488484/
[11:31] <sitter> in NEW now [ubuntu/yakkety-proposed] kactivities-stats 5.22.0-0ubuntu1 (New)
[11:34] <yofel> soee: hm, that built with libkf5screen6, weird
[11:35] <yofel> SIGH
[11:35] <yofel> I forgot that lib*KF5*screen is part of plasma
[11:35] <yofel> soee: uploading another set just for plasma
[11:37] <soee> :D
[11:38] <soee> btw. yofel do we have green light from your side to put P 5.6.4 with FW 5.22 in backports ppa?
[11:39] <yofel> as soon as someone has put it into backports landing and we have a verified working set of packages that we can sync into backports
[11:40] <yofel> spectacle up
[11:40] <soee> thank you
[11:41]  * yofel wonders if he could wire up a transition map for landing...
[11:42]  * sgclark wonders what a transition map is
[11:43]  * soee scratching his head ..
[11:43] <yofel> sgclark: a transition tracker page like http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.60.html
[11:43] <yofel> would require me to hack together package lists that "ben" can read and use the debian release team's auto-transitioner to detect whether kscreen is our only issue
[11:44] <yofel> I did that in the past already, need to remember where that's lying around...
[11:44] <sgclark> ah that indeed looks useful
[11:45] <yofel> for the primary archive, our release team accepts .ben files to add to http://people.canonical.com/~ubuntu-archive/transitions/
[11:45] <yofel> those are really just 3 lines with the "Parameters" you see on the page
[11:46] <soee> yofel: you uploade kde-spectacle to staging-plasma not to staging-frameworks ?
[11:46] <yofel> which are just definitions on which packages have "bad" dependencies (here: libkf5screen6), and "good" ones (here: libkf5screen7)
[11:46] <yofel> soee: yes, after all, libkscreen is in *plasma*
[11:46] <yofel> an upload to frameworks will build with libkscreen 5.5, which isn't what we need
[11:47] <soee> why then kde-spectacle is in frameworks ppa ?
[11:47] <yofel> because I uploaded to the wrong ppa?
[11:47] <soee> ahh :D
[11:47] <yofel> yes, the answer is as simple as that :P
[11:48] <soee> well than the one from plasma ppa installed fine before, the one from frameworks did not
[11:48] <yofel> right
[11:49] <soee> yofel: and can you remove the one in staging-frameworks ?
[11:49] <yofel> that's why once stuff is ~ok on the status pages, it should be moved to -landing, so we have ONE environment to QA, not multiple ones
[11:49] <yofel> soee: the new one will have a higher version, so it doesn't matter. And I'm too lazy for that
[11:49] <yofel> soee: come join the ninjas and you can do that yourself :P
[11:51] <soee> :D
[11:53] <yofel> soee: FWIW, also apply for membership, then you can edit the QA website yourself :P
[11:54] <yofel> I updated some of the links
[11:59] <yofel> https://packages.debian.org/experimental/irssi-plugin-quassel <3
 Soee +1
[13:05]  * clivejo straightens sitter's dickie-bow and pats him on the head
[13:05] <clivejo> thanks for the upload :)
[13:07]  * clivejo offers sitter a mini bar of Kinder chocolate
[13:13] <clivejo> anyone up for fixing a few KCI issues?
[13:37] <clivejo> sgclark:  ppc64el build of kdnssd-kf5 5.22.0-0ubuntu1 in ubuntu yakkety PROPOSED failed
[13:37] <clivejo> but I cant see why it failed?
[13:37] <clivejo> https://launchpadlibrarian.net/260089244/buildlog_ubuntu-yakkety-ppc64el.kdnssd-kf5_5.22.0-0ubuntu1_BUILDING.txt.gz
[13:47] <sgclark> um I: Built successfully youo got me lol
[13:47] <sgclark> yofel: ^
[13:48] <yofel> clivejo: probably a dep resolution issue and someone already retried it
[13:49] <yofel> or something like that
[13:49] <sgclark> I do have the retry going
[14:08] <sitter> yofel: needs mergy I guess, also note comment plz https://code.launchpad.net/~timo-jyrinki/ubuntu-seeds/kubuntu.yakkety.stop_depending_on_transitional_packages/+merge/295073
[14:10] <yofel> sitter: bloody workaround for knewstuff or how that's called -installer not being able to pull in required QML packages at runtime
[14:11]  * yofel still sees no merge button on LP - bummer
[14:12] <yofel> debian people have a knack for good bug titles *g* (debian 824059)
[14:13] <clivejo> Elf and Safety issue there!
[14:13] <clivejo> that should be upgraded to category bright and flashing red
[14:16] <sitter> yofel: ah yes. someone should get kubuntu to package and then get ximion on making packagekit able to qml and then make knewstuff packagekit away ^^
[14:17] <sitter> (actually the packagekit part might entirely be optional since knewstuff just needs a simple install-request api)
[14:17] <yofel> there's another issue
[14:17] <yofel> the classic one
[14:17] <yofel> !info packagekit
[14:17] <yofel> wheee
[14:18] <yofel> why am I working on this distro again?
[14:18] <clivejo> you <3 the community!
[14:19] <sitter> *hachooo* packagekit:amd64/xenial 1.1.0-2+16.04+build3 uptodate
[14:22] <sgclark> dunno, even retiring seems an impossible task.
[14:26] <yofel> IKR
[14:26] <sitter> are you peeps using the install checker magic?
[14:26] <sitter> http://kci.pangea.pub/job/mgmt_daily_promotion_yakkety_unstable/
[14:26] <sitter> or have you given up on that
[14:26] <sitter> because I am currently refactoring this to support more generic repos (i.e. other than PPAs) and I am wondering if it is even worth aiming for backwards compatibility with the existing KCI code there
[14:32] <sgclark> sitter: did you see my kci comments? my internet seems cranky lately
[14:33] <sitter> sgclark: I did not
[14:33] <sgclark> blech
[14:34] <sgclark> in short it is broken due to stable trying to build master for stable packaging. I am not sure I will have time for KCI depending how my future goes.
[14:35] <clivejo> Id like to learn it, if someone has the time to teach me and be patient!
[14:38] <sgclark> Well start by learning Ruby.
[14:38] <sgclark> I am not the one to teach that though, I did not write the magic.
[14:39] <sgclark> and please do not burn yourself out clivejo...
[14:39] <sitter> sgclark: you need to add suitable override rules https://github.com/ScarlettGatelyClark/pangea-tooling/blob/master/ci-tooling/data/overrides/base.yaml
[14:40] <clivejo> sgclark: when Im in the mood I enjoy learning
[14:40] <sitter> e.g. '*{git.launchpad.net,debian.org,packaging.neon}*/plasma/*': https://github.com/ScarlettGatelyClark/pangea-tooling/blob/master/ci-tooling/data/overrides/base.yaml#L10
[14:40] <clivejo> I learn by doing
[14:40] <sitter> except I see you can't map via /plasma/ since launchpad has no subdirs, so you probably have to expand that rule somehow
[14:41] <sgclark> right
[15:31] <acheron88> clivejo: seems like the 4.4.0-23.41 kernel just copied to yakkety-proposed should have the patch to fix kernel module building
[15:32] <clivejo> Im happy enough on 4.6 :)
[15:32]  * soee waits for Kernel + X + Nvidia fixes = no more tearing  :(
[15:33] <clivejo> soee could be waiting a long time
[15:33] <soee> true :|
[15:33] <acheron88> good. seems OK here as well. just thought I would mention it in case
[15:35] <clivejo> no, thanks for mentioning it :)
[15:36] <acheron88> export __GL_YIELD="USLEEP" in /etc/profile.d/Tearing.sh gets rid of all tearing on this nvidia card
[15:37] <clivejo> acheron88: what card have you?
[15:37] <acheron88> 705, which is pretty rubbish
 This won't help. The problem is with hybrid graphics
[15:40] <acheron88> I always avoid anything with hybrid graphics. too many horror stories trying to get those to work well
[15:47] <soee> well the idea behind them was to save power when you dont need better gpu
[15:48] <BluesKaj> many gamers buying laptops , hence the hybrid gpus 
[15:51] <soee> well there are some fixes in Kernel 4.5 and already but also some merges are pending in X and also nvidia driver has to be updated
[15:51] <acheron88> yeah, I know the point. just not for me.
[15:53] <acheron88> soee: if all that results in no need to apply a fix each time, then great :)
[15:54] <soee> well this problem is known since when ? 2014 :D
[15:55] <soee> no idea when it will get fixed 
[15:55] <soee> and this is pretty sad :?
[15:55] <soee> clivejo: ping
[15:57] <clivejo> soee: pong
[15:57] <soee> clivejo: are you able to move  Plasma 5.6.4 and Frameworks 5.22 to landing ppa 
[15:57] <soee> ?
[15:58] <soee> so here https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports-landing
[15:58] <soee> yofel: shall the backports landing pap be cleared first ?
[15:58] <BluesKaj> too bad about bumblebee has such hit and miss support , it used to work quite well a couple of yrs ago
[15:58] <yofel> I would recommend that
[15:59]  * yofel has intel+nvidia optimus in his notebook
[15:59] <yofel> running purely on intel lately. But it's funny that both intel and nvidia run linux a lot better than windows(10)
[15:59] <BluesKaj> oops scuse the poor grammar there 
[16:00] <soee> yofel: yes but you have this tearing problem that hurts eyes 
[16:00] <yofel> either the windows implementation sucks, or the intel windows driver sucks, something of that
[16:00] <yofel> soee: with nvidia? Yes, although that never bothered me that much - or rather I didn't really see much of it
[16:01] <yofel> I switched to intel because the nvidia driver had really bad performance for me lately. To the point that intel feels faster...
[16:01] <soee> yofel: yes, if i play some HD movies, play games etc. the problems is pretty common
[16:01] <soee> yofel: can you flush backports landing please ? :)
[16:01] <BluesKaj> yofel:  well you obviously know how to set it up properly compared to those poor souls who bought a hybrid system without considering linux usage
[16:02] <yofel> what always annoyed me is the GPU memory content garbage after resume from suspend...
[16:02] <yofel> soee: might as well
[16:02] <yofel> clivejo: I'll also sync FW and plasma while at it, screm if that's a bad idea
[16:03] <yofel> *scream
[16:03] <clivejo> archive sync?
[16:04] <yofel> staging -> b-l
[16:04] <clivejo> is there a way to archive sync automatically?
[16:05] <soee> yofel: i can then try to call for some testers on G+
[16:05] <yofel> I use a script..
[16:05] <soee> when we have this in landing
[16:18] <yofel> copy done, I'll try to figure out the transition foo later so we can continue the QA
[16:20] <soee> ?
[16:21] <yofel> automatic way to detect what happened to spectacle
[16:22] <yofel> bbl
[16:42] <soee> yofel: but is it ready to tet what we have i landing ?
[18:05] <yofel> soee: that is what was in frameworks and plasma staging, I haven't checked anything more yet
[18:22] <dbacc> hey! Is there a difference between installing Ubuntu and apt-get install kubuntu-full and installing Kubuntu regarding configurations and files (concerning pure kde packages)?
[18:54] <Guest64779> soee 5.6.4 is ready to test?
[18:55] <Guest64779> opps
[18:55] <ahoneybun> there we go
[18:56] <soee> ahoneybun: yes
[18:56] <ahoneybun> so I can download from the staging ppa with no big breaks?
[18:56] <soee> no staging
[18:57] <soee> use backports landing: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports-landing
[18:57]  * ahoneybun is confused 
[18:57] <ahoneybun> I have plasma staging atm
[18:57] <soee> well than you have pretty much the same :)
[18:57] <ahoneybun> that is weird 
[18:57] <ahoneybun> weird naming
[18:57] <soee> why ?
[18:58] <ahoneybun> staging should be very early testing
[18:58] <ahoneybun> a landing should be the FINAL bui;ld
[18:58] <ahoneybun> with bugs worked out mostly
[18:59] <soee> yes and we fixed all issues in staging so packages were moved to landing as the one that are candidates to land in backports
[19:02] <ahoneybun> mm
[19:02] <ahoneybun> so should I remove the ppa then add landing?
[19:02] <ahoneybun> soee ^
[19:03] <soee> yes, but if you installed from staging you probably wont see updates :)
[19:03] <clivejo> ahoneybun: are you having problems?
[19:03] <ahoneybun> not really
[19:03] <ahoneybun> panel disappeared when I disconnected from a projecter
[19:05] <clivejo> dont leave PPA's active
[19:05] <clivejo> always update and disable them
[19:05] <ahoneybun> I'm removing the staging one
[19:05] <clivejo> especially the staging ones
[19:06] <acheron88> backports-landing now enabled and upgraded successfully on my main machine
[19:06]  * clivejo wonders if sgclark got around to uploading plasma 5.6.4 to yakkety
[19:06] <acheron88> decided what the hell
[19:06] <clivejo> acheron88: any issues?
[19:07] <soee> clivejo: she uploaded all except kactivities-stats i think, and sitter did it earlier today
[19:07] <acheron88> none so far, but only did it a few mins ago
[19:07] <acheron88> plasma/splash certainly loads noticeably quicker
[19:07] <soee> :)
[19:07] <ahoneybun> same here
[19:14] <ahoneybun> well plasma started!
[19:14] <ahoneybun> Plasma 5.6.4
[19:14] <ahoneybun> Frameworks 5.22
[19:14] <soee> ;]
[19:20] <sgclark> clivejo: no I did not bother as frameworks was not done, I assumed plamsa depended on it
[19:21] <sgclark> clivejo: is frameworks all built?
[19:25] <ahoneybun> sgclark what was the latest?
[19:25] <ahoneybun> 5.22?
[19:25] <sgclark> frameworks was 5.22
[19:25] <ahoneybun> I
[19:25] <ahoneybun> I
[19:26] <ahoneybun> damn 
[19:26] <ahoneybun> I'm on 5.22 on backports-landing
[19:26] <sgclark> anyway I have to leave for a bit, so I will start the script. Can't promise it won't break while I am gone though
[19:26] <ahoneybun> ok 
[19:26] <sgclark> oh this is yakkety not xenial
[19:28] <ahoneybun> xenial for me
[19:28] <sgclark> ah yeah, he doesn;t need me for backports
[19:38] <mparillo> I am updating XX on real HW after sudo add-apt-repository ppa:kubuntu-ppa/backports-landing
[19:43]  * acheron88 now waits for plasma 5.7 :P
[19:43] <soee> i prefere Apps 16.04 first :D
[19:43] <mparillo> I am sure soee will alert us to it.
[19:45] <soee> no! ;)
[19:45] <ahoneybun> I'm sure he has a script for it
[19:46] <acheron88> thank you all for that nice update :) great work
[19:51] <mparillo> rebooting...
[19:57] <mparillo> KInfocenter reports XX KDE Plasma Version 5.6.4; Frameworks 5.22
[19:58] <mparillo> Spectacle is bound to my print screen key ow.
[19:58] <mparillo> now
[19:58] <mparillo> Good work. Go out and have a swift half.
[20:11] <jimarvan> helloz :)
[20:13] <yofel> o/
[20:14] <jimarvan> :D
[20:14] <jimarvan> the kubuntu podcast event is moved to Friday, right?
[20:15] <yofel> ahoneybun: ^
[20:17] <ahoneybun> mm
[20:17] <ahoneybun> I believe June 3rd
[20:17] <ahoneybun> which is a friday
[20:18] <jimarvan> cool
[20:18] <ahoneybun> don't quote me
[20:19] <jimarvan> no worries, i'll be looking ;)
[20:19] <ahoneybun> mm not on my calendar
[20:20] <ahoneybun> oh
[20:20] <ahoneybun> says June 8th
[20:22] <jimarvan> ye wed june 8 saw it
[20:24] <soee> yofel: few people already tested landing backports, no issues reported :)
[20:24] <yofel> ok, there's at least one thing I need to fix, but nobody uses that I guess
[20:24] <soee> and that is ?
[20:24]  * ahoneybun wonders if Kontact will work 
[20:26] <sgclark> I think plasma-intgration will need a sponsor
[20:26] <ahoneybun> mm kickoff bug is still there
[20:26] <soee> ahoneybun: what bug ?
[20:26] <ahoneybun> soee when you switch launcer styles the favorites get reset
[20:29] <soee> ahoneybun: this https://bugs.kde.org/show_bug.cgi?id=358108 ?
[20:30] <ahoneybun> that's a wishlist
[20:30] <soee> dd you reported some bug ?
[20:41] <sgclark> clivejo: plasma uploading, but I suspect there will be a few that you will need a sponsor, I will send a request to list again.
[20:44]  * sheytan wants to test backports
[20:45] <mparillo> Looks like this applies to XX as well as YY in Plasma 5.6.4: https://bugs.kde.org/show_bug.cgi?id=362105
[20:45] <soee> sheytan: please do :)
[20:45] <valorie> sheytan: I think we need a couple more testers for ppa:kubuntu-ppa/backports-landing before moving it to backports
[20:45] <mparillo> Note this is the first time I tested on real HW. Previously, it was VM only.
[20:45] <mparillo> Note: This is NOT a Kubuntu-specific bug.
[20:45] <sheytan> soee: valorie: i will 
[20:46]  * valorie goes to upgrade the "old" laptop YY
[20:46] <valorie> but daughter and husband are headed our way
[20:59] <ahoneybun> mparillo I've not had that problem in 5.6.3
[20:59] <ahoneybun> also no I did not soee
[21:23] <soee> yofel: how hard is backporting QT 5.6 ?
[21:24] <yofel> no idea
[21:24] <yofel> someone try it, then we'll know :P
[21:24] <soee> :P
[21:24] <soee> will you release backports today ?
[21:25] <mamarley> There are already Qt 5.6 packages for Xenial in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-011/+packages.  Some of the backported KDE stuff would need to be recompiled in order to install it though.
[21:26] <soee> mamarley: who work on it ?
[21:26] <mamarley> Mirv
[21:26] <soee> so it is balned to be somehow available in 16.04 ?
[21:26] <soee> *planned
[21:26] <mamarley> No.
[21:26] <mamarley> (Not officially, anyway.  Quite possibly in a PPA though.)
[21:27] <soee> sitter: did you do a lot of adjustements to have QT 5.6 in Neon ?
[21:27] <yofel> I CONQUERED BEN muahahahahaha https://yofel.net/kubuntu/backport-report/ben/
[21:27] <yofel> well, again
[21:28]  * yofel needs something to drink
[21:28] <soee> you did waht ?
[21:28] <yofel> that thing has so horrible docs that I have to read the ocaml source whenever I use it *shudder*
[21:28] <yofel> soee: "ben" is the transition tracker tool
[21:28]  * soee sends 0.7 L RedBull  to yofel
[21:29] <yofel> thanks :D
[21:29] <soee> yofel: and we can't grab somehow QT 5.6 packages form Neon :D ?
[21:30] <mamarley> You don't need to get them from Neon, you can get them from that landing-011 PPA.
[21:30] <yofel> again no idea. (Although I would answer that with no)
[21:30] <yofel> I have yet to spend a single second thinking about what to do with QT 5.6
[21:30] <yofel> so far we didn't need it, and I'm still working on xenial so I quite frankly don't care
[21:31] <mparillo> ahoneybun: I do not think I had that (https://bugs.kde.org/show_bug.cgi?id=362105 ) on 5.6.4, but now I have it on physical HW from backports-landing on XX and in a VM from plasma-staging on YY
[21:33] <ahoneybun> I've tried it on 5.6.3 with Nvidia and intel
[21:33] <mparillo> ahoneybun: Sorry, what I wanted to say is that I did not notice it on 5.6.3, but I certainly see it on 5.6.4
[21:35] <soee> mamarley: why landing-011 ?
[21:36] <ahoneybun> I had no problems in 5.6.3 mparillo, not tried it in 5.6.4 yet
[21:37] <yofel> clivejo: excercise in release development, do you know what https://yofel.net/kubuntu/backport-report/ben/ is trying to tell you?
[21:38] <clivejo> oh you have a website
[21:38] <clivejo> yofel.net!
[21:38] <yofel> well it's a domain, nothing in the webroot but some folders
[21:38] <mamarley> "403 Forbidden"
[21:39] <yofel> that's intentional
[21:39] <mamarley> I know :)
[21:39] <clivejo> Transition progress of libkf5screen from 6 to 7
[21:39] <clivejo> measured at 83%
[21:39]  * clivejo wonders how thats calulated
[21:39] <yofel> open the details page
[21:40] <yofel> now  check the "good" box, and you'll see that 83% is the amount of green packages
[21:41] <clivejo> yes I see
[21:41] <clivejo> what is lxqt-config
[21:41] <clivejo> never seen that before
[21:41] <clivejo> Lubuntu?
[21:41] <yofel> !info lxqt-config
[21:42] <yofel> yeah, the lxde successor. Maybe they decided to use kscreen for themselves
[21:42] <yofel> so, I generated the page to catch any applications that might end up breaking when we publish the backports
[21:43] <yofel> in this case, as libkf5screen7 *breaks* libkf5screen6, lxqt-config would be uninstallable if someone using lxqt would add our backports
[21:43] <clivejo> this is based on the debian transition tracker?
[21:43] <yofel> yes, same ben, just with the ubuntu patches, and a heavily hacked together package list generator....
[21:46] <yofel> so, no-change rebuild for lxqt-config uploaded
[21:46] <clivejo> what do we do about that?  it dependant on libkf5screen-dev,
[21:46] <yofel> if you remember all the bug reports we had in wily about stuff breaking with the backports, *this* would have prevented that
[21:47] <yofel> a no-change rebuild is all that should be needed. It just needs to pick up the dep on the new lib
[21:47] <yofel> that's all I did for kde-spectacle too
[21:47] <clivejo> should you not email someone about it?
[21:47] <yofel> and you'll notice that spectacle is also listed on that page
[21:48] <yofel> how so? *We* updated libkscreen in *our* archive. So *we* make sure that stuff doesn't get broken
[21:48] <yofel> we are the only ones that can fix stuff in our archives anyway
[21:48] <clivejo> yes, but when other projects do that to us it annoys me
[21:49] <yofel> well, then you have to tell them to fix their archive. Not much you can do about it
[21:49] <yofel> other than that
[21:49] <clivejo> even if its a No change rebuild, its still adds a changelog?
[21:49] <clivejo> and creates a new binary
[21:50] <yofel> yes, you need the changelog for the higher version. And the new binary is the point as the binary needs to be linked against the new lib
[21:50] <yofel> so ldd shows the correct dep (as that's really all that dpkg-shlibdeps cares about, well mosty)
[21:50] <clivejo> but in this cased the VCS seems to be directly from debian
[21:51] <yofel> sure, we only sync that from debian
[21:51] <yofel> but the ubuntu release team will do exactly the same thing I did once we upload libkscreen to yakkety
[21:52] <yofel> that's how you get all those "buildX" versions in the archive
[21:52] <clivejo> is there a Ben instance for all our software?
[21:53] <yofel> no, this is something I configured the last couple hours. Can be extended to whatever we want though
[21:53] <clivejo> sgclark: thanks for uploading Plasma :)
[21:53] <clivejo> is it difficult to setup?
[21:54] <clivejo> how does it know?
[21:54] <clivejo> like can I query launchpad directly?
[21:54] <yofel> no you can't
[21:55] <clivejo> I love the way KCI shows the dependencies, so you can work out where the issue might be
[21:55] <sgclark> n
[21:55] <sgclark> p
[21:55] <yofel> First I had to download all the package lists, generate a merged set that combine all of main, universe, etc. into a "main" Packages.gz, then another set that also included the ppa packages
[21:55] <clivejo> eakkk sounds like a lot of work
[21:56] <yofel> then I fed that into a custom version of the auto-transitioner that's used by tanglu, which generated the .ben file, which ben then used to generate that website using another merged set of package lists
[21:56] <yofel> somewhat, yes, but I had some of that written for tanglu already, so I didn't start from scratch
[21:56] <sgclark> things seem stuck on kio though, it is built with New whatever that means. all deps seem to think it is unavailable *shrug*
[21:57] <yofel> sgclark: binary NEW means the binaries need to be approved by an archive admin before they're available in the archive
[21:57] <sgclark> but proposed builds seem stuck
[21:57] <sgclark> shouldnt they be able to find that dep?
[21:58] <yofel> how would they if the binaries are not in any downloadable location?
[21:58] <sgclark> or maybe I am losing it.
[21:58] <yofel> they are stuck pre-publisher
[21:58] <yofel> -release only mentions pam-kwallet and libkscreen for NEW though...
[21:58] <yofel> unless the bot lags
[21:58] <sgclark> ahh so proposed items cannot depend on other proposed. interesting
[21:58] <yofel> yes they can
[21:58] <yofel> but not stuff in NEW
[21:59] <sgclark> oh
[21:59] <sgclark> I gete it
[21:59] <yofel> stuff in NEW is not in a package list
[21:59] <sgclark> ok
[21:59] <clivejo> how long do packages stay in propposed?
[21:59] <sgclark> bell ent off thanks
[21:59] <yofel> because an archive admin could decide to reject the binaries
[21:59] <sgclark> yep I get it now
[21:59] <sgclark> sorry
[21:59] <yofel> clivejo: until a tool called "britney" decides that it's safe to move them to -release
[22:00] <clivejo> how does it decide that?
[22:00] <sgclark> so I think plasma will be held up with this too
[22:01] <yofel> it has multiple checks. That includes installability (would some other package become uninstallable by the update?), transitions (what we just talked about, the transition tracker has to be 100% green), autopkgtests, etc.
[22:01] <clivejo> why did it seem that xenial dev was quicker to get stuff into the archive?
[22:01] <yofel> we uploaded everything at once?
[22:01] <yofel> not the particulary best idea, but we managed
[22:01] <sgclark> there were also many folks working at the time, I think there are several at a conference here
[22:02] <yofel> clivejo: if you're curious what britney does, see the 2 proposed migration links on qa.kubuntu.co.uk
[22:02] <sgclark> that I was suppose to go to, oops
[22:04] <clivejo> kcoreaddons (5.18.0-0ubuntu1 to 5.22.0-0ubuntu1)
[22:04] <clivejo> thats one of ours
[22:05] <yofel> yay... test failures...
[22:05] <sgclark> yippie
[22:05]  * sgclark runs away
[22:05] <yofel> wait for me!
[22:05] <sgclark> lol
[22:08] <clivejo> what does it mean regression in kpeople
[22:09] <yofel> means "passed before, fails now"
[22:09] <clivejo> quite a few frameworks 5.22 on that list
[22:09] <yofel> yes, and many "not considered", so a couple have test failures, and some are held back because they depend on those
[22:10] <Angario> Will this 5.6.4 update fix the multi-monitor issues?
[22:11] <soee> Angario: lot of this problems are related to QT
[22:17] <soee> https://www.youtube.com/watch?v=Dy6MpsDPKts
[22:50] <yofel> clivejo: if you're still curious, the shell scripts on https://yofel.net/kubuntu/backport-report/ do the magic
[22:51] <yofel> the dose reports are also fun to read. Beside lots of garbage, they also nicely tell you that the old -dbg packages are broken :D
[22:51] <clivejo> bedtime reading I reckon
[22:55] <valorie> ok, I tried backports-landing on the wrong computer
[22:55] <valorie> no backports for YY!
[22:56]  * clivejo nods
[22:59] <valorie> now running it on the XX travel laptop
[23:00] <valorie> I didn't want to upgrade it again before heading to the cabin with it
[23:00] <valorie> so what needs testing in YY?
[23:04] <yofel> ok, bedtime, nini
 ttfn
[23:05] <clivejo> night yofel
[23:05] <clivejo> sgclark: are you still working on apps?
[23:06] <sgclark> not right this minute. If you want to fix stuff go for it. mostly done.
[23:07] <mparillo> valorie: I assume you already tested plasma-staging on YY?
[23:08] <valorie> I did, but I think there was more added later
[23:08] <valorie> it's been difficult to keep track of everything with all that's been happening
[23:09] <valorie> just today we buried my daughter's cat who died last night of lymphoma
[23:09] <valorie> my poor dau. lost her grandad and cat in a week
[23:09] <valorie> :(
[23:10] <valorie> as soon as the travel laptop finishes upgrading, I'll try again with plasma staging on the YY laptop
[23:10]  * sgclark hugs valorie
[23:17] <valorie> ty sgclark
[23:17] <valorie> you skipped OSCON?
[23:24] <valorie> huh, on the XX box even the flashdownloader worked
[23:24] <valorie> that has been bugging me for 3 mo. or more
[23:24] <valorie> rebooting it
[23:33] <sgclark> valorie: yeah conferences still cost money to eat and stuff. Had to skip this one.
[23:35] <valorie> got it
[23:55] <valorie> the YY box seems perfect although KDEconnect isn't pairing
[23:56] <valorie> new kernel is fine, etc.
[23:56] <valorie> chromium starts up, works, dropbox syncs, etc.