[02:31] ovidiu-florin what is the size you used for that IRC icon on the Podcast section?> [02:32] nvm [02:55] wait how do we login... [03:00] ovidiu-florin http://kubuntu.org/kubuntu-podcast/ [03:00] :))) [07:33] sgclark, clivejo: I'm only realizing this now, but when I look at https://code.launchpad.net/~kubuntu-packagers/+git, why is the namespace missing? And https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git is empty.. [07:34] could yo elaborate on namespace... I did what you want. You havent exactly been here. [07:34] I have killed myself getting where we are now. feel free to fix [07:34] I know, was so tired that I decided to take the weekend off [07:35] well, I can fix it... but that'll change the URLs of all repositories again [07:35] sigh [07:35] brb [07:36] I rembember asking exactly why yoou did not want to have framework/plasma etc.. [07:36] but whatever [07:37] I have literally worked non stop this weekend [07:37] sgclark: go take the week off (: [07:37] ................ [07:37] fine whatever [07:38] * sitter hugs sgclark [07:38] yofel: FWIW, the super directory is fairly stupid in all sorts of ways. such as when things move (khelpcenter plasma->apps) [07:38] sitter: we need a yakkety image. but I am not sure I care anymore. [07:39] sync all the debian! [07:39] yeah I wanted and lost that fight [07:39] ooph [07:40] I got Ci working with launchpad except merges [07:40] that is a beast I was going to work on tomorrow. but meh [07:47] sitter: why that? It makes esp. those moves a non-issue [07:48] sgclark: don't misunderstand me, that you A LOT for working on this [07:48] I was just irritated a bit as I talked about this with clive last week.. [07:50] he tried and could not. I stepped up. learned ruby a bit and mustered the best I could. [07:50] was very happy with my progress. now not so much. [07:50] I showed you the ecm I had and the ONLY complaint you had was origin [07:51] changing the URLs should be a simple sed run, but lets see if moving a repo on launchpad is a thing [07:51] so how am I suppose to know? [07:51] so far launchpad is seriously limited [07:51] right, partly my fault. I only realized the missing namespace when you talked about CI picking up automation, which shouldn't have been possible [07:52] I changed some bit of code getting that to work [07:52] bit it does.. [07:52] but rather [07:53] I forked pangea so in theory sitter will not hate me [07:54] only thing I could not get to work is mergers, and that is a matter of sorting out how the heck to get a token for launchpad API [07:54] yofel: they are a non-issue because they are still the same thing. if they weren't the same thing one of the two would need a source rename anyway. as such they make the release scope change an issue to begin with in that you now have a khelpcenter (up to plasma 5.6) which is plasma/ but you also have a khelpcenter (apps 16.08 onwards) which is applications/ but they both are the same thing just released at different cadences [07:55] right. [07:56] so debian makes copies of the repositories? [07:56] kci.yaml is instead only a straight list of jobs instead of broken into namespaces [07:56] I mean, it's not like we would acutally ship 2 different versions of it, so why is that a problem again? [07:56] and I could not use * because yoou cannot ssh inot git.launchpad.net no shells available :( [07:57] you could get the list from an API call I guess.. [07:57] sitter had some fancy API wrapper for ruby [07:57] if you can go for it. I could not [07:57] yofel: at the very least you have one supported version in the archive of the last released kubuntu and one not supported version in the archive of teh next kubuntu that follows [07:57] yofel: I am using his ruby code.. [07:57] in a CI context it creates unnecessary world because now you need to deal with there being two khelpcenters that are really the same khelpcenter but in different scopes [07:58] isn't it the job of the branches to figure that out? [07:59] they are branches across repos [07:59] if they were the same repo sure [07:59] but they aren't because they are in different directories [07:59] which is why the dir approach is silly :P [07:59] sgclark: token... irb [07:59] well, that's why I wanted to only have one directory for everything? [07:59] irb? [07:59] interactive prompt [08:00] then run https://paste.kde.org/pxkbjuwls [08:01] pmq6n6kxe [08:01] https://paste.kde.org/pmq6n6kxe [08:01] looks like this [08:01] sgclark: you now have a tokens config https://paste.kde.org/pyxxctf3r [08:02] hm, looks like you can freely change the project that a git repo belongs to [08:03] sgclark: if you want to use the ruby lib you basically repeat the two lines of code in your script. of which the first loads the lib and the second loads the token from ~/.config/lp-tokens.json [08:03] ah [08:03] ok [08:04] if I calm down and decide to continue. I will try that tomorrow. [08:04] once you have that you can use one of the scripts in ci-tooling/kci for guidance on how to use the lib itself [08:05] yeah I have actually sorted out much of what you have going on here [08:05] very crafty [08:05] I am actually enjoying ruby [08:05] much more than python.. [08:06] but anyway, 1 am , time to take a break... === pavlushka_ is now known as pavlushka [09:25] sgclark: this would fix the repository namespace https://gist.github.com/Yofel/c4c6ca5270ea1e8c4b8f69a0ec2b8769 [09:25] run it whenever is convenient for you [09:25] (that's also the API for getting a list of all valid repositories, see https://launchpad.net/+apidoc/devel.html#git_repositories) [09:31] yofel: hiho [09:32] hey [09:32] have you seen the ppas related talk and can you remove those unused if you accept it ? [09:33] only skimmed over it so far [09:42] soee_: the plan was to delete beta and experimental? [09:44] hmm i think more, let me check log [09:46] [19:52] correct, sorry, yes please remove everything but staging/landing. and be clear that staging is generally broken. landing is really where folks need to be unless asked to test staging [09:47] and i think: daily/weekly CI [09:47] as they are not used almost a year now and we can create them if we start providing that builds [09:48] backports stays ofc. [09:48] i asked Scarlett about beta backports and i think she said that this might be use when we will have more packagers [09:48] but probably not any soon? [09:50] ok, so... [09:50] sgclark, clivejo, valorie: ci daily/weekly and ppa beta/experimental are DISABLED now [09:50] that will hide them from non-team-members and prevents uploads to them [09:51] deleting a PPA also causes apt errors for users, so lets do that when we know that nobody is using them anymore [09:52] the staging ppa's already have capital letter warnings to not use them, maybe that should be made more visible.. [09:52] i doubt anyone uses daily/weekly CI [09:53] the CI itself might have code for that somewhere, so I'll leave the deletion of those up to sgclark [09:53] ok [09:57] regarding beta and experimental. IMO experimental is probably obsolete, everyone just uses personal repos these days. [09:57] Not having beta means that we have no place to ever put beta versions for stable releases anymore. I'm not quite convinced that we don't plan to ever do that again [09:58] it still counts as a test repo though, so it shouldn't be on the wiki page [10:05] ahoneybun, i sent you a PM about kubuntu DVD's for 16.04 (mentioning here if for some reason the PM doesn't reach you) === inetpro_ is now known as inetpro === mgraesslin_ is now known as mgraesslin [11:09] can anyone help with my gpg problem. I have a number of users on my system, to do diferent jobs (Kubuntu, OSM, business and personal). Log into the account I want via Konsole and do my work [11:10] up unto recently Ive been using this successful but its stopped being able to remember my passphase via gpg-agent [11:50] Hiyas all [11:57] hi again [11:57] hiho [12:31] clivejo: is your GPG_AGENT_INFO in the env kept intact when you do that? [12:32] and does the target path and the right agent PID exist? [12:32] no, its blank for every user [12:32] sgclark: is something blocking you from lp 1576455? [12:32] Launchpad bug 1576455 in kde-l10n-ru (Ubuntu Xenial) "SRu kde-l10n-* translation packages" [Undecided,New] https://launchpad.net/bugs/1576455 [12:33] is gpg-agent actually running? [12:33] yes [12:33] and /tmp/gpg-something exists? [12:34] no [12:35] sgclark: just asking as I see nothing in the upload queue yet [12:35] wont create a socket [12:35] what does it say when you run 'gpg-agent' in konsole? [12:35] gpg-agent[6432]: gpg-agent running and available [12:36] huh [12:36] exactly! [12:36] env | grep GPG_AGENT is really empty? [12:36] hm, wait [12:37] echo $GPG_AGENT_INFO is a blank line [12:48] clivejo: FWIW, I don't have a socket on this system either (but no gpg key) [12:48] it still says that the agent is fully functional though o.O [13:06] clivejo: we are working on the launchpad git branches already, right? [13:12] hmm, no upgrades in Yakkety for 2 days [14:00] yofel: kinda [14:01] sgclark has pushed frameworks as far as I know [14:01] uh oh :D [14:01] plasma [14:01] I also see apps [14:01] I was modifying KA to use LP rather than git [14:02] cloned plasma packages [14:02] rm'ed yakkety branch as it was based on master [14:02] and checkout'ed out xenial_archive into new yakkety branch [14:02] but just for plasma [14:03] I was trying to run staging and gpg-agent wouldnt work, so thats where Im at [14:03] sgclark said she was going to work on apps [14:03] ah, are all yakkety branches broken? [14:03] clivejo: Trying to stage Plasma 5.6.x? [14:04] 5.6.3 [14:04] * mamarley happy dance. [14:04] but I cant sign the packages [14:04] so .... [14:04] clivejo: wait, you only fixed the plasma branches? [14:04] why not everything? [14:04] I kinda got shouted at :/ [14:04] ... [14:05] now scripting the fixing requires writing logic to not delete any good branches :S [14:05] when fixing everything would've been trivial [14:05] yofel: feel free to delete the plasma yakkety branches [14:05] nothing new in there [14:06] clivejo: I would delete *all* [14:06] well I know sgclark was working on yakkety FW5.21 [14:06] brrr [14:07] http://qa.kubuntu.co.uk/ppa-status/frameworks/build_status_5.21.0_yakkety.html [14:07] I guess somekind of silent git diff would work... [14:07] I couldnt get the git copy to work properly [14:07] nothing will work right for me! [14:08] well, and I missed that she used the wrong namespace [14:08] *that* is trivial to fix [14:08] the branches not :S [14:09] how do you tell ka about a new dist ie yakkety? [14:09] IIRC you first need to initialize the package lists [14:10] what name space are we supposed to use? [14:10] and for the new code from santa maybe edit another dozen files, dunno [14:10] clivejo: URIs are supposed to be ~kubuntu-packagers/kubuntu-packaging/+git/$repo [14:10] but currently the project is missing [14:11] what are they now? [14:11] ~kubuntu-packagers/+git/$repo [14:12] * yofel thought: "how hard can it be to figure out the parent of a git branch" [14:12] well, http://stackoverflow.com/questions/3161204/find-the-parent-branch-of-a-git-branch [14:12] I think I need a different solution [14:17] although, the broken yakkety branches should not have any diff from master [14:17] the plasma ones are from xenial_archive [14:21] right, I just want an automated way that doesn't delete any branches with valid changes in them [14:21] beyond me :( [14:22] I cant even sign stuff right now [14:29] grrrrrr [14:29] https://paste.kde.org/pkdv84qdo [14:29] its available or now available, make up your mind! [14:29] not [14:32] hm, looks like the CI is "fixing" the branches already [14:33] the history ends up wrong, but the code might be ok... [14:33] so instead of deleting the branches, merging xenial into them might make more sense [14:35] ah ha!!! [14:36] so we kind of just forced us to do another debian merge :P [14:36] * clivejo dances [14:36] (which is a non-issue in most cases) === mgraesslin_ is now known as mgraesslin [14:42] gpg is working again [14:43] Yay! [14:43] had to "export GPG_AGENT_INFO=/home/clivejo/.gnupg/S.gpg-agent:0:1" [14:43] before I start the daemon [14:44] wonder why that setting got messed up [14:44] or how [14:45] maybe I should generate a new key, using my kubuntu email while I at it! [14:46] nice big 4096-bit one [14:46] come to think of it, I had agent startup problems a long time ago. These days I have custom startup logic for it (so I have working code on all systems, even servers) [14:46] you could also edit your existing key to add the mail (that's what I did) [14:47] think a new 4096 one would be better [14:47] the other one is a year old now [14:48] yofel: what does Der Dichter mean? [14:50] The guy that writes poems [14:50] clivejo: the poet [14:52] right, memory fail [14:52] I see [15:02] hm, actually, the branch merging would only work if debian didn't remove anything that we need [15:02] so in the end, someone still has to read the branch diff output of all repositories [15:07] cant you recreate a complete copy of debian git in the correct place [15:07] and then sgclark can merge in her changes? [15:07] for FW? === DalekSec_ is now known as DalekSec === Jobava_ is now known as Jobava [15:34] yofel: do we have password required for live session ? [15:34] no [15:34] yofel: can you tk e look @ #kubutnu [15:34] *kubuntu [15:34] user reports it requires password [15:35] there is a bug report about users not being able to install kubuntu thanks to plasma crashing repeatedly [15:35] if that ends with the login screen appearing, that would explain what he sees [15:35] but I'm just guessing [15:35] oh, trusty === kfunk_ is now known as kfunk [16:30] Hi there 😄 [16:32] heyho [16:35] howdy [16:48] * yofel out [16:48] FYI: I don't pay much attention to IRC on evenings lately. Rather ping me on Telegram if there's something important [18:17] sitter: were you able to make a yakkety docker image? Or point me to instructions on doing it? pretty please [18:28] hi sgclark [18:28] hiyas [18:28] did you see yofel's links earlier? [18:29] the one where I was not informed about the kubuntu-packaging namespace until to late? sure. [18:29] the fixes on github? [18:30] huh> [18:30] o/ [18:30] ? [18:30] sgclark: https://gist.github.com/Yofel/c4c6ca5270ea1e8c4b8f69a0ec2b8769 [18:30] should take care of it [18:30] ah [18:31] no I did not see that. [18:31] ok [18:31] sadly I already ran applications and in the middle of that, I can do it after though [18:32] sure, I didn't run that as that should be done at the same time as fixing the CI URIs [18:32] yeah will have to do that too [18:32] so do it whenever is convenient for you [18:33] do you know if yakkety images were made for ci? [18:33] no idea [18:33] ok [18:33] did you fix the branches for applications? [18:34] I am fixing them as I go [18:34] ah ok, thanks [18:34] I branched off wrong branch :( [18:34] my fault. fixing stuff as I go [18:35] and currently mergers are totally broken. so I am manually merging as well. fun stuff [18:35] right, technically the CI "fixed" some of that by practically doing a debian merge on its own.. [18:35] nah that is me [18:35] I just hope that nothing important got dropped by that [18:35] ci mergers are broken [18:35] aah ok, then great :) [18:35] that not so much :/ [18:36] I have to do the lp magic to get token for that to be fixed [18:36] on my to list. but it is better to do them by hand right now with all the moving and such [18:36] to be careful [18:37] ack [18:42] yofel: do take a look at akonadi for me though. that one seems to be a pain point for me. when you have time, no rush [18:42] sgclark: ah right, if you didn't read the backlog yet: Are you stuck on something regarding kde-l10n? [18:42] yofel: backlog seems to have been cut off. yes I have an sru waiting and waiting [18:43] a chunk of packages got missed, breaking installs across the world [18:43] I fixed that bug up a bit so it looks like a valid SRU. But I think the SRU team is waiting for you to upload things [18:43] literally :) [18:43] as I saw nothing in the queue I was curious if you're stuck [18:43] shadeslayer_: uploaded them for me [18:43] um [18:44] to yakkety, but there's nothing in xenial unapproved [18:44] we uploaded both yakkety and xenial [18:44] shadeslayer_: ^^ [18:44] well I gave xenial to him to upload [18:44] hm... I wonder if I missed something [18:46] and according to infinity you and I are suppose to be able to upload our package set without a motu [18:46] You can upload xenial yourself though [18:47] sure we can. Problem last cycle was that we had at least one source from each component that we couldn't upload [18:47] which kind of defeats the packageset [18:47] blah [18:47] bugfixes we can do though [18:47] can we fix that? [18:47] we cannot upload NEW sources, that's >= MOTU [18:48] once they're uploaded, we can fix the packageset [18:48] please ask kde to not make any new components for the time being, thanks :P [18:48] LOL [18:48] I understand now [18:48] we have several new already [18:48] kactivities split for one [18:49] AFAIR, we should be able to upload SRUs for pretty much everything for xenial if we need to. So you don't need a sponsor for that [18:49] just actual development is a bit.. annoying [18:50] ok, so I should just push these xenial translations? [18:50] * yofel started writing his core dev application, but that'll take a while [18:50] cool [18:50] Yes, but please put the bug # into the changelog so the SRU team knows what they belong to [18:50] I was approved for outreachy which means actual money, so my core-dev is backburnered again [18:51] ah [18:51] ok, then I have to rerun. will do that later. [18:52] also see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure - regarding bug status (I already created the xenial task) [18:57] * yofel hides again [19:46] <@marcinsagol>: Is this channel out of sync! [19:46] <@Clifford>: Looks like it [19:46] <@marcinsagol>: @ovidiuflorin can you do something about it? [19:52] <@ovidiuflorin>: done [19:52] <@ovidiuflorin>: my ISP went down today [19:52] <@ovidiuflorin>: and bot died when it came back [19:56] anyone have idea what is wrong here: http://pastebin.com/SHTwZiev ? [19:57] you need to pay the electric bill [19:58] looks like you are trying to force the installation of MySQL 5.6, but the default is 5.7 [19:58] <@ovidiuflorin>: it's not electric [19:58] <@ovidiuflorin>: the whole ISP went down [19:58] <@ovidiuflorin>: 4G as well [19:58] <@ovidiuflorin>: so I went to sleep [19:59] <@ovidiuflorin>: there was nothing I could do [19:59] <@ovidiuflorin>: when I woke up, it worked [19:59] <@ovidiuflorin>: :-P [19:59] @ovidiuflorin I was replying to soee and his mysql problem [19:59] clivejo: not me, user on #kubuntu asked for help [20:00] he must have mysql-community-server installed [20:00] which relies on mysql-common and mysql-client [20:01] did they default mysql-server to 5.7 in wily too? [20:03] clivejo: problem with akonadi dep http://pastebin.com/yunPUCUh [20:04] clivejo: where are we with all this LP migration? [20:04] soee: bit of a nightmare [20:04] dont ask :P [20:04] :D [20:05] apparently LP has namespaces [20:05] and you didnt tell us! [20:05] i thought it is pretty obvious :D [20:06] teaching us a lesson huh? [20:07] :) [20:09] clivejo: Yeah he seems to have installed 5.7 from some external source and it's gotten everything twisted up. [20:15] on the migration, if my wacky backlog tells me true, we're not done, but it's getting sorted [20:15] my thanks to all of you who sweated blood on that project [20:16] * valorie is looking forward to seeing CI back too [20:19] ahoneybun: ricktimmis: are you guys doing a Kubuntu podcast recording this week? [20:19] Yes.. Weds [20:19] do you want to add it to the UOS schedule? [20:20] if it's before 2000 UTC that is [20:20] Err... thinking [20:20] ahoneybun: Comments [20:20] I know you were looking at this [20:21] I believe the HOA is scheduled for 20:00 BST = 19:00 UTC [20:21] ahoneybun: Poke, Prod.. [20:22] he might be busy, I don't need an answer this very moment [20:22] 19:00 [20:22] I think is 3pm to me [20:23] Ah ha.. I knew he was there [20:23] if you guys want it, please fill out http://summit.ubuntu.com/uos-1605/propose_meeting/ and then I'll put it on the schedule [20:23] yeah, 1900 is 3pm for us [20:23] it looked kinda full before [20:23] * ricktimmis dives off to check G+ event details [20:23] ok 1900 is awesome [20:23] hmmm, has anybody updated the /topic lately? Isn't Plasma 5.6.3 our target next? [20:23] I don't have access to it I think [20:24] ahoneybun: we have an "Overflow" room we can use [20:24] Yes event is 19:00 UTC [20:24] sweet [20:24] unsure why we have finished stuff in the topic [20:24] * ricktimmis Jumps to podcast channel to avoid off-topic [20:25] another question: who is running our social media stuff these days? [20:26] I don't see tweets from us, and is someone answering on FB/G+ ? [20:28] I know ovidiu-florin is answering from his own profile on G+ in our community there [20:32] oh stuff [20:36] I randomly answer some stuff on G+ when I remember. That is not often [20:36] and as for migration I have to move the repos again, but can't till I finish apps because I had already run the script [20:37] speaking of which clivejo are you working on plasma>>? [20:38] I think I figured out how to get docker images, but since I can't commit to blue systems I think it is time to switch jenkins to my fork. [20:42] sgclark: no, I have had problems with my gpg debsign [20:42] aww still? I thought I saw you dancing earlier [20:42] and been holding off until your guys get the LP git sorted out [20:43] my guys? [20:43] you [20:43] oh lol [20:43] right ok [20:43] well you and yofel :P [20:44] and soee [20:44] so are we working on Plasma 5.6.3? [20:44] I was updating a plasma/packages wiki page [20:45] I was trying to [20:45] um soee is working on stuff? [20:45] but no progress [20:45] awesome [20:45] I couldnt sign the packages [20:45] valorie: afaik only frameworks and apps are in progress [20:45] and the script isnt bumping frameworks [20:46] I'm sure y'all will figure this out [20:46] !releases [20:46] Ubuntu releases a new version every 6 months. Each version is supported for 9 months (non-LTS) or 5 years (LTS). More info at https://wiki.ubuntu.com/Releases & http://wiki.ubuntu.com/TimeBasedReleases [20:46] then I heard the git wasnt in the right place [20:47] so purged my workspace [20:51] dang I don't see a way to change repo through jenkins [20:51] I need access to the actual server [20:52] * sgclark is tired of ramming into walls [20:52] is that LP admins, or who? [20:52] blue-systems [20:52] ah [20:53] oh well giving up on yakkety builds. back to apps [20:53] if they have an IRC channel, it isn't public [20:53] :( [20:54] perhaps sitter knows who to ask.... [20:54] starbuck11: What do we need to do to get access to the actual jenkins server for kci? [20:55] probably late over there. [20:55]