[00:00] ovidiu-florin: do you have the automation repo cloned? [00:00] no [00:01] where is it hosted? [00:01] git+ssh://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation use the git+ssh url [00:01] er wait [00:01] ovidiu-florin: use git+ssh://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation [00:01] aaaargh [00:02] chrome, please die [00:02] same link [00:02] https://help.launchpad.net/Code/Git#Configuring_Git [00:02] https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/ [00:11] ovidiu-florin: got it? === yofel changed the topic of #kubuntu-devel to: Kubuntu - Friendly computing | Plasma 5.5.1: W/TODO X/WIP Apps 15.08.3: W/TEST 15.12.0: TODO FW 5.17: W/TODO X/WIP | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | No, plasma 5.5 isn't packaged yet [00:11] .3 wip -> test [00:11] yofel: not yet [00:11] configurig git to use the roght username [00:13] yofel: done [00:14] good, now try this: ./package-name-list -d xenial -r frameworks [00:15] permission denied [00:15] where do I give my public key? [00:16] it's querying depot.kde.org, see README for the ssh username [00:17] I just whitelisted you, so try again when you're done [00:18] depot is the kde server for unreleased things [00:20] done [00:21] when the script succeeded, commit and push the change. The status page will pick it up on the next refresh [00:22] $ ./package-name-list -d xenial -r frameworks [00:22] got version 5.17 stable [00:22] write package-name-lists/frameworks-xenial [00:22] git diff package-name-lists/frameworks-xenial [00:22] that's it [00:22] that should actually show a diff.. [00:22] it printed that [00:22] nothing else got printed [00:23] what if you do git diff now? [00:23] package-name-lists/frameworks-xenial got modified [00:23] well good, then that worked at least [00:24] addeed breeze and oxygen icons [00:24] that's how we keep our package lists updated to show what we ship for a release [00:27] now what? [00:27] push the change [00:27] what commit message? [00:28] something sane? "Update frameworks package list for 5.17" or so [00:38] * ovidiu-florin Zzzzz [00:38] can we continue ub the nmorning? [00:38] * ovidiu-florin is off to bed [00:39] sure, I'm off shortly as well, nini [07:39] Good morning sexy people [07:41] yofel: shouls I procede and commit the change? [07:41] Sorry for last night, I fell asleep with my head on the keyboard [08:05] yofel: I've updated the KA clone, and ran it again. I see those changes are not pushed yet, so I'll commit them now [08:06] done [08:06] commited and pushed [08:06] yofel sgclark ping me when you're around, meanwhile I'll work on some KMail bugs === santa is now known as Guest24025 === _stowa_ is now known as _stowa === lordieva1er is now known as lordievader === lordievader is now known as Guest78182 === ejat_ is now known as ejat === Guest78182 is now known as lordievader [11:33] yofel: apps 15.08.3 are ready to test in Wily ? [11:33] l10n is missing, but otherwise they're ready in ppa-landing [11:36] yofel: why plasma 5.4.3 was not removed from landing ppa if it is in backports ppa ? [11:36] I forgot to do that [11:36] wouldn't it be a good idea to have ppas clear ? if something goes from one ppa -> to next [11:37] yes, but in this case, those packages are already in the target ppa, so it doesn't make a difference [11:37] otherwise I would've done the clean and recopy [11:39] i'm a bit lost :) i'm talkign about situation whan for exampel we have something in landing ; it was tested ; moved to backports ; than landing ppa should be cleard from this stuff that was just moved to backports [11:39] any ETA for Plasma 5.5 in backports, btw? :) (no hurry) [11:41] soee: first to make something clear, ppa-landing is for /ppa, not /backports. And in this case, those packages are in both PPAs, so they literally have no effect [11:41] so cleaning things up after I noticed my mistake, waiting for the janitor, then recopying - would've been a great waste of time [11:42] recopying ? [11:42] copy again? as I already copied them once from staging to landing [11:42] yofel: do you use some script to copy ppa -> ppa or it requires manual action? [11:42] script [11:43] oh so it can also auto-clean source ppa after packages hits target one ? [11:43] yes, we also have a script for that, but I don't auto-do that to prevent packages getting lost if LP somehow screws up a copy [11:45] but as I said, if it mattered, I would've fixed it. But in this case you have a PPA with A, and another one with A and B. So if you already have A, the A in the other PPA won't even be considered [11:48] yofel: "So if you already have A, the A in the other PPA won't even be considered" - yest this one is clear and i'm not worried about such situations :) All this as about having ppas clear s i think 1 or 2 days ago sgclark said that some builds were failing because of full ppas or something [11:49] that was CI, can't really keep that clear [11:49] so CI have nothign to do with landing ppa ? [11:51] kfunk: i think there is no ETA :) [11:53] no [11:54] hmm, wait we/me have already 15.08.3 in Wily .. [11:55] that was the hacked together backports set, this is the SRU set [11:55] adding ppa shows no updates at all [11:55] right, you need a system without backports to test this [11:56] oh ok, my mistake :) [11:58] np, It's not that obvious.. [12:12] Hiyas all [12:15] yofel: you're back [12:16] yeeey [12:16] tell me what to do [12:16] only for 20 more minutes, then I'm off watching star wars. Got to get the priorities right :P [12:17] anyway, thanks to your change, oxygen-icons now appears red on the frameworks status page [12:17] yaaaa a a y... [12:19] so what's happening with plasma 5.5? [12:19] WIP [12:20] ovidiu-florin: so looking at the build log, it's trying to run qmake-qt5 - which isn't something that exists [12:20] yofel: ECM cannot find qmake [12:20] at least not on debian systems... [12:21] so this might actually need a patch in ecm [12:21] BluesKaj: do you have Wily instance withoout backports enabled ? [12:22] yofel: can we confirm that qmake is on that machine? [12:23] soee, I have wily on the laptop, but the backports are enabled [12:23] haven't upgraded it yet [12:23] it's actually not, which is another issue. /usr/lib/x86_64-linux-gnu/qt5/bin/qmake is in qt5-qmake, which isn't installed [12:23] yofel: apt recommends to install qt5-qmake [12:23] but it doesn't install it [12:24] it suggests it, and buildds run with --no-install-recommends [12:24] so that's not a recommended, it a required [12:24] where does that get set? [12:24] right, for this build. So you need to add qt5-qmake in the Build-Depends field of oxygen-icons [12:26] I'm not sure where that is [12:26] yofel: ^ [12:26] somewhere in the KA repo? [12:26] right, so you'll want to add this to your gitconfig: [12:26] [url "git+ssh://git.debian.org/git/"] [12:26] insteadOf = debian: [12:27] done [12:27] then you go, git clone debian:pkg-kde/frameworks/oxygen-icons5 [12:27] git checkout kubuntu_xenial_archive [12:27] permission denied [12:28] ah dang, let me get the public url [12:28] where do you get the URLs from? [12:28] git clone git://anonscm.debian.org/git/pkg-kde/frameworks/oxygen-icons5 [12:29] memory myself, but give me a sec [12:29] http://anonscm.debian.org/cgit/pkg-kde/ has the pkg-kde repo list [12:29] usually it's pkg-kde//.git [12:30] got it [12:30] uhm, that has no kubuntu branch o.O [12:30] how do the scripts even handle that [12:32] yofel: so I just add it to control and comit , right? [12:32] wait a sec [12:32] soee, just tried to upgrade wily ..all packades up tp date [12:33] packages [12:34] BluesKaj: yes but there are Apps 15.08.3 SRU to test, won't do with backports enabled as they are installed than already [12:35] ovidiu-florin: ok sorry, I'm out of time, but something is really not right with o-i regarding git repo and epoch and stuff, so this will take a while longer [12:37] * ovidiu-florin didn't even notice BluesKaj 's typo [12:38] soee, Apps 15.08.3 SRU? [12:38] yofel: ok, ping me when you return [12:38] please don't forget [12:39] ovidiu-florin, I guess because I make so many typos , nobody notices anymore :-) [12:39] :))) [12:40] * sitter wonders what possessed yofel to go the movie theatre in the middle of the day [12:41] force? [12:44] sitter: +1 [12:45] sitter: can you help me with this building issue? [12:45] sitter: He's gone to see nativity 3 obviously [12:50] madness I say [12:50] ovidiu-florin: oxygen-icons5 should not need qmake. if it does that likely is a bug [12:52] sitter: what is that package anyway? [12:52] I dont' see a readme in it [12:53] what do you mean? [12:53] an, info I wanted is in control [12:53] * ovidiu-florin is reading the build logs again [13:00] sitter: I can't tell, where are the sources of oxygen-icons5 [13:00] ? [13:00] kde:oxygen-icons5 [13:01] ko [13:01] ok [13:24] sitter: oxygen-icons5 needs ECM [13:24] ECM needs qmake [13:28] [13:50] ovidiu-florin: oxygen-icons5 should not need qmake. if it does that likely is a bug [13:29] so you're saying tha toxygen-icons5 sould not need ECM? [13:29] no. I am saying "oxygen-icons5 should not need qmake" [13:51] it doesn't, directly === cyphermox_ is now known as cyphermox [16:25] soee, jubo has a habit of not paying any attention to advice. I find it very frustrating trying to help him . I mostly try to avoid him nowadays [16:26] :) [16:39] I've had pretty much the same experience with them [18:54] yofel: are you back? [19:03] <_Groo_> yofel: ping [19:06] <_Groo_> could anyone help me with the "kubuntu way of doing things now" , aka flow? [19:06] <_Groo_> i backported sddm to wily as requested [19:06] <_Groo_> 0.13 [19:06] <_Groo_> for now i sent it to one of my ppas, but how do i start using the proper kubuntu way? [19:07] <_Groo_> i read https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/README [19:07] <_Groo_> but im confused [19:07] <_Groo_> i dont know how to start, really :P [19:15] <_Groo_> yofel: anyway, sddm 0.13.0 is in https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pbppa/+packages [19:16] <_Groo_> yofel: lets use this package as a training/howto on how i should upload this packages properly [19:16] <_Groo_> yofel: once you have sometime (or any other kubuntu developer), give me a ping on how to proceed [19:18] <_Groo_> could anyone tell me where i get/download/add-apt the package/file/github/whatever that has ./package-name-list for ex? [19:19] <_Groo_> the stupid readme tell what to do but not where to download [19:19] <_Groo_> nvm [19:19] <_Groo_> <--- dumb [19:19] <_Groo_> https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation [21:53] yofel: ping [22:26] ovidiu-florin: re [22:27] yofel: how was the SW movie? [22:27] good, I'll leave it at that. [22:28] ;) [22:29] _Groo_: first of all, by assigning the relevant bugs to you and setting them to in progress *before* you get to work ;) [22:29] we use those for coordination and duplicate-work prevention [22:32] yofel: sitter said oxygen-icons5 should not depend on qmake [22:33] it depends on ECM and ECM depends on qmake [22:34] right, and he does have a point. [22:35] sgclark: why are there backport changelogs in kde-l10n-common ?!? [22:35] * yofel deletes those [22:36] yofel: so it should not depend on ECM? [22:37] if it does not require it, no (see CMakeLists.txt) [22:38] cmakelists requirs it [22:39] then it needs to depend on e-c-m, but maybe e-c-m is missing a runtime dep [22:44] I don't understand [22:45] well, it has to depend on e-c-m, otherwise it will fail with "missing ECM" [22:45] and then that means ecm needs qmake marked as a dependency, right? [22:46] sounds like it - or harald meant to check whether the ECM component that uses qmake is actually needed, which would make that an upstream bug that it uses something it doesn't actually need [22:46] can't really say without actually looking into it [22:47] in such situations I usually just build locally, get it to build, then when I know what was wrong, I look into it in more detail [22:47] where locally == pbuilder chroot [22:49] currently the qmake-qt5 thing is irritating me, as I don't know what that's supposed to be, but I'm not an ecm expert either [22:53] yofel: would it be wrong to add it as a dependency? [22:53] to ECM? [22:54] If the ecm cmake files have qmake calls in them, no [22:56] yofel: can we have a hangout please [22:56] I don't understand this [22:56] _Groo_: and before I forget the rest of my answer: thanks for doing that! I'll try to look at it soon so we can upload it to xenial. [22:57] sddm will probably also need a git base merge though [22:57] ovidiu-florin: well ok, lets try [22:58] can I listen in? [22:58] I have nothing against it [22:58] I'll leave the setup to you then [22:59] wait, how does hangouts even work these days [23:00] oh right, there was that app [23:00] yofel: here: https://meet.jit.si/ImmenseVegetablesOfferRemorsefully [23:00] this is easier [23:00] and it's free software [23:00] fine with me [23:06] yofel: emc control requires qttools5-dev, doesn't that bring in qmake as well? [23:11] o/ soee_ [23:12] <_Groo_> yofel: ellisistfroh replied to me by email regarding sddm [23:12] <_Groo_> yofel: some stuff i need to change [23:13] <_Groo_> yofel: what ive been asking since the beginning , is exactly HOW should i proceed when doing packages. you said i need to assign the bug to me, you mean via lp? thats what im trying to figure out here, the proper workflow [23:14] <_Groo_> it would help newcomers if you guys had a "first contribution" for dummies, with all the steps involved [23:14] <_Groo_> but ok, let me assign the the bug to me [23:15] <_Groo_> https://www.irccloud.com/pastebin/cezWBd22/ [23:15] <_Groo_> how do i do a SRU-backport? what are the steps [23:15] <_Groo_> ? [23:15] <_Groo_> i know how to package stuff, i just dont know how to do it with your workflows and rules, thats what im trying to learn [23:16] <_Groo_> so i can start doing bigger steps and play with the automation scripts and the like [23:20] _Groo_ you would need to package it for xenial first I think [23:20] <_Groo_> clivejo: that is easy [23:20] <_Groo_> clivejo: ill do it when i get home [23:20] get it tested [23:20] <_Groo_> clivejo: how? [23:20] <_Groo_> clivejo: besides testing myself [23:21] <_Groo_> clivejo: that didnt sound right :P [23:21] there are people here who can test [23:21] <_Groo_> clivejo: ill announce it here [23:21] put it into your PPA and use the bot to announce it [23:21] <_Groo_> clivejo: ok [23:22] if everything checks out yofel can then put it into the xenial archive [23:25] one of the release managers can then apply for a SRU request to put it in wily, if needbe - https://wiki.ubuntu.com/StableReleaseUpdates [23:26] _Groo_: is there a LP bug open for it? [23:29] is this the LP bug - https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1516837 [23:29] Launchpad bug 1516837 in sddm (Ubuntu) "[update request] SDDM 0.13.0 released on Nov. 4th" [Wishlist,Triaged] [23:30] <_Groo_> yes it is, ill apply to it [23:31] <_Groo_> clivejo: there, i assigned it to me [23:32] <_Groo_> ill work on xenial and announce it here, prolly tonight or tomorrow, im going home from work in 20 min [23:33] you can refer to the bug in your changelog [23:33] <_Groo_> will do [23:34] then LP should autoclose it when it gets uploaded [23:36] LP 1519564 [23:36] Launchpad bug 1519564 in sddm (Ubuntu) "[merge request] SDDM 0.12.0 released on Sept. 5th" [Wishlist,Triaged] https://launchpad.net/bugs/1519564 [23:38] same bug me thinks [23:39] anywho, Im off to bed [23:39] night all [23:52] _Groo_: hey, I was just talking to ovidiu about the workflow, and we'll try to come up with something next week. [23:52] Currently our workflow is a mess, it's undocumented and to make things even more fun it's currently changing [23:53] The LP bug workflow is the standard ubuntu workflow, but I don't remember where the documentation for that is either :/ [23:54] for the automation stuff, the current workflow is roughly outlined in the README, I don't really know how to extend that, so suggestions welcome [23:56] also, there's no such thing is an SRU-backport [23:56] !sru [23:56] Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates [23:56] is exlcusively for bugfixes [23:57] I'm fairly sure that there will be wily people that will want to use the newer sddm, so we can put it into our backports ppa for them [23:57] you could even do an offical backports request, which is documented somwhere on wiki.ubuntu.com [23:57] yofel: is it safe to upgrade sddm without complex tesing ? [23:58] not really, which is why I wouldn't do that without testing it in xenial for a while [23:58] +1 [23:59] but our backports ppa is a place where "shit can happen", so if someone is prepared to update qt, plasma, frameworks and apps to a new major version, sddm doesn't make things that much worse