[00:00] <yofel> ovidiu-florin: do you have the automation repo cloned?
[00:00] <ovidiu-florin> no
[00:01] <ovidiu-florin> where is it hosted?
[00:01] <yofel> git+ssh://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation use the git+ssh url
[00:01] <yofel> er wait
[00:01] <yofel> ovidiu-florin: use git+ssh://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation
[00:01] <yofel> aaaargh
[00:02] <yofel> chrome, please die
[00:02] <ovidiu-florin> same link
[00:02] <yofel> https://help.launchpad.net/Code/Git#Configuring_Git
[00:02] <yofel> https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/
[00:11] <yofel> ovidiu-florin: got it?
[00:11] <yofel> .3 wip -> test
[00:11] <ovidiu-florin> yofel: not yet
[00:11] <ovidiu-florin> configurig git to use the roght username
[00:13] <ovidiu-florin> yofel: done
[00:14] <yofel> good, now try this: ./package-name-list -d xenial -r frameworks
[00:15] <ovidiu-florin> permission denied
[00:15] <ovidiu-florin> where do I give my public key?
[00:16] <yofel> it's querying depot.kde.org, see README for the ssh username
[00:17] <yofel> I just whitelisted you, so try again when you're done
[00:18] <yofel> depot is the kde server for unreleased things
[00:20] <ovidiu-florin> done
[00:21] <yofel> when the script succeeded, commit and push the change. The status page will pick it up on the next refresh
[00:22] <ovidiu-florin> $ ./package-name-list -d xenial -r frameworks
[00:22] <ovidiu-florin> got version 5.17 stable
[00:22] <ovidiu-florin> write package-name-lists/frameworks-xenial
[00:22] <ovidiu-florin> git diff package-name-lists/frameworks-xenial
[00:22] <ovidiu-florin> that's it
[00:22] <yofel> that should actually show a diff..
[00:22] <ovidiu-florin> it printed that
[00:22] <ovidiu-florin> nothing else got printed
[00:23] <yofel> what if you do git diff now?
[00:23] <ovidiu-florin> package-name-lists/frameworks-xenial got modified
[00:23] <yofel> well good, then that worked at least
[00:24] <ovidiu-florin> addeed breeze and oxygen icons
[00:24] <yofel> that's how we keep our package lists updated to show what we ship for a release
[00:27] <ovidiu-florin> now what?
[00:27] <yofel> push the change
[00:27] <ovidiu-florin> what commit message?
[00:28] <yofel> something sane? "Update frameworks package list for 5.17" or so
[00:38]  * ovidiu-florin Zzzzz
[00:38] <ovidiu-florin> can we continue ub the nmorning?
[00:38]  * ovidiu-florin is off to bed
[00:39] <yofel> sure, I'm off shortly as well, nini
[07:39] <ovidiu-florin> Good morning sexy people
[07:41] <ovidiu-florin> yofel:  shouls I procede and commit the change?
[07:41] <ovidiu-florin> Sorry for last night, I fell asleep with my head on the keyboard
[08:05] <ovidiu-florin> yofel: I've updated the KA clone, and ran it again. I see those changes are not pushed yet, so I'll commit them now
[08:06] <ovidiu-florin> done
[08:06] <ovidiu-florin> commited and pushed
[08:06] <ovidiu-florin> yofel sgclark ping me when you're around, meanwhile I'll work on some KMail bugs
[11:33] <soee> yofel: apps 15.08.3 are ready to test in Wily ?
[11:33] <yofel> l10n is missing, but otherwise they're ready in ppa-landing
[11:36] <soee> yofel: why plasma 5.4.3 was not removed from landing ppa if it is in backports ppa ?
[11:36] <yofel> I forgot to do that
[11:36] <soee> wouldn't it be a good idea to have ppas clear ? if something goes from one ppa -> to next 
[11:37] <yofel> yes, but in this case, those packages are already in the target ppa, so it doesn't make a difference
[11:37] <yofel> otherwise I would've done the clean and recopy
[11:39] <soee> i'm a bit lost :) i'm talkign about situation whan for exampel we have something in landing ; it was tested ; moved to backports ; than landing ppa should be cleard from this stuff that was just moved to backports
[11:39] <kfunk> any ETA for Plasma 5.5 in backports, btw? :) (no hurry)
[11:41] <yofel> soee: first to make something clear, ppa-landing is for /ppa, not /backports. And in this case, those packages are in both PPAs, so they literally have no effect
[11:41] <yofel> so cleaning things up after I noticed my mistake, waiting for the janitor, then recopying - would've been a great waste of time
[11:42] <soee> recopying ?
[11:42] <yofel> copy again? as I already copied them once from staging to landing
[11:42] <soee> yofel: do you use some script to copy ppa -> ppa or it requires manual action?
[11:42] <yofel> script
[11:43] <soee> oh so it can also auto-clean source ppa after packages hits target one ?
[11:43] <yofel> yes, we also have a script for that, but I don't auto-do that to prevent packages getting lost if LP somehow screws up a copy
[11:45] <yofel> but as I said, if it mattered, I would've fixed it. But in this case you have a PPA with A, and another one with A and B. So if you already have A, the A in the other PPA won't even be considered
[11:48] <soee> yofel: "So if you already have A, the A in the other PPA won't even be considered" - yest this one is clear and i'm not worried about such situations :) All this as about having ppas clear s i think 1 or 2 days ago sgclark said that some builds were failing because of full ppas or something
[11:49] <yofel> that was CI, can't really keep that clear
[11:49] <soee> so CI have nothign to do with landing ppa ?
[11:51] <soee> kfunk: i think there is no ETA :)
[11:53] <yofel> no
[11:54] <soee> hmm, wait we/me have already 15.08.3 in Wily  ..
[11:55] <yofel> that was the hacked together backports set, this is the SRU set
[11:55] <soee> adding ppa shows no updates at all 
[11:55] <yofel> right, you need a system without backports to test this
[11:56] <soee> oh ok, my mistake :)
[11:58] <yofel> np, It's not that obvious..
[12:12] <BluesKaj> Hiyas all
[12:15] <ovidiu-florin> yofel: you're back
[12:16] <ovidiu-florin> yeeey
[12:16] <ovidiu-florin> tell me what to do
[12:16] <yofel> only for 20 more minutes, then I'm off watching star wars. Got to get the priorities right :P
[12:17] <yofel> anyway, thanks to your change, oxygen-icons now appears red on the frameworks status page
[12:17] <yofel> yaaaa a a y...
[12:19] <BluesKaj> so what's happening with plasma 5.5?
[12:19] <yofel> WIP
[12:20] <yofel> ovidiu-florin: so looking at the build log, it's trying to run qmake-qt5 - which isn't something that exists
[12:20] <ovidiu-florin> yofel: ECM cannot find qmake
[12:20] <yofel> at least not on debian systems...
[12:21] <yofel> so this might actually need a patch in ecm
[12:21] <soee> BluesKaj: do you have Wily instance withoout backports enabled ?
[12:22] <ovidiu-florin> yofel: can we confirm that qmake is on that machine?
[12:23] <BluesKaj> soee, I have wily on the laptop, but the backports are enabled
[12:23] <BluesKaj> haven't upgraded it yet
[12:23] <yofel> it's actually not, which is another issue. /usr/lib/x86_64-linux-gnu/qt5/bin/qmake is in qt5-qmake, which isn't installed
[12:23] <ovidiu-florin> yofel: apt recommends to install qt5-qmake
[12:23] <ovidiu-florin> but it doesn't install it
[12:24] <yofel> it suggests it, and buildds run with --no-install-recommends
[12:24] <ovidiu-florin> so that's not a recommended, it a required
[12:24] <ovidiu-florin> where does that get set?
[12:24] <yofel> right, for this build. So you need to add qt5-qmake in the Build-Depends field of oxygen-icons
[12:26] <ovidiu-florin> I'm not sure where that is
[12:26] <ovidiu-florin> yofel: ^
[12:26] <ovidiu-florin> somewhere in the KA repo?
[12:26] <yofel> right, so you'll want to add this to your gitconfig:
[12:26] <yofel> [url "git+ssh://git.debian.org/git/"]
[12:26] <yofel>     insteadOf = debian:
[12:27] <ovidiu-florin> done
[12:27] <yofel> then you go, git clone debian:pkg-kde/frameworks/oxygen-icons5
[12:27] <yofel> git checkout kubuntu_xenial_archive
[12:27] <ovidiu-florin> permission denied
[12:28] <yofel> ah dang, let me get the public url
[12:28] <ovidiu-florin> where do you get the URLs from?
[12:28] <yofel> git clone git://anonscm.debian.org/git/pkg-kde/frameworks/oxygen-icons5
[12:29] <yofel> memory myself, but give me a sec
[12:29] <yofel> http://anonscm.debian.org/cgit/pkg-kde/ has the pkg-kde repo list
[12:29] <yofel> usually it's pkg-kde/<namespace>/<source>.git
[12:30] <ovidiu-florin> got it
[12:30] <yofel> uhm, that has no kubuntu branch o.O
[12:30] <yofel> how do the scripts even handle that
[12:32] <ovidiu-florin> yofel: so I just add it to control and comit , right?
[12:32] <yofel> wait a sec
[12:32] <BluesKaj> soee, just tried to upgrade wily ..all packades up tp date
[12:33] <BluesKaj> packages
[12:34] <soee> BluesKaj: yes but there are Apps 15.08.3 SRU to test, won't do with backports enabled as they are installed than already
[12:35] <yofel> ovidiu-florin: ok sorry, I'm out of time, but something is really not right with o-i regarding git repo and epoch and stuff, so this will take a while longer
[12:37]  * ovidiu-florin didn't even notice BluesKaj 's typo
[12:38] <BluesKaj> soee, Apps 15.08.3 SRU?
[12:38] <ovidiu-florin> yofel: ok, ping me when you return
[12:38] <ovidiu-florin> please don't forget
[12:39] <BluesKaj> ovidiu-florin, I guess because I make so many typos , nobody notices anymore :-)
[12:39] <ovidiu-florin> :)))
[12:40]  * sitter wonders what possessed yofel to go the movie theatre in the middle of the day
[12:41] <bshah> force? </badpun>
[12:44] <kfunk> sitter: +1
[12:45] <ovidiu-florin> sitter: can you help me with this building issue?
[12:45] <davmor2> sitter: He's gone to see nativity 3 obviously
[12:50] <sitter> madness I say
[12:50] <sitter> ovidiu-florin: oxygen-icons5 should not need qmake. if it does that likely is a bug
[12:52] <ovidiu-florin> sitter: what is that package anyway?
[12:52] <ovidiu-florin> I dont' see a readme in it
[12:53] <sitter> what do you mean?
[12:53] <ovidiu-florin> an, info I wanted is in control
[12:53]  * ovidiu-florin is reading the build logs again
[13:00] <ovidiu-florin> sitter: I can't tell, where are the sources of oxygen-icons5
[13:00] <ovidiu-florin> ?
[13:00] <sitter> kde:oxygen-icons5
[13:01] <ovidiu-florin> ko
[13:01] <ovidiu-florin> ok
[13:24] <ovidiu-florin> sitter: oxygen-icons5 needs ECM
[13:24] <ovidiu-florin> ECM needs qmake
[13:28] <sitter> [13:50] <sitter> ovidiu-florin: oxygen-icons5 should not need qmake. if it does that likely is a bug
[13:29] <ovidiu-florin> so you're saying tha toxygen-icons5 sould not need ECM?
[13:29] <sitter> no. I am saying "oxygen-icons5 should not need qmake"
[13:51] <ovidiu-florin> it doesn't, directly
[16:25] <BluesKaj> soee, jubo has a habit of not paying any attention to advice. I find it very frustrating trying to help him . I mostly try to avoid him nowadays  
[16:26] <soee> :)
[16:39] <genii> I've had pretty much the same experience with them
[18:54] <ovidiu-florin> yofel: are you back?
[19:03] <_Groo_> yofel: ping
[19:06] <_Groo_> could anyone help me with the "kubuntu way of doing things now" , aka flow?
[19:06] <_Groo_> i backported sddm to wily as requested
[19:06] <_Groo_> 0.13
[19:06] <_Groo_> for now i sent it to one of my ppas, but how do i start using the proper kubuntu way?
[19:07] <_Groo_> i read https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/README
[19:07] <_Groo_> but im confused
[19:07] <_Groo_> i dont know how to start, really :P
[19:15] <_Groo_> yofel: anyway, sddm 0.13.0 is in https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pbppa/+packages
[19:16] <_Groo_> yofel: lets use this package as a training/howto on how i should upload this packages properly
[19:16] <_Groo_> yofel: once you have sometime (or any other kubuntu developer), give me a ping on how to proceed
[19:18] <_Groo_> could anyone tell me where i get/download/add-apt the package/file/github/whatever that has ./package-name-list for ex?
[19:19] <_Groo_> the stupid readme tell what to do but not where to download
[19:19] <_Groo_> nvm
[19:19] <_Groo_> <--- dumb
[19:19] <_Groo_> https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation
[21:53] <ovidiu-florin> yofel: ping
[22:26] <yofel> ovidiu-florin: re
[22:27] <soee> yofel: how was the SW movie?
[22:27] <yofel> good, I'll leave it at that.
[22:28] <soee> ;)
[22:29] <yofel> _Groo_: first of all, by assigning the relevant bugs to you and setting them to in progress *before* you get to work ;)
[22:29] <yofel> we use those for coordination and duplicate-work prevention
[22:32] <ovidiu-florin> yofel: sitter said oxygen-icons5 should not depend on qmake
[22:33] <ovidiu-florin> it depends on ECM and ECM depends on qmake
[22:34] <yofel> right, and he does have a point. 
[22:35] <yofel> sgclark: why are there backport changelogs in kde-l10n-common ?!?
[22:35]  * yofel deletes those
[22:36] <ovidiu-florin> yofel: so it should not depend on ECM?
[22:37] <yofel> if it does not require it, no (see CMakeLists.txt)
[22:38] <ovidiu-florin> cmakelists requirs it
[22:39] <yofel> then it needs to depend on e-c-m, but maybe e-c-m is missing a runtime dep
[22:44] <ovidiu-florin> I don't understand
[22:45] <yofel> well, it has to depend on e-c-m, otherwise it will fail with "missing ECM"
[22:45] <ovidiu-florin> and then that means ecm needs qmake marked as a dependency, right?
[22:46] <yofel> sounds like it - or harald meant to check whether the ECM component that uses qmake is actually needed, which would make that an upstream bug that it uses something it doesn't actually need
[22:46] <yofel> can't really say without actually looking into it
[22:47] <yofel> in such situations I usually just build locally, get it to build, then when I know what was wrong, I look into it in more detail
[22:47] <yofel> where locally == pbuilder chroot
[22:49] <yofel> currently the qmake-qt5 thing is irritating me, as I don't know what that's supposed to be, but I'm not an ecm expert either
[22:53] <ovidiu-florin> yofel: would it be wrong to add it as a dependency?
[22:53] <ovidiu-florin> to ECM?
[22:54] <yofel> If the ecm cmake files have qmake calls in them, no
[22:56] <ovidiu-florin> yofel: can we have a hangout please
[22:56] <ovidiu-florin> I don't understand this
[22:56] <yofel> _Groo_: and before I forget the rest of my answer: thanks for doing that! I'll try to look at it soon so we can  upload it to xenial. 
[22:57] <yofel> sddm will probably also need a git base merge though
[22:57] <yofel> ovidiu-florin: well ok, lets try
[22:58] <clivejo> can I listen in?
[22:58] <ovidiu-florin> I have nothing against it
[22:58] <yofel> I'll leave the setup to you then
[22:59] <yofel> wait, how does hangouts even work these days
[23:00] <yofel> oh right, there was that app
[23:00] <ovidiu-florin> yofel: here: https://meet.jit.si/ImmenseVegetablesOfferRemorsefully
[23:00] <ovidiu-florin> this is easier
[23:00] <ovidiu-florin> and it's free software
[23:00] <yofel> fine with me
[23:06] <ovidiu-florin> yofel: emc control requires qttools5-dev, doesn't that bring in qmake as well?
[23:11] <clivejo> o/ soee_
[23:12] <_Groo_> yofel: ellisistfroh replied to me by email regarding sddm
[23:12] <_Groo_> yofel: some stuff i need to change
[23:13] <_Groo_> yofel: what ive been asking since the beginning , is exactly HOW should i proceed when doing packages. you said i need to assign the bug to me, you mean via lp? thats what im trying to figure out here, the proper workflow
[23:14] <_Groo_> it would help newcomers if you guys had a "first contribution" for dummies, with all the steps involved
[23:14] <_Groo_> but ok, let me assign the the bug to me
[23:15] <_Groo_> https://www.irccloud.com/pastebin/cezWBd22/
[23:15] <_Groo_> how do i do a SRU-backport? what are the steps
[23:15] <_Groo_> ?
[23:15] <_Groo_> i know how to package stuff, i just dont know how to do it with your workflows and rules, thats what im trying to learn
[23:16] <_Groo_> so i can start doing bigger steps and play with the automation scripts and the like
[23:20] <clivejo> _Groo_ you would need to package it for xenial first I think
[23:20] <_Groo_> clivejo: that is easy
[23:20] <_Groo_> clivejo: ill do it when i get home
[23:20] <clivejo> get it tested
[23:20] <_Groo_> clivejo: how?
[23:20] <_Groo_> clivejo: besides testing myself
[23:21] <_Groo_> clivejo: that didnt sound right :P
[23:21] <clivejo> there are people here who can test
[23:21] <_Groo_> clivejo: ill announce it here
[23:21] <clivejo> put it into your PPA and use the bot to announce it
[23:21] <_Groo_> clivejo: ok
[23:22] <clivejo> if everything checks out yofel can then put it into the xenial archive
[23:25] <clivejo> one of the release managers can then  apply for a SRU request to put it in wily, if needbe - https://wiki.ubuntu.com/StableReleaseUpdates
[23:26] <clivejo> _Groo_: is there a LP bug open for it?
[23:29] <clivejo> is this the LP bug - https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1516837
[23:30] <_Groo_> yes it is, ill apply to it
[23:31] <_Groo_> clivejo: there, i assigned it to me
[23:32] <_Groo_> ill work on xenial and announce it here, prolly tonight or tomorrow, im going home from work in 20 min
[23:33] <clivejo> you can refer to the bug in your changelog
[23:33] <_Groo_> will do
[23:34] <clivejo> then LP should autoclose it when it gets uploaded
[23:36] <clivejo> LP 1519564
[23:38] <clivejo> same bug me thinks
[23:39] <clivejo> anywho, Im off to bed
[23:39] <clivejo> night all
[23:52] <yofel> _Groo_: hey, I was just talking to ovidiu about the workflow, and we'll try to come up with something next week.
[23:52] <yofel> Currently our workflow is a mess, it's undocumented and to make things even more fun it's currently changing
[23:53] <yofel> The LP bug workflow is the standard ubuntu workflow, but I don't remember where the documentation for that is either :/
[23:54] <yofel> for the automation stuff, the current workflow is roughly outlined in the README, I don't really know how to extend that, so suggestions welcome
[23:56] <yofel> also, there's no such thing is an SRU-backport
[23:56] <yofel> !sru
[23:56] <yofel> is exlcusively for bugfixes
[23:57] <yofel> I'm fairly sure that there will be wily people that will want to use the newer sddm, so we can put it into our backports ppa for them
[23:57] <yofel> you could even do an offical backports request, which is documented somwhere on wiki.ubuntu.com
[23:57] <soee_> yofel: is it safe to upgrade sddm without complex tesing ?
[23:58] <yofel> not really, which is why I wouldn't do that without testing it in xenial for a while
[23:58] <soee_> +1
[23:59] <yofel> but our backports ppa is a place where "shit can happen", so if someone is prepared to update qt, plasma, frameworks and apps to a new major version, sddm doesn't make things that much worse