[07:20] hi, anyone responsible/knowledgeable of packinging online? [07:32] clivejo: registered KDE ID, and can now get to that notes page [10:01] soee_: ping [10:02] clivejo: pong [10:02] can you install plasma-desktop from staging plasma ppa and verifty that the kickoff recent documents now open ? [10:08] clivejo: yes it works fine [10:24] yofel: can I move the patched plasma-desktop package to backports PPA? [10:25] technically only after you copied to to -landing and did an upgrade test [10:26] I'm 99% certain that nothing will go wrong, but that's how things usually go wrong... [10:27] * mamarley is about to do an upgrade test. :) [10:28] mamarley: on xx? [10:28] Yep. It installed cleanly, rebooting now… [10:30] no need for rebooting [10:30] just run in krunner: killall plasmashell && plasmashell [10:30] My system needed a reboot anyway. [10:30] i see :) [10:31] Hmm, I actually don't have any recent documents in Kickoff. [10:38] Ive no way of doing upgrade tests myself [10:40] that’s why I ask soee_ to be my guinea pig :P [10:43] this korganizer bug is really annoying me now [10:43] use dolphin to open a random text file/image etc and it should add that to the recent docs [10:51] clivejo: Im currently upgrading from 15.10 to 16.04 if you need something checked... [11:45] Hey folks === fregl_ is now known as fregl [12:29] yofel: looks like Debian are using the kdeconnect packaging for the kf5 version - http://anonscm.debian.org/cgit/pkg-kde/kde-extras/kdeconnect.git/tree/debian/changelog [12:29] for anyone with that panel autohide/can cover issue https://quickgit.kde.org/?p=plasma-workspace.git&a=commit&h=e1ae057fef297b46d17256d497e8e2f4e24c1264 [12:30] should we drop the kdeconnect-plasma and sync with them again? [12:30] lol. quiet for ages [12:32] clivejo: probably, I have no idea how kdeconnect works, so your guess is as good as mine [12:33] well I think the reason we split was that kdeconnect was the KDE4 version and kdeconnect-plasma was KF5 [12:35] but as to why kdeconnect-plasma depends on kdeconnect is beyond me! [12:37] sorry it Recommends: kdeconnect === rdieter_ is now known as rdieter_work [14:01] Maybe worth trying to ask developer; ) === Guest51294 is now known as adrian [19:34] !info kdeconnect [19:34] kdeconnect (source: kdeconnect): connect smartphones to your KDE Plasma Workspace. In component universe, is optional. Version 0.8-0ubuntu5 (yakkety), package size 50 kB, installed size 202 kB [19:35] !info kdeconnect-plasma [19:35] kdeconnect-plasma (source: kdeconnect-plasma): connect smartphones to your KDE Plasma desktop. In component universe, is optional. Version 0.9+git20160315-0ubuntu1 (yakkety), package size 354 kB, installed size 1641 kB [19:35] Maybe ask Riddell about it if you [19:35] have problems [19:36] Ive been talking to him about it [19:36] just wondering what to do about it [19:36] And you know why we have this two packages? [19:36] yes [19:37] at the time of the kf5 port Jon spoke to the dev and though the new version was going to be called kdeconnect-plasma [19:38] but that didnt happen [19:39] But we renamed it anyway? [19:39] Debian didn’t package the kf5 version until February this year, and continued to use the upstream package name [19:39] Or the *-plasma is some meta package? [19:40] the plasma one is KF5 port [19:40] And we obviously don't need both no? And we have them only because of Debian? [19:40] kdeconnect in our archive should still be KDE4 [19:41] we have both cause we packaged it first [19:41] I'm confused :( [19:41] why? [19:42] Jonathan created the kdeconnect-plasma packaging after speaking to the devs working on it [19:42] the new port was supposed to be named kdeconnect-plasma [19:43] but for some reason it wasnt and they just used the same name [19:44] what Im trying to work out is it if we fall back the sync in line with Debian will that affect users still on KDE4 [19:44] is that still a thing? [19:44] in Kubuntu land [19:45] Yofel need to say something about it :) [19:45] Clivejo and Apps are hard to finish? [19:47] ish [19:47] minuet needs a 3rd party lib called drumstick packaged so it can continue building [19:48] spectacle needs purpose packaged to add in the sharing features [19:49] that just had a RC, so Im waiting on the actual release of that [19:49] KDE PIM has a major bug for me [19:49] :/ [19:49] but Im starting to think thats unique to me [19:50] Is it known and reported ? [19:50] Its reported, but noone can recreate it [19:50] it seems to be related to my Kolab account [19:51] when I add my Kolab account korganizer and its reminder service crash [19:51] Hmm.. I never used Kolab so can't help here. [19:51] Did you tried it without Kolab integration? [19:51] yes, it works fine with it [19:51] without it [19:52] kdesdk-kioslaves I have NO idea what wrong with that [19:52] Maybe also worth asking Jonathan for some feedback [19:53] krdc needs install files fixed [19:53] acheron_uk: do you want to look at that? [19:55] and then I need to do the wonderful translations [19:55] why cant you all just speak English :P [19:56] * clivejo pokes @marcinsagol with a big stick [19:56] That would be boring :) [19:57] but you type it so well, why do you need your desktop in Polish? [19:57] I'm just local patriot :d [19:58] * clivejo feels lost without PIM [19:59] I wanted to add a reminder to start kde-l10n tomorrow morning when internet is less busy and cant create a To-do item === palasso_ is now known as palasso [20:25] clivejo: look at what sorry? [20:28] ummm. already done then? [20:28] yeah I pushed something [20:28] not sure if it will fix it! [20:28] was wearing my OSM hat there! [20:29] seems to have built at least [20:30] got some missing files :) [20:30] still? or you mean all fixed? [20:32] https://launchpadlibrarian.net/261635560/buildlog_ubuntu-yakkety-amd64.krdc_4%3A16.04.1-0ubuntu1~ubuntu16.10~ppa5_BUILDING.txt.gz [20:32] unsure where to put those .h files# [20:32] meant to go though those packaging notes and other stuff today, as somehow it never quite happened [20:33] they are already out of date due to our Debian to Launchpad move [20:34] yeah, I gathered [20:35] .h files listed as missing? [20:35] they are files being built, but not installed anywhere [20:40] so I see. [20:41] I dont understand why -./usr/lib/x86_64-linux-gnu/libkrdccore.so is listed [20:41] thats listed in not-installed [20:45] think I'll need to read up on installing files and library symlinks before I can really comment on that. [20:46] really only learnt so far what I've needed to do some specific things, and so have some glaring gaps [20:46] I thought that the not-installed file used a different format [20:47] ie ./usr/lib/*/libkrdccore.so [20:47] * acheron_uk shrugs [20:50] oh well, Ill try that and see [20:52] I kinda wish KCI wouldnt build a project if and upstream package failed [20:52] hopefully I can get stuck into some docs/guides tomorrow. [20:53] that reminds me, suppose I better un-ignore the kubuntu-ci messages [20:54] LOL [20:54] or join its channel if they annoy you [20:54] #kubuntu-ci [20:55] I dont mind them here, gives me the chance to notice things [20:55] ah yes I saw that the other day [20:56] hopefully we will get on top of it and it wil become a useful tool again# [20:57] I miss the old project neon [20:58] I wasnt here for it [20:58] that was nice being able to have a separate neon install and session co-installed with the normal plasma [20:59] I can see how a working CI system would help with dev [20:59] well, I wasn't 'here' here, but I insalled it and used it occasionally when I was curious [21:00] I like new software [21:00] but my main reason for learning how to package was to try and help package Kolab on Ubuntu! [21:01] I couldn't stick with the LTS release until it expired lol [21:01] but I kinda got side tracked [21:01] !info kolab [21:02] Package kolab does not exist in yakkety [21:02] indeed [21:02] ok. not what I thought it was then obviously [21:02] but it should be there! [21:03] it like an open source M$ Exchange [21:03] a lot of things should to be honest [21:04] Kolab and KDE PIM are supposed to be working together to bring it to the desktop [21:05] but its so fickle! [21:05] o/ sick_rimmit [21:06] Yay clivejo [21:06] Hi there [21:06] valorie: ping [21:06] I would like some more up to date debian science stuff, but doubt that will ever happen [21:06] sick_rimmit: did you get my message earlier? [21:06] debian science suff? [21:06] stuff [21:06] clivejo: No sorry [21:07] sick_rimmit: do you need any help preparing for the Dojo? [21:07] I definetly need help doing it [21:07] may I see the slides? [21:07] Mostly someone on hand to field questions, and correct me [21:07] Sure hang on [21:07] let me look em out [21:09] clivejo: https://wiki.debian.org/DebianScience/Physics a lot of that not even close to being up to date [21:10] are they in Ubuntu? [21:10] just out0dated? [21:10] Right got em [21:10] a lot, but same out of dateness [21:10] they are on Google Docs [21:10] you should apply to maintain them [21:11] dojo = 7pm UK time? [21:12] find the project in Launchpad, open a bug to Update and take ownership of the bug, upload the new version to your PPA and find a sponsorer to upload to the archive [21:13] maybe one day. step at a time and all that.... [21:13] LOL [21:13] baby steps :) [21:14] you seem to have a good understanding on how packaging works [21:14] the parts of it I've tinkered with. [21:14] if debian is up to date, just sync their packaging [21:14] as said, there are some big black holes though. [21:15] but Debian can be slow in certain areas too [21:15] actually, probably more holes than anything [21:15] yesp, debian is snail pace in some areas [21:16] been a while since I looked where their plasma has got to actually [21:16] they actually doing well on that [21:17] and looks like my sid VM has been zapped in a clearout, so no updating that to see [21:17] Maxy is working away on it [21:17] good :) [21:20] ok, krdc is totally ignoring the not-installed file [21:22] that's the sort of thing I'm not sure on. do you go with what works sayign what the hell? or do you try to resolve anyway? [21:23] so far I've just done things for myself, and working is fine, slightly bodged and/or with a few errors or not. [21:24] I was taught to use prefix of ./ in the not-installed file [21:25] but it didnt have that originally so I just used what was there [21:25] Ive added the prefix now see it that work :/ [21:25] trail and error [21:26] sometimes the only way. [21:27] Maxy removed the prefixes in this commit - http://anonscm.debian.org/cgit/pkg-kde/applications/krdc.git/commit/?id=c57792680ff47f3cf97840bed1ce370fd6686122 [21:27] well, as quick a way as any anyway [21:27] not sure why [21:28] I wonder is it a new Debian thing [21:31] acheron_uk: if you can spot why some of those KCI builds are failing and want to fix them, just paste the git diff [21:31] unstable is using the kubuntu_unstable branch in LP [21:33] a lot of them are LP acting up [21:33] and causing a chain reaction [21:35] lovely. squinting at buildlogs playing 'spot the failure' [21:36] that looks frustrating on KCI [21:36] its hard on the eyes! [21:36] there is actually a tool in KCI for parsing the logs [21:36] just as well [21:38] see down the left menu there is a link "Parsed Console Output" [21:38] that can usually tell you what happened [21:41] also a project can fail if one of the two builds fail (ie i386 fails, but amd64 is successful) [21:44] ah, so for breeze for e.g. was a couple of unpackaged files again? [21:45] -./usr/lib/x86_64-linux-gnu/cmake/Breeze/BreezeConfig.cmake [21:45] -./usr/lib/x86_64-linux-gnu/cmake/Breeze/BreezeConfigVersion.cmake [21:46] yep [21:46] do you want to fix that? [21:47] If you can go through how [21:47] sure [21:47] first how do you think [21:49] well, presumably need to know if they want to be installed or ignored? [21:50] hmmm, I missed rick [21:52] add to https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/breeze/tree/debian/breeze.install?h=kubuntu_unstable [21:53] nice to see more and more green [21:56] clivejo: or perhaps not. [21:57] hummm Im not sure myself! [21:58] part of me wants to put them in a -dev package [21:58] makes me feel better [21:59] there is no breeze dev package. nor has there been or needs to be as far as I know [22:00] https://quickgit.kde.org/?p=breeze.git&a=commit&h=1a38234564fcf30625c22d719c706236e97b2e62 [22:00] ah [22:00] so they need to be installed [22:01] I guess pop them into breeze.install [22:01] do you know about the wrap-and-sort tool? [22:02] https://quickgit.kde.org/?p=breeze.git&a=commit&h=7996fb97d314f64115b2d712bb93e83988ac99f8 [22:04] not convinced that needs to be installed? [22:09] wrap-and-sort = nope [22:12] apt install devscripts [22:12] its a handy tool for sorting install files so you dont have to sort them manually [22:14] they need to be installed [22:14] the issue is where [22:14] usually these things go in a -dev package [22:15] and then other packages depend on breeze-dev package in the control file [22:15] but Id need yofel's help on that [22:16] not convinced, but could be wrong [22:22] for example, cmake files are provided by this package !info libkf5declarative-dev [22:22] http://packages.ubuntu.com/yakkety/amd64/libkf5declarative-dev/filelist [22:22] !info libkf5declarative-dev [22:22] libkf5declarative-dev (source: kdeclarative): development files for kdeclarative. In component universe, is optional. Version 5.18.0-0ubuntu1 (yakkety), package size 18 kB, installed size 131 kB [22:23] thats what makes me think they should be in a -dev package [22:23] yes, they should. [22:24] Im asking for advice in Debian IRC [22:26] just had a peek in the neon archives, and they have a -dev package for builds done after those files were added [22:26] acheron_uk: have you a link? [22:26] it's the Debian Way [22:27] http://archive.neon.kde.org/dev/unstable/pool/main/b/breeze/?C=M;O=A [22:29] http://packaging.neon.kde.org/cgit/plasma/breeze.git/commit/?h=Neon/unstable&id=9d38004f2eba3b7dd5a5fac5fe2f86240c4cdb43 [22:29] acheron_uk: Debian agree too [22:29] needs a new package breeze-dev [22:29] ah yes [22:31] so you need to define the package in the control file and then tell it the files it needs to install into that new package [22:31] wasn't convinced had suddenly sprung a dev package, but obviously it has [22:32] should be simple(ish) for that [22:32] well this is how things evolve ! [22:33] when you start to see other packages looking for BreezeConfig.cmake, you'll know what provides it :) [22:33] indeed [22:33] also handy to know, as breeze is a package I sometimes hack and rebuild [22:34] what do you hack in it? [22:34] so you need to make the changes to kubuntu_unstable from LP [22:35] more compact kwin decoration - getting rid of the annoying colour line separator on the deco when using different colours [22:37] acheron_uk: basically this commit - http://packaging.neon.kde.org/cgit/plasma/breeze.git/commit/?h=Neon/unstable&id=9d38004f2eba3b7dd5a5fac5fe2f86240c4cdb43 [22:37] but add a changelog entry [22:37] saying what you have done and why [22:39] that seems straightforward [22:45] how are you getting on? [22:46] in what sense? can't actually do anything as have no access [22:47] if you make the changes and send me the git diff Ill commit it for you [22:47] OK. I'll do that [22:50] it you install pastebinit you can just type "git diff | pastebinit" [22:50] it will generate a URL you can copy and paste to me [22:51] just a sec then [22:51] :) [22:54] if I can remeber how to add a file in git [22:56] I use a tool called git gui [22:57] * clivejo has a terrible memory for commands [22:57] I can stage files to commit, commit and push all from that UI [22:58] its nice to see what you are actually changing, in pretty colours! [23:03] hmm. empty diff. [23:03] did you commit? [23:04] should I have done [23:04] nope [23:04] git diff shows changes from the last commit [23:05] oh, well I did [23:06] Revert the commit "git reset HEAD~" [23:07] and see if "git diff" has output [23:12] had to backtrack. how to make sure the new breeze-dev.in is included in the diff? [23:13] dont add the files [23:13] just do a git diff [23:13] so git checkout kubuntu_unstable, edit the files and do a git diff [23:13] in that case http://paste.ubuntu.com/16696652/ [23:14] you are missing the new file breeze-dev.install and your changelog entry [23:15] that's what I meant [23:17] presumably the new file is not tracked [23:18] did you add it? [23:19] no, you said not to [23:20] humm I dunno [23:21] can you just copy and paste your changelog entry? [23:23] which changelog? [23:23] for your changes [23:24] all I have ins breeze-dev.install added and control modified [23:24] did you write a new changelog entry? [23:25] no. thought you justs wanted the diff on the 2 files [23:26] think it's a bit late foe me and this lol [23:26] no prob [23:26] what I was trying to ask for was the entire commit for the package [23:27] so I could just push it [23:27] what would you write for the changelog entry [23:27] so would add to 1st entry on https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/breeze/tree/debian/changelog?h=kubuntu_unstable [23:28] what Im trying to point out is that the changelog in kubuntu_unstable is released [23:29] once we release to the archive, you shouldnt change it [23:29] so we need to make an UNRELEASED entry [23:30] can you give me a description for this? [23:30] in your own words :) [23:32] um [23:32] sorry, am I being evil [23:32] ha, finally the truth! [23:33] <3 [23:33] oddly, I can cope with complicated physics, but this hurts my head [23:33] LOL yofel is way worse! [23:34] he links to pages and pages of Debian instructions! [23:34] great for sending you to sleep [23:35] if I was doing it for myself I would put "add new dev package for cmake config files" [23:36] seriously need to re-read up on git as well. [23:37] acheron_uk: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/breeze/commit/?h=kubuntu_unstable&id=32ca10e4c4415c4cde5ded920c2eddd4e4374cd5 [23:41] what I would have like to have done if git had cooperated ;) [23:41] I know, and its getting late here so I understand when things dont go according to plan [23:42] did you look at git gui ? [23:43] yes, not exactly intuitive [23:47] not a great fan of git to be honest, even with a gui [23:49] it takes a while to get used to [23:50] but it is a useful tool for this kind of work [23:52] I'll work it out tomorrow when I have more patience for it. Bound to be something obvious to add that to the diff [23:54] OK. Night I think. Thanks for being patient [23:55] no problem [23:55] valorie: I see xen is back to his usual actions, in the mailing list. This sort of drawn out response that soon esclates to messages such as the one he sent to the irc mailing list is what caused him to be banned from kubuntuforums [23:55] right, I'm planning to mod him on kub-devel [23:57] 'git add' and 'git diff --staged' maybe [23:57] heh was thinking the same thing once I got home from work [23:57] as soon as I say night I think of something [23:57] LOL [23:57] wait until you start dreaming about it! [23:59] * acheron_uk shrinks back in horror [23:59] ouppss [23:59] shouldnt have told you that! [23:59] scare you off