=== Sho_ is now known as Guest90692 [06:48] Good morning. [06:49] good night haha [06:51] Hehe, you were just going to bed? [06:51] yeah , gnight [06:55] going to try to do some testing this cycle. I take it there still aren't any iso's ready for kubuntu to test? Haven't found anything at least. [06:55] Sleep well, sgclark [06:56] we are far from ready, not enough resources, anyway need to sleep. [06:56] rbetzen: You can allways test the daily iso's (though they might still have a critical bug), or upgrade from 15.10 to test stuff. [06:58] Thanks. I'll do that. Just making sure I wasn't missing a release. ;) [07:00] rbetzen: Kubuntu skipped Alpha 2, you haven't missed a thing ;) [08:56] i posted feature request on plasma-devel ml, if someone want to comment please do https://mail.kde.org/pipermail/plasma-devel/2016-February/049202.html [10:41] clivejo: no [10:41] clivejo: last thread I see is sddm breakage [10:45] sitter: can you update discover in KCI to grab from plasma-discover in debian git? [10:47] clivejo: will do so later today [10:48] thanks :) [11:51] Hey folks [12:11] sitter Riddell : can anyone tell me why this merge is failing - http://kci.pangea.pub/job/merger_kwallet-pam/252/console [12:14] clivejo: drop that branch remotes/origin/kubuntu_unstable_pam-auth-update [12:14] no intention to pursue [12:15] also it fails because the merge chain failed [12:15] [I] merger: Merging remotes/origin/kubuntu_xenial_archive into kubuntu_stable. [12:15] [I] merger: Merging kubuntu_stable into kubuntu_unstable. [12:15] [I] merger: kubuntu_unstable -> remotes/origin/kubuntu_unstable_pam-auth-update [12:15] so if you want to find out why exactly it failed you'll have to merge the branches like that locally [12:15] why am I culprit!!! [12:16] because jenkins [12:16] !!!11one! [12:16] Sorry, I don't know anything about 11one! [12:16] :p [14:37] but what is remotes/origin/kubuntu_unstable_pam-auth-update [14:37] and who put it there [14:38] git log might give a hint [14:38] not about who pushed though [14:40] how do I drop the remote? [14:43] why would you drop origin?!? [14:44] or do you mean delete the branch? [14:45] ... from the remote [15:07] On Xenial with the landing PPA, has anybody noticed that the kwalled migration password dialogue box comes up with every boot? [15:20] I remember someone mentioning that before, but I haven't seen it myself [15:21] It was happening to me for a while, but then it seemed to resolve itself. === ovidiu is now known as ovidiu-florin [16:38] sitter yofel - http://anonscm.debian.org/cgit/pkg-kde/plasma/kwallet-pam.git/commit/?h=kubuntu_unstable_pam-auth-update [16:38] could KCI have created that branch? [16:38] that branch is a bane to merges [16:38] no clue what it is for [16:39] but it should NOT be in the merges [16:39] sgclark: know how to remove it? [16:39] from CI? sadly no [16:40] and what does it mean by remotes [16:40] remotes/origin/kubuntu_unstable_pam-auth-update? [16:41] https://www.kernel.org/pub/software/scm/git/docs/git-remote.html [16:42] can it be removed with git remote remove? [16:43] clivejo: probably want to get the ok from yofel, I do not have authority to remove annoying branches [16:44] All I know is I am sick of being stalked by CI for a branch I know nothing about and as far as I can tell we do not use. [16:44] sgclark: ditto [16:44] clivejo: read the manual scarlett pointed to, a remote is a "repository", you're talking about branch deletion [16:45] as for the deletion itself, I'm not sure if we can [16:45] there was some discussion about qt-kde policies there... [16:45] * clivejo puts hands up [16:45] I have no idea, just want to see it fixed! [16:45] lisandro: are we allowed to delete branches from the repositories that only affect us? [16:46] yofel: sitter: or we can just remove the merge from CI? I don't understand why that merge is there [16:47] sitter will have to answer that, I have no idea how the merge tooling works [16:47] yah we should probably e filled in there [16:47] s/e/be/ [16:54] I would assume it's some kind of mixed hard-coded/auto branch detection in the ci tooling [16:54] bbl [16:54] k [16:59] yofel: if everything works as expected you shouldn't be able to do so [16:59] don't get me wrong: the repos' scripts where meant for another workflow [17:00] for example we avoided temporary branches [17:19] yofel: forgot to mention, if you need to remove a branch ping me [17:26] fairly certain that is not what we want. Just removal from CI which requires sitter [19:30] lordievader: ok thanks. That's about what I remembered, but wasn't certain. We'll fix this in the CI instead. [19:30] lisandro: ^ [19:30] lordievader: feel yourself unpinged ^^ [19:31] yofel: ACK [19:35] Hehe, but I like to be pinged -.- [19:36] :D [19:39] lordievader: ping [19:39] * clivejo waves [19:40] ooo syncroton [19:41] sounds like a Transformer [19:41] \o/ [19:42] WTF!! [19:43] Ive never seen that before [19:43] Writing more data than expected (1909437 > 1909428) [IP: 91.189.91.24 80] [19:49] you are on higher level now :D you produce more data than expected [19:49] oh good lord [19:49] git init git [19:50] oups, wrong window [20:04] Riddell: you worked on packaging kolab? [20:04] libkolab - https://obs.kolabsys.com/package/view_file/Kolab:Winterfell/libkolab/debian.changelog?expand=1 [20:17] clivejo: looking at the log sitter and detrout were the last two to package that. sitter did the actual port. What exactly do you need? [20:18] dont need anything, just surprised to see Riddell in the changelog and wanted to chat to him about it [20:18] I think Diane is actually working on it for debian right now, you can find her in the debian-qt-kde channel. I see you in there. She doesn't bite. [20:18] YOu will see him in many changelogs.. haha [20:19] I chatted with Diane yesterday, she said she doesnt have time to work on Kolab [20:19] ah [20:20] I have packaged it, I don't recall anything crazy about it, although libkolabxml needs to be packaged first [20:20] thats the client side stuff? [20:21] it is a lib [20:21] yup [20:21] but we package it beacuse Kontact uses it [20:22] !info libkolabxml xenial [20:22] Package libkolabxml does not exist in xenial [20:22] !info libkolabxml wily [20:22] Package libkolabxml does not exist in wily [20:23] !info libkolab wily [20:23] Package libkolab does not exist in wily [20:23] !info libkolab-dev wily [20:23] libkolab-dev (source: libkolab): Development package for Kolab library. In component universe, is optional. Version 1.0.0-0ubuntu1 (wily), package size 10 kB, installed size 63 kB [20:24] !info libkolab-dev xenial [20:24] libkolab-dev (source: libkolab): Development package for Kolab library. In component universe, is optional. Version 1.0.0-0ubuntu1 (xenial), package size 10 kB, installed size 63 kB [20:24] !info libkolabxml1v5 [20:24] libkolabxml1v5 (source: libkolabxml): Kolab XML format (shared library). In component universe, is optional. Version 1.1.1-3 (wily), package size 639 kB, installed size 3641 kB [20:24] bah [20:24] oh [20:24] there it is [20:24] clivejo: ^ [20:24] thats quite old :/ [20:25] v2 now [22:02] * clivejo pokes soee_ [22:05] * soee_ watching at clivejo [22:06] me head hurts [22:06] :D [22:12] i think new frameworks should be released soon [22:14] ugh [22:15] the reaction should be: weeeeeeeeeee :D [22:15] not enough hours in the day for all this work hahahahah [22:15] * sgclark goes a little bit crazy [22:16] from what i see only those apps are huge madness [22:17] and this is what i would never understand [22:17] we should be able to just grab released tars, build them and done... [22:17] not some merging and other magic [22:18] * clivejo raises eyebrow [22:20] its not magic, its dark black magic [22:20] EVIL [22:20] yeah it is the merges that are killing us really [22:21] but I do see why, just it is too much work for our small team. I think other flavor maybe sync to debian so don't feel the pain? not sure [22:21] I think you are the only one working on them sgclark [22:21] flavors [22:22] and what about Neon - they don't care about Debian ? [22:23] I know nothing about Neon sorry, got kicked out of the loop. [22:23] wrr why ubuntu installs xserver-xorg-video-amdgpu while i do not have such gpu :/ [22:24] yeah I never understood the piles of xservers installed [22:24] why do it installs libmirclient also ... [22:24] does Kubuntu uses enywhere some mir* stuff ? [22:27] there is no driver auto-detect at install time (not very portable, is it?) - so all available drivers get installed [22:27] * clivejo waves at yofel [22:27] not in the UI parts, but we share some of the UI core stack [22:27] heyho [22:27] :/ [22:28] it's not like it has a practical effect [22:28] does this card still apply - https://trello.com/c/nYFDC2qg ? [22:28] we shop tons of libs that are nearly useless, but we ship them anyway [22:28] *ship [22:30] including some unity stuff *shivers* [22:30] *shrug* [22:31] someone who cares could check if we could manually exclude some recommends in the seeds [22:31] I care, but not just that much [23:03] For Kf5, I don't think there's much in the way of Ubuntu specific requirements that would prevent syncing most things. [23:04] If there's things that need to be pushed to the Debian branches to make that possible, feel free to ping me. [23:05] ScottK I have been trying to push the sync path. Makes more sense to me. Not sure where we are on that. yofel? === keithzg_ is now known as keithzg [23:06] especailly these apps [23:06] I haven't look at that at all [23:06] most of these are no changes [23:06] a) we're done with frameworks ourselves by now b) when we worked on plasma, debian wasn't done with frameworks [23:07] That's the usual problem. [23:07] so we could sync stuff now, but I don't intend to *keep* waiting on the sycns [23:07] right [23:07] It'll be a bit different post feature freeze. [23:07] wasnt that the purpose of ppa-landing? [23:08] anyway, back to my merge tastic cave. ugh [23:08] the purpose of ppa-landing was a mis-used ppa so people could test stuff while we get things uploaded [23:08] then we got distracted and other stuff and stuff never got uploaded [23:08] ah [23:08] I only got the e-c-m permissions fixed this week. So now we can actually *try* to upload stuff [23:08] gotcha [23:08] ok [23:09] right, need to go for developer. so much so little time. I have to wear my kde hat next week. Things will be tight. [23:09] you concentrate on what you have to do. We'll figure things out somehow [23:10] and wehn I get a $ job it will be even tighter lol [23:10] yeah I know [23:13] has the apps merge trello card gone? [23:14] it somehow moved to backlog [23:14] ah [23:14] there it is [23:23] hmm kubuntu-ci is being strangely quiet [23:24] think its broken again [23:24] or maybe its caught up [23:25] nope, I have pushed several merges, should have seen a few [23:26] now I have to manually look /grumble. spoiled by CI links haha [23:26] should okular not have an unstable and stable branch - http://anonscm.debian.org/cgit/pkg-kde/applications/okular.git/ [23:28] I dont see why it would differ from the rest [23:28] doesnt seem to be in KCI [23:29] wasn't it only ported to frameworks now? [23:29] we didn't CI qt4 apps [23:32] will I create a stable and unstable branch while Im here? [23:36] yofel: ^ [23:40] ah possibly yeah recent port. makes sense [23:52] yofel: help me please :( [23:59] sgclark: why would a git merge not be sorting the changelog right? [23:59] clivejo: sadly this first run doing merges this way changelogs seems to be the problem point. you will have to manually cut paste the entries in the proper order. :(