18:31:06 #startmeeting 18:31:06 Meeting started Tue Jan 8 18:31:06 2013 UTC. The chair is tittiatcoke. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:31:06 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:31:23 #meetingtopic Welcome to the openSUSE KDE community IRC meeting! Please wait with other discussion until the meeting is over. This meeting is logged. 18:31:34 The agenda for tonight is: 18:31:49 1. Should we remove things which were maintained by SUSE before and are basically unmaintained now, e.g. kio_sysinfo (ctrippe) 18:31:56 2. Status KDE 4.10 release 18:32:02 3. Status KDE 4.9.x releases 18:32:08 4. Artwork (openSUSE KDE Desktop theme, lightdm-kde-greeter, etc) 18:32:16 5. Include KDE Telepathy in openSUSE 12.3 18:32:32 6. Validation/Status of the items on our KDE Improvement page. 18:32:40 7. Remove old repositories (krop) concerned: KR46, KR47(?), K:U:P/(KR47,KR48,KR49_12.1) 18:33:27 Any other topics ? 18:33:39 8. Other issues 18:33:45 8. Misc :p 18:33:46 :-) 18:33:46 simon... there 18:34:00 I didn't want to list the standard topics :-) 18:34:10 Ok. Let's start with the old action items 18:34:25 #topic Action Items 18:34:35 items from the last meeting: 18:34:45 tittiatcoke shumski update the kdebase4-openSUSE github repo with the new plasma-theme and submit to factory 18:34:48 This one is done 18:35:04 tittiatcoke keep the discussion apper/kupdateapplet on the actionlist until we know what happens with the PackageKit zypp backend. 18:36:09 Status here is that the zypp backend is not adjusted so far, but it seems we found a new volunteer that is willing to port the zypp backend to the new PackageKit version. Dantti has offered his help here as that he is interested in getting the new apper version released/shipped 18:36:36 what a shame for the zypp maintainers 18:36:36 next action tittiatcoke set out an actionplan to decouple KR49 from KDF and then to update KDF with the 4.10 packages 18:37:25 rabauke: I know. I send out an email to the ML to get feedback on what they wanted to do, but almost no feedback. It seems that they lost interest in the new PackageKit (or they do not have the time) 18:38:09 The decoupling of KR49 from KDF has been done. And KDF contains 4.10 RC2 atm. (see also separate agenda point) 18:38:27 adra push kde-gtk-config to KDF for inclusion in Factory. 18:38:38 adra: afaik, this is done, right ? 18:38:53 yes 18:39:08 wstephenson & einar77 create a patch-formatter to add the kde standard headers. 18:39:20 wstephenson: Any status on this one ? 18:39:40 no, sorry 18:39:50 No problem :-) 18:39:59 einar77, ctrippe Organize a bug squashing for the KDE bugs in 11.4. 18:40:24 I believe this was done. At least there was a week of cleaning up bugs, etc :-) 18:40:42 yup, few moths ago :-) 18:40:44 we discovered that having 2 kids is more work than 1... 18:41:08 wstephenson: can't you return the second? 18:41:15 :-) I know. But believe me it will get better eventually :) 18:41:16 wstephenson: customer rights... 18:41:52 i could ask my wife but i wont be able to code if she knocks me out 18:42:37 Let's not do that :-) We don't want anybody getting hurt :p 18:42:53 ctrippe_: Are you there ? 18:42:58 have to leave, sorry. 18:43:11 krop: Ok. 18:43:32 tittiatcoke: yep, sorry. 18:43:35 #topic Should we remove things which were maintained by SUSE before and are basically unmaintained now, e.g. kio_sysinfo 18:43:41 The bug squashing happend 18:43:59 ctrippe_: Ok :-) But you raised also the indicated topic about kio_sysinfo. 18:44:05 * plinnell waves 18:44:28 ctrippe_: Could you explain ? 18:45:25 We have severel things packaged which were maintained by suse before and are to my knoledge no unmaintained, e.g. sysinfo 18:45:46 You will find several bugs about it which nobody cares to fix 18:46:20 what about moving them upstream into their unmaintained folder? 18:46:26 I also tend to think sysinfo is doing more harm than good these days 18:46:45 dunno if there are any other examples though 18:46:53 their = KDE 18:46:59 rabauke: I believe that sysinfo is already somewhere on KDE git 18:47:30 wstephenson: do you know what happened with sysinfo ? 18:47:37 tittiatcoke: then it can be removed IMHO if it causes trouble. 18:47:40 cb400f: We have other patches like ksuseinstall.. 18:47:55 it is upstreamed, but there are distro specific backends 18:47:57 true.. that one prolly does more harm than good too 18:48:26 wstephenson: Ok. 18:48:38 ctrippe_: But do we have bugs reported for ksuseinstall ? 18:48:48 I have at least one 18:48:49 cb400f: details? 18:49:09 https://bugzilla.novell.com/show_bug.cgi?id=671578 18:49:13 openSUSE bug 671578 in openSUSE 12.2 (KDE4 Workspace) "ksuseinstall does not respect "don't ask again"" [Normal,New] 18:50:22 wstephenson: it'll install weird gnome apps for handling things cuz of issues with .desktop files/mimetypes I guess.. and prompt people about missing stuff which is not available in their repos anyway 18:50:22 trivial to fix 18:50:29 yet noone has done it in years 18:50:50 wstephenson: You will take that one ? 18:51:21 bigger problem that we dont wontfix bugs we wont fix.. 18:51:25 tittiatcoke: sure 18:51:29 Ok :-) 18:52:10 #action wstephenson will work on ksuseinstall (bug#671578) 18:52:34 cb400f: about installin mimetypes. It searches for apps supporting the mimetype and installs the fist one. ANd 'g' comes before 'k' 18:52:39 wstephenson: But the wontfix bugs, I guess is a global issue and not just for KDE bugs ? 18:53:30 tittiatcoke: yes 18:53:35 Ok :-) 18:53:52 ok sorry 18:53:58 I managed to arrive at last 18:54:21 einar77: hi. We are at the first agenda item with regards to suse specific tools. 18:54:40 quikcly checking the backscroll 18:55:22 What would be the opinion for kio_sysinfo ? Drop it or try to fix it ? 18:55:36 tittiatcoke: point 1. does it work? 18:55:44 point 2. does it have outstanding issues? 18:56:19 einar77: both points is yes. I am not sure what outstanding issues we have 18:56:52 I would argue for dropping then 18:56:53 people always click on internal filesystems and expect them to be mounted/accessed... and it doesn't happen 18:58:18 My rationale for not dropping "custom" tools is: a. be self-maintaining (i.e. trivial stuff, stable for years etc) b. have someone (from the community?) maintain it 18:58:33 but I'd rather go for a. 19:00:13 me too 19:00:40 and then the follow-up question is, do we have tools which fulfill the "a" requirement? 19:00:47 kio_sysinfo does not look like one 19:00:53 it's dead weight.. with little added value over what kde provides.. and bugs and no maintenance 19:01:03 my vote goes for axing 19:01:06 I'd vote to drop the greeter too now that we're at it 19:01:09 +1 19:01:13 cb400f: which greeter? 19:01:26 the one with all the outdated information on first login 19:01:26 SUSEgreeter 19:01:28 SUSEgreeter 19:01:28 the stuff that appears at startup? 19:01:35 cb400f: Why that one ? 19:01:36 hmmm 19:01:43 cb400f: how can that be updated? 19:01:56 I think it's a html file in git somewhere 19:02:11 afaik ctrippe_ fixed that link ? 19:02:30 cb400f: if it's just HTML, it should be just fixed 19:02:50 nah, cuz next release it won't be updated again.. and users don't read it anywho 19:02:56 It's html + a bit of code 19:03:19 pull it out of git and put it into the package so everybody with access to obs' webgui or more can update it 19:03:57 hmmm perhaps 19:05:04 rabauke: At this moment it is in the kdebase-opensuse github repo, where we also have the other KDE defaults (plasma, etc). We have access to that one and we are building the package (kdebase4-openSUSE) 19:05:35 and the link now points to userbase.kde.org 19:05:40 but apparently it is too hidden for "casual" contributors 19:05:52 userbase.kde.org is quite active wrt end-user docs 19:05:54 so it's ideal 19:06:20 rabauke: Then we can agree that the package kdebase4-openSUSE can be maintained on OBS and on regular basis we are updating the git repo. 19:06:53 whatever helps to give easy access to the text that needs to be updated. 19:06:53 I would rather do the other way, proper source control is ++ 19:07:05 (no, OBS isn't a proper VCS) 19:07:17 einar77: true 19:08:03 tittiatcoke: perhaps better connections between obs and the repo 19:08:15 I have no idea how it is built from there (source service?) 19:08:31 in any case, before drifting too far from the topic, I'd say the greeter should not be drpped 19:08:32 einar77: Nope. somebody has to download the git-repo and make the tarball :-) 19:08:38 ugh 19:08:47 einar77: :-) 19:09:03 einar77: I guess some optimization can happen there :-) 19:09:23 And no source services allowed in Factory :-) So we need a tarball 19:09:35 bleh, yes, requires some thought 19:09:41 what sources should be lost? they are outdated and close to being dropped because of that. 19:09:46 I guess that we reached an alignment to drop kio_sysinfo ? 19:09:49 yes 19:09:51 I think 19:10:09 not sure instead on susegreeter (personally -1 on dropping) 19:10:20 #agreed Drop kio_sysinfo from the KDF/Factory repo's. 19:10:37 Who is in favor to drop the SUSEgreeter ? 19:10:43 o/ 19:11:03 If we drop sysinfo now, we have to modify a few patches 19:11:39 ctrippe_: Let's see indeed where we have to make adjustments. Maybe we can do this together with RC3. 19:11:44 +1 dropping suse greeter 19:11:54 sysinfo is ok for now 19:12:19 I would say: keep the greeterfor now 19:12:38 wstephenson: alin rabauke any preference ? 19:12:56 shumski: ^^ 19:13:09 i would drop it, but no strong opinion about it 19:13:09 tittiatcoke: keepit 19:13:09 keep the greeter and make its content easily available, i.e. without git. sysinfo, drop it, if there are major issues. 19:13:15 I do not use it so I cannot tell. 19:13:25 :-) 19:13:42 the greeter is nice... tohave if not too much trouble I can maintain 19:13:57 #agreed Keep the SUSEgreeter, but make the content easily available for updates. 19:13:58 at the end there is jsut some text with two links 19:14:03 rabauke: There is the tarball in kdebase4-opensuse which also contains the greeter 19:14:21 alin: Yup :-) 19:14:26 ctrippe_: no need to access any git repo? 19:14:59 rabauke: Sure you can patch kdebase4-opensuse like any other package 19:15:09 rabauke: That is what I initially indicated. You can update the tarball and then we have to update the git repo from the tarball 19:15:19 The question is if tittiatcokeaccepts such submissions or sents you to git :-) 19:15:51 ok, I will write that down somewhere in the wiki so we can point people to it next time somebody asks how to jhelp 19:15:52 I might easier and faster accept SR's then git pull requests :-) 19:16:02 rabauke: Ok. 19:16:24 Ok. I guess the last one in this area is the ksuseinstall. Dtop it or keep it ? 19:16:38 drop 19:17:27 anybody else ? 19:17:32 drop 19:17:43 tittiatcoke: what is that for? 19:17:45 drop it because of the mimetype stuff and keep because of working kaffeine + libxine-codecs -> no vote from me 19:18:25 alin: it hooks into a few mimetypes to grab codecs when they are not available 19:18:37 ping llunak whether he wants to take care of his baby. if not drop it 19:18:54 also if you click on a .php it 19:18:54 rabauke: I was rhetoric... 19:18:54 alin: http://help.opensuse.org/ksuseinstall/ 19:19:03 in theory packagekit should offer the same functionality 19:19:04 'll suggest to install gedit or something like that 19:19:13 from me drop it... 19:19:35 wstephenson: There is a big difference between theory and practice when it comes to packagekit :-) 19:19:35 just let us hope gnome does not have something like that that takes over the computer 19:19:50 the value add ksuseinstall offers should be doing a better job, eg letting you add community repos 19:20:24 wstephenson: this value drops like 1/n for n-> inf, if it does not work 19:20:28 cb400f: that happens because gedit pollutes the mimetype database with excessive capabilities 19:21:09 I can imagine :-) .. but I guess there's no feasible fix for that 19:22:24 So far we have a majority for dropping ksuseinstall. 19:22:55 drop it, from me also 19:23:09 I agree with rabauke, maybe llunak has time to maintain it? it's the best opensuse can offer legalwise for 'newcomers' 19:24:16 Ok. Then lets agree that I will ask llunak if he has time/willingness to maintain ksuseinstall. If not, then we drop it. Decision should be made latest by the end of the month (due to 12.3) 19:24:25 he clearly doesn't.. maybe he could be bullied into fixing one or two bugs, and then leave it to bitrot again 19:24:58 i don't know how interested llunak is in kde at all these days 19:25:20 he still joins the channel, but i suspect he's just using kor and hacking on libreoffice 19:25:55 wstephenson: Let's see. I think that we owe it to ask him if he is interested to support ksuseinstall or not. 19:26:00 agreed 19:26:36 #action tittiatcoke ask llunak if he is willing/interested to support ksuseinstall. If not then ksuseinstall will be dropped 19:26:39 i am looking at that code and the 'don't show again' checkbox should work, the config key is set 19:26:49 ctrippe_: Any other suse specific programs ? 19:26:58 do we have others? 19:27:06 einar77: I don't know :-) 19:27:10 einar77: sure 19:27:11 I guess not. 19:27:28 reduced menu depth in kickoff 19:27:30 well there was a discussion to use a native updater applet again ;) 19:27:44 wstephenson: that's as bad as the "remaining battery time in plasma" 19:27:47 You mean the YOU ? 19:27:59 Has one long standing bug but otherwise works, so I amfro keeping it 19:28:20 wstephenson: to be honest, I'd prefer that the zypp backend for pk would get some interest, but it's clearly not a priority 19:28:36 ctrippe_: Maybe we should discuss it with the upstream maintainer of kickoff if he/she is willing to take this upstream ? 19:28:48 that guy working on that appstore thingy for gsoc must be really pleased 19:28:57 I thought dantii would take over 19:29:03 but I guess he should have seen it coming 19:29:06 einar77: Dantti offered to help with porting the zypp backend to the new pk 19:29:12 tittiatcoke: Sounds good 19:29:36 tittiatcoke: it mostly depends on how big of an endeavor is 19:29:45 with some sed scripts 19:29:49 Let's hope that it is as easy as that it sounds :-) But then we get the question if coolo is going to accept a new PackageKit or not for 12.3 19:29:49 tittiatcoke: there's no "maintainer" for kickoff 19:30:02 also upstream will switch it to a c++/qml hybrid for 4.11 19:30:08 einar77: Ok. 19:30:41 (at least, that's the intention) 19:31:08 I guess that all are in favor of keeping the kickoff patch for the reduced menu depth ? 19:31:25 yes, if it works 19:31:26 tittiatcoke: until upstream will diverge (in ~6 months after 4.10) 19:31:29 I have no issues with it 19:31:31 sure, keep it till its broke 19:31:40 erm broken ;-) 19:31:42 i thought it was broken for a long time? was it fixed? 19:31:47 I prefer the submenus over the upstream model too 19:32:20 wstephenson: Yes but only if you start to move thigs in a "bad" way 19:33:05 For refernce https://bugzilla.novell.com/show_bug.cgi?id=356553 19:33:08 alternatively we could drop kickoff and switch to homerun :-) 19:33:09 openSUSE bug 356553 in openSUSE 12.2 (KDE4 Workspace) "Creating New KMenu Submenu Makes Single Sub-Menu Items Invisible in K-Menu and Kickoff" [Normal,New] 19:33:34 tittiatcoke: weshould consider it for 12.3+1 by starting early and switchign perhaps 19:33:37 IF it's viable 19:34:08 i'm a bit disappointed by homerun tbh. can't seem to keyboard navigate it 19:34:24 wstephenson: haven't tested yet (I use only krunner) 19:35:23 but I agree on keeping the patch 19:35:27 wstephenson: Correct. The menu's can not be chosen by the keyboard. 19:35:29 till it breaks, why not? 19:35:35 the places category is cluttered 19:35:59 the keyboard thing alone sounds like a shipstopper to me 19:36:10 cb400f: +1 19:36:22 none of the 15 fulltime developers bluesystems have on it like to use their kb? 19:36:23 #agreed keep the kickoff patch for reduced menudepth 19:36:39 ctrippe_: Any other that you want to bring up ? 19:36:44 no 19:36:46 or maybe it's just intended for touch screens 19:36:49 no 19:36:56 no 19:37:08 #topic Status KDE 4.10 release 19:37:27 tittiatcoke: what in particular about 4.10? 19:37:43 cartman approved it for 12.3 19:37:59 I just wanted to give a quick update :-) 19:38:05 good, so nightmares about having to rediff my patches are over 19:38:31 I am not sure if everybody knows that we have a 2 week delay in the official release of KDE 4.10 and that this goes over the pre-release freeze for 12.3. 19:38:56 wstephenson: Question is if coolo is fine with it :-) 19:39:58 Based on the delay, I have asked the Release managers if we could have an exception and push 4.10 Final just before the pre-release freeze (4 - 5 February). So far we have a green light from cartman with support from wstephenson. 19:39:58 didn't coolo leave for suse? or was that somebody else? 19:40:04 coolo wrote something about updates on -factory ml today :-) 19:40:09 cb400f: Yup 19:40:13 especially as we talked about generally enforcing version freeze more strictly this release 19:40:26 coolo: are you ok with it? 19:41:34 http://lists.opensuse.org/opensuse-factory/2013-01/msg00083.html 19:41:46 while we are waiting. when will kr410 be created? 19:41:48 he says packages with little risk are allowed.. I guess that includes kde sc ;-) 19:42:43 I am planning to create KR410 when RC3 is released. 19:42:53 ok 19:43:10 wstephenson: tittiatcoke but kde 4.10 would be out before at least the tar balls 19:43:24 so technically at the moment we are still before the freeze 19:43:34 the tarballs are out 1 week before 19:43:37 alin: I know, but we can not publish the packages officially 19:43:37 we will simply not publish them on 5 19:43:51 alin: it's a bit sophistic, I'd say 19:44:24 I mean since we will not publish before the release day 19:44:38 (as upstream I'd kill you all if you did ;) 19:44:59 I am sure that we can work things out. :-) Have faith. In the worst case we ship 12.3 with KDE 4.10 RC3 and have a maintenance update ready when 12.3 is released :-) 19:45:03 yes 19:45:24 indeed 19:45:40 upstream has also started the testing initiative 19:45:46 So whatever happens the user will get 4,10 final :-) Either with 12.3 or directly as maintenance release. 19:46:19 Ok. I will keep all of you posted on the progress and status of getting 4.10 final into 12.3 19:46:32 With this I would like to switch to the next topic 19:46:40 #topic Status KDE 4.9.x releases 19:47:10 I think upstream wants to do one more release 19:47:18 but I'm not that up to date 19:47:26 einar77: They do ? I thought that 4.9.5 would be the last one. 19:47:30 ok 19:47:34 I think so too 19:47:36 then we're already at 4.9.5 ;) 19:47:42 that was what I was missing 19:48:31 Yup. KR49 got 4.9.5 19:49:48 any questions on KDE 4.9.x ? Most of the repo's are now disabled from building. And I am wondering if we should keep on providing rebuilds purely based on changes with libqt4 19:50:22 would there be any significant fixes in libqt4 at this point? 19:50:43 sounds like a waste of buildpower and bandwidth to me.. rebuilding that stuff 19:51:04 cb400f: KR49 has already got Qt 4.8.4, so I guess we can keep it that way and not to rebuild it 19:51:37 So for now let's keep them disabled 19:51:49 Next topic :-) 19:51:52 #topic Artwork (openSUSE KDE Desktop theme, lightdm-kde-greeter, etc) 19:52:08 shumski: can you give an update on your work ? 19:53:00 shumski: well, i guess we should wait for Beta to get a broader feedback, so far i'm left in a dark wether is this any good :-) 19:53:26 Did everybody saw the new plasma theme ? 19:53:31 shumski: more blogging needed? ;) 19:53:50 einar77: nope, more testers :-) 19:54:03 I saw screenies.. is it intended as the default? 19:54:14 cb400f: Yup 19:54:40 i am currently working on KDM and Ksplash 19:54:43 well, my current plan is to fix some icons, and polish the dark colorscheme 19:54:47 just for the record I'm very much against any dark theme as default 19:55:09 i think we are not going to stick with a dark color scheme as default cb400f 19:55:33 does the plasma theme follow kde color scheme? 19:55:56 it is quite transparent 19:56:01 cb400f: we have 3 colorshemes, 2 lighter ones, and one darker which uses the plasma colors 19:56:03 but has some noice overlays 19:56:26 but i guess we could remove the noice from the plasma theme, as it's now on the wallpaper 19:56:46 and yes cb400f the wallpaper will be a mix of dark gray and green. 19:59:43 shumski: Maybe we can make the colorscheme and the plasmatheme seperately available as tarballs ? 20:00:03 do we want a lightdm theme? I'm not sure as lightdm is still not suitable for normal usage with systemd 20:00:06 tittiatcoke: as in separate packages? sure 20:00:17 then more people can try out at least the colorschemes and maybe also the plasma-theme 20:00:40 einar77: At this moment lightdm can not be used without consolekit 20:00:54 at least not reliable for end-users 20:01:21 tittiatcoke: i can make the packages, it's just the question where? 20:01:30 cb400f: Maybe when shumski publish the schems, you can have a look at them, try them out and provide feedback ? 20:01:36 tittiatcoke, the plasma theme requires at least a current kde setup and won't fully work on 12.2 but i guess everyone here is up2date ;) 20:02:09 marcus: well, will work, just maybe not in a way as with 4.10 20:02:09 marcus: Don't bet on that :-) I am sure the majority is using 4.9.x :-[) 20:02:20 and I'm on 4.8 even 20:02:22 hehe,, ok 20:02:45 but I should get my act together and set up a virtual machine for KDF 20:02:58 :-) 20:03:19 shumski: do we build your theme also for 12.2 in KDF ? 20:03:20 also I'll install 12.3 beta on my testpartition 20:03:27 great 20:03:35 (unless I hear rumours about grub2 messing things up) 20:03:39 tittiatcoke: nope, just for Factory 20:03:50 shumski: Maybe we should also make the changes for 12.2 :-) 20:04:05 tittiatcoke: good idea :-) 20:04:24 it is KDF after all 20:04:24 cb400f: grub2 works :-) 20:04:37 Ok. anything else about the KDE artwork ? 20:04:38 it just does not look good ;) 20:04:53 I'm sure grub2 works decently.. it's actually more the yast bootloader setup that worries me a little bit 20:05:02 ;-) 20:05:09 cb400f: Have faith :p 20:05:31 Ok. next topic :-) 20:05:37 #topic KDE Telepathy 20:05:56 tittiatcoke: aside the issues with haze, I think it's mature enough to replace kopete 20:06:07 einar77: what issue with haze? 20:06:15 er 20:06:17 not haze 20:06:19 farstream 20:06:23 too many things 20:06:24 einar77: but that is solved... 20:06:29 already? 20:06:39 einar77: there is a compat package 20:06:44 alin: we still don't have call-ui working 20:06:54 it's just that it built 20:06:55 shumski: what do you mean? 20:07:04 shumski: I can see myself... 20:07:28 alin: ok, i tried with a few people, didn't work 20:07:33 shumski: plus I think that is on top of kopete's capabilities... 20:07:36 shumski: what did not work? 20:07:46 alin: video didn't work 20:07:59 shumski: strange... 20:08:32 shumski: does kopete provide video? 20:08:37 yes, for some 20:08:39 protocols 20:08:42 alin: for gtalk afaik 20:08:44 not sure if it *works* now 20:08:46 Ok. Despite if things are working or not, I really wonder if we should push it to KDF/Factory now as that it is a new feature. And we have past the 12.3 Feature freeze. 20:08:58 tittiatcoke: a little late 20:09:06 Yup 20:09:07 offer it in outside repos 20:09:14 but more widely advertised 20:09:17 tittiatcoke: i think we shall have it not install 20:09:20 tittiatcoke: sflphone wasn't packageable? 20:09:27 tittiatcoke: as default... 20:10:00 We have KTP in KDE:Extra, so it is available for people and after 12.3 we should move it to KDF so that we can move it to Factory. 20:10:26 +1 20:10:32 +1 20:10:47 cb400f: sflphone is packaged somewhere in network:telephony 20:11:01 Seems to be an old version however. 20:12:42 yeah, and no kde frontend, right? 20:13:05 cb400f: There is sflphone-client-kde package there (as well as a gnome client) 20:13:34 cb400f: You have the common package and then a package for the kde client and a package for the gnome client 20:13:38 oh, nice.. wonder why it didn't appear in my webpinstant search 20:14:00 but it seems somehow unmaintained at the moment :-( 20:14:24 I will create an update to the latest version and submit. Let's see if we can take over maintainership there :-) 20:14:53 Anything else on KDE Telepathy ? 20:15:22 #topic Validation/status of the items on the KDE improvement page. https://en.opensuse.org/openSUSE:KDE_improvements 20:15:25 tittiatcoke: I am for including it... we may get more people to test 20:15:45 alin: noted. Let's see. 20:16:46 Looking at our improvement pages, I see the following items without a real status: 20:16:55 ktp should definitely be included if possible, but maybe not default.. don't the kubuntu familia already use it as default? 20:17:06 cb400f: yes 20:17:12 cb400f: and fedora too 20:17:16 cb400f: I will talk to coolo to see if we still can get KTP in there :-) 20:17:49 tittiatcoke: knights was ont he list 20:18:03 yup. But nobody picked that one up. 20:18:10 tittiatcoke: and check wiith DimStar will he accept compat package. or don't ship call.ui 20:18:14 tittiatcoke: it is in extra... all it needs is a sr 20:18:16 game of kings needs to be in the distro for kings ;-) 20:18:17 Same goes for Kamoso :) 20:18:25 :-| 20:19:04 tittiatcoke: I discovered vlc is better to take pictures witht he camera 20:19:10 :-) 20:19:36 initially kamoso used vlc as a backend ;-) .. until it went with always fun gstreamer 20:19:48 it has this bug currently https://bugs.kde.org/show_bug.cgi?id=307147 20:19:49 KDE bug 307147 in kamoso (general) "Build failed against libkipi 2.0.0" [Normal,Resolved: fixed] 20:19:58 tittiatcoke: cb400f https://build.opensuse.org/package/show?package=knights&project=KDE%3AExtra 20:20:02 say it and I will sr it 20:20:17 (it's fixed, but seems kipi plugins don't work) 20:20:19 I think is already at the last version 20:20:35 moin 20:20:43 coolo: Hi :-) 20:21:02 evening 20:21:13 einar77: time is relative.. and persona 20:21:14 l 20:21:15 how are the ladies? 20:22:52 coolo: we have two questions. First one is regarding my email to be able to update KDE 4.10 to Final just before the pre-releaes freeze (packages would be submitted somewhere around 3-4 February. (That is the email that I send to you). 20:23:47 yep, ismail already ACKed 20:24:05 coolo: second one is if you still would accept some side packages into 12.3 coming from KDE. We are then talking about KDE Telepathy and Knights (Chess frontend) 20:24:18 kamoso! :-) 20:24:24 tittiatcoke: as soon as the apper situation is green I'm open to talk about updates 20:24:34 I don't want to talk about chess games if we have no working update applet 20:24:45 or zypper backend 20:24:52 coolo: understood. 20:26:48 nice, kde being bound to the faith of zypp people caring. 20:27:09 let's hope that dantti can do some miracle work 20:27:15 rabauke: if dantti manages to fix it, it's a non issue 20:27:20 we need to wait at the moment 20:27:38 is there a problem sticking with the old packagekit? .. it has been working better than ever lately 20:27:45 cb400f: are you using vlc? 20:28:01 cb400f: no need of kamoso... 20:28:01 if he does the job it will be even more embarrasing for the opensuse zypp devs 20:28:10 sometimes.. I'll need to try the webcam feature.. it's new to me that it exists 20:28:12 cb400f: Actually I have been using apper and don't really have issues 20:28:23 me neither 20:28:23 rabauke: but that's not our interest at the moment, we're interested in a working update applet 20:28:26 people often ask about such stuff.. and install cheese on kde systems 20:28:51 alin: Also vlc is not offered by openSUSE repositories 20:28:53 i am not too optimistic dantti will be able to get a production quality zypp backend done. he is too distant from opensuse 20:28:59 rabauke: "the opensuse zypp devs" is about one guy from what I gather on the zypp-devel list 20:29:11 rabauke: and that guy is paid from suse to do maintenance work 20:29:33 cb400f: the png is broken.. for the one in packman but the idea is like this cvlc -I dummy v4l2:// --video-filter scene -V dummy --scene-ratio 5 --scene-format jpg --scene-prefix img --scene-path $HOME --no-scene-replace --run-time 10 vlc://quit 20:29:43 coolo: and opensuse is the test rabbit for suse, which makes it only fair to pay at least some of its contributors 20:29:57 and its still a shame 20:30:04 alin: will that be in guide ;-) 20:30:25 shumski: I know more tricks... 20:30:26 I wonder which update applet Gnome is using 20:30:39 something integrated into gnome afaikl 20:30:50 FYI, I need to leave, but scribus 1.4.2 is very very soon :-) 20:30:52 packagekit based surely? 20:30:55 but it should rely on packagekit as well 20:30:58 plinnell: Ok. Thanks 20:31:00 out before freeze methinks 20:31:21 and knowing gnome.. that means it prolly requires pk 0.8 too 20:31:30 :-) 20:31:51 but I guess that their client currently works ok with the current pk 20:31:55 * plinnell wishes we could have kde for SLES 12 20:33:06 o/ 20:33:14 Ok. Let's agree the following. I will check with Gnome what their plans are and if they have any issues. I will also check the bug reports on what we have open for Apper to see if this is still valid or not. 20:33:42 tittiatcoke: ok... ifyou want me I can test... 20:33:44 don't take their word for it if they say "no issues" 20:33:50 cb400f: :-) 20:34:00 ok guys, I need to sign off 20:34:01 they always claim it works... no matter how many bugs are in the zypp backend 20:34:07 I'll check later the rest of the meeting 20:34:15 einar77: Ok. Thanks 20:34:44 #action tittiatcoke check the updater/packagekit situation in Gnome and validate open bugreports for Apper. 20:34:57 krop: Are you there ? 20:35:11 partially yes 20:35:17 Ok. It's your topic :-) 20:35:20 #topic Remove old repositories (krop) concerned: KR46, KR47(?), K:U:P/(KR47,KR48,KR49_12.1) 20:35:53 I would like to add a discussion about KUA for 11.4 for this topic 20:35:54 +1 20:35:55 So, we have 1/many obsolete repositories, 2/ many rebuilds when updating any package in KUP 20:36:19 +1 for dropping the repos that is 20:36:26 are there any download stats available? sounds like a niche market honestly 20:36:28 that takes a lot of space and a lot of build power 20:37:23 I can understand KR46 and KR47, but why would you drop KUP for KR49/12.1 ? 20:37:36 remur_030: niche market for whom? I donot think one would like to consider niche the part that never updates 20:37:43 KR46 is built for 11.4, KR47 is built for 11.4 & 12.1, and KUP builds for many repos 20:37:49 one issue I could see though is that those still using these repos will not get any updates not even officials anymore because apper does not skip on error but stops to check. so people will have to know that they have to remove a repo. 20:38:25 was a typo, we have KR47/12.1, KR48/12.1, I'm not sure people using these KDE flavours are interested in unstable packages 20:38:27 if they use KUP they are no longer civilians 20:38:36 i would axe all 11.4 repos 20:38:40 alin: I was more thinking about KUP, who uses this with outdated opensuse? 20:38:43 kr46 does not make sense on any supported distro (except possibly evergreen) 20:38:45 Playground should certainly go. KR46 as well. the others somebody might call for evergreen, but then they should have taken them over a long time ago. 20:38:56 alin: the other ones shouldn't rebuilt that often no? 20:39:49 can we maybe split that up into KR and KUP? Because I think KUP might be way more expensive for the OBS infrastructure 20:39:53 it is 2y old software... why should we bother? 20:40:14 KR doesn't really need any rebuilds no? so it's just hosting old stuff 20:40:17 krop: thougght kup is build only for stable + factory... 20:40:57 we had this discussion some time ago... somebody wants crazy things on stable -1 one... then it is his problem 20:41:26 for KUP, in order to limit the used space and power, I'd like to limit the build to O:F+ current opensuse version 20:41:47 krop: +whatever it needs to go on 20:41:52 including relevant KR4x for current opensuse version? 20:42:07 yes 20:42:14 and KDF+current opensuse 20:42:17 why not KDF? 20:42:32 actually I guess somebody running KUP will be using kdf not kr? 20:42:34 https://build.opensuse.org/project/repositories?project=KDE%3AUnstable%3APlayground that's the current repos 20:43:02 remur_030: you might have some guy who just wants the amarok beta or calligra beta on an otherwise fairly stable system 20:43:24 or testing kscreen .. or sumfink 20:43:37 the KR47,48 and 12.1 repos should be wiped imo 20:43:52 cb400f: might as well have sombody who wants to do this on his opensuse - 1 release :-/ 20:44:35 krop: we keep the first 5? and the supported kde? 20:44:45 sure.. but if we need to limit build power wastage I think krop's suggestion is fair 20:45:17 also it matches the KDF policy more or less 20:45:36 which also isn't built for stable -1 anymore 20:45:42 hmm, right 20:46:24 ok.. so we shall vote on this? kup remains with factory plus stable 20:46:29 ? 20:46:53 tittiatcoke: wake up 20:46:54 stable = current release? 20:46:55 stable as in current opensuse plus current stable kr? 20:47:00 remur_030: yes 20:47:04 alin: I am here :-) 20:47:11 then +1 20:47:23 tittiatcoke: so we give to krop the knife to prune the kup? 20:47:24 so, as a more generic rule: (Factory + current opensuse version)*KDE flavors (KRxy, KDF, KUSC) 20:47:33 yup 20:47:40 krop: +1 20:47:52 #agreed KUP to be build for (Factory + current opensuse version)*KDE flavors (KRxy, KDF, KUSC) 20:48:01 #agreed to delete KR46 and KR47 20:48:19 tittiatcoke: and 48 20:48:30 #agreed to delete KR48 20:48:37 tittiatcoke: as 4.8 would come via 12.2 20:48:40 perfect 20:48:56 hm, what about 12.1 users still running 4.8? 12.1 is still supported 20:49:08 and again, not much build power required for non touched kr 20:49:13 yeah, better keep kr48 for 12.1 only 20:49:23 remur_030: is supported but not in kup 20:49:27 one may wonder why we still have KDE:Qt45/46/47 but we're missing Dirk for this topic 20:49:54 alin: err I thought this was about KR repos in general, not the KUP ones 20:49:54 :-) KDE:Qtxx is dirk's territory 20:49:55 krop: let us add that for next time.. 20:50:04 tittiatcoke: or send him an email 20:50:15 as I do not remember seeing him lately 20:50:32 alin: indeed. 20:50:33 dantti_laptop: was here... 20:50:48 guys, can we finish this. I really have to run :-) 20:50:56 ? 20:50:57 tittiatcoke: yes 20:51:03 next point... 20:51:14 #topic Misc, Q&A 20:51:21 Any other topics or questions ? 20:51:22 dantti_laptop: something related about apper 20:51:31 tittiatcoke: I want to add simon 20:51:46 alin: I am fine to add simon in KDF, but you heard coolo :-) 20:51:56 tittiatcoke: anyone interested in? http://simon-listens.blogspot.co.at/2012/12/simon-040.html 20:52:05 alin: ok, I can't find anything usefull on backlog, am I still useful? 20:52:25 danish team put in a huge effort over christmas to translate the thing :-) 20:52:37 cb400f: cool... 20:52:39 dantti_laptop: Not for the meeting :-) 20:52:52 and people tend to complain about kde accessibility.. so it'd be cool to have it I think 20:52:53 ok :) 20:52:54 alin: I would say push it to KDF and then we will see :-) 20:53:29 tittiatcoke: I will push it to extra and then from there we see next week 20:53:44 #action alin to push simon to KDE:Extra 20:53:48 anything else ? 20:54:19 tittiatcoke: no 20:54:21 not from me 20:54:29 not from me 20:54:35 no 20:54:45 Oki :-) Apologies for rushing the ending :-) 20:54:50 thanks for hosting! 20:54:51 I have a bit 20:54:58 cb400f: go :-) 20:55:06 * wstephenson blames jospoortvliet for turning on the work tractor beam 20:55:08 any opinions if kua/11.4 should be dropped? 20:55:18 but we now have a nice article about chromebooks published: https://news.opensuse.org/2013/01/08/opening-the-can-initial-support-for-opensuse-on-the-arm-chromebook/#comments 20:55:21 drop 20:55:27 +1 wstephenson 20:55:31 cb400f: I would drop it 20:55:34 I tend to think it should go.. but I feel a bit bad for the evergreeners 20:55:41 just tuned it a bit and gave it the spotlight on the front page as well as on G+, facebook and twitter :D 20:55:59 cb400f: then ask them whether they are going to maintain it. if not, drop 20:56:34 * jospoortvliet goes again, sorry to interrupt the meeting. Hugs for all :D 20:56:40 #action cb400f Check with the evergreen maintainers if they are willing to maintain KUA for 11.4. If not, then drop the repo 20:56:43 ok, I think I'll just clean it.. :-) think I know the answer to the question 20:56:49 :-) 20:57:16 Ok. guys. Next meeting in two weeks. (22 January same time, same channel) :-) 20:57:25 #endmeeting