[20:02:21] !herd kde [20:02:22] (kde) abcd, ago, alexxy, creffett, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 [20:02:26] 1. roll call, first attempt [20:02:46] -*- creffett here [20:04:08] --> tampakrap (~tampakrap@gentoo/developer/tampakrap) hat #gentoo-meetings betreten [20:06:30] well, that was successful. [20:06:36] will try again at :15 [20:06:49] hmm [20:07:11] hmm indeed [20:09:11] hmm [20:09:14] -*- dilfridge here [20:09:44] you guys are falling apart :p [20:10:03] our leader is MIA and I requested the meeting be moved up a week [20:10:17] and nobody being here for meetings is pretty standard anyway [20:10:23] :p [20:10:28] looking at the bug numbers it's not so bad [20:10:43] I'm surprised that I managed to get my time conversions right this time :P [20:10:49] hehe [20:10:52] I didn't [20:10:53] we need to decide on a new time I think :p [20:10:59] yeah, we do [20:11:15] preferably not decided only by the people who can make the meetings :P [20:11:17] sorry guys, but I need to leave. Whatever you decide, I'm sure will be the best choice :) [20:11:28] oh dear :D [20:11:38] I'll vote on your behalf ;) [20:11:48] hehe, go ahead [20:11:54] -*- creffett decides to make kensington team leader and start a massive project to switch the backend of KDE to GTK+ [20:12:02] dastergon: congratulations!! [20:12:04] kensington: just let amarok hidden in a corner and we'll be fine ;) [20:12:41] well, either way I'll be emailing kde@ with a request for opinions [20:12:53] thank you dilfridge :) [20:13:42] mmmm, KDE/GTK+, nasty [20:14:05] this is what happens when I'm in charge [20:15:36] anyway, hopeful attempt at roll call, failing this we try again next week [20:15:41] !herd kde [20:15:42] (kde) abcd, ago, alexxy, creffett, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 [20:15:57] ^ guest starring dastergon [20:15:57] -*- kensington (maybe) [20:16:03] -*- dilfridge [20:16:31] -*- creffett here [20:18:16] ...sigh [20:18:26] okay, meeting pushed to next week, I guess [20:18:28] well [20:18:34] what's actually on the agenda? [20:18:44] or more precisely, [20:18:49] what is important / urgent? [20:18:53] -*- creffett checks [20:19:28] I had bug 430286 for a while but it disappeared mysteriously [20:19:31] dilfridge: https://bugs.gentoo.org/430286 ">=kde-base/konsole-4.9.0 freezes on double-click"; Gentoo Linux, KDE; UNCO; Martin.vGagern:kde [20:19:48] 3 potential blockers to stabilizing 4.9, whether to stabilize 4.9.3, when to move cmake to the tree, and what to do about the polkit-kde-kcmodules fiddling with stuff in /usr [20:19:53] I *think* after logging out and in, and it only happened during the in-place upgrade [20:19:54] (I note that while our herd member list is large, not too many seem to have much time at the moment, so I don't think we'll get too much improved turnout at a later date) [20:20:22] true [20:20:40] yes [20:20:45] I think we should move 4.9.3 to tree and stable it, too many fixes are waiting in stable [20:20:49] s/stable/~arch/ [20:20:53] so, we have three potential blockers to stabilizing 4.9: https://bugs.gentoo.org/show_bug.cgi?id=430286, https://bugs.gentoo.org/show_bug.cgi?id=434156, https://bugs.gentoo.org/show_bug.cgi?id=438274 [20:21:01] bug 434156 is hard to debug without help from upstream [20:21:04] https://bugs.gentoo.org/434156 "kde-base/kmail-4.9.1: Problems creating imap folder"; Gentoo Linux, KDE; CONF; dilfridge:kde [20:21:26] the last one is tracking upstream [20:21:27] and since upstream in this particular case usually does not care for gentoo... [20:22:08] I'd say these are not really blockers (the first one would be but I have not seen it for a while) [20:22:16] my thoughts are that the three aren't crucial enough to block stabilization, and the last one is upstreamed and we can backport a fix if/when it comes up [20:22:27] ack [20:22:49] mmhh where is ago? [20:23:04] :| [20:23:09] excellent question [20:23:47] and then 4.9.3 will be our stable candidate [20:23:49] what is the sec bug that ago was talking about? [20:24:10] not sure [20:24:18] !bug #438452 [20:24:20] kensington: https://bugs.gentoo.org/438452 "kde-base/konqueror : Multiple vulnerabilities (CVE-2012-{4512,4513,4514,4515})"; Gentoo Security, Vulnerabilities; IN_P; ago:security [20:25:02] we did some investigating and all the fixes are in kdelibs [20:25:12] ok [20:25:21] in various versions, the last fixed in 4.9.3 [20:25:24] so either fast-stable 493 or backport [20:25:36] fast-stable 493 [20:25:47] yeah why not [20:26:03] there's quite a few bugs cropping back up that are fixed in ~arch, so++ [20:26:18] all right, that's settled [20:26:22] when do we move 493 to the tree? [20:26:23] eg. rich0 ran into stable build failure today [20:26:41] searching for the cve numbers on bugs.kde.org gives no results :( [20:26:52] creffett: now? [20:27:03] dilfridge: fine with me [20:27:04] with stabilization as soon as ago can do it? [20:27:08] mhm [20:27:20] ++ [20:27:46] I'll move it into the tree later today [20:27:50] cool [20:28:09] there's a list of misc apps in the overlay due for stabilisation too [20:28:18] I'll be gone soon, need to be back at work 8 sharp... [20:28:19] is there anything special to that beyond "copy everything into kde-base/"? I haven't actually done a move-kde-to-tree before :) [20:28:30] okay, will discuss that later [20:28:45] creffett: the bump script can do it [20:28:49] okay [20:29:20] but in the past I've also done it with find and cp [20:29:36] last two: cmake I say we bump and wait a week or so before moving to tree, and the polkit-kde-kcmodules let's throw a CONFIG_PROTECT in for now and we'll look at symlinking in KDE 4.10 [20:29:41] the only difficulty is not missing any patches [20:30:44] cmake: ack [20:31:10] polkit-... not sure what you want to achieve with CONFIG_PROTECT [20:31:40] but all changes only become critical with 4.10 I guess, we probably dont want to make big adaptions within 4.9 series [20:32:08] protecting /usr/share/polkit-1/actions because right now KDE modifies that and so it can be overwritten on upgrade [20:32:15] ah ok [20:32:15] yes [20:32:31] CONFIG_PROTECT for now and moving it maybe with 4.10 [20:32:48] ++ [20:32:52] mhm, but the exact implementation can wait until we start getting pre-releases of 4.10\ [20:32:56] and that's all from me [20:32:57] yes [20:33:21] everything else is good for next meeting I think [20:33:35] mhm, will go push them onto the agenda for next month [20:33:39] thanks all [20:33:57] thank you :) [20:35:19] creffett: don't worry, you are doing great [20:35:43] I'm not even supposed to be running these things, johu is [20:36:04] not really [20:36:11] team leader != meeting chairman [20:36:15] he's the fearless leader