15:08:11 #startmeeting kde-sig 15:08:11 Meeting started Tue Apr 23 15:08:11 2013 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:08:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:08:14 #meetingname kde-sig 15:08:14 The meeting name has been set to 'kde-sig' 15:08:18 #topic roll call 15:08:29 hello all, who's around for a friendly kde-sig meeting today? 15:08:43 hello :) 15:09:14 than, ltinkl, jreznik, Kevin_Kofler, dvratil , kde*foo : ping 15:09:17 Present. 15:09:24 present 15:10:08 * jreznik is here, has to leave earlier today 15:11:03 #info rdieter jgrulich Kevin_Kofler than jreznik present 15:11:08 #chair jgrulich Kevin_Kofler than jreznik 15:11:08 Current chairs: Kevin_Kofler jgrulich jreznik rdieter than 15:11:17 #topic agenda 15:11:20 * ltinkl present too 15:11:27 #info ltinkl present too 15:11:29 #chair ltinkl 15:11:29 Current chairs: Kevin_Kofler jgrulich jreznik ltinkl rdieter than 15:12:03 what to discuss today? personally, would like to hear a juicy report on the solid sprint :) 15:13:01 * rdieter will give status update on kde-redhat repo outage/downtime 15:13:45 anything else? 15:14:22 I can't think of anything else to be honest. 15:14:31 ok, moving ... 15:14:37 #topic kde-redhat repo/outage 15:14:45 just quick update. 15:15:05 discoverred on my way home from the office yesterday that the primary host for kde-redhat repos went offline 15:15:32 working from home today, so I likely won't get a chance to address this until first thing tomorrow morning 15:16:04 plan is to retire the old box for good this time, finally move things to a virtualized (redundant) host 15:16:26 the one currently running @ http://kdeforge2.unl.edu/kde-redhat/ 15:16:44 any questions/comments? 15:17:53 * rdieter hrms, may consider putting new primary host @ repos.fedorapeople.org too 15:18:36 (to serve mirrorlists only) 15:18:47 anyway, moving on... 15:18:56 #topic solid sprint report 15:19:08 looks like jgrulich, ltinkl, dvratil and friends are up to fun 15:19:14 * rdieter saw http://ltinkl.blogspot.com/2013/04/solid-developers-sprint-take-2.html 15:19:24 anything you guys would like to add ? 15:19:25 ltinkl, jgrulich: could you please give some update about solid sprint? 15:19:47 yeah :) was a lot of fun, the most important stuff is written in that blogpost 15:20:09 and at least one blog post will be about plasma-nm :) 15:20:17 the juicy bits... Alex managed to break the git repo twice in 10 minutes, Saturday night at 1 am :D 15:20:37 yay alex. woot 15:21:20 Alex pushed kde-runtime master into 4.10 branch 15:21:37 he basically screwed the kde-workspace 4.10 branch, we were quite lucky to have caught one sysadmin still awake at that time :) 15:21:49 ye and then repeated it 10 minutes later 15:22:04 in a more ellaborate (and non reversible) way 15:22:44 impressive. he should win a prize or something 15:23:50 ltinkl: thanks for organizing it. Looks like it was very productive 15:24:21 rdieter: it definitely was, we set a list of goals and topics to work on in the upcoming months 15:24:28 http://community.kde.org/Solid/Meetings/Forge2 15:26:02 * rdieter has to take another phone call, tag someone to continue leading meeting for next 10-15 minutes? 15:30:18 Well, for now we can continue talking about Solid if there's more to say about it. 15:31:00 I'll take the lead of the meeting. 15:33:18 OK, I guess that's all about Solid… 15:33:23 #topic Open Discussion 15:33:26 Anything else? 15:33:43 is there any blocker bugs which need to be fixed? 15:34:13 Uhm… For Alpha I don't think so. 15:34:42 We will need to get the "Apper checks for updates even on the live image" bug fixed for Beta though. 15:35:13 The service backing the plasmoid (I think it's a kded4 service) really needs to honor the "Never check for updates" setting. 15:35:43 On the live image, it's a Beta blocker. 15:35:57 Otherwise, the lack of respect for user settings is just an annoyance. 15:36:47 i suppose we may have to simply disable the apper systray plasmoid on the live image 15:37:25 (running it there at all makes little sense) 15:37:27 updates notification appears even if plasmoid disabled in tray 15:37:27 imo it doesn't make sense to enable apper on livecd 15:37:28 I don't think disabling the plasmoid alone is going to be sufficient. 15:37:34 nucleo: Yeah right. 15:37:40 The plasmoid is just the UI. 15:37:44 nucleo: oh, really? ugh 15:37:49 It's the backing service which is the problem. 15:38:07 I *assumed* it was the plasmoid forcing a refresh of the plasma dataengine causing the problem 15:38:18 rdieter: yes, I disabled it and restarted KDE, then notification appeared 15:38:50 rdieter: yup, need to fix it in the kded module 15:39:13 the plasmoid just appears when the kded module signals there are updates 15:39:23 * rdieter can't find the bug 15:39:28 not against apper ? 15:39:42 .bug 948099 15:39:43 maye 15:39:44 rdieter: Bug 948099 Apper ignores "never check for updates" option (also on the live image) - https://bugzilla.redhat.com/show_bug.cgi?id=948099 15:40:22 Yes, that one. 15:40:41 ok, any objections adding to our F19Blocker-kde tracker ? 15:41:18 No. 15:41:28 Except, which one. This one or the older: 15:41:29 go ahead 15:41:45 .bug 928296 15:41:48 Kevin_Kofler: Bug 928296 Updates are checked in Fedora 19 Alpha TC2 KDE Live - https://bugzilla.redhat.com/show_bug.cgi?id=928296 15:42:00 ? (They should be duplicates of each other, really.) 15:42:00 bigger hammer would be to disable the kded apper service too, on the live image 15:42:21 Kevin_Kofler: probably, +1 15:42:36 I'll dup the older to the new one 15:44:04 We could use such sledgehammer approaches, but I'd really like to see a real fix, because not honoring that setting also sucks for user experience on the installed system! 15:44:42 yes, this is not only about live image 15:45:00 Dang, in that case I should have just set the old bug to depend on the new one 15:45:01 Plus, it's easier to enable the checks on the live image when wanted (e.g. live USB with overlay) if you can enable them from the Apper UI rather than having to enable the service in the System Settings kded4 service configuration. 15:45:03 oh well 15:45:47 no one will disagree a proper fix is preferable 15:45:59 (OTOH, disabling the service does reduce resource usage. The usual tradeoff…) 15:46:14 but if it's "include hack to fix blocker" or "wait indefinitely for proper fix", I know which I'd choose 15:46:30 disabling apper service in systemsettings don't changes anything 15:46:54 nucleo: it has to, nothing else can touch packagekit otherwise 15:47:25 otoh, if something else is indeed refreshing packagekit behind our backs, then it's not our bug 15:47:31 nucleo: disable and restart kded4 15:47:41 just disabling it won't change anything 15:48:16 I only mwant to say that apper icon left in tray if service disabled 15:48:34 nucleo: , implementing this right would mean disabling both 15:48:46 well, this = evil hack solution 15:49:57 I can spend some time on "the evil hack(tm)" today, unless someone's willing to look into fixing properly in the meantime? 15:50:24 probably ought to ping dannti too 15:50:46 yup 15:52:51 * rdieter pinged in upstream bug, https://bugs.kde.org/show_bug.cgi?id=317838 15:53:48 1/2 evil method could be to find the code responsible for for refreshing packagekit, and wrap in pseudo-code like: if (update_interval != never ) ... 15:56:31 anyway, hour's almost up, any last thoughts before closing meeting? 15:58:05 alright, thanks everyone! 15:58:07 #endmeeting