[00:01] I think so.. [00:02] "I swear pim is cursed" - you only realized that now? XD [00:02] it's been cursed since 4.5 or so [00:04] :( theres KCI gone for 20 hours or more :( [00:05] yofel: should I add kubuntu_unstable branches for those two new packages in debian git? [00:05] go ahead [00:05] stable too? [00:13] yofel: stable too? [00:13] hm.. I guess so.. [00:14] sorry, Im tired [00:14] cant think [00:16] dito -.- [00:16] ok done [00:16] if one of you could poke KCI to build those [00:16] Im gonna go to bed [00:17] night all [02:33] ok all blogged out. and need a break. oh jobs that need kicked. will do that. [05:43] valorie: What's this new distro list meant to cover that wasn't covered by either the packager or release lists? [06:38] ScottK: social issues/upcoming stuff larger than immediate packaging stuff -- on both sides [06:48] yofel: Qt 5.6 delayed again roughly two weeks. it's probably obvious by now that we won't get it, but just saying it aloud. backport requests to 5.5 welcome, I've been trying to help the multi-monitor use case with several new backports. [07:30] yofel, sgclark, or clivejo -- should I ppa-purge ppa:kubuntu-ppa/staging-kdeapplications and then add ppa:kubuntu-ppa/staging-misc and upgrade (to my xenial box)? [07:30] or can I just remove ppa:kubuntu-ppa/staging-kdeapplications [07:30] to make the best test for y'all [08:30] Hi, I'm trying to create a boot-stick. Neither Start Disk-Creator nor Unetbootin does the task. I get "BOOT ERROR" [08:30] This is MAH Bootstick!! [08:30] What does your MB use to boot? [08:31] Oh and Help in #kubuntu please :) [08:32] I created a lot of sticks the last hours: Ubuntu 15.10 Kubuntu 15.10 Lubuntu 15.10 None of those works [09:01] Good morning. === mgraesslin is now known as oom_killer === oom_killer is now known as mgraesslin [12:02] Hey folks [12:03] hiho BluesKaj [12:07] Hey soee [12:16] soee: can you test apps 15.12.1? [12:17] clivejo: sure but later at home, here @ work im on Wily [12:18] and also misc staging too, we need these packages tested so we can get them into xenial archive! [12:18] http://scarlettgatelyclark.com/2016/kubuntu-kde-where-oh-where-have-i-been-busy-i-say/ [12:18] anyone testing Xenial, please test those ! [12:18] contains Frameworks 5.18 Plasma 5.5.4 Applications 15.12.1 [12:20] come on wily, builds on xenial, why not you! [12:20] clivejo: Frameworks and Plasma 5.4.4 have been tested already [12:22] hmmm [12:22] wily mbox i386 failed to build [12:31] stupid thing [12:33] is plasma 5.6 available in the ppas? [12:34] hey clivejo, how goes it? [12:41] clivejo: what's the state with kdepim? [12:41] I still get dpkg: error processing archive /var/cache/apt/archives/libkf5akonadicore-bin_4%3a15.12.1-2ubuntu1~ubuntu16.04~ppa2_amd64.deb (--unpack): [12:41] trying to overwrite '/usr/bin/akonadiselftest', which is also in package kdepimlibs-bin 4:15.12.0-0ubuntu1~ubuntu16.04~ppa3 [12:50] * yofel finishes reading scarlett's blog post and tries agian [13:18] staging-misc still throws the overwrite error [13:21] clivejo: Test which applications? [13:33] yofel at this point point kdepim will not even build. I am inclined to skip it. [13:33] +1 [13:34] other than that we are good to go, unless some testers arrived and has said otherwise [13:36] any word on when and which ppa plasma 5.6 will be available? [13:37] BluesKaj: not anytime before our current work is in archive. sorry [13:39] np sgclark, I just read JR's announcement on kde dot news, but there were no links, so i thought ask here [13:40] i'd ask [13:50] sgclark: if you want me to help you may want to throw me more than https://launchpadlibrarian.net/245559807/buildlog_ubuntu-xenial-amd64.kdepim_4%3A15.12.1-1ubuntu1~ubuntu16.04~ppa5_BUILDING.txt.gz [13:50] at least i'm going to need to know exactly which ppas you're using for that [13:50] ah sorry. just woke up [13:50] tsdgeos: all in here https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-misc [13:51] ok [13:51] thankyou [14:20] sgclark: can you copy in prison and try it? [14:21] clivejo: from ci ? no, we need only packages going to archive. [14:21] whyis it copied from ci? perhaps it needs to be packaged in xenial_archive? [14:22] its supposed to be in frameworks, no? [14:23] it was not with frameworks. it had a git version [14:24] I dunno, debian git has it as a framework - http://anonscm.debian.org/cgit/pkg-kde/frameworks/prison.git/ [14:24] I am busy with family right now, can't look for another hour or so [14:25] oh maybe not [14:26] its not found in the staging apps build [14:29] +1 for stripping out PIM, if my opinion counts to anyone :P [14:29] that version is odd. Is it not release upstream I wonder? [14:29] though it is an optional dep, it should not FTBFS pim in theory. [14:30] Its optional and not install in the apps staging PPA [14:30] which rules it out [14:30] correct. because it is apparently not released with the kf5 we have. [14:31] anyway, I suspect it is build order maybe. possibly. [14:40] finished 15 hours ago [14:40] maybe poke it to rebuild? [14:40] maybe something it needed wasnt published 15 hours ago [14:43] Ill retry it :/ [15:27] clivejo: tsdgeos: I am fairly certain I found the problem. akonadi-calendar was built with an old akonadi. I will bump version req and rebuild. cross your fingers. [15:33] hiho [15:33] clivejo: if i have 5.5.4 and Framework 5.18 installed shall i test only apps ? [15:35] sgclark: staging-application is the one to be tested ? [15:36] soee staging-misc. but wait a few I may very well have pim fixed soon [15:36] well mostly fixed, still no kolab [15:39] sgclark: shall we deal with this pim? You wrote on blok it might be broken again [15:39] *blog [15:41] sorry I do not understand. [15:41] I think I found the problem and in the middle of trying to fix. [15:44] sgclark: "" [15:44] Upstream is making massive [15:44] sgclark: ok, plz keep me updated on whether i need to work on this or not [15:44] changes and ABI is broken. Aka, even if we manage to get the builds green, there is still large chances for crashy behavior. [15:45] soee: yes. but I think I found the problem. and working on fixing it. [15:45] I am not sure what you are trying to tell me sorry. [15:49] sgclark: ok. ping me when it is read for tests [15:50] will do === JoseeAntonioR is now known as jose [17:11] git pull [17:13] git checkout working_branch :) [17:14] nope [17:14] kubuntu_unstable :P [17:14] batch patch and push [17:14] any response with this ffe ? [17:14] yup [17:15] spoke to Iain Laney who commented on the bug [17:15] with what result ? :) [17:15] he wants it all to be uploaded in one batch [17:15] i see [17:15] so sgclark has been working on putting all the packages into a misc PPA [17:16] are we ready for it ? or wating for Scarlett to fix PIM ? [17:16] and everything has built, bar PIM [17:16] I think sgclark was taking one last stab at PIM [17:16] she is working on fix [17:16] correct [17:16] if it doesnt work, we may just ommit it [17:16] was gonna try kolab as well, but I dont have a clue what you did here [17:17] I need to revert my last kolab commit [17:17] to our branch [17:18] btw. after this upload we can pust into archive also 5.5.5 wen it is ready ? [17:18] *put [17:19] soee_: nope [17:19] oh ? [17:19] archive is frozen [17:19] 5.5 is a point release? I think we can actually [17:19] yes, and 5.5.5 is jsut bugfix release [17:19] oh [17:20] we can't put any new features, bug fixes ok [17:20] I finda took from Phil it wouldnt make it [17:20] so this one yes and Frameworks 5.19 in backports [17:20] but lets try and get our current batch inarchive shall we. [17:20] my bad [17:20] * sgclark goes back to fighting with kolab [17:20] sgclark: I reckon just remove PIM [17:21] we need the rest in the archive [17:23] then we can concentrate on apps 16.04 [17:24] in plasma 5.5.5 missing systray icons issue is finally fixed, and it is last bugfix in 5.5 series so you should put is in main repo after you finish ffe :) [17:24] they werent released yet no ? [17:25] soee_: source tars are available, but we havent done anything yet [17:26] actually 5.6 beta is out :) [17:26] but they wont make into 16.04 anyway [17:26] nope [17:26] atleast not with normal updates [17:26] so i would say: first Frameworks 5.19, than Plasma 5.6 than Apps 16.04 [17:27] I dont think those can go into the archive [17:27] need to ask Phil [17:28] no no ;) [17:28] just backports [17:28] sgclark: if I have time later, will I stage plasma 5.5.5? [17:29] no please. let get this stuff in archive. do not do anything until it is. [17:29] ok [17:30] is there anything else I can do? [17:30] just keep up the ci work, that is great help [17:30] ad will make 5.5.5 a cinch when the time comes [17:32] sgclark: how could I roll back kubuntu_unstable to stable? [17:32] http://anonscm.debian.org/cgit/pkg-kde/kubuntu/libkolab.git/log/?h=kubuntu_unstable [17:33] I think gitk has an easy way to reset to x commit [18:25] I now have vanilla Xenial from today's daily iso installed onto a USB flash drive, all updates applied, no PPAs added yet. Running OK so far on Acer Aspire ZS600. Let me know if there's something I can test . [18:26] genii: yes there will be a lot [18:26] stay tuned for info :) [18:26] Will do :) [18:26] I am going to connect to IRC on that box now through webchat [18:29] * genii-xenial sips [19:01] !info ring [19:01] Package ring does not exist in wily [19:02] arg [19:03] oh that is old [19:03] apparently not - https://ring.cx/ [19:04] not ring, kmime build lol [19:04] oh, my bad! [19:06] sgclark: any luck with PIM? [19:06] making progress. [19:07] getting kolab going as well while I am at it. [19:07] fairly certain the versions you were trying needs akonadi-next [19:08] which is unreeased and far in the future [19:08] unreleased [19:08] * genii-xenial sips [19:08] Hi folks [19:09] hi sick_rimmit [19:09] howdy [19:09] Is everything cool with the FFE ? [19:09] well the libkolab version I was working on is the lastest from Kolab Systems [19:10] but its for their server side stack and built using libcalendaring [19:12] sounds scary. sticking with merging unstable [19:13] so I found the files it was looking for in the PIM stack [19:13] and it seemed to build on LP [19:13] Can anyone advise me on how to go about writing for the Ubuntu Weekly Newsletter [19:14] but kdepim doesnt like it :/ [19:15] Doh! I got it sorry [19:16] sick_rimmit: Perhaps talk to pleia [19:16] sick_rimmit: try talking to https://launchpad.net/~lyz [19:17] wow, how did libkscreen get so far out of snyc with debian! [19:17] yeah pleia2 can find her usually in #xubuntu channel [19:17] clivejo: my guess is you in wrong repo [19:18] http://anonscm.debian.org/cgit/pkg-kde/plasma/libkscreen.git [19:18] do a diff on ours against master [19:18] we have different install files etc [19:19] Whoa, two Yippee in a row [19:22] wow no debian merge on that either. how did you stumble on that clivejo? guess we need to do that [19:22] pets KCI, good boy! [19:22] lol [19:22] sgclark: fixing KCI [19:22] thought it was a symbols issue [19:23] but then realised it was something more! [19:23] can you do it? I have to still do kde-l10n or we can switch :P [19:23] Ill try it, need to learn [19:23] which one lol [19:23] but I will probably need a hand [19:23] libkscreen [19:24] ok, sure I will be here all day [19:24] I have it cloned here and been looking at a merge [19:24] lots of problems [19:24] keep everything debian [19:25] one question is why do we have libkf5screen7? [19:25] the only thing to be wary on is packaname differences in deps [19:25] I have not even looked at that and would not know. [19:25] one thing though is our packaging for master? that will make a difference [19:26] so go with debian changes first [19:26] what do they have 6? [19:26] debian only have 6 [19:26] we have 6 ^ 7 [19:26] & [19:27] 6 and 7 ? huh? lol [19:27] the 6/7 matches the soversions [19:27] so it needs to match the tar we are building [19:28] -- Installing: /«BUILDDIR»/libkscreen-5.5.4+git20160302.2116+16.04/debian/tmp/usr/lib/x86_64-linux-gnu/libKF5Screen.so.5.6.90 [19:28] -- Installing: /«BUILDDIR»/libkscreen-5.5.4+git20160302.2116+16.04/debian/tmp/usr/lib/x86_64-linux-gnu/libKF5Screen.so.7 [19:28] -- Installing: /«BUILDDIR»/libkscreen-5.5.4+git20160302.2116+16.04/debian/tmp/usr/lib/x86_64-linux-gnu/libKF5Screen.so [19:28] 7 is plasma 5.6, isn't it? [19:28] well the lib inside said tar [19:28] right, 5.6.90 [19:28] I think so yofel. my guess is he has unstable [19:29] wait, that's plasma 5.7-dev o.O [19:29] sgclark: right [19:29] uh [19:29] Im trying to fix KCI unstable [19:29] clivejo: be sure you are working in kubuntu_xenial_archive [19:29] oh do the merge in the above branch, not unstable [19:29] https://launchpadlibrarian.net/245143871/buildlog_ubuntu-xenial-amd64.libkscreen_4%3A5.5.4+git20160302.2116+16.04-0_BUILDING.txt.gz [19:30] whatever you do in _unstable is completely irrelevant for xenial [19:30] forgete that for now [19:30] but when I looked at the packaging, we have a lot of diff with debian [19:30] do a merge in kubuntu_xenail_archive and we will deal with k [19:30] so? [19:30] do what scarlett says [19:30] * yofel hides again [19:30] hah [19:31] Im just wondering why [19:31] we wont be next release. but yes this release there were some that are major deffrences. go with debian. [19:31] ugh can't type [19:31] or spelll [19:32] lol [19:32] debian have a libkf5screen-bin.install and we dont [19:32] things like that [19:32] use theirs [19:32] different tests etc [19:32] debian debian debian [19:32] thats why I asked [19:32] :P I know [19:33] ok :) [19:33] Im just explaining why Im asking! [19:33] yep. np. [19:34] but if I merge into xenial archive wont that upset the misc staging you are working on? [19:34] just remember to add breaks/replaces where files end up in different binaries [19:34] maybe one of you guys should look at it! [19:34] Im confusing myself [19:34] we can once you're done with it ;) [19:34] Ill break it [19:35] you can fix it after that [19:35] clivejo: git checkout kubuntu_xenial_archive then git merge master [19:35] yofel: you say the kindest things [19:35] fix conflicts [19:35] push [19:35] viola [19:36] ;P [19:36] two small little words "fix conflicts [19:36] fix conficts by deleting head and keeping master [19:37] simple :) [19:37] but debians symbols are only for amd64 [19:38] ours are both [19:38] keep theirs. batchpatch later if you have to [19:38] http://kubuntu.org/news/kubuntu-packaging-party/ [19:39] Tis going to be a blast ;-) [19:40] sgclark: that para in the mail isn't english is it? [19:43] err my cat took out my internet [19:44] so many UNRELEASED entries in these changelogs [19:44] what do I do with them? [19:46] nothing [19:46] depends... [19:47] I'll tell you after I see the result [19:47] well maxy's I want to delete [19:47] don't [19:47] libkscreen (4:5.5.4-2~) === ejat_ is now known as ejat [19:48] just base on that. -2~ubuntu1 might not be a common version, but a valid one [19:49] so what about libkscreen (4:5.5.4-0ubuntu1) UNRELEASED; urgency=medium [19:49] and libkscreen (4:5.5.1-0ubuntu2) UNRELEASED; urgency=medium [19:49] and libkscreen (4:5.5.1-0ubuntu1) UNRELEASED; urgency=medium [19:49] merge contents into the merge changelog. All of them if they're right behind each other [19:49] actually, let me clone that [19:50] that looks weird [19:50] this whole package is weird [19:50] how did THAT happen o.O [19:50] what? [19:51] the changelog [19:51] I have NO idea [19:51] cant make head nor tails of it [19:51] that looks like people running 'dch -i' wich debchange set to the old behavior [19:52] which is not what you want to do [19:52] did I do it? [19:52] * Fix unstable build to reflect the .so version of 7. [19:52] why is that in _archive ?!? [19:53] oh, right, that was the package that got merged, then downgraded to work again later on [19:53] urgh [19:53] the changelogs got left in to not conflict with CI I think [19:54] clivejo: please do the merge, then I'll rewrite the changelog [19:54] just leave the changelog? [19:54] just put something there and commit it. I'll rewrite it anyway [19:55] If there gets to be anything to test, please ping this name, the genii-xenial box is next to me but I'm using this one as my primary [19:57] genii will do [19:57] ok yofel, push [19:57] pushed [19:57] now theres a surprise [19:57] leave it, I'll break it again anyway [19:59] ok so my internet is going wonky. working on l10n though. [20:00] clivejo: you didn't update the breaks/replaces [20:00] kscreen_backend_launcher moved, meaning the breaks needs to be << 4:5.5.4-2~ [20:01] otherwise fine [20:02] so what does it break? [20:03] libkf5screen6 ? [20:03] yes [20:03] but only the archive version? [20:03] 4:5.4.3? [20:03] +++ b/debian/libkf5screen-bin.install [20:03] +usr/lib/*/libexec/kf5/kscreen_backend_launcher [20:03] --- a/debian/libkf5screen6.install [20:03] -usr/lib/*/libexec/kf5/kscreen_backend_launcher [20:04] we have people using 5.5.4 according to the changelog, so I'm using the last possible debian rev as base [20:04] well Im using it [20:04] from the PPA [20:05] right, so you'll probably appreciate not getting an error ;) [20:05] I would [20:05] so how do you write the breaks to take that into consideration? [20:06] as I said above, it now says libkf5screen6 (<< 4:5.5.4-2~) [20:07] 4:5.5.4-0ubuntu1~ is lower than that [20:08] pushed, I just got rid of all the surplus changelogs [20:08] oh, needs more fixing [20:09] debian/libkf5screen6.install:usr/share/dbus-1/services/org.kde.kscreen.service [20:09] debian/libkf5screen-bin.install:usr/share/dbus-1/services/org.kde.kscreen.service [20:09] that's just plain uninstallable [20:10] wth is --- a/debian/meta/upstream_scm.json [20:11] meta? [20:11] just wondering as the remaining debian diff shows that as deleted [20:14] clivejo: _archive and _unstable fixed [20:15] that needs uploaded into misc staging now? [20:15] yup [20:15] cause the old version must have big problems! [20:15] really? [20:16] the merge commit doesn't show many changes [20:16] the changelog was the strangest part [20:18] wonder why Bhushan Shah added a build-dep to kwayland-dev [20:18] would that be a new dep for 5.6? [20:19] probably, we do want to manage wayland screens eventually ^^ [20:21] yup [20:21] KF5WaylandConfig.cmake [20:21] can those commits be reapplied? [20:22] what do you mean? [20:22] well its failed, it needs kwayland-dev to build [20:23] oh, right, the whole merge disorder reverted some stuff from unstable [20:23] go ahead [20:23] is it possible to watch the stream without joining G+? [20:23] oh there are gone [20:24] did you revert them all? [20:24] or is that what merging with debian did [20:24] well, someone merged unstable into archive, which made a bunch of reverts necessary, which then got merged into unstable [20:24] that's why you don't do such things [20:25] was it me? [20:25] dunno, didn't check [20:28] is standards up to 3.9.7 now? [20:29] yeah, 3.9.7.0 is in testing [20:29] * yofel looks at what changes [20:29] *changed [20:29] oh [20:29] 2.1 Version 3.9.7.0 [20:29] Released February, 2016. [20:30] Maxy knows his stuff! [20:31] not much relevant for us [20:31] 32 * Policy: [12.3] recommend to ship additional documentation for package 'pkg' [20:31] 33 in a separate package 'pkg-doc' and install it into /usr/share/doc/pkg. [20:31] if anything. But we've been doing that usually [20:32] if I change my deb email to clivejo@kubuntu.org do I have to do anything with my key? [20:32] does the email show up if you look at 'gpg --list-keys' ? [20:32] if not you'll want to add it [20:32] and publish the changes [20:33] Jobava: no idea :) [20:33] if it will be streamed than ye [20:33] yofel: yes it does [20:33] then you should be fine [20:34] I mean my aol one shows, not my kubuntu one [20:34] clivejo: you didn't publish that though https://pgp.mit.edu/pks/lookup?search=clivejo&op=index [20:34] ah, then you need to add it [20:35] should I make a new key for my new email? [20:35] you can edit the existing one [20:35]