=== mgraesslin_ is now known as mgraesslin [08:04] yofel: repos updated, thanks for the script. Running the ci update script now ( not that it matters without a yakkety docker image). [08:04] * sgclark goes to bed === ghostcube_ is now known as ghostcube [11:16] Hey folks [11:17] o/ [11:19] howdy [11:20] hey yofel, clivejo [11:27] did we ever make the packaging notepad into a proper document? [11:27] * yofel started out crossing out references to alioth [11:27] s/out// [11:31] <@Sick_Rimmit>: yofel no but I was looking at that last night, reading through it [11:31] <@Sick_Rimmit>: I thought it was good, and could be brought into both a document, and some training slides for Kubuntu Dojo [11:32] @Sick_Rimmit: ok, I'm crossing out stuff that's obsolete, and I added a small section on gitconfig setup [11:32] <@Sick_Rimmit>: Yes please [11:32] for the new launchpad paths [11:32] <@Sick_Rimmit>: if you update it [11:32] <@Sick_Rimmit>: perhaps ask the others to look over it [11:32] ack [11:33] <@Sick_Rimmit>: I would be happy to start work on docs and slides from Monday next week [11:39] ok, updated what I wanted. [11:39] acutally, that reminds me... [11:41] @ovidiuflorin / ovidiu-florin: just as a reminder: Now that we're on LP you have commit access to the repositories ;) [11:43] As does Rick for that matter, as all kubuntu members do [11:44] <@Sick_Rimmit>: Ooo that is going to be really helpful [11:45] yofel: so we're completely switched back to LP now? [11:45] yofel: you don't have to give both nicks [11:45] for me, at least, it's the same [11:46] mostly. The main repositories are moved, anything extra can be done as needed (calligra, pkg-kde-tools, etc.) [11:46] ah ok [11:46] but write target is Lauchpad now [11:46] <@Sick_Rimmit>: I would like to ask some questions on that, but am at work at present, maybe later [11:46] if you give with @ then IRC and telegram starts screaming at me [11:46] :D [11:46] I'd like to make a diagram of the workflow [11:47] and put it on the contribute page of our site [11:47] that would be helpful, the only thing that's changed is that you can substitute git.debian.org with git.launchpad.net in all places [11:48] other than that the workflow stays until everything is running again [11:48] hiho [11:49] yofel: we still don't have a diagram with the current workflow [11:49] hell, I still don't understand the current workflow [11:49] we have the thing that you once started.. [11:49] I know.... [11:50] but it's more like a quick tips than an actual guide for noobs [11:50] let me put a reminder in my calendar to draw something on paper tomorrow if I can find the time [11:50] paper is great [11:50] thank you [11:53] *blink* [11:53] valorie: happy birthday! [12:14] * yofel deleted oxygen-icons5 from yakkety staging-frameworks (has an epoch) [12:39] yofel: have you made any changes to the KA scripts for LP? [12:39] not yet [12:40] mind if I try? [12:51] maxyz: are you sure that xephyr hack in frameworks actually works? the way I see it after `xvfb-run ... Xephyr` $! would be the one of xvfb-run and killing that leaves Xephyr fairly uninterested [12:57] clivejo: go ahead [13:05] maxyz: terminating the pgroup instead of just the lead process seems to do the trick http://packaging.neon.kde.org/cgit/frameworks/kconfig.git/commit/?h=Neon/unstable-fix-test-kill&id=89d373e1f7b6655d52a737a32a513f459302554f alternatively we could pgrep -P all children and term all of them, which probably is slightly more accurate than going by pgroup [13:13] maxyz: -9 also might be handy, I am currently booting them manually and every once in a while they go defunct instead of actually terminating [13:19] hola. I want to take a look on the source code of the timeout counter widget. which package should I choose? https://www.kde.org/info/plasma-5.5.0.php [13:20] time out widget? [13:21] clivejo, yeah, it's called timer basically [13:24] !info plasma-widgets-addons xenial [13:24] plasma-widgets-addons (source: kdeplasma-addons): additional widgets for Plasma 5. In component universe, is optional. Version 4:5.5.5-0ubuntu1 (xenial), package size 287 kB, installed size 1500 kB [13:25] I think its in there [13:25] kdeplasma-addons-5.5.0 [13:26] installed into /usr/share/plasma/plasmoids/org.kde.plasma.timer/ [13:35] yofel: ping [13:35] hm? [13:35] bump-build-dep-versions [13:36] where does it get its info? [13:36] no idea [13:36] I didn't write that [13:36] actually, IIRC some code there is broken [13:36] I can get it to bump the plasma versions [13:37] but not the frameworks [13:37] something tries to make bundled version files without allowing to manually set the version, while the version files should be by-component [13:37] I never really looked at that in depth [13:37] grrr [13:37] gbp:error: 'debuild -i -I -S -sa -nc' failed: it exited with 29 [13:43] maxyz: nevermind, killing the pgroup is equally ineffective -.- [13:46] yofel: [13:46] git does not match archive [13:46] missing lines: bluedevil (4:5.5.5-0ubuntu1) xenial; urgency=medium [13:46] -- Philip Muškovac Thu, 14 Apr 2016 13:31:17 -0700 [13:46] I guess the branches are still broken [13:47] but thats whats in the archive - https://launchpad.net/ubuntu/+source/bluedevil/4:5.5.5-0ubuntu1 [13:47] yes, and what does the branch say? [13:48] https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/bluedevil/tree/debian/changelog?h=kubuntu_yakkety_archive [13:48] ah the time [13:48] 14:24:36 -0700 [13:48] aaah right [13:48] so change the time in the branch [13:48] meh, that looks like fallout from the time when shadeslayer__ wasn't able to push his upload [13:49] to match the archive [13:49] right, please do that [13:49] will probably happen in a bunch of other repositories as well [13:49] * clivejo :( [13:54] should I fix the xenial branch too? [13:56] ah [13:56] the official version of FW is 5.12.0 ? [13:56] not 5.12? [13:57] yes [13:57] you probably mean 5.21 though [13:57] yeah, stupid dyslexic brain [13:58] ^^ [13:58] my brain messes up the order of numbers [14:00] fixing xenial is probably not needed [14:00] ok [14:00] the branches don't match the packages exactly, but we won't be doing anything but single-package SRUs, and for those that doesn't matter [14:00] theres a versions.json in KA config/ folder [14:01] the frameworks was missing a .0 [14:03] you can omit the .0 in the places where it's used for the build-deps, just not wherever the changelog is touched [14:06] nope, the script is still not bumping the frameworks [14:06] https://paste.kde.org/p1tnlnwh4 === soee changed the topic of #kubuntu-devel to: Kubuntu - Friendly computing | Yakkety open, happy hacking | Plasma 5.5.5: X/archive, Apps 15.12.3: X/archive, FW 5.18: X/archive , FW 5.21 Y/WIP| https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | Package Docs (WIP) https://notes.kde.org/p/kubuntu-packaging [14:07] its bumping the plasma [14:07] but not the FW [14:08] oh, for plasma? [14:08] IIRC we intentionally seperated that [14:08] plasma only bumps internal plasma deps [14:09] we might want to bump frameworks as well [14:09] so it doesnt bump frameworks? [14:09] but thanks to the cyclic deps we had last release we had to remove that [14:09] I thought it was supposed to bump both [14:10] it was originally, but that made stuff unbuildable, so it was removed [14:10] clivejo, thanks. I'm trying to read this: https://techbase.kde.org/Development/Tutorials/Plasma5/QML2/GettingStarted but it's missing some parts (!! FixMe !!) [14:10] technically we want that [14:10] but then each component still needs its own version file so we control what gets updated [14:11] maybe staging should take an addition parameter, ie what bump we need? [14:11] because "everything" does not work [14:11] that's probably better kept in a config file, but something like that [14:11] can somebody guide me a bit? I've created the basic folder structure and metadata.desktop, main.qml, CMakeLists.txt [14:12] hakermania: this is probably better asked in #kde-devel ? [14:12] clivejo, excellent [14:13] or maybe #plasma [14:14] we tend to talk about bringing KDE software into Ubuntu here [14:15] eakkk [14:15] script crashed and burned! [14:16] fatal: remote error: Repository '~kubuntu-packagers/kubuntu-packaging/+git/discover' not found. [14:16] oh, that thing. IIRC we can drop all the special handling for that [14:16] just call it plasma-discover? [14:17] how do you find stuff on LP git [14:17] yes, grep for that in the automation code, that's rewritten in 2 scripts and a couple config files I belive [14:17] https://code.launchpad.net/~kubuntu-packagers/+git [14:17] thats the list of packages [14:17] but is there no search? [14:18] doesn't look like it [14:19] * clivejo rolls eyes [14:20] kubuntu-automation/upstream-names.json [14:20] kubuntu-automation/package-name-list [14:20] kubuntu-automation/ubuntu-archive-upload [14:21] which upstream is it talking about?! [14:22] depends on the context? [14:23] LOL there is none! [14:23] upstream-names.json [14:23] ah, kde [14:24] so that entry is correct [14:24] "plasma-discover": "discover", [14:24] thats the path it uses for the actual source [14:24] can I put a comment in that file? [14:24] wait [14:24] didn't they fix that? [14:25] no they didn't :( [14:25] nope, still called discover-5.6.3.tar.xz [14:26] then the entry in that file is correct [14:26] but the special casing code for the repo naming in the scripts not [14:27] # Mapping for names of packages in Kubuntu and the related source code tarballs on KDE download site [14:28] it ok to add that at the top of upstream-names.json ? [14:28] no, JSON has no comment syntax [14:28] you could add a "comment" entry with that though [14:30] oh, urgh [14:30] nevermind [14:30] just bit confusing for newbies [14:31] so its this line [14:31] "discover": "plasma-discover", [14:31] in package-name-list [14:31] I wonder if we shouldn't just fix the repository name [14:32] it is [14:32] https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/plasma-discover [14:32] no, usually our repos are named after the upstream source [14:32] oh [14:32] otherwise 'baloo' would be baloo-kf5 [14:33] there's 2 exceptions to that rule: kde4libs and plasma-discover (see the code in ubuntu-archive-upload) [14:33] just rename the LP git repo [14:33] might be best solution? [14:34] in the long run, yes, but that'll break the CI as well, so lets talk to sgclark about that first [14:34] LOL [14:35] never going to get plasma staged at this rate! [14:35] why are you trying to stage plasma anyway? It's not like it'll actually build [14:35] why not? [14:36] supposedly requires Qt 5.6 [14:36] oh, didnt know that [14:37] does FW 5.21 not need it? [14:37] I'm not 100% sure, but that's what people keep screaming all the time [14:38] OTOH, stage it and we'll know [14:38] Plasna 5.6 does not require QT 5.6 [14:38] who is responsible for packaging QT? https://launchpad.net/qt ? [14:38] if this is what you are talking abot :) [14:38] but for now you'll probaly have to take the repo name code from ubuntu-archive-upload and put it into staging-upload [14:39] soee: ok thanks, then I'm misinformed [14:39] yofel: Neon also ships with QT 5.5 [14:39] and last days Jonathan created ppa to test QT 5.6 builds for Neon [14:42] clivejo: btw... thanks for finding and fixing all the workflow bugs :P [14:42] I wish I could say my pleasure! [14:42] but getting rather annoying now :P [14:43] but on the plus side I have a new super key [14:43] a big red one? >.> [14:43] and can sign packages off as a kubuntu team member [14:43] it took AGES to generate! [14:43] so it must be good! [14:45] how do I upgrade to yakkety? [14:45] * clivejo memory is pathetic [14:46] edit your sources.list [14:46] no gui for it? [14:47] * clivejo thinks yofel should code a gui for packaging [14:47] drag and drop [14:48] uh, you can edit it with software properties I believe, but you're probably best of using search and replace / sed at this point [14:50] and when it comes to a packaging GUI.. [14:50] yofel: who normally packages QT? [14:50] there is something that can show a GUI for the debian metadata files, but it was horrible when I last tried it at debconf [14:51] clivejo: debian-qt-kde, i.e. Mirv_ and mitya57_ mostly I believe. It's WIP (5.6.0 is stuck in experimental because "too buggy") [14:51] eakk [14:52] is KCI fixed now? [14:52] using LP branches? [14:52] AFAIK yes, but it has no triggers, so all it does are daily builds [14:53] seems to be stuck on mgmt_docker [14:54] oh right, there are no docker images for yakkety [14:54] scarlett said something like that [14:54] ah [14:54] doesnt is auto generate the image? [14:54] like once a day? [14:54] docker needs a base image to build from, and there is none [15:05] does plasma 5.6 need a min FW version? [15:15] clivejo: look and #plasma what Martin wrote [15:16] *at === shadeslayer_ is now known as shadeslayer [15:20] ok, I removed discover from the package list and re-run [15:21] its completed with 4 errors [15:21] 2 out of sync [15:21] and 2 libksysguard: build was interrupted [15:21] what does build was interrupted mean? [15:21] "something went wrong, please look at it yourself" [15:22] ah no, that's a packagae build failure [15:22] i.e. patch not applying or so [15:22] ah [15:22] you patched libksysguard in 5.5 ? [15:22] with 5.6 patch [15:22] maybe? [15:23] I don't remember [15:24] does staging merge in kubuntu_unstable? [15:24] it should [15:24] you might want to make sure that xenial_archive is properly merged though [15:25] (it wasn't for oxygen-icons5 when I looked at that earlier) [15:25] so if I wanted to work on fixing these, I should commit to kubuntu_unstable? [15:26] not if you work in staging, unstable is for the CI [15:26] where could I put my changes? [15:27] _archive [15:27] as usual [15:27] as UNRELEASED? [15:27] right [15:27] as usual [15:27] the script automatically does that anyway [15:28] but if I have 5.6.3 in there wont it get messed up next time staging script is run? [15:29] Now running lintian... [15:29] E: user-manager changes: bad-distribution-in-changes-file yakkety [15:29] W: user-manager source: out-of-date-standards-version 3.9.6 (current is 3.9.7) [15:30] you cannot re-run the script on an existing repository anyway [15:31] if you bumped to 5.6.3 once, then that's it. If you want to retry delete all your local work and start fresh [15:31] *if* you did not push [15:31] I havent pushed [15:31] if you did push then staging-upload may not be run again [15:31] or uploaded to LP [15:32] there are a lot of FW build deps Id like to bump and things to change [15:32] LP we can just wipe clean if something happens, git... is a bit trickier [15:32] maybe bump the standards too [15:32] feel free to revert the bump seperation [15:32] just make sure that e.g. no deps on any application stuff gets bumped in plasma [15:33] Ill try fixing these out of syncs errors [15:35] what would you advise doing? push what Ive done and work through them manually? or trash it all and wait until KCI is fixed up ? [15:37] push it if you're happy with the overall changes. The version changing is something I would rather fix before that [15:38] the out of sync things you can push after you fix them though, then it won't happen again next time [15:38] we'll have to re-upload everything at some point anyway when the VCS info in the repositories is fixed [15:39] what branch does the staging script merge in? [15:39] it should merge everything into the target, i.e. _archive [15:39] before Id make these changes to kubuntu_unstable [15:40] CI would do its magic and the staging script merged in the fixes [15:40] well, you can still do that [15:40] but with CI out of the picture at the moment, its not doing that "magic" [15:40] you just won't get an immediate build from the CI [15:41] you should be able to still manually trigger builds though [15:41] just not for yakkety [15:41] its yakkety Im working on [15:41] then you're stuck with the non-ci wokflow for now [15:41] ok maybe its best to push and upload what Ive done [15:42] and do it manually [15:42] at least Ill get buildlogs and reports from LP to aid in fixing [15:42] that's what the non-ci workflow is.. [15:43] just the initial script run should work correctly in that case [15:43] (i.e. version bumps ...) [15:43] * clivejo wasn’t a packager in those olden days! [15:44] we gave people funny ideas in #plasma... [15:46] yofel: are you planning to update the VCS fields via a script? [15:46] to point to LP [15:46] yes, that's just stuck at LP telling me nonsense (see #launchpad) [15:46] I guess I'll have to use our fixed lists [15:47] eak [16:00] I found another reason why we want a namepace for the git branches [16:00] LP supports merge requests for project git repositories, but not for personal ones [16:00] for whatever reason [16:03] can we "control" the LP commits? [16:04] as in? [16:04] like review commits before they go in? [16:04] well, anyone who's a member of kubuntu-packagers in some way has direct commit access [16:04] everyone else has to do merge requests [16:05] can somebody look into this bug report? https://bugs.kde.org/show_bug.cgi?id=362612 [16:05] KDE bug 362612 in discover "problems to Install evolution over the plasma discover" [Normal,Resolved: downstream] [16:05] o.O [16:07] looks like ovidiu-florin had another power outage [16:07] apt install evolution doesnt ask me to remove anything [16:08] installing it though discover didn't even ask me anything [16:08] other than my PW [16:08] its wanting to install gnome components though [16:09] that's normal [16:09] maybe they remove network manager? [16:10] they don't, otherwise apt would tell you [16:10] hummm [16:10] cant recreate that bug then [16:11] me neither [16:12] if he did proceed with the installation, then his history.log might tell something, otherwise I'm clueless [16:12] funny enough, discover now shows me the broken text on the main page [16:12] it didn't do that a while ago [16:13] told ya :P [16:14] I wonder if we should ship gnome software next release.. [16:14] hm, LP can create snappy packages from git branches [16:14] I really need to start looking at that thing [16:15] apol: so, we can't reproduce that... and I'm not really sure why discover would behave different from synaptic either [16:16] bbl [16:17] maybe he clicked on the uninstall radio button in Discover? [16:18] in the addons section [16:24] hi acheron88 [16:25] hi clivejo :) [16:25] anything to test? it's all a bit 'stable' at the moment [16:26] * clivejo is really really getting very annoyed with Kontact [16:26] did a clean install of 16.04 on this machine to make it nice and fresh [16:26] Im sure its mysql5.7 related [16:27] was working fine before they released that [16:27] I don't use kontact. In fact I avoid most of the KDE PIM, as I never got on with it [16:27] I use it a lot [16:27] and this is really bugging me now [16:27] 5 minutes its been trying to open this email [16:28] yes, things like akonadi and mysql backend for PIM used to be a complete PITA [16:28] so I got used to using stansalone apps for most of it [16:28] good idea [16:28] * clivejo opens gmail on phone [16:29] only thing from PIM I use is akregator, and that will run with akonadi disabled. [16:30] there we go, done and dusted on phone and Kontact is still thinking about it [16:30] thunderbird is getting long in the tooth, but still works great here [16:31] and I can tar.gz my TB profile if I need to move to a new machine, and it just works on the new one. [16:31] even a windoze one. (forgive me) [16:32] I love kde/kubuntu, but not PIM [16:36] morning [16:38] yofel: I tried my old key and still cannot access kci.pangea.pub any luck for you? [16:39] clivejo: I have had to manually merge everything. [16:39] be happy you did not pick applications.. === ovidiu-florin is now known as ovidiuflorin === ovidiuflorin is now known as ovidiu-florin === ovidiu-florin is now known as ovidiuflorin [17:43] umm what does the git clone all actually do? [17:47] the KA script? [17:47] yeah [17:47] it barfs on me. but I think I thought it was something it is not [17:47] it is grabbing both sources I see now [17:47] you can pass it the component [17:48] like to clone all apps [17:48] but well it fails so it grabs nothing [17:48] goes and grabs all the app git [17:48] has it been updated to use the correct git [17:48] ./git-clone-all -t ../yakkety-frameworks/ -r frameworks -d yakkety [17:49] File "/home/ftpubuntu/stable/frameworks/5.21.0/" not found. [17:49] Template url to clone: git+ssh://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/%s [17:49] does the -t path exist [17:49] uh yes [17:49] where is it getting that ftpubuntu junk? [17:50] try it with like "~/yakkety-frameworks [17:50] that is depot [17:50] same failure [17:51] why is it going to depot? I do not understand [17:51] oh well lost interest again. I will hack up a shell script [17:51] it was working for me [17:51] running ci update again. hope to fix at least mergers [17:52] sgclark: did you pull KA? [17:52] I can't do anything about docker until I get access to server or sitter decided to talk to me [17:52] clivejo: yeah got your changes [17:53] you had the login set as yourself# [17:53] wut? [17:53] I did not see a flag for login [17:54] "git-ssh-kubuntu":"git+ssh://sgclark-guest@git.debian.org/git/pkg-kde/%s/%s.git" [17:54] it uses you local environment to decide [17:55] sgclark: are you trying to login as 'ubuntu' to kci? [17:55] oh perhaps I did that on accident... I had terrible times with the script deciding for me [17:55] sigh [17:55] there's 4 of your keys in that account [17:55] all I am trying to do is use git-clone-all to for what I thought was a simple cloning of all repos [17:56] that's what it is supposed to do.. [17:56] oh [17:56] yofel I think we are talking of different things [17:56] just needs an URI fix for launchpad [17:56] sgclark: I was originally talking about kci [17:56] where I can login fine [17:57] I think it was probably trying to use scarlett [17:57] I am to use ubuntu@kci? [17:57] I have this in my ssh config (as I always forget that too): [17:57] Host kci [17:57] User ubuntu [17:57] HostName 54.252.111.19 [17:58] thank you [17:59] I am in thanks yofel [18:00]