15:00:32 #startmeeting kde-sig 15:00:32 Meeting started Tue Mar 19 15:00:32 2013 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:32 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:36 #meetingname kde-sig 15:00:36 The meeting name has been set to 'kde-sig' 15:00:40 #topic roll call 15:00:47 hi all, who's present today? 15:00:53 present 15:00:55 present 15:00:59 hi 15:01:12 present 15:01:33 lukas is sick 15:01:36 Present. 15:02:05 * jreznik is here 15:02:15 #info rdieter jgrulich dvratil_ than Kevin_Kofler jreznik present 15:02:17 ltinkl is in a car service 15:02:27 #info ltinkl sends regards 15:02:38 jgrulich: so in reality, his car is sick :) 15:02:39 #chair jgrulich dvratil_ than Kevin_Kofler jreznik 15:02:39 Current chairs: Kevin_Kofler dvratil_ jgrulich jreznik rdieter than 15:02:57 #topic agenda 15:03:10 agenda, Kevin_Kofler already suggested f17/kde-4.10.1 topic 15:03:25 at the end, can discuss test day results 15:03:59 anything else? 15:04:04 multilib issue 15:04:13 in index.cache.bz 15:04:53 i saw some kde apps which have this problem 15:05:18 ok 15:05:26 let's get started... 15:05:41 #topic kde-4.10.1 for f17, ready for stable updates? 15:06:00 any remaining issues or reservations to pushing kde-4.10.1 stable for f17? 15:06:04 So, the F18 version is already stable, the F17 one has the required karma too now, so IMHO, ship it! 15:06:06 * rdieter has none 15:06:37 i feel better giving it at least a few more days (than f18) 15:07:07 It's had those now. :-) 15:07:37 plasmate is not yet in f17 -> no plasmoidviewer available 15:07:52 It's in testing, same as on F18. 15:08:00 or is it part of the update? 15:08:04 If you want us to push it to stable, karma it up to at least 1. :-) 15:08:37 rnovacek: submitted separately, in updates-testing 15:09:06 it used to be in -workspace, so it's regression if it gets pushed separately 15:09:12 we decided a week (or 2) ago not to consider plasmate a blocker 15:09:27 someone asked for it today in #fedora-kde 15:09:47 (since it's a developer tool, developers can just as easily fetch it from kde repos or updates-testing) 15:09:53 rdieter: ok, sorry, didn't know that 15:10:00 but karma/testing can indeed speed it's move to stable updates too 15:11:04 any other comments wrt f17 (good or bad)? 15:11:29 * rdieter readies pushing the big red button 15:12:28 rdieter: i have updated to 4.10.1 on my test machine without any issue. 15:13:11 is anyone really using it on f17? I still think kde repo is better for it for people who really wants f17 with 4.10 but seems I'm in minority 15:13:26 jreznik: i've been using it awhile, but I don't count 15:13:30 jreznik: At this point the decision has been made. 15:13:36 we've gotten some feedback on kde list too 15:13:41 It's only a matter of when now. 15:13:55 Kevin_Kofler: I know decision was made, I'm just curious how confident we are 15:13:57 We aren't going to let it linger in testing forever. 15:14:07 rdieter: well, I 100% trust you - so you count :) 15:14:20 just noticed, according to bodhi, the f17 update has only been public (pushed to updates-testing), since 2013-03-12 08:26:5 15:14:27 Kevin_Kofler: for me it's bad it even hit testing :) 15:14:42 barely just a week still. 15:15:16 It's been in kde-testing for longer than that. 15:15:28 And it has the required karma. 15:16:02 yes, I know, just mentioning it for full disclosure. i personally thought it had been longer 15:16:32 not that I expect any particular f17-specific bugs to jump out and surprise us at this point 15:17:14 ok, I'll queue it in ~15-20 minutes when I get a chance 15:17:16 moving on... 15:17:29 #topic multilib index.cache issues 15:17:31 ok, do ti 15:17:46 than: your topic 15:19:17 i saw the multilib issue in some kde packages 15:19:24 kate, kdf, kgamma, kwallet, audiocd-kio 15:19:40 it's in index.cache.bz2 15:20:10 * rdieter thought all those core kde packages were *supposed* to be fixed now 15:20:27 :( 15:20:37 imo we can make the html doc as noarch package 15:21:02 right, i'd suggest in general a best practice is to simply avoid possible problems by making some noarch common/doc subpkg 15:21:13 or use the workaround with sed what we used in kdelibs 15:21:22 actually, that won't "fix" it... won't koji fail the build? 15:21:27 Well, won't the build fail if you do a noarch subpackage and it's different between arches? 15:21:34 Right. 15:21:45 though I'd consider a koji failure highlighting the problem better than surprises later 15:21:48 I think we need to use the sed hack unless/until upstream fixes it. 15:22:37 so, I'd suggest filing bugs to document problems, ping/cc tosky 15:22:44 Kevin_Kofler: imo make noarch package is cleaner 15:22:45 and apply workarounds in the meantime 15:24:47 than: We need the sed hack even if we do the noarch subpackage, see above. 15:26:26 Kevin_Kofler: why do we need the sed hack? it's noarch package 15:26:27 yeah, we'll hit that the hard way eventually. :) 15:26:43 than: koji enforces that noarch content be identical across different archs 15:26:56 and fails builds if not 15:26:57 rdieter: ah ok 15:27:53 i will take care of those packages 15:28:33 * than thinks there're still a lot of kde packages which have this issue 15:28:47 * than is still investigating and fixing 15:29:38 it's all from my side 15:29:46 next topic please 15:31:21 Is there a next topic? 15:31:38 #topic kde test day results 15:32:20 just wanted to mention we got some (not a lot) test day results to triage. 15:32:42 on the the test day wiki page, and in the form of newly filed bugs 15:34:14 that's all. 15:34:49 #topic open discussion 15:34:54 anything else for today? 15:35:37 Not from me. 15:38:33 (I got disconnected for about 2 minutes there, did I miss anything?) 15:38:50 else, let's end the meeting 15:38:50 No. 15:38:55 k, thanks everyone! 15:38:57 #endmeeting