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