15:11:05 #startmeeting kde-sig 15:11:05 Meeting started Tue Dec 22 15:11:05 2015 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:11:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:11:05 The meeting name has been set to 'kde-sig' 15:11:08 #meetingname kde-sig 15:11:08 The meeting name has been set to 'kde-sig' 15:11:11 #topic roll call 15:11:16 here 15:11:18 hi all, friendly kde-sig meeting, who's present today? 15:13:18 * heliocastro here 15:13:25 #info rdieter heliocastro present 15:13:30 may be a fast meeting (yay) 15:13:37 eheh 15:13:53 hi 15:13:57 topics: Possible solutions fotr a CI 15:14:05 #info tosky present 15:14:09 #chair heliocastro tosky 15:14:09 Current chairs: heliocastro rdieter tosky 15:14:13 topics: What is missing on frameworks/plasmas 5 15:15:15 #topic agenda 15:15:38 #info topic ideas: CI solutions, what's missing on frameworks/plasma 5 15:15:46 * dvratil is here 15:16:22 I can report on plasma 5.5.1 (2?) update 15:17:08 dvratil: k 15:17:13 we can start with that 15:17:22 #topic recent updates status 15:17:45 5.5.1 is in rawhide (should be complete now) 15:17:59 \o/ 15:18:04 Too late, 5.5.2 is released 15:18:06 * heliocastro hides 15:18:14 * rdieter slowly working through kde-apps-15.12.0 stack 15:18:16 but 5.5.2 was released today, so I might as well update to that in stables 15:19:11 dvratil: You are slow :-D 15:19:34 But seriously, this is a topic for thee possible CI 15:19:51 yeah, I know :( hard to time fine between all the eating and drinking ;-) 15:19:59 s/time fine/find time/ 15:20:15 no no, eat and drinking always priority 15:20:52 Depends on what you mean by "drinking". ;-) 15:20:52 * heliocastro afraid to look of his kg number few days after 15:21:34 wrt kde-apps-15.12.0 stuff, lots of new kf5 ports 15:22:00 so fun big stuff coming soon to rawhide: digikam (and friends libkipi, etc...) 15:22:06 cool! 15:22:13 (but that will be a fair amount of packaging work) 15:22:26 This "fixes" the thumbnail/preview generation 15:22:27 since it (digikam) also depends on kf5 pim stuff 15:22:35 oh 15:23:07 so doing the work on my f23 box will be interesting (I may have to rig up a rawhide devel box) 15:23:42 having a rawhide machine for testing probably will be a good thing anyway, particularly, because there is a kde spin blocker right now 15:23:49 (plasmashell isn't starting properly for some reason) 15:24:04 just remember that digikam is not exactly released yet 15:24:07 I'm *assuming* it's some sort of rawhide'ism (since it doesn't happen on f23) 15:24:14 tosky: sure, 5.0.0-beta2 only so far 15:24:32 I guess you could package KF5 PIM for F23- similarly to how you package kdepimlibs 4 for F24+. 15:24:38 I'm hopeful a stable release will be available by f24 release, but I probably should ask them 15:24:44 I.e., make the thing compile, but don't ship an Akonadi server for it. 15:25:08 Kevin_Kofler: maybe, but if I'm going to that much work, I'd rather spend that time getting rawhide working 15:25:30 we'll see, I'll come up with *something* 15:25:34 well digikam does not really depend on Akonadi, right? It only uses some of the libs that were part of kdpeimlibs4? 15:25:41 dvratil: right 15:26:03 those libs can be pulled to F22/23 easily, as they are co-installable with kdepimlibs4 15:26:03 so far, it only wants: KF5CalendarCoreConfig.cmake 15:26:28 (and KF5KipiConfig.cmake) 15:26:50 dvratil: if those libs are useful without kf5 akonadi, that would be nice 15:27:07 ok, I'll try that approach first 15:27:56 any other updates? 15:28:29 nothing else from me 15:28:38 moving on... 15:28:44 #topic CI solutions 15:28:48 heliocastro: ? ^^ 15:29:02 Ok 15:29:06 we have three options 15:29:12 1 - Use rawhide 15:29:19 and later update copr 15:29:28 2 - Use copr directly 15:29:41 and pass snapshots to rawhide 15:29:43 and 3 15:29:52 3 - Request usage of kde CI 15:30:04 An thought a 4th option actually 15:30:26 Use KDE CI as main Jenkins, but results and compile machine be rawhide OR copr 15:30:43 didn't know that was possible :) 15:31:02 rdieter: Jenkins is basically a control framework that uses other machines to do the job 15:31:17 since both koji or copr has command line 15:31:22 and notifications 15:31:32 we can control this from jenkins 15:31:50 I personally prefer any solution that uses rawhide since that has the added bonus of not having to manually sync/update anything there (right?) 15:32:27 I would be ok with rawhide option, but will be Adam ? 15:32:27 I guess that option wouldn't strictly be continuous either 15:32:35 But what do you want to CI? If you want to do daily/weekly snapshots as some other distros are doing, I don't think it's good to dump those into Rawhide because Rawhide eventually branches for release. 15:32:48 IMHO, a Copr is a better solution then. 15:32:55 CI for branch changes, not for each commit 15:33:22 If a new thing is tagged on branch, then wake up that specific package and generate a build 15:33:30 If you want to do only releases, then you can probably do it in Rawhide (but then that's not really "continuous" anymore). 15:33:43 Is continuos, but not daily 15:34:05 We just trigger the necessary rebuilds on depends 15:34:12 ok, if it's on tags, rawhide++ 15:34:26 Daily would be too much 15:34:39 Not impossible of course, but still too much 15:34:56 of course, the way kde releases happen, sometimes tags are pushed late 15:35:07 only after tarballs are released, depends 15:35:32 but that's a kde.org fixable problem 15:35:57 Yes, and this we can easily help them 15:37:50 heliocastro: let's take the results we have from our chat here so far onlist, see if we can find anyone else interested in helping, then come up with a concrete plan of action? 15:37:56 can you do that? 15:38:20 Yes, i do that tomorrow 15:38:56 thanks 15:39:15 #topic what's missing on frameworks/plasma 5 15:40:06 I already hinted at a bit of this: kde-apps-15.12.0 includes a lot more kf5 stuff, including kf5 libkipi (and friends), which is needed by digikam-5.0.0 too 15:41:11 heliocastro had the noble goal of trying to ship f24 kde spin kdelibs(v4) free 15:41:19 so others include: okular 15:41:46 * rdieter has to go in ~5 minutes, can someone else finish leading the meeting? (or maybe we can be done by then :) ) 15:41:51 * heliocastro too 15:41:59 finish now, and we continues on mail 15:42:25 any other notable kde4 stuff we still ship (I can't think of anything else) 15:42:27 ? 15:43:19 can't think of any other major app either 15:43:24 rdieter: And do you think F24 is a realistic target for that or do you think it's too early? I just don't have the big picture in front of me to answer that question myself. 15:43:58 without a firm list of apps, hard to judge, but given that we already know okular is in that list, the odds are not good 15:44:35 fyi, I see comps-f24 needs love to adjust kdepim pkgs to kf5 versions 15:45:14 IIRC, kdelibs3 went away with F12, so 3 releases after KDE/Plasma 4 was introduced. So that'd be F25 this time. 15:45:19 Kevin_Kofler: oh, I guess we still have konqueror/kwebkitpart 15:45:35 but hopefully we can kick that out in favor of qupzilla (or whatever) when qtwebengine lands 15:46:20 On second thought, I think keeping a kde4 runtime available would still be nice 15:46:57 The break point is pim 15:47:00 Okular will be released in time 15:47:01 Maybe krita on qt5 15:47:11 calligra in general 15:47:44 keeping kdelib4 runtime is ok 15:47:49 work in ongoing there, but no kf5-based prereleases yet that I'm aware of (like digikam) 15:47:52 make default plasma 5 depends on it no 15:48:11 ok, any final thoughts before closing meeting? 15:48:17 (or least before I have to leave)? 15:48:28 Is all ok from my side 15:49:10 ok, thanks everyone 15:49:12 #endmeeting