[00:14]  * yofel moved kubuntu-automation out of kubuntu-packaging again
[00:17] <sgclark> hmm stable is using kde master... that is so not what we want...
[00:20] <sgclark> oh
[00:21] <sgclark> I *think* their is code here using plasma/frameworks/applications namespaces. ugh
 so how do we make kde telepathy work with google?
[00:40] <sgclark> add google account?
[00:41] <sgclark> online accounts in systemsettings add google
[00:43] <sgclark> mm yes.. component is tied to namespace
[00:43]  * sgclark thinks
[00:47] <tux|dude> Anyone else had issues with plasma shell getting a bit bogged down after a while so you have to either reboot your machine or reboot plasma shell to fix it?
[00:48] <sgclark> not in a long time
[00:48] <tux|dude> Really? 
[00:49] <sgclark> 11 days and massive work and running good
[00:49] <tux|dude> Because I've been having some issues like that myself
[00:49] <tux|dude> It's weird and I dunno why it is happening because I didn't get it on 15.10
[00:49] <sgclark> really, I have been working non stop
[00:49] <sgclark> plasma is behaving. CI not so much
[00:50] <sgclark> I am on xenial though
[00:50] <sgclark> are you using the 5.6 ?
[00:58] <tux|dude> I'm on xenial and using 5.5.5
[00:58] <tux|dude> Is 5.6 out?
[00:59] <sgclark> I am also on 5.5.5 xenial
[01:00] <tux|dude> I see...
[01:00] <tux|dude> Might be my gpu or something
[01:00] <sgclark> clivejo was packaging 5.6 . However I don't know if he finished and he is long asleep and probably not here this wewekend
[01:01] <sgclark> weekend*
[01:01] <tux|dude> I see
[01:01] <tux|dude> Well it's weird and I dunno why it keeps doing this but hopefully 5.6 fixes it
[01:02] <sgclark> ah looks like he got yakkety done. but it will be some time yet before we get backports done.
[01:02] <tux|dude> Right, I see
[01:02] <tux|dude> Well either way I'll see what I can find
[01:02] <sgclark> ok
[01:02] <sgclark> sorry I am not much help
[01:04] <tux|dude> Oh don't worry
[01:04] <tux|dude> You assisted me how you could and I appreciate that :)
[01:05] <sgclark> :)
[01:05] <tux|dude> Meanwhile I'm installing xenial onto this old pentium D machine I had lying around to see how it performs haha
[01:06] <sgclark> Ok I need to rip myself away from this computer. I am seeing double. see you all tomorrow.
[01:06] <tux|dude> Later
[01:21] <ScottK> sgclark: I think it was just upload and pray.
[01:23] <sgclark> eek I don't think infinity will like that answer lol
[01:23] <sgclark> ok thanks
[01:32] <ScottK> sgclark: I don't recall it being a problem for stable updates.
[01:33] <sgclark> this is an SRU
[01:38] <ScottK> That's what I meant be stable update.
[01:40] <sgclark> oh right sorry
[02:17] <N3X15> That bot is not happy
[02:27] <N3X15> Feel sorry for the poor soul who has to keep all those Jenkins jobs up to date.
[03:11] <ahoneybun> clivejo ping
[03:12] <sgclark> I would think he is asleep
[03:12] <ahoneybun> sgclark can I show you something?
[03:12] <ahoneybun> I'm on BBB
[03:13] <sgclark> I am pre occupied.
[03:13] <ahoneybun> I see
[03:13] <ahoneybun> it is pretty awesome
[03:14] <ahoneybun> is the patreon account cancelled?
[03:14] <sgclark> huh?
[03:14] <ahoneybun> since your with the outreach thing
[03:15] <sgclark> mm no. I will still be doing stuff, just not 10+ hours a day
[03:15] <sgclark> if folks want to cancel so be it.
[03:15] <ahoneybun> alright cool
[03:15] <ahoneybun> I won't won't
[03:16] <sgclark> I cannot survive on 100 dollars a month
[03:16] <ahoneybun> *I won't
[03:16] <ahoneybun> of course
[07:57] <lordievader> Good morning.
[10:02] <BluesKaj> Hey all
[10:18]  * clivejo 's body wanders into the room like a zombie 
[10:19] <clivejo> hi BluesKaj
[10:19] <BluesKaj> hi clivejo
[10:22] <clivejo> sorry sgclark, I was talking rubbish last night about those three packages
[10:23] <clivejo> for some reason I thought because I didnt package I assumed they were in plasma, but they are new packages
[10:24]  * clivejo needs sleep but cant get any!
[13:54]  * clivejo yawns
[13:55]  * sgclark does too
[13:55] <sgclark> so we have bugs still in the CI.
[13:55] <clivejo> Im like a zombie today
[13:56] <clivejo> sorry for last night
[13:56] <sgclark> I did not sleep well either :*(
[13:56] <sgclark> oh no worries. there are more package changes coming
[13:56] <clivejo> so I see
[13:56] <sgclark> well namespace moves
[13:56] <clivejo> did I see somewhere that you copied the missing plasma packages to LP?
[13:57] <sgclark> yeah I did, off debian master
[13:57] <clivejo> ah cool, thannks
[13:57] <sgclark> so at least there is something to start with
[13:57] <clivejo> I made a boo boo with plasma-discover
[13:57] <clivejo> I had a local git copy and renamed it in LP to just discover
[13:58] <clivejo> but I then commited to the old name :(
[13:58] <clivejo> so theres a plasma-discover with a yakkety branch
[13:59] <clivejo> https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/plasma-discover
[13:59] <clivejo> I need to push that branch into the discover repo
[14:00] <clivejo> this one - https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/discover
[14:00] <clivejo> and delete the other one
[14:01] <sgclark> dunno how to accomplish that except manually.
[14:01] <clivejo> oh actually I reverted that change, so I think we are ok!
[14:02] <clivejo> Ill just delete the plasma-dsicover repo
[14:02] <sgclark> ok
[14:02] <sgclark> I should probably fix ci to use discover...
[14:02] <sgclark> nm I already did
[14:03]  * sgclark needs more coffee
[14:03] <clivejo> did I hear yofel say something about moving KA?
[14:04] <sgclark> I think I saw that in the midst of failure
[14:04] <clivejo> yeah hes moved it - https://code.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation
[14:05] <clivejo> Ill rm my local version and clone it from that
[14:05] <clivejo> so I dont accidently move it back!
[14:06] <clivejo> BTW those new packages in plasma, did you add them to package list?
[14:06] <sgclark> hehe good plan
[14:06] <sgclark> yes
[14:06] <sgclark> oh
[14:06] <sgclark> my ci list
[14:06] <sgclark> perhaps they need to be added to KA
[14:06] <clivejo> yup
[14:06] <clivejo> here - https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/dev-package-name-lists
[14:07] <clivejo> Ill add them to yakkety 
[14:07] <clivejo> so hopefully git-clone-all should work now 
[14:10] <clivejo> ok done
[14:11] <clivejo> have to remember to add them into xenial when we go to backport
[14:14] <clivejo> sgclark: do you know how the build dep bump script works?
[14:14] <sgclark> clivejo: afraid not
[14:15] <clivejo> it only seemed to bump the plasma packages
[14:15] <clivejo> I need it to bump the FW too
[15:13] <BluesKaj> any chance of  somenew splashscreen themes/options in kubuntu's future? the orange etc is becoming boring
[16:52] <soee_> hiho
[17:50] <clivejo> !info pkg-kde-tools
 How's it going clivejo?
[17:54] <clivejo> dunno
[17:54] <clivejo> 2 and half hours sleep is not good
 Indeed :/ Take something freshy to drink; )
[17:56] <clivejo> and scripts not doing what I want
[17:57] <yofel> sgclark, clivejo: the KA move was me moving it *back* to it's location. For some reason it was under kubuntu-packaging yesterday - but that's only for packaging branches
[17:57] <clivejo> yofel: how did it get there?
[17:57] <yofel> that's what I want to know...
[17:58] <clivejo> I usually clone it from the web UI address
[17:58] <yofel> I just noticed yesterday that 'git pull' complained about an invalid location
[17:59] <yofel> hm. I should proably merge pkg-kde-tools, I have a bug for that anyway
[18:00] <yofel> bbiab
[18:01] <clivejo> yofel: is there any way to get git-clone-all to clone into a sub directory?
[18:01] <clivejo> ie discover/discover/debian
[18:02] <clivejo> or even discover/git/debian like the staging script does?
[18:17] <yofel> clivejo: not that I know of
[18:17] <yofel> what's the use case?
[18:18] <clivejo> Ive used git-clone-all for my package list
[18:18] <clivejo> bumped all the deps and fixed the 3 new packages
[18:18] <clivejo> pushed to the YY branch
[18:19] <clivejo> now I want to run git-buildpackage-ppa on all the folders
[18:20] <yofel> do-all should do that, no?
[18:21] <clivejo> its makes a buildarea in the root of the cwd
[18:21] <yofel> yes?
[18:22] <clivejo> and seems to go mental
[18:22] <yofel> well, that's not good. Got a log?
[18:23] <clivejo> let me try again
[18:23] <clivejo> there are 42 packages
[18:24] <clivejo> but last time it only built the source for like 6 of them
[18:24] <yofel> weird
[18:24] <clivejo> yeah and no strange output
[18:24] <clivejo> it looks like the staging script
[18:25] <clivejo> ie downloading source, building source, debsign
[18:26] <clivejo> Ill try it again
[18:26] <clivejo> I was expecting 42 source files
[18:26] <yofel> the source fetching is different
[18:27] <yofel> staging uses a custom rsync command, gbp uses usync
[18:27] <clivejo> uscan instead of rsync?
[18:27] <yofel> erm, yes, uscan
[18:27] <clivejo> yeah, but I can see the output is grabbing the correct tarball
[18:27] <yofel> someone should write usync (i.e. an uscan that actually works)
[18:28] <clivejo> theres a guy on OSM IRC called someone, Ill ask him!
[18:29] <clivejo> oh actually hes SomeoneElse
[18:29] <yofel> :D
[18:32] <soee_> yofel: Plasma provides own breeze grub and plymouth themes right?
[18:33] <yofel> I don't know
[18:34] <yofel> if they do, we don't use them
[18:35] <clivejo> oh, it worked this time
[18:35] <clivejo> 42 changes files
[18:36] <clivejo> there are two new packages breeze-grub and breeze-plymouth
[18:37] <yofel> well, that answers soee_'s question I guess ^^
[18:37] <clivejo> I guess we have to install them somewhere to enable them
[18:38] <soee_> so they are optional - not installed in Kubuntu by default ?
[18:38] <clivejo> LOL I have no idea
[18:38] <clivejo> I just packaged them
[18:39] <clivejo> Im assuming another package needs to depend on them to install it
[18:40] <clivejo> KCC will probably have to make a decision on if they want a fully branded plasma boot process
[18:42]  * clivejo likes his text boot up, gives one the illusion of travelling very fast in an elevator
[18:54] <clivejo> yofel is there any way to force full source upload via dput, or do I have to debuild -S -sa?
[18:57] <yofel> you have to pass -sa, or rather you have to make the gbp do that (no, you cannot do it after that as it requires different .dsc contents)
[18:58] <yofel> for now edit the script and find where it adds -sd, and edit that
[19:26] <clivejo> !info libplymouth-dev
[19:27] <clivejo> !info plymouth-dev
[20:04] <clivejo> sgclark: Im still getting an error about krunner - https://paste.kde.org/paidpmpsd
[20:06] <clivejo> yofel: would you mind looking at it?
[20:53] <clivejo> anyone on Yakkety?
[20:55] <yofel> clivejo: libkf5runner-dev needs to break/replace kapptemplate and kapptemplate needs the files removed
[20:56]  * clivejo nods
[20:56] <clivejo> but Im not allowed to touch it
[20:57] <yofel> you're not allowed to touch kapptemplate 15.12 o.O?
[20:57] <clivejo> not allowed to touch any 5.21 FW
[20:57] <clivejo> on penalty of a slow painful death 
[20:57] <yofel> fix it in git and tell her you fixed it
[20:58] <yofel> then she can upload whenever she needs it
[20:58] <clivejo> yofel: are there any docs on kubuntu-batch-backport-git script?
[20:59] <yofel> no, that's just a braindump (or shell dump) of the steps I did to backport something
[20:59] <yofel> that would need quite a bit of refactoring to be a runnable script
[20:59] <yofel> hm..
[21:00]  * yofel hands clivejo the "Divine pointer to Yofel"
[21:00] <yofel> just in case she does get angry at you
[21:01] <clivejo> seems to build ok without it, but install is causing me problems
[21:02] <clivejo> and got a severe shortage of yakkety testers!
[21:02] <yofel> right, no matter what we do, this issue needs a fix in both packages
[21:02] <clivejo> can you do it please?
[21:03] <yofel> meh, can do, in an hour or so though
[21:03] <clivejo> ok
[21:03] <clivejo> did this script run for you correctly?
[21:04] <yofel> it should roughly do the job, but you might want to uncomment the dput line for now..
[21:04] <clivejo> I might run it line by line
[21:05] <clivejo> I dont think we have kubuntu_xenial_backport branches
[21:05] <yofel> I don't think I actually ever ran the script myself, but that's just what I ran line by line (rewritten using variables)
[21:05] <yofel> right, those have to exist first
[21:05]  * clivejo nods
[21:05]  * clivejo is starting to understand the logic in the scripts
[21:06] <yofel> to create those: git-clone-all what you need, then do-all checkout the archive branch, then do-all checkout -b the backports one, then do-all checkout the backports branch
[21:06] <clivejo> before it was just a mess of strange looking commands that did some kind of black magic
[21:06] <clivejo> well I have all of plasma cloned locally
[21:07] <yofel> works too
[21:07] <clivejo> do I checkout xenial_archive and use that as start point to create xenial_backports?
[21:07] <yofel> yes
[21:07] <clivejo> :)
[21:07] <clivejo> Ill start that then
[21:07] <clivejo> might be more testers available for xenial
[21:10] <soee_> yakkety fails to install :/
[21:47] <clivejo> soee_: have you tried to upgrade a xenial install to yakkety?
[21:48] <soee_> nope
[21:48] <clivejo> ok
[21:48] <soee_> clivejo: ill test backports first
[21:48] <soee_> i tried to install YY in VB but installer is broken
[21:48] <clivejo> LOL
[21:48] <clivejo> YY is packaged and needs testing
[21:49] <clivejo> backports isnt :P
[21:49] <soee_> just push the magic button :D
[21:49] <soee_> and backports should be easy:)
[21:49] <clivejo> its not that magic !
[21:49] <clivejo> SHOULD BE!
[21:50] <clivejo> but it hould also be tested by more people on Yakkety!
[21:50] <clivejo> yofel: I have 4 new packages dont have a xenial_archive branch
[21:51] <clivejo> just checkout yakkety?
[21:51] <yofel> yes. (what other options do you have? ^^)
[21:52] <clivejo> move them to manual and do them later when Im bit more comfortable !
[21:53] <clivejo> so they are chectout out on yakkety alreadly
[21:54] <clivejo> so the new branch is kubuntu_xenial_backports ?
[21:54] <clivejo> with an s
[22:01] <clivejo> yofel: why would plasma-sdk 5.5.5 be unreleased?
[22:03] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/plasma-sdk/tree/debian/changelog?h=kubuntu_xenial_archive
[22:03] <clivejo> Im confused
[22:10] <yofel> clivejo: sure it was, just ubuntu2 not
[22:10] <yofel> that's not worth a SRU
[22:14] <clivejo> but the merge is generating two UNRELEASED versions
[22:14] <yofel> yes, and for backports, nobody cares
[22:15] <clivejo> this is normal?
[22:15] <yofel> (yet)
[22:15] <clivejo> oh ok
[22:15] <yofel> well, theoretically the second entry shouldn't really happen with dch...
[22:15] <clivejo> some it did properly and some it created two entries
[22:15] <yofel> but it's a side effect of merging branches
[22:16] <yofel> oh, the yakkety branch has the second unreleased version
[22:16] <yofel> so yeah, this is what I would expect to happen
[22:17] <clivejo> but I dont understand how xenial_archive has UNRELEASED
[22:17] <yofel> because I fixed all Vcs entries in xenial as well and edited a changelog entry for that?
[22:17] <clivejo> surely that should only contain what is mirrored in the archive?
[22:17] <yofel> UNRELEASED means "pending, unreleased change"
[22:18] <yofel> well it *does*, just + some extra changes
[22:18] <clivejo> Im just trying to get my head around it
[22:18] <yofel> that's what git is for, *working on a package*
[22:19] <yofel> we're not uploading every single commit we do to the yakkety release either, no matter whether it makes sense or not
[22:19] <clivejo> I understand why you put it in yakkety and kubuntu_unstable etc
[22:19] <clivejo> just xenial_archive thats bothering me
[22:19] <yofel> I think you make the mistake of assuming that xenial is immutable
[22:19] <yofel> I am still working on xenial
[22:20] <yofel> there will be other people still working on it
[22:20] <yofel> that's why there is a branch for xenial
[22:20] <clivejo> cause its LTS?
[22:20] <yofel> and not just one single packaging branch
[22:20] <yofel> cause it's still supported
[22:20] <yofel> it might happen that I do a commit on a wily_archive branch tomorrow - because it's still supported
[22:21] <clivejo> ah, so if you released an update to plasma-sdk for example, then you would want that new archive version to record the URL change in the changelog
[22:21] <yofel> yes
[22:21] <clivejo> think I got it
[22:22] <clivejo> dunno why but I thought that xenial_archive was now locked to mirror the archive
[22:22] <clivejo> ie only released versions
[22:23] <yofel> no, that's what tags are for
[22:23] <clivejo> ok, so regarding backports
[22:23] <clivejo> Ive two UNRELEASED entries
[22:23] <clivejo> thats ok?
[22:23] <yofel> for the archive I would say "fix it", but for the ppa, nobody reads the changelog, so just nvm it
[22:23] <clivejo> I kinda want to fix them :/
[22:24] <yofel> not that easy as this is how dpkg-mergechangelogs behaves... you would have to post-process the changelog after the merge to fix this
[22:24] <yofel> can be done, sure...
[22:25] <clivejo> but not worth the effort
[22:25] <yofel> but might need a custom changelog editor that squashes entries
[22:26] <clivejo> ok so there was 7 merge conflicts with the changelog
[22:26] <clivejo> I manually edited them and removed the second UNRELEASED entry, commit my changes
[22:27] <clivejo> in the script you git-buildpackage-ppa before you commit
[22:27] <clivejo> doesnt git-buildpackage-ppa check the git branch?
[22:27] <yofel> oh, yes I do
[22:28] <yofel> I guess I didn't get any conflicts, so merge auto-committed
[22:28] <clivejo> can I push first?
[22:29] <yofel> if you sure you're happy with what you have so far, sure
[22:29] <clivejo> as happy as I can be, with limited understanding!
[22:31] <clivejo> did you get a chance to fix that framework that was broken?
[22:32] <yofel> no, let me do that now
[22:33] <clivejo> Ill need to copy over xenial frameworks to the plasma staging to get these to build
[22:36] <clivejo> soee_: any other issues with FW5.21 on Xenial?
[22:36] <soee_> i can install them now and check how it go
[22:37] <clivejo> maybe wait until yofel fixes that conflict
[22:37] <soee_> ok
[22:37] <soee_> meanwhile  https://www.youtube.com/watch?v=k25X8RAjJ00
[22:38]  * clivejo ears start to bleed
[22:40] <clivejo> can you concentrate listening to that?
[22:43] <soee_> sure :)
[22:43]  * clivejo is just grumpy from lack of sleep
[22:47] <yofel> hm, we'll probably have to see what other conflicts we'll get :S
[22:47] <yofel> well, fixed in the kapptemplate 16.04 package
[22:47] <clivejo> uploaded to staging?
[22:48] <clivejo> both X and Y?
[22:49] <yofel> krunner yes, kapptemplate.... well, I can hack up a package that I'll have to do anyway 
[22:49] <yofel> this is one of the cases where I would really like a yakkety_wip branch, as I've no place to stage stuff that I need in the archive :/
[22:50] <clivejo> why cant you have a wip branch?
[22:50] <yofel> right now? policy
[22:50] <yofel> OTOH, we don't have one... 
[22:51] <yofel> so I guess I could just push a temporary branch
[22:51] <clivejo> LOL you're the boss now!
[22:51] <yofel> yeah, I kind of forgot that for the moment :P
[22:52] <clivejo> if it helps workflow
[22:53] <yofel> right, it just has to not disrupt it, but as the branch names are fixed, it shouldn't
[22:54] <clivejo> my internet is slooooowww tonight
[22:55] <yofel> mine's fine... except when I was trying to play some overwatch earlier, but I blame blizzard beta servers for that
[22:56] <clivejo> soee_: http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.6.3_xenial.html
[22:57] <mamarley> I'm trying to download updates for my Yakkety VM and that is going really slowly too.
[22:58] <clivejo> Im uploading to LP
[22:58] <clivejo> slowwly
[22:58] <mamarley> Also, macvtap doesn't seem to be compatible with wireless adapters.  In fact, it completely breaks the connection for the host system too.
[22:58] <soee_> mamarley: you were able to install YY in VB ?
[22:59] <mamarley> soee_: I am using KVM.  I installed from a daily image a few days ago.
[23:00] <yofel> ok, both uploaded
[23:01] <mamarley> Darn, I still can't install plasma-desktop on Yakkety because kactivities is at 5.18 instead of 5.21.
[23:01] <clivejo> eak
[23:02] <clivejo> FW PPA mustnt have been purged
[23:02] <yofel> oh right, that's FTBFS
[23:02] <clivejo> mamarley: did you install from FW staging?
[23:02] <clivejo> or Plasma?
[23:03] <mamarley> clivejo: I have both frameworks and plasma staging added on that system.
[23:03] <clivejo> remove FW
[23:03] <yofel> hm, how did stuff build without activities
[23:04] <clivejo> Scarlett built a few versions
[23:04] <clivejo> and I copied one that worked
[23:04]  * yofel git-clone-all's frameworks
[23:05] <yofel> and this is a typical night again. I answer a question, intend to fix one package and end up doing a dozen other things
[23:05] <yofel> *sigh*
[23:05] <clivejo> sorry :(
[23:06] <yofel> don't be. Happens all the time anyway :P
[23:06] <yofel> hm, nobody fixed the auto-remotes
[23:06] <yofel> yay, another thing to fix
[23:06]  * yofel does that first
[23:06] <clivejo> what remotes do you want?
[23:07] <clivejo> are you linking to the actual neon repo?
[23:07] <mamarley> clivejo: I ppa-purged staging-frameworks and it still complains about no kactivities 5.21.
[23:07] <yofel> that and debian is missing
[23:08] <soee_> uhm mamarleyyes that was problematic package when i tried to purgestaging frameworks from xenial
[23:08] <clivejo> kactivities-kf5 - 5.21.0-0ubuntu1~ubuntu16.10~ppa1 from plasma staging works
[23:10]  * valorie shuts down this machine to open up on the "new" one
[23:10] <clivejo> ok, upload is complete
[23:10] <clivejo> http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.6.3_xenial.html
[23:10] <clivejo> waiting on FW5.21 Xenial
[23:11] <yofel> I love how neon.kde.org has no hint on where the code is
[23:11] <clivejo> yofel: I think they locked it down recently too :/
[23:11] <yofel> clivejo: why does it work there and not in frameworks o.O?
[23:11] <clivejo> need to be a KDE dev to access
[23:11] <yofel> wth?
[23:12] <yofel> well, I am, so that'll work
[23:12] <yofel> but wait, that makes no sense
[23:12] <yofel> unless they locked down write access, which is ok
[23:12] <clivejo> I was trying get a clone to mess around with 5.6 
[23:12] <clivejo> see if I could get it working
[23:12] <clivejo> but anom access was blocked
[23:14] <clivejo> even read access
[23:15] <yofel> clivejo: can you clone git://packaging.neon.kde.org/forks/base-files
[23:15] <yofel> because I can
[23:16] <clivejo> I could for a few days
[23:16] <clivejo> then it was asking for a password
[23:16] <clivejo> I asked in Neon channel and told me I need dev access
[23:17] <clivejo> and Im not a dev
[23:17] <clivejo> I asked about how to get it and I need a sponsor
[23:18] <mamarley> clivejo: It says it can't find a package called "kactivities-kf5".
[23:18] <clivejo> mamarley: Im not sure what happened with it
[23:18] <yofel> clivejo: well can you clone it now or not?
[23:19] <clivejo> I think Scarlett merged with debian or something
[23:19] <clivejo> I can clone that repo
[23:20] <yofel> ok, so that's anon, wfm
[23:21] <clivejo> oh
[23:21] <clivejo> git clone git://packaging.neon.kde.org/plasma/kcm-touchpad.git
[23:21] <clivejo> works
[23:21] <clivejo> maybe I hit a nerve :/
[23:22] <clivejo> I wasnt very happy about needing dev to read access
[23:23] <yofel> ok, I have write access, was just using the wrong config
[23:23] <clivejo> can git access be restricted for reads as well?
[23:24] <yofel> maybe, but the CI has to access it somehow, and this IS an open source project...
[23:24] <clivejo> because thats the same url I was using
[23:24] <yofel> maybe it was just broken
[23:25] <clivejo> maybe!
[23:25] <yofel> now where was I before I got distracted
[23:25] <yofel> ah right, frameworks
[23:26] <yofel> ok, all but siduction works out of the box
[23:26] <yofel> yay me
[23:26] <clivejo> :)
[23:27] <clivejo> what is siduction?
[23:27] <yofel> santa's distro
[23:27] <clivejo> oh
[23:28] <clivejo> why do we need it?
[23:29] <yofel> we don't - it's just there
[23:29] <yofel> well, if the anon access would work I would appreciate it
[23:29] <yofel> but it asks me for a gitlab password
[23:29] <yofel> not that I don't have one, but that's not how anon works
[23:34] <soee_> ;D
[23:35] <soee_> https://youtu.be/Lj5BCHvlJOQ?t=173
[23:35] <yofel> ...
[23:37] <mamarley> I can't find kactivities 5.21 anywhere, so still no Plasma 5.6.3 on Yakkety. :/
[23:38] <yofel> hm, scarlett said that she fixed a bunch of things in frameworks, but I see a lot of ppa1
[23:38] <yofel> let me rebuild everything
[23:38] <mamarley> Thanks :)
[23:39] <yofel> kactivities is in the ppa, but it didn't build
[23:39] <clivejo> its ppa6?
[23:39] <mamarley> Where at?  I looked at the package details and couldn't find it.
[23:40] <yofel> weird, the qa page has it http://qa.kubuntu.co.uk/ppa-status/frameworks/build_status_5.21.0_yakkety.html
[23:40] <yofel> clivejo: ppa5
[23:40] <clivejo> https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-plasma/+packages?field.name_filter=kactivities&field.status_filter=published&field.series_filter=yakkety
[23:41] <yofel> right, I think a couple fixes are missing, so I'll just upload from git
[23:41] <clivejo> I copied these over to plasma-staging
[23:41] <clivejo> and its what I have installed on my system now
[23:41] <yofel> the uploading from git should fix it
[23:42] <clivejo> hopefully
[23:43] <clivejo> I dont understand how you can start with backports and then dev
[23:43] <clivejo> over my head
[23:43] <yofel> because it doesn't really matter
[23:44] <yofel> either you do stuff and merge backwards, or you do stuff and merge forwards
[23:44] <yofel> same result
[23:44] <yofel> oh right, I wanted to work on pkg-kde-tools
[23:44]  * yofel mirrors git