From 6d43693606f4330227e38716241bd62253adcb3b Mon Sep 17 00:00:00 2001 From: Johannes Huber Date: Wed, 8 Apr 2015 18:23:03 +0200 Subject: Shorten logs and summaries --- meeting-logs/20071013-summary.txt | 72 + meeting-logs/20071013.txt | 338 ++++ meeting-logs/20080306-summary.txt | 80 + meeting-logs/20080306.txt | 518 ++++++ meeting-logs/20081204-summary.txt | 31 + meeting-logs/20081204.txt | 641 +++++++ meeting-logs/20090108-summary.txt | 27 + meeting-logs/20090108.txt | 666 ++++++++ meeting-logs/20090212-summary.txt | 34 + meeting-logs/20090212.txt | 761 +++++++++ meeting-logs/20090305-summary.txt | 40 + meeting-logs/20090305.txt | 769 +++++++++ meeting-logs/20090401-summary.txt | 74 + meeting-logs/20090401.txt | 601 +++++++ meeting-logs/20090521-summary.txt | 182 ++ meeting-logs/20090521.txt | 1769 ++++++++++++++++++++ meeting-logs/20090618-summary.txt | 51 + meeting-logs/20090618.txt | 1064 ++++++++++++ meeting-logs/20090820-summary.txt | 41 + meeting-logs/20090820.txt | 545 ++++++ meeting-logs/20090917.txt | 572 +++++++ meeting-logs/20090924.txt | 230 +++ meeting-logs/20091119.txt | 959 +++++++++++ meeting-logs/20100225-summary.txt | 66 + meeting-logs/20100225.txt | 612 +++++++ meeting-logs/20100318-summary.txt | 38 + meeting-logs/20100318.txt | 206 +++ meeting-logs/20100604-summary.txt | 21 + meeting-logs/20100604.txt | 282 ++++ meeting-logs/20100902-summary.txt | 37 + meeting-logs/20100902.txt | 234 +++ meeting-logs/20110210-summary.txt | 107 ++ meeting-logs/20110210.txt | 566 +++++++ meeting-logs/20110331.txt | 370 ++++ meeting-logs/20110602-summary.txt | 44 + meeting-logs/20110602.txt | 553 ++++++ meeting-logs/20110831.txt | 479 ++++++ meeting-logs/20120116-summary.txt | 70 + meeting-logs/20120116.txt | 630 +++++++ meeting-logs/20120322-summary.txt | 76 + meeting-logs/20120322.txt | 282 ++++ meeting-logs/20120419-summary.txt | 41 + meeting-logs/20120419.txt | 169 ++ meeting-logs/20120517-summary.txt | 73 + meeting-logs/20120517.txt | 324 ++++ meeting-logs/20120621-summary.txt | 39 + meeting-logs/20120621.txt | 143 ++ meeting-logs/20120816-summary.txt | 95 ++ meeting-logs/20120816.txt | 539 ++++++ meeting-logs/20120927.txt | 260 +++ meeting-logs/20121108.txt | 119 ++ meeting-logs/20130117.txt | 212 +++ meeting-logs/20130321.txt | 368 ++++ meeting-logs/20130523.txt | 407 +++++ meeting-logs/20140329.txt | 456 +++++ meeting-logs/20140810.txt | 389 +++++ meeting-logs/kde-herd-meeting-log-20071013.txt | 338 ---- meeting-logs/kde-herd-meeting-log-20080306.txt | 518 ------ meeting-logs/kde-herd-meeting-log-20081204.txt | 641 ------- meeting-logs/kde-herd-meeting-log-20090108.txt | 666 -------- meeting-logs/kde-herd-meeting-log-20090305.txt | 769 --------- meeting-logs/kde-herd-meeting-summary-20071013.txt | 72 - meeting-logs/kde-herd-meeting-summary-20080306.txt | 80 - meeting-logs/kde-herd-meeting-summary-20081204.txt | 31 - meeting-logs/kde-herd-meeting-summary-20090108.txt | 27 - meeting-logs/kde-herd-meeting-summary-20090305.txt | 40 - meeting-logs/kde-project-meeting-log-20090212.txt | 761 --------- meeting-logs/kde-project-meeting-log-20090401.txt | 601 ------- meeting-logs/kde-project-meeting-log-20090521.txt | 1769 -------------------- meeting-logs/kde-project-meeting-log-20090618.txt | 1064 ------------ meeting-logs/kde-project-meeting-log-20090820.txt | 545 ------ meeting-logs/kde-project-meeting-log-20090917.txt | 572 ------- meeting-logs/kde-project-meeting-log-20090924.txt | 230 --- meeting-logs/kde-project-meeting-log-20100225.txt | 612 ------- meeting-logs/kde-project-meeting-log-20100318.txt | 206 --- meeting-logs/kde-project-meeting-log-20100604.txt | 282 ---- meeting-logs/kde-project-meeting-log-20100902.txt | 234 --- meeting-logs/kde-project-meeting-log-20110210.txt | 566 ------- meeting-logs/kde-project-meeting-log-20110331.txt | 370 ---- meeting-logs/kde-project-meeting-log-20110602.txt | 553 ------ meeting-logs/kde-project-meeting-log-20110831.txt | 479 ------ meeting-logs/kde-project-meeting-log-20120116.txt | 630 ------- meeting-logs/kde-project-meeting-log-20120322.txt | 282 ---- meeting-logs/kde-project-meeting-log-20120419.txt | 169 -- meeting-logs/kde-project-meeting-log-20120517.txt | 324 ---- meeting-logs/kde-project-meeting-log-20120621.txt | 143 -- meeting-logs/kde-project-meeting-log-20120816.txt | 539 ------ meeting-logs/kde-project-meeting-log-20120927.txt | 260 --- meeting-logs/kde-project-meeting-log-20121108.txt | 119 -- meeting-logs/kde-project-meeting-log-20130117.txt | 212 --- meeting-logs/kde-project-meeting-log-20130321.txt | 368 ---- meeting-logs/kde-project-meeting-log-20130523.txt | 407 ----- meeting-logs/kde-project-meeting-log-20140329.txt | 456 ----- meeting-logs/kde-project-meeting-log-20140810.txt | 389 ----- .../kde-project-meeting-summary-20090212.txt | 34 - .../kde-project-meeting-summary-20090401.txt | 74 - .../kde-project-meeting-summary-20090521.txt | 182 -- .../kde-project-meeting-summary-20090618.txt | 51 - .../kde-project-meeting-summary-20090820.txt | 41 - .../kde-project-meeting-summary-20100225.txt | 66 - .../kde-project-meeting-summary-20100318.txt | 38 - .../kde-project-meeting-summary-20100604.txt | 21 - .../kde-project-meeting-summary-20100902.txt | 37 - .../kde-project-meeting-summary-20110210.txt | 107 -- .../kde-project-meeting-summary-20110602.txt | 44 - .../kde-project-meeting-summary-20120116.txt | 70 - .../kde-project-meeting-summary-20120322.txt | 76 - .../kde-project-meeting-summary-20120419.txt | 41 - .../kde-project-meeting-summary-20120517.txt | 73 - .../kde-project-meeting-summary-20120621.txt | 39 - .../kde-project-meeting-summary-20120816.txt | 95 -- .../kde-qt-projects-meeting-log-20091119.txt | 959 ----------- 112 files changed, 18372 insertions(+), 18372 deletions(-) create mode 100644 meeting-logs/20071013-summary.txt create mode 100644 meeting-logs/20071013.txt create mode 100644 meeting-logs/20080306-summary.txt create mode 100644 meeting-logs/20080306.txt create mode 100644 meeting-logs/20081204-summary.txt create mode 100644 meeting-logs/20081204.txt create mode 100644 meeting-logs/20090108-summary.txt create mode 100644 meeting-logs/20090108.txt create mode 100644 meeting-logs/20090212-summary.txt create mode 100644 meeting-logs/20090212.txt create mode 100644 meeting-logs/20090305-summary.txt create mode 100644 meeting-logs/20090305.txt create mode 100644 meeting-logs/20090401-summary.txt create mode 100644 meeting-logs/20090401.txt create mode 100644 meeting-logs/20090521-summary.txt create mode 100644 meeting-logs/20090521.txt create mode 100644 meeting-logs/20090618-summary.txt create mode 100644 meeting-logs/20090618.txt create mode 100644 meeting-logs/20090820-summary.txt create mode 100644 meeting-logs/20090820.txt create mode 100644 meeting-logs/20090917.txt create mode 100644 meeting-logs/20090924.txt create mode 100644 meeting-logs/20091119.txt create mode 100644 meeting-logs/20100225-summary.txt create mode 100644 meeting-logs/20100225.txt create mode 100644 meeting-logs/20100318-summary.txt create mode 100644 meeting-logs/20100318.txt create mode 100644 meeting-logs/20100604-summary.txt create mode 100644 meeting-logs/20100604.txt create mode 100644 meeting-logs/20100902-summary.txt create mode 100644 meeting-logs/20100902.txt create mode 100644 meeting-logs/20110210-summary.txt create mode 100644 meeting-logs/20110210.txt create mode 100644 meeting-logs/20110331.txt create mode 100644 meeting-logs/20110602-summary.txt create mode 100644 meeting-logs/20110602.txt create mode 100644 meeting-logs/20110831.txt create mode 100644 meeting-logs/20120116-summary.txt create mode 100644 meeting-logs/20120116.txt create mode 100644 meeting-logs/20120322-summary.txt create mode 100644 meeting-logs/20120322.txt create mode 100644 meeting-logs/20120419-summary.txt create mode 100644 meeting-logs/20120419.txt create mode 100644 meeting-logs/20120517-summary.txt create mode 100644 meeting-logs/20120517.txt create mode 100644 meeting-logs/20120621-summary.txt create mode 100644 meeting-logs/20120621.txt create mode 100644 meeting-logs/20120816-summary.txt create mode 100644 meeting-logs/20120816.txt create mode 100644 meeting-logs/20120927.txt create mode 100644 meeting-logs/20121108.txt create mode 100644 meeting-logs/20130117.txt create mode 100644 meeting-logs/20130321.txt create mode 100644 meeting-logs/20130523.txt create mode 100644 meeting-logs/20140329.txt create mode 100644 meeting-logs/20140810.txt delete mode 100644 meeting-logs/kde-herd-meeting-log-20071013.txt delete mode 100644 meeting-logs/kde-herd-meeting-log-20080306.txt delete mode 100644 meeting-logs/kde-herd-meeting-log-20081204.txt delete mode 100644 meeting-logs/kde-herd-meeting-log-20090108.txt delete mode 100644 meeting-logs/kde-herd-meeting-log-20090305.txt delete mode 100644 meeting-logs/kde-herd-meeting-summary-20071013.txt delete mode 100644 meeting-logs/kde-herd-meeting-summary-20080306.txt delete mode 100644 meeting-logs/kde-herd-meeting-summary-20081204.txt delete mode 100644 meeting-logs/kde-herd-meeting-summary-20090108.txt delete mode 100644 meeting-logs/kde-herd-meeting-summary-20090305.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20090212.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20090401.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20090521.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20090618.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20090820.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20090917.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20090924.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20100225.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20100318.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20100604.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20100902.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20110210.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20110331.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20110602.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20110831.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20120116.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20120322.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20120419.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20120517.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20120621.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20120816.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20120927.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20121108.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20130117.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20130321.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20130523.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20140329.txt delete mode 100644 meeting-logs/kde-project-meeting-log-20140810.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20090212.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20090401.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20090521.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20090618.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20090820.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20100225.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20100318.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20100604.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20100902.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20110210.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20110602.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20120116.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20120322.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20120419.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20120517.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20120621.txt delete mode 100644 meeting-logs/kde-project-meeting-summary-20120816.txt delete mode 100644 meeting-logs/kde-qt-projects-meeting-log-20091119.txt diff --git a/meeting-logs/20071013-summary.txt b/meeting-logs/20071013-summary.txt new file mode 100644 index 0000000..567b83c --- /dev/null +++ b/meeting-logs/20071013-summary.txt @@ -0,0 +1,72 @@ +Summary of 13 October 2007 KDE herd meeting + +Active participants: cryos, genstef, jmbsvicetto*, keytoaster, philantrop, tgurr +In the channel: masterdriverz +Missing: caleb, centic, carlo, deathwing00, mattepiu, troll, vanquirius +* = invited guests + +- Project page: The update of the project page was approved by the participants. + +- Process improvement: This topic was postponed until the next meeting. + +- Misc: + +1. Bump to KDE 3.5.8: +The bump to KDE 3.5.8 is taking place in a git repository to allow for others +to take part, too, and avoid critisism like for the last bump. +This allows interested users to be "trained on the job" including the use of +our QA tools in a controlled environment outside the official tree. +Furthermore, the KDE 3.5.8 is not meant to be public until the release as per +upstream request. +Nevertheless, we will put the finished packages into the tree as package.masked +ASAP to allow arch teams and other devs to test. After that's done, a mail will +be sent to kde@g.o and the core mailinglist by Philantrop. + +2. KDE 3.5.8 in stable for 2007.1: +We will *try* to get KDE 3.5.8 into stable in time for 2007.1 but if we don't, +the world won't stop spinning. We will *not* inform the release guys about us +making it in time to not endanger their time frame needlessly if we don't make it. + +3. Changing to split ebuilds by default: +This suggestion was rejected by the participants for 3.5.x. We will make it the +default for KDE 4, though. + +4. State of KDE4 in the overlay(s): +KDE4 in the overlay is doing well. People are installing it, using it and are +reporting bugs. We currently have both monolithic and split ebuilds. +The participants decided 3:1 for keeping the monolithic ebuilds for KDE4. + +5. Miscellaneous +- A particpant asked for information on cmake ("crash course"). Any input is +appreciated. + +- cmake-utils.eclass. Several participants asked to get it into the tree. The final +remaining "showstopper" is the src_test function which is mostly a verbatim copy +of the one in ebuild.sh. We currently need it to determine if it's an in-source or +out-of-source build. Any input on this is appreciated. +Philantrop is going to re-submit the eclass to the dev mailinglist next week. + +- Arch Testers / Herd Testers. It was suggested to have Herd Testers for the KDE +herd as per GLEP 41. The suggestion was accepted by unanimous vote. +Philantrop will talk to hparker, the AT lead about it. +genstef and jmbsvicetto will prepare a draft for the project page and mail to +kde@g.o. + +- A participant suggested to move the scheduled meeting to the first Saturday of +each month. This was approved by unanimous vote. +keytoaster will update the project page accordingly. + +- Several participants asked about the Herd lead status as this is currently not +reflected on the project page. The participants asked keytoaster to add the +following to the project page directly above the "Members" box: +"We do not have a formal lead: Decisions can be made by every herd member but it usually is a good idea to ask Philantrop because he is around and knowledgable." + + +Tasks: +- Put the finished KDE 3.5.8 packages into the tree in p.mask by October, 14th 2007 +and inform kde@g.o and the core mailinglist about it. (Philantrop) +- cmake-utils.eclass should be re-submitted to the dev mailinglist by next week. (Philantrop) +- Contact the AT project on how to implement HTs for the KDE herd. (Philantrop) +- Prepare a draft for the project page about HTs. (genstef, jmbsvicetto) +- Update the project page with information about project lead and monthly meetings. (keytoaster) + diff --git a/meeting-logs/20071013.txt b/meeting-logs/20071013.txt new file mode 100644 index 0000000..720381e --- /dev/null +++ b/meeting-logs/20071013.txt @@ -0,0 +1,338 @@ +[Sa Okt 13 2007] [20:00:44] Join tgurr has joined this channel (n=tgurr@hbrn-590f7fff.pool.einsundeins.de). +[Sa Okt 13 2007] [20:00:54] !herd kde +[Sa Okt 13 2007] [20:00:57] Philantrop: (kde) caleb, carlo, centic, cryos, deathwing00, genstef, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, troll, vanquirius +[Sa Okt 13 2007] [20:01:00] here? +[Sa Okt 13 2007] [20:01:03] yes +[Sa Okt 13 2007] [20:01:19] Is it 18:00 hours already? +[Sa Okt 13 2007] [20:01:22] yes +[Sa Okt 13 2007] [20:01:24] cryos|laptop: Yes. :-) +[Sa Okt 13 2007] [20:01:33] At least in UTC. :-) +[Sa Okt 13 2007] [20:01:34] 20:00 in germany :) +[Sa Okt 13 2007] [20:01:40] 20:01! +[Sa Okt 13 2007] [20:01:44] I make it 14:01. +[Sa Okt 13 2007] [20:01:58] cryos|laptop: You're *way* behind! ;-) +[Sa Okt 13 2007] [20:02:03] hi all :) +[Sa Okt 13 2007] [20:03:12] Any objections against waiting for two or three more minutes? Deathwing00 told me he would be here. :-) +[Sa Okt 13 2007] [20:03:43] yes +[Sa Okt 13 2007] [20:03:49] * cryos|laptop murmurs about German efficiency :D +[Sa Okt 13 2007] [20:03:52] just start +[Sa Okt 13 2007] [20:05:17] Ok, let's go then. +[Sa Okt 13 2007] [20:05:47] 1. Update to the project page - are we happy with it now that it's been updated? Any additions, etc? +[Sa Okt 13 2007] [20:06:55] i'm happy with it :) +[Sa Okt 13 2007] [20:07:03] We, jmbsvicetto, keytoaster and myself have added what we thought was appropriate and it seems we all agree on it, atm. :-) +[Sa Okt 13 2007] [20:07:29] So that task from the last meeting is done. :-) +[Sa Okt 13 2007] [20:07:50] 2. Review of the project page is done, too, aunless anyone objects now. :-) +[Sa Okt 13 2007] [20:08:11] Nope. +[Sa Okt 13 2007] [20:08:34] 3. Process improvement - NeddySeagoon can't make it today, it seems. +[Sa Okt 13 2007] [20:08:48] It doesn't seem as if much can be done about it anymore anyway... +[Sa Okt 13 2007] [20:09:02] yup +[Sa Okt 13 2007] [20:09:19] 4. Miscellaneous - bump to KDE 3.5.8 +[Sa Okt 13 2007] [20:09:53] As I'Ve mailed to all of you, I've set up a git repository to collaborate on it. So far, jmbsvicetto, Ingmar^, tgurr and myself worked on it. +[Sa Okt 13 2007] [20:10:12] I've gotten exactly zero feedback to my mail about it. :-) +[Sa Okt 13 2007] [20:10:33] Are you manually bumping it? Sorry - I have been mostly offline these last few weeks/months. +[Sa Okt 13 2007] [20:10:49] i couldn't answer because i'm currently not at home and running windows :( +[Sa Okt 13 2007] [20:11:13] cryos|laptop: we've bumped the monolithic ebuilds manually, yes. The splits were initially done by the script and are now being combed through manually. +[Sa Okt 13 2007] [20:11:47] Philantrop: OK - sounds good. We always used to just mask and bump - why the git repo now if I may ask? +[Sa Okt 13 2007] [20:12:20] cryos|laptop: The last bump was critisized by many as rushed and bad. I wanted to avoid that this time. :) +[Sa Okt 13 2007] [20:12:26] Masking allowed us to get the arch teams on board and give them access to the tarballs before release via dev.gentoo.org and gentoo-core. +[Sa Okt 13 2007] [20:12:44] Then we could just unmask after the official release. +[Sa Okt 13 2007] [20:12:46] cryos|laptop: Furthermore, like this, interested users like Ingmar^ could help, too. +[Sa Okt 13 2007] [20:13:01] cryos|laptop: And, of course, we'll put them into the tree and package.mask soon. :-) +[Sa Okt 13 2007] [20:13:26] Philantrop: thanks for your mail, was very good :) +[Sa Okt 13 2007] [20:13:34] Philantrop: is there a release date scheduled yet? +[Sa Okt 13 2007] [20:13:41] Just seems to be making the process more hassle for arch teams to get involved with and interested users can send patches. I have been away so I am mainly asking. +[Sa Okt 13 2007] [20:13:50] genstef: Yes, it's to be released on the 16th. :-) +[Sa Okt 13 2007] [20:14:36] cryos|laptop: Well, yes, they could but why not combine both? We can still do the p.mask/tarball stuff (like tomorrow :-) ) *and* let others help directly. +[Sa Okt 13 2007] [20:14:46] I always worry about the trend towards overlays and separate repos making it harder to see and track stuff. +[Sa Okt 13 2007] [20:14:58] Just my opinion though - I know others like it. +[Sa Okt 13 2007] [20:15:24] cryos|laptop: My main point is: People like Ingmar^ are very, very good dev "material" and training them on the job helps, IMHO. +[Sa Okt 13 2007] [20:15:29] cryos|laptop: right, but this stuff isnot meant to be public by upstream +[Sa Okt 13 2007] [20:15:31] I have very little right to criticise anything due to my recent inactivity anyway. +[Sa Okt 13 2007] [20:16:01] cryos|laptop: No, that's wrong. You have *all* the right to critisize. I'd just like to *convince* you. :-) +[Sa Okt 13 2007] [20:16:15] * cryos|laptop will be quiet - I can see the reasoning. +[Sa Okt 13 2007] [20:16:45] well, but cryos is right. Last time the mail went to gentoo-core and every dev was able to test iirc +[Sa Okt 13 2007] [20:17:19] Anyway, I intend to put the stuff into the tree by tomorow (in p.mask) and inform -core. :-) +[Sa Okt 13 2007] [20:17:25] Any objections? +[Sa Okt 13 2007] [20:17:37] Philantrop: right, sounds cool! Enough time for the arch teams to test then :) +[Sa Okt 13 2007] [20:17:54] genstef: Yes, I hope so. +[Sa Okt 13 2007] [20:18:10] I don't think, though, we'll make it to 2007.1 or do you think we can/should? +[Sa Okt 13 2007] [20:18:25] Into stable, I mean. +[Sa Okt 13 2007] [20:18:34] When is the snapshot date? +[Sa Okt 13 2007] [20:18:37] * genstef does not care about releases +[Sa Okt 13 2007] [20:18:48] everyone runs emerge --sync anyways .. +[Sa Okt 13 2007] [20:18:58] xxxxxxxxxxxx - Initial snapshot +[Sa Okt 13 2007] [20:18:58] xxxxxxxxxxxx - Final snapshot +[Sa Okt 13 2007] [20:18:58] xxxxxxxxxxxx - Release +[Sa Okt 13 2007] [20:19:21] well, imo stable the earlier the better +[Sa Okt 13 2007] [20:19:25] cryos|laptop: ^^^ +[Sa Okt 13 2007] [20:19:34] It would be silly to try and make those dates, but I totally agree with genstef. +[Sa Okt 13 2007] [20:19:40] Stable the earlier the better. +[Sa Okt 13 2007] [20:20:03] but 19th will not happen I think +[Sa Okt 13 2007] [20:20:04] genstef: Yes, same here. I just wouldn't want to tell the release guys now we'll make it and possibly delay them if we don't. Opinions? +[Sa Okt 13 2007] [20:20:11] sorry, we are having dinner now, i'll read the conversation when i'm back +[Sa Okt 13 2007] [20:20:17] ok +[Sa Okt 13 2007] [20:20:36] Philantrop: so we will not make it +[Sa Okt 13 2007] [20:20:50] Philantrop: I wouldn't tell them we would make it - the 9th is too tight a schedule really. +[Sa Okt 13 2007] [20:21:25] In some ways it is a shame - would be good to have 3.5.8 GRPed. +[Sa Okt 13 2007] [20:21:33] Ok, let's say we can *try* but if we don't, the world will not stop spinning. I will *not* inform the release guys about us making it in time. +[Sa Okt 13 2007] [20:21:53] sounds good to me +[Sa Okt 13 2007] [20:21:58] I'm home +[Sa Okt 13 2007] [20:22:02] Sorry for the delay +[Sa Okt 13 2007] [20:22:06] jmbsvicetto: Welcome back! :-) +[Sa Okt 13 2007] [20:22:28] Ok, next point: "Changing to split ebuilds by default? That would mean going through all KDE ebuilds and changing the dependency order." +[Sa Okt 13 2007] [20:22:47] * genstef is against it. +[Sa Okt 13 2007] [20:22:56] * Philantrop is against it, too. +[Sa Okt 13 2007] [20:23:05] But if you must for 4.0, you can +[Sa Okt 13 2007] [20:23:27] I don't see the need but maybe there are other opinions? +[Sa Okt 13 2007] [20:23:34] I would rather see us do it for 4.0 and leave 3.5 well enough alone. +[Sa Okt 13 2007] [20:24:10] yeah, not for 3.x +[Sa Okt 13 2007] [20:24:12] The apache herd screw around lots inside minor releases and it hasn't made them very popular... +[Sa Okt 13 2007] [20:24:21] cryos|laptop: That sounds like a good idea. genstef, what do you think? +[Sa Okt 13 2007] [20:24:31] May be not lots, but when they have it has been painful at times. +[Sa Okt 13 2007] [20:24:33] and better kill monolithic stuff for 4.0 altogether +[Sa Okt 13 2007] [20:24:42] jakub: That's one more point later. :-) +[Sa Okt 13 2007] [20:24:43] jakub: sounds good +[Sa Okt 13 2007] [20:25:04] Philantrop: well, just a suggestion... :) +[Sa Okt 13 2007] [20:25:15] * cryos|laptop adds a here, here. +[Sa Okt 13 2007] [20:25:22] but yeah, messing with the (last?) 3.5.x release in this way will piss off users +[Sa Okt 13 2007] [20:25:36] So, we keep the current dep order for now but change it to split as default for >=4.0? +[Sa Okt 13 2007] [20:26:05] Philantrop: right, because split definitely has advantages, with many patches coming in +[Sa Okt 13 2007] [20:26:19] I would like to see us go to split by default +[Sa Okt 13 2007] [20:26:21] Philantrop: and 4.0 I expect to get many bugreports+patches early :) +[Sa Okt 13 2007] [20:26:23] genstef: Indeed. :-) +[Sa Okt 13 2007] [20:26:34] Philantrop: as said, you really want to keep monolithic stuff for 4.0? +[Sa Okt 13 2007] [20:26:41] sounds just like maintenance overhead to me +[Sa Okt 13 2007] [20:26:49] jakub: hey, leave the lead to Philantrop! +[Sa Okt 13 2007] [20:27:01] genstef: We already get them for the 4.0 overlays. Which leads us to the next point: KDE4 in the overlays. :-) +[Sa Okt 13 2007] [20:27:07] genstef: hey, gimme a beer! :P +[Sa Okt 13 2007] [20:27:17] I can live with split for >= 4.0, though +[Sa Okt 13 2007] [20:27:26] jmbsvicetto: Ok, that's decided then. :-) +[Sa Okt 13 2007] [20:27:30] * genstef paurs some beer into the wire to jakub's glass +[Sa Okt 13 2007] [20:27:44] anyway, the point - users are horrible confused by the blockers b/w monolithic/split, they've never grokked it +[Sa Okt 13 2007] [20:27:52] and really makes the eclasses/ebuilds a mess +[Sa Okt 13 2007] [20:28:08] KDE4 in the overlay is doing well. People are reporting bugs, installing it and using it. We currently have both monolithic and split ebuilds. +[Sa Okt 13 2007] [20:28:40] and you have a special project and channel for it :) +[Sa Okt 13 2007] [20:28:42] jakub: I got a block earlier because I tried to emerge kdesdk-3.5.8 and kdevelop-3.5 +[Sa Okt 13 2007] [20:28:46] Personally, I'd like to keep the monolithic ebuilds. We usually follow upstream and we give our users the freedom of choice. :-) +[Sa Okt 13 2007] [20:28:54] Philantrop: if you could make zmedico into sticking ranged deps into EAPI-1 by the KDE4 release time, that'd be awesome :P +[Sa Okt 13 2007] [20:28:58] jakub: We should really have a way to prevent that +[Sa Okt 13 2007] [20:29:23] jakub: We need ranges and sets +[Sa Okt 13 2007] [20:29:48] jmbsvicetto: well, for sets, you can workaround in a semi-reasonable way by the metabuilds... +[Sa Okt 13 2007] [20:29:52] jakub: That would allow us to drop the meta / meta use flags +[Sa Okt 13 2007] [20:29:54] for ranged deps, the hacks are insane :/ +[Sa Okt 13 2007] [20:30:23] Let's assume for now that we won't get ranged deps/real sets in time for 4.0. :-) +[Sa Okt 13 2007] [20:30:46] Philantrop: gah, torture Zac to do it! :> +[Sa Okt 13 2007] [20:31:25] hehe +[Sa Okt 13 2007] [20:31:27] jakub: :-)) I can't. I only torture soon-to-be devs. Not grizzled veterans. ;-) +[Sa Okt 13 2007] [20:31:34] jakub: I thought your preferred method involved beer ;) +[Sa Okt 13 2007] [20:31:51] jakub: even kegs of beer +[Sa Okt 13 2007] [20:32:01] jmbsvicetto: heh, if that fails, you need something more... effective :D +[Sa Okt 13 2007] [20:32:31] Guys, KDE4 and monolithic ebuilds - to keep them or not to keep them. That's the question. What's your answer? Mine is: Keep them. :-) +[Sa Okt 13 2007] [20:32:56] !herd kde +[Sa Okt 13 2007] [20:33:00] Philantrop: (kde) caleb, carlo, centic, cryos, deathwing00, genstef, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, troll, vanquirius +[Sa Okt 13 2007] [20:33:11] * genstef did not write those +[Sa Okt 13 2007] [20:33:23] so I just go with philantrop on that matter :) +[Sa Okt 13 2007] [20:33:38] Philantrop: As long as we can start the work for split from the meta, we might as well keep them +[Sa Okt 13 2007] [20:33:44] but the splits should be default by then +[Sa Okt 13 2007] [20:33:53] tgurr: Agreed. +[Sa Okt 13 2007] [20:33:53] tgurr++ +[Sa Okt 13 2007] [20:34:23] shrug; you're going to maintain the stuff :P +[Sa Okt 13 2007] [20:34:36] Three times "yes" so far: Philantrop, genstef, tgurr (splits will be default). cryos|laptop? +[Sa Okt 13 2007] [20:34:49] like: kdebase and kdebase-mon? ;) instead of kdebase-meta? +[Sa Okt 13 2007] [20:35:23] I would get rid, but don't object that much to keeping. +[Sa Okt 13 2007] [20:35:24] -mon? :) +[Sa Okt 13 2007] [20:35:25] kdebase is going to be split in two, right? +[Sa Okt 13 2007] [20:35:31] So I vote no. +[Sa Okt 13 2007] [20:35:37] kdebase and kdebase-plasma(?) +[Sa Okt 13 2007] [20:35:59] masterdriverz: Any thoughts? :) +[Sa Okt 13 2007] [20:36:13] cryos|laptop: Thanks, noted. :-) +[Sa Okt 13 2007] [20:37:05] Ok, so it's 3:1 for keeping the monolithic ebuilds for KDE4. +[Sa Okt 13 2007] [20:37:17] Anything else on KDE4? +[Sa Okt 13 2007] [20:37:37] jmbsvicetto: From our side we have runtime, workspace and apps in kdebase +[Sa Okt 13 2007] [20:37:43] * jakub still offers a keg for getting sets and ranged deps in b4 KDE4 :D +[Sa Okt 13 2007] [20:37:51] Sho_: sorry, that's it - kdebase and kdebase-workspace +[Sa Okt 13 2007] [20:38:28] Sho_: That's what Ingmar^ said, iirc +[Sa Okt 13 2007] [20:38:47] jmbsvicetto: ^^ ding ding - motivation above! :) +[Sa Okt 13 2007] [20:38:54] jmbsvicetto: Ingmar^ is a great fan of splitting. He might do even more. :-) +[Sa Okt 13 2007] [20:38:57] :) +[Sa Okt 13 2007] [20:38:57] anyway, /me out for a couple of plops, have fun guys :) +[Sa Okt 13 2007] [20:39:14] Quit tibix_ has left this server (Read error: 110 (Connection timed out)). +[Sa Okt 13 2007] [20:39:17] Ok, the point for KDE4 should be done then. :-) +[Sa Okt 13 2007] [20:39:46] Join tibix_ has joined this channel (n=tibix@host86.200-45-178.telecom.net.ar). +[Sa Okt 13 2007] [20:39:48] Next point: I'm going to document the procedure of bumping to the minor KDE revisions. Any help is welcome. I'll present a draft soon. +[Sa Okt 13 2007] [20:40:05] jakub: If we need you, we'll send you a *SIGBEER* ;) +[Sa Okt 13 2007] [20:40:58] Anything I should take special care of when documenting possible bump procedures? +[Sa Okt 13 2007] [20:42:01] Ok, obviously not. :-) +[Sa Okt 13 2007] [20:42:11] Philantrop: Sorry, but since you're talking about documentation, most people are likely to need some kde4 crash course - in particular to cmake +[Sa Okt 13 2007] [20:42:29] s/most/some/ +[Sa Okt 13 2007] [20:42:31] jmbsvicetto: ok, sounds like a deal :) +[Sa Okt 13 2007] [20:42:56] jmbsvicetto: :-) Well, yes, but there's not much we can do about it, I think. Self-education should be most effective unless you have a better suggestion. :) +[Sa Okt 13 2007] [20:43:40] jmbsvicetto: Unless you want to install a "re-education camp". ;) +[Sa Okt 13 2007] [20:43:46] hehe +[Sa Okt 13 2007] [20:44:13] hmmm, camp... steaks... _beer_ +[Sa Okt 13 2007] [20:44:19] Philantrop++ +[Sa Okt 13 2007] [20:44:21] Well, I guess I'll need to reeducate myself, since I haven't seen kde4 in a while ;) +[Sa Okt 13 2007] [20:44:31] jmbsvicetto: I'll add this to the summary, though. Maybe someone has an idea or helpful link. :-) +[Sa Okt 13 2007] [20:44:52] jakub: I thought more along the lines of a prison camp. ;-) +[Sa Okt 13 2007] [20:44:59] Philantrop: it would be cool to explain why it is best to have the non-working ebuilds in the git to allow external help and afterwards in gentoo-x86 to allow internal testing :) +[Sa Okt 13 2007] [20:45:32] genstef: It doesn't have to be git, just an overlay +[Sa Okt 13 2007] [20:45:46] jmbsvicetto: right +[Sa Okt 13 2007] [20:45:46] genstef: But git is good a choice +[Sa Okt 13 2007] [20:46:10] git would be cool for the portage tree imo. Just pull from external contributors :) +[Sa Okt 13 2007] [20:46:16] well, * >> cvs :) +[Sa Okt 13 2007] [20:46:36] genstef: You know how the cvs/svn/git/* debate ended last time ;) +[Sa Okt 13 2007] [20:46:48] genstef: We don't *have* to do it in a git repository for all times. This was just one approach. :-) +[Sa Okt 13 2007] [20:47:07] jmbsvicetto: well yeah, it's not gonna get anywhere... +[Sa Okt 13 2007] [20:47:11] jmbsvicetto: ok, better not discuss it then ;) +[Sa Okt 13 2007] [20:47:20] jmbsvicetto: we'll be stuck w/ cvs until we switch infra first +[Sa Okt 13 2007] [20:47:53] jakub: I wouldn't say that. I think robbat2 is close to accept git +[Sa Okt 13 2007] [20:48:06] !herd kde +[Sa Okt 13 2007] [20:48:09] Philantrop: (kde) caleb, carlo, centic, cryos, deathwing00, genstef, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, troll, vanquirius +[Sa Okt 13 2007] [20:48:09] switch infra! +[Sa Okt 13 2007] [20:48:10] Anything else we should discuss? :-) +[Sa Okt 13 2007] [20:48:11] jakub: He has worked on it to supress the shortcommings +[Sa Okt 13 2007] [20:48:16] * jakub really out now... oh btw, getting the new eclasses eclass-manpages friendly would be nice :) +[Sa Okt 13 2007] [20:48:26] jakub: Yes, that's in the making. :-) +[Sa Okt 13 2007] [20:48:48] Philantrop: if you want help, poke me ;) +[Sa Okt 13 2007] [20:48:55] Philantrop: What about the cmake eclass? +[Sa Okt 13 2007] [20:49:00] jakub: Thanks, I surely will! :-) +[Sa Okt 13 2007] [20:49:26] jmbsvicetto: We have one more showstopper in it: cmake-utils-src_test. We need to work on that before I re-submit it. +[Sa Okt 13 2007] [20:49:26] Philantrop: Has it been merged to Portage or is it still on the overlay? +[Sa Okt 13 2007] [20:49:36] jmbsvicetto: It's still in the overlay only. +[Sa Okt 13 2007] [20:49:37] Philantrop: Oh and one final issue - ATs/HTs! +[Sa Okt 13 2007] [20:49:43] waah, cmake.eclass is not yet in the tree? +[Sa Okt 13 2007] [20:49:56] urrx, should be imo +[Sa Okt 13 2007] [20:50:12] genstef: Unfortunately, no. People had lots of suggestions. We've done most of it but that one remains. +[Sa Okt 13 2007] [20:50:28] genstef: I'm going to try to get it in next week, though. +[Sa Okt 13 2007] [20:51:45] jmbsvicetto: ping +[Sa Okt 13 2007] [20:51:55] The problem is: cmake-utils' src_test is mostly a copy of the one in ebuild.sh but we currently need it to check whether it's an in-source or out-of-source build. +[Sa Okt 13 2007] [20:52:05] Any help on this would be greatly appreciated. +[Sa Okt 13 2007] [20:52:37] jmbsvicetto: "ATs/HTs". What's your suggestion about them? +[Sa Okt 13 2007] [20:52:51] Well, glep41 http://www.gentoo.org/proj/en/glep/glep-0041.html created ATs and HTs +[Sa Okt 13 2007] [20:53:01] jmbsvicetto: so, config ata is sompiled into the kernel, same as config ide +[Sa Okt 13 2007] [20:53:03] I think kde would benefit from having a HT team +[Sa Okt 13 2007] [20:53:10] jmbsvicetto: Yes, but it has been rejected by the council in its current state. :) +[Sa Okt 13 2007] [20:53:19] shade: We're in the middle of a meeting. Give us a few minutes, ok? Thanks +[Sa Okt 13 2007] [20:53:34] Philantrop: Not rejected. It hasn't been implemented +[Sa Okt 13 2007] [20:53:36] jmbsvicetto: ok, np:) +[Sa Okt 13 2007] [20:53:51] Philantrop: And ATs get official recognition +[Sa Okt 13 2007] [20:53:55] jmbsvicetto: I thought so, too. Look at the relevant meeting's log, though. :) +[Sa Okt 13 2007] [20:54:21] Philantrop: What hasn't been accepted is the @g.o email addresses. Everything else was accepted +[Sa Okt 13 2007] [20:54:32] Philantrop: So, can I be a kde ht? +[Sa Okt 13 2007] [20:54:40] We use HTs in the sci herd quite successfully. +[Sa Okt 13 2007] [20:54:42] jmbsvicetto: There's nothing to say against Herd Testers, though. :-) +[Sa Okt 13 2007] [20:54:57] Philantrop: Pretty, pretty please? +[Sa Okt 13 2007] [20:55:04] ;) +[Sa Okt 13 2007] [20:55:05] cryos|laptop: Oh? That's good to know. Never heard about them before. :) +[Sa Okt 13 2007] [20:55:05] I got them boosted bugzilla powers and access the overlay. +[Sa Okt 13 2007] [20:55:23] Philantrop: Quite a few went on to become devs later too. +[Sa Okt 13 2007] [20:55:32] cryos|laptop: How's the procedure to make them HTs? +[Sa Okt 13 2007] [20:55:55] I think I was supposed to make a web page about this stuff. +[Sa Okt 13 2007] [20:56:01] cryos|laptop: :-)) +[Sa Okt 13 2007] [20:56:05] Philantrop: Anyway, "personally" I won't gain anything I don't have yet, with the exception of showing up in the kde team page. But other people could get official recognition +[Sa Okt 13 2007] [20:56:27] jmbsvicetto: Well, there's precedent, it seems and it makes sense... +[Sa Okt 13 2007] [20:56:31] I just used to talk to someone who I have forgotten now who was in charge of the AT project about getting bugzie sorted. +[Sa Okt 13 2007] [20:56:34] yeah, I like the idea +[Sa Okt 13 2007] [20:56:41] cryos|laptop: hparker ;) +[Sa Okt 13 2007] [20:56:43] cryos|laptop: That would be hparker. +[Sa Okt 13 2007] [20:56:48] Yes jmbsvicetto! +[Sa Okt 13 2007] [20:56:54] cryos|laptop: hparker +[Sa Okt 13 2007] [20:56:57] It has been a while :) +[Sa Okt 13 2007] [20:57:08] So, do we want Herd Testers? I support the idea. Others? +[Sa Okt 13 2007] [20:57:20] I think it works well and would support the idea. +[Sa Okt 13 2007] [20:57:35] cryos|laptop: s/would/will/ !!! ;) +[Sa Okt 13 2007] [20:57:57] masterdriverz, tgurr: Your vote? +[Sa Okt 13 2007] [20:58:04] sure :) +[Sa Okt 13 2007] [20:58:08] It is a great chance for people to get a bit of a taste of being a dev and decide if it is for them. Some only ever want the HT position and others drift away again,. +[Sa Okt 13 2007] [20:58:43] Means when people go on to become devs they are usually more certain about actually wanting to do it too. +[Sa Okt 13 2007] [20:58:56] Ok, so we have four "yes" (genstef, cryos|laptop, tgurr, Philantrop) and no objections. :-) +[Sa Okt 13 2007] [20:59:04] cryos|laptop: Yes, sounds really good to me. :-) +[Sa Okt 13 2007] [20:59:21] I'll talk to hparker about it. +[Sa Okt 13 2007] [20:59:24] so we need some amendment to the project page about that, right? +[Sa Okt 13 2007] [20:59:39] genstef: Yes, thanks for volunteering! ;) +[Sa Okt 13 2007] [20:59:45] including the procedure of how a herd member goes about promoting someone to HT :) +[Sa Okt 13 2007] [20:59:50] ok :) +[Sa Okt 13 2007] [20:59:58] genstef: You would add a section listing the HT members and some documentation on how to become one +[Sa Okt 13 2007] [21:00:06] right +[Sa Okt 13 2007] [21:00:29] genstef: So you'd be willing to make a draft for that? Maybe for the next meeting (or earlier)? :) +[Sa Okt 13 2007] [21:00:30] genstef: I'm probably going to have to do something similar for sparc ATs, so if you want, I can work with you on that +[Sa Okt 13 2007] [21:01:02] jmbsvicetto: ok, cool! +[Sa Okt 13 2007] [21:01:14] Philantrop: will send it to kde@gentoo.org then +[Sa Okt 13 2007] [21:01:27] genstef, jmbsvicetto: Thanks, guys! I'll add that to the summary, too. +[Sa Okt 13 2007] [21:01:44] Anything else, gentlemen? +[Sa Okt 13 2007] [21:02:43] Philantrop: About six-sigma, are we still interested in trying it on kde? +[Sa Okt 13 2007] [21:02:55] Philantrop: If so, do we leave that for a future meeting where NeddySeagoon can help? +[Sa Okt 13 2007] [21:03:12] jmbsvicetto: Good question. Opinions? +[Sa Okt 13 2007] [21:03:36] six-sigma? +[Sa Okt 13 2007] [21:04:07] tgurr: Oh, right. That was before your dev time. It's a process improvement thing. +[Sa Okt 13 2007] [21:04:25] tgurr: I'll forward you a mail about it. +[Sa Okt 13 2007] [21:04:47] re +[Sa Okt 13 2007] [21:05:00] I'd say we invite Neddy to our next meeting and see about it then. Any objections? +[Sa Okt 13 2007] [21:05:07] Philantrop, thanks :) +[Sa Okt 13 2007] [21:05:14] keytoaster: Welcome back! :-) +[Sa Okt 13 2007] [21:05:27] :) +[Sa Okt 13 2007] [21:05:29] Anything else? +[Sa Okt 13 2007] [21:06:29] I'll make a summary of our meeting and export a log from Konversation. I'll mail it around to kde@g.o and if it's fine, I'll ask keytoaster to add it to our project page. Ok? +[Sa Okt 13 2007] [21:06:33] Philantrop: Maybe just a heads-up about next meeting date? +[Sa Okt 13 2007] [21:06:39] Philantrop: thanks :) +[Sa Okt 13 2007] [21:06:41] Philantrop: sure +[Sa Okt 13 2007] [21:07:08] If I'm not mistaken, next meeting will take place at 13/11 +[Sa Okt 13 2007] [21:07:28] Ok, then. The next meeting will take place on November, 10th, 2007 at 18:00 UTC here in #gentoo-kde. :-) I'll mail reminders again and poke you guys on IRC whereever I find you. :-) +[Sa Okt 13 2007] [21:08:04] Sorry, 10/11 +[Sa Okt 13 2007] [21:08:15] Philantrop, uhm, could we do that on another date +[Sa Okt 13 2007] [21:08:25] keytoaster: What's wrong with that date? :-) +[Sa Okt 13 2007] [21:08:43] i just found out that my family visits my friend every second saturday of the month as well... +[Sa Okt 13 2007] [21:09:02] so we'll probably be having dinner at this time, just like today +[Sa Okt 13 2007] [21:09:14] so i will most likely never be able to attend the whole meeting +[Sa Okt 13 2007] [21:09:17] first saturday then? :) +[Sa Okt 13 2007] [21:09:22] fine for me +[Sa Okt 13 2007] [21:09:28] hehe +[Sa Okt 13 2007] [21:09:32] !herd kde +[Sa Okt 13 2007] [21:09:35] Philantrop: (kde) caleb, carlo, centic, cryos, deathwing00, genstef, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, troll, vanquirius +[Sa Okt 13 2007] [21:09:45] Shall we move our meetings to the first Saturday each month? +[Sa Okt 13 2007] [21:09:48] first saturday is bug day, but fine with me ;) +[Sa Okt 13 2007] [21:10:42] cryos|laptop, genstef, keytoaster, masterdriverz, tgurr? First Saturday each month from November on? +[Sa Okt 13 2007] [21:10:51] yes +[Sa Okt 13 2007] [21:11:07] Yes. +[Sa Okt 13 2007] [21:11:17] fine to me +[Sa Okt 13 2007] [21:11:44] Anyone objects having a note on the project page about the "usual" meeting time? +[Sa Okt 13 2007] [21:12:01] In case any interested party wants to follow the meetings +[Sa Okt 13 2007] [21:12:12] If I didn't misread genstef he doesn't object to it either so that would be 5:0 in favour of moving it. :-) +[Sa Okt 13 2007] [21:12:54] keytoaster: Could you add a note about the 1st Sat every month as our meeting time? +[Sa Okt 13 2007] [21:13:28] yup +[Sa Okt 13 2007] [21:13:53] It's decided then: The next meeting will take place on November, 3rd, 2007 at 18:00 UTC here in #gentoo-kde. :-) +[Sa Okt 13 2007] [21:14:05] i'll do it as soon as i'm home +[Sa Okt 13 2007] [21:14:12] keytoaster: Sure, no worries. :-) +[Sa Okt 13 2007] [21:14:30] !herd kde +[Sa Okt 13 2007] [21:14:31] Philantrop: (kde) caleb, carlo, centic, cryos, deathwing00, genstef, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, troll, vanquirius +[Sa Okt 13 2007] [21:14:32] Anything else for tonight, guys? +[Sa Okt 13 2007] [21:15:16] Can't recall anything else +[Sa Okt 13 2007] [21:15:37] Ok, thanks to all of your for attending. It's great this works and I really appreciate your feedback and help! +[Sa Okt 13 2007] [21:15:46] s/your/you :-) +[Sa Okt 13 2007] [21:15:52] Philantrop: well, I wonder about a kde lead? I think we decided last time about it, but cannot find anything on the project page? +[Sa Okt 13 2007] [21:16:03] genstef: We didn't decide about it. :) +[Sa Okt 13 2007] [21:16:30] genstef: I think we decided to *not* decide ;) +[Sa Okt 13 2007] [21:16:41] We could decide about it, of course. +[Sa Okt 13 2007] [21:16:46] Philantrop: some note like "we do not have a lead: decisions can be made by everyone but it usually it is a good idea to ask philantrop because he is around and knowledgable" +[Sa Okt 13 2007] [21:17:46] I would like to propose we select a lead for kde and I want to suggest Philantrop +[Sa Okt 13 2007] [21:17:46] anyways, not that important .. +[Sa Okt 13 2007] [21:18:48] Does anyone want to open up the election process? +[Sa Okt 13 2007] [21:18:58] jmbsvicetto: totally against it +[Sa Okt 13 2007] [21:19:05] we already decided on the matter :) +[Sa Okt 13 2007] [21:19:13] it just needs to be reflected on the project page +[Sa Okt 13 2007] [21:19:14] Against the lead or the election? ;) +[Sa Okt 13 2007] [21:19:19] Ah, ok :) +[Sa Okt 13 2007] [21:19:38] you said what we decided +[Sa Okt 13 2007] [21:19:42] :) +[Sa Okt 13 2007] [21:19:51] genstef: We'll add the note as you suggested to the project page. :-) +[Sa Okt 13 2007] [21:19:56] keytoaster: Mind to add a note to the page? ;) +[Sa Okt 13 2007] [21:20:11] Philantrop: We should also send a mail to -core or -dev announcing it +[Sa Okt 13 2007] [21:20:20] give me a complete text :) +[Sa Okt 13 2007] [21:20:40] keytoaster: look a few lines a bove the long text. +[Sa Okt 13 2007] [21:21:00] keytoaster: "We do not have a formal lead: Decisions can be made by every herd member but it usually is a good idea to ask philantrop because he is around and knowledgable." +[Sa Okt 13 2007] [21:21:41] ah, k, thanks +[Sa Okt 13 2007] [21:22:17] Ok, final call: Anything else? :-) +[Sa Okt 13 2007] [21:22:18] possibly close to the members box +[Sa Okt 13 2007] [21:22:34] keytoaster: Directly above the box, I'd say. :-) +[Sa Okt 13 2007] [21:24:28] I'm off then, ok? +[Sa Okt 13 2007] [21:25:00] Ok, let's call this meeting closed! Thanks again! :-) diff --git a/meeting-logs/20080306-summary.txt b/meeting-logs/20080306-summary.txt new file mode 100644 index 0000000..3208285 --- /dev/null +++ b/meeting-logs/20080306-summary.txt @@ -0,0 +1,80 @@ +Summary for the Gentoo KDE herd meeting on Thursday, 6th of March 2008 + +Participants: +caleb, cryos, deathwing00, genstef, ingmar, jmbsvicetto, keytoaster, philantrop, tgurr, zlin + +1. Bump to KDE 3.5.9: + +Apart from a few minor issues, the bump to KDE 3.5.9 went well. + +https://bugs.gentoo.org/211116 (mixing split and monolithic ebuilds) was +discussed. 3 participants didn't want the current behaviour changed, 3 were in +favour of changing it. Thus, it was agreed that Ingmar, who volunteered to +change it, should feel free to do it. + +2. KDE 3.5.8 in stable for 2008.0. + +Philantrop stated that KDE 3.5.8 will be in the 2008.0 release. + +3. Removal of KDE < 3.5.8 from the tree. + +gentoofan23 brought up the issue of the removal of older (specifically 3.5.7) +stable KDE versions from the tree after about 19 days and asked for a longer +period for users to upgrade to the newest stable version. +30 days were suggested as a rule of thumb and agreed upon by the majority of +the participants. + +4. State of KDE4 in the tree. + +Ingmar and zlin gave a short information about KDE4 in the tree. The ebuilds in +the tree are in a pretty good state. Their dependencies need to be updated for +compatibility with the newly introduced split Qt-4.4 ebuilds. + +KDE 4.0.2 is currently planned to be included in the tree during the weekend. +(p.masked) + +Anyone who wants to help with the bump to 4.0.2 should simply mail Philantrop +his ssh public key. Interested users who can show they're able and willing to +work on ebuilds are *explicitly* invited, too. +The bump to 4.0.2 is taking place in a git overlay again to allow for non-ebuild +devs to participate, too, and it's a great way to become a dev as Ingmar and +zlin can verify. + +5. Herd Testers: Current state and next steps. + +The HT stuff was delayed because of the trustee elections, etc. +jmbsvicetto and deathwing00 agreed to flesh out the work of a KDE Herd Tester +and publish information about it on the usual Gentoo news channels (pr@g.o, +GMN, Forums). + +6. Lead election: + +Having a sub-lead was discussed to ensure not to have a single point of failure +in case the lead disappears. In a vote, 3 herd members expressed their wish for +a sub-lead, 5 voted against it and there was one abstention. Thus, the notion +was rejected. + +deathwing00 initiated a vote for the lead. Philantrop was nominated and accepted +the nomination. +Philantrop was voted for by 9 of the participants, no votes against him and no +abstentions. Thus, Philantrop was elected the lead of the Gentoo KDE project. + +deathwing00 is going to inform the GMN, pr@g.o and post it on the forums. + +7. Review of the project page + +gentoofan23 and deathwing00 volunteered to update the project page with respect +to KDE versions and other information in the sections 3, 4, 8 and 9 till the +next meeting. + +8. Miscellaneous + +It was decided to re-instate the monthly meetings on the first Thursday each +month. + +9. Date of the next meeting and closing. + +The next KDE herd meeting takes place on Thursday, 3rd of April 2008. + +Philantrop thanked all the Gentoo KDE people for their great work and their +trust in him. diff --git a/meeting-logs/20080306.txt b/meeting-logs/20080306.txt new file mode 100644 index 0000000..acda721 --- /dev/null +++ b/meeting-logs/20080306.txt @@ -0,0 +1,518 @@ +[Do Mär 6 2008] [20:30:29] !herd kde +[Do Mär 6 2008] [20:30:31] Philantrop: (kde) caleb, carlo, cryos, deathwing00, genstef, ingmar, jmbsvicetto, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, zlin +[Do Mär 6 2008] [20:30:32] ping ^^^ +[Do Mär 6 2008] [20:30:37] evening :) +[Do Mär 6 2008] [20:30:38] pong +[Do Mär 6 2008] [20:30:50] :> +[Do Mär 6 2008] [20:31:14] ctennis == caleb +[Do Mär 6 2008] [20:31:19] meh +[Do Mär 6 2008] [20:31:24] ctennis: Yes, thanks, I know. :-) +[Do Mär 6 2008] [20:31:32] just making sure everyone else did :) +[Do Mär 6 2008] [20:32:05] bzzzzz +[Do Mär 6 2008] [20:32:09] * gentoofan23 guessed +[Do Mär 6 2008] [20:33:02] jmbsvicetto, masterdriverz, genstef around? :-) +[Do Mär 6 2008] [20:33:11] * cryos|laptop had no clue... +[Do Mär 6 2008] [20:33:22] Mode ChanServ gives channel operator privileges to deathwing00. +[Do Mär 6 2008] [20:33:28] Mode deathwing00 gives channel operator privileges to you. +[Do Mär 6 2008] [20:33:34] Mode deathwing00 gives masterdriverz the permission to talk. +[Do Mär 6 2008] [20:34:20] Ok, let's start guys! :-) First on the agenda is the bump to 3.5.9 which was somewhat, bumpy... ;) +[Do Mär 6 2008] [20:34:24] Mode deathwing00 gives ctennis the permission to talk. +[Do Mär 6 2008] [20:34:44] deathwing00: Thanks, but this will be open floor anyway. :-) +[Do Mär 6 2008] [20:34:50] ok +[Do Mär 6 2008] [20:35:29] We have one major issue open: Split and monotlithic ebuilds. Split ebuilds depend hard on split dependencies and won't accept monolithic ebuilds. +[Do Mär 6 2008] [20:35:45] Some of us want to change that, some others don't. Your opinions? +[Do Mär 6 2008] [20:36:33] Well, doesn't it depend on the program? Some could do a || dep on split/monolithic and some can't, right? +[Do Mär 6 2008] [20:37:25] gentoofan23: No, not really as basically any monolithic ebuild would install what its split packages would. +[Do Mär 6 2008] [20:37:43] But we're talking about kde-base/* only here. +[Do Mär 6 2008] [20:38:10] My opinion is that we should opt to drop monolithic ebuilds for the following reasons: 1) Applying security fixes and patches to a split ebuild implies less development and maintenance effort, which in turn 2) implies less compilation on users and 3?) if I remember correctly KDE 4 was going to drop monolithic components (how's that by the way?) +[Do Mär 6 2008] [20:38:46] ++ +[Do Mär 6 2008] [20:38:48] KDE 4 has had them dropped already +[Do Mär 6 2008] [20:38:53] !bug 211116 +[Do Mär 6 2008] [20:38:55] Philantrop: https://bugs.gentoo.org/211116 maj, P2, All, infoman1985@gmail.com->kde@gentoo.org, REOPENED, pending, kde-base/*-3.5.9 split packages can't be mixed with kde-base/*-3.5.9 monolithic packages. +[Do Mär 6 2008] [20:38:55] Philantrop: https://bugs.gentoo.org/211116 maj, P2, All, infoman1985@gmail.com->kde@gentoo.org, REOPENED, pending, kde-base/*-3.5.9 split packages can't be mixed with kde-base/*-3.5.9 monolithic packages. +[Do Mär 6 2008] [20:39:15] ^^^ That's the bug. +[Do Mär 6 2008] [20:39:29] but I disagree, dropping monolithic :3.5 ebuilds is a regression imho, besides, some slow arches only have those keyworded, and I see no reason to force a change upon them on a version of KDE that's getting EOL'ed soon +[Do Mär 6 2008] [20:40:12] mixing splits and monolithic was never supported by us anyways, was it? possible yes.. sadly :) +[Do Mär 6 2008] [20:40:15] I'm with Ingmar on this one +[Do Mär 6 2008] [20:40:31] I'd like to keep it the way it is as only a few users even complained and most jsut switched to split ebuilds. :-) +[Do Mär 6 2008] [20:40:49] * Philantrop scribbles two names into his little black book... ;-) +[Do Mär 6 2008] [20:40:55] well, other users apparently care enough to attach a partial patch +[Do Mär 6 2008] [20:41:03] we are not planning on offering monolithic ebuilds on KDE 4, are we? +[Do Mär 6 2008] [20:41:04] tgurr: it used to be possible through the eclasses. 3.5.9 uses EAPI=1 and thus doesn't use those eclass functions anymore... +[Do Mär 6 2008] [20:41:11] deathwing00: Nope. :-) +[Do Mär 6 2008] [20:41:17] pong +[Do Mär 6 2008] [20:41:20] sorry, just got home +[Do Mär 6 2008] [20:41:22] and it doesn't make sense for a user that kdebase + kdenetwork works, but kdebase + kopete doesn't +[Do Mär 6 2008] [20:41:30] jmbsvicetto: No problem. Thanks for being here. +[Do Mär 6 2008] [20:41:36] I object as some boxes I maintain use monolithic and it'd be a huge pain to switch to split. I imagine many others would feel pain to +[Do Mär 6 2008] [20:41:48] and that's a good point too +[Do Mär 6 2008] [20:41:49] If we are to not provide it on KDE 4, we can let it be for now, I guess +[Do Mär 6 2008] [20:41:55] converting = lots of useless work +[Do Mär 6 2008] [20:42:15] gentoofan23: the problem is mixing. not all splits or all monos. +[Do Mär 6 2008] [20:42:34] make all splits block all monos and vice-versa +[Do Mär 6 2008] [20:42:52] that's essentially what we have now +[Do Mär 6 2008] [20:42:58] "you want a full mono, you got -meta" +[Do Mär 6 2008] [20:43:06] I agree on that one +[Do Mär 6 2008] [20:43:35] zlin: is it correctly implemented or are we missing something? +[Do Mär 6 2008] [20:43:46] Ok, let's try a slightly different approach - is anyone here willing to change what we have now? :-) +[Do Mär 6 2008] [20:43:59] * Philantrop looks at Ingmar and zlin. *g* +[Do Mär 6 2008] [20:44:32] we can sort of vote if necessary +[Do Mär 6 2008] [20:44:36] Guess that means that I'll do it +[Do Mär 6 2008] [20:44:49] Sure you can vote, but unless you convince me *not* to do it, it's going to happen though :> +[Do Mär 6 2008] [20:45:18] Join mikb has joined this channel (n=mikb@c211-31-30-148.belrs4.nsw.optusnet.com.au). +[Do Mär 6 2008] [20:45:19] Ingmar: I missed something in here... what is gonna happen? +[Do Mär 6 2008] [20:45:20] deathwing00: Well, I've already recorded opinions. At the moment, we're stuck at 2:2 but if Ingmar volunteers, why not. :-) +[Do Mär 6 2008] [20:45:37] Philantrop: ok, got it +[Do Mär 6 2008] [20:45:43] Quit mikb has left this server (Client Quit). +[Do Mär 6 2008] [20:45:53] \o/ +[Do Mär 6 2008] [20:45:54] deathwing00: What Ingmar wants to do is allowing users to mix 3.5.9 splits and monos again. I'm not too strongly against it. :-) +[Do Mär 6 2008] [20:46:02] It's simply stupid to force monolithic users to switch +[Do Mär 6 2008] [20:46:38] Ingmar: Well, considering that they will have to switch for KDE4 anyway, it wouldn't be too bad, I think, but since you volunteered... :-) +[Do Mär 6 2008] [20:46:43] arfie's patch shows what's we want to change.. might not be complete but you get the idea... +[Do Mär 6 2008] [20:46:48] As I've told others before, I agree that the problems caused by mixing splits/monos is reason enough to have splits hard dep on split +[Do Mär 6 2008] [20:47:11] But if Ingmar wants to support it, let him +[Do Mär 6 2008] [20:47:27] jmbsvicetto: Well, a thing Ingmar brought up elsewhere, we might run into even more bug reports now. :) +[Do Mär 6 2008] [20:47:39] Ingmar: If anyone else is willing to help you, you might want ot use an overlay to do that work +[Do Mär 6 2008] [20:47:45] Philantrop: so who is 'yeah' and who is 'nay'? +[Do Mär 6 2008] [20:48:15] deathwing00: I'm a yeay/neah ;) +[Do Mär 6 2008] [20:48:20] hehe +[Do Mär 6 2008] [20:48:30] * gentoofan23 isn't sure if he can vote, so he abstains. :). That's rather paradoxical though +[Do Mär 6 2008] [20:48:36] deathwing00: I've recorded you as "nay" to mixing, me too, jmbsvicetto undecided. Ingmar and zlin "yay". :-) +[Do Mär 6 2008] [20:48:44] ok +[Do Mär 6 2008] [20:48:51] * cryos|laptop is nay... +[Do Mär 6 2008] [20:48:54] jmbsvicetto: decide already +[Do Mär 6 2008] [20:49:17] cryos|laptop: Just to be sure: "Nay" to mixing splits and monos in 3.5.9? +[Do Mär 6 2008] [20:49:23] Yep +[Do Mär 6 2008] [20:49:23] Ingmar: If you do that work on an overlay, I can try to help on "a few" ebuilds - no promises though +[Do Mär 6 2008] [20:49:45] cryos|laptop: Thanks, noted. Anything you could add to make Ingmar see the light? ;-) +[Do Mär 6 2008] [20:50:16] Philantrop: Just that it really does not seem worth the effort, we looked at this in the beginning when splits were introduced.. +[Do Mär 6 2008] [20:50:26] deathwing00: My view is that allowing that is a good thing, but I understand if we decide otherwise. In any case, I can't commit that to the tree. I can try to help on an overlay though +[Do Mär 6 2008] [20:50:48] carlo is clearly a "yay" too and it was supported till 3.5.8 +[Do Mär 6 2008] [20:50:52] If he wants to do it I think he should try it but I wouldn't spend my time trying to fix that personally. It seems tough to get it right and I wonder where the pay off is. +[Do Mär 6 2008] [20:51:27] * cryos|laptop has been largely AFK in recent months though - desktop in a US customs area in New York still :-( +[Do Mär 6 2008] [20:51:46] cryos|laptop: That's annyoing. :-( +[Do Mär 6 2008] [20:52:04] Ok, se can we settle this by saying Ingmar may fix it if he wants? :-) +[Do Mär 6 2008] [20:52:05] I have another argument that you could consider, if we add this for 3.5.9 and then it exists no longer to KDE 4, won't the users be forced into monolithic anyway? +[Do Mär 6 2008] [20:52:14] Yeah - delays, delays and more delays. Do have my Gentoo laptop working with KDE4 and 3.5.9 though. +[Do Mär 6 2008] [20:52:26] deathwing00: To split ebuilds, yes. +[Do Mär 6 2008] [20:52:37] cryos|laptop: At least something. :-) +[Do Mär 6 2008] [20:52:48] Philantrop: yeah, that's what I meant +[Do Mär 6 2008] [20:52:52] deathwing00: that's a different SLOT though so it doesn't matter all that much imo +[Do Mär 6 2008] [20:52:59] Philantrop: I agree with that +[Do Mär 6 2008] [20:53:15] Quit ZeRoX has left this server (Client Quit). +[Do Mär 6 2008] [20:53:19] IIRC, the move forward is another point on this discussion +[Do Mär 6 2008] [20:53:32] zlin: I understand, but it might be a needless effort, we could focus our efforts elsewhere, m¢ :) +[Do Mär 6 2008] [20:53:39] Ok, final call for violent objections against Ingmar changing it. :-) +[Do Mär 6 2008] [20:53:48] no veto here +[Do Mär 6 2008] [20:54:07] deathwing00: that just means it's low priority.. :) +[Do Mär 6 2008] [20:54:16] zlin: agreed +[Do Mär 6 2008] [20:54:22] Ok, any other points that should be brought up for the past 3.5.9 version bump? +[Do Mär 6 2008] [20:55:10] Ok, topic 2: KDE 3.5.8 is stable now and will be in the 2008.0 release. :-) +[Do Mär 6 2008] [20:55:10] I have a point(slightly related). Is there anything wrong with keeping the old stable around a little longer(3.5.7 specifically)? +[Do Mär 6 2008] [20:55:34] gentoofan23: Well, what's wrong with removing it after a newer one has gone stable? +[Do Mär 6 2008] [20:56:15] Join ZeRoX has joined this channel (n=zerox@nelug/developer/zer0x). +[Do Mär 6 2008] [20:56:16] Well, we don't intend to support 5 versions of KDE +[Do Mär 6 2008] [20:56:38] Philantrop: Stable users only had 19 days(iirc) to upgrade before 3.5.7 got booted. It bit me in that I needed to install a specific aspect of Kde and only 3.5.8 was available. So I had to upgrade all of kdelibs,base to get that new portion +[Do Mär 6 2008] [20:57:11] given that we have a newer version which we know is way better, fixes tons of bugs and noone neither upstream nor downstream want to support the old version... +[Do Mär 6 2008] [20:57:26] Ingmar: I'm not suggesting that, I'm suggesting keeping it around a bit longer. 19 days is a little short +[Do Mär 6 2008] [20:57:30] I honestly don't see why we'd keep old stable versions around when never, better stable ebuilds are available +[Do Mär 6 2008] [20:57:33] it isn't +[Do Mär 6 2008] [20:57:42] gentoofan23: Well, yes, I would have thought two weeks were enough to update. It was even for my old Alpha workstation with 233 MHz. :) +[Do Mär 6 2008] [20:58:16] eh, I was a little busy. but granted that, I concede my point I guess +[Do Mär 6 2008] [20:58:22] gentoofan23: What would have been long enough for you? +[Do Mär 6 2008] [20:58:35] (Under normal circumstances.) +[Do Mär 6 2008] [20:58:41] Philantrop: This falls down to the discussion between maintainers/ats about whether old working versions shold be kept around or not +[Do Mär 6 2008] [20:58:55] Philantrop: maybe 45 days? +[Do Mär 6 2008] [20:59:07] gentoofan23: How about 30? :-) +[Do Mär 6 2008] [20:59:15] * Philantrop emulates a bazaar. ;-) +[Do Mär 6 2008] [20:59:19] Philantrop: even that'd be ok I guess +[Do Mär 6 2008] [20:59:19] 30 sounds more reasonable to me +[Do Mär 6 2008] [20:59:25] Join NeddySeagoon has joined this channel (n=NeddySea@gentoo/developer/NeddySeagoon). +[Do Mär 6 2008] [20:59:25] Mode ChanServ gives NeddySeagoon the permission to talk. +[Do Mär 6 2008] [20:59:30] Philantrop: I agree that for maintainers it makes sense to kick old versions - in particular for a project with as many ebuilds as kde +[Do Mär 6 2008] [20:59:30] 19 is rather unreasonable to me. +[Do Mär 6 2008] [20:59:41] yay to 30 days by me then +[Do Mär 6 2008] [20:59:54] jmbsvicetto: That's why we did it, indeed. :-) +[Do Mär 6 2008] [21:00:08] hey, Kubuntu is still supporting a KDE from 3 years ago :-P +[Do Mär 6 2008] [21:00:08] And Ingmar stole all those commits from me! ;-) +[Do Mär 6 2008] [21:00:19] hehe +[Do Mär 6 2008] [21:00:38] gentoofan23: 30 days are ok then? :-) +[Do Mär 6 2008] [21:00:40] So next time Philantrop will be so pressed to get thsoe commits, it won't even be 19 days :> +[Do Mär 6 2008] [21:00:57] Philantrop: yeah, it should be. Of course, I don't use mips :p +[Do Mär 6 2008] [21:01:21] gentoofan23: It doesn't matter anymore. mips has gone the unstable road +[Do Mär 6 2008] [21:01:35] jmbsvicetto: Oh yes, that is true +[Do Mär 6 2008] [21:01:37] Ok, anything else on the bump or 3.5.8 in the upcoming release? +[Do Mär 6 2008] [21:01:49] gentoofan23: From now on, mips needs to keyword a version at least until everyone marks it stable +[Do Mär 6 2008] [21:02:00] they already did +[Do Mär 6 2008] [21:02:03] monolithic 3.5.9 +[Do Mär 6 2008] [21:02:10] Ingmar: ok +[Do Mär 6 2008] [21:02:11] * Philantrop sobs +[Do Mär 6 2008] [21:02:21] * Philantrop sees his ebuilds tainted. ;-) +[Do Mär 6 2008] [21:02:30] Philantrop: :) +[Do Mär 6 2008] [21:02:31] or he didn't, but he's going to, any time soon :) +[Do Mär 6 2008] [21:03:01] Ok, anything else on the bump or 3.5.8 in the upcoming release? (Final call) +[Do Mär 6 2008] [21:03:31] Great. gentoofan23 already brought up topic 3 - Removal of KDE < 3.5.8 from the tree. :-) +[Do Mär 6 2008] [21:04:02] Ingmar kindly killed 3.5.5 to 3.5.7. So we don't have to worry about those anymore. :-) +[Do Mär 6 2008] [21:04:05] uh, I swear I didn't see that on the agenda. +[Do Mär 6 2008] [21:04:08] * gentoofan23 hides +[Do Mär 6 2008] [21:04:09] so that's done. next! :> +[Do Mär 6 2008] [21:05:04] Well, I guess since zlin has a hot date with a rubber doll, we should move on to topic 4 - State of KDE4 in the tree. ;-) +[Do Mär 6 2008] [21:05:24] Oo +[Do Mär 6 2008] [21:05:34] Ingmar, zlin: Let's hear - what's in the tree, when's 4.0.2 going in? :-) +[Do Mär 6 2008] [21:05:54] well, as such the ebuilds in the tree are in a pretty good state. the deps need to be updated for compatibility with the newly introduced split qt-4.4 ebuilds and it needs to be bumped to 4.0.2 (only kdebase and games have been bumped thus far)... +[Do Mär 6 2008] [21:05:54] Ingmar, zlin: And: What's the state of KDE 4.0.2 by your findings? :-) +[Do Mär 6 2008] [21:06:07] Well, some time this weekend, so far we've been busy with the newer Qt +[Do Mär 6 2008] [21:06:40] And the two of you did a great job with Qt, I'd say. :) +[Do Mär 6 2008] [21:06:43] honestly I haven't had a lot of time to use 4.0.2 yet.. but it'll come in the following days. +[Do Mär 6 2008] [21:06:48] Ingmar / zlin: Can I start working on kdenetwork? +[Do Mär 6 2008] [21:06:55] jmbsvicetto: certainly +[Do Mär 6 2008] [21:06:58] jmbsvicetto: Yes, please :) +[Do Mär 6 2008] [21:07:01] ok +[Do Mär 6 2008] [21:07:07] Do you want me to look at anything else? +[Do Mär 6 2008] [21:07:14] any help with bumping it will be appreciated +[Do Mär 6 2008] [21:07:46] eh, I'd help but amd64 AT's need a stable system. :( +[Do Mär 6 2008] [21:07:46] Right, and that goes for bug reports too :) +[Do Mär 6 2008] [21:07:51] I've updated my amd64 and x86 to 4.0.2 during the night, so I can start working on kdenetwork after the meeting +[Do Mär 6 2008] [21:08:11] maybe I'll be able to do it, but don't expect much :) +[Do Mär 6 2008] [21:08:27] s/do/help/ +[Do Mär 6 2008] [21:08:31] As for zlin's plea for help: Anyone who wants to help should simply mail me his ssh public key. Interested users who can show they're able and willing to work on ebuilds are *explicitly* invited, too. :-) +[Do Mär 6 2008] [21:09:29] The bump to 4.0.2 is taking place in a git overlay again to allow for non-ebuild devs to participate, too, and it's a great way to become a full dev as Ingmar and zlin can verify. :-) +[Do Mär 6 2008] [21:09:48] :) +[Do Mär 6 2008] [21:09:56] and as we want berniyh to do too! :> +[Do Mär 6 2008] [21:10:17] poor ignorants... they don't know it yet... *g* +[Do Mär 6 2008] [21:10:22] well, I might be able to help in places. I +[Do Mär 6 2008] [21:10:29] I'll e-mail my key +[Do Mär 6 2008] [21:10:46] gentoofan23: Ok, thanks, we'll work out the details later. +[Do Mär 6 2008] [21:11:14] Ok, anything else about KDE4 for now? +[Do Mär 6 2008] [21:12:03] just a question, what's the policy for things from playground/ going into gentoo-x86? +[Do Mär 6 2008] [21:12:26] various plasmoids come to mind. +[Do Mär 6 2008] [21:12:27] we can discuss that later +[Do Mär 6 2008] [21:12:29] It'd be wrong +[Do Mär 6 2008] [21:12:39] playground is what upstream doesn't consider release worthy +[Do Mär 6 2008] [21:12:45] alright. +[Do Mär 6 2008] [21:13:12] gentoofan23: We could have it in the overlay, though. :-) +[Do Mär 6 2008] [21:13:14] Meaning that it may work, but they won't support it +[Do Mär 6 2008] [21:13:18] definitely +[Do Mär 6 2008] [21:13:26] we already have a lot of it in the overlay +[Do Mär 6 2008] [21:13:29] Ok. +[Do Mär 6 2008] [21:13:40] Ingmar: They don't really support the other stuff either - see KDE 4.0.0. ;-> +[Do Mär 6 2008] [21:13:56] do we ? which cpv ? +[Do Mär 6 2008] [21:14:02] They just release it. Like Pandora did. ;-) +[Do Mär 6 2008] [21:14:05] Pfft, stop being a pansy and use 4.0.2 damnit +[Do Mär 6 2008] [21:14:36] Ok, anything else about KDE4 for now? (Final call.) +[Do Mär 6 2008] [21:14:41] orzelf: 6-8 packages... +[Do Mär 6 2008] [21:15:01] orzelf: Please ask about that in #genkdesvn. The guys there will help you. +[Do Mär 6 2008] [21:15:05] Most of the extragear things is really few work to package it btw +[Do Mär 6 2008] [21:15:59] oh, I might be confusing extragear and playground. maybe it's only a couple of packages then. ;) +[Do Mär 6 2008] [21:16:44] Ok, topic 5 - Herd Testers: Current state and next steps. jmbsvicetto, you're the one in charge with respect to that. :-) +[Do Mär 6 2008] [21:17:17] Well, I haven't done much yet. With the elections and a few other things, I was distracted +[Do Mär 6 2008] [21:17:31] However, the only person that as contacted me about HT was gentoofan23 +[Do Mär 6 2008] [21:17:40] jmbsvicetto: Yes, I know. You corrupted Neddy and four others. ;-) +[Do Mär 6 2008] [21:17:47] Philantrop: Has anyone else talked with you about it? +[Do Mär 6 2008] [21:17:57] Did you get berniyh's mail? :p +[Do Mär 6 2008] [21:18:05] jmbsvicetto: No, not so far. What we should +[Do Mär 6 2008] [21:18:17] jmbsvicetto: yeah, I was accepted by Philantrop as well. Haven't been doing much though +[Do Mär 6 2008] [21:18:17] hehe +[Do Mär 6 2008] [21:18:23] berniyh: Did you sent me an email? +[Do Mär 6 2008] [21:18:27] Ingmar: mail? +[Do Mär 6 2008] [21:18:33] jmbsvicetto: not that i know of ;) +[Do Mär 6 2008] [21:18:35] * do is flesh things a bit out, I think so that people know what we'd like to see done. :-) +[Do Mär 6 2008] [21:18:38] *none +[Do Mär 6 2008] [21:18:52] berniyh: ufff! :) +[Do Mär 6 2008] [21:19:01] jmbsvicetto: Don't worry, berniyh is worse a slacker than you are. ;-) +[Do Mär 6 2008] [21:19:11] hehe +[Do Mär 6 2008] [21:19:20] jmbsvicetto: maybe he meant that viagra thing? *g* +[Do Mär 6 2008] [21:19:32] Philantrop, zlin : ok ,thx. +[Do Mär 6 2008] [21:19:55] Philantrop: Agreed. We might also want to announce again that we're open for HTs and that people can help that way +[Do Mär 6 2008] [21:20:10] I can announce that on GMN +[Do Mär 6 2008] [21:20:11] Philantrop: We might want to push something to gmn and gentoo-pr +[Do Mär 6 2008] [21:20:18] shall I take note? +[Do Mär 6 2008] [21:20:21] berniyh: :) +[Do Mär 6 2008] [21:20:26] jmbsvicetto: Yes, good idea. We'll come to that in topic 8 - misc. :-) +[Do Mär 6 2008] [21:20:32] deathwing00: Yes, please. +[Do Mär 6 2008] [21:20:42] I can also "abuse" the forums for that ;) +[Do Mär 6 2008] [21:20:44] maybe have dberkholz put something on the front page? (as in not gmn) +[Do Mär 6 2008] [21:20:47] Philantrop: noted :) +[Do Mär 6 2008] [21:20:53] deathwing00: yes, please +[Do Mär 6 2008] [21:21:04] deathwing00, jmbsvicetto: Can you come up with a good text together? +[Do Mär 6 2008] [21:21:04] gentoofan23: that's gentoo-pr ;) +[Do Mär 6 2008] [21:21:11] Philantrop: sure thing +[Do Mär 6 2008] [21:21:16] Philantrop: I'll work with deathwing00 +[Do Mär 6 2008] [21:21:18] jmbsvicetto: oh, k +[Do Mär 6 2008] [21:21:26] jmbsvicetto: right after the meeting would be a good timing for me +[Do Mär 6 2008] [21:21:46] jmbsvicetto, deathwing00: Thanks, great! Once you're done, please mail it to kde@ so that we all can review it. Agreed? +[Do Mär 6 2008] [21:21:57] Philantrop: agreed +[Do Mär 6 2008] [21:21:58] deathwing00: If you could give me 30 minutes to have dinner, my stoamach would thank you ;) +[Do Mär 6 2008] [21:22:07] jmbsvicetto: no problem +[Do Mär 6 2008] [21:22:07] Philantrop: sure +[Do Mär 6 2008] [21:22:23] Philantrop: next ? +[Do Mär 6 2008] [21:22:29] Thanks! Anything else on HTs? +[Do Mär 6 2008] [21:22:50] other than the fact that I have no idea what to do, no ;-) +[Do Mär 6 2008] [21:23:07] gentoofan23: jmbsvicetto and deathwing00 will get you up to speed. *g* +[Do Mär 6 2008] [21:23:11] Philantrop: I don't think so. Not at this moment, at least +[Do Mär 6 2008] [21:23:18] Philantrop: :) +[Do Mär 6 2008] [21:23:34] Ok, anything else on HTs? (Final call.) +[Do Mär 6 2008] [21:23:54] Ok, let's move on to topic 6: +[Do Mär 6 2008] [21:23:56] 6. Lead election: +[Do Mär 6 2008] [21:23:56] During recent recruitments, DevRel informed us that the KDE project should have +[Do Mär 6 2008] [21:23:56] a lead as per GLEP39. Some herd members and other devs contacted Philantrop +[Do Mär 6 2008] [21:23:56] about it, too, and requested an election. A simple vote on IRC should be held. +[Do Mär 6 2008] [21:24:01] jmbsvicetto: I have to do forums threads as well btw +[Do Mär 6 2008] [21:24:09] ok +[Do Mär 6 2008] [21:24:35] Philantrop: I think it's about time we elect some leads +[Do Mär 6 2008] [21:25:14] jmbsvicetto: Yes, people asked me about that. As most of you know or can imagine, I volunteer. :-) +[Do Mär 6 2008] [21:25:22] Philantrop: That can help, by letting other people know who to talk to +[Do Mär 6 2008] [21:25:37] Philantrop: O'rly? ;) +[Do Mär 6 2008] [21:25:42] haha +[Do Mär 6 2008] [21:25:51] I second your nomination +[Do Mär 6 2008] [21:26:02] I even vote for Philantrop :) +[Do Mär 6 2008] [21:26:12] Philantrop++ +[Do Mär 6 2008] [21:26:13] Philantrop: I sugest we have 2 leads +[Do Mär 6 2008] [21:26:14] Same ;) +[Do Mär 6 2008] [21:26:27] jmbsvicetto: political power corrupting you? ;-) +[Do Mär 6 2008] [21:26:49] Philantrop: Whether we want an operation and a strategic lead or just a lead and sub-lead, it can help having a failsafe contact +[Do Mär 6 2008] [21:26:50] jmbsvicetto: why? +[Do Mär 6 2008] [21:26:50] I think jmbsvicetto means lead + sublead, as in former times +[Do Mär 6 2008] [21:27:03] gentoofan23: :) +[Do Mär 6 2008] [21:27:25] zlin: For the failsafe +[Do Mär 6 2008] [21:27:27] Philantrop: I think we concluded that we didn't want to split dutties (op + start), right? +[Do Mär 6 2008] [21:27:40] I don't think we need more than one lead, tbh +[Do Mär 6 2008] [21:27:52] 'dutties (op + start)'? +[Do Mär 6 2008] [21:28:04] op + strat* +[Do Mär 6 2008] [21:28:10] Some of us are more than active enough on irc, that there's always someone quick enough to answer KDE questions etc +[Do Mär 6 2008] [21:28:14] actually it's operation and technical +[Do Mär 6 2008] [21:28:14] Ingmar: What? You just want a lead and an HT lead? :o ;) +[Do Mär 6 2008] [21:28:16] ahh, and duties. ;) +[Do Mär 6 2008] [21:28:34] zlin: my bad :) +[Do Mär 6 2008] [21:28:58] I propose to vote if we want to have a sublead first, then vote for candidates +[Do Mär 6 2008] [21:29:03] I'm with Ingmar on this - the students among us are around anyway. ;-) +[Do Mär 6 2008] [21:29:45] I'm with Ingmar on this too. +[Do Mär 6 2008] [21:29:46] zlin: The principle behind the strategic + operational lead, was to have someone concerned with the big picture and another person taking care of the day-to-day +[Do Mär 6 2008] [21:30:14] jmbsvicetto: We all take care of day-to-day stuff. :-) +[Do Mär 6 2008] [21:30:16] Yes, and my point is that day-to-day is more than taken care of +[Do Mär 6 2008] [21:30:23] ok +[Do Mär 6 2008] [21:30:35] If you're happy with just a lead, then I accept that +[Do Mär 6 2008] [21:30:39] Let's vote on the sub-lead, I'd say. Yay/Nay, please. +[Do Mär 6 2008] [21:30:45] not that we can't improve in that, but I don't see a problem, and I don't see your suggestion as a solution ;) +[Do Mär 6 2008] [21:30:48] Nay +[Do Mär 6 2008] [21:30:49] I've already seconded a nomination ;) +[Do Mär 6 2008] [21:30:49] Yay +[Do Mär 6 2008] [21:30:51] * Philantrop votes nay +[Do Mär 6 2008] [21:30:54] Nay +[Do Mär 6 2008] [21:31:02] Yay +[Do Mär 6 2008] [21:31:17] * cryos|laptop abstains +[Do Mär 6 2008] [21:31:17] 2 Yay - 3 Nay ? +[Do Mär 6 2008] [21:31:22] ctennis: ^^ +[Do Mär 6 2008] [21:31:30] masterdriverz: ^^ +[Do Mär 6 2008] [21:31:31] hehe +[Do Mär 6 2008] [21:31:34] * gentoofan23 isn't sure if he can vote... +[Do Mär 6 2008] [21:31:42] You can, if you say nay +[Do Mär 6 2008] [21:31:43] gentoofan23: go on +[Do Mär 6 2008] [21:31:47] Ingmar: lol +[Do Mär 6 2008] [21:31:54] nay then +[Do Mär 6 2008] [21:32:02] haha +[Do Mär 6 2008] [21:32:16] I guess, nay passes then +[Do Mär 6 2008] [21:32:21] honestly, that *was* my opinion :) +[Do Mär 6 2008] [21:32:43] :p +[Do Mär 6 2008] [21:33:02] so, do we want Philantrop as lead? Yay/Nay? +[Do Mär 6 2008] [21:33:04] Yay +[Do Mär 6 2008] [21:33:05] yay +[Do Mär 6 2008] [21:33:09] Yay +[Do Mär 6 2008] [21:33:10] yay above too +[Do Mär 6 2008] [21:33:12] yay +[Do Mär 6 2008] [21:33:13] yay +[Do Mär 6 2008] [21:33:15] yay +[Do Mär 6 2008] [21:33:24] Philantrop: To do it the right way, we should open a nomination period and then have a voting period +[Do Mär 6 2008] [21:33:39] why are we even voting if there is only one nominee? *g* +[Do Mär 6 2008] [21:33:53] ok, if anyone feels comfortable with that, Yay +[Do Mär 6 2008] [21:33:58] gentoofan23: well, if over 50% goes nay, then we have to elect someone else +[Do Mär 6 2008] [21:34:08] If there're any other nominees, I'd suggest them to stand up :) +[Do Mär 6 2008] [21:34:20] Else Idon't see the point of an election, waste of time :) +[Do Mär 6 2008] [21:34:29] oh, I guess I was likening it to a political election. +[Do Mär 6 2008] [21:34:29] Ingmar: tell devrel +[Do Mär 6 2008] [21:35:07] Philantrop: the sublead thing is 3y - 4n +[Do Mär 6 2008] [21:35:07] So, other candidates? +[Do Mär 6 2008] [21:35:11] this isn't a political election. we just need the whole team to be comfortable with the chosen lead +[Do Mär 6 2008] [21:35:31] zlin: right :) +[Do Mär 6 2008] [21:35:54] Philantrop: This is another good reason to get gmn and gentoo-pr +[Do Mär 6 2008] [21:36:05] ? +[Do Mär 6 2008] [21:36:17] Philantrop: Let people know about our new lead and remind them of kde HTs +[Do Mär 6 2008] [21:36:29] Philantrop: ^ +[Do Mär 6 2008] [21:36:35] bah, deathwing00 ^ +[Do Mär 6 2008] [21:36:35] jmbsvicetto: Yes, a sec. :-) +[Do Mär 6 2008] [21:36:37] Philantrop: u sure you don't want jmbsvicetto as your sublead? +[Do Mär 6 2008] [21:36:46] jmbsvicetto: noted +[Do Mär 6 2008] [21:36:51] deathwing00: Thanks, but I'm not interested +[Do Mär 6 2008] [21:37:03] deathwing00: If we were to have a sub-lead, I had another in mind +[Do Mär 6 2008] [21:37:25] deathwing00: Well, let's keep things simple - everyone here can still make decisions so you're all sub-leads, IMHO. :) +[Do Mär 6 2008] [21:37:35] hehe +[Do Mär 6 2008] [21:38:17] For verification: sublead vote: 3 "yays", 3 "nays", one abstention, right? +[Do Mär 6 2008] [21:38:19] Philantrop: can you give me the vote counts on sublead y/n/a and lead election y/n/a? +[Do Mär 6 2008] [21:38:23] wheeeeeeeee! I'm one of the 10+ gentoo-kde executive vps^D^D^Dsub-leads ;) +[Do Mär 6 2008] [21:38:24] dooooooork +[Do Mär 6 2008] [21:38:37] jeeves: :P +[Do Mär 6 2008] [21:38:53] lead election: 7 yays, no nays, no abstention. +[Do Mär 6 2008] [21:39:04] noted +[Do Mär 6 2008] [21:39:17] sublead is a deadlock then? +[Do Mär 6 2008] [21:39:44] let's make it a 3 yays and 4 nays then :) +[Do Mär 6 2008] [21:40:04] noted +[Do Mär 6 2008] [21:40:08] ok +[Do Mär 6 2008] [21:40:15] tgurr: I need your vote on Philantrop :) +[Do Mär 6 2008] [21:40:32] yay for this wulf thing ;) +[Do Mär 6 2008] [21:40:42] done with that +[Do Mär 6 2008] [21:41:02] Philantrop: you have been elected as KDE lead, my congratulations +[Do Mär 6 2008] [21:41:13] Philantrop: copy-paste your speech here +[Do Mär 6 2008] [21:41:14] Thanks, guys. :-) +[Do Mär 6 2008] [21:41:17] * deathwing00 grins +[Do Mär 6 2008] [21:41:44] I have no speech and I don't want to waste your time so just let me thank my grand-parents, my parents, my wife, my children, my pet... ;-) +[Do Mär 6 2008] [21:41:54] ;-)) +[Do Mär 6 2008] [21:41:58] next issue +[Do Mär 6 2008] [21:42:10] Topic 7 - Review of the project page. +[Do Mär 6 2008] [21:42:28] Apart from the lead thing - what do we need to update=? +[Do Mär 6 2008] [21:42:37] kde-pr could take care of it if you want +[Do Mär 6 2008] [21:42:40] lots of kde 3.5.7 stuff. +[Do Mär 6 2008] [21:42:47] stable version + testing version and status of kde4 +[Do Mär 6 2008] [21:42:52] I have a cvs checkout here, I could update things to a semi-sane state +[Do Mär 6 2008] [21:43:14] That'd be nice +[Do Mär 6 2008] [21:43:16] kde-pr? +[Do Mär 6 2008] [21:43:36] kde-pr: just invented subproject +[Do Mär 6 2008] [21:43:47] gentoofan23, deathwing00: How about the two of you do it together? +[Do Mär 6 2008] [21:43:49] who volunteered? :> +[Do Mär 6 2008] [21:44:12] yeah, I am already asuming these duties +[Do Mär 6 2008] [21:44:15] deathwing00: that means you are an indirect sublead :) +[Do Mär 6 2008] [21:44:24] gentoofan23: you mean a monkey +[Do Mär 6 2008] [21:44:40] hehe +[Do Mär 6 2008] [21:44:44] deathwing00: well, the two can be related :) +[Do Mär 6 2008] [21:44:55] * cryos|laptop has to go - duty calls +[Do Mär 6 2008] [21:45:00] Congrats Philantrop :D +[Do Mär 6 2008] [21:45:02] gentoofan23, deathwing00: Can I take that for a "yes"? +[Do Mär 6 2008] [21:45:07] cryos|laptop: laters :) +[Do Mär 6 2008] [21:45:12] cryos|laptop: Thanks and thanks for having been here! +[Do Mär 6 2008] [21:45:15] Philantrop: sure. ;) +[Do Mär 6 2008] [21:45:33] Philantrop: affirmative, I'll take care of everything that needs to be spread to the public opinion everyone likes, with the help of everyone who likes +[Do Mär 6 2008] [21:45:46] gentoofan23, deathwing00: Can you do it till the next meeting (next month)? +[Do Mär 6 2008] [21:45:51] cryos|laptop: thank you for sparing your time :) +[Do Mär 6 2008] [21:46:18] Philantrop: when is the next meeting? tomorrow? +[Do Mär 6 2008] [21:46:28] deathwing00: next month. :-) +[Do Mär 6 2008] [21:46:32] Philantrop: probably. +[Do Mär 6 2008] [21:46:38] I already am editing a few things. +[Do Mär 6 2008] [21:46:49] will do +[Do Mär 6 2008] [21:46:55] I'll send any patches to kde@ for review +[Do Mär 6 2008] [21:47:04] Philantrop: What are we missing? +[Do Mär 6 2008] [21:47:21] gentoofan23, deathwing00: Ok, thanks! :-) And, yes, please, mail it to kde@. +[Do Mär 6 2008] [21:47:25] Philantrop: I'm being poked to have dinner +[Do Mär 6 2008] [21:47:44] jmbsvicetto: Missing? And poked by whom? :-) +[Do Mär 6 2008] [21:47:46] jmbsvicetto: meet you here in 35 minutes +[Do Mär 6 2008] [21:48:04] Philantrop: What other points? I'm at my parents house +[Do Mär 6 2008] [21:48:14] gentoofan23: can we have talk about it after the meeting? +[Do Mär 6 2008] [21:48:18] jmbsvicetto: Misc and next meeting date. :-) +[Do Mär 6 2008] [21:48:29] deathwing00: uh, maybe. I might have to go after the meeting though +[Do Mär 6 2008] [21:48:32] jmbsvicetto: Nothing very special, I think. :-) +[Do Mär 6 2008] [21:48:37] ok +[Do Mär 6 2008] [21:48:42] Quit orzelf has left this server (Remote closed the connection). +[Do Mär 6 2008] [21:48:51] I'll try to poke in a few minutes +[Do Mär 6 2008] [21:49:25] deathwing00, gentoofan23: 3, 4, 8, 9 of kde.gentoo.org need to updated, I think. :-) +[Do Mär 6 2008] [21:49:43] Philantrop: noted +[Do Mär 6 2008] [21:49:46] what do you mean by all those numbers? +[Do Mär 6 2008] [21:49:54] gentoofan23: The headlines. :-) +[Do Mär 6 2008] [21:50:01] oh, noted +[Do Mär 6 2008] [21:50:16] Ok, anything else about the project page? +[Do Mär 6 2008] [21:50:31] and of course we are here if you need additional info to write it... :) +[Do Mär 6 2008] [21:51:00] just a reminder to someone with cvs access to update proj/en/desktop/ with Philantrop as the Lead of the KDE project +[Do Mär 6 2008] [21:51:12] should be a one-liner +[Do Mär 6 2008] [21:51:20] zlin: noted, thanks! +[Do Mär 6 2008] [21:51:42] Anything else about the project page? (Final call.) +[Do Mär 6 2008] [21:51:56] zlin: :) +[Do Mär 6 2008] [21:52:11] Topic 8 - Miscellaneous +[Do Mär 6 2008] [21:52:14] gentoofan23: write a paragraph, then it looks like it is important ;) +[Do Mär 6 2008] [21:52:33] Anyone with anything to bring up? +[Do Mär 6 2008] [21:53:18] Ok, I have one point - as he hinted at earlier, deathwing00 kindly volunteered to help with spreading the news about the Gentoo KDE project. I'd like to take up this offer. :-) +[Do Mär 6 2008] [21:53:25] oh +[Do Mär 6 2008] [21:53:25] oh, what about #5 in index.xml? what is the status on monthly meetings? +[Do Mär 6 2008] [21:53:28] let me interrupt +[Do Mär 6 2008] [21:54:01] Philantrop: gentoofan23 made me notice that we could create a new section about meetings, with dates, sumary and logs +[Do Mär 6 2008] [21:54:02] gentoofan23: We'll resume that. :-) +[Do Mär 6 2008] [21:54:33] kde herd meeting? +[Do Mär 6 2008] [21:54:33] summary* +[Do Mär 6 2008] [21:54:33] deathwing00: Yes, we should updated section 5. I'd like to have monthly meetings again. +[Do Mär 6 2008] [21:54:34] ;-) +[Do Mär 6 2008] [21:54:40] genstef: Welcome! :-) +[Do Mär 6 2008] [21:54:41] right. +[Do Mär 6 2008] [21:54:45] hi genstef +[Do Mär 6 2008] [21:55:04] Philantrop: noted :) +[Do Mär 6 2008] [21:55:15] Anything else for topic 8 - Miscellaneous? +[Do Mär 6 2008] [21:55:25] one thing to note is that the first saturday of every month is Bugday, not sure if that will make any conflicts. +[Do Mär 6 2008] [21:55:34] bugday is dead +[Do Mär 6 2008] [21:55:47] eroyf: don't blame me plz :) +[Do Mär 6 2008] [21:55:52] not your fault +[Do Mär 6 2008] [21:55:58] gentoofan23: Oh, right, most people turned out to have no time during the weekend. What's best for everyone here? +[Do Mär 6 2008] [21:55:59] more my fault +[Do Mär 6 2008] [21:56:13] Philantrop: why not like today? +[Do Mär 6 2008] [21:56:16] Is Thursday good for everyone? +[Do Mär 6 2008] [21:56:23] Well, it is probably best for me +[Do Mär 6 2008] [21:56:29] Sundays are not very good +[Do Mär 6 2008] [21:56:41] Thursday afternoons are good, usually +[Do Mär 6 2008] [21:57:14] I like Thursdays, too. :-) +[Do Mär 6 2008] [21:57:38] thursday is great +[Do Mär 6 2008] [21:57:49] Anyone *against* (!) choosing Thursday? +[Do Mär 6 2008] [21:57:53] I prefer thursday over friday at least +[Do Mär 6 2008] [21:58:13] * Philantrop hums "It's just another manic Thursday"... ;-) +[Do Mär 6 2008] [21:58:18] anyone for Mondays? *g* +[Do Mär 6 2008] [21:58:33] Thursday it is. :-) +[Do Mär 6 2008] [21:58:44] PR: noted +[Do Mär 6 2008] [21:58:52] Second one, I'd say. Objections? +[Do Mär 6 2008] [21:59:07] first thursday of every month +[Do Mär 6 2008] [21:59:31] Ok, first. Objections? +[Do Mär 6 2008] [21:59:42] Perfect. *g* Anything else for topic 8 - Miscellaneous? +[Do Mär 6 2008] [22:00:07] can we go now? there's so much to do... *g* +[Do Mär 6 2008] [22:00:12] btw, I am at Cebit tomorrow :-) +[Do Mär 6 2008] [22:00:17] Join zsz has joined this channel (n=zsz@sa-184-64.saturn.infonet.ee). +[Do Mär 6 2008] [22:00:18] Ok, guys, final topic - Date of the next meeting and closing. +[Do Mär 6 2008] [22:00:19] well, I'm out, later everyone +[Do Mär 6 2008] [22:00:19] eh on the weekend +[Do Mär 6 2008] [22:00:21] second thursday is council meetings. not sure if that's a pro or a con though. :> +[Do Mär 6 2008] [22:00:24] Congrats, Philantrop +[Do Mär 6 2008] [22:00:40] zlin: Oh, right. Then it's really first. :-) +[Do Mär 6 2008] [22:00:52] yes +[Do Mär 6 2008] [22:00:57] gentoofan23: goodbye :-) +[Do Mär 6 2008] [22:01:04] Last topic: Date of the next meeting and closing. +[Do Mär 6 2008] [22:01:11] Quit gentoofan23 has left this server (Client Quit). +[Do Mär 6 2008] [22:01:16] April, 3rd, 2008. +[Do Mär 6 2008] [22:01:30] * zlin acks +[Do Mär 6 2008] [22:01:33] noted +[Do Mär 6 2008] [22:01:43] :) +[Do Mär 6 2008] [22:01:44] Anything else, guys? :-) +[Do Mär 6 2008] [22:01:50] Topic Ingmar sets the channel topic to "KDE 4.0 guide: http://tinyurl.com/27tbt5 | KDE herd meeting (april 3rd, 2008, 19:30 UTC, here). Agenda: http://tinyurl.com/2hhsvc | Problems upgrading to stable KDE 3.5.8? http://tinyurl.com/yqk4le | http://dev.gentoo.org/~masterdriverz/kde-help.txt | KDE Bugs: http://tinyurl.com/3bpdlv | If we're too quiet try #kde | KDE4 live ebuilds? -> "kde" overlay and #genkdesvn. | KDE 4 doesn't work with qt-4.4 *yet*". +[Do Mär 6 2008] [22:01:51] yes. +[Do Mär 6 2008] [22:02:05] you missed to say that you all are doing a great job. +[Do Mär 6 2008] [22:02:26] Hats off to the qt4 beta1 folks +[Do Mär 6 2008] [22:02:38] No, that's closing and that's what I'm doing now: Thanks for all your great work, guys! It's a great pleasure to work with you! :-) +[Do Mär 6 2008] [22:03:00] ctennis: you mean "heads off" ;-) +[Do Mär 6 2008] [22:03:08] that too! +[Do Mär 6 2008] [22:03:33] Quit mark_alec has left this server ("Konversation terminated!"). +[Do Mär 6 2008] [22:03:35] ctennis: And it's nice to have one of the grumpy old men back on IRC. ;-) +[Do Mär 6 2008] [22:03:47] :) +[Do Mär 6 2008] [22:03:58] heh +[Do Mär 6 2008] [22:04:07] I wish I had more time to play +[Do Mär 6 2008] [22:04:28] but it seems like there's no problem in picking up my slack +[Do Mär 6 2008] [22:04:34] :) +[Do Mär 6 2008] [22:04:34] Ok, guys, this meeting is now officially closed! :-) +[Do Mär 6 2008] [22:04:46] * deathwing00 cheers at the new lead +[Do Mär 6 2008] [22:04:56] ctennis: with qt-4.4? +[Do Mär 6 2008] [22:04:57] ctennis: :) +[Do Mär 6 2008] [22:04:58] ctennis: Oh, you should have seen Ingmar and zlin swear about Qt's build system sometimes... ;-) +[Do Mär 6 2008] [22:05:11] * berniyh nods +[Do Mär 6 2008] [22:05:13] we're still swearing.. ;) +[Do Mär 6 2008] [22:05:23] I'll mail the log and summary to kde@. :-) +[Do Mär 6 2008] [22:05:46] Philantrop: I'll reuse it :) +[Do Mär 6 2008] [22:06:04] deathwing00: That was my dark intention. :-) +[Do Mär 6 2008] [22:06:21] :) +[Do Mär 6 2008] [22:07:04] okay, zlin forced me to say that I vote for philantrop and against a sub-lead +[Do Mär 6 2008] [22:07:37] LOL +[Do Mär 6 2008] [22:07:37] err +[Do Mär 6 2008] [22:07:44] s/.*I vote/I vote/ +[Do Mär 6 2008] [22:07:52] keytoaster: noted +[Do Mär 6 2008] [22:09:35] ehrm, when will the 4.0.2 ebuilds be in portage ? +[Do Mär 6 2008] [22:09:44] Philantrop: I'll post the most interesting things on our forums btw :) +[Do Mär 6 2008] [22:09:49] * brot ducks +[Do Mär 6 2008] [22:10:09] deathwing00: Thanks! :-) Please let me know the link. :-) diff --git a/meeting-logs/20081204-summary.txt b/meeting-logs/20081204-summary.txt new file mode 100644 index 0000000..8f86331 --- /dev/null +++ b/meeting-logs/20081204-summary.txt @@ -0,0 +1,31 @@ +kde3: + cryos and tampakrap are willing to handle its dying. Their priority should be stabilising 3.5.10 and making it live along 4.X. +kde4-eclasses: + currently in reviewing + Jmbsvicetto and krytzz promised helping me up with testing get_latest_kdedir. + Moving htmlhandbook to eclass? jmbsvicetto/scarabeus + fix remaining tree ebuild so they use NEED_KDE="version" and not NEED_KDE="slot" scarabeus will do it. + only eapi2 and greater in eclass: jmbsvicetto will look on this one. +kde4: + try to push versioning in one prefix into upstream. It will be bliss for maintaining. cryos (on kde camp :P) +people-in-team: + write mail to all whom are mentioned on project page and not active to determine their current status. :( + jmbsvicetto willing to do this. +qt4: + yngwin is currently only qt dev, he should get some help, reavertm volunteer (see HT guys are useful :]) +tampakrap: + getting his ebuild-quiz done i scarabeus am willing to help. Yngwin as mentor. +kde-crazy: + snapshots: tampakrap, alexxy, patrick; state: somehow working + live: sput, krytzz, reavertm; state: well live ;] +networkmanager: + scarabeus will ask rbu if he need some help with this vital part of kde4.2 networking. +mysql: + cooperate with robbat2 since kde4.2 and amarok are dead without it. Jmbsvicetto volunteer to help robbat2 so lets se what will be outcome from this. + +:::LONG TERM::: +kde-look/apps: + maybe create some generator for those apps, take look onto app-portage/g-cpan how perl mages do it. +bugwranglers: + reavertm, proposal about letting normal users to wrangle our bugs, most of them are needinfo or already closed so let users help us. + Maybe some wrangler-quiz.txt will be needed. \ No newline at end of file diff --git a/meeting-logs/20081204.txt b/meeting-logs/20081204.txt new file mode 100644 index 0000000..e4c2b60 --- /dev/null +++ b/meeting-logs/20081204.txt @@ -0,0 +1,641 @@ +2008 Dec 04 20:01:04 http://dev.gentoo.org/~scarabeus/kde_meeting0812.txt +2008 Dec 04 20:01:11 time is here +2008 Dec 04 20:01:13 so who is around? +2008 Dec 04 20:01:23 -*- tampakrap +2008 Dec 04 20:01:26 -*- bonsaikitten +2008 Dec 04 20:01:43 !herd kde +2008 Dec 04 20:01:44 (kde) caleb, carlo, cryos, deathwing00, genstef, jmbsvicetto, keytoaster, mattepiu, scarabeus, tgurr +2008 Dec 04 20:01:54 guys you should all show up :] +2008 Dec 04 20:01:54 -*- krytzz +2008 Dec 04 20:02:01 hi there! +2008 Dec 04 20:02:22 -*- jmbsvicetto +2008 Dec 04 20:02:40 krytzz, Sput: you two around? +2008 Dec 04 20:02:42 -*- cryos|work is here +2008 Dec 04 20:02:49 yes +2008 Dec 04 20:03:20 ok i think that is most we can get, any words from others, stating that they show up too? +2008 Dec 04 20:03:35 scarabeus: No idea +2008 Dec 04 20:03:49 I guess we should let their backlog do its work ;) +2008 Dec 04 20:04:02 scarabeus: About your agenda, we should start with a "simple" point - who is still working / willing to work with KDE 3.5 +2008 Dec 04 20:04:10 me +2008 Dec 04 20:04:15 bonsaikitten: That doesn't work with caleb and carlo ;) +2008 Dec 04 20:04:28 I am somewhat, but with limited time... +2008 Dec 04 20:04:31 as long as it is only ebuild maintenance and not C++ stabbing I'm willing to keep it alive +2008 Dec 04 20:04:41 but I have no interest in 3.5 anymore :) +2008 Dec 04 20:04:48 i said i still use kde3 in my main desktop and wanted to have various tests about that and check bugs of course +2008 Dec 04 20:04:54 but i was busy with the quiz +2008 Dec 04 20:04:55 -*- cryos|work has waning interest in it... +2008 Dec 04 20:05:18 our users want it, so those primitives have to be kept happy ;) +2008 Dec 04 20:05:41 yes i would say it is requirement to have kde3 around until kde4.3 +2008 Dec 04 20:05:42 --> MartyMcFly (n=martin@dslb-088-064-190-153.pools.arcor-ip.net) has joined #gentoo-kde +2008 Dec 04 20:06:00 maybe even longer. if 3.5 is stable enough maintenance should be cheap +2008 Dec 04 20:06:01 yes +2008 Dec 04 20:06:03 I'm not saying we should drop 3.5, I'm asking who is willing to keep it alive ;) +2008 Dec 04 20:06:05 Quite probably, but it is essentially dead upstream. +2008 Dec 04 20:06:07 jkt|: maybe you will be interested in this too +2008 Dec 04 20:06:20 -=- hwoarang is now known as hwo[a]rang +2008 Dec 04 20:06:25 I will do what I can to help. +2008 Dec 04 20:06:28 Also, who is willing to work on the issues caused by the mixing of 3.5 with 4 +2008 Dec 04 20:06:44 me :) +2008 Dec 04 20:06:44 I have noted many distros already dropping it in new releases. Just keeping unported apps around. +2008 Dec 04 20:07:08 cryos|work: people would hate us, kde4 is not yet ready, even i miss some features +2008 Dec 04 20:07:10 I guess all of us will be hybrid users as noone goes back to a 3.5 desktop anymore :) +2008 Dec 04 20:07:16 I will help when I can, I think I may have neglected to pick up all the pieces... +2008 Dec 04 20:07:34 --> reavertm (n=maciek@bcv18.neoplus.adsl.tpnet.pl) has joined #gentoo-kde +2008 Dec 04 20:07:34 cryos|work: life happened. don't beat yourself up for that :) +2008 Dec 04 20:07:48 scarabeus: I am not talking about dropping it, I am however pointing out the deadness of upstream in that sense and what other distros are tending to do. +2008 Dec 04 20:08:08 i understand. +2008 Dec 04 20:08:12 Thanks bonsaikitten ;-) +2008 Dec 04 20:08:13 (if I'm out again it means my hardware is failing again, don't bother) +2008 Dec 04 20:08:17 <-- duog (n=doug@78-86-178-196.zone2.bethere.co.uk) has quit (Remote closed the connection) +2008 Dec 04 20:08:22 We should keep an eye on what is happening elsewhere. +2008 Dec 04 20:08:22 -=- Mode #gentoo-kde [+v reavertm] by scarabeus +2008 Dec 04 20:08:35 so we'll keep it alive, but there's a good chance we won't give it high priority +2008 Dec 04 20:09:03 agreed, on low priority i think we can handle this, and we should be closing up enhancement request for kde3 +2008 Dec 04 20:09:10 since it would be just pointless work +2008 Dec 04 20:09:24 <-- hvengel (n=hvengel@astound-66-234-194-11.ca.astound.net) has quit (Read error: 110 (Connection timed out)) +2008 Dec 04 20:09:42 mostly agree +2008 Dec 04 20:09:53 kde page stated along with some kde4 release announcement: "Don't look back" :) +2008 Dec 04 20:09:55 after all kde4.2 is close and will be stable enough +2008 Dec 04 20:10:31 ok so lets mark kde3 as work for cryos and tampakrap, i think you two can talk out what is needed on that field +2008 Dec 04 20:10:38 anyone else willing to jump on kde3? +2008 Dec 04 20:10:57 i don't think we need more people +2008 Dec 04 20:11:05 let's focus on kde4 "the future" +2008 Dec 04 20:11:09 cryos|work: Yes, a dead upstream (3.5) and their lack of work to keep more than one version around are the most important cause of the open bugs - imho +2008 Dec 04 20:11:43 <-- St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has quit ("http://quassel-irc.org - Chat comfortably. Anywhere.") +2008 Dec 04 20:11:49 jmbsvicetto: Certainly, and so the distros are forced to move along with them unless they have considerable resources. +2008 Dec 04 20:11:55 --> St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has joined #gentoo-kde +2008 Dec 04 20:12:01 well, upstream simply has no manpower to maintaint both +2008 Dec 04 20:12:07 cryos|work: never underestimate gentoo users ;) +2008 Dec 04 20:12:07 There was some talk of a distro maintained patch set but I haven't seen mention of it recently. +2008 Dec 04 20:12:24 cryos|work: ask arch linux team +2008 Dec 04 20:12:25 cryos|work: For 3.5? +2008 Dec 04 20:12:31 they have probably best kde3 team around +2008 Dec 04 20:12:33 currently +2008 Dec 04 20:12:43 their kdemod is epic +2008 Dec 04 20:13:06 htmlhandbook provides whole help or only some additional files? +2008 Dec 04 20:13:20 St_MPA3b: whole help +2008 Dec 04 20:13:33 scarabeus: thanks +2008 Dec 04 20:13:55 scarabeus: talking about htmlhandbook, I ended up not moving it away from ebuilds and into the eclass :\ +2008 Dec 04 20:13:57 scarabeus: and there are currently no file collisions if htmlhandbook is turned off? +2008 Dec 04 20:15:11 in @kde-live +2008 Dec 04 20:15:30 jmbsvicetto: well that goes for next point of meeting +2008 Dec 04 20:15:33 kde4 eclasses +2008 Dec 04 20:15:40 i heavily rewrote them +2008 Dec 04 20:15:48 applied some suggestions from jmbsvicetto +2008 Dec 04 20:15:53 (again?) +2008 Dec 04 20:15:55 --> breiti (n=breiti@p5DD69917.dip0.t-ipconnect.de) has joined #gentoo-kde +2008 Dec 04 20:15:57 any moar points to them +2008 Dec 04 20:16:04 when there will be commit? +2008 Dec 04 20:16:13 reavertm: they are still the same, it was not yet accepted. +2008 Dec 04 20:16:52 So what are the main changes made? +2008 Dec 04 20:17:12 mostly we allow dynamic detection for kde4 +2008 Dec 04 20:17:23 so apps can work with kde4.1 and kde4.2 and live +2008 Dec 04 20:17:25 no matter what +2008 Dec 04 20:17:32 nice +2008 Dec 04 20:17:32 eclasses handles all deps correctly +2008 Dec 04 20:17:40 also i removed most of not required code +2008 Dec 04 20:17:41 Which one are they linking too/building against? +2008 Dec 04 20:17:45 This is a bad thing(tm) in design, but I don't have a better alternative +2008 Dec 04 20:18:21 cryos|work: well now you can specify which kde it needs as minimal and then specify search order for other kde versions +2008 Dec 04 20:18:26 basicly it preffers -kdeprefix +2008 Dec 04 20:18:34 (actually one guy had problems with updating from 4.1.2 to 4.1.3 with -kdeprefix using portage eclasses and kde-crazy ones didn't help +2008 Dec 04 20:18:45 If they build/link against the latest version installed, they may not link to an earlier version, if it builds against old that doesn't have new symbols it won't compile. +2008 Dec 04 20:18:46 it may still need some checks +2008 Dec 04 20:19:12 cryos|work: that all can be ebuld specified +2008 Dec 04 20:19:21 <-- mx-tvt (n=costa@175.230.54.77.rev.vodafone.pt) has quit (Remote closed the connection) +2008 Dec 04 20:19:23 That is why I have always erred on the side of saying this is possible but a support nightmare. +2008 Dec 04 20:19:37 reavertm: he had fucked up kdesvn eclasses i guess, since we used that slot loong ago +2008 Dec 04 20:19:41 If it seems to work that is great though. +2008 Dec 04 20:19:55 yeah it works for all overlay guys +2008 Dec 04 20:20:06 and also my eclass supports koffice +2008 Dec 04 20:20:07 I think in general they should build/link against oldest installed version that satisfies the deps. +2008 Dec 04 20:20:13 which i can maintain with bonsaikittens help +2008 Dec 04 20:20:17 if he is still interested +2008 Dec 04 20:20:19 If KDE devs did their job well it will link to the latest version. +2008 Dec 04 20:20:21 koffice2 +2008 Dec 04 20:20:41 i could help there too a little bit +2008 Dec 04 20:20:41 cryos|work: that is default behavior +2008 Dec 04 20:20:42 So if we are planning on supporting it that should be the default behaviour. +2008 Dec 04 20:20:52 That sounds good to me then. +2008 Dec 04 20:21:00 scarabeus: There are a few things about get_latest_kdedir. That function shouldn't have hardcoded version strings - they should instead be defined in a var like KDE_SLOTS +2008 Dec 04 20:21:02 but dev can specify other order in ebuild +2008 Dec 04 20:21:31 OK, but I would discourage them from doing that unless they have an amazing reason to do so. +2008 Dec 04 20:21:33 jmbsvicetto: well enjoy its updating :] i will be hapy to see help from others :], i have no idea how to use it best, so i did it this way +2008 Dec 04 20:21:50 cryos|work: all written in comments for those variables +2008 Dec 04 20:21:56 scarabeus: Yeah, I'll see what I can do about it +2008 Dec 04 20:22:52 Sounds fine, we just need to stick to some policies for in tree stuff at least. +2008 Dec 04 20:23:08 scarabeus / cryos|work: Most of the issues that we're having (besides the linking to a versioned dir) is that upstream is breaking ABI continuously for KDE4, right? +2008 Dec 04 20:23:09 i use it for in tree stuff just fine +2008 Dec 04 20:23:14 --> NSaibot (n=quassel@i3ED6C704.versanet.de) has joined #gentoo-kde +2008 Dec 04 20:23:18 jmbsvicetto: right +2008 Dec 04 20:23:33 <-- NSaibot (n=quassel@i3ED6C704.versanet.de) has quit (Remote closed the connection) +2008 Dec 04 20:23:46 cryos|work: i will run some test tomorow and fix all remaining compatibility problems +2008 Dec 04 20:24:10 jmbsvicetto: Yeah, but they promised not to after 4.1. I guess they are failing... +2008 Dec 04 20:24:23 --> non7top (n=non7top@77.66.156.160) has joined #gentoo-kde +2008 Dec 04 20:24:25 Oh, an important point about the eclasses - are we ready to block kde4 eclasses for EAPI-0 and EAPI-1? +2008 Dec 04 20:24:30 I am talking at Camp KDE 2009 too - KDE and Gentoo. +2008 Dec 04 20:24:43 cool ^^ +2008 Dec 04 20:24:47 i volte for only eapi2 +2008 Dec 04 20:24:54 --> NSaibot (n=quassel@i3ED6C704.versanet.de) has joined #gentoo-kde +2008 Dec 04 20:24:57 scarabeus: EAPI-2 or later ;) +2008 Dec 04 20:25:00 yes +2008 Dec 04 20:25:39 Can we block change the EAPI on an existing in tree e-class? Don't we need to maintain backwards compatibility on eclasses? +2008 Dec 04 20:26:08 That is a question as I can't remember what the policy is. +2008 Dec 04 20:26:09 cryos|work: well packages will be broken if they use eapi lower than 2 and our eclass even currently +2008 Dec 04 20:26:13 so we should block it +2008 Dec 04 20:26:24 That would allow us to drop the QT4_BUILT_WITH_USE_CHECK, KDE4_BUILT_WITH_USE_CHECK and friends +2008 Dec 04 20:26:33 <-- fedux (n=fedux@host157.190-137-19.telecom.net.ar) has quit ("Saliendo") +2008 Dec 04 20:26:57 cryos|work: I'll confirm it with zmedico, but iirc the eclasses are now saved to vdb +2008 Dec 04 20:27:13 I am just not certain we can do that, but I could be wrong. An eclass that used to work with a version of portage should at least work to uninstall said ebuild. +2008 Dec 04 20:27:14 and no eapi1 package currently uses our eclass +2008 Dec 04 20:27:38 If the policy has changed due to portage changes then fine, but last I checked it had not. +2008 Dec 04 20:27:47 cryos|work: I'll be sure to check it +2008 Dec 04 20:27:50 You could leave empty functions there, but they had to remain there. +2008 Dec 04 20:28:14 So that it is possible to uninstall the cached ebuild that didn't cache its eclass. +2008 Dec 04 20:28:16 -*- jmbsvicetto mumbles - versioned eclasses +2008 Dec 04 20:28:29 -*- cryos|work thinks versioning should be used. +2008 Dec 04 20:28:29 cryos|work: understood +2008 Dec 04 20:28:37 It would get rid of many of these concerns. +2008 Dec 04 20:29:00 ok this could be handled later, jmbsvicetto can i wrote you as man taking care of eapi2only? +2008 Dec 04 20:29:03 We have what we have and I didn't want changes to hose peoples systems. +2008 Dec 04 20:29:59 <-- kaffeedoktor (n=kaffeedo@rps3741.ovh.net) has quit (Remote closed the connection) +2008 Dec 04 20:30:24 --> kaffeedoktor (n=kaffeedo@rps3741.ovh.net) has joined #gentoo-kde +2008 Dec 04 20:30:35 ok for next issue i see is wrong SLOT for our kde4 packages in the tree +2008 Dec 04 20:30:41 scarabeus: sure +2008 Dec 04 20:30:41 how to deal that +2008 Dec 04 20:30:51 i did something that should work for ktorrent +2008 Dec 04 20:30:59 hm ill have a look +2008 Dec 04 20:31:01 but i hope there will be better solution for the others +2008 Dec 04 20:31:12 scarabeus: what "wrong" slot? +2008 Dec 04 20:31:16 they use 4.1 +2008 Dec 04 20:31:21 -*- cryos|work is confused too. +2008 Dec 04 20:31:25 what used to mark kde they work +2008 Dec 04 20:31:34 but with new eclasses they should be marked as app version +2008 Dec 04 20:31:36 not slot of kde +2008 Dec 04 20:31:53 What app version? +2008 Dec 04 20:32:00 for example +2008 Dec 04 20:32:04 ktorrent has version 3 +2008 Dec 04 20:32:07 and 2 +2008 Dec 04 20:32:10 in the tree +2008 Dec 04 20:32:15 so 2 is slot:0 +2008 Dec 04 20:32:19 and 3 is slot:3 +2008 Dec 04 20:32:25 but now it was slot:4.1 +2008 Dec 04 20:32:28 cryos|work: I know what he means +2008 Dec 04 20:32:34 2 is for kde3? +2008 Dec 04 20:32:39 reavertm: yes +2008 Dec 04 20:32:43 cryos|work: The code used to apply only for packages in kde-base, that restriction was removed +2008 Dec 04 20:32:54 Can the two actually be slotted? +2008 Dec 04 20:33:02 That is another issue +2008 Dec 04 20:33:05 isn't this an issue only for -kdeprefix? +2008 Dec 04 20:33:08 Is it wise to remove the restriction? +2008 Dec 04 20:33:21 Are they all going into kdeprefix now? +2008 Dec 04 20:33:22 cryos|work: yes it is working as charm :] +2008 Dec 04 20:33:34 cryos|work: probably not, but it was done to enforce the use of prefix in kde-misc +2008 Dec 04 20:33:34 cryos|work: yes all packages sets themself based on kdeprefix +2008 Dec 04 20:33:50 I mean, if kde3 apps are going to /usr/kde/3.5 soon, there should be no issue anymore +2008 Dec 04 20:34:20 reavertm: That means we'll get with the kde3 apps the same issue we currently have with kde4 apps - they stop working after you bump kde version +2008 Dec 04 20:34:23 What about with -kdeprefix? They are still good I assume? +2008 Dec 04 20:34:40 The slot is changed, but the install location is still /usr +2008 Dec 04 20:35:01 well, kde3 will be no longer revbumped I'm afraid +2008 Dec 04 20:35:02 So they do the funky blocker that allows simulataneous files that collide, +2008 Dec 04 20:35:15 cryos|work: yes - that needs to be fixed +2008 Dec 04 20:35:22 jmbsvicetto hm i thought every future version of ktorrent for example it stays in the 3 slot right? +2008 Dec 04 20:35:33 cryos|work: i will give you my list of thoughts for kde3 +2008 Dec 04 20:35:38 and with the other extragear apps too +2008 Dec 04 20:35:57 cryos|work: http://dev.gentoo.org/~scarabeus/kde3-misc_packages.txt +2008 Dec 04 20:36:06 with scarabeus update yes. It was going to be 4.X without it +2008 Dec 04 20:36:07 krytzz: yep +2008 Dec 04 20:36:12 If you are installing the app into the kdeprefix then it makes sense for it to share the slot of the prefix dir it goes into. +2008 Dec 04 20:36:28 <-- deathwing00 (n=deathwin@gentoo/developer/Deathwing00) has quit ("Leaving.") +2008 Dec 04 20:36:32 cryos|work: well it can go to -kdeprefix too +2008 Dec 04 20:36:35 cryos|work: That was my thought, but now I have my doubts +2008 Dec 04 20:36:51 and you cant make dynamic slot +2008 Dec 04 20:37:03 cryos|work: amarok stopped working here with 4.1.80 because it was installed with 4.1.3, even though I still have 4.1.3 around +2008 Dec 04 20:37:07 sice ktorrent-3.1 now can go intoo 4.1 4.2 and live dirs +2008 Dec 04 20:37:20 That is why I have always had my doubts about slotting apps not released with the main KDE modules, you have to make artificial bumps I guess to other packages? +2008 Dec 04 20:37:40 How does ktorrent decide which prefix to install to? +2008 Dec 04 20:37:40 cryos|work: at this point I really don't know what to do +2008 Dec 04 20:38:05 :( +2008 Dec 04 20:38:07 This scheme sounds really messy, but I haven't been using it and so don't know what to say. +2008 Dec 04 20:38:16 cryos|work: One idea that crossed my mind was to install these apps into /usr/kde/apps/${PN}/${PV} +2008 Dec 04 20:38:24 the easiest would be to allow only one KDE4 installed... +2008 Dec 04 20:38:41 -*- cryos|work kinda suggested that... +2008 Dec 04 20:38:48 but scarabeus tried doing that and couldn't get it working with symlinks +2008 Dec 04 20:38:58 yeah i failed there too much +2008 Dec 04 20:39:03 it was not working for me +2008 Dec 04 20:39:10 Having so many options can be extremely tough to support. +2008 Dec 04 20:39:13 feel free to do it again for yourself +2008 Dec 04 20:39:21 cryos|work: i know :( +2008 Dec 04 20:40:06 That is why many distros choose not to do this, and it has bitten us many times in the past. 3.5 is simpler now due to no more bumps. +2008 Dec 04 20:40:11 cryos|work: This is another case were the real solution would be for upstream to think about this and provide a solution for having multiple versions in the same prefix +2008 Dec 04 20:40:36 we should try to push versioning on upstream +2008 Dec 04 20:40:40 that is not bad idea +2008 Dec 04 20:40:41 I agree with you entirely +2008 Dec 04 20:40:55 has anyone asked for this already? +2008 Dec 04 20:41:07 cryos|work: You've talked before with upstream about this, haven't you? +2008 Dec 04 20:41:12 I do think having multiple minor versions available to people who do not really know what they are doing is possibly a recipe for failure... +2008 Dec 04 20:41:28 jmbsvicetto: Yes, and I will probably talk about it again at Camp KDE in January. +2008 Dec 04 20:41:48 Many other distro developers also very much wanted this, and to a degree it works. +2008 Dec 04 20:41:56 Didn't you have a presentation you did about this issue? +2008 Dec 04 20:41:57 Not to the degree Gentoo would like though. +2008 Dec 04 20:42:08 Yes - it is on my blog somewhere. +2008 Dec 04 20:42:22 That should be an interesting reading for people in the team +2008 Dec 04 20:42:49 <-- MartyMcFly (n=martin@dslb-088-064-190-153.pools.arcor-ip.net) has quit (Remote closed the connection) +2008 Dec 04 20:43:03 yeah i would like to see it :] +2008 Dec 04 20:43:23 hm but with -kdeprefix there is no problem then... if the ABI is stable +2008 Dec 04 20:43:38 http://blog.cryos.net/archives/146-Gentoo-KDE-Talk-at-aKademy.html +2008 Dec 04 20:44:58 ok next point is more nice and all developers are needed: we need some lead, so people can oficialy find one, /me is proposing jmbsvicetto O:P (meantime looking on presentation on second monitor) +2008 Dec 04 20:45:00 I will be preparing half of the talk for the KDE and distros talk in January - so let me know if there are things you would like to be raised. +2008 Dec 04 20:45:46 -*- cryos|work never really saw the need for the hierarchy in small herds, but whatever makes you happy. +2008 Dec 04 20:46:23 --> Scorcere1 (n=Scorek@77-87-120-128.rev.masterkom.pl) has joined #gentoo-kde +2008 Dec 04 20:46:28 The KDE herd didn't have a lead for years and flourished, then dwindled... It is all about building a friendly community (lead or no). +2008 Dec 04 20:46:58 I agree with cryos|work about having a friendly community +2008 Dec 04 20:47:00 i have nothing against it :p +2008 Dec 04 20:47:05 :D +2008 Dec 04 20:47:31 Oh and I'm not that eager to get the "lead" hat :P +2008 Dec 04 20:47:32 i dont mind how this will evolve so i leave this one definetly up to all +2008 Dec 04 20:47:44 jmbsvicetto: yeah i am pretty sure of this :D +2008 Dec 04 20:47:54 noone wants to be lead i would say +2008 Dec 04 20:47:56 i think we should have a leader just as the other herds do +2008 Dec 04 20:48:05 not because we need someone to decide +2008 Dec 04 20:48:16 A quick note - team and not herd :P +2008 Dec 04 20:48:27 We're talking about the people and not about the packages ;) +2008 Dec 04 20:48:41 i will be the queen ;) +2008 Dec 04 20:48:41 jmbsvicetto: herd is missused for this for so long... +2008 Dec 04 20:48:44 --> dagger (n=dagger@piasek.co.uk) has joined #gentoo-kde +2008 Dec 04 20:49:06 i think word herd needs redefinition but it is not on todays topic +2008 Dec 04 20:49:12 -*- cryos|work never got why people were so picky about the words used, is it really a herd of packages? :D +2008 Dec 04 20:49:34 a bunch of packages +2008 Dec 04 20:49:35 ok so no lead for now, when times change jmbsvicetto is first on the row :P +2008 Dec 04 20:49:41 gentoo kde-bunch-of-people +2008 Dec 04 20:49:56 It is work time for me over here, I could do with getting stuff done soon. So I may leave in 5-10 mins. +2008 Dec 04 20:49:59 moving on to other not so pleasant topic, I think we need to look at the team members again - afaik, we have people listed in the kde page that haven't done anything kde related for many, many months +2008 Dec 04 20:50:06 <-- comawhite (n=comawhit@unaffiliated/comawhite) has quit ("Leaving") +2008 Dec 04 20:50:26 --> tgurr (n=tgurr@gentoo/developer/tgurr) has joined #gentoo-kde +2008 Dec 04 20:50:26 -=- Mode #gentoo-kde [+o tgurr] by ChanServ +2008 Dec 04 20:50:36 Hi tgurr +2008 Dec 04 20:50:40 agreed, we should clean it up, ask everyone if they are willing to do something and so on (does not count for people that are mentioned away) +2008 Dec 04 20:50:46 jmbsvicetto: hi +2008 Dec 04 20:50:58 <-- erulabs (n=seandon@net-cf9a4013.noc.impulse.net) has quit ("Leaving.") +2008 Dec 04 20:51:05 <-- JaMa (n=JaMa@chaos.mk.cvut.cz) has quit (Remote closed the connection) +2008 Dec 04 20:51:32 Getting to the same old same, it would help if all the members would be willing to join irc, but I don't have any illusions about getting some people in here +2008 Dec 04 20:51:50 jmbsvicetto: are you willing to mail them +2008 Dec 04 20:52:06 About being team members, sure? +2008 Dec 04 20:52:11 ok +2008 Dec 04 20:52:16 i am writing up notes +2008 Dec 04 20:52:20 so we have them after end +2008 Dec 04 20:52:21 :] +2008 Dec 04 20:52:38 about members +2008 Dec 04 20:52:42 we have problem in qt herd +2008 Dec 04 20:52:46 it is just yngwin +2008 Dec 04 20:53:00 how to get some qt devepoer :] +2008 Dec 04 20:53:05 I can even do something better, send a mail to the kde alias and ask everyone for a little introspection and to let us know if they're still part of the team and or want to be part of the team ;) +2008 Dec 04 20:53:20 jmbsvicetto: that i leave up to you :] +2008 Dec 04 20:53:22 scarabeus: I thought carlo and caleb where still in the team +2008 Dec 04 20:53:39 they are but they are inactive and non-responsive +2008 Dec 04 20:53:40 did you hear/see some commits from them in last month/2 +2008 Dec 04 20:53:41 scarabeus: with the obvious reservations about the above point +2008 Dec 04 20:53:56 yngwin: ok, just wanted to confirm +2008 Dec 04 20:54:04 reavertm: maybe you might be interested +2008 Dec 04 20:54:11 well, no major qt release recently so they may just wait for 4.5 +2008 Dec 04 20:54:21 yngwin: I'll talk to you about qt +2008 Dec 04 20:54:22 in qt maintenance a bit? +2008 Dec 04 20:54:28 and that reminds me, yngwin should get commit acces to kde-crazy +2008 Dec 04 20:54:32 reavertm: yes +2008 Dec 04 20:54:57 yngwin: do you have access to kde-testing? If not, you should also have it +2008 Dec 04 20:54:58 does bonsaikitten have access? :p +2008 Dec 04 20:55:11 jmbsvicetto: i dont +2008 Dec 04 20:55:16 krytzz: silence there! ;D +2008 Dec 04 20:55:21 unless i do but dont know it +2008 Dec 04 20:55:33 hmm, well I can try by forget about Qt from Trolltech svn fro bow - they shit svn only as daily snapshots via rsync +2008 Dec 04 20:55:37 bonsaikitten: I forgot to tell you, but robbat2 replied to me earlier saying you should have access now +2008 Dec 04 20:55:46 jmbsvicetto: ok, let me try :) +2008 Dec 04 20:55:57 for now^^ +2008 Dec 04 20:55:58 also, phonecall, I kinda missed the last half hour or so +2008 Dec 04 20:56:01 ok, my purpose with the kde-* overlays was for everyone on the team to have access to them +2008 Dec 04 20:56:10 yeah agreed +2008 Dec 04 20:56:36 I initially asked jokey to grant access to everyone at the time in the team. I haven't followed it through, so I'll talk to robbat2 again asking for an update about the current status +2008 Dec 04 20:56:52 and i took the liberty and added yngwin to team list on kde page, since it is project page for qt and kde, not only kde, i think i forget to mention that before for that i am ashamed +2008 Dec 04 20:57:05 ok tnx +2008 Dec 04 20:57:18 maybe i should get op status here then as well +2008 Dec 04 20:57:18 scarabeus: Yes, you're right +2008 Dec 04 20:57:22 sure +2008 Dec 04 20:57:30 keytoaster: I think it has to be you doing it +2008 Dec 04 20:57:45 keytoaster: iirc, we transfered +F to you +2008 Dec 04 20:58:57 oooh. can has access :D +2008 Dec 04 20:59:01 yngwin: seems I was able to grant it to you +2008 Dec 04 20:59:06 DrEeevil: you fail. +2008 Dec 04 20:59:08 <-- NSaibot (n=quassel@i3ED6C704.versanet.de) has quit (Remote closed the connection) +2008 Dec 04 20:59:12 bonsaikitten: :) +2008 Dec 04 20:59:32 ok one more infra thing +2008 Dec 04 20:59:36 -=- Mode #gentoo-kde [+o yngwin] by jmbsvicetto +2008 Dec 04 20:59:44 tampakrap would need normal mentor if he wants to became full dev +2008 Dec 04 20:59:51 i am willing to help him with the quiz +2008 Dec 04 20:59:57 but someone must oversee +2008 Dec 04 20:59:59 who can do that +2008 Dec 04 21:00:11 I'm too young for that I think +2008 Dec 04 21:00:14 end-quiz we are speaking about +2008 Dec 04 21:00:15 I'm also willing to help, but I still don't have the 6 months, so I can't mentor +2008 Dec 04 21:00:16 --> genady12 (n=genady12@87.69.85.204) has joined #gentoo-kde +2008 Dec 04 21:00:17 first of all is everyone ok with that? +2008 Dec 04 21:00:19 my quantum status is confusing +2008 Dec 04 21:00:31 -*- bonsaikitten is 2 years on, 2 years off ... +2008 Dec 04 21:00:42 bonsaikitten: You're *chaotic* ;) +2008 Dec 04 21:00:44 bonsaikitten: ;] you are cheating :D +2008 Dec 04 21:00:47 i am +2008 Dec 04 21:00:55 so is that 2 years or 2 months now? :) +2008 Dec 04 21:00:57 --> oc2k1 (n=oc2k1@p5B104618.dip.t-dialin.net) has joined #gentoo-kde +2008 Dec 04 21:01:16 bonsaikitten: we need to ask Betelgeuse +2008 Dec 04 21:01:22 :) +2008 Dec 04 21:01:39 I think it is better if I stay out of it for a while +2008 Dec 04 21:01:39 perhaps jokey could do it? +2008 Dec 04 21:01:54 krytzz: jokey is away +2008 Dec 04 21:01:56 i thought jokey was caught up in real life +2008 Dec 04 21:01:57 jokay is away +2008 Dec 04 21:02:01 ok +2008 Dec 04 21:02:06 yngwin: you cant do it? +2008 Dec 04 21:02:19 i can +2008 Dec 04 21:02:29 although i dont feel guru enough +2008 Dec 04 21:02:53 :] +2008 Dec 04 21:03:07 yngwin: you are guru enough! +2008 Dec 04 21:03:14 dont worry, from mine humble PoV you are guru enought +2008 Dec 04 21:03:16 well, if you say so :) +2008 Dec 04 21:03:27 :) +2008 Dec 04 21:03:36 thanks :) +2008 Dec 04 21:03:52 is there a bug for tampakrap's recruitment? +2008 Dec 04 21:04:01 no +2008 Dec 04 21:04:02 keytoaster: yes you did +2008 Dec 04 21:04:06 err +2008 Dec 04 21:04:08 <-- Scorcerer (n=Scorek@77-87-120-128.rev.masterkom.pl) has quit (Connection timed out) +2008 Dec 04 21:04:08 -=- Scorcere1 is now known as Scorcerer +2008 Dec 04 21:04:08 jmbsvicetto: yes you did +2008 Dec 04 21:04:21 yngwin: nope i can create one, i made him HT yesterday +2008 Dec 04 21:04:27 okay +2008 Dec 04 21:04:42 I let it pass, but since scarabeus mentioned the project page, we both applied some changes to the page to integrate KDE4 as a regular release and to update the status of the overlays +2008 Dec 04 21:04:58 Don't know if everyone has checked it and whether there's any objection to it +2008 Dec 04 21:05:03 scarabeus: then i'll second on that, and then we can see what betelgeuse says +2008 Dec 04 21:05:09 <-- scratch[x] (n=scratch@83.239.148.148) has quit (No route to host) +2008 Dec 04 21:05:14 tampakrap: kaloriziko ;) +2008 Dec 04 21:05:23 wtf? +2008 Dec 04 21:05:25 we can do this stuff after meeting, great :] +2008 Dec 04 21:05:43 ok last two things per my list +2008 Dec 04 21:05:46 first is kde4.2 +2008 Dec 04 21:05:50 so what shape is it in +2008 Dec 04 21:05:56 it is just statusreport for it +2008 Dec 04 21:06:00 scarabeus: Good and BAD!!! +2008 Dec 04 21:06:01 so speak up kde-crazy people +2008 Dec 04 21:06:04 I'll take care of them snapshots +2008 Dec 04 21:06:09 well, it works :) +2008 Dec 04 21:06:15 i'll also give priority to snapshots +2008 Dec 04 21:06:21 plasma crashes often :p +2008 Dec 04 21:06:22 kde 4.2? its crap. it friggin' needs mysql +2008 Dec 04 21:06:28 scarabeus: my keyboard layout is still messed up - but nepomuk and plasma have a better look ;) +2008 Dec 04 21:06:36 it works quite well for me +2008 Dec 04 21:06:41 also for me nepomuk is strange +2008 Dec 04 21:06:46 had a few compile failures, but nothing unexpected +2008 Dec 04 21:06:54 I guess trunk is way better than snapshots, but... regressions are quite often recently +2008 Dec 04 21:07:01 but rest is ok +2008 Dec 04 21:07:02 ebuild-wise - it's pretty mature +2008 Dec 04 21:07:14 One important point about snapshots, they can't rely on live packages +2008 Dec 04 21:07:24 live is in a very good shape, snapshots have been a bit neglected +2008 Dec 04 21:07:25 but upstream will mess with buildsystem for sure +2008 Dec 04 21:07:31 -*- bonsaikitten is just digesting them +2008 Dec 04 21:07:35 So we need to bug other teams or add new versions/snapshots if required to the overlay/tree +2008 Dec 04 21:07:50 especially opensync :p +2008 Dec 04 21:07:55 opensync is problem +2008 Dec 04 21:07:57 currently +2008 Dec 04 21:08:20 and also networkmanager, i took liberty of speaking up with rbu on our behalf +2008 Dec 04 21:08:31 opensync and it;s plugins were problematic with kde3 already +2008 Dec 04 21:08:34 and today/tomorow nm-0.7 hit the tree +2008 Dec 04 21:08:38 scarabeus: one solution is to try to add an update to kde-crazy overlay until it gets in the tree +2008 Dec 04 21:08:52 ah nice +2008 Dec 04 21:08:55 kitchensync is just lame kde3 port +2008 Dec 04 21:08:59 scarabeus: rbu has shown interest in getting nm working +2008 Dec 04 21:09:03 yes +2008 Dec 04 21:09:08 scarabeus: he might need some help with it, though +2008 Dec 04 21:09:09 he already made it work +2008 Dec 04 21:09:17 jmbsvicetto: well i will ask +2008 Dec 04 21:09:48 The GNOME team was also interested in getting 0.7 in the tree, iirc +2008 Dec 04 21:10:19 yeah, everyone is crazy about those networkmanager desktop applets... +2008 Dec 04 21:10:42 can we prevent such cross-repo dependencies in the future? +2008 Dec 04 21:10:54 I would just love to get some applet that does the eap stuff for me ;) +2008 Dec 04 21:11:05 bonsaikitten: what deps? +2008 Dec 04 21:11:08 there will be rule for next time all must be on portage/overlay +2008 Dec 04 21:11:14 like nm +2008 Dec 04 21:11:23 like kde4 requiring nm from rbu overlay +2008 Dec 04 21:11:24 we should have a copy in our repo if that happens +2008 Dec 04 21:11:31 yeah, agreed +2008 Dec 04 21:11:36 hm but this sucks somehow +2008 Dec 04 21:11:44 if you have both overlays you have the ebuild 2 times +2008 Dec 04 21:11:50 at least until we can get Zac to support repo deps ;) +2008 Dec 04 21:11:50 and you dont know if the 2 differ or something +2008 Dec 04 21:12:05 repodeps ;] +2008 Dec 04 21:12:10 it sounds llike sam rep band +2008 Dec 04 21:12:11 also its additional maintenance work +2008 Dec 04 21:12:25 talking about overlays i'd like to remind everyone that versioned misc packages go to kde-testing :) +2008 Dec 04 21:12:35 krytzz: yes, we should only have them until it gets pushed into the tree +2008 Dec 04 21:12:36 yeah, i just see GLEP for it being discussed, then presented, then rejected or suspended :P +2008 Dec 04 21:12:39 ok tampakrap :p +2008 Dec 04 21:13:02 ok so what with opensync +2008 Dec 04 21:13:06 it is BbD +2008 Dec 04 21:13:08 tampakrap: versioned "not known to be broken" misc packages ;) +2008 Dec 04 21:13:13 broken by design +2008 Dec 04 21:13:13 i wouldnt mind with a central gentoo-deps overlay :p +2008 Dec 04 21:13:30 we call that "the main tree" +2008 Dec 04 21:13:38 scarabeus you mean opensync akonadi plugin or kitchensync? +2008 Dec 04 21:13:44 so, how fast are we going to get 4.2 there as ~arch? +2008 Dec 04 21:13:51 bonsaikitten then stab people to get things faster in there then :p +2008 Dec 04 21:13:54 and is kde 4.2 a stable candidate? +2008 Dec 04 21:14:06 bonsaikitten: I don't think we should get 4.2 in the tree until RC +2008 Dec 04 21:14:09 yeah crappy opensync +2008 Dec 04 21:14:16 krytzz: I'm just cleaning up. If that's not enough go screw yourself counterclockwise ;) +2008 Dec 04 21:14:24 bonsaikitten: I would also hard mask the RCs and lift the mask with 4.2 +2008 Dec 04 21:14:25 i think it is time to have a stable kde4 version +2008 Dec 04 21:14:31 jmbsvicetto: acceptable +2008 Dec 04 21:14:48 scarabeus yes, but be more specific, opensync from portage is crappy or kde opensync support? +2008 Dec 04 21:14:49 i think if the 4.2 progress continues like know it should be great by 4.2.1 +2008 Dec 04 21:14:58 opensync from portage +2008 Dec 04 21:14:59 now +2008 Dec 04 21:14:59 bonsaikitten: we might however start thinking on moving 4.2 into kde-testing +2008 Dec 04 21:15:02 opensync itself +2008 Dec 04 21:15:09 bonsaikitten: at least as soon as we take care of the eclasses +2008 Dec 04 21:15:17 eclasses first! :D +2008 Dec 04 21:15:17 jmbsvicetto: +1 +2008 Dec 04 21:15:34 and I do think 4.2 should be a stable candidate - let's just see how it works +2008 Dec 04 21:15:47 one thing we need to solve quickly is getting 3.5.10 marked stable +2008 Dec 04 21:16:05 that is already stated in the summary paper :] +2008 Dec 04 21:16:08 jmbsvicetto which 4.2? you mean snapshots and revbump as 4.2 and keep them updated along with snaphots from kde-crazy? +2008 Dec 04 21:16:10 jmbsvicetto: i'll start working on kde3 right after this meeting +2008 Dec 04 21:16:18 if yes, then you are crazy ;) +2008 Dec 04 21:16:33 why? +2008 Dec 04 21:16:35 nope to testing should go only snapshots marked as betaX +2008 Dec 04 21:16:36 reavertm: I mean that I think 4.2 snapshots should be moved to testing +2008 Dec 04 21:16:45 reavertm: after the eclasses are merged back again +2008 Dec 04 21:16:49 snapshot itself i disagree +2008 Dec 04 21:16:57 but snapshots for beta1 beta2 rcX +2008 Dec 04 21:16:58 yes +2008 Dec 04 21:17:04 scarabeus: yes, that's what I mean +2008 Dec 04 21:17:10 should have been clearer +2008 Dec 04 21:17:16 I wouldn't advise that atm - there may be many changes and syncing them between kde-crazy <-> kde-testing ... +2008 Dec 04 21:17:17 great then we agree :] +2008 Dec 04 21:17:34 reavertm: just delete it and copy from point A to point B +2008 Dec 04 21:17:39 reavertm: git cherry-pick ;) +2008 Dec 04 21:17:41 it wont harm kittens TM +2008 Dec 04 21:17:52 jmbsvicetto: cherry-pick cross repos? +2008 Dec 04 21:17:56 yes +2008 Dec 04 21:17:58 wow +2008 Dec 04 21:18:00 that i didnt know +2008 Dec 04 21:18:05 that is even more cooler +2008 Dec 04 21:18:11 scnaphots are keep sync from live now - and I would just wait until some rc is released, and patched in kde-crazy and then quick revbup and move -> testing +2008 Dec 04 21:18:28 scarabeus: hmm, now you're going to force me to test it to be sure I didn't came up with that +2008 Dec 04 21:18:36 well, if you volunteer to do it :) +2008 Dec 04 21:19:14 <-- genady12 (n=genady12@87.69.85.204) has quit (Read error: 145 (Connection timed out)) +2008 Dec 04 21:19:15 ok this can be suspended and handled later +2008 Dec 04 21:19:20 reavertm: The idea was to try to have RCs in the tree, so we should try to get something in testing before that +2008 Dec 04 21:19:21 now more pain in the ass TM issue +2008 Dec 04 21:19:25 mysql +2008 Dec 04 21:19:28 whole kde needs it +2008 Dec 04 21:19:33 aarghl! :) +2008 Dec 04 21:19:33 and amarok is chapter itself +2008 Dec 04 21:19:42 what to do with it +2008 Dec 04 21:19:43 scarabeus: There's only one option here: work with robbat2 +2008 Dec 04 21:19:50 yes... we cant do anything about that :( +2008 Dec 04 21:19:58 did you see the eclass +2008 Dec 04 21:19:58 yes, I agres 4.2 should be in tree asap but moving it to testing only for the sake of having it in kde-testing is bad idea imho +2008 Dec 04 21:20:01 does he maintain mysql? +2008 Dec 04 21:20:04 did? did? i dont like it +2008 Dec 04 21:20:09 krytzz: yes he does +2008 Dec 04 21:20:09 scarabeus: I've asked him yesterday and he's still waiting for mysql upstream to reply to his request for a dynamic lib for mysql/e +2008 Dec 04 21:20:17 I've already put my mysql rant in gentoo-dev :P +2008 Dec 04 21:20:17 ah ok +2008 Dec 04 21:20:31 scarabeus: what do you mean? +2008 Dec 04 21:21:03 jmbsvicetto: too chaotical too much patches too much crazy +2008 Dec 04 21:21:11 but i dunno how is upstream cooperating +2008 Dec 04 21:21:19 reavertm: The point of kde-testing is to be the bridge to the tree +2008 Dec 04 21:21:28 ok on other hand who is willing to cooperate with robbat2 on that? +2008 Dec 04 21:21:32 scarabeus: you mean mysql eclass? +2008 Dec 04 21:21:37 jmbsvicetto: ay sir +2008 Dec 04 21:21:46 scarabeus: mysql isn't that "simple" +2008 Dec 04 21:22:05 scarabeus: And robbat2 if surely one if not the "one" gentoo mysql yoda +2008 Dec 04 21:22:09 s/if/is/ +2008 Dec 04 21:22:12 I've seen this eclass and it's.. well.. a bit complex as eclass for one package +2008 Dec 04 21:22:34 reavertm: it adds a build system to a braindead package ;) +2008 Dec 04 21:22:39 scarabeus: I'm willing to work with robbat2 about mysql +2008 Dec 04 21:22:58 yeah, I heard.... +2008 Dec 04 21:23:09 --> genady12 (n=genady12@87.69.85.204) has joined #gentoo-kde +2008 Dec 04 21:23:12 great puting you to the txt :] +2008 Dec 04 21:23:27 ok issues from my side mentioned +2008 Dec 04 21:23:32 scarabeus: I'll have to check that text - it feels like I'm being "canned" ;) +2008 Dec 04 21:23:36 someone else has something that needs to be handled +2008 Dec 04 21:23:49 jmbsvicetto: dont worry i try to make it to be factical +2008 Dec 04 21:23:58 is there an open bug for 3.5.10 stabilization? +2008 Dec 04 21:24:01 yes +2008 Dec 04 21:24:08 if not let's create one to sum up the issues +2008 Dec 04 21:24:12 ok then +2008 Dec 04 21:24:15 yeah, about the kde-plasma category: could we do it? +2008 Dec 04 21:24:15 If ctrl+f3 worked here, I could get you the number quicker ;) +2008 Dec 04 21:24:17 i'll search +2008 Dec 04 21:24:24 bug kde-3.5.10 +2008 Dec 04 21:24:27 do you like it? +2008 Dec 04 21:24:44 krytzz: I don't think we should go down that route +2008 Dec 04 21:25:13 ok what are the alternatives +2008 Dec 04 21:25:14 krytzz: If we try to get kde-plasma, kde-plasmoids, ..., we're going to create resistance +2008 Dec 04 21:25:28 no, only kde-plasma jmbsvicetto for everything plasma-related +2008 Dec 04 21:25:31 kde-plasma only it is going to be +2008 Dec 04 21:25:32 we've lived with kde-base and kde-misc for a long, long time +2008 Dec 04 21:25:34 could we have plasmoids for more than one version? and in case of slotted kde's, could we install a plasmoid for every session? +2008 Dec 04 21:25:59 how many packages are we talking and what type of packages +2008 Dec 04 21:25:59 tampakrap: nope it is same as misc packages for more kde installs +2008 Dec 04 21:26:09 tampakrap they won't build that easy +2008 Dec 04 21:26:11 jmbsvicetto: plasma aplets and enginges +2008 Dec 04 21:26:15 hm ok thats just personal preference how filled the categories are, but i prefer fewer packages per category +2008 Dec 04 21:26:28 currently about 150 on kde-apps/look +2008 Dec 04 21:26:39 and we can bundle them all in the end +2008 Dec 04 21:26:54 scarabeus: if we're talking about kde-look, perhaps we're going down the wrong path +2008 Dec 04 21:26:58 categories are bad btw, some tag clouds should be introduced one day... +2008 Dec 04 21:27:10 scarabeus: I'm thinking if we couldn't try to do something similar to what the perl team did with cpan +2008 Dec 04 21:27:15 --> Eythan (n=Eythan@AMontpellier-152-1-30-159.w81-251.abo.wanadoo.fr) has joined #gentoo-kde +2008 Dec 04 21:27:16 reavertm one day... yes :p +2008 Dec 04 21:27:22 jmbsvicetto: what they did +2008 Dec 04 21:27:40 some perl magic i guess ;] +2008 Dec 04 21:27:45 yup ;) +2008 Dec 04 21:28:09 --> fedux (n=fedux@190.55.126.139) has joined #gentoo-kde +2008 Dec 04 21:28:11 app-portage/g-cpan g-cpan: generate and install CPAN modules using portage +2008 Dec 04 21:28:19 hm +2008 Dec 04 21:28:58 i assume this is like ruby gems? +2008 Dec 04 21:28:59 so dedicated tool only for some plasmoids? +2008 Dec 04 21:29:24 not worth it imho +2008 Dec 04 21:29:31 I haven't looked at their implementation, but if I'm not mistaken, they've created a tool to help install packages in cpan. So instead of having one ebuild for every kde-look package, we could try to have some tool that helps install packages from kde-look +2008 Dec 04 21:29:38 i thought that upstream was going to apply a tool for downloading and easy installing plasmoids +2008 Dec 04 21:29:53 yeah kde-look, but plasmoids still have to be compiled +2008 Dec 04 21:30:04 cpan stuff not +2008 Dec 04 21:30:07 and have various dependencies +2008 Dec 04 21:30:31 No way to get them working without ebuilds? +2008 Dec 04 21:30:34 tampakrap hm but only for script plasmoids? +2008 Dec 04 21:30:34 and apply to different kde versions +2008 Dec 04 21:30:44 i'm not sure +2008 Dec 04 21:30:48 well, actually I was thinking about some ebuild generator with automatic depencency discovering (originally for plasmoids from playground) +2008 Dec 04 21:31:11 jmbsvicetto: not bad idea +2008 Dec 04 21:31:13 I think we need to think more about this +2008 Dec 04 21:31:17 writing it down as long-term goal +2008 Dec 04 21:31:18 while ebuild generator (without deps) I got done already, eclass is not yet ready for fetch/unpack from playground +2008 Dec 04 21:31:56 Are plasmoids "heavy"? +2008 Dec 04 21:32:09 some of them +2008 Dec 04 21:32:12 very few +2008 Dec 04 21:32:13 some are pretty normal c++ apps, so i would say yes +2008 Dec 04 21:32:33 the script ones can be installed by plasma, we dont have to care about these +2008 Dec 04 21:33:38 Anything else? +2008 Dec 04 21:33:45 well, we could do as well some knewstuff2 interface for kde4 for plasmoids but we're not kde devs.. +2008 Dec 04 21:34:10 (it could reduce problem of plasmoids to installing them as icon themes) +2008 Dec 04 21:34:26 yeah debug useflag in eclass +2008 Dec 04 21:34:33 but ok this was already discussed +2008 Dec 04 21:34:41 it is on dev already +2008 Dec 04 21:34:45 was it? +2008 Dec 04 21:34:45 ah ok +2008 Dec 04 21:34:46 so lets see how that evolve +2008 Dec 04 21:34:53 aa, my proposition? +2008 Dec 04 21:34:59 reavertm: we might have to write it as glep +2008 Dec 04 21:35:00 it won't evolve... +2008 Dec 04 21:35:03 and push it trhought +2008 Dec 04 21:35:38 no way, just pass - it's against "ultimate freedom" and to package manager specific +2008 Dec 04 21:35:45 i dont care they are picky about it, i think they would not agree with anything that does not worship their ethernal glory (dont cite me that is just brief overview of those flames) +2008 Dec 04 21:35:46 as it uses FEATURES +2008 Dec 04 21:36:43 anyway, "our own" debug suport you mean? +2008 Dec 04 21:37:03 well, "additiomnal debug codepaths" are supported already +2008 Dec 04 21:38:01 hm so scarabeus whats the role model for kde-misc ebuilds now? +2008 Dec 04 21:38:22 krytzz: have no idea +2008 Dec 04 21:38:29 everything what is not in kde-base +2008 Dec 04 21:38:32 actually I see no role for kde-misc really - never seen +2008 Dec 04 21:38:32 from what i can see +2008 Dec 04 21:38:44 ok, kdevelop, kdesvn then? +2008 Dec 04 21:39:03 hm +2008 Dec 04 21:39:09 oh it is mess like hell +2008 Dec 04 21:39:14 kdevelop is in KDE even and it will be in kde-base soon I guess (released as part of KDE) +2008 Dec 04 21:39:21 it is messy a bit +2008 Dec 04 21:40:00 ok is this still part of meeting chat or we can dismisso ourselfs? +2008 Dec 04 21:40:11 i have nothing further +2008 Dec 04 21:40:12 oh typos it is going to kill me one day +2008 Dec 04 21:40:39 scarabeus bug wranglers - needed or not? +2008 Dec 04 21:40:47 not now, we have pretty big list +2008 Dec 04 21:40:59 i will write it onto longterm with you as person interested +2008 Dec 04 21:40:59 ok +2008 Dec 04 21:41:01 ? +2008 Dec 04 21:41:37 I think you're looking at it from the wrong pov - bug-wranglers +2008 Dec 04 21:41:40 well, I'm not going to push if it's seen not necessary +2008 Dec 04 21:42:13 ok, i'm putting in a staffing-needs/recruitment request for developers and/or herd testers for qt herd +2008 Dec 04 21:42:16 I would like to model it a bit like KDE team, at least have more of them than 1 +2008 Dec 04 21:42:25 We don't need bug wranglers to look at new bugs and check if they're kde bugs. We need people that work through kde bugs and help get them resolved - by providing patches, by doing tests, by interacting with users. +2008 Dec 04 21:42:31 ok when the eclasses are merged every kde-testing ebuild should have the KDE_MINIMUM thing scarabeus? +2008 Dec 04 21:42:42 nope +2008 Dec 04 21:42:56 krytzz: kde_minimal is only override variable +2008 Dec 04 21:43:00 it should work as they are now +2008 Dec 04 21:43:10 read up description in eclass +2008 Dec 04 21:43:13 ok +2008 Dec 04 21:43:14 ill do +2008 Dec 04 21:43:45 ok, one last request from me - if you work in the overlays, be sure to run repoman full from time to time. There's some extra cookies for those also running pcheck ;) +2008 Dec 04 21:44:04 http://dev.gentoo.org/~scarabeus/kde_meeting_state.txt +2008 Dec 04 21:44:12 and i am going to save the log from this +2008 Dec 04 21:44:13 got it ^^ +2008 Dec 04 21:44:21 should i put it onto kde space? +2008 Dec 04 21:44:37 and please try to forward my access to kde-testing, i want to do some kde3 work there +2008 Dec 04 21:45:58 scarabeus: sure diff --git a/meeting-logs/20090108-summary.txt b/meeting-logs/20090108-summary.txt new file mode 100644 index 0000000..5b61c01 --- /dev/null +++ b/meeting-logs/20090108-summary.txt @@ -0,0 +1,27 @@ +kde3: + sent mail asking for volunteers since we are short on staff on kde3. Sqashing bugs/etc. - cryos +eclasses: + done, commit to the tree, anounce on dev, make sure all ebuilds are updated to new structure and revbumped. - scarabeus +kde4: + 4.1.4 after eclasses and mics apps are done, not earlier! - alexxy as a new dev :] + disable +kdeprefix on stable (in the tree) - jmbsvicetto? + 4.2 doublecheck for missing ebuilds, generate metas - alexxy, tampakrap + policykit: suspended for now, when time comes we should cooperate with gnomies + printing: bump everything first in kde-testing, move to tree when we think it is ready, printing suspended until this is done. - !!! NOBODY !!! (leave it on gentoo-desktop?) + write nice guide - tampakrap + fix homepages for kdebase ebuild on correct ones in kde structure - patrick + mono - suspended until someone care, we dont want them - scarabeus +qt4 + status: yngwin states he has some qt apprentices, which is great :] + overlay: there will be new overlay for qt stuff which is yngwin creating + pyqt/pykde messie - patrick, yngwin if they get to it :] + +SPLIT/MERGE overlays VOLTES: +yngwin: merge +kitten: merge +scarab: merge +tampakrap: merge +reavertm: merge +alexxy: merge +cryos: dont mind merge +sput: merge \ No newline at end of file diff --git a/meeting-logs/20090108.txt b/meeting-logs/20090108.txt new file mode 100644 index 0000000..264dc6a --- /dev/null +++ b/meeting-logs/20090108.txt @@ -0,0 +1,666 @@ +[20:00:10] my dear friends it the time to start the meeting :] +[20:00:13] masking 4.1 shouldn't be needed +[20:00:21] MEATING +[20:00:22] it is. +[20:00:28] *ding ding ding* +[20:00:30] yes =) +[20:00:31] --> linex (n=quassel@60.54.93.166) has joined #gentoo-kde +[20:00:35] !herd kde +[20:00:36] PSYCHO___: (kde) caleb, carlo, cryos, deathwing00, genstef, jmbsvicetto, keytoaster, mattepiu, patrick, scarabeus, tgurr +[20:00:40] time for meating +[20:00:43] emerge -DuvaN world will pull in 4.1 packages unless all your world entries use :3.5 +[20:00:47] it's quite annoying actually +[20:00:49] /mode +m +[20:00:52] tehehehehehe +[20:00:53] *** Mode #gentoo-kde +v alexxy by scarabeus +[20:01:12] =) +[20:01:20] heh +[20:01:20] Thanks a lot! Have fun with the meeting. +[20:01:20] =) +[20:01:28] -*- Sput had to fix his dad's world file to avoid installing KDE4 +[20:01:28] *** Mode #gentoo-kde +v hwoarang by scarabeus +[20:02:02] --> cryos|work (n=mhanwell@gentoo/developer/cryos) has joined #gentoo-kde +[20:02:02] *** Mode #gentoo-kde +o cryos|work by ChanServ +[20:02:08] <-- mortalmatt (n=matthew@p54A6D9A6.dip.t-dialin.net) has quit ("Leaving") +[20:02:12] now we can start :) +[20:02:17] :D +[20:02:30] cant we have at least few devs anounce their presence +[20:02:37] -*- yngwin present +[20:02:44] Look in the nick list... +[20:02:52] jmbsvicetto? +[20:03:15] hello +[20:03:25] I'm using quassel +[20:03:26] cryos|work: well only you me and yngwin are online, rest is away :] +[20:03:40] bonsaikitten: ?? +[20:03:43] yes? +[20:03:44] are you there? +[20:03:46] he is :] +[20:03:50] Sucks - I nearly didn't make it. Compositing and Avogadro crashed my X server... +[20:03:54] I got the core running and I use my client to connect to it. +[20:03:56] bonsaikitten is away-faking as usual :) +[20:04:03] whut! +[20:04:16] Its just a bot! +[20:04:16] ok i guess we can wait few minutes if jmbsvicetto shows up :] +[20:04:28] or start without him? +[20:04:29] maybe reavertm too +[20:04:31] bonsaikitten: Are you turing complete? +[20:04:48] Why do I have do pane of the same channel topand below +[20:05:05] cryos|work: I doubt it, but I do have some strange loops +[20:05:13] <-- the_p (n=the_p@cust.static.62-152-211-38.swisscomdata.ch) has quit (Remote closed the connection) +[20:05:35] does anyone know when dev.gentooexperimental.org will be up again? +[20:05:47] victorlf__: it isn't? +[20:05:58] nope +[20:05:59] right +[20:06:45] --> MartyMcFly (n=martin@dslb-088-066-055-066.pools.arcor-ip.net) has joined #gentoo-kde +[20:07:27] linex: the top one is the chat monitor, it shows activity in all channels that you are in +[20:07:53] linex: you can move it +[20:08:05] linex: or hide it by rightclick +[20:08:16] why is d.ge.o so popular? +[20:08:22] in the top bar^ +[20:08:24] --> tbeadle_ (n=tbeadle@204.181.64.60) has joined #gentoo-kde +[20:08:26] because we have our files in there :] +[20:08:26] Ah ok. nice feature but I don't think I want it. Not right now. Its removable, right ? +[20:08:35] what files? +[20:09:00] -*- Sput failed getting a shell on d.ge.o yet :/ +[20:09:02] tampakrap: snapshots of phonon4exampe +[20:09:03] tampakrap: because it hots so much +[20:09:13] right. someone fscked php +[20:09:14] ah yes +[20:09:36] MrRat: I right clck. There Configure. Then what ? +[20:09:49] linex: yes rightclick in the bar above topic, where file,view,etc... is +[20:10:03] ok +[20:10:03] --> restle (n=restle@212.6.7.10) has joined #gentoo-kde +[20:10:23] see "show chat monitor" +[20:10:30] ok, its gone. Its called Chat Monitor, right ? +[20:10:44] there. +[20:11:24] Mr Rat : is it possible to have the traditional channel tabs instead of the tree-like on the left ? +[20:11:31] linex: #quassel for other quassel related help :p +[20:11:40] ok i guess we should start so we can end up reasonably and hope others show up in progress... objections? +[20:11:41] MrRat: ok fair enough +[20:12:36] <-- tbeadle_ (n=tbeadle@204.181.64.60) has quit (Read error: 54 (Connection reset by peer)) +[20:12:41] first on the nice list is just sumarising of previous meeting (read as what is not done from that list :]) +[20:12:43] no objections here +[20:12:43] --> tbeadle_ (n=tbeadle@204.181.64.60) has joined #gentoo-kde +[20:12:44] linex: however id prefer tabs myself too :p +[20:12:46] http://www.gentoo.org/proj/en/desktop/kde/meeting-logs/kde-herd-meeting-summary-20081204.txt +[20:13:04] MrRat: :) +[20:13:17] -*- cryos|work is listening... +[20:13:30] ok, what's the latest on 3.5.10 stabilizing? +[20:13:37] For the record PSYCHO___ = ? +[20:13:44] scarabeus +[20:13:44] scarabeus +[20:13:48] OK +[20:13:52] <-- tbeadle (n=tbeadle@204.181.64.60) has quit (Read error: 104 (Connection reset by peer)) +[20:14:05] <-> scarabeus is now known as frogeater +[20:14:13] <-> You are now known as scarabeus +[20:14:42] 3.5.10 is stable enough for the users but still there are many open bugs regarding it +[20:14:55] and of course there is still the issue with the misc apps +[20:15:18] is there any progress? or nobody is working on it seriously +[20:15:25] the eclass has to be updated to make them prefixed to /usr/kde/3.5 +[20:15:29] maybe we should write on dev we want some volunteers +[20:15:46] i'm ok with this +[20:15:53] as a side remark: 3.5.10 will definitely be upstream's last release +[20:15:55] --> agamn (n=agamn@ip-83-134-215-20.dsl.scarlet.be) has joined #gentoo-kde +[20:15:58] i also can work on it but was busy with quiz and other things lately +[20:15:59] ok +[20:16:00] shame +[20:16:28] some patches still go into svn, but no further releases are planned. +[20:16:36] -*- cryos|work has found it tough finding spare time to work on 3.5.10... +[20:16:44] we need it stable in order to make 4.X stable :] +[20:16:56] since only 3.5.10 has correct cryos magic :] +[20:17:11] ok but i think we should concentrate on kde-4.2 release first and then to 3.5 +[20:17:21] so let's do a call for volunteers to help squash bugs on 3.5.10 +[20:17:31] agreed +[20:17:31] ok who will sent the mail on dev? +[20:17:40] you :) +[20:17:48] I will as and when I can send the time, but currently my spare time is at a real premium :-( +[20:18:08] well i am getting my time pretty sqeezed too :] +[20:18:16] so we shall see :] +[20:19:12] ok next thing is kde4 eclasses are ready for commit to the main tree +[20:19:27] after this commits, all in tree ebuilds must be updated and revbump +[20:19:38] and seems most of kde4 misc apps already ready for this eclasses +[20:19:39] and users must use these versions in order for flawless update +[20:19:45] I still think the default for live outside of kde-base should be changed back to what it was - doesn't directly affect tree ebuilds though. +[20:20:07] cryos|work: ok that i missed, fix that in some commit please, so i dont forget again +[20:20:23] I will do it - I just didn't want to cause it to yo-yo... +[20:20:26] make it +kdeprefix for everything live by default +[20:20:38] cryos|work: i already agreed on it :P i only forget +[20:20:52] Yep - explicitly setting to - will continue to work. +[20:20:56] -*- cryos|work goes to do that... +[20:21:18] anything else to eclasses? +[20:21:21] but there still should be possible to install live kde misc apps with kde 4.1 or 4.2 +[20:21:31] alexxy: it is :} +[20:21:39] you just need to set kdeprefix correctly first +[20:21:41] It is - set -kdeprefix. +[20:21:46] and for that you need to know what are you doing +[20:22:19] because some misc apllets exists only as -9999 ones +[20:22:24] Anyone using live should know what they are doing... +[20:22:38] agreed with cryos on this +[20:22:47] me too =) +[20:23:05] ok i guess ecalsses were polished pretty fine :] +[20:23:10] <-- undetected (n=laika@27.138.45.66.cm.sunflower.com) has quit +[20:23:11] btw i saw kde 4.1.4 tagged in svn +[20:23:17] They are looking good to me. +[20:23:27] alexxy: yeah, that'll keep us busy next week :) +[20:23:29] ok since he mention it SOMEBODY willing to bump 4.1.4 +[20:23:39] do we want it or need it? +[20:23:41] Yes it was and I think tarballs are uploaded. +[20:23:42] and what about misc apps? +[20:23:42] It will be a nice bump to all KDE apps when the new eclass goes in. +[20:23:56] cryos|work: good idea +[20:23:57] :] +[20:24:00] should live misc apps stay in :live and not in stable systems? +[20:24:06] Kill two birds with one stone. +[20:24:07] ok so we do eclass -> misc apps ->4.1.4 +[20:24:37] ok who is going to do actual bump +[20:24:40] All live apps should be in the :live slot shouldn't they? +[20:24:52] my opinion to this: ^^ +[20:25:04] can be in :0 if dev thinks it is needed +[20:25:12] we shouldn't provide live ebuilds for stable systems, it gets maintainance a hell +[20:25:13] but default is live +[20:25:24] It seems like a bad move to me. +[20:25:33] May be snapshots if it is warranted... +[20:25:38] we can make snapshots for some mis apps +[20:25:43] if they realy needed +[20:25:51] *misc +[20:26:05] well we dont give users chance to use live in stable, and if they pull kde-crazy, they have to pick consequences themselves +[20:26:27] agreed with snapshots if it is needed app +[20:26:44] <-- tbeadle_ (n=tbeadle@204.181.64.60) has quit (Read error: 60 (Operation timed out)) +[20:26:46] and what about the opposite? should we provide versioned apps in :live? +[20:26:50] i would suggest only make snapshots for things that should go into official tree +[20:26:51] and some things about kde :4.2 +[20:26:57] it needs +[20:27:03] networkmanager 0.7 +[20:27:19] well i finished nm-0.7 with blessing from rbu :] +[20:27:24] so it also needs policykit +[20:27:59] policykit is suspended for now, i spoke with gnome and they have it too, i would do it with cooperation, so we will have actualy better chance not to screw up :] +[20:28:00] also if we want to bump some stuff like kde printer applet we should have system-config apps unmasked +[20:28:31] alexxy: one problem per while man, if you throw 15 problems we should pick up on what to answer? :D +[20:28:51] let's start with the overlay situation before we discuss versioning ... +[20:28:56] scarabeus: its still one global problem +[20:29:02] deps of kde-4.2 +[20:29:02] --> tbeadle_ (n=tbeadle@204.181.64.60) has joined #gentoo-kde +[20:29:03] ) +[20:29:09] i know :D +[20:29:26] important question about stable tree: +[20:29:35] should we allow usage of +kdeprefix for stable users? +[20:29:49] i vote for no :) +[20:29:53] we had this nice discussion and i think for stable tree this feature could be disabled +[20:30:02] I always voted no... +[20:30:19] I think jmbsvicetto may have more to say here though. +[20:30:26] this fature should be use.masked +[20:30:32] I am not sure this can be decided without others here. +[20:31:00] so if people realy realy want it they should unmask this feature +[20:31:10] yup ;] +[20:31:33] Sounds like a good idea - still a shame more devs are not present if they wanted to discuss this further. +[20:31:47] alexxy: you have meeting about becoming dev tomorow right? +[20:31:53] well, in case we provide this, we could not officially support it +[20:31:53] its will look like a situation with clustered lvm extensions =) they are masked by default +[20:32:00] scarabeus: yes +[20:32:01] cryos|work: well this time i announced it properly +[20:32:20] I didn't say you didn't - you did a great job coordinating the meeting. +[20:32:20] ok i think alexxy can do bump for 4.1.4 as act of new dev :] so he try it too :} +[20:32:42] +1 +[20:32:58] cryos|work: it was supposed to sound like i am sad they didnt come even with proper anouncement... +[20:33:27] that handles in tree moves for 4.2 preparation, which is great :] +[20:33:34] heh =) i'll try +[20:33:49] also one thing for kde-testing overlay, somebody should doublecheck for missing ebuilds, in last week we added 2 completely new ones +[20:33:52] Sounds good, although make sure people are around to help/mentor ;-) +[20:34:07] scarabeus: Real life happens... I am sure jmbsvicetto would have made it if he could. +[20:34:42] yes yes he was looking forward on this meeting, he has few issues, and i think he would like to present his mysql magic ;] +[20:35:07] so who is willing to look up on kde-testing, that is important think that should not be forgoten +[20:35:23] What do you mean look up on? +[20:35:43] also i think we should sanitize deps of kde:4.2 packages +[20:35:47] You mean bump to rcs etc when they are tagged? +[20:35:57] some of deps already provided by kdelibs +[20:35:59] nope, there are missing ebuilds from dirs +[20:36:08] for example some missing games +[20:36:12] and missing applications +[20:36:22] as example bomber and kwrited +[20:36:24] so i think this deps shoul be reoved from kde-base packages since they already depend on kdelibs +[20:36:30] bomber added today +[20:36:37] kwrited yesterday +[20:36:42] tampakrap: i know, and what else is missing, that is the point +[20:36:51] oh +[20:36:52] someone has to doublecheck, cmakelists/directories +[20:37:03] you wanna do it? +[20:37:17] ok but we want two for this :) +[20:37:37] scarabeus: ok i'll oko for missing 4.2 apps +[20:37:38] =) +[20:37:43] ok so you two :] +[20:37:58] -*- alexxy uses kde 4.2 as dayly desktop] +[20:38:01] :] +[20:38:35] policykit is suspended until gnome starts working on it too as i said +[20:38:44] and one last thing regarding 4.2 +[20:38:49] there is printing dialog again +[20:38:52] written in python +[20:39:01] using system-config-bla +[20:39:02] files +[20:39:53] and something else +[20:39:55] these packages are from dberkholz whom allowed us to mess with them, i think we should start playing with this in testing +[20:40:08] and add printing later and not with bump of 4.2 +[20:40:09] -*- dberkholz highlights +[20:40:12] we should bump every kde-misc app to eapi2 in kde-testing +[20:40:15] since it wont be correctly tested +[20:40:40] tampakrap: what for, only if they use kde4-base +[20:40:50] i mentioned to scarabeus previously but not to everyone. it's very important that you bump everything before testing, because current versions are very outdated. +[20:41:03] <-- bicyclerepairman (n=sam@host86-128-227-224.range86-128.btcentralplus.com) has quit (Read error: 110 (Connection timed out)) +[20:41:22] anyone specialy interested in making this work? +[20:41:41] :( +[20:41:55] reavertm could do this but he isn't here :( +[20:42:08] he said he wont have time today +[20:42:15] he is only one properly excused :D +[20:42:41] --> mikb (n=mikb@c122-106-202-225.belrs3.nsw.optusnet.com.au) has joined #gentoo-kde +[20:42:52] ok, leave this one open and if he won't handle it, we'll announce it on g-desktop +[20:43:04] sounds good +[20:43:04] anyone has something with regards for kde4.1/4,2 what i didnt speak of? +[20:43:28] --> looonger (n=quassel@host-89-231-128-7.rawamaz.mm.pl) has joined #gentoo-kde +[20:43:35] yes +[20:43:58] should we provide versioned kde4 apps in live? +[20:44:04] <-- BCMM (n=bcmm@unaffiliated/bcmm) has quit (Remote closed the connection) +[20:44:09] or only live ones? +[20:44:14] in crazy you mean? +[20:44:27] there should be everything we think that is not mature enought +[20:44:32] for example those koffice ebuilds +[20:44:35] i mean globally +[20:44:40] what about kde-plasmoids? +[20:44:52] alexxy: you want them, you review them +[20:44:56] :D +[20:45:01] should we provide install of amarok2 in live and add block for amarok-live? +[20:45:01] --> tgurr (n=tgurr@gentoo/developer/tgurr) has joined #gentoo-kde +[20:45:01] ohhh +[20:45:01] *** Mode #gentoo-kde +o tgurr by ChanServ +[20:45:08] and what about sets +[20:45:13] in off tree? +[20:45:27] in off tree we can use them as we want i think +[20:45:39] for tree we have to prepare metas, which will be done with 4.2 bump +[20:45:58] can we add sets to off tree? +[20:46:16] why not +[20:46:18] or this will be done only after stabilazing portage-2.2? +[20:46:37] btw i'll write the guide for 4.2 and live this time for real :) +[20:46:53] ok writing it up to summary :] +[20:46:54] --> undetected (n=laika@27.138.45.66.cm.sunflower.com) has joined #gentoo-kde +[20:47:16] we can't put any sets in the official tree, but you can provide sets for them in the overlay +[20:47:25] as said yngwin +[20:47:39] for now we have to live with metas and be happy with eapi2 +[20:47:41] guys, why don't you put the direct url for each kde application instead of the generic www.kde.org? i mean, let's take for example marble, it's homepage is set to www.kde.org, but i think it would be 100 times better to put its own homepage ( http://edu.kde.org/marble/ ). so one interested to marble don't go to the kde homepage, but to its own. what do you think? +[20:48:08] --> jbrouault (n=jbrouaul@ARennes-552-1-79-210.w92-135.abo.wanadoo.fr) has joined #gentoo-kde +[20:48:18] xdmx: open bug and give us ebuilds and correct urls, up to then kde.org will be used, we wont search web for them i guess :] +[20:48:41] or we could use edu.kde.org for example +[20:48:47] scarabeus: http://nopaste.com/p/aHK4XLra6 this is a first one (some are to recheck because unmantained, i don't know if it's better to set directly the usertech site for some..) :) +[20:49:32] wow :] is anyone willing to do this? i am pretty sure i wont have itme for it, so i can only mark it as long term :] +[20:49:54] bonsaikitten: you dont wana use your regexp skillz? +[20:50:44] scarabeus: meh. maybe. if noone else can be coerced :) +[20:51:02] i guess it looks you are only one left with nothing assigned +[20:51:13] scarabeus: you too :) +[20:51:31] nope i am with putting eclasses to the tree and fixing all ebuilds +[20:51:37] :) +[20:51:38] i think it is pretty annoymarble -> http://edu.kde.org/marble/ +[20:51:38] kbounce -> http://games.kde.org/game.php?game=kbounce +[20:51:38] kbreakout -> http://games.kde.org/game.php?game=kbreakout +[20:51:38] kdiamond -> http://games.kde.org/game.php?game=kdiamond +[20:51:38] kgoldrunner -> http://games.kde.org/game.php?game=kgoldrunner +[20:51:38] klines -> http://games.kde.org/game.php?game=klines +[20:51:38] kolf -> http://games.kde.org/game.php?game=kolf +[20:51:38] kollision -> http://games.kde.org/game.php?game=kollision +[20:51:38] ksame -> http://games.kde.org/game.php?game=ksame +[20:51:38] kspaceduel -> http://games.kde.org/game.php?game=kspaceduel +[20:51:38] kbattleship -> http://games.kde.org/game.php?game=kbattleship +[20:51:38] kmahjongg -> http://games.kde.org/game.php?game=kmahjongg +[20:51:38] kreversi -> http://games.kde.org/game.php?game=kreversi +[20:51:38] kshisen -> http://games.kde.org/game.php?game=kshisen +[20:51:38] kfourinline -> http://games.kde.org/game.php?game=kfourinline +[20:51:43] crap +[20:51:46] what did i push +[20:52:02] hm +[20:52:04] interesting +[20:52:12] lol +[20:52:28] please pastebin don't spam the channel +[20:52:31] grrr +[20:52:35] lmao +[20:52:51] second time today quassel pasted when i didnt push that damn button :D +[20:53:15] scarabeus: cause you text contains newlines +[20:53:36] alexxy: i didnt write it i marked it from buffer and put into my editor +[20:53:38] not here +[20:53:41] i think this is everything about 4.1/4.2 +[20:53:46] yes /me too +[20:53:53] anyone has something in regards for that +[20:54:06] guess not +[20:54:21] tgurr: your ebuild in genkdesvn for that pdf in scribus is broken, take look on fixed one in kde-crazy +[20:54:35] ok we get to qt4 yngwin, you have something interesting there? +[20:54:42] yes +[20:54:50] i have several recruits now +[20:55:00] so it's starting to look good :) +[20:55:21] :) +[20:55:22] hwoarang is doing good work on qt4-build.eclass +[20:55:23] <-- Psychey (n=me@1x-193-157-193-9.uio.no) has quit (Success) +[20:55:25] scarabeus: not my biggest problem atm ;) kernel is also broken on 2 machines here ... +[20:55:28] ah hold on +[20:55:37] yngwin and everybody +[20:55:50] qt4-build class needs to be ported on EAPI2 standards +[20:55:55] yngwin: great you should sent the other aprentices here too so we can meet them :] +[20:56:03] this means that qt-4.4.9999 live ebuilds +[20:56:06] need to change too +[20:56:07] yes, i think sping came by the other day +[20:56:10] hwoarang: i guess on that you should use reavertm, he has great insight :] +[20:56:27] he's one of the qt-creator devs +[20:56:44] ok scarabeus. will talk to him +[20:56:48] so, we have been squashing qt4 bugs +[20:56:56] but qt ebuilds should move to qt overlay when it is ready +[20:57:13] i dont feel comfortable to play on kde-crazy :D +[20:57:18] i agree with this +[20:57:29] yes, we should have the qt overlay up and running in a few days +[20:57:44] hwoarang: we dont bite ;D +[20:57:47] then we'll push stuff to kde-testing/crazy when they're ready +[20:57:56] scarabeus: we do :p +[20:58:02] :D +[20:58:13] yngwin: dont forget to upload kde-teams keys if you want us to help you ;] +[20:58:35] yes, i'll look into that once it's really up +[20:58:47] :] +[20:59:02] another thing, i want to stabilize qt 4.4.2 +[20:59:10] first split ebuilds version to go stable +[20:59:15] i volte yes :] +[20:59:24] <-- hvengel (n=hvengel@astound-66-234-194-11.ca.astound.net) has quit (Read error: 145 (Connection timed out)) +[20:59:38] note: new kde4 eclasses specialy depends on splited qt ebuilds, i dropped the old mono qt stuff +[20:59:55] i wrote a migration guide, because i've seen many problems, but according to jkt and zmedico it should go smooth now +[20:59:55] you need some help there from us or bug is filled and all is going fine? +[21:00:42] well, i need a stable system with qt-4.3 and PyQt4, then test if keywording 4.4 ebuilds and masking 4.3 really gives a smooth upgrade path +[21:01:18] hm, read as: ANYONE ON STABLE HERE? ;] +[21:01:26] whats that? :P +[21:01:26] -*- tampakrap +[21:01:36] so i was planning to test that in a chroot tonight otherwise +[21:02:01] -*- alexxy uses ~arch ( read as ~amd64 ~x86 ~mips and ~arm) +[21:02:03] ok you two can talk it out, it is up to you :] +[21:02:07] tampakrap: you have qt-4.3 on there? +[21:02:24] no but i can downgrade 4.4 isn't even needed in this one +[21:02:42] ok, we'll talk about that after the meeting then +[21:03:03] ook +[21:03:41] another item is qt-embedded has not been receiving any love +[21:03:58] but i probably should speak to embedded people about that +[21:04:32] there i guess we are not much able to help :] only if as embedded can be count some cluster ;] +[21:05:36] he he =) +[21:06:11] yngwin: btw i looked on hwoarangs eom today and give him notes, i guess when he incorporate the updates he will pass review from recruiters so you will get new coleague :] +[21:06:23] and i need to get a pythonista to mentor me a bit wrt ebuilds using python (mostly PyQt4 packages) +[21:06:34] qt-embedded = Qt Extended now? +[21:06:36] scarabeus: great +[21:06:44] or what is that supposed to be? +[21:07:03] seems qt extended +[21:07:06] yngwin: when you are on pyqt take creepy look on pykde on the route i think :] +[21:07:14] yngwin: I can try to help with python things +[21:07:15] since qt embedded was renamed to it +[21:07:20] Sput: yes, qt-extended / qtopia +[21:07:27] k +[21:07:46] -*- Sput would like to have a Gentoo way of installing the Qtopia SDK +[21:07:55] scarabeus: i'll do what i can +[21:08:00] :] +[21:08:03] bonsaikitten: great +[21:09:12] --> hvengel (n=hvengel@astound-66-234-194-11.ca.astound.net) has joined #gentoo-kde +[21:09:19] now i would like to know what is state of that mysql issue, but we are out since only guy working on it is jmbsvicetto so this note will be added to the summary additionaly, i would really like to have amarok2 on amd64 with kde4.2 bump +[21:09:45] <-- St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has quit (Read error: 54 (Connection reset by peer)) +[21:09:50] --> St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has joined #gentoo-kde +[21:09:53] -*- cryos|work would love to see amarok 2, but thinks the move to MySQL as the *only* backend wasn't good... +[21:10:07] indeed +[21:10:17] --> neyz (n=neyz@ram94-6-82-242-23-69.fbx.proxad.net) has joined #gentoo-kde +[21:10:22] they are going to import others too +[21:10:25] i wonder why they couldn't use qt-sql interface, which can use various DBs +[21:10:43] because *censored* *censored* *censored* +[21:11:56] I am going to need to pay less attention to this meeting and more to work now... +[21:11:57] no they are not going to import others +[21:12:01] it'll stay mysql only +[21:12:07] ok, so we need to wait for feedback from jmbsvicetto on this +[21:12:08] I heard they weren't either, but don't know. +[21:12:41] I really question the intelligence of using such a heavy weight dep for a music player as the only option though. +[21:12:58] -*- yngwin just uses mpd +[21:12:58] I am not about to go trolling, but think it is a step backwards. +[21:13:15] well most of packagers think that it is step back +[21:13:25] what for fully fledged mysql on desktop machine +[21:13:29] In Avogadro we very carefully consider even optional deps, required deps even more so. +[21:13:43] from my own experience I claim that being unable to use sqlite is a sign of bad design +[21:13:45] I don't want to have to install things like MySQL on my EeePC... +[21:13:52] they're censoring the chatroms! protest! +[21:13:53] mysql only pseudoproffesional db :( +[21:13:55] it can handle millions of items, why can't it handle 6k songs? +[21:14:05] scarabeus: be quiet please :D +[21:14:09] sqlite can's work remotely though +[21:14:12] *can't +[21:14:13] 6k should be enough for anybody +[21:14:22] amarok upstream is not willing to maintain more than one backend +[21:14:27] Sput: uhm ... yeah ... let me just stab you a bit +[21:14:30] bonsaikitten: well i am doing some things as db specialist, so i know what is good db, and mysql never was such thing :D +[21:14:32] -*- yngwin has 21k +[21:14:34] Why do I care if it can work remotely? +[21:14:43] and yes, they didn't properly design their db access :p +[21:14:52] thanks to embeded, they need to run on local machine which is also great +[21:14:53] :D +[21:14:53] scarabeus: I've worked with sqlite and currently have >50 MySQL servers to babysit +[21:14:59] cryos|work: many people share their db over several instances +[21:15:07] bonsaikitten: hope you enjoy it :] +[21:15:10] cryos|work: I have a central file server, and with amarok1 I used to have a central database +[21:15:11] Yeah, but everyone? +[21:15:18] I like Amarok 2.0. +[21:15:19] I certainly don't. +[21:15:23] scarabeus: I could tell you things, but then I'd have to shoot me +[21:15:30] :D +[21:15:31] <-- Aw0L (n=awol@mx1.spfldsparc.org) has quit (Read error: 104 (Connection reset by peer)) +[21:15:31] <-- St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has quit (Operation timed out) +[21:15:35] I loved amarok, love the look of amarok 2. +[21:15:37] is this a good time to mention that I'd like koffice snapshots in kde-testing? +[21:15:41] We are drifting off topic though. +[21:15:44] hey i found one non flame topic +[21:15:49] MONO bindings in kde4 +[21:15:50] ok, before this becomes a flamefest, anything else on meeting? +[21:15:54] do we ship them or not? +[21:15:59] MONO is inherntly bad. +[21:16:01] no +[21:16:06] i volte for no +[21:16:09] !herd mono +[21:16:14] but if they will do them... +[21:16:18] there is no mono herd? +[21:16:25] lol +[21:16:26] I would go with no unless someone really wants to do it themselves. +[21:16:27] do we have any apps that use them? +[21:16:44] !herd dotnet +[21:16:45] scarabeus: (dotnet) compnerd, jurek, loki_val +[21:16:58] ok i will ask them if they want to create them :] +[21:17:04] haha +[21:17:04] otherwise they wont be shipped then +[21:17:16] scarabeus: ? +[21:17:52] loki_val: if you want kde-mono bindings +[21:17:53] loki_val: we have mono bindings in kde4, and nobody here uses mono, are you interested in it? +[21:18:42] I use only kde3 +[21:18:58] so it's dead :) +[21:19:05] Sometime when kde4 works for me, perhaps. +[21:19:05] so its dead :] +[21:19:16] loki_val: ok i will write suspended for now :] +[21:19:28] --> Vash63 (n=quassel@ip68-2-28-213.ph.ph.cox.net) has joined #gentoo-kde +[21:19:31] did we discuss the overlay situation already? +[21:19:32] bonsaikitten: ? +[21:19:39] afaik no +[21:19:45] might be a good time now :) +[21:19:45] nope i leave it on last thing +[21:19:50] because ti will be flame again +[21:19:54] i have one last thing +[21:19:59] no but we can't without jmbsvicetto and reavertm +[21:20:15] you know how we handle linguas in kde ebuilds +[21:20:24] how about move this magic to cmake-utils eclass +[21:20:29] so every cmake ebuild can use it +[21:20:40] agree +[21:20:51] How come kde-base/kde-l10n isnt in @kdebase? +[21:20:54] actually, i think there should be a generic linguas eclass +[21:20:59] ni1s: it is in @kde +[21:21:10] yngwin: well i write most abstract cmake stuff +[21:21:22] if some autotools mage wants to step in and write the same for autotools +[21:21:24] ok, that could be a start +[21:21:39] scarabeus, yeah, but it feels very baseish +[21:21:59] ni1s: it is not base requirement for system, and some people dont want it at all +[21:22:35] <-- gyama (n=gyama@89.143.147.33) has left #gentoo-kde +[21:22:41] scarabeus, ah ok +[21:23:00] ok i suspend the move to cmake utils eclass for now +[21:23:05] lets see how time evolve then :] +[21:23:14] i will try to talk someone to try it on autotools :] +[21:23:33] ok now we get to highly awaited topic +[21:23:52] too many overlays someone says :] merge kde-testing to kde-crazy or keep them splitted +[21:23:53] overlays? +[21:24:00] i personaly want them splitted like they are +[21:24:04] merge +[21:24:08] --> ivanich (n=ivanich@ivanich.tenet.odessa.ua) has joined #gentoo-kde +[21:24:10] cryos|work said we should define a policy +[21:24:11] split +[21:24:20] there's too many changes that don't get applied to the other +[21:24:27] but it is hard to maintain and sync changes between reavertm and alexxy :) +[21:24:43] that is good point +[21:24:45] yes +[21:24:53] but what about users that want only test something that is almost ready +[21:24:59] split feels better assuming the eclasses are always in sync (or different per overlay) +[21:25:00] we should use package masks? +[21:25:00] so we should efine policy for commiting tio overlays +[21:25:18] yes it is easier to maintain this way +[21:25:23] since no one merge changes from one overlay to other if he commit something +[21:25:32] personally my main duties was the syncing +[21:25:37] *were +[21:25:42] we can have merging supervisor ;] +[21:25:47] tampakrap was great one :D +[21:25:55] but didn't want to :) +[21:25:57] merge +[21:26:18] depends how much syncing is needed +[21:26:26] to my mind its better to merge overlays again +[21:26:29] quite much +[21:26:41] well i like the split only from users view +[21:26:43] then i can imagine having 1 overlay would be better +[21:26:43] and keep live stuff masked + unkeyworded +[21:26:53] just keep live unkeyworded +[21:27:06] only hardmask stuff that is known not to work +[21:27:08] if we are able to make visible only mature stuff for users which first checkout +[21:27:10] i am for merge too +[21:27:21] two overlays is realyhard to maintain +[21:27:25] profile.mask is the solution +[21:27:32] no +[21:27:44] -*- cryos|work was getting coffee and doing work... +[21:27:59] kde-testing stuff can go ~arch, and crazy stuff unkeyworded +[21:28:00] scarabeus: we can mask all live stuff +[21:28:07] live stuff is already masked +[21:28:08] right +[21:28:14] ok that sounds reasonable +[21:28:16] no it isn't +[21:28:29] it isn't hardmasked i mean +[21:28:31] If it is unkeyworded it is enough. +[21:28:32] about masking +[21:28:39] oh +[21:28:42] my bad +[21:28:47] You have to specially keyword and checkout an overlay. +[21:28:50] its better to have live stuff p.masked also +[21:28:58] If it makes you happy. +[21:29:02] :D +[21:29:04] alexxy: why? unkeywording is enough +[21:29:14] unkeywording is indeed enought +[21:29:21] no it isn't +[21:29:21] i have to drink my cure, brb +[21:29:28] in case of phonon it isn't +[21:29:34] yngwin: its too easy for user to unmask live stuff by error +[21:29:36] It is already in an overlay, and has no keywords. You have to specifically keyword **/ +[21:29:46] <-- Vash63 (n=quassel@ip68-2-28-213.ph.ph.cox.net) has quit (Read error: 54 (Connection reset by peer)) +[21:29:46] It isn't too easy. +[21:29:47] people symlink everything and live phonon gets installed in snapshots' machines +[21:29:52] alexxy: they need to specifically add ** keyowrds +[21:29:57] If it makes you happy and you stop bickering you can mask it too. +[21:29:59] <-- hvengel (n=hvengel@astound-66-234-194-11.ca.astound.net) has quit (Connection timed out) +[21:30:07] --> hvengel (n=hvengel@astound-66-234-194-11.ca.astound.net) has joined #gentoo-kde +[21:30:10] I think it is overkill though. +[21:30:13] symlinking unmask is easy too +[21:30:19] yeah but they symlink the whole p.keywords folder even if i splitted it for every version +[21:30:29] that is users fault +[21:30:34] the solution is a clear guide then +[21:30:35] --> St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has joined #gentoo-kde +[21:30:39] yes +[21:30:41] not two overlays +[21:30:46] You cannot prevent stupid users from doing stupid things. +[21:30:57] Just provide a clear path and reasonable policies. +[21:31:02] indeed +[21:31:05] --> Vash63 (n=quassel@ip68-2-28-213.ph.ph.cox.net) has joined #gentoo-kde +[21:31:14] It is too easy for a user to type rm -rf / +[21:31:21] lol +[21:31:21] :D +[21:31:24] lol +[21:31:30] cryos|work: this wil not work =) +[21:31:34] cryos|work: so what is your merge/split statement :D +[21:31:42] i mean rm -rf / will not work +[21:31:48] =) +[21:31:53] [ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo "You live" +[21:31:53] I would merge, but don't mind too much. +[21:32:01] brb +[21:32:09] rm -rf /* then? +[21:32:11] ok so far the voltes are: +[21:32:18] yngwin: merge +[21:32:18] kitten: merge +[21:32:18] scarab: merge +[21:32:18] tampakrap: merge +[21:32:18] reavertm: merge +[21:32:18] alexxy: merge +[21:32:18] cryos: dont mind merge +[21:32:22] Still to easy... +[21:32:31] so i guess we will again have one overlay :D +[21:32:33] also sput merge +[21:32:34] I would go with, but won't cry if you don't ;-) +[21:32:46] Hi +[21:32:48] :D +[21:32:51] Hey - he's here! +[21:32:53] HELLOOOOO +[21:32:56] sorry guys, but I've been tied up at work :\ +[21:32:57] hi! +[21:32:57] it's alive!!!!! +[21:33:08] its moving, RUN :D +[21:33:11] ok meeting is over we have one overlay end of the story bye +[21:33:13] I'm very sorry, but I had expected to be free for the meeting +[21:33:15] I need to mostly disappear and get some work done... +[21:33:30] Sorry I missed you jmbsvicetto. +[21:33:43] -*- cryos|work out - will read ML summary if there is one... +[21:33:43] I'll have to grab dinner in around 15 minutes. Is there anything I can clear up / explain / detail ? +[21:33:50] cryos|work: Hi. I'm sorry too +[21:34:09] jmbsvicetto: Life happens. We tried not to steam roll stuff ;-) +[21:34:27] I do need to go though. +[21:34:30] jmbsvicetto: we were volting about merge/split overlays and all volted for merge or dont mind merge :D +[21:34:54] About the tasks I was expected to do from the last meeting: 1. mysql - I'm stuck at the patch in the bug - I wasn't able to do more yet. 2. contact people to check whether they want to be in the kde team - I'm sorry, but I didn't got this done. +[21:35:01] cryos|work: hehe +[21:35:03] cryos|work: later +[21:35:11] :D +[21:35:20] scarabeus: ok, so my vote would have lost +[21:35:27] --> tinytony_ (n=tinytony@77.53.34.198) has joined #gentoo-kde +[21:35:37] scarabeus: what was the 3rd task I had to do? +[21:35:37] jmbsvicetto: ok for the mails i guess you will do it in future so no biggie in that +[21:35:54] jmbsvicetto: the third one i did instead of you +[21:35:55] :D +[21:36:09] Yeah, I'll try to get it done this week. I can also tell you some of them are under undertakers notice +[21:36:16] scarabeus: what was it? +[21:36:20] scarabeus: eclasses? +[21:36:23] eapi2only eclasses +[21:36:25] which i handled +[21:36:37] scarabeus: Thanks and sorry for leaving it up to you +[21:36:52] no problem really, i had time so i did it :] +[21:36:58] at least i know the eclass pretty well :] +[21:37:04] hehe +[21:37:15] scarabeus: want to know mysql "intimately"? ;) +[21:37:18] are we ok with moving eclasses to the tree? +[21:37:28] back +[21:37:44] looks like i will do it on saturday i guess +[21:37:46] scarabeus: I noticed reavertm seemed to find a bug in the eclasses related to the blocks +[21:37:48] tampakrap: ^ +[21:38:00] Were you able to sort that out? +[21:38:02] jmbsvicetto: ok one bug, needs to be fixored +[21:38:10] jmbsvicetto: he didnt tell me a thing +[21:38:20] btw I even think that merging the overlays is less confusing for users than the current state, where they always need to ask around which overlay contains what +[21:38:21] I think he sent a mail to the desktop alias +[21:38:32] there should be only one official gentoo KDE overlay one can point people +[21:38:35] Sput: I also didn't do the blog entry :\ +[21:38:40] oh i see +[21:38:50] jmbsvicetto: which blog entry? +[21:38:57] btw alexxy has review tomorow in case you dont know +[21:39:03] The one I was going to explain it (the overlays) +[21:39:08] scarabeus: I didn't +[21:39:10] alexxy: Good luck :) +[21:39:18] jmbsvicetto: thanks +[21:39:19] =) +[21:39:35] and i guess we should pronounce the meeting over uness jmbsvicetto has something new he wants to adres +[21:39:42] alexxy: I'm going to be busy tonight, but if you want / need to ask something, poke me until I reply ;) +[21:39:42] oh missing letters, shame on me +[21:39:55] scarabeus: No, nothing to add +[21:40:14] unit DISMISS! \ No newline at end of file diff --git a/meeting-logs/20090212-summary.txt b/meeting-logs/20090212-summary.txt new file mode 100644 index 0000000..288437c --- /dev/null +++ b/meeting-logs/20090212-summary.txt @@ -0,0 +1,34 @@ +KDE PPLE AROUND: +alexxy, tampakrap, wired, hwoarang, scarabeus, yngwin, Sput, jmbsvicetto, reavertm, krytzz, +EXCUSED: +cryos, deathwing00, tgurr +NOT EXCUSED: +the rest :P + +Review of previous: +update for 4.2 went ok. Some minor issues :] +there is missing review for pyqt/pykde and printing stuff, that will be deffered until somebody step up for the fixing/testing. + +This one: +droping of 4.1. - tampakrap + +voting for leader -> jmbsvicetto, he get 7 voltes from devs (alexxy, tampakrap, hwoarang, scarabeus, yngwin, deathwing00) rest is not around so deal with it :] +all hail to the new leader jmbsvicetto :P + +prefixing and using multiple versions of the kde in one prefix -> cooperation with upstream +installing libs and things versioned and use eselect to pick the one we want... +read the log around 21:30 and keep going for this one +jmbsvicetto, reavertm, maybe somebody more + +3.5 - dropping the old .7 and .8 +poke archies about stabling and checking keywords on .9 +alexxy is going to do this one + +patches sharing with other distros +new patching glep, help wanted and i welcome any critic on current state (on mail until i anounce on -dev). +http://dev.gentoo.org/~scarabeus/patches-glep.html +scarabeus + +pykde - needs love, unprefixing probably, who will do it? + +and more and more... \ No newline at end of file diff --git a/meeting-logs/20090212.txt b/meeting-logs/20090212.txt new file mode 100644 index 0000000..f8d29e5 --- /dev/null +++ b/meeting-logs/20090212.txt @@ -0,0 +1,761 @@ +21:00 <@scarabeus> ok sunshines, meeting time :P +21:00 <@hwoarang> is it time? +21:00 <@scarabeus> !herd kde +21:00 * yngwin kicks Willikins +21:00 <@scarabeus> i am going to hurt willikins... +21:00 <+wired> lmao +21:00 <@hwoarang> fail? +21:00 <+MrRat> wired: do you know the amarok qt-4.5 bug at all? +21:00 <@hwoarang> errr meeting time +21:00 <+wired> yeah i read a bug you posted earlier about a missing line +21:01 <@yngwin> i'll use this clone here +21:01 <@scarabeus> :] +21:01 <@hwoarang> ok who broke Willikins +21:01 <@scarabeus> but i want that herd +21:01 <@scarabeus> !herd kde +21:01 < arachnist> hwoarang: i did +21:01 < arachnist> ;) +21:01 <+MrRat> wired: http://rafb.net/p/g1msai72.html +21:01 <@scarabeus> !herd qt +21:01 <@hwoarang> :D +21:01 <+wired> !herd kde +21:01 <@scarabeus> ok the other route +21:01 <+wired> ^_^ +21:01 <+MrRat> wired, thats it, just one line +21:02 <+wired> alright - does that work with 4.4.2 as well? +21:02 <+MrRat> wired: but the file is not generated until about 10% of the build when qtscriptgenerator runs +21:02 <@scarabeus> alexxy, bonsaikitten, cryos, hwoarang, jmbsvicetto, keytoaster, tampakrap, yngwin, dagger_, krytzz, MrRat, reavertm, Sput, wired +21:02 <@scarabeus> meeting +21:02 <@scarabeus> who is around +21:02 * alexxy here +21:02 * tampakrap +21:02 * wired ^_^ +21:02 <+Sput> see above +21:02 * hwoarang * +21:02 * yngwin is a square +21:03 <+MrRat> wired: so when the file is generated, i can edit it and back out of the directory and build is success +21:03 <+krytzz> that joke is OLD :p +21:03 * reavertm reporting +21:03 <@jmbsvicetto> Sput: You're missing people :P +21:03 * jmbsvicet waves hand +21:03 <@yngwin> krytzz: so am i ;) +21:03 <+wired> MrRat: i see +21:03 <+Sput> I'm what? +21:03 <+Sput> mostly I'm missing alcohol and inspiration right now +21:03 <@jmbsvicetto> Sput: Not in FOSDEM? ;) +21:03 <+wired> MrRat: i'll check it out after the meeting +21:04 * yngwin notes that caleb and carlo are missing as usual +21:04 <@scarabeus> ok so are we waiting on somebody else +21:04 <@scarabeus> i wrote carlo a mail +21:04 <@scarabeus> asking him to drop at least for volte :( +21:04 <@tampakrap> cryos also said he will probably be away +21:04 <+wired> we'll give him the logs ^_^ +21:05 <@scarabeus> i know about those missing i am asking if we are waiting on somebody more? +21:05 <@yngwin> bonsaikitten? +21:05 <@scarabeus> yup right +21:05 <@scarabeus> this one i would like to see :P +21:05 <@scarabeus> !lastspoke bonsaikitten +21:06 <@scarabeus> ok that bot actualy dont work now +21:06 <@hwoarang> stupid bots +21:06 -- rangerpb- is now known as rangerhomezzz +21:06 <@scarabeus> ok i give him 4 minutes (agreed?) +21:06 <@tampakrap> ok +21:06 <@hwoarang> k +21:06 <@tampakrap> should i call him? :) +21:06 <@scarabeus> so he has 10 minutes after meeting start to show up :] +21:06 <@scarabeus> :D +21:07 <@alexxy> ok +21:07 <@alexxy> bonsaikitten: !~!!! +21:07 <+krytzz> we count to ten, then shout as loud as we can +21:07 < kev009> what does use=raster for qt-gui? +21:07 <+wired> speeds things up +21:07 <+MrRat> kev009: speed! +21:07 <@scarabeus> krytzz: i would wake teh kids +21:07 <+krytzz> kev009 but breaks compositing :p +21:08 * hwoarang walks around +21:08 * scarabeus prepares editor and stuff for volting and so on :] +21:09 <@hwoarang> time is up +21:09 * wired is building live qt and kde ^_^ +21:10 <@scarabeus> actualy 50 secs +21:10 <@scarabeus> now up +21:10 <@scarabeus> ok +21:10 < kev009> krytzz: is there a document that expalins how compositing breaks? +21:10 <+reavertm> kev009 later please +21:10 <@scarabeus> i officialy start february gentoo kde meeting in year 2009 +21:10 <@scarabeus> :} +21:10 <@scarabeus> so first subject is review of old one +21:11 <@scarabeus> i think we did great job with 4.2 and we deserve some cookies :] +21:11 <@scarabeus> only thing that is missing from last month summary is pyqt/pykde and printing +21:11 <+krytzz> yeah, it was great +21:11 <@scarabeus> so how is the printing status reavertm +21:11 <@scarabeus> only testing needed or some more coding? +21:11 <+reavertm> printing status - it's reportedly working fine +21:12 <@tampakrap> so can we add it to the tree? +21:12 <+reavertm> we need maintainer +21:12 <@scarabeus> ok process will be 1 week in overlay, and then the main tree +21:12 <@scarabeus> reavertm: that is no problem +21:12 <@scarabeus> we are kde herd +21:12 <@scarabeus> we became maintainer +21:12 <@tampakrap> right +21:12 <+reavertm> system-config-printer and pycups are part of leftwovers after Donnie +21:12 <@scarabeus> i know +21:13 <+reavertm> they are straight dependecies for out printing kde stuff +21:13 <@scarabeus> but if it is fixed and working for us we canmaintain +21:13 <@scarabeus> ok there are no issues, so feel free to remove the mask from it in overlay :] +21:13 <@alexxy> scarabeus: also we should unmask networkmanager/policykit +21:13 <+reavertm> and there is one new ebuild that possibly needs to be perfected with some python deps as well - hal-cups-info (in overlay) +21:13 <@scarabeus> alexxy: that is negative my friend +21:13 <@scarabeus> we get to that +21:13 <@tampakrap> we can also start maintaining them and ask in -dev if there are any others intrested in maintaining +21:13 <+reavertm> (it's printer-applet dep) +21:13 <@jmbsvicetto> We could ask the printing herd if they want to co-maintain it +21:13 <@scarabeus> jmbsvicetto: there is no printing herd +21:14 <@scarabeus> really i looked +21:14 <@scarabeus> they are mostly dead +21:14 <@jmbsvicetto> ok +21:14 <@jmbsvicetto> Where's tgur? +21:14 <@yngwin> paper is so last century :p +21:14 <@scarabeus> i have no clue +21:14 <@tampakrap> !seen tgurr +21:14 < Willikins> tampakrap: tgurr was last seen 6 days, 16 hours, 49 minutes and 14 seconds ago, quitting IRC (Remote closed the connection) +21:14 < Philantrop> jmbsvicetto: Health troubles. +21:14 <@jmbsvicetto> Philantrop: ok, thanks for the info +21:14 <@tampakrap> Philantrop: thanks +21:14 <@jmbsvicetto> Philantrop: Do you know if he's still interested in printing packages? +21:15 < Philantrop> jmbsvicetto: Mostly in cups and friends, yes. +21:16 <@scarabeus> ok in that case reavertm should speak to him :] +21:16 <@scarabeus> ok we can wait with printing on him :] +21:16 <@scarabeus> hope his sickness is not serious and he will get well soon :] +21:18 <@scarabeus> ok one more question for the last meeting +21:18 <@scarabeus> did somebody sent that mail about kde3? +21:18 <@yngwin> i havent seen any +21:18 <@scarabeus> that we actualy ask for help on them +21:18 <@scarabeus> tampakrap: so it will be your responsibility i guess +21:18 <@tampakrap> ok +21:19 <@tampakrap> i'll also talk with carlo about this +21:19 <@jmbsvicetto> oh, there was a user that had a comment in my blog entry pleading for us not to drop kde3 +21:19 <@scarabeus> we are not droping it :] +21:19 <@scarabeus> at least for now :] +21:19 <+reavertm> we're droping 4.1 :) +21:19 <+reavertm> (are we?) +21:19 <@scarabeus> and next year i guess +21:19 <@scarabeus> yup we are +21:19 <@scarabeus> as said reaver +21:19 <@scarabeus> anyone is against it? +21:20 <@scarabeus> i wolte for drop :] +21:20 <@hwoarang> +1 +21:20 <@tampakrap> drop +21:20 <+reavertm> kill it +21:20 <+wired> farewell +21:20 <@yngwin> 4.1? yes +21:20 <+Sput> +1 +21:20 <@scarabeus> 4.1 drop are we speaking about :] not the 3.5 :] +21:20 <@scarabeus> yngwin: ^ +21:20 <@yngwin> :) +21:20 <+wired> nobody will miss it anyway ^_^ +21:20 <@jmbsvicetto> bye bye 4.1 +21:20 < termite47384> hwoarang, MrRat: amarok fix0red? +21:20 <@scarabeus> ok super +21:21 <@hwoarang> termite47384 will get to it +21:21 <+Sput> absolutely no need to keep that one around +21:21 <@scarabeus> soo what is on schedule? ah jmbsvicetto you are :] +21:21 < termite47384> sorry, I was away and wasn't sure if you had already +21:21 <@hwoarang> \o/ +21:21 <@jmbsvicetto> scarabeus: :P +21:21 <@scarabeus> btw who will do the drop +21:21 <@scarabeus> alexxy: ? +21:21 <@jmbsvicetto> 4.1? +21:21 <@scarabeus> yup +21:21 <@scarabeus> the drop +21:21 <@tampakrap> may I? +21:21 <@jmbsvicetto> sure +21:21 <@scarabeus> tampakrap: if you want :] +21:21 <+reavertm> still we need to sort packages that may explicitly depend on it +21:22 <+reavertm> so called kde-misc +21:22 <@scarabeus> there are none in the tree :] +21:22 <@tampakrap> of course +21:22 <@scarabeus> tested/fixed +21:22 <+wired> there are +21:22 <+wired> i.e. lancelot-menu +21:22 <@tampakrap> let's double check to be sure +21:22 <@scarabeus> only the powerdevil and lancelot +21:22 <@scarabeus> :] +21:22 <@scarabeus> ok +21:22 <@scarabeus> lets go and volte the leader as we promised +21:22 <@scarabeus> jmbsvicetto: looks like you are the only aplicant +21:22 < Philantrop> *VOTE*. It's *vote*. +21:23 <@tampakrap> i'll drop it in weekend as i'll be away tomorrow (exams) +21:23 <@scarabeus> typo is still the typo +21:23 <+MrRat> The volte is a very small circle that is used in the training of a horse +21:23 <+MrRat> :) +21:23 <+reavertm> could anyone nlighten me, what exactly is this voting for? +21:23 <+wired> o_o MrRat +21:23 <@scarabeus> reavertm: kde team leader +21:23 <@scarabeus> gentoo kde team leader +21:24 <+reavertm> ah, I got confused with Donnie stepping out from desktop lead +21:24 <@scarabeus> so jmbsvicetto why we should volte for you, some promotial i guess :] +21:24 <+reavertm> *down +21:24 <@scarabeus> again +21:24 <@scarabeus> why the crap i write volte +21:24 <@scarabeus> i know it is vote :P +21:24 < dberkholz> well. i can't really step out till someone else steps in +21:24 < dberkholz> till then, i make a great figurehead +21:24 <@yngwin> :) +21:25 <@scarabeus> :D +21:25 <@jmbsvicetto> scarabeus: hmm, because you were impressed with me in FOSDEM? ;) +21:25 <@scarabeus> :] +21:25 <+reavertm> ok, +1 on Jorge +21:25 <@yngwin> +1 +21:26 <@alexxy> scarabeus: yep =) i can drop 4.1.x +21:26 <+krytzz> i dont know if i have the right to vote but, +1 +21:26 <+Sput> _1 +21:26 <@scarabeus> alexxy: too late :] +21:26 <+Sput> eh +21:26 <+Sput> +1 +21:26 <@hwoarang> +1 +21:26 <+wired> +1 +21:26 <@alexxy> and i vote for jmbsvicetto to be kde lead +21:26 <@scarabeus> actualy it counts only from devs :} +21:26 < rane> gratz jmbsvicetto +21:26 <@scarabeus> but i suggest the other way +21:26 <@jmbsvicetto> dberkholz: You make much more than a figurehead, but we're very happy with your figurehead ;) +21:26 <@scarabeus> who is against +21:26 <+Sput> meh, I can still give my moral support :) +21:26 <@jmbsvicetto> rane: :) +21:27 <@jmbsvicetto> scarabeus: you might want to count the positive votes ;) +21:27 <@scarabeus> and ftr i volte for him too +21:27 <@jmbsvicetto> scarabeus: hehe (volte) ;) +21:27 <@tampakrap> jmbsvicetto++ +21:27 * Sput applies 240 volts to scarabeus +21:27 <@scarabeus> sdamn +21:27 <+wired> lmao +21:27 <+MrRat> haha +21:27 <@scarabeus> ok you have 5 votes now +21:27 <+wired> beat a typo with a typo, thats something ^_^ +21:28 <@jmbsvicetto> scarabeus: Don't know if you want to count deathwing00's vote +21:28 <@scarabeus> oh right 6 +21:28 <+MrRat> +1 +21:28 <+MrRat> count me +21:28 <@scarabeus> hwoarang: ping dude +21:28 <@hwoarang> i did say +1 +21:29 <@hwoarang> :) +21:29 <@scarabeus> ok 7 +21:29 <@jmbsvicetto> scarabeus: who's missing? bonsaikitten, cryo? +21:29 <@scarabeus> yup +21:29 <@jmbsvicetto> c/cryo/cryos/ +21:29 <@scarabeus> we can count kittens volte on fosdem? +21:29 <@tampakrap> keytoaster and tgurr +21:29 <@tampakrap> and carlo +21:30 <@yngwin> and caleb +21:30 <+reavertm> ok, lets' go further - 7 is enough already :) +21:30 <@jmbsvicetto> and corsair and genstef if we look at the kde page +21:30 <@scarabeus> those are kde devs? +21:30 <@jmbsvicetto> according to the page +21:30 <@hwoarang> are they active or smtg? +21:30 <@jmbsvicetto> Not in a long time, afaik +21:30 <@scarabeus> actualy i remember somebody promised that he will clean that up :] +21:31 <@jmbsvicetto> So, do I get to wear the KDE royal crown or what? ;) +21:31 <@scarabeus> jmbsvicetto: ok you are the leader +21:31 <@hwoarang> \o/ +21:31 <@scarabeus> nobody volted against actualy :] +21:31 <@yngwin> hail jmbsvicetto +21:31 <@jmbsvicetto> :) +21:31 * scarabeus bows in front of our new leader +21:31 <@tampakrap> congratulations!! +21:31 <@hwoarang> and as a leader you should provide us some free beers +21:31 <@scarabeus> jmbsvicetto: btw you have to update the page yourself, i hate cvs :] +21:31 <@jmbsvicetto> Thanks for the confidence guys +21:31 <+krytzz> right +21:31 <@alexxy> he he =) +21:31 <@jmbsvicetto> :) +21:32 <@alexxy> congratulations jmbsvicetto +21:32 <@tampakrap> POP *champagne* +21:32 <@yngwin> i can update the webpage +21:32 <@yngwin> need to edit it anyway +21:32 <@jmbsvicet> yngwin: thanks +21:32 <@yngwin> np +21:33 <@scarabeus> ok this was actualy funniest part of the meeting +21:33 <@scarabeus> things that will came are not that nice +21:33 <@alexxy> yep +21:33 <@yngwin> so grab another beer +21:34 <@jmbsvicetto> scarabeus: so I guess I can just leave now ;) +21:34 <@scarabeus> grm +21:34 <@scarabeus> actualy you should be leading the discussion now ;P +21:34 <@jmbsvicetto> hehed +21:34 <@scarabeus> ok lets start with upstream and prefixing thingie +21:34 <@scarabeus> i think that is something you have something to say about :] +21:35 <+reavertm> hmm? please introduce topic +21:35 <+reavertm> ah, kdeprefixing +21:35 <+reavertm> but what part of exactly? +21:35 <@tampakrap> i'll change topic +21:36 <+reavertm> no noe +21:36 <@scarabeus> not kdeprefixing +21:36 tampakrap changed the topic of #gentoo-kde to: Official gentoo-kde project channel | KDE 4 guide: http://tinyurl.com/4n47v4 | Next meeting 12/02/2009@20:00 UTC |Overlays: kde-testing, qting-edge | Want to help us? Ask channel staff for info | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | jmbsvicetto is the new leader!! +21:36 <@scarabeus> instaling multiple kde versions in one prefix +21:36 <+reavertm> hmm, how? +21:36 <+reavertm> elaborate please :) +21:36 <@scarabeus> that what jorge has to do +21:36 <@scarabeus> i have not much clue +21:36 jmbsvicetto changed the topic of #gentoo-kde to: Official gentoo-kde project channel | KDE 4 guide: http://tinyurl.com/4n47v4 | meeting: now - multiple installs under 1 prefix |Overlays: kde-testing, qting-edge | Want to help us? Ask channel staff for info | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | jmbsvicetto is the new leader!! +21:37 <+reavertm> I would like to hear what's all about first +21:37 <@jmbsvicetto> ok +21:37 <@jmbsvicetto> We were talking in FOSDEM that the real solution to our kdeprefix issues is to get KDE support for multiple versions in the same prefix +21:38 <+reavertm> eselect? +21:38 <@jmbsvicetto> To get that, we'll need versioned libs and we could use versioned apps (possibly with some symlinks to choose the default versions to use) +21:38 <@alexxy> hmm +21:38 * reavertm shuts up +21:38 <@alexxy> that will be good +21:38 <@jmbsvicetto> reavertm: that was one option presented +21:38 <@scarabeus> which sounds most reasonable +21:38 <@jmbsvicetto> reavertm: I thought it wasn't the best option - at least according to users. But if we get the versioned libs+apps, than it could be a good solution +21:38 <@alexxy> jmbsvicetto: what was another option? +21:39 <@jmbsvicetto> reavertm: the eselect would only select the "default" version +21:39 <+reavertm> what do you mean - versioned libs/apps +21:39 --rangerhom- is now known as rangerpb +21:39 <@scarabeus> sonames pn-version and so on +21:39 <@alexxy> jmbsvicetto: you mean that konsoel would be konsole-4.2.0 ? +21:39 <@jmbsvicetto> reavertm: having kwrite-4.1 or libkdeinit4_kinfocenter.so.4.2.0 +21:40 <@scarabeus> alexxy: only 4.2 +21:40 * Sput wouldn't add support for point releases +21:40 <@jmbsvicetto> alexxy: probably 4.2 +21:40 <@scarabeus> :} +21:40 <@alexxy> hmm +21:40 <+wired> upstream is willing to do something like that? +21:40 <+Sput> though this will of course screw up tab completion :( +21:40 <@scarabeus> upstream is willing to accept our patches for that +21:40 <+Sput> no more automatic space! +21:40 <+Sput> ooh, upstream should do that, rather than us? +21:40 <@jmbsvicetto> alexxy: the idea of the symlinks would be to have a konsole that would point to the version the user wants. Anyone using 4.2 as their default version, could still run 4.1 with konsole-4.1 or live with konsole-live +21:41 <@alexxy> ok +21:41 <+wired> this sounds so much cleaner than kdeprefix +21:41 <@alexxy> what will be with .desktop files? +21:41 <@jmbsvicetto> Sput: That would be the best option, but it doesn't seem likely they'll want to do it by themselves +21:41 <+reavertm> and messy +21:41 <+reavertm> what about shared data? +21:41 <+Sput> also this would allow other distros (with no concept of slotted installs) to support multiple versions easily +21:41 <@jmbsvicetto> Sput: They were however somewhat open to accept our patches to get it done +21:42 <@tampakrap> alexxy and reavertm made some good points +21:42 <+reavertm> like kbuildsysoca area of interest? +21:42 <@scarabeus> reavertm: actualy it is easy to suffix any filename with cmake so it can be all sufixed correctly +21:42 <@jmbsvicetto> reavertm: We could have /usr/share/kde//* or /usr/share/kde/- +21:43 <+reavertm> for me it's just a rehash of kdeprefix but with messed up files and separate - swtitched shared data areas +21:43 <@jmbsvicetto> reavertm: kdeprefix was never the best option. It was just the easy way to get around the fact that kde doesn't version libs/apps +21:43 <+reavertm> it would be easier to just eselect using kdeprefix +21:43 <@scarabeus> actualy this one would mean pretty nice elimination of kdeprefix really +21:43 <@jmbsvicetto> yes +21:44 <+reavertm> and actualy selected version of KDE would be target destination of actually built kde-misc package +21:44 <@scarabeus> reavertm: dependency nightmare +21:44 <@scarabeus> really +21:44 <@jmbsvicetto> reavertm: that seems worse, imho +21:45 <+reavertm> scarabeus we have deps already set per ebuild +21:45 <@jmbsvicetto> reavertm: Instead, with this proposal, kde-misc packages could link directly the unversioned deps +21:45 <@alexxy> ohh +21:45 <@alexxy> deps hell +21:45 <@scarabeus> reavertm: as said jmbsvicetto ^^ +21:45 <@jmbsvicetto> reavertm: The issue it raises is that KDE keeps breaking ABI which would break the packages +21:45 <@scarabeus> you could with this enable easy linking and it would be correct +21:45 <+Sput> well, easiest would just be going back to good old slots. :> +21:45 <@scarabeus> Sput: grm +21:45 <@alexxy> jmbsvicetto: what will be with misc apps that only works with for example kde>=4.3 +21:45 <@jmbsvicetto> Sput: we have slots :P +21:46 <@scarabeus> they link to the kdelibs.so-4.3.0 +21:46 <@jmbsvicetto> alexxy: well, you're not going to like my answer, but *pkgconfig* +21:46 <@scarabeus> for example +21:46 <+Sput> jmbsvicetto: KDE is no longer supposed to break ABI +21:46 <@jmbsvicetto> scarabeus: kdelibs-4.3 I would say +21:46 <@scarabeus> or pkgconfig is even better :] +21:46 <@scarabeus> Sput: they did it. +21:46 <@scarabeus> so we can expect more +21:47 <@jmbsvicetto> What we can do in the future, is to be very active in the kde-packagers / kde-build mls and don't let them get away with ABI breakage +21:48 <@alexxy> hmm +21:48 <@jmbsvicetto> Now, who would like to work on this and does anyone have any ideas on how to get it started? +21:48 <@alexxy> so kde upstream will accept splitting of kde apps? +21:49 <+reavertm> where are kde-misc packages installed and are they subject to versioning as well? +21:49 <@jmbsvicetto> alexxy: They will start doing it for 4.3 +21:49 <@jmbsvicetto> reavertm: I would say /usr and yes +21:50 <@jmbsvicetto> reavertm: Perhaps only between major versions +21:50 <@alexxy> hmm +21:50 <@alexxy> thats will be good +21:50 <+reavertm> so the only thing that's to be done is switching XDG_DATA_DIRS? +21:50 <@alexxy> they idea to add svn rev to snapshots was bad +21:50 <@scarabeus> probably in basic +21:50 <@scarabeus> but also adding sonames and so on +21:50 <@scarabeus> alexxy: that is other point +21:50 <@jmbsvicetto> alexxy: scarabeus mailed them about it +21:50 <@scarabeus> i already sent the mail +21:50 <@scarabeus> but get no response +21:51 <@scarabeus> for 4 days now +21:51 <@scarabeus> so i think we need to push it more +21:51 <@scarabeus> where is the best place? +21:51 <+reavertm> ok, I have a question - how is versioning binaries going to be implemented? +21:51 <+reavertm> via symlinks or shell scripts that set proper env for them? +21:51 <+reavertm> (scripts means overhead) +21:52 <@jmbsvicetto> reavertm: I think we should add the version when we install +21:52 <@jmbsvicetto> reavertm: We also need to write an eselect backend that can help manage the symlinks +21:54 <+reavertm> with eselect env may be switched right away - just like in java-config +21:54 <@scarabeus> btw you are planning way ahead i think, now we should think about who is willing to work on it :] +21:54 <+wired> jmbsvicetto: you said upstream will accept patches for versioning, wouldn't that eliminate the need for env switching? +21:54 <+reavertm> so only symlinks would be sufficient +21:54 * jmbsvicet puts the crown and starts delegating +21:54 <@jmbsvicetto> ;) +21:55 <@scarabeus> jmbsvicetto: dont look at me +21:55 <@jmbsvicetto> wired: If we want to have both around, we'll need the 2 +21:55 <+reavertm> wired env switchig is XDG_DATA_DIRS at least +21:55 <@scarabeus> i will be busy with the other distro patches sharing +21:55 <@jmbsvicetto> wired: unless users are willing to run kwrite-4.1 and amarok-2, instead of kwrite and amarok +21:55 * bonsaikit fell asleep ... +21:55 <+wired> if kde shipped kwrite-4.2 binary +21:55 <@jmbsvicetto> bonsaikitten: Got that bored? :P +21:55 <+wired> we would only need a symlink to make it run +21:56 <@scarabeus> bonsaikitten: tell me your volte ;P +21:56 <@jmbsvicetto> lol +21:56 <@scarabeus> :] +21:56 <@scarabeus> i am just curious +21:56 <@scarabeus> he wont be included :D +21:56 <@jmbsvicetto> wired: yes, but that's what we need eselect for +21:56 <@bonsaikitten> I vote for freedom +21:56 <@jmbsvicetto> scarabeus: lol -> "volte" ;) +21:56 <@scarabeus> ah +21:56 <@scarabeus> sdflhsdlfgksdhs +21:56 * bonsaikit still isn't coherent +21:56 <+wired> jmbsvicetto: i agree, i was refering to env switching, not symlink management +21:57 <@jmbsvicetto> wired: ok +21:57 <+Sput> bonsaikitten: nobody was talking about voting, you are supposed to do a little volte... +21:57 <+reavertm> I like the idea in general +21:57 <@jmbsvicetto> reavertm: what can we do to start the work? +21:57 <@jmbsvicetto> (since you are our cmake expert) +21:58 <@alexxy> write module for eselect +21:58 <@scarabeus> alexxy: that might be actualy last point +21:58 <@bonsaikitten> Sput: re-volt-ing? +21:58 <+reavertm> yeah, that's the magic part +21:58 <+wired> eselect is probably the last of our issues +21:58 <+reavertm> me expert? no.. +21:59 <@scarabeus> reavertm: yes you are our expert :] +21:59 <+reavertm> besides I can't answer about this off the top of my head right away +21:59 <@scarabeus> ok who is willing to work on this: +21:59 <@scarabeus> it is more upstream than gentoo +21:59 <@scarabeus> ? +21:59 <@jmbsvicetto> I'll have to look at it +22:00 <@jmbsvicetto> reavertm: can I nag you about cmake for this? +22:00 <+reavertm> I'll look into it +22:01 <@scarabeus> anyone else? +22:01 <@scarabeus> *doggyeyes* +22:01 <@scarabeus> or actualy *puppyeyes* +22:01 <@jmbsvicetto> scarabeus: Thanks for your offer +22:01 <@scarabeus> that sad look :] +22:01 <@scarabeus> jmbsvicetto: i will be quite fine with patch cooperation +22:01 <@scarabeus> :P +22:01 * jmbsvicet just made his first lead decision +22:01 <@jmbsvicetto> :P +22:01 <@scarabeus> :D +22:01 <@alexxy> heh =) +22:01 <@alexxy> btw +22:01 <@scarabeus> jmbsvicetto: ok and mine lead decision is delegat +22:02 <@scarabeus> e +22:02 <@scarabeus> so HTs what are you doing? :P +22:02 <@alexxy> whet will be with kde 3.5? +22:02 <@scarabeus> alexxy: that is on tampakrap, dont worry :] +22:02 <@tampakrap> mostly on carlo i'd say +22:02 <@jmbsvicetto> bonsaikitten: Anyway we can use your tinderbox for helping with the testing? +22:02 <@alexxy> there still parts of 3.5.7 3.58 3.5.9 and 3.510 +22:03 <@yngwin> i'd say drop 3.5.{7,8} +22:03 <@yngwin> and stabilize .10 asap +22:03 <@scarabeus> ok that is good idea +22:03 <@scarabeus> get rid of 7.8 +22:03 <@jmbsvicetto> yeah, but we need to check arches keywords +22:03 <@scarabeus> the arch teams has plenty time up to now to stable 3.5.9 on all needed arch +22:03 <+reavertm> stabilize 3.5.10 with revbumping kde-misc to be installed in /usr/kde/3.5? +22:03 <@scarabeus> yep +22:04 <@alexxy> yep +22:04 <@alexxy> but 3.5.8 is monolitic +22:04 <@alexxy> last monolitic release +22:04 <@scarabeus> that is no problem +22:04 <@jmbsvicetto> alexxy: 3.5.9 +22:04 <@scarabeus> and 3.5.9 is mono to +22:04 <@alexxy> so we can drop it =) +22:04 <@jmbsvicetto> 3.5.10 was teh first release without monos +22:05 <@jmbsvicetto> we need to check arch keywords as at least mips will probably lose all keywords +22:05 <@scarabeus> jmbsvicetto: well since mips is only ~ and they had actualy pretty long time to do it up to now... +22:06 <@scarabeus> but ok, lets poke them +22:06 <@jmbsvicetto> scarabeus: let's talk to them +22:06 <@alexxy> heh +22:06 <@alexxy> i can test kde on ~mips +22:06 * reavertm has his own 3 agenda points on the list +22:06 <@alexxy> =) +22:06 <@scarabeus> jmbsvicetto: actualy alexxy can do it :] +22:06 <@scarabeus> late +22:06 <@scarabeus> :D +22:07 <@jmbsvicetto> alexxy: are you in the mips arch team? +22:07 <@alexxy> seems they add me +22:07 <@alexxy> =) +22:07 <@alexxy> i have mips machine @work +22:07 <@alexxy> running gentoo +22:07 <@jmbsvicetto> Good :) +22:07 <@alexxy> also i have premison to add arm keywords +22:07 <@alexxy> =) +22:08 <+wired> so our kde4 upstream patches goal is to patch cmake to build/install everything version-prefixed with version-suffixed binaries? +22:08 <@scarabeus> alexxy: ok i delegate this point to you :] +22:08 <@scarabeus> ok one last thing from me +22:08 <@scarabeus> cooperating with reasonable distributions in patches sharing +22:09 <@alexxy> jmbsvicetto: i'll test kde:4.2 on mips +22:09 <@scarabeus> reasonable as debian for example +22:09 <@scarabeus> not as suse +22:09 <@hwoarang> scarabeus: like? +22:09 <@jmbsvicetto> alexxy: ok, thanks +22:09 <@scarabeus> hwoarang: like they have upstream and downstream patches we would like so we use them +22:09 <+Sput> you mean: distros backporting features from 4.3 trunk to 4.1 stable are not reasonable? :) +22:09 <@scarabeus> and in return we share our patches +22:09 <@jmbsvicetto> scarabeus: We can work with any distro - it all depends on their work ;) +22:09 <@scarabeus> for that i wrote this +22:09 <@scarabeus> http://dev.gentoo.org/~scarabeus/patches-glep.html +22:09 <@scarabeus> jmbsvicetto: i know +22:10 <@scarabeus> but i think we should make our patches nicely accessable like debian do +22:10 <+dagger_> I just came back home ;( +22:10 <@scarabeus> dagger_: bad for ya :] +22:10 <+reavertm> we use sed :P +22:10 <+Sput> System Message: ERROR/3 (patches-glep.txt, line 65) +22:10 <+Sput> Unexpected indentation. +22:10 <+Sput> coool : +22:10 <@scarabeus> i know +22:10 <+Sput> :) +22:10 <@scarabeus> it is not finished +22:11 <@scarabeus> christ why i showed it to you +22:11 <@scarabeus> i thought that somebody start complaining +22:11 <+Sput> :D +22:11 <@scarabeus> notes for this one will be accepted on my mail for now +22:11 <@scarabeus> until i get it into some reasonable shape for anouncing +22:12 <@hwoarang> your abstract idea is quite resonable +22:12 <@hwoarang> have you talked about this with other distro dudes? +22:12 <@tampakrap> we had a small chat with a debian-kde guy at fosdem +22:12 <@scarabeus> yep i talked with kde +22:12 <@scarabeus> debina +22:12 <@scarabeus> craaap +22:13 <@jmbsvicetto> scarabeus: You'll want to talk to infra and security teams about your proposal +22:13 <@scarabeus> yes i will do it +22:13 <@scarabeus> when i finish it +22:13 <@scarabeus> :P +22:13 <@jmbsvicetto> hehe +22:13 <@scarabeus> i dont want to come there with my hands empty +22:13 <@scarabeus> i would feel lame +22:14 <@scarabeus> so you know that i am on this one +22:14 <@scarabeus> that is everything from my side +22:14 <@scarabeus> anyone what do you have to discuss +22:14 <@jmbsvicetto> scarabeus: Did we cover all business in the agenda? +22:15 <@scarabeus> the things i pointed out +22:15 <@scarabeus> but this month i didnt get notes from others +22:15 <@scarabeus> (short time) +22:15 <+reavertm> ok... pykde4? +22:15 <@scarabeus> that is why i ask now +22:15 <@scarabeus> that bonsaikitten said that he will look on it +22:15 <@scarabeus> last meeting +22:15 <@scarabeus> :D +22:15 <+reavertm> that's the problem :) +22:16 <+reavertm> ok, another one +22:16 <+reavertm> what about non-SLOTted sets? +22:16 <@alexxy> btw +22:16 <@alexxy> when sets will be added to tree? +22:16 <+reavertm> I'd propose to remove them or made symlinks -> @kdebase -> @kdebase-4.2 and so on +22:17 <@tampakrap> are the symlinks valid? +22:17 <+reavertm> because unSLOTtted sets pulll all versions from every SLOT +22:17 <+reavertm> (in overlay) +22:17 <+reavertm> alexxy no +22:17 <+reavertm> never :) +22:17 <+reavertm> tampakrap why they coudn't be? +22:17 <@scarabeus> reavertm: good idea +22:18 <@jmbsvicetto> alexxy: That needs more time +22:18 <@jmbsvicetto> alexxy: we need to get an agreement about it +22:18 <@alexxy> ohh +22:18 <@alexxy> =( +22:18 <@tampakrap> reavertm: i don't know, i'm just asking :) +22:18 <@scarabeus> tampakrap: it works +22:18 <@yngwin> i guess that means at least waiting till portage 2.2.0 final release +22:18 <@jmbsvicetto> reavertm: the unversioned set should match the last version +22:19 <@tampakrap> last version of portage kde or of snapshots? +22:19 <+reavertm> yes +22:19 <@jmbsvicetto> reavertm: wait, you want them to have slotted deps? They can't +22:19 <+reavertm> those would be symlinks to latest set (but versioned one) +22:19 <+reavertm> jmbsvicetto it simplyfies upgrade +22:19 <@alexxy> yep +22:20 <+reavertm> I want unslotted sets to be removed or changed to symlinks to corresponding slotted sets +22:20 <@jmbsvicetto> reavertm: The unversioned deps should match the last version with sed s/:.*$// +22:20 <@alexxy> but unversioned sets should point to latest in tree slot +22:21 <@jmbsvicetto> reavertm: We need/want users to run the unversioned sets for installing - thus it can't have slotted deps +22:21 <+reavertm> jmbsvicetto wait wait +22:21 <+reavertm> there would be @kdebase set - the only difference would be, it would be symlink to @kdebase-4.2 +22:22 <@jmbsvicetto> reavertm: but that would mean it would have a kdebase-startkde:4.2 dep +22:22 <@tampakrap> aka latest portage version +22:22 <+reavertm> how are deps related? +22:22 <@jmbsvicetto> reavertm: I'm thinking :P +22:22 <+reavertm> they would be symlinks to latest portage version +22:23 <@jmbsvicetto> reavertm: I understand what you're trying to do. It might be the easiest option and it might even work +22:23 <+reavertm> (just like they are now) - but with SLOT definition so that we actually pull only that slot +22:23 < Enrico[ITA]> hi guys! if here there is some dev of kde-testing overlay there are some missing deps in kde-3.5.keywords file: kde-base/kde-i18n:3.5 ~kde-base/dcoppython-3.5.10 (and app-pda/libopensync but this is not part of kde ^^) +22:23 <@jmbsvicetto> Enrico[ITA]: we're in the middle of a meeting. Stick around and we can talk about it later +22:24 <@jmbsvicetto> reavertm: ok, I think I can live with it +22:24 <@tampakrap> i agree with that too +22:24 <+reavertm> jmbsvicetto well, it doesn't change anything from user perspective +22:24 <@jmbsvicetto> reavertm: my concern was that we might be restricting users to a specific slot +22:24 < Enrico[ITA]> jmbsvicetto: oh don't warry it is not a huge issue ^^. but ok i can wait no problem ^^ +22:24 <@scarabeus> yeah it should work +22:24 <@scarabeus> jmbsvicetto: that should be working correctly +22:25 <@scarabeus> the update with this +22:25 <@scarabeus> iirc the behavior portage does +22:25 <+reavertm> well, we would be responsible for managing those symlinks in overlay +22:25 <@jmbsvicetto> reavertm / scarabeus: yes, I see it should work +22:25 <@jmbsvicetto> reavertm: hmm, I do hope to get those sets in the tree - one day, one day +22:26 <@jmbsvicetto> reavertm: actually, if/when zmedico gets to re-work the sets, we might just have unversioned sets +22:26 <+reavertm> yeah +22:26 < Enrico[ITA]> well since you are in the middle of a meeting think about mark kde 3.5.10 as stable (and maybe even kde4.2!!!!) well i'm just kidding don't ban me ihihihi :P +22:26 <@jmbsvicetto> reavertm: or we would, if upstream stopped playing with moving apps between tarballs and renaming apps +22:26 < Enrico[ITA]> i don't speak no more promise ^^ +22:27 <+reavertm> well, it's up to us how we split packagees jmbsvicetto :) +22:27 * reavertm likes good refactoring +22:27 <@jmbsvicetto> reavertm: we'll have to follow the work being done for 4.3 +22:27 <@jmbsvicetto> :) +22:28 <@tampakrap> that's why snapshots and :live are :) +22:28 <@tampakrap> we were following 4.2 pretty well if you recall +22:28 <@jmbsvicetto> yes, but they're talking about splitting packages for 4.3 +22:29 <@jmbsvicetto> They seem willing to break apps, but not libs +22:29 <@jmbsvicetto> I think we should probably rethink the way we split libs and kdebase-runtime/kdebase-workspace +22:29 <@alexxy> why? +22:29 <@tampakrap> so what? i rebuild live every two days i follow changes +22:30 <@jmbsvicetto> alexxy: we probably don't need to split it up so much +22:30 <+reavertm> probably +22:30 <@alexxy> well i think current split are pretty well =) +22:30 <+reavertm> I'd vote for debian-like splitting scheme +22:31 <+reavertm> they split kdepim completely (like we do) but kdebase-workspace /runtime not that much +22:31 <@alexxy> reavertm: what it looks like? +22:31 <@tampakrap> ok i'll have a look at this +22:31 <+reavertm> (as those apps need to be installed for kde to work anyway) +22:31 <+reavertm> (they split plasma from kdelibs - for now reason whatsoever) +22:32 <@alexxy> hmmm +22:33 <+reavertm> ok, and I have another idea - drop kdepimlibs from DEPEND in eclass +22:33 <@alexxy> last time i take a look at debian it was using kde 2.x or 1.x dont remember +22:33 <+reavertm> I made alittle research and there are just some components that actually need it +22:34 <+reavertm> and plenty of people crying aabout mysql deps (akonadi server is pulled by kdepimlibs) +22:34 <+reavertm> alexxy well... you can look at Kubuntu... +22:34 <@jmbsvicetto> reavertm: seems like aseigo was willing to split plasma from kdelibs too +22:34 <+reavertm> it's debian afterall +22:34 <@tampakrap> upstream is going to import other dbs as well +22:34 <+reavertm> tampakrap any evidence? +22:34 <@jmbsvicetto> reavertm: if we can drop it, we should +22:34 <@tampakrap> fosdem talks :) +22:34 <@jmbsvicetto> (kdepimlibs) +22:34 <+reavertm> apart tahat techbase article saying that itis possible to implement but not planned? +22:35 <@jmbsvicetto> tampakrap: s/import/support/ ? +22:35 <+reavertm> jmbsvicetto yeah, we can +22:35 <+reavertm> I've made a list for kde-base stuff that needs it (I was grepping KdepimLibs in cmakelistx.txt in tarballs +22:36 <@jmbsvicetto> reavertm: ok, I'll look at it +22:36 <+reavertm> jmbsvicetto no, you "encourage" kitten to take care of pykde4 :) +22:36 <@jmbsvicetto> hehe +22:37 * jmbsvicet picks up the whip and calls for bonsaikitten +22:37 <@jmbsvicetto> kitten, kitten +22:38 <@scarabeus> :D +22:38 <@scarabeus> ouka i am back +22:38 <@scarabeus> what i sleft +22:38 <@scarabeus> (sorry i feel really dizzy today) +22:39 <+MrRat> reavertm: yes more db support is coming for akonadi +22:39 <+MrRat> http://techbase.kde.org/Projects/PIM/Akonadi#Akonadi_FAQ +22:40 <@jmbsvicetto> What are we still missing for today? +22:40 <+MrRat> a crazy hack at fixing amarok2 for qt-4.5 +22:40 <@tampakrap> yes, me and scarabeus saw it at fosdem talk of the debian kde packager +22:41 <@scarabeus> jmbsvicetto: i dont know +22:41 <@scarabeus> i dont have anything for adding +22:41 <@scarabeus> anyone else something? +22:41 <@ hwoarang> yngwin do we have something to add? +22:42 <@scarabeus> hwoarang, yngwin: actualy you two could you test qt-4.5 on kde-4.2 and spread patches? :] +22:42 <@ yngwin|2> kde4 doesnt work here +22:42 <@tampakrap> y? +22:42 <@hwoarang> works here though +22:43 <@hwoarang> scarabeus who this thing gonna work? +22:43 <@alexxy> http://dpaste.com/119912/ +22:43 <@hwoarang> gentoo qt <-> gentoo kde <-> kde upstream +22:43 <@alexxy> list of kde-3.5.[45678] ebuilds +22:43 <+wired> i can help on qt4.5/kde4.2 testing :) +22:43 <@hwoarang> we need to CC kde@gentoo.org on every kde4+qt4-5 related issue +22:43 <@ alexxy> yngwin: hwoarang: plasma segfaults with qt 4.5 if you dont recompile it +22:44 <@alexxy> same for knotify +22:44 <@hwoarang> there is a topic on kde forums +22:44 <@hwoarang> kde-4.2+qt-4.5 +22:44 <@tampakrap> recompile qt or knotify? +22:44 <@alexxy> so you two should add it to ewarn +22:44 <@hwoarang> maybe it will be good to monitor it +22:44 <@alexxy> recompile knotify and plasma-workspace +22:45 <@hwoarang> alexxy: we need to narrow down what should be rebuild +22:45 <@hwoarang> if something fails +22:45 <+reavertm> I guess I'm out of ideas for today as well +22:45 <@hwoarang> and i think that our ewarn message is quite clean +22:45 <@hwoarang> "if something fails, rebuild it" +22:45 <@alexxy> yep +22:45 <@jmbsvicetto> alexxy: the kde packages segfault after qt upgrade is an old issue +22:45 <@tampakrap> are these talks still on the meeting? +22:45 <@alexxy> but you only mention kdelibs +22:45 <@hwoarang> this is what every qt package states on pkg_postinst +22:45 <@alexxy> =) +22:46 <@alexxy> jmbsvicetto: i know +22:46 <@hwoarang> if this solution is valid i ll add it +22:46 <@alexxy> but for 3.5 only kdelibs was needed to be recompiled +22:46 <@hwoarang> but there is a report on forums that libplasma+ plasma-workspace didn solve it +22:46 <@alexxy> for 4.2 its at least kdelibs and plasma-workspace +22:47 <+MrRat> if sets were in portage an @kde-4.2 would solve it +22:47 <+MrRat> :P +22:47 <@alexxy> he he +22:47 <@hwoarang> so , from my part i ll CC kde@g.o alias on every mixed kde4+qt4.5 bug +22:47 <@hwoarang> to work it together +22:47 <@scarabeus> http://pastebin.ca/1335397 +22:48 <@scarabeus> reformat add on cvs +22:48 <@hwoarang> i wish i could do it on bugs.kde.org too +22:48 <@scarabeus> i am sick and going to sleep +22:48 <@scarabeus> i hope i wont be needed today anymore +22:48 <@tampakrap> i guess meeting is over +22:49 <@jmbsvicetto> scarabeus: You should end the meeting then ;) +22:49 <@jmbsvicetto> hwoarang: what are you missing in bgo ? +22:49 <@tampakrap> you are the leader +22:49 <@hwoarang> mmm +22:49 <@jmbsvicetto> ah, bko +22:50 <@hwoarang> every time i try to add a gentoo alias +22:50 <@hwoarang> it slaps me +22:50 <@hwoarang> ah +22:50 * jmbsvicet puts the hat and officialy ends the meeting +22:50 <@hwoarang> no on bgo +22:50 <@hwoarang> on bugs.kde.org +22:50 <@jmbsvicetto> yeah, I noticed it after I asked +22:50 <@jmbsvicetto> scarabeus: just one issue before you go, if you have 2 minutes +22:52 <@scarabeus> ook +22:53 <@scarabeus> listening +22:53 < arachnist> so, since the meeting has ended +22:53 < arachnist> is there a nice, working networkmanager plasmoid for kde-4.2? :> +22:53 < arachnist> preferably with an ebuild +22:54 <@jmbsvicetto> scarabeus: About the meetings, do you want me to start doing the preparation work or would you be willing to keep doing it? +22:54 <@scarabeus> i am willing to keep doing it if you want :] +22:54 <@jmbsvicetto> scarabeus: You've been doing a great job and I don't want to take away that pleasure from you ;) +22:54 <@jmbsvicetto> scarabeus: thanks +22:54 <@scarabeus> it is not pleasure ;D +22:54 <@scarabeus> but i will do it +22:54 <@jmbsvicetto> Hehe +22:54 <@scarabeus> since nobody else wants to do it :] +22:55 <@jmbsvicetto> ok, meeting in 1 month? +22:55 <@scarabeus> arachnist: there is networkmanager-applet-9999 in kde-testing +22:55 <@jmbsvicetto> I think we should review the date as I missed the council meeting today :\ +22:55 <+MrRat> arachnist: networkmanager-applet ebuild is in kde-testing, but in short, networkmanager nor the applet work well. +22:56 <+MrRat> arachnist: use wicd +22:56 < arachnist> wicd? +22:56 <+MrRat> yes +22:56 < arachnist> it needs gtk +22:56 <@scarabeus> yup 1 per month +22:56 <@scarabeus> feel free to change the date +22:56 < arachnist> there;s a reason i have gtk+ in package mask +22:56 < Pesa> may i ask if you could remove the new hard dep on qt-phonon for Qt 4.5, making it optional? +22:56 <@scarabeus> i just randomly picked +22:56 < arachnist> there's* +22:56 <+MrRat> wicd works great and you can start wicd-client in kde4's ststem settings autostart and it works great +22:57 <@jmbsvicetto> scarabeus: ok +22:57 < arachnist> not a very valid one, but there is ;> +22:57 <@jmbsvicetto> scarabeus: I think we might opt for the 1st Thursday of the month +22:57 <@jmbsvicetto> I'll ask in the alias/ml +22:57 <@scarabeus> that is already in there or not? +22:57 <@scarabeus> :D +22:57 <@jmbsvicetto> ok, I'm going to eat something +22:58 <@yngwin> Pesa: there is no hard dep on qt-phonon +22:58 <@scarabeus> on the first Wednesday/Thursday of every month at 19:00 UTC +22:58 <@scarabeus> indeed i wrote this ;} diff --git a/meeting-logs/20090305-summary.txt b/meeting-logs/20090305-summary.txt new file mode 100644 index 0000000..09f2d37 --- /dev/null +++ b/meeting-logs/20090305-summary.txt @@ -0,0 +1,40 @@ +AROUND: +yngwin, wired, scarabeus, alexxy, cryos, jmbsvicetto, hwoarang, bonsaikitten, tampakrap, reavertm + +kde3 state/others: +- merging to master branch in kde-testing soon, for more info/help offers talk with tampakrap +- so correct prefixing for kde3 and no more blocks are coming near to you. +- create important bug list and ask bugday people and others for help -> tampakrap + +amarok maintainer: +- send mail to -dev to get one -> scarabeus + +homepage updates: +- we need to keep our webspace up-to-date and guides actualy working -> yngwin, tampakrap + +pykde: +squash the bugs/issues, unslot, unkdeprefix... -> bonsaikitten + +kbluetooth4: +may be even working, needs testing/patching -> wired + +kde4 stabling/keywording: +we need to check deps so they are working on target arches +also we should make less strict deps on kde4 eclass -> scarabeus on this + +cmake-utils: +hopefully done, now only bugfixing -> reavertm, scarabeus + +removal of htmlhandbook: +introduce working doc flag -> probably scarabeus (needs to be done before 4.2.2) + +tarballs splitting and libs/apps versioning: +- discussion to start on the desktop ml -> jmbsvicetto + +snapshots: +send mail to dirk -> jmbsvicetto +repack tarballs -> bonsaikitten +set on rest for now by majority vote, come and volunteer if you want it changed + +bugsquash: +let's aim at having each kde team member fixing 5 bugs per week diff --git a/meeting-logs/20090305.txt b/meeting-logs/20090305.txt new file mode 100644 index 0000000..a52c535 --- /dev/null +++ b/meeting-logs/20090305.txt @@ -0,0 +1,769 @@ +[21:08:49] LETS BEGIN :D +[21:09:07] so first nice question is +[21:09:10] WHO IS AROUND? +[21:09:16] o/ +[21:09:17] !herd kde +[21:09:21] yngwin: (kde) alexxy, caleb, carlo, cryos, deathwing00, genstef, jmbsvicetto, keytoaster, mattepiu, patrick, scarabeus, tampakrap, tgurr +[21:09:21] !herd qt +[21:09:22] (qt) caleb, carlo, hwoarang, yngwin +[21:09:24] -*- wired is here +[21:09:29] -*- yngwin is present +[21:09:37] -*- alexxy here +[21:09:50] xine-lib-9999 does not compile yngwin because of missing Makefile.in +[21:09:50] *** Mode #gentoo-kde +v reavertm by scarabeus +[21:10:22] where are the other slackers :P +[21:10:37] slacking +[21:10:38] :p +[21:10:54] bumbl: see forum thread. if there is a patch/solution, i will apply it (tonight or tomorrow) +[21:10:58] -*- cryos|work is kinda here, ill, stressed... +[21:11:19] cryos|work: hi :] +[21:11:59] <-- KotBehemot (n=dracul66@unaffiliated/kotbehemot) has quit (Remote closed the connection) +[21:12:03] ping +[21:12:20] Sorry for being late +[21:12:22] ok we are closing onto desired goal >50% around :] +[21:12:22] I think you need to ping an address, or is that a broadcast packet? +[21:12:24] here +[21:12:34] <-- genady12__ (n=genady12@80.178.17.222.adsl.012.net.il) has quit (Read error: 110 (Connection timed out)) +[21:12:54] where is our main slacker? bonsaikitten are you here? +[21:12:56] =) +[21:13:09] am I ? +[21:13:16] yes! +[21:13:29] cryos|work: broadcast ping ;) +[21:13:34] ok so i guess we can start, others would have to show up later... +[21:13:37] any objections? +[21:13:54] none +[21:13:57] who are we missing? +[21:13:59] =) +[21:14:02] tampa +[21:14:05] Carlo! ;-> +[21:14:05] tampakrap i guess and reaver +[21:14:14] Philantrop: :P +[21:14:17] Philantrop: you actualy get him on irc at some point? :] +[21:14:17] Hi Wulf +[21:14:30] scarabeus: No, he never was nor will he ever. +[21:14:34] Hi Phil :) +[21:14:34] jmbsvicetto: Hello! :-) +[21:14:39] hehe +[21:14:52] scarabeus: carlo is a "mail" guy +[21:14:52] --> KotBehemot (n=dracul66@unaffiliated/kotbehemot) has joined #gentoo-kde +[21:15:05] yea i got that :] +[21:15:14] jmbsvicetto: ... if he communicates at all. +[21:15:37] Philantrop: well, a reply to a 4 or 6 month mail is still a reply :P +[21:15:40] http://www.pastebin.cz:80/15872 +[21:15:44] jmbsvicetto: :-) True. +[21:15:48] i'm here +[21:15:50] here is a list what we will chat about today +[21:15:53] hello tampy +[21:15:59] tampy! +[21:16:03] lol +[21:16:32] -*- cryos|work only claims 42% presence --- man flu... +[21:16:44] ok so we can start with kde3.5.10 state +[21:16:50] cryos|work: get well soon +[21:16:51] cause on that we all probably will just listen :D +[21:16:52] i'd like to say a few things about KDE 3 first +[21:17:17] may I? +[21:17:20] Hi Theo +[21:17:21] yes proceed +[21:17:22] say +[21:17:32] ok +[21:17:39] cryos|work: yeah, my cold has been bugging me for the past week :\ +[21:17:50] in kde-testing i have a kde-3.5 branch with new eclasses +[21:18:13] those eclasses prefix misc kde apps in /usr/kde/3.5 and permit eapi2 ebuilds +[21:18:38] i have started writing all kde-base ebuilds in eapi 2 i have about 60 here +[21:19:02] jmbsvicetto told me today to try to get rid of arts and use a different backend +[21:19:18] i'm not sure if this can be done and to be honest i don't know if it worths it +[21:19:24] i'd like your opinion +[21:19:24] -*- jmbsvicetto looks innocently into the sky +[21:19:37] and of course some testing of you people +[21:19:53] tampakrap: if it's too much work, forget arts +[21:19:54] kill arts. +[21:20:05] in my opinion kde 3.5.10 works as is, and i wouldnt spend too much time on 'improving' the ebuilds +[21:20:07] especially the kde4 guys, as the pending big issue is the proper use of kde3 apps inside kde4 environment +[21:20:12] tampakrap: I was just interested to find out if we could kill it +[21:20:21] jmbsvicetto: You could. +[21:20:22] --> looonger (n=looonger@host-89-231-128-7.rawamaz.mm.pl) has joined #gentoo-kde +[21:20:43] tampakrap: have you done any changes to the eclasses since we lasted talked about them? +[21:20:46] i agree with killing +[21:20:53] Philantrop: we should, but meh :\ +[21:20:57] give peas a chance +[21:21:17] wired: yes but not pushed +[21:21:17] jmbsvicetto: I wouldn't do it anymore. It's not worth the effort anymore. +[21:21:24] yeah, I agree +[21:21:50] it was allways broken from my POV and it is not worth the problems with it i guess +[21:21:57] tampakrap: how can we help you getting it done? +[21:22:02] tampakrap: ok, just asking because last time i used them [by accident] kdebluetooth failed to install +[21:22:23] wired: most of the bugs i tried to fix +[21:22:24] kdebluetooth is problematic anyway +[21:22:30] should probab;ly be hardmasked +[21:22:30] jmbsvicetto: i'll ping you guys when i need help don't worry +[21:22:41] tampakrap: If you think the eclasses are "almost done", you should probably merge them to the master branch +[21:22:54] yngwin: it works fine for me (with bluez < 4) +[21:22:57] yes i'm about to do it +[21:23:03] ok :) +[21:23:14] ok +[21:23:31] --> scratch[x] (n=scratch@83.239.148.148) has joined #gentoo-kde +[21:23:46] but i agree with Philantrop it is not worth the effort, everyone is moving to kde4.2, just a quick cleanup of kde3 is enough +[21:23:53] yep +[21:23:59] on a related note, i want to mask ~qt-3.3.8 for removal, and leave only ~qt-3.3.8b in tree +[21:24:05] and i am more intrested in kde4 too +[21:24:30] kde 3.5.x is old =) +[21:24:31] yngwin: feel free +[21:24:31] <-- er0x (n=kvirc@client-87-247-122-156.inturbo.lt) has quit ("KVIrc Insomnia 4.0.0, revision: , sources date: 20090224, built on: 2009/03/04 18:54:25 UTC http://www.kvirc.net/") +[21:24:56] alexxy: maybe old, but it works ;) +[21:25:02] :] +[21:25:04] yngwin: Is anything holding qt-3.3.8 around? +[21:25:13] yngwin: looking at keywords I see they're the same +[21:25:15] i thought kdebluetooth +[21:25:30] ok about kdebluetooth +[21:25:31] ah, ok +[21:25:38] not 100% sure, will look tomorrow +[21:25:43] there might be some users who still want to use kde 3.5 until ~ kde 4.4 (which is when all the third party developers will have ported their apps (hopefully)) +[21:25:51] NOTE: (guys i found out that my loging is not working with this weechat version so i will write summary and somebody else will have to put the log on devspace) +[21:26:08] bumbl: hmm, besides k3b, which major apps are still missing? +[21:26:09] -*- wired keeps logs +[21:26:11] bumbl: it's no reason to wait for them to release, we can provide working snapshots +[21:26:17] jmbsvicetto: nothing! +[21:26:20] scarabeus: I have logs, don't worry +[21:26:23] ouk +[21:26:40] jmbsvicetto: k3b, konversation, that i know +[21:26:46] kile +[21:26:48] and others +[21:26:51] jmbsvicetto: kaffeine4 is still very basic (kaffeinegl seems dead) +[21:26:53] kde3 is still needed +[21:26:54] quanta!!!!!!!!!! +[21:26:56] kile works from :live +[21:27:07] <_genuser_> qt-core is almost done. +[21:27:08] k3b dont at this moment +[21:27:09] live is not good for normal users :] +[21:27:13] yngwin: I liked quanta :) +[21:27:13] ok about kdebluetooth i'll have a look at it and try to find the very best solution +[21:27:16] <_genuser_> then more hours for kdelibs. +[21:27:21] Konversation's KDE 4 port is shaping up nicely, so that will be gone from the list soon. +[21:27:27] jmbsvicetto: yeah quanta is badly missing +[21:27:35] we can make snapshots for kile +[21:27:36] =) +[21:27:43] jmbsvicetto: i was hoping for quanta with vimpart +[21:27:44] blah +[21:27:47] <_genuser_> I'm so excited that in 2 days I can finally run kde4.2. :) +[21:28:06] <_genuser_> that was sarcastic. +[21:28:09] shouldn't kdevelop4 replace quanta? +[21:28:09] <_genuser_> hopefully it runs soon. +[21:28:10] jmbsvicetto: Kile +[21:28:14] we can make snapshots for many packages and maybe we can start doing it +[21:28:15] tampakrap: do you need our help somewhere on kde3? +[21:28:30] using TexClipse and this just sucks :D +[21:28:36] scarabeus: not now maybe in a few days +[21:28:52] oh and obviously we still a "working" amarok ;) +[21:29:00] genady12_: ah that's why my sarcasm detector went wild +[21:29:16] scarabeus: next? getting 3.5.10 stabled? +[21:29:21] people please we have a meeting here... +[21:29:26] right +[21:29:29] hehe lets wait what tampakrap shows us +[21:29:43] for now lets fix the prefixing +[21:29:45] :] +[21:29:51] we still have ~2 months :D +[21:30:06] For getting 3.5.10 marked as stable? :\ +[21:30:08] why? there's no need to keep 3.5.10 from going stable +[21:30:12] scarabeus: remember my kepas thing *g* +[21:30:15] I was hoping to do it next month +[21:30:18] as i said the main issue is running kde3 apps inside kde4 env that's where i need help and testing +[21:30:22] THIS month +[21:30:32] yngwin: :) +[21:30:33] how can we do it this month with so many bugs open? +[21:30:36] jmbsvicetto: for 4.2 starting its consideration :D +[21:30:48] <-- ABCD (n=ABCD@wikipedia/ABCD) has quit (Client Quit) +[21:31:03] ok this leads to the virtualbox snapshots i talked about +[21:31:09] tampakrap: can you make a list of the important bugs that need fixing? so we can work on that, and ask users (bugday!) to help +[21:31:14] we should create some generic gentoo instalation with kde3 and kde4 for testing +[21:31:17] yes i can +[21:31:27] --> ABCD (n=ABCD@wikipedia/ABCD) has joined #gentoo-kde +[21:31:28] that would be helpful +[21:31:37] scarabeus: Im on that +[21:31:51] i should separate kde base bugs from the misc ones as a first step +[21:31:52] yngwin / tampakrap: I think the most imporant point to get 3.5.10 marked as stable is getting the eclasses in the tree +[21:31:56] wired: How is that coming? Do you need my help? +[21:32:26] brb +[21:32:31] * tampakrap has changed topic for #gentoo-kde to: "MEETING NOW | Official gentoo-kde project channel | KDE 4 guide: http://tinyurl.com/4n47v4 | Overlays: kde-testing, qting-edge | Want to help us? Ask channel staff for info | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | KDE 4.2.1 is available | Weird issues with nvidia-drivers-180.35? bug 260441 | Qt 4.5.0 committed" +[21:32:34] NoirSoldats: well with 4.2.1 and all it kinda fell behind, but its cool, i figured out how to compact the thing as well so its more a matter of time now +[21:32:49] i think we're done with kde3 +[21:32:57] if nobody has questions on ya +[21:33:08] wired: I'm here if ya need me or my processors. :) +[21:33:31] alright, we'll talk about it after the meeting +[21:33:32] oh the last i wanted to tell about kde3 +[21:33:34] --> panard (n=panard@2a01:e35:8a09:e130:2e0:61ff:fe11:7adb) has joined #gentoo-kde +[21:33:34] anyone ever noticed you can compile all of koffice-2 except Krita +[21:33:50] comawhite: i know, not now, later i will talk with you +[21:34:04] okay +[21:34:23] carlo is doing an excellent job with kde3 misc apps he closed many bugs but he is never on irc, has anyone contacted him ever? +[21:34:33] only by email +[21:34:52] i gave up after he didnt answer my emails last year +[21:35:00] ok i'll keep that in mind +[21:35:05] <-- Bluespear (n=speedy@dhcp-83-219-104-51.customers.tvtnet.ch) has quit ("Leave") +[21:35:06] tampakrap: You should use mail to talk to carlo +[21:35:07] tampakrap: only by mail, or best is creating bug with high priority assigned to him +[21:35:11] that is how i contacted :D +[21:35:22] ok +[21:35:49] ok next thingie is: +[21:35:55] we need somebody maintain the amarok +[21:36:10] not me +[21:36:18] not me =) +[21:36:23] hehe +[21:36:24] is anyone from us willing to be official maintainer? +[21:36:25] both kde3 and 4? +[21:36:29] yeah both +[21:36:32] scarabeus: I haven't looked at 5.1.72 yet (mysql), but I'll get back to it this week +[21:36:34] omg +[21:36:37] --> eyal_ (n=eyal@IGLD-80-230-109-116.inter.net.il) has joined #gentoo-kde +[21:36:51] scarabeus: I don't think amarok for kde3 should require much work +[21:36:55] jmbsvicetto: :P +[21:37:00] --> mschiff (n=mschiff@e176096142.adsl.alicedsl.de) has joined #gentoo-kde +[21:37:05] jmbsvicetto: well not much work but minor bugz are poping up +[21:37:06] jmbsvicetto: no it does :) +[21:37:10] so polishing it needs +[21:37:17] :\ +[21:37:25] it is a mess, pretty abandoned +[21:37:42] yes, flameeyes tried to drop it on me +[21:37:44] i guess we could sent mail on -dev +[21:37:48] amarok-1.4 ? +[21:37:54] indeed +[21:38:11] as i offered to help at the time when he had to go to hospital +[21:38:40] hehe +[21:38:54] he assigned all amarok bugs to me +[21:38:55] soo do we have suicider, erm i mean maintainer... +[21:38:59] btw amarok-2.2 released +[21:39:04] tampakrap: yeah i know +[21:39:20] tampakrap: what?! +[21:39:24] 2.0.2 +[21:39:28] he cant write +[21:39:29] :D +[21:39:32] look i'm a big fun of amarok but until the end of the month i'll be pretty busy with some things and i can't take it +[21:39:43] yes i know i am not saying you should +[21:39:45] we could just hardmask it and assign to maintainer-needed ;) +[21:39:58] ok i will sent the mail on the dev you lazy .... +[21:40:00] :D +[21:40:01] i wonder if amarok compiles with qt-4.5 now +[21:40:11] hwoarang: Mine did. +[21:40:19] hmm +[21:40:26] so does here but the upstream bug is still open +[21:40:27] hwoarang: With a little hacking. +[21:40:31] we can add amarok 2.0.2 to overlay +[21:40:36] and reproducable by many users +[21:40:36] to see if it works +[21:40:41] scarabeus: add me silently to the amarok bugs +[21:40:42] +1 to alexxy +[21:41:01] jmbsvicetto: ok adding as note if you are really sure :] +[21:41:09] yup +[21:41:16] scarabeus: I'll take a look at it +[21:41:23] will the kde-herd and sound-herd maintainers remain though? +[21:41:33] yes of course :] +[21:41:41] ok amarok is done i think :] +[21:41:56] i dont think anyone @sound is really interested +[21:42:16] now i have "homepage updates" it means that we have pretty much tons of outdates info on webspace, in doc and in informations +[21:42:23] i don't care for sound-herd after all :) +[21:42:28] so we need somebody that will actualy try to keep that up-to-date +[21:42:39] -*- tampakrap +[21:42:43] tampakrap: careful, i am in sound :p +[21:42:45] next subject :) +[21:42:54] :P +[21:43:08] tampakrap: you will really keep the web updated? are you sure it is lots of pages and lots of stuff :] +[21:43:23] specialy now main page and the guide needs heavy lifting +[21:43:29] so do you have time?... +[21:43:33] i can help +[21:43:36] look as i said until the end of a month i'll be pretty busy with some things, next i'll have too much free time +[21:43:49] i'll take care of the guide though +[21:44:14] ok you two, try to work it out somehow then :] +[21:44:30] bonsaikitten: ping +[21:44:33] now i need you :] +[21:44:36] what! +[21:44:39] wait a minute +[21:44:46] I'm just providing access to tarballs ;) +[21:45:02] bonsaikitten: nope, i need YOU to take look on pykde bugs, and actualy fix them +[21:45:10] yeah +[21:45:11] since you are most relevant for this +[21:45:14] one quick note about the guide, people when you are fixing major stuff please do the guide fixes too immediately or assign it to someone, but it is a must +[21:45:23] scarabeus: I claim incompetence ;) +[21:45:32] been quite busy with work, maybe I find some time during the weekend +[21:46:14] greatie +[21:46:21] bonsaikitten: feel free to even remove it from kdeprefix +[21:46:32] well, first gotta fix slotting +[21:46:37] yup +[21:46:39] then see why it randomly fails +[21:46:46] then learn enough C++ to fix it +[21:46:50] :D +[21:47:24] there is nothing how i could help, combo of python and cpp is overhead for me +[21:47:25] :] +[21:47:29] hehe +[21:47:37] I still have so many other bugs I want to take care of :( +[21:47:53] maybe mask pykde4 then +[21:47:59] it will allways be that way, but this is one of the biggest kde4 stable blockers now +[21:48:54] yngwin: even that might be the final solution if we wont make it work +[21:49:02] althrought it would disable lots of plasmoids +[21:49:10] no Final Solutions here +[21:49:20] now it just fails for too many ppl +[21:49:23] we are pacifists who give every ebuild a chance +[21:49:34] :D +[21:49:36] :) +[21:50:13] -*- bonsaikitten glares at Phil +[21:50:59] any of you have any ideas about the bluez and kbluetooth, somebody who uses it, i might make it work, but frankly i dont use it much so i might missed stuff, it needs testing and maybe even patching +[21:51:03] kbluetooth4 +[21:51:56] so let's ask users :) +[21:52:04] bluez is hardmasked +[21:52:06] just compiled pykde4-9999 successfully +[21:52:07] I have no bluetooth equipment +[21:52:12] so it needs really brave insaners to test +[21:52:25] -*- alexxy dont have bluetoth +[21:52:33] i have bluetooth but i stopped trying with kbluetooth4 some time ago because it broke my nerves +[21:52:36] i can test again +[21:52:45] --> himikof (n=himikof@129.167.249.ozerki.net) has joined #gentoo-kde +[21:52:51] --> Varox (n=Varox@p4FD441A6.dip.t-dialin.net) has joined #gentoo-kde +[21:53:04] wired: ok +[21:53:08] i will leave it up to you +[21:53:18] gnokii + bluez + kdebluetooth4 + /me = /me insane +[21:53:34] ok. i think i saw a patch for solid and bluez4 somewhere +[21:53:39] <-- Ghabit (n=quassel@91.149.157.195) has quit ("No Ping reply in 30 seconds.") +[21:53:41] ok as sidenote and selfegomasturbation, this week i fixed KOFFICE and it works fine +[21:53:53] so we are prepared to add it for the tree :] +[21:53:54] --> Ghabit (n=quassel@91.149.157.195) has joined #gentoo-kde +[21:53:58] i was about to ask it, what was the issue? +[21:54:00] yey +[21:54:16] i spent 6-7 hours on it +[21:54:21] -*- wired writes down todo notes ^_^ +[21:54:29] and developed nice cmake hate :D +[21:54:40] ok well done +[21:54:58] --> bschindler|away (n=quassel@zux221-218-241.adsl.green.ch) has joined #gentoo-kde +[21:55:17] haha +[21:55:25] build systems seem to be very good for hate +[21:55:30] indeed +[21:55:39] but still i like it more than scons and bam +[21:55:42] scarabeus: so you've finally learned to hate cmake? :P +[21:55:53] jmbsvicetto: sorry for my disbelieve +[21:55:53] scarabeus: Are you feeling the love for autotools again? ;) +[21:55:57] yes :D +[21:55:57] --> kostekjo (n=opera@chello084010120054.chello.pl) has joined #gentoo-kde +[21:56:03] cause autotools wont allow such messy code +[21:56:08] <-- Varox (n=Varox@p4FD441A6.dip.t-dialin.net) has quit (Remote closed the connection) +[21:56:08] or i didnt see it anywhere +[21:56:17] hehe +[21:56:28] reavertm: pingping +[21:56:29] scarabeus: take a look @gromacs +[21:56:30] =) +[21:56:30] scarabeus: you should check kde autotools - it's also great ;) +[21:56:39] :D +[21:56:39] to see autotools mess code +[21:56:47] ok ok dont make me ruin my ideals +[21:56:52] hehe +[21:56:59] let's rewrite kde to use maven +[21:57:09] that would be orgasmic +[21:57:14] bonsaikitten: let's use propper autotools :P +[21:57:25] jmbsvicetto: that would have been my second-best suggestion :) +[21:57:46] ok jmbsvicetto do you have some items that we need to squash for 4.2 stabling +[21:57:54] currently we get hit by only minor stuff +[21:58:04] so i am asking if you have something actualy major +[21:58:04] --> non7top (n=non7top@77.66.156.160) has joined #gentoo-kde +[21:58:11] we need to double check webkit, qt-phonon and java deps +[21:58:21] jmbsvicetto: i already did webkit optional +[21:58:23] some arches don't support any or some of these +[21:58:41] mips dont have java +[21:58:50] for that we have virtuoso i guess +[21:58:53] at least untill icedtea6 will hit tree +[21:58:54] isn't the java issue fixed for soprano and such? +[21:58:56] btw that package needs to be splitted +[21:58:58] which reminds me, can we make all deps in kde4-base.eclass optional? +[21:59:03] cause it is 150mb big as one +[21:59:11] yngwin: talk with me later about it +[21:59:15] ok +[21:59:16] i am open for suggestions +[21:59:56] <-- S-man (n=quassel@cc84863-b.zwoll1.ov.home.nl) has quit (Remote closed the connection) +[22:00:09] i'll repeat, isn't the java issue fixed? +[22:00:18] tampakrap: seems yes +[22:00:34] at least i have sane deps tree on mips +[22:00:38] tampakrap / alexxy: Have you talked to ali_bush about that? +[22:00:49] i talked with ali_bush +[22:00:51] He was reporting an issue with gen1 jvms +[22:01:05] he said he'll look into it tomorrow +[22:01:14] --> S-man (n=quassel@cc84863-b.zwoll1.ov.home.nl) has joined #gentoo-kde +[22:01:41] great :] +[22:01:43] virtuoso does need ~15mb (the parts kde actually uses) +[22:02:18] yes but the rest is 10x bigger that is why i said that we should split it +[22:02:27] (apparently) +[22:02:54] (qt-)phonon is not supported/keyworded on alpha, ia64, mips, sparc and x86-fbsd +[22:02:55] yep +[22:03:12] stil the idea of splitting proposed by trueg is rather silly? (virtuoso-data, virtuoso-backends? it's database server :P) +[22:03:17] yngwin: i'll keyword phonon on mips +[22:03:22] ok +[22:03:31] alexxy: please keyword qt-demo as well +[22:03:32] webkit seems to have problems at least in big endian arches +[22:03:39] hwoarang: later +[22:03:44] yes +[22:03:44] only after kde =) +[22:03:52] btw, there is probably no more separate phonon release +[22:04:03] jmbsvicetto: my mips is bigendian +[22:04:27] USE-flags if possible +[22:05:00] alexxy: at least for sparc and I think ppc64 webkit has alignment issues +[22:05:41] -*- alexxy thinks that we should have abi and endianes keywords for packages +[22:05:47] only sparc +[22:05:58] ppc64 does have qt-webkit keyworded +[22:06:29] alpha and ia64 dont +[22:07:33] on the soprano[sesame2] java issue, it seems sesame doesn't like sun-jre-bin +[22:08:15] ok lads +[22:08:16] isn't this fixed? +[22:08:31] i will take care of easying the deps in eclass and you take care about keywording and deps :] +[22:09:22] wired to build? of it doesn't like switching between sun-jdk and sun-jre-bin after it was succesfully built +[22:09:54] --> Zucca (i=zucca@a88-112-55-25.elisa-laajakaista.fi) has joined #gentoo-kde +[22:09:54] reavertm: when i was testing it it would skip sesame2 support if sun-jre-bin was set as system-vm +[22:10:05] build fail +[22:10:14] it need somebody from java to look and investigate +[22:10:22] there's also another issue with sesame +[22:10:34] <-- bschindler (n=quassel@zux221-218-241.adsl.green.ch) has quit (Read error: 110 (Connection timed out)) +[22:10:37] if you run emerge with sudo +[22:10:41] scarabeus: I've heard of cmake not finding java +[22:10:44] it skips sesame support +[22:10:56] i talked to ali_bush about it and he said he'll look into it +[22:10:56] jmbsvicetto: it find it +[22:11:00] but marks as not sufficient +[22:11:04] i did bit investigation +[22:11:13] you can't build it with sun-jre and no wonder - it needs jdk - that's first +[22:11:44] second is - cmake FindJNI doesn't support many jdk's (IBM to mention one) +[22:11:53] sounds reasonable, but no checks are done for it +[22:11:59] (I have even some patch for that module somewhere) +[22:12:08] then give it upstream +[22:13:52] ok now we are getting to the fancy stuff +[22:13:54] <-- kostekjo (n=opera@chello084010120054.chello.pl) has left #gentoo-kde +[22:14:01] reavertm: how is looking the cmake stuff you are working on +[22:14:11] now the eclass in the testing is working right, can we make it more gentooish +[22:14:17] or it is not worth efforts? +[22:14:32] gentooish? +[22:14:34] :D +[22:14:40] scarabeus: could you please expand? i have no idea what you are talking about +[22:14:57] it's done, testing (rebuilding with kde now) +[22:14:58] tampakrap: obeying our variables and so on +[22:15:05] i tested too +[22:15:08] this afternoon +[22:15:10] works fine +[22:15:16] it's about preserving gentoo C(XX)?_FLAGS and such +[22:15:32] --> Zuccace_ (i=zucca@a88-112-55-25.elisa-laajakaista.fi) has joined #gentoo-kde +[22:15:35] goodie +[22:15:43] reavertm: ok so lets say we have this as final agreed? +[22:15:50] no more major updates :] +[22:16:01] scarabeus you tested it with obsolete cmake-utils and I already fund some user of forum (or here) complainging at /usr/local and claimig that he sysnced overlay recently +[22:16:13] he is lying +[22:16:14] g +[22:16:16] it is working +[22:16:17] ups :p +[22:16:23] tested on tons of cmake-utils ebuilds +[22:16:29] i have some stuff in /usr/local too +[22:16:36] wired: then try the stuff recompile +[22:16:48] kk +[22:16:57] its just soprano, i'll do it now +[22:17:17] no, it's cmake issue, not soprano issue +[22:17:22] i mean +[22:17:25] its soprano files +[22:17:26] in there +[22:17:27] :) +[22:17:31] yes it is cmake-eclass isue +[22:17:34] so sync and try plz +[22:17:39] on it +[22:17:40] so we can have it from the first hand +[22:18:09] <-- yngwin (n=yngwin@gentoo/developer/yngwin) has quit (Read error: 104 (Connection reset by peer)) +[22:18:19] meanwhile we removed htmlhandbook useflag so we have to create new generation for the docs :] +[22:18:31] --> yngwin_ (n=yngwin@gentoo/developer/yngwin) has joined #gentoo-kde +[22:18:31] *** Mode #gentoo-kde +o yngwin_ by ChanServ +[22:18:40] it is not biggie but it would be nice to have some reasonable doc system instead of broken htmlhandbook for 4.2.2 +[22:18:53] any ideas on this? +[22:18:57] doc USE flag? +[22:19:19] reavertm: hehehe +[22:19:21] sry, lost network +[22:19:21] i like this +[22:19:27] it was wrong +[22:19:28] and what then - extracyting /doc when set? +[22:19:48] yup but wont be smart to have kde-docs package +[22:19:52] easier and convinient +[22:20:47] -*- NoirSoldats seconds the idea of a kde-docs package. +[22:21:08] <-> yngwin_ is now known as yngwin +[22:21:22] why kde-docs? +[22:21:25] so... gather docs from all kde-base modules? +[22:21:35] yup +[22:21:36] If I only install 3 or 4 apps, why should I have the docs for all of KDE? +[22:21:42] <-- looonger (n=looonger@host-89-231-128-7.rawamaz.mm.pl) has quit (Client Quit) +[22:21:43] --> ayevee (n=quassel@62.140.238.1) has joined #gentoo-kde +[22:21:53] -*- reavertm agrees with jmbsvicetto :P +[22:21:54] ok so useflag you say +[22:21:55] ok +[22:21:57] :( +[22:22:04] my nice idea squashed to the dust :D +[22:22:04] jmbsvicetto: How big would the docs really be though? In total? +[22:22:10] quite much +[22:22:17] I mean, it's easier to maintain it at package level +[22:22:28] <100MB? +[22:23:04] am I the only one for whom automo-9999 fails to build? +[22:23:46] scarabeus: synced, emerge -av1 soprano but the files still installed in /usr/local +[22:23:48] scarabeus: Hmm, I have a suggestion for how to handle the docs, that should solve both ends of the spectrum.. if I may. +[22:23:57] ayevee: not now. we are in the middle of a meeting +[22:24:08] hwoarang: sorry +[22:24:19] <-- ayevee (n=quassel@62.140.238.1) has quit (Client Quit) +[22:24:22] np +[22:24:34] scarabeus: why was htmlhandbook wrong? +[22:24:59] htmlhandbook is installing *unpacked* docs +[22:25:19] ah ok +[22:25:20] sth like difference between .chm and unpacked help contents +[22:25:36] (i have no problem with that but i see the point) +[22:27:06] are we still in point 3 ? :\ +[22:27:27] :D +[22:27:33] we have 3 issues left +[22:27:39] I see we'e jumped ab it +[22:27:39] i pick randomly :D +[22:27:42] a bit* +[22:27:48] <-- Zucca (i=zucca@a88-112-55-25.elisa-laajakaista.fi) has quit (Read error: 110 (Connection timed out)) +[22:27:54] 4, 5 and 6 ? +[22:27:59] ok reavertm we will probably work on this +[22:28:12] those are due to now +[22:28:19] scarabeus: ^^ soprano still installs in /usr/local +[22:28:22] now lets talk about the splitting then +[22:28:27] wired: ok i will owrk on that +[22:28:32] ok :) +[22:28:55] reavertm: do you know how is upstream going with its splitting for 4.3? +[22:29:22] --> mikkoc_ (n=mikko@151.59.215.164) has joined #gentoo-kde +[22:29:57] upstream is going to split modules or to support splited builds? +[22:29:58] <-- scratch[x] (n=scratch@83.239.148.148) has quit ("Ухожу") +[22:30:10] or something else? +[22:30:32] related to binary/lib versioning? well, they don't seem to be eager (see the need - talked with dfaure ) to change .so version to make it possible to install multiple installations aside +[22:30:51] I wonder who came up with the idea (maybe I don't have clear picture) +[22:31:05] jmbsvicetto: you are most relevant for this ideas +[22:31:24] ok +[22:32:19] Our talk at FOSDEM was that they would (could?) probably split all the bins, but there were some resistance to lbis +[22:32:22] libs* +[22:32:45] is that about keeping 4.x and 4.(x+1) aside? +[22:33:13] jkt|: yes and in same prefix +[22:33:49] anyway - providing more restictive .so versions would restict their ABI compatibility - they already increase soversion for newer libs +[22:34:02] scarabeus: that's the next step +[22:34:13] -*- Sput thinks it does not make much sense to split libs that are always needed anyway +[22:34:37] so we would need either dependencies on *every*library* level (and not tied to particular kde version) or just override their choice on our side +[22:34:43] The first step from them was splitting the tarballs. The second step is providing support to have multiple versions around +[22:34:53] Sput: I tend to agree +[22:35:17] reavertm: libtool!!! ;) +[22:35:26] <-- anselmolsm (n=anselmo@200.184.118.130) has quit (Read error: 113 (No route to host)) +[22:35:40] hh +[22:35:45] <-- Zuccace_ (i=zucca@a88-112-55-25.elisa-laajakaista.fi) has quit (Read error: 110 (Connection timed out)) +[22:35:58] I don't know libtool and I'm not eager to learn it (libtool is broken as well, besides :P) +[22:36:36] reavertm: I mean that this issue of lib versions and deps is what libtool does +[22:37:02] setting versions for kde libs is not a problem +[22:38:09] reavertm: I mean run-time deps +[22:38:32] reavertm: Having app A with a rdep on lib X-1.0.1 and not lib X-1.0.2 +[22:38:41] <-- Sho_ (n=EHS1@kde/hein) has quit (Read error: 104 (Connection reset by peer)) +[22:39:28] --> anselmolsm (n=anselmo@200.184.118.130) has joined #gentoo-kde +[22:39:30] So, who's interested in this subject? +[22:39:56] i am not enought l33t for this one +[22:40:00] --> kostekjo (n=opera@chello084010120054.chello.pl) has joined #gentoo-kde +[22:40:32] neither am I +[22:40:37] <-- kostekjo (n=opera@chello084010120054.chello.pl) has left #gentoo-kde +[22:41:09] I don't believe you :P +[22:42:06] --> root (n=root@hor-jdh171.hor.ucl.ac.uk) has joined #gentoo-kde +[22:42:14] ok, I guess we should talk about this later. Let's see if we can get anything in the ml +[22:42:15] <-> root is now known as lfranchi +[22:42:26] Are you guys still awake? ;) +[22:42:36] <-- lfranchi (n=root@hor-jdh171.hor.ucl.ac.uk) has quit (Client Quit) +[22:42:37] yep +[22:42:39] i am trying +[22:42:42] ook +[22:42:43] hehe +[22:42:48] yeah i just woke up at 19:00 utc +[22:42:48] next thing +[22:42:50] importand one +[22:42:51] --> rex_ (n=quassel@host135-243-dynamic.4-87-r.retail.telecomitalia.it) has joined #gentoo-kde +[22:42:54] snapshots +[22:42:57] what should we do +[22:43:04] upstream dont give a f**k +[22:43:07] stop providing them i guess +[22:43:23] scarabeus: I'll try to mail Dirk directly +[22:43:34] I don't feel like it's worth repacking +[22:43:39] Dirk is the packager? +[22:43:40] last time it took him a few months to get back, but I won't lose anything by sending the mail +[22:43:43] Philantrop: ping +[22:43:44] it is getting high priority cause pple liek the feature +[22:43:49] scarabeus: I can script fixed ones +[22:43:56] Dirk Mueller is "release-team" :P +[22:44:04] <-- Civil (n=Civilian@95-24-48-161.broadband.corbina.ru) has quit (Remote closed the connection) +[22:44:05] scarabeus: that way we'd use our own mirroring +[22:44:06] that's why we can't get any feedback :P +[22:44:22] jmbsvicetto: Hm? +[22:44:25] --> leo (n=leo@hor-jdh171.hor.ucl.ac.uk) has joined #gentoo-kde +[22:44:26] reavertm: he's on the packagers and release ml +[22:44:33] <-> leo is now known as lfranchi +[22:44:40] we can repack this tarbolls +[22:44:55] yes, but he's de facto only man reposnible for releases and tarballs +[22:44:56] Philantrop: Have you tried to get someone from KDE about the snapshots names? +[22:45:09] yo Sput +[22:45:11] Philantrop: By you, I mean you, Ingmar or someone else from exherbo +[22:45:22] Sput: i get to complain at you now :) +[22:45:33] jmbsvicetto: Nope, we decided we don't care enough. :) +[22:45:38] hehe +[22:45:42] that's the spirit +[22:45:42] Philantrop: slacker :P +[22:45:44] hehe +[22:45:49] that is the point we are getting now :D +[22:46:10] actually we have similar approach I guess :) +[22:46:12] jmbsvicetto: "[05. 03. 2009 21:29] slacker! :p" <-- to me. :-> +[22:46:24] lol +[22:46:25] hehe +[22:47:00] I'll provide some feedback to the ml when / if I get something +[22:47:03] <-- mikkoc (n=mikko@151.59.212.173) has quit (Read error: 110 (Connection timed out)) +[22:47:04] <-- pipipde (n=pip@e179244051.adsl.alicedsl.de) has quit (Read error: 110 (Connection timed out)) +[22:47:08] we still need tarbolls for snapshots +[22:47:12] what's the backup plan then? +[22:47:15] ok lets state we sent hte mail +[22:47:22] and bonsaikitten will repack for time being +[22:47:26] I'm going to send another mail today +[22:47:34] ok you sent the mail +[22:47:42] jmbsvicetto: maybe CC to many KDE people and mls +[22:47:59] tampakrap: I'm going to address the packagers, the release team and Dirk directly +[22:48:01] so i'm just getting started with kde-svn ebuilds on gentoo, and automoc failed to install (failed to even begin checking out from svn). can anyone in here help me? +[22:48:09] --> pipipde (n=pip@e179247082.adsl.alicedsl.de) has joined #gentoo-kde +[22:48:25] lfranchi: later1 we have meeting there +[22:48:31] oh, sorry +[22:48:36] -*- lfranchi hides +[22:48:59] lfranchi: I guess it will be fixed soon, but will, many people use live kde (didn't have time to look up the issue) +[22:49:12] bonsaikitten: so you can rly pack it with not big effort? +[22:49:42] scarabeus: we can repack them as tar.lzma +[22:49:43] =) +[22:49:47] sweeet +[22:49:50] via scripts +[22:49:54] -*- jmbsvicetto kills alexxy +[22:49:58] tar.bz2 :P +[22:50:08] jmbsvicetto: .lzma better =) +[22:50:12] well since they really want their svn in the filename, maybe we can convince them to use a 4.x.SVNREV.tar.bz2 scheme? +[22:50:26] wired: well the svnrev is not deterministic +[22:50:31] jmbsvicetto: if you mailed Dirk, you would be mentining placing .svnrevision file or sth in tarball? +[22:50:31] you have to go and check for that revnumber +[22:50:40] normaly you just add +1 +[22:50:56] as I guess it's at least the way we agreed with thiago +[22:50:56] i see +[22:51:08] reavertm: I can suggest that as an alternative +[22:51:15] well i don't see them changing their minds any time soon, alexxy's log was pretty clear +[22:51:38] jmbsvicetto: I mean, let him know we already discussed it with kde folks :P +[22:52:09] reavertm: I will also ask for different options if they don't want weekly snapshots to be used by packagers +[22:52:21] wired: well, you may read jmbsvicetto log as well (later that day) +[22:52:57] if they don't want us to use - I think we should not use :P we just need to follow trunk changes then :P +[22:53:31] It's sufficient to prepare next stable (4.3) release +[22:53:34] --> Linux (n=marcus@92-234-252-159.cable.ubr06.blac.blueyonder.co.uk) has joined #gentoo-kde +[22:53:41] Hey everyone. +[22:53:49] besides - people should use portage version :P +[22:53:58] hehe +[22:53:59] Is KDE 4.2.1 available yet? I synced yesterday. +[22:54:09] Linux: Yes. +[22:54:11] yes, sync again +[22:54:16] so not making snapshots available we probably have greater 4.2 userbase to test and possibly stabilize later +[22:54:19] OK. :) +[22:54:53] reavertm: the snapshots are useful, imo +[22:55:10] as unstable snaphosts are not really *releases* but just svn dump - they are usually as broken as live +[22:55:16] i agree with reavertm, live is enough, we already maintain too many kde releases +[22:55:22] -*- alexxy starts repacking kde 4.2.65 +[22:55:29] :D +[22:55:34] alexxy: talk with kitten +[22:55:42] ok, if no one is willing to work on them for now, let them rest +[22:55:49] ook +[22:55:50] agreed +[22:55:54] We have enough things to take are already +[22:56:18] scarabeus: bugs? bugz? BUGZ??? ;) +[22:56:19] last thing +[22:56:24] BUGZZZZZZZZZZZZZZZZZZZZZZZ +[22:56:30] :) +[22:56:30] we have tons of them +[22:56:31] zzzzzzzzzz +[22:56:31] many dupes +[22:56:34] many needs fix +[22:56:37] many are trivial +[22:56:40] yngwin: :) +[22:56:44] and there is sh*tload of them +[22:57:01] nice, i was eating +[22:57:14] don't read then ;) +[22:57:15] good now you will starve as me :D +[22:57:22] hahahahahah +[22:57:23] -*- Sput looks into automoc now +[22:57:37] except somebody fixed that already +[22:57:43] Sput it may be as well cmake-utils related +[22:58:01] scarabeus: tell us the last issue and go to watch some pr0n +[22:58:06] :D +[22:58:12] the issue is we need to work on bugz +[22:58:24] tampakrap: you didn't watch pr0n during the meeting like the rest of us? +[22:58:25] we need smebody actualy devolting lots of time on them +[22:58:44] we need a cleanup as a first step +[22:58:44] Should we set some goals about bugs? +[22:58:53] yep that might be good +[22:58:57] -*- reavertm still has some updates 4.2.1 and wonders whether anyone wants them, especially with 4.2.1 removed from overlay :P +[22:58:59] take care of trackers, duplicates and resolved +[22:59:01] and then fixed +[22:59:15] Do we want to reduce them to a certain number by X months? Do we want to set a goal of taking care of X bugs per week? +[22:59:15] reavertm: pastebin it :] +[22:59:18] i'm sure 100 of them are already fixed or duplicate +[22:59:33] yes +[22:59:36] or invalid +[22:59:36] jmbsvicetto: you are the leader, you should set the number +[22:59:51] --> cypr1nus (n=cypr1nus@plus.ds14.agh.edu.pl) has joined #gentoo-kde +[22:59:57] scarabeus: when I'm done rebuilding kde with them (along with cmake-utils and those pasted kde4 eclass thing - so far so good) +[23:00:12] actualy we can have policy like "you want to be in herd fix X bugz a month" +[23:00:14] :D +[23:00:19] or some other contribution to kde +[23:00:51] i'm ok will all these, just give us the deadlines +[23:00:51] heh =) +[23:01:07] OK. Let's have a vote: get bugs under X or fix X bugs per week? +[23:01:25] the second +[23:01:27] yes! +[23:01:38] the second is more reasonable :] +[23:01:38] define "fix" +[23:01:40] I think the later might be more productive and may help feeling work done +[23:01:43] -*- bonsaikitten self-removes from the herd preemptively +[23:01:44] +1 +[23:01:53] bonsaikitten: hehe +[23:01:56] hhahahahahha +[23:02:06] bonsaikitten: we can give you expection for the kittening :D +[23:02:08] marking as RESOLVED/FIXED only to decrease bug count is wrong approach - I'd agree with flameeyes here :P +[23:02:22] well it has to be fixed too +[23:02:30] I'm not going to create a rule "if you don't fix X bugs per week, you're out", but I think we should all try to solve at least X bugs per week +[23:02:34] haha +[23:02:37] well, for starters it would probably help to weed out the duplicates +[23:02:41] well, I'm fixing too many other things +[23:02:41] reavertm: sure +[23:03:10] jmbsvicetto: btw did you sent the mail about removing of members to nonactive kde members? +[23:03:15] So, a reasonable number would be between 2 and 10? +[23:03:35] 4-10 +[23:03:57] 5 per week? +[23:03:58] a week +[23:04:00] 5 +[23:04:17] but actualy we are fixing even more :P +[23:04:21] i have 5 for today :D +[23:04:27] more than 5 +[23:04:28] lol +[23:04:29] :D +[23:04:33] ;) +[23:04:35] 10? +[23:04:39] 7? +[23:04:41] tampakrap: that is hard to tell +[23:04:46] Ok, let's all try to fix at least 5 bugs per week +[23:04:48] bug a day might be good idea +[23:04:51] ook +[23:04:57] tampakrap: Let's not aim too high +[23:04:59] at least 5 bugs per week +[23:05:14] <-- Caster (i=Caster@gentoo/developer/caster) has quit ("Don't waste your time, or time will waste you.") +[23:05:15] fine +[23:05:19] tampakrap: You're feel to fix 50 in a week if you can ;) +[23:05:27] oh i am? +[23:05:34] yes :P +[23:05:41] ok now we are clear +[23:05:42] bah, You're free* +[23:05:44] a bug a day keeps the doctor away +[23:05:53] hahahhaaha +[23:06:05] bumbl: nice moto +[23:06:07] a bug per day keeps the ladys away +[23:06:12] rofl +[23:06:13] lawl +[23:06:17] hehe +[23:06:20] lol +[23:06:28] dagger: you wanna help with bugz? +[23:06:28] I suggest we had bumbl moto to our page ;) +[23:06:32] do you rly want that to happen? +[23:06:32] tampakrap: 10 bugs a day keep your life away :p +[23:06:35] scarabeus: sure +[23:06:37] jmbsvicetto: agreed +[23:06:56] So, anything else? +[23:07:01] we are done +[23:07:03] dismissed diff --git a/meeting-logs/20090401-summary.txt b/meeting-logs/20090401-summary.txt new file mode 100644 index 0000000..168f528 --- /dev/null +++ b/meeting-logs/20090401-summary.txt @@ -0,0 +1,74 @@ +Roll call: +KDE devs: alexxy, bonsaikitten, cryos, hwoarang, jmbsvicetto, scarabeus, tampakrap, yngwin +KDE ATs: krytzz, reavertm, wired + +Agenda for the meeting: +- unprefixing misc stuff +- moving plasmoids to the tree +- kde3 state +- moving printing to the tree +- upstream responses on packaging snapshots +- removing dead members +- pykde fixing +- handling kdeprefix for base... eselect? +- koffice status / what is needed +- moving meeting to another date (about 2 weeks before release of upstream so +we can talk about what is needed to be done for current release) +- stable live status (if the guys working on it shows up ;]) + + - Removing kdeprefix for apps not in kde-base + reavertm explained that the goal was to drop the kdeprefix use flag for all apps + outside of kde-base and that he already started the work for it (including a rewrite + of the eclasses) in the dropped-kdeprefix-on-non-kde-base branch in the kde-testing + overlay. This means deprecating NEED_KDE in favor of KDE_REQUIRED and KDE_MINIMAL, so + that packages are built not against the newest available KDE (when there's more than + 1 version) but instead to the oldest - respecting KDE_MINIMAL. + There was a long discussion about kdeprefix, its purpose, benefits and alternatives. + The final consensus was to follow reavertm's solution. + + - KDE3 state + tampakrap explained the eclasses are ready to move all packages under /usr/kde/3.5. + He's still testing ebuilds and could use the help of 2 people to test kde-misc apps. + wired and jmbsvicetto offered to help. tampakrap will prepare a list of packages and + we're going to search for people through the page and a mail to the dev ml. + To start the work on getting KDE4 marked stable, we agreed to get this work done by + the end of the month - we'll be masking 3.5.9 monos as soon as we get 3.5.10 marked + stable. + + - Moving Plasmoids to the tree + Plasmoids were moved to kde-misc category and will be added when they're tested + with +kdeprefix + + - Adding printing packages to the tree. + We've decided to hold this until KDE-4.3. + + - Upstream response to the packaging snapshots mail + No reply again. As we're being ignored, we've decied to repackage the snapshots. + + - Removing dead members + jmbsvicetto will go over the retirement bugs and will send emails to the members + that are MIA. He will get the team membership cleaned before next meeting. + + - pykde fixing + There are some problems with having more than one pykde version with +kdeprefix + as it installs files outside the prefix. The solution might be to "unprefix" it + or to have a new package just with the python files. In any case, patrick was + "nominated" to work on this. + + - handling kdeprefix for base ... eselect + After some discussion we agreed eselect was not the solution + + - koffice status / what is needed + scarabeus informed the team that koffice-2.0 is going to be released at the end + of the month and asked what we should do about it. scarabeus suggested to have + the stable release hardmasked in the tree. We agreed to try to get one of the + rcs in the tree before that to allow users to test it. + + - moving meeting to another date + We decided to have KDE meetings at the 3rd Thursday of the month. + + - stable live status + We didn't discuss this topic. + +As a final note, jmbsvicetto reminded people that we still have a *few* open bugs +and that we should all try to help get that number down. diff --git a/meeting-logs/20090401.txt b/meeting-logs/20090401.txt new file mode 100644 index 0000000..0c83346 --- /dev/null +++ b/meeting-logs/20090401.txt @@ -0,0 +1,601 @@ +21:01 <@scarabeus> hey +21:01 <@scarabeus> now we can start +21:01 <@jmbsvicetto> I'm out of here. See you later :P +21:02 <@alexxy> jmbsvicetto: stay here =) +21:02 <@scarabeus> hehe +21:02 <@scarabeus> !herd kde +21:02 < Willikins> (kde) alexxy, caleb, carlo, cryos, deathwing00, genstef, jmbsvicetto, keytoaster, mattepiu, patrick, scarabeus, tampakrap, tgurr +21:02 <@scarabeus> krytzz: reavertm Sput wired +21:02 <@scarabeus> ausing again +21:02 <@scarabeus> meeting time +21:03 <+krytzz> aye +21:03 * tampakrap is here +21:03 <@cryos|work> That was an hour ago wasn't it? I thought we were done :P +21:03 * jmbsvicetto agrees +21:03 <@scarabeus> :D +21:03 * alexxy here or there like a psi^2 +21:04 <@scarabeus> bonsaikitten: dont hide, i saw ya +21:04 -!- jmbsvicetto changed the topic of #gentoo-kde to: Official Gentoo KDE Project channel | Next Meeting^Wamarok party: Wednesday April 1st 19:00 UTC | KDE 4 guide: http://tinyurl.com/4n47v4 | Overlays: kde-testing, qting-edge | Want to help us? Ask channel staff for info | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 +21:04 <@scarabeus> !herd qt +21:04 < Willikins> scarabeus: (qt) caleb, carlo, hwoarang, yngwin +21:04 * jmbsvicetto starts jumping around +21:04 <@jmbsvicetto> scarabeus: ok, ok. I'll behave ;) +21:04 <@hwoarang> im here +21:04 * hwoarang GOGO GREEEEEEEEEEEEEECE +21:04 <@scarabeus> jmbsvicetto: well you are the lead, you do the example for us :D +21:05 <@scarabeus> remember we store meeting logs tho :D +21:05 <@tampakrap> i think we shouldn't this time +21:05 <@scarabeus> hehe +21:05 <+reavertm> ok... +21:05 <@scarabeus> reavertm: you are first on list +21:05 <@scarabeus> so speak up +21:06 <@scarabeus> :D +21:06 <+reavertm> so, kdeprefix +21:06 <@scarabeus> http://www.pastebin.cz:80/16911 +21:06 <+reavertm> the idea is ... to drop it :) +21:06 <@scarabeus> (list for others) +21:06 * wired back +21:06 <@alexxy> or mask kdeprefix useflag +21:06 <@alexxy> =) +21:06 <+reavertm> (from non kde-base) +21:06 <@tampakrap> i agree +21:07 <+reavertm> I already started to play in dropped-kdeprefix-on-non-kde-base branch if anyone is interested +21:07 <@alexxy> may be better to mask it for all packages +21:07 <+reavertm> in the process I rewritten kde4 eclass +21:07 <@alexxy> so people who realy want could unmask it +21:07 -!- spitfire_ [n=quassel@ackz136.neoplus.adsl.tpnet.pl] has joined #gentoo-kde +21:07 <+reavertm> important changes are: +21:07 <@scarabeus> alexxy: nah i prefer nonkdeprefix, it is better +21:08 <@scarabeus> alexxy: less thins to worry about +21:08 <+reavertm> NEED_KDE deprecated in favor of KDE_REQUIRED and KDE_MINIMAL (the latter already there) +21:08 <+wired> scarabeus++ +21:08 <@alexxy> scarabeus: i use -kdeprefix too +21:08 <@alexxy> so we can mask kdeprefix use flag for tree packages +21:08 <@tampakrap> if we mask it, we somehow still provide support for it, something that i don't want +21:08 <@cryos|work> I use -kdeprefix too, but I think it would be nice to keep it as an option that can be unmasked. It has its uses, I just don't think it is for general consumption... +21:08 <@alexxy> so people who want install 4.2 4.3 and live together can unmask it +21:09 <+reavertm> my eclass drops kdeprefix from non-kde-base +21:09 <@scarabeus> alexxy: the part for non-kde-base +21:09 <@scarabeus> not for base kde +21:09 <@scarabeus> :D +21:09 <+reavertm> do you even read me? +21:09 <@scarabeus> we are not removing the flags from kdebase/* +21:09 <@scarabeus> :D +21:09 <@cryos|work> Is there a way to hack it back in for non-kde-base if you don't care about support? +21:09 <@tampakrap> everybody stop typing until reavertm finishes his words please +21:09 <@scarabeus> cryos|work: narp +21:10 <@scarabeus> for the eclass i already read it and i think it is much cleaner, specialy no "get_latest_kdedir" +21:10 <@cryos|work> I work on several packages where I would like trunk and release. I could locally hack it, but the current situation is useful even if not supporte.d +21:10 <+reavertm> RPATH solves possible linking issues +21:10 <@scarabeus> well we droped mostly live slot for packages +21:10 <@scarabeus> cryos|work: buty you can allways override prefix so it shoudl be no prob +21:11 <+reavertm> now packages are built not agains newest available KDE (if more installed) but with the oldest - yet respecting KDE_MINIMIAL +21:11 <@cryos|work> Seems a shame, but I can maintain custom ebuilds for the few I work on. +21:11 <+reavertm> scarabeus: all live slots dropped +21:12 <@jmbsvicetto> hmm, scarabeus / reavertm drop kdeprefix for non-live, right? +21:12 <@scarabeus> for everything +21:12 <@jmbsvicetto> scarabeus / reavertm: !kde-base live apps should install under /usr/kde/live +21:13 * cryos|work thought that too... +21:13 <+reavertm> /usr/kde/live is KDE release dir and should not contain any 3rd party apps imho +21:13 <@scarabeus> that wont run for pple that install live misc apps for 4.2 in example +21:13 <@alexxy> jmbsvicetto: no =) +21:13 <@jmbsvicetto> We've been talking about this for a long time. all live ebuilds should go under /usr/kde/live +21:13 <@scarabeus> i use lots of live apps +21:13 <+reavertm> how aboyut accessing those live packages from kde 4.2 ? +21:13 * alexxy also use kile amarok and k3b +21:13 <@alexxy> with 4.2 and 4.3 snapshots +21:14 <@alexxy> so i dont like idea of dropping kdeprefix for misk apps +21:14 <@jmbsvicetto> If we use the KDE_MINIMAL it should work, no? +21:14 <@cryos|work> So you are dropping any support for installing/building live apps against live KDE builds? +21:14 <@alexxy> in way as jmbsvicetto said +21:14 -!- [DWSR] is now known as DWSR +21:14 <+reavertm> how is dropping kdeprefix from live packages related to not being able to use them with 4.2 ? +21:14 <@scarabeus> cryos|work: so you think live should be special case... +21:15 <@scarabeus> reavertm: well it can be done so live is special enviroment +21:15 <@alexxy> i think better to mask kdeprefix use flag for all kde in tree +21:15 <@scarabeus> and we can just not bother for it +21:15 <@jmbsvicetto> scarabeus: That's why live doesn't fit in SLOTS ;) +21:15 <@cryos|work> scarabeus: I always have, but I tend to work with live and do development, but want a stable desktop for work... +21:15 <@alexxy> so people who want eg 4.2 and live togther can deal with it +21:16 <@scarabeus> alexxy: current approach is broken +21:16 <+reavertm> I use 4.2 and live non-kde-base stuff +21:16 <@scarabeus> i srsly fear next major release +21:16 <@jmbsvicetto> ok, let's try something different +21:16 <@jmbsvicetto> The point of having kdeprefix was to allow running more than 1 version at the same time +21:16 <@cryos|work> I guess for people with live KDE, and live misc apps built against 4.2 things would likely still work though. +21:16 <@scarabeus> eys that is maintained +21:16 <+reavertm> jmbsvicetto: be more precise +21:16 <+reavertm> more than one version of what? +21:17 <+reavertm> KDE release or any package? +21:17 <@jmbsvicetto> With the exception of live (imo) which should be under /usr/kde/live - the real solution for that is to change the kde build system and have all versions under /usr +21:17 <@cryos|work> KDE, but are you really trying to separate packages that build against it? +21:17 <@scarabeus> well it is like kde3 +21:17 <@scarabeus> cryos|work: +21:17 <@jmbsvicetto> reavertm: more than one KDE release +21:17 -!- non7top [n=non7top@94.77.134.21] has joined #gentoo-kde +21:17 <+reavertm> and you'll still have it :P +21:18 <@cryos|work> OK - I will stay quiet. I am really busy today anyway and have not been on IRC for weeks.... +21:18 < spitfire_> cryos|work: no it doesn't always work. I had quassel built against 4.2 and it didn;t run in live complaining about missing symbols in oxygen.so. +21:18 <@jmbsvicetto> The point is whether anyone is willing to start the work +21:18 <@jmbsvicetto> I haven't looked at that yet +21:18 <+reavertm> spitfire_: +21:18 <+reavertm> nop +21:18 <@jmbsvicetto> cryos|work: I would like to get your opinion about this issue +21:18 <+reavertm> you had quassel built againd live that didn;'t work with 4.2 +21:19 <+reavertm> because so far it was like this - having 4.2 and -9999 - apps were bult againt *the newest* kde +21:19 <@cryos|work> At least now KDE will work if built against an old KDE and linked to a newer one. +21:19 <@scarabeus> yes +21:19 <@jmbsvicetto> cryos|work: We've talked a lot about this and tried to reach a compromise that would satisfy everyone, so I would like that any change gets our support +21:19 <@cryos|work> So building against 4.2 and linking to live should work, assuming no one screwed up and I do that a lot. +21:19 <@scarabeus> yes it have to wor +21:19 <@scarabeus> the cant break abi +21:19 < spitfire_> reavertm: sry to interrupt but for example quassel never finds kde-live, always builds against 4.2 +21:19 <+reavertm> actually there's RPATH +21:20 <+reavertm> if we drop RPATH then we may start worrying about linkage problems +21:20 <@cryos|work> It doesn't have to - people screw up... And there is RPATH which can force linking to a particular path. +21:20 <@jmbsvicetto> scarabeus: that's the "theory", but that's not their practice +21:20 <@alexxy> spitfire_: later +21:20 <@scarabeus> indeed +21:20 <@cryos|work> jmbsvicetto: They do pretty well on the whole, but RPATH alleviates issues with screw ups too... +21:20 <+reavertm> (and I'm going to drop rpath for -kdeprefix) +21:20 <+reavertm> (btw) +21:20 <@jmbsvicetto> cryos|work: all the mess with libplasma, phonon, kdeartwork-kscreensaver, ... +21:21 <+reavertm> phonon is kdeprefix problem +21:21 <@cryos|work> Like I said, they do pretty well... ABI is really tough to keep stable... +21:21 <+reavertm> it install kde4 plugins +21:22 <+reavertm> adding QT_PLUGIN_PATH to /usr/lib64/kde4/plugins could possibly solve it +21:22 <@jmbsvicetto> cryos|work: The problem is that 4.0 was nowhere where they wanted it to be, so they've realized many things required changes +21:22 <@cryos|work> Yeah, I know... Mixing versions is always really tough to get right too. +21:22 <+reavertm> 4.3 is meant to be ABI compliany with 4.2 +21:23 <@scarabeus> ok how about removing prefix totaly +21:23 <@scarabeus> and have live/stable +21:23 * jmbsvicetto looks at bonsaikitten +21:23 <@scarabeus> so live apps are their own env +21:23 <@scarabeus> and the stable is /usr +21:23 * reavertm doesn't get it +21:23 <+reavertm> where does live go? +21:23 <@scarabeus> on the live note we can generate snapshots (weekly) +21:23 <@scarabeus> /usr/kde/live/ +21:24 <@scarabeus> everything live +21:24 <@bonsaikitten> jmbsvicetto: what! +21:24 <+reavertm> how is this different from current situation? +21:24 <@scarabeus> i still prefer your solution +21:24 <@jmbsvicetto> scarabeus: To be honest, I'm losing the "motivation" to keep hammering about kdeprefix, but that was the major issue I had to deal with when we started working back in KDE +21:24 <@scarabeus> reavertm: that there wont be kdeprefix anywhrere else than in live +21:24 <@jmbsvicetto> scarabeus: That's why I've resisted so long to dropping it +21:24 -!- ali_bush [n=alistair@gentoo/developer/alibush] has quit [Remote closed the connection] +21:24 <@scarabeus> jmbsvicetto: well reavers approach is working with +kdeprefix and keeping good usability +21:24 <@jmbsvicetto> bonsaikitten: Do you still care about kdeprefix or not? +21:25 <@scarabeus> trust me it is 500% better than current solution of mine +21:25 * cryos|work has also grown tired of the back and forth... Just want a reasonably stable env for users, and a solution for developers.... +21:25 <@alexxy> kdeprefix can be masked +21:25 <@jmbsvicetto> bonsaikitten: As I recall, you also felt it was important to have it and to allow users to mix versions +21:25 <+reavertm> well, it's not working yet :P +21:25 <@bonsaikitten> jmbsvicetto: my opinion hasn't changed since it was introduced +21:25 <@alexxy> so users who sant it will unmask it +21:25 <+reavertm> (plugins are not loaded properly - amarok issue) +21:25 <@alexxy> but its good fature to have more then one kde release installed +21:26 <@scarabeus> i would say lets see how it work and we can roll it out with 4.2.3 +21:26 <+reavertm> what's all with this masking kdeprefix? +21:26 <+reavertm> you can use.force it if you like :P +21:26 <@jmbsvicetto> cryos|work / bonsaikitten: So, what do you say about this? +21:26 <@scarabeus> i am for reavers solution +21:27 <@cryos|work> Honestly, I am no longer certain what is being proposed. I feel like we really need to pick a solution and try to stick with it. The Apache team went back and forth over a few years and drove many users away... +21:27 <@alexxy> reavertm's solutions better for misk packages +21:27 <+reavertm> my idea (if it works) is to be possible to have kdeprefixed releases and the rest in /usr (accessible from any kde installed) +21:27 <@jmbsvicetto> I guess I'll swallow kdeprefix at this time and will try to force me to look at the build system to allow the multiple versions / better split of packages +21:27 <@bonsaikitten> jmbsvicetto: I haven't followed the discussion enough to have useful input +21:28 <@jmbsvicetto> cryos|work / bonsaikitten: Then if you don't oppose, I say we try reavertm's approach +21:28 <@scarabeus> bonsaikitten: kdeprefix for kde-base, misc apps into /usr including live misc apps +21:28 <@bonsaikitten> sounds acceptable +21:28 <@bonsaikitten> as I haven't contributed anything relevant in a while I don't see why I should be the decider +21:28 <@scarabeus> ok majority already agreed +21:28 <+reavertm> well, there's nothing spectaculat to try now, if it works then we'll see - i need to handle this plugins paths 1st +21:29 <@cryos|work> I can live with it, I would rather be able to put misc live apps in /usr/kde/live too, but can likely hack the ebuilds I care about... +21:29 <@jmbsvicetto> cryos|work / bonsaikitten: If in the end we realize we lost some flexibility, that will only serve to foster the need to look for the real solution (imho) - fixing the build system +21:29 <@bonsaikitten> jmbsvicetto: acceptable :) +21:29 <@scarabeus> bonsaikitten: could you fix at least 258027 +21:29 <+reavertm> actually there's not a problem with restoring kdeprefix for misc apps, but +21:29 <@cryos|work> So you are going to try and mix multiple versions in /usr? +21:29 <+reavertm> live kde-misc would nee to have separate prefix :P +21:30 <@jmbsvicetto> cryos|work: I think that's the "final" solution +21:30 <@jmbsvicetto> cryos|work: I don't have any particular skill or knowledge to get it done, though +21:30 <@cryos|work> That sounds amazingly tough to pull off. +21:30 <@cryos|work> Not this solution though? +21:30 <+reavertm> ok, cryos|work what's your proposition? +21:30 <@bonsaikitten> scarabeus: oh ... let's see +21:31 <+krytzz> hm... would that allow to mix 4.2 kdelibs and live kde-misc stuff for example? +21:31 <+reavertm> maybe it apperas easier to handle than kde-misc in /usr +21:31 <@cryos|work> I don't have one, more trying to understand what this proposal is planning on changing. +21:31 <@jmbsvicetto> cryos|work: That solution isn't "compromised" for the current proposal +21:31 <@scarabeus> the current pospal is easing major bumps, lets stick with it for 4.3 and then we can think about updating the build system +21:31 * cryos|work was just trying to figure out if he understood what *this proposal* encompassed. +21:32 <+reavertm> ok, let me summarize +21:32 <+reavertm> the problem with kdeprefix for kde-misc apps is as follows : +21:33 <+reavertm> let's say we have taglib-extras +21:33 <+reavertm> it has optional kde integration +21:34 <@cryos|work> So you are concerned with corner cases? +21:34 <+reavertm> still it's just typical lib and should be accessed globally - it would be nice for it to not be kde-prefixed +21:34 <+reavertm> or any other app - like amarok - I want it installed and used from any KDE4 i have (and I have 4.2, 4.3, live) +21:34 <@cryos|work> I totally agree. I was the one who wanted to throw everything in /usr apart from development builds where people got to pick up the pieces themselves... +21:35 <@cryos|work> If I develop on amarok I can write a custom ebuild if I want it in my /usr/kde/live as any dev can, so the impact is not terrible. +21:35 <@cryos|work> I was more trying to confirm the scope of the changes proposed. +21:36 <@jmbsvicetto> reavertm: The only issue I see and the reason for the kdeprefix is if you have k3b-1.* working and want to follow k3b-2.* (which I think is still broken), you're not willing to have to choose between one or the other +21:36 <@jmbsvicetto> reavertm: But as stated, I'm going to drop my "resistance" +21:36 <+reavertm> k3b-1 will be installed in kde3 prefix so i am told +21:36 <+reavertm> (tampakrap?) +21:36 <@cryos|work> That was my concern, but those users could be out of luck... +21:36 <@cryos|work> At some stage having too much choice can spread us too thin. +21:37 <@cryos|work> Many distros are just dropping KDE 3 entirely already. +21:37 <@jmbsvicetto> cryos|work: yeah. The problem is that some users have been mailing us asking us not to do it +21:37 <@scarabeus> ok put it straight: lets just comfor for now on that we are going to support unprefixing misc apps +21:37 <@jmbsvicetto> cryos|work: And I think we haven't convinced everyone in the kde team that kde-4 is better +21:37 * jmbsvicetto looks at yngwin +21:37 <@cryos|work> I am not proposing we do - I am just pointing out what is happening. +21:38 <@jmbsvicetto> cryos|work: I agree +21:38 <@cryos|work> I think many distros dropped KDE 3 too soon. +21:38 <+reavertm> kdeprefix as great idea and flexibility it adds, it's pain in ass to mantain :P +21:39 <@cryos|work> I was more making the point that Gentoo has such an extreme amount of choice compared to other distros we could end up chasing bugs no-one else cares about that only crop up in slotted envs. +21:39 <+reavertm> (btw, eselect for kde is not required) +21:39 <@cryos|work> Reducing overall quality which is bad. Not claiming I have the answer either... ;-) +21:40 <@scarabeus> :] +21:40 <@jmbsvicetto> we're all brainstorming ;) +21:40 <@jmbsvicetto> tampakrap: How's your work on the kde3 eclasses going? +21:41 <@cryos|work> I am very attached to Gentoo and KDE. I don't want to see it go to crap, don't have as much time as I would like these days. +21:41 <@tampakrap> eclasses are ready +21:41 <@tampakrap> i'm still on the ebuilds +21:41 <@scarabeus> and the packages are compilling fine? +21:41 <@jmbsvicetto> tampakrap: kdeprefix isses on kde4 are hurting us, but colisions with kde3 apps are doing us more harm (imho) +21:41 <@cryos|work> Bumped avogadro for the super nerdy people who want to play though ;-) +21:41 <@tampakrap> i'll tell you what i need +21:41 <@tampakrap> if there are two people willing to test kde3 misc apps that would be greate +21:42 <@tampakrap> great +21:42 <@scarabeus> herd testers i bet +21:42 * wired raises hand +21:42 <@yngwin> evening +21:42 <@scarabeus> also write mail to desktop and dev +21:42 <+wired> yngwin: =] +21:42 <@jmbsvicetto> tampakrap: with kde4 env? +21:42 <@alexxy> cryos|work: i'll test it with students (avogadro) +21:42 <+reavertm> btw, masking kdeprefix is good idea for typical users +21:42 * yngwin completely forgot about the meeting, sry +21:42 <@tampakrap> i'll prepare a list with the packages and eapi2 as well them +21:42 <@jmbsvicetto> tampakrap: if so, I can do some tests +21:42 <@cryos|work> alexxy: Great - I fixed the desktop file among many other things... +21:42 <@tampakrap> i'm on kde-base only still +21:42 <@alexxy> reavertm: yep +21:43 <+reavertm> I guess it should be done when 4.2.2 is introduced +21:43 <@cryos|work> reavertm: That was always my point - typical users don't want/understand kdeprefix. If they do they will unmask and use. +21:43 <@alexxy> i think kdeprefix is not for users +21:43 <@alexxy> =) +21:43 <@cryos|work> It is awesome for devs/power users though. +21:43 <+wired> many users activate it without knowing though, mask++ +21:43 <+krytzz> hm... i thought gentoo is for powerusers? +21:43 <@jmbsvicetto> cryos|work: iirc, kdeprefix is no longer an IUSE default +21:44 <+reavertm> I want 4.2.2 stable in portage, so let make it easier for users to use +21:44 * yngwin is with krytzz +21:44 <@scarabeus> krytzz: you. sent. ssh key. me. now +21:44 <@cryos|work> jmbsvicetto: I didn't know it ever was. +21:44 <+reavertm> jmbsvicetto: yeah, but still users see USe flag and enable it out of curiosity :P +21:44 <+wired> krytzz: the definition of a poweruser is amazingly flexible these days.... +21:44 <+krytzz> scarabeus: ok, few minutes +21:44 <+krytzz> wired: ok well +21:44 <@scarabeus> cryos|work: YOU CHANGED IT TO ENABLED BY DEFAULT FIRST :D +21:44 <@scarabeus> heh caps +21:45 <@cryos|work> Many Gentoo users are not what I would call power users, but I guess by definition we have more advanced users than *buntu for example.. +21:45 <@cryos|work> scarabeus: For :live only! +21:45 <+wired> we also have a lot of users who'd want to be powerusers +21:45 <@alexxy> he he =) +21:45 <+wired> =] +21:45 <@yngwin> i'd say gentoo targets powerusers +21:46 <@yngwin> doesnt mean all our users are tho +21:46 <@jmbsvicetto> reavertm: well, that's the same thing as CFLAGS. Gentoo's policy has never been to hide it from the user - even if that leads to user bitting himself in the rear ;) +21:46 <+krytzz> wired: lol +21:46 <+reavertm> btw, our existing problems with kdeprefix *only* phonon and pykde +21:47 <@jmbsvicetto> reavertm: +affect? +21:47 <@scarabeus> ok back on topic tampakrap are you able to get needed stuff around here or you need our direct intervention (ak more devs searching for testing monkeys?) +21:47 <+reavertm> jmbsvicetto: hmm? +21:47 <@tampakrap> no just some testing mostly +21:48 <@tampakrap> i don't think we should waste more manpower on kde3 +21:48 * wired now that we're all here, can someone pretty please cp the latest .2 tbz2s to d.ge.o? +21:48 <@jmbsvicetto> reavertm: never mind +21:48 <+reavertm> ah, right - phonon and pykde4 - the only really kdeprefix *issue* +21:48 <+reavertm> the rest is just inconvenience +21:49 <@jmbsvicetto> reavertm: The phonon issue is mostly upstream "hard-coding" the plugins location, right? +21:49 <@scarabeus> ok so kde3 is moving forward, i would say that we need to have it done by end of april some time on may... so we can actualy stable the kde4 +21:49 <+reavertm> I can easily not drop kdeprefix and install 3rd party apps with kde they were built against (still changing need_kde behaviour) +21:50 -!- smith_ [n=smith_@adsl-62-167-36-86.adslplus.ch] has joined #gentoo-kde +21:50 <+reavertm> phonon issue is bunding KDE plugins with phonon +21:50 <@jmbsvicetto> scarabeus: we need to go for 3.5.10 stable *soon* +21:50 <@scarabeus> jmbsvicetto: btw i would like to mask the kde +21:50 <@scarabeus> jmbsvicetto: old nonsplit stuff i mean +21:50 <+reavertm> hence, phonon should be in location visihble by all KDE releases +21:50 <@jmbsvicetto> 3.5.9? +21:50 <+reavertm> or kdeprefixed +21:51 <@scarabeus> jmbsvicetto: yes +21:51 <@jmbsvicetto> scarabeus: Not without 3.5.10 stable! +21:51 -!- mikkoc [n=mikko@host254-81-dynamic.7-79-r.retail.telecomitalia.it] has quit [Read error: 60 (Operation timed out)] +21:51 <@jmbsvicetto> scarabeus: unless you're the one doing it and I can redirect all bugs, mails, threats, ... to you :P +21:51 <@yngwin> well, we can leave split 3.5.9 unmasked, and just mask the monolithic pkgs +21:52 <@jmbsvicetto> yngwin: we could, but we have quite vocal users already complaining about the drop of the monos for 3.5.10 +21:52 <+reavertm> or just put proper blocks +21:52 <@yngwin> then when 3.5.10 is stable, we can mask the rest +21:52 <@yngwin> jmbsvicetto: well, too bad, i'd say +21:52 -!- mikkoc [n=mikko@host182-164-dynamic.56-82-r.retail.telecomitalia.it] has joined #gentoo-kde +21:52 <@jmbsvicetto> ok +21:52 <@yngwin> or someone must stand up to become monolithic maintainer +21:53 <+reavertm> jmbsvicetto: who are those vocal users? +21:53 -!- anselmolsm_ [n=anselmo@200.184.118.130] has joined #gentoo-kde +21:53 <+reavertm> devs by occasion? +21:53 <@jmbsvicetto> reavertm: no +21:53 <+reavertm> idf so, let them step up to maintain :P +21:53 -!- anselmolsm [n=anselmo@200.184.118.130] has quit [Read error: 113 (No route to host)] +21:54 <@jmbsvicetto> reavertm: hehe, wait until you become a dev and you'll see how "demanding" some users can be ;) +21:54 <+reavertm> and what was basis for their objections? +21:54 -!- anselmolsm_ is now known as anselmolsm +21:55 <+reavertm> write migrating guide (if there's no already) and that's all. period +21:55 <@yngwin> we've had that for years +21:55 <@scarabeus> yeah i was speaking about the monos +21:55 <@jmbsvicetto> Some people just want monos. I haven't seen many and in particular good motives. But they want them, nonetheless +21:55 <+reavertm> Qt4 split was much more difficult yet it was done +21:55 <+reavertm> jmbsvicetto: I want reiser4 in gentoo-sources and? +21:55 <@jmbsvicetto> ok, ok +21:56 <+reavertm> some people want some things and they won't have it nevertheless :P +21:56 <@yngwin> use hitchhiker-sources then +21:56 <@jmbsvicetto> When they knock at my door I'll be sure to point them somewhere else ;) +21:56 * cryos|work has a meeting... Bye! +21:56 <+krytzz> bye +21:56 <@jmbsvicetto> bye cryos|work +21:56 <+reavertm> jmbsvicetto: let me brainwash them then +21:56 <+reavertm> bye cryos|work +21:56 <+wired> bye cryos|work +21:56 * cryos|work will try to contribute more this month! +21:56 <@jmbsvicetto> scarabeus: sorry for the disturbance. +21:57 <@jmbsvicetto> So, about kdeprefix we're done, right? +21:57 <@scarabeus> bb +21:57 <@scarabeus> yes +21:57 <@scarabeus> kde3 and kdeprefix is done +21:57 <@jmbsvicetto> about 3.5 tampakrap will do more tests and is searching for people to help with kde-misc apps +21:57 -!- mx-tvt [n=quassel@bl9-29-140.dsl.telepac.pt] has quit [Read error: 110 (Connection timed out)] +21:57 <+reavertm> I'll see what i can do - anyway i propose some my changes in eclass anyway as it's much shorter and easier to read now +21:57 <@jmbsvicetto> scarabeus: What's next? +21:58 <+reavertm> plasmoids to tree +21:58 <+reavertm> pros/cons :) +21:58 <@scarabeus> yeah i think we can start adding them +21:58 <@scarabeus> we cook them since pre 4.1 and still in the overaly +21:58 <@scarabeus> so lets make users happy +21:58 <+reavertm> I haven't tested all of them yet +21:58 <@jmbsvicetto> They're in kde-misc now, right? +21:59 <@scarabeus> i will add only those i personaly tested +21:59 <@yngwin> reavertm: that's what ~arch is for +21:59 <@yngwin> :p +21:59 <@scarabeus> jmbsvicetto: yes i did the move, actualy forced wire to move it +21:59 <+wired> i've tried them all at least once +21:59 <@jmbsvicetto> scarabeus: In that case I have nothing to say ;) +21:59 <+reavertm> anyway i already found one problem - systemmontor or sth has been moved to kdeplasma-addons and conflicts with kdeplasma-addons:live +21:59 <@scarabeus> ok i just want to hear OK :D +21:59 <+reavertm> about plasmoids +21:59 <+wired> most of them get regular updates btw and there are a lot more available in kde-look +21:59 <+reavertm> let me check them 1st +21:59 <@jmbsvicetto> reavertm: we can add a block on a slot package +22:00 <+reavertm> I fixed most deps in kde-misc but still something may be wrond there +22:00 <+wired> i think most plasmoids are simple enough to be safely added to ~ +22:00 <+reavertm> wired applied blocks already +22:00 <@scarabeus> ok this one was quick +22:00 <@scarabeus> so we just test them and start moving +22:00 <@scarabeus> :] +22:01 <@scarabeus> next is printing +22:01 <@scarabeus> reavertm: how is it looking +22:01 <+reavertm> printing.. +22:01 <@jmbsvicetto> scarabeus: what are we missing? The deps? +22:01 <@scarabeus> jmbsvicetto: we have everything +22:01 <@scarabeus> jmbsvicetto: the problem is it pulls half of gnome +22:01 <+reavertm> if I leave it as it is now - system-config-printer-kde is done, printer-applet not yet +22:01 <+reavertm> scarabeus: no longer +22:01 <@scarabeus> the better then +22:02 <@scarabeus> ok so i will coordinate it with you after 4.2.2 is released (weekend probably) +22:02 <@scarabeus> reavertm: agreed +22:02 <@scarabeus> ? +22:02 <+reavertm> just let me finish printer-applet the way I did system-config-printer-kde (taking some files from system-config-printer) and they can go +22:02 <+reavertm> scarabeus: yeah +22:03 <@scarabeus> ok cool then +22:03 <@scarabeus> jmbsvicetto: do we have any response on the snapshot thingie? +22:03 <+reavertm> I made system-config-printer-kde is totally independent from system-config-printer +22:03 <@jmbsvicetto> Not that I have seen +22:03 <@jmbsvicetto> scarabeus: I sent the mail 2 days ago, though. +22:03 <@alexxy> so they simply ignoring us +22:03 <@scarabeus> jmbsvicetto: ok so alexxy will have to do it himself for all the time +22:04 <@jmbsvicetto> scarabeus: I think as cryos|work was suggesting, we ignore them for now and keep doing the work alexxy is doing +22:04 <@scarabeus> alexxy: btw i heared some noise about l10n not working +22:04 <@alexxy> scarabeus: its working for -kdeprefix +22:04 <+reavertm> Dirk was in kde-devel for a minute +22:04 <@alexxy> didnt test it with +kdeprefix +22:04 <@alexxy> =) +22:04 -!- mkyral [n=maros@nezmar.jabbim.cz] has left #gentoo-kde [] +22:04 <@scarabeus> ok then it is their issue they can fix it +22:05 -!- sIbOk [i=sNOUbOR@56.Red-80-36-227.staticIP.rima-tde.net] has joined #gentoo-kde +22:05 <@scarabeus> jmbsvicetto: again one more on you +22:05 <@scarabeus> jmbsvicetto: how is dead member removing +22:05 <@scarabeus> going on +22:05 <@jmbsvicetto> I'm going to go over the retirement bugs (I think a few of them have already retired) and will then send mails to the folks that haven't been around for a long time +22:06 <@jmbsvicetto> I'll have the page cleaned by next meeting +22:06 <@scarabeus> ok +22:07 <@scarabeus> pykde +22:07 <@scarabeus> bonsaikitten: +22:07 <@scarabeus> so you say it works +22:07 <@scarabeus> despite the bugs in bugzilla +22:07 <@bonsaikitten> I haven't been able to reproduce +22:07 <+reavertm> problem with pykde4 is kdeprefix +22:07 <@bonsaikitten> I guess I'll need to change my testing strategy :) +22:07 <+reavertm> all kde installs pykde4 in site-packages +22:07 <@jmbsvicetto> reavertm: build or runtime error? +22:07 <@alexxy> so lets mask kdeprefix use flag +22:07 <@alexxy> =) +22:07 <+reavertm> install +22:07 <@alexxy> like it was for networkmanager +22:07 <+reavertm> so - two choices +22:07 <@scarabeus> there was sip buildtime errors +22:08 <+reavertm> make eselect module or slot them properly +22:08 <@jmbsvicetto> reavertm: I have pykde-4.2.1 installed with +kdeprefix here +22:08 -!- kamik [n=quassel@dslb-088-065-079-200.pools.arcor-ip.net] has joined #gentoo-kde +22:08 <+reavertm> so that pykde4 live will go to /usr/kde/live and so on +22:08 <+reavertm> jmbsvicetto: install pykde4-9999 as well +22:08 <+reavertm> you need package.provided entry now to do it +22:09 <@jmbsvicetto> reavertm: I'm not running live ebuilds here +22:09 <+reavertm> well, some people are :) +22:09 <@jmbsvicetto> sure, I'm just conveying my experience here +22:09 <@scarabeus> one +kdeprefix is ok +22:09 <@scarabeus> more than one kdeprefix is fail +22:09 <@scarabeus> for pykde +22:09 <@jmbsvicetto> ah, ok +22:10 <+reavertm> hell, it even install files in /usr/share/sip +22:10 <+reavertm> (apart from site-packages) +22:11 <+reavertm> bonsaikitten: some QA notice says that precompiled modules need to go to site-packages +22:11 <@bonsaikitten> :( +22:11 <+reavertm> is it possible to create external site packages in kde slot? (/usr/kde/4.2 etc) +22:12 <+reavertm> and set some PYTHON_PATH or whatever in startkde? +22:12 <@jmbsvicetto> This is why having multiple versions around in /usr is going to be "messy" :\ +22:13 <+reavertm> bonsaikitten: what useful python env variables do you know that would help here? :) +22:13 <@jmbsvicetto> reavertm: perhaps the correct solution here would be to remove the python files and have a single package that is used by all versions? +22:13 <+reavertm> that is also possible but... +22:14 <+reavertm> pykde4 happeds to install /usr/kde/live/lib64/kde4/kpythonpluginfactory.so +22:14 <+reavertm> which is in kdeprefixed location +22:14 <@jmbsvicetto> if they didn't break abi compatibility, it should be possible to use the latest pykde version with earlier 4.X releases +22:14 <+reavertm> installing it in /usr prefix is the same thing like installing kde-misc in /usr +22:15 <+reavertm> (may not work - like this plugin thing I'm struggling with) +22:16 <+reavertm> yes, I'm not worrying about linking, it should work - still ebuild would need some tweaks to make it build not agains kde release it is from but minimal installed +22:16 <@jmbsvicetto> reavertm: pkgconfig!! +22:16 <@scarabeus> he he he +22:16 <@scarabeus> again prefix you +22:16 <@scarabeus> SILENCE +22:16 <@scarabeus> :D +22:17 <+reavertm> what is pkgconfig going to solve? +22:17 <@alexxy> lets mask kdeprefix =) +22:17 <+reavertm> buildig is no longer an issue :P +22:17 <+reavertm> running is :) +22:17 <@jmbsvicetto> If they were using autotools they could use pkgconfig to chose the minimum so version needed +22:18 <+reavertm> jmbsvicetto: ah, eclass does it already +22:18 <+reavertm> (picks lowest kdelibs, yet >=KDE_MINIMAL) +22:18 <@scarabeus> ok i gues we are done with the pykde :P +22:18 <+reavertm> are we? +22:18 <@yngwin> hardmask? +22:18 <+reavertm> what's the solution then :P +22:18 <@scarabeus> yeah lets kitten handle it +22:19 <@scarabeus> also write whiny mail on dev +22:19 <+reavertm> I'd slot the f*er +22:19 <@jmbsvicetto> scarabeus: hehe - solution? hand it over to Patrick ;) +22:20 <+reavertm> along with phonon +22:20 <@scarabeus> jmbsvicetto: yup +22:20 -!- cypr1nus [n=cypr1nus@plus.ds14.agh.edu.pl] has quit [Read error: 104 (Connection reset by peer)] +22:20 <@scarabeus> (i am practising my "solid-rock" face) +22:20 <+reavertm> or ,If I get plugins in /usr to work, it will be solved +22:20 <@scarabeus> :] +22:21 <@scarabeus> so, um, what was next, ah, koffice2 +22:21 <@jmbsvicetto> reavertm: I haven't looked at that in a long time, but can't you specify more than 1 RPATH? +22:21 <@jmbsvicetto> reavertm: more than 1 dir in RPATH +22:21 <+reavertm> RPATH is not problem, they are all linked well, just app can't find those plugins +22:21 <@jmbsvicetto> isn't it supposed to look in the compiled RPATH? +22:22 <+reavertm> I am yet to check some things +22:22 <+reavertm> for plugins? no +22:22 <+reavertm> RPATh is just for linker +22:22 -!- neuron [n=neuron@85.252.65.217] has joined #gentoo-kde +22:23 -!- Civil [n=Civilian@95-24-156-60.broadband.corbina.ru] has quit [Remote closed the connection] +22:23 <+reavertm> if plugins are in /usr/kde/XXX/lib64/kde/ and /usr/kde/XXX/lib64/kde/plugins - app needs to know where to find them +22:24 <+reavertm> (usually just works if app was comopiled against kde XXX and istalled in /usr/kde/XXX +22:24 <+reavertm> otherwise it fails to find them even when KDEDIRS and QT_PLUGIN_PATh is pointed there +22:25 <+reavertm> yet I'm to test some things so we'll see - it should work somehow +22:25 -!- cypr1nus [n=cypr1nus@plus.ds14.agh.edu.pl] has joined #gentoo-kde +22:25 -!- looonger [n=looonger@host-89-231-128-7.rawamaz.mm.pl] has quit [Client Quit] +22:25 <+reavertm> I have manually compiled kdevelop in ~/kde4 and my KDEDIRS just points there and it workds +22:26 <+reavertm> so maybe it's something with building it gentoo way +22:26 <+reavertm> (I guess I'll try kdeprefix-less kdevelop...) +22:27 -!- _Phlogi [n=quassel@138-135.1-85.cust.bluewin.ch] has joined #gentoo-kde +22:27 <+reavertm> ok, what's next? +22:27 -!- non7top [n=non7top@94.77.134.21] has quit [Remote closed the connection] +22:27 <@scarabeus> koffice +22:28 <+reavertm> I built kword and it works +22:28 <@scarabeus> the state is i fixed the crap +22:28 <@scarabeus> it works +22:28 <@scarabeus> problem is that it is not much usable +22:28 <@scarabeus> they are going to release it at the end of this month +22:28 <@scarabeus> so i will add it to the tree +22:28 <+reavertm> 2.0? oh crap +22:28 <@scarabeus> but i am not sure if it should go masked or not +22:28 <@scarabeus> 2.0 indeed +22:29 <+krytzz> released? oh zomg :p +22:29 <@jmbsvicetto> scarabeus: maybe we should get an rc in the tree first, no? +22:29 <@scarabeus> jmbsvicetto: ideas? +22:29 <@scarabeus> well i have the tarball and it is just matter of renaming +22:29 <@scarabeus> anyone can do it +22:29 <@jmbsvicetto> scarabeus: the rc could be masked and pending bug reports, 2.0 would be unmasked or not +22:30 <@jmbsvicetto> The 2.0 tarball? +22:30 <+reavertm> btw, let someone just in any case look at those ebuilds and see whether deps are correct (rdepend, depend, commondepend handled carefully) +22:30 <@scarabeus> yeah i am worried about it and in doubts +22:30 <@scarabeus> it definetly is stable +22:31 <@scarabeus> but it lacks some features and it looks just ugly +22:31 <@tampakrap> i like the :live one though +22:31 <@tampakrap> haven't tested the releases +22:31 <@tampakrap> maybe we can create snapshots +22:32 <@scarabeus> what for +22:32 <@scarabeus> i have todays taged rc1 +22:32 <@scarabeus> :D +22:32 <@tampakrap> ok then +22:32 <+reavertm> KOffice 1.9.99.0 RC1 uploaded +22:32 <@scarabeus> not yet, it is on ktown :] +22:32 <+reavertm> just pasted announcement +22:32 <@scarabeus> jmbsvicetto: so what do you thing the stable at the end of the month as pure testing or hardmasked? +22:33 <@jmbsvicetto> I haven't used koffice myself, so I'm not sure +22:34 <@jmbsvicetto> But if you're in doubt, try pusing something masked into the tree and check for bug reports +22:34 <@scarabeus> ok +22:34 <@scarabeus> good idea +22:35 -!- Varox [n=Varox@p4FD44E52.dip.t-dialin.net] has joined #gentoo-kde +22:35 <@scarabeus> last thing on the list: +22:35 <@scarabeus> moving the meeting date +22:35 <@scarabeus> i would like to see meeting 14 days before upstream release for public +22:35 <@jmbsvicetto> pushing* +22:35 <@jmbsvicetto> scarabeus: releases what? ;) +22:36 <@tampakrap> we don't have much to talk before release i think +22:36 <@scarabeus> kde +22:36 <@scarabeus> we are kde team +22:36 <@tampakrap> after release is everything that comes in surface +22:36 -!- sIbOk [i=sNOUbOR@56.Red-80-36-227.staticIP.rima-tde.net] has quit ["kUALKIER hiJO dE pUTA sAbE lO q dARTE sI tIENE q dOLERTE pERO No kUALKIER hiJO dE pUTA sABE lO q dARTE sI tIENE q gUSTARTE, y] +22:37 -!- helch [n=helch@212-41-103-166.adsl.solnet.ch] has quit [Remote closed the connection] +22:38 <@scarabeus> hmm +22:38 <@scarabeus> what does other think? +22:39 <+krytzz> hm +22:39 -!- Phlogi [n=quassel@138-135.1-85.cust.bluewin.ch] has quit [Read error: 110 (Connection timed out)] +22:40 <+wired> maybe a week is enough? +22:40 <+krytzz> i would agree with tampakrap i think, but i have nothing against short-dated meetings +22:40 <@jmbsvicetto> scarabeus: floating schedule or point to 3rd Thursday of the month? +22:40 <@scarabeus> 3rd thursday i had on my mind +22:40 <+krytzz> when $PANIC_LEVEL reaches 10 would be good :p +22:41 <@scarabeus> well or 4th week +22:41 <@jmbsvicetto> krytzz: Isn't it too late by then? ;) +22:41 <@scarabeus> the problem is that release is today +22:41 <+krytzz> k... 9? :p +22:41 <@jmbsvicetto> scarabeus: 4th will hit council meetings +22:41 <@scarabeus> ok i will write to summary what ever you decide :] +22:42 <@jmbsvicetto> I think 3rd would be better, but am open to other dates +22:42 <@yngwin> 3rd sounds good +22:43 -!- MaNI [n=malcolm@dsl-247-169-66.telkomadsl.co.za] has joined #gentoo-kde +22:45 <@scarabeus> ok i go for 3rd too then +22:45 <@jmbsvicetto> So, what are we missing? +22:45 <@tampakrap> one last joke +22:45 <@tampakrap> hwoarang wants me to change my cloak to gentoo/slacker/tampakrap +22:46 <@scarabeus> hm and you could not write this yesterda +22:46 <+krytzz> hehe +22:47 <@alexxy> he he =) +22:47 -!- g1lt [n=quassel@203-79-94-158.cable.telstraclear.net] has joined #gentoo-kde +22:48 <@scarabeus> jmbsvicetto: http://dpaste.com/22343/ +22:48 <@scarabeus> jmbsvicetto: again no log, i didnt reboot my client yet :D +22:48 <@scarabeus> uptime 48 days cant be ruined :D +22:50 <@jmbsvicetto> hehe +22:50 <@jmbsvicetto> tampakrap: You have a long road to go before you qualify for that :P +22:50 <@jmbsvicetto> tampakrap: We have real "slacker" experts around here ;) +22:50 <@tampakrap> i don't think so, take a look at my cia.vc page +22:51 <@jmbsvicetto> So are we done? +22:51 <@tampakrap> yes, where is the summary? +22:51 * reavertm unpauses music +22:52 <@jmbsvicetto> In that case, let me remind people that we still have a *few* open bugs and that we should all try to help get that number down +22:52 <@scarabeus> tampakrap: http://dpaste.com/22343/ +22:52 <@scarabeus> yeah and ehm officaly meeting is over ;] diff --git a/meeting-logs/20090521-summary.txt b/meeting-logs/20090521-summary.txt new file mode 100644 index 0000000..8b52f4f --- /dev/null +++ b/meeting-logs/20090521-summary.txt @@ -0,0 +1,182 @@ +21.5.2009 - KDE Meeting +Roll-call: wired, alexxy, scarabeus, dagger, hwoarang, tampakrap, bonsaikitten, krytzz, yngwin, civil, papillon81, reavertm, lxnay, cryos, jmbsvicetto + +Cryos legitimely excused from not attending much, new baby on the route. Grats to him! :] + +Doc handling +- doc == aplication handbook or handbook, to be decided... +- enable +doc/handbook by default for kde-base +- aplication api documentation - scarabeus write mail asking for some global useflag for it on -dev +- rename doc useflag to handbook with 4.3 again :D +- make it more handleable by eclass rather than in the ebuilds +- lxnay volunteer to do the packages update in overlay +- so priority coruse is: + - mail to dev asking how to do it + - wait a bit and if nothing constructive comes up do the rename for 4.3 + +kde3 +- kill arts, all misc apps needs it removed and be stabled before 3.5.10 stabling +- stable 3.5.10, all kde related misc apps needs to be revbumped/verbumped and stabled before it +- tampakrap starts handling 3.5.10 stabilisation - stable bug asap 15.6. deadline +- writing doc about kde3/4 mixing - tampakrap + +kdeprefix +- long discussion about support of kde4 +kdeprefix install in kde3 and gnome, will chat with reaver about it on aproperiate bug +- add ewarn for user when installing with +kdeprefix so we assure he knows what he is messing with. (controled same like live warning) + +kde 4.3 +- libknotification already handled, pdepend for kdelibs. +- policykit looks ok +- so no much work for 4.3 itself + +kde/kde3 useflag +we voted about it, result: +kde - latest supported kde 4, 5, whatever +kde3 - for now kde 3 series, when kde5 is out there will be kde4 useflag and so on,... +as long as new version is expected to be highly experimental we will have kdeX where X is the version number. When proper support in portage arrives it mutate into kde and older kde mutate to kdeY where Y is X-1 + +phonon +- ship snapshot into the tree with kde 4.3 +- separating xine part to be able use qt-phonon instead of normal phonon with kde - probably reaver + +CODE: +improve it, and add requirements we find out that are needed +since next meeting the code will be considered final, and not folowing it will be punished + +relwithdebuginfo: +deffered after some work on it, not worth efforts + +GUIDE: +tampakrap promised to write the guide for kde3/4 mix that will cover also kde4 installing + +kdebindings: +scarabeus + reaver: invent some logic there; delegate work to other HTs + +sabayon: +discuss the topic more with joost_op at some other more convinient time +so far done -> +bugs from ppl with @sabayonlinux.org will be handled legitimely as our bugs +and we will reflect them as HTs for kde team so we dont have recheck reported things (aka we trust sabayon devs :}) + +------------------------------------------------ +Qt topics +------------------------------------------------ + +Rollcall Qt herd +---------------- + +- hwoarang, tampakrap, yngwin present +- carlo absent +- recruits wired, Pesa and spatz present + + +Meeting length +-------------- + +The KDE Project meeting was going on for too long, all agreed. It was suggested +that it would be good to have more frequent and shorter meetings. Also, Qt +topics could be discussed early in the meeting. Details will be discussed at +another time. + + +Phonon issues +------------- + +KDE herd has asked us to introduce a kde useflag for ebuilds depending on:: + || ( x11-libs/qt-phonon media-sound/phonon ) +so that media-sound/phonon can be preferred for KDE users, as a workaround for +current portage shortcomings. yngwin will work out a proposal for affected Qt +ebuilds. + +Also, the suggestion was offered to split the backends from phonon into +separate packages (gstreamer from qt-phonon, and xine from kde's phonon), so we +could have one phonon core package (most likely x11-libs/qt-phonon). It was +decided that this is worth looking into. + + +Recruits +-------- + +As to the status of recruits for the Qt team: + +- wired is done with the quizzes, so he only needs grilling by a recruiter and + can be expected to become a full dev within the next few weeks +- Pesa has been very active already in contributing +- spatz just joined us as newest recruit +- sping is busy with GSoC and will continue recruitment process after that, he + is especially interested in Qt3/KDE3 maintenance + + +Qt status in tree +----------------- + +- bug 266201: 4.5.1 is going stable, but arches are taking their time (only + alpha and ppc so far) +- bug 270475: bug in the eclass about the platform switch, which affects + chroots and some arches like ppc, a solution is being worked on in the + overlay +- bug 235685: webkit sigbus on sparc, we will try to get upstream to fix it, in + the meantime we can use a patch on sparc only (and maybe on other arches like + alpha) +- bug 270769: ppc rendering fix will be fast-tracked for stabilization +- bug 209626: make qt eclasses ready for eclass-manpages, hwoarang offered to + take care of this +- bug 224951: qt4-qtruby has been hardmasked for a while, so we should fix or + remove the package; decided we'll work on it to see if it's fixable, + otherwise ask ruby herd to agree with removal; yngwin will commit his + intermediate work to overlay +- bug 236341: Pesa and hwoarang will work on removing automagic deps from PyQt4 +- bug 43827: qvfb and related embedded ebuilds could be proxy-maintained, we + will approach users that might be interested + + +Overlay +------- + +As mentioned during the discussion of the KDE overlay's CODE document, we +should start using similar commit policies, especially starting the commit +message with $PN. + +Both 4.5.9999 and 4.9999 versions of Qt ebuilds in overlay are actively +maintained and used, so status is OK. + +A lot of packages are being moved from overlay to the official tree, so work +there is progressing well. Pesa will work with ali_bush to get the latest +version of qtjambi into the tree. + + +Eclasses +-------- + +There has been discussion on -dev ML about blocking mixed Qt versions. Paludis +doesn't handle the blocks and dependencies the same way portage does, but it +was concluded that the proposal currently in overlay, which works fine with +portage, is the best solution so far, so we will go ahead and implement that in +the official tree as well. + +It was also decided to remove the custom-cxxflags useflag and the default +strip-flags from the qt4-build.eclass, as testing has shown that Qt is not as +sensitive to optimized flags anymore. We will let this change coincide with +committing the 4.5.2 (next release) ebuilds into the official tree. + +There has been a lot of development going on in the qt4-edge.eclass (the +overlay version of qt4.eclass). We have implemented additional default phases +for src_configure and src_install, the eqmake4 function has seen a lot of +improvements, and there is experimental functionality for handling translation +files. + +We decided to add that as a new eclass to the official tree, once the ongoing +work on eqmake4 and translations crystalizes. We will then mark the old eclass +as deprecated and open a tracker bug for migration of packages to the new +eclass. There was some brainstorming about naming the new eclass, but +bikeshedding is to be continued outside of the meeting. + + +Elected Qt team lead +-------------------- + +As we are now a fast growing team, yngwin felt the need to bring up the issue +of elections for a Qt team lead, as he assumed the position when no one was +looking after qt herd. The decision was this is not needed, as the team members +are unanimously happy with the current situation of yngwin being the de facto +leader. diff --git a/meeting-logs/20090521.txt b/meeting-logs/20090521.txt new file mode 100644 index 0000000..c66ea36 --- /dev/null +++ b/meeting-logs/20090521.txt @@ -0,0 +1,1769 @@ +22:00 (@alexxy) !time +22:00 (Willikins) alexxy: Europe - Moscow - Thu May 21 23:00 MSD +22:00 (@alexxy) heh +22:00 (@scarabeus) roll-call slackers +22:00 (+wired) w000t +22:00 (@alexxy) time to start +22:00 (@scarabeus) !herd kde +22:00 (@alexxy) =) +22:00 (Willikins) (kde) alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, patrick, scarabeus, tampakrap, tgurr +22:00 (+wired) meh +22:00 (+wired) hopefully last meeting im not in that list +22:00 (dagger) huh +22:00 (+wired) :D +22:00 (@alexxy) time to start meeting +22:00 (nirbheek) hurr hurr +22:00 (@scarabeus) Time to start meting :D +22:00 (@alexxy) who is here? +22:00 -> tampakrap +22:00 (@hwoarang) wait! +22:00 (nirbheek) Time to start mating! +22:00 -!- Pesa [n=Pesa@bluemchen.kde.org] joins -> #gentoo-kde +22:00 (@hwoarang) !herd qt +22:00 (dagger) alexxy: I'm not here :) +22:00 (@hwoarang) ladies? +22:01 (dagger) hwoarang: lol +22:01 (Willikins) (qt) carlo, hwoarang, tampakrap, yngwin +22:01 (Gentle) is the libusb blocker ( http://dpaste.com/46414/ ) known? How to best avoid it? +22:01 (nirbheek) !herd gnome +22:01 (Willikins) (gnome) dang, eva, ford_prefect, leio, nirbheek, remi +22:01 (+wired) that list as well +22:01 (nirbheek) Low attendance, hmmm. +22:01 (@hwoarang) Pesa: dont hide , come over here +22:01 (+wired) nirbheek: lolz +22:01 (Pesa) i'm here, just in time :D +22:01 (@scarabeus) bonsaikitten: you too, are you around? +22:01 (@bonsaikitten) no, I'm a square +22:01 -!- mode/#gentoo-kde [+vvvv papillon81 Phlogi _Phlogi Civil] by scarabeus +22:01 (@alexxy) bonsaikitten: or you square today? +22:01 (@bonsaikitten) :) +22:01 (nirbheek) bonsaikitten, lrn2read vowels +22:02 (@scarabeus) :D +22:02 (nirbheek) So, wait, this is it? This is the meeting? +22:02 (@scarabeus) so we are missing few devs, and importantly our lead +22:02 (nirbheek) rollcall followed by silence? +22:02 (+krytzz) im a triforce +22:03 (cvandonderen) I want to join too! :-D:-P +22:03 (@alexxy) jmbsvicetto: !!!!! +22:03 (dagger) should I *stab* him? +22:03 (+wired) nirbheek: our meetings happen in brainwave levels :P +22:03 (@hwoarang) yngwin_: !! +22:03 (+wired) the leads are away +22:03 (@alexxy) Civil: ! +22:03 (@hwoarang) slacking leaders :D +22:03 (+wired) maybe they went out for beers +22:03 (+wired) :D +22:03 (@alexxy) mine beer is near me +22:03 (@alexxy) =) +22:04 (@hwoarang) +1 +22:04 (@scarabeus) mine too :] +22:04 (@scarabeus) ok +22:04 (+Civil) alexxy, ? +22:04 (@hwoarang) o_0 +22:04 (+wired) i see +22:04 (dagger) I've got tonic with me (no without gin) +22:04 (@yngwin_) present +22:04 (@hwoarang) !! YEY!! +22:04 (+wired) beer meeting this will be +22:04 -!- yngwin_ is now known as yngwin +22:04 (+wired) yngwin: :D +22:04 (spatz) for me? you shouldn't have :p +22:04 -> papillon81 is here +22:04 -> Civil is here +22:04 -!- hwoarang topic of #gentoo-kde ->> Gentoo KDE | meeting 21.5. 19:00 UTC | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU | Beer meeting in +22:04 (@hwoarang) stupid topic +22:04 -!- joost_op [n=joost@86.92.194.222] joins -> #gentoo-kde +22:04 (+wired) hwoarang: you fail it +22:05 -> nirbheek is here +22:05 (joost_op) evening +22:05 (@scarabeus) nirbheek: you want really to be listed on the roll-call? +22:05 -!- mode/#gentoo-kde [+v spatz] by yngwin +22:05 -> nirbheek does not know why he is here except maybe for espionage and sabotage +22:05 (@scarabeus) nirbheek: dont you fear other gnomies would burn you as witch +22:05 -> reavertm around +22:05 -!- mode/#gentoo-kde [+v Pesa] by yngwin +22:05 (nirbheek) scarabeus, they're too busy slacking :p +22:05 (@scarabeus) ok +22:05 (@scarabeus) i think better it wont get +22:05 (@scarabeus) most of us is here +22:05 (@hwoarang) :D +22:06 (+wired) yodabeus +22:06 (@scarabeus) :D +22:06 (@scarabeus) ok somebody must do the log +22:06 (+reavertm) nirbheek: we'll talk about some desktop file related stuff that touches gnome as well, so stay here :) +22:06 (@scarabeus) i still didnt find how todo it on quassel +22:06 (+wired) i'm logging +22:06 (@scarabeus) great +22:06 (@hwoarang) nice +22:06 (nirbheek) reavertm, kewl +22:06 (@scarabeus) so anyone has something to the topic list we have on the mail, or we should start right away with it? +22:07 (cvandonderen) scarabeus: you can just copy-paste it from the backlog +22:07 (@tampakrap) why not wait 10 minutes for others? +22:07 (@scarabeus) cvandonderen: not convinient +22:07 -> papillon81 has got no mail +22:07 (cvandonderen) scarabeus: we did it last time for a kde.org meeting ;-) +22:07 (@scarabeus) tampakrap: what others, only boss and cryos is missing +22:07 -!- Red_Devil [n=red@lounge.datux.nl] <- quit [Read error: 110 (Connection timed out)] +22:07 (@tampakrap) boss then +22:07 -> jokey enters spectator mode +22:08 (nirbheek) jokey, YESH +22:08 (nirbheek) I finally catch you +22:08 -!- _Phlogi [n=quassel@38-77.76-83.cust.bluewin.ch] <- quit [Read error: 110 (Connection timed out)] +22:08 (+reavertm) http://dpaste.com/46416/ - meeting agenda +22:08 (+papillon81) reavertm: thanks +22:08 (@scarabeus) http://archives.gentoo.org/gentoo-dev/msg_c5211b31c0fbff058bc767e3ac8ef077.xml +22:08 (@scarabeus) for those whom dont like pastebins +22:09 (@yngwin) scarabeus: carlo is missing too +22:09 -> lxnay sniffs packets from now +22:09 (@scarabeus) yngwin: he will be allways missing +22:09 (@yngwin) i know, but i consider this an offence +22:09 (@scarabeus) well he does not reply to mine mails either +22:10 (@scarabeus) ok i will write it to summary and let it to jorge to sort out :P +22:10 (@yngwin) yes please +22:10 (@hwoarang) no +22:10 (+reavertm) a'ka "removing dead members" ? +22:10 (@hwoarang) i ve talked to jorge before 2-3 days +22:10 (cvandonderen) I could do the kde4 guide.... +22:10 (@hwoarang) he said it is up to qt herd to deal with him +22:10 (@hwoarang) :) +22:10 (@yngwin) ok +22:10 (cvandonderen) I'm new to Gentoo, so I can do it based on experiences encontered +22:10 (@yngwin) i'll take care of it then +22:11 (@hwoarang) ok +22:11 -> cryos|work wife is having a baby in a few weeks - he may not be present for the next few meetings. Sorry! +22:11 -!- kdeR [n=wired@musici.static.otenet.gr] joins -> #gentoo-kde +22:11 (@hwoarang) o_0 +22:11 (@hwoarang) new developer :D +22:11 (@tampakrap) congratulations! +22:11 (@yngwin) good luck with that +22:11 (+krytzz) haha +22:11 (@scarabeus) cryos|work: wow, cool, enjoy the little slacker, be sure you wont be sleeping either :] +22:11 (@yngwin) :) +22:12 (+krytzz) yeah congratulations +22:12 (dagger) cryos|work: grats to you and your mrs dude :) +22:12 (@hwoarang) \o/ congrats cryos|work :) +22:12 (@cryos|work) Thanks - expecting lots of ups and downs over the next few months. Today has been hectic... +22:12 (@cryos|work) US time zone doesn't help me get here either... +22:12 (+wired) cryos|work: congrats =] +22:12 (@alexxy) he he =) congratulations cryos|work =) +22:13 (@jmbsvicetto) Hello +22:13 (jokey) new dev training++ +22:13 (dagger) yaay jmbsvicetto! +22:13 (+krytzz) yay chef +22:13 (+wired) jmbsvicetto: leader! +22:13 (@hwoarang) :) +22:13 (+wired) w00t +22:13 (@jmbsvicetto) Sorry guys, but I just sat down at work. I've been working up until now +22:13 (@hwoarang) no worries +22:13 (@hwoarang) i bet we are about to break a record today +22:13 (@scarabeus) jmbsvicetto: the network magic? :] +22:14 (lxnay) jmbsvicetto: helloes +22:14 (@scarabeus) ok i know we all can say hello for next 20 minutes, but lets get started :] +22:14 (@scarabeus) topic 1; doc handling +22:14 (@scarabeus) reavertm: anything changed on that subject? +22:14 (nirbheek) #gentoo-kde +22:15 (@scarabeus) and for specified packages with api-doc we will create new useflag +22:15 (nirbheek) mumble, mumble, what about packages that just rebuild the docs? +22:15 (nirbheek) And unconditionally install docs? +22:15 (@jmbsvicetto) cryos|work: congrats +22:15 (@scarabeus) nirbheek: we dont have such :] +22:16 (+reavertm) I support idea of leaving 'doc' for handbooks and introduce some other useflag when there's apidocs along with use documentation +22:16 (@cryos|work) Thanks jmbsvicetto :P +22:16 (@jmbsvicetto) scarabeus: getting ready for that +22:16 (@scarabeus) reavertm: so we agree on that :] +22:16 (nirbheek) scarabeus, but hypothetically, if you guys did, what would you do :p +22:16 (+krytzz) nirbheek slap upstream +22:16 (@jmbsvicetto) Hi everyone +22:16 (nirbheek) krytzz, difficult to slap entire gnome :p +22:16 (joost_op) right now compile kdelibs +doc results in a 268MB vs 48MB package +22:16 (nirbheek) jmbsvicetto, HELLO. +22:16 (@scarabeus) so what would be the apidoc useflag +22:17 (+reavertm) same for kdepimlibs +22:17 (@scarabeus) api-doc apidoc +22:17 (@scarabeus) anything else? +22:17 (@jmbsvicetto) reavertm: By default on Gentoo, user docs should be installed +22:17 (@scarabeus) suggestions ... +22:17 (cvandonderen) and will the apidoc useflag only be for kde, or Gentoo-wide? +22:17 (@scarabeus) jmbsvicetto: they are large +22:17 (@jmbsvicetto) reavertm: Only api / dev docs / examples should be conditional on use flags +22:17 (+reavertm) jmbsvicetto: hmm +22:17 (+wired) we could keep useflag for user docs but + it +22:17 (+reavertm) well, that's the way as well +22:18 (@scarabeus) sounds reasonable +22:18 (@scarabeus) +doc on kde-base +22:18 (@jmbsvicetto) scarabeus / reavertm: If they are large, they fit with the other docs - thus should depend on a use flag +22:18 (+reavertm) nirbheek: how do you have it on gnome? +22:18 (@jmbsvicetto) Gentoo does allow for exceptions ;) +22:18 (nirbheek) reavertm, we ignore the problem entirely =p +22:18 (+wired) lolz +22:18 (@scarabeus) jmbsvicetto: well then lets invent apidoc +22:18 (@jmbsvicetto) nirbheek: hehe +22:18 (@scarabeus) jmbsvicetto: docs are handled fine +22:18 (cvandonderen) and then make it kde-docs or something, because Java installs apidoc with doc too +22:18 (@scarabeus) but as joost said +22:18 (@scarabeus) 268 mb vs 48 mb +22:18 (@jmbsvicetto) scarabeus: what fills those 268MB ? +22:19 (nirbheek) docsdammitwhatelse +22:19 (@yngwin) maybe a discussion on dev ml is warranted, about global apidoc useflag +22:19 (@scarabeus) jmbsvicetto: api documentation +22:19 (@scarabeus) yngwin: i hate writing on -dev +22:19 (@scarabeus) yngwin: everything that is not anouncement turns to flame +22:19 (joost_op) for users having +doc in their make.conf, its not what they wanted +22:19 (lxnay) scarabeus: ;) true +22:19 (@yngwin) well, thats the official channel... +22:19 (+reavertm) if gentoo policy is to install docs by default, maybe we should drop 'doc' useflag for handbooks then +22:20 (+wired) scarabeus: it works if you just ignore flame[baits] +22:20 (nirbheek) scarabeus, ignore all replies is the solution +22:20 (@scarabeus) reavertm: now when it finaly works? ;] +22:20 -!- Devrethman [i=mpd@D-128-208-118-158.dhcp4.washington.edu] <- quit [Read error: 110 (Connection timed out)] +22:20 (@scarabeus) reavertm: i would go with +doc +22:20 (+wired) nah it should be optional, its gentoo +22:20 (+krytzz) me too scarabeus +22:20 (+spatz) if doc should be enabled by default then it should be done in the profile +22:20 (+wired) +doc sounds best +22:20 (@yngwin) no! +22:20 (+krytzz) why not +22:20 (@hwoarang) i dont like +doc +22:20 (+reavertm) not in profile +22:20 (@alexxy) heh ; to me seems better to use doc for user docs +22:20 (dagger) +doc sounds the best. If you want, you can disable it +22:20 (nirbheek) spatz, that results in too many circular deps +22:20 (@scarabeus) in kde-base packages +22:20 (@yngwin) not in profile +22:20 (+reavertm) better +doc per ebuild +22:20 (@scarabeus) yes per ebuild +22:21 (nirbheek) spatz, it's officially unsupported by Gentoo for global enabling +22:21 (@scarabeus) and the apidoc i will sum up some mail then +22:21 (@jmbsvicetto) scarabeus: But is it only api documentation or the handbook as well? +22:21 (+reavertm) jmbsvicetto: we need to distinguish them where they are both +22:21 (+reavertm) (like in kdelibs) +22:21 (@scarabeus) jmbsvicetto: +doc for documetnation only +22:21 (+reavertm) +doc whould be just for handbooks +22:21 (@scarabeus) jmbsvicetto: apidoc or sth for api doc +22:21 -> yngwin goes off to set -doc in make.conf +22:21 (@scarabeus) jmbsvicetto: where we ask on -dev for suggestions +22:22 (@scarabeus) yngwin: :D +22:22 (@yngwin) i can use internet thankyouverymuch +22:22 (dagger) yngwin: how about kde-base/* -doc :) +22:22 (@jmbsvicetto) ok, let me ask again. I'm not talking about use flags yet. I'm just trying to undestand what type of docs we have and an approximate size +22:22 -!- Enrico|ITA| [n=quassel@host86-47-dynamic.7-87-r.retail.telecomitalia.it] joins -> #gentoo-kde +22:22 (@yngwin) dagger: if only portage would support that +22:22 (@scarabeus) jmbsvicetto: the doc is 5-10megs +22:22 (@scarabeus) per package +22:22 (dagger) yngwin: ouch. I though it does +22:22 (@scarabeus) jmbsvicetto: apidoc is big crap +22:22 (@jmbsvicetto) yngwin: It does, if you change the order for inheritance ;) +22:23 (@yngwin) huh? +22:23 (joost_op) jmbsvicetto, it looks like right now on kdelibs with +doc it generates an insane size on the disc.. for no clear reason.. +22:23 (@jmbsvicetto) scarabeus: So 5-10MB for handbook and possible >100MB for the rest? +22:23 (@scarabeus) y +22:23 (@scarabeus) so growth in total about +500meg now +22:23 (@alexxy) ohh +22:23 (@alexxy) realy big +22:23 (dagger) that's quite extensive +22:23 -> scarabeus already has -doc in use +22:23 (@jmbsvicetto) yngwin: It's possible to affect the way portage treats the use flags - but I'll leave that for another time +22:24 (@yngwin) jmbsvicetto: we were talking about wildcard support +22:24 (@jmbsvicetto) Ah, sorry. I -meant you were talking about -* default use flags +22:24 (+reavertm) or rather per-category USE flags +22:24 (@jmbsvicetto) s/-meant/thought/ +22:25 (+reavertm) anyway, we're deviating a bit from the topic +22:25 (@scarabeus) bit +22:25 (@jmbsvicetto) scarabeus: In that case, let's talk about it in the dev ml +22:25 (@scarabeus) ok +22:25 (@scarabeus) i will sent that mail +22:25 (+reavertm) so we leave kdelibs alone for now or invent use flag for apidocs? +22:25 (@scarabeus) reavertm: first -dev +22:25 (@scarabeus) reavertm: then we will do whole thing +22:25 (@scarabeus) for now waiting on the mail +22:26 (+reavertm) it will take forever +22:26 (@jmbsvicetto) scarabeus: Personally I would suggest we install handbook by default (handbook use flag) and leave the doc use flag for the rest (disabled by default) +22:26 (@scarabeus) reavertm: i give them 7 days +22:26 (+reavertm) we can rename USE flag anytime +22:26 (+reavertm) (and play with it in overlay) +22:26 (@scarabeus) pple would tear us apart :D +22:26 (@scarabeus) if we move back to handbook D: +22:26 (+wired) lol +22:26 (+reavertm) pple can kill our asses - who does the work - decides +22:26 (@alexxy) he he =) +22:26 (@jmbsvicetto) scarabeus: +handbook for user docs ;) +22:26 (@alexxy) someone would forced to rebuild whole kde +22:26 (nirbheek) ouch +22:26 (joost_op) yeah it makes more sense.. +22:26 (+reavertm) jmbsvicetto: +handbook or +doc? +22:27 (joost_op) (o; +22:27 (@jmbsvicetto) My proposal would be +handbook for handbook and doc for the rest +22:27 (+wired) alexxy: doesn't portage profile/updates cover user flag changes? +22:27 (@scarabeus) --newuse +22:27 (+reavertm) (I'd like to rename +100 ebuilds and eclass) +22:27 (@jmbsvicetto) reavertm: meaning eapi docs +22:27 (@scarabeus) pple would hate us +22:27 (joost_op) since +doc right now generates the handbook +22:27 (+wired) use* +22:27 (@jmbsvicetto) s/eapi/api/ +22:27 (joost_op) keeping kdelibs out of it +22:27 (@alexxy) wired: no =) +22:27 (+reavertm) (i mena I woundn't lke to rename so many use flags...) +22:28 (@jmbsvicetto) We can do any changes in the use flags for 4.3 +22:28 (Kuja^) wired: it only handles package renames afaik +22:28 (+wired) meh +22:28 -!- BarbieGentoo-er is now known as Tina- +22:28 (@scarabeus) i agree with reaver, we need some test suicider who will do it, with apidoc we have 2 packages to change +22:28 -!- jmbsvicetto topic of #gentoo-kde ->> Gentoo KDE | meeting: Now | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU +22:29 (@scarabeus) with handbook we have to touch all +22:29 (@jmbsvicetto) scarabeus: The handbook should be dealt with in the eclasses, imo +22:29 (@scarabeus) jmbsvicetto: ok but it will be todo for 4.3 +22:29 (+reavertm) it's already dealt there, but ebuilds need to fixed as well +22:29 (@jmbsvicetto) scarabeus: that's my opinion +22:29 (@scarabeus) or 4.4 +22:29 (@scarabeus) :D +22:30 (@jmbsvicetto) scarabeus: But you don't have to agree with me ;) +22:30 (joost_op) i'd address it to 4.4 +22:30 (joost_op) but thats just my ho +22:30 (@scarabeus) well i am just lazy, cause it is annoying work +22:30 -!- ehustad [n=espen@ti511220a080-1003.bb.online.no] joins -> #gentoo-kde +22:30 (@scarabeus) go throught all ebuilds and manualy check them +22:30 (@scarabeus) there is 250 of them +22:30 (@scarabeus) and pple still commit to them +22:30 (@scarabeus) so merge failitures +22:30 (@scarabeus) AAGHR +22:30 (dagger) scarabeus: make it 40 each :) +22:31 -!- UT2K3 [n=UT2K3@one.lanrena.ilk.de] joins -> #gentoo-kde +22:31 -> lxnay can do annoying work +22:31 (@scarabeus) lxnay: you are realy willing to do it? +22:32 -> lxnay hides +22:32 (lxnay) ;) +22:32 (lxnay) well we can talk about it +22:32 (@scarabeus) as you wish +22:32 (joost_op) lxnay, hahaha leave it to scarabeus +22:32 (lxnay) but sure +22:32 (joost_op) we have enough todo +22:32 (lxnay) i can help out +22:32 -> joost_op grins +22:32 (@scarabeus) :] +22:32 (@scarabeus) :D +22:32 (+reavertm) I'd like to see how it's handled elsewhere 1st +22:32 (@scarabeus) reavertm: by elsewhere you mean? +22:33 (UT2K3) hi guys i upgraded to kde-4.3 and now the most icons are missing +22:33 (@jmbsvicetto) ok, so we'll use the dev ml to discuss the split between the documentation and the use flags for it. Anyone objects? +22:33 (@jmbsvicetto) UT2K3: We're in the middle of a meeting, please leave it for after the meeting +22:33 (UT2K3) ok +22:33 (lxnay) anything that falls into split attracts me, split and reign +22:34 (+reavertm) elsewhere, gnome (nirbheek by ignoring problem you mean installing everything provided by autoconf not caring whether docs are there or not?), openoffice, whatever +22:34 (nirbheek) reavertm, yeah, pretty much +22:34 (@scarabeus) reavertm: mostly they dont care +22:34 (nirbheek) the doc use-flag on gnome packages rebuilds the docs +22:34 (nirbheek) But even that's inconsistent for a few packages +22:35 (nirbheek) (some packages don't use gtk-doc) +22:35 (nirbheek) Oh, and these are api docs :p +22:35 (nirbheek) ls /usr/share/gtk-doc/html +22:35 (@jmbsvicetto) hmm, so do we want to move that discussion to the dev ml? +22:36 -> jmbsvicetto looks at the clock +22:36 (@scarabeus) jmbsvicetto: jup +22:36 (+reavertm) anyway if 'doc' is for developer documentation, we need new USE flag for handbooks +22:36 (@scarabeus) end of this topic :] +22:36 (@jmbsvicetto) ;) +22:36 (@jmbsvicetto) KDE3? +22:36 (@scarabeus) that was FUBAR +22:36 (@scarabeus) total one +22:36 (@scarabeus) when we moved it to the tree +22:36 (@scarabeus) many things broke +22:36 -!- jmbsvicetto topic of #gentoo-kde ->> Gentoo KDE | meeting: Now - KDE3 | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU +22:37 (@scarabeus) even now it is not finished +22:37 (@tampakrap) not exactly +22:37 (+Pesa) please try to avoid the gtk-doc mess ;) +22:37 (@tampakrap) we knew from the beginning that were was going to be a mess with kde3 misc apps +22:37 (@jmbsvicetto) Well, we also have gcc-4.4 and glibc-2.10 joining the *fun* +22:37 (Mirrakor) :) +22:37 (+reavertm) kde3, well, the state is kdelibs is hacked to replace some entries of .desktop files on the fly to make kde4 apps (even those from kdeprefix) distinguished (and runnable) +22:37 (+wired) btw kdelibs3 -r6 just failed on me +22:37 (+reavertm) but... +22:38 (+wired) probably due to glibc or gcc =] +22:38 -!- cvandonderen [n=casper@212-182-159-91.ip.telfort.nl] <- quit ["leaving"] +22:38 (+wired) kde3 session lists all -kdeprefix kde4 apps in menu now properly +22:38 (@jmbsvicetto) Just a quick point, I think we should open a tracker bug about gcc-4.4 and another about glibc-2.10 breakages with KDE apps +22:38 (@alexxy) yep =) i use gcc 4.4 and new glibc +22:38 (+reavertm) the problem is - not all kde4 executables want to work within kde3 (or any non kde4) session +22:39 (@scarabeus) reavertm: i think that pple will have to live with it +22:39 (+wired) reavertm: actually all kde4 apps i tested worked in kde3 session +22:39 (+wired) reavertm: always -kdeprefix +22:39 (@scarabeus) with +kdeprefix i know it is evil +22:39 (+reavertm) wired: install 4.2 in kdeprefix and live in kdeprefix as well (so you have two kde4 releases in kdepredfx) and install kde3 +22:39 (@scarabeus) but it wont work correctly so i think kde3 should not see it at all +22:39 (+wired) kdeprefix isn't supported atm +22:39 (+reavertm) troubles start there +22:40 (+wired) the patch doesn't even care +22:40 (@scarabeus) and we should focus on making the kde3 misc apps revbumped and stabled +22:40 (+reavertm) wired: looked at my patch? +22:40 (+reavertm) my patch does care :) +22:40 (@scarabeus) reavertm: i know you patched it, simple, just revert it +22:40 (+wired) haven't seen your patch +22:40 (+krytzz) i think who uses kde3 and kdeprefix doesnt deserve better :p +22:40 (+reavertm) well, it works with -kdeprefix as well +22:40 (@scarabeus) one +kdeprefix version never saw other +kdeprefix one +22:40 (@scarabeus) so... +22:40 -!- UT2K3 [n=UT2K3@one.lanrena.ilk.de] <- quit ["Bambus> frei nach dem motto: was ist besser als 14? 2 x 7 :o"] +22:40 (+wired) reavertm: does it work or not then? +22:40 (+reavertm) the point is - there's other approach +22:41 -!- ehustad_ [n=espen@ti511220a080-1003.bb.online.no] <- quit [Read error: 110 (Connection timed out)] +22:41 (+reavertm) wired: patch works, but just replacing those is not sufficient to run kde4 apps (kde 4.2 apps) within kde3 +22:41 (+wired) well no +22:41 (+reavertm) they try to load oxygen theme from live kde +22:41 (+wired) kde4 kdeprefix apps will need a wrapper script +22:41 (+reavertm) that's issue that needs to be resolved +22:41 (+wired) just as kde3 apps need kde3 wrapper script in kde4 +22:41 (+reavertm) that's stupid anyway +22:42 (+reavertm) let me check wrapper +22:42 (+papillon81) what is the main issue behind the kde3 topic that needs to be discussed here? +22:43 (+wired) having all stuff available in all menus +22:43 (+papillon81) k +22:43 (@tampakrap) ok apart from that +22:43 (+reavertm) wrapper doesn't fix this +22:43 (+reavertm) so anyway +22:43 (+reavertm) new idea is to modify .desktop files directly +22:43 (@tampakrap) i started opening stabilization bugs for various kde3 apps +22:44 (+reavertm) substitute paths with absolute ones, add suffixes to names to make it distinguished etc +22:44 (@tampakrap) i think monolithics can be masked and 3.5.10 can go to stabilization since 3.5.9 is dead +22:44 (@yngwin) ah that reminds me, are we deprecating arts as per bug 270575 ? +22:44 (Willikins) yngwin: https://bugs.gentoo.org/270575 "Dropping USE="arts" and USE="esd""; Gentoo Linux, Applications; NEW; ssuominen@g.o:qa@g.o +22:44 (+reavertm) i alrady started working on desktop-file-edit util (in desktop-file-utils, maybe it will be added there sometime) +22:44 (@scarabeus) we should +22:45 (@hwoarang) at last :) +22:45 (@yngwin) i think we can just remove arts support in 3.5.10 +22:45 (@scarabeus) yup that would be smart +22:45 (@tampakrap) can arts be safely disabled? it needs testing +22:45 (@scarabeus) remove arts support in 3.5.10 +22:45 (@yngwin) but we should check stable tree for packages requiring arts, if any +22:45 (@scarabeus) tampakrap: actualy more breakages is arts enabled +22:45 (+reavertm) nirbheek: you're not going to hack .desktop files loader in gnome to make kde4 apps (from multiple prefixes) not seen as duplicates? +22:45 (@scarabeus) tampakrap: it is more question, can we affort supporting arts +22:45 (+papillon81) lol +22:46 (@bonsaikitten) kill it with fire +22:46 (@bonsaikitten) then kill it again until it is dead +22:46 -!- gengor|lunch is now known as gengor +22:46 (+wired) lol +22:46 -> papillon81 has arts disabled since ages +22:46 (nirbheek) reavertm, why should they not be shown as duplicates? +22:47 (nirbheek) (I'm unfamliar with exactly how kde4 prefixes work) +22:47 (+reavertm) if you have kde4.2 in /usr/kde/4.2 and /usr/kde/live - you'll get two identical "Text editor" icons lanching same app +22:47 (+reavertm) (the one that is 1rst in PATH +22:48 (@yngwin) kde4 installs vim? +22:48 (@hwoarang) lol :P +22:48 (@yngwin) "text editor" ... +22:48 (+reavertm) kwrite +22:48 (nirbheek) reavertm, I'm confused, how can two paths in PATH cause duplicate .desktops? +22:48 (Enrico|ITA|) yngwin: kde4 rocks, vim rocks so they pull in each other :D +22:48 -!- jkt| [n=jkt@gentoo/developer/jkt] <- quit [Read error: 60 (Operation timed out)] +22:49 (@scarabeus) reavertm: i still think it is just wasting time +22:49 (@scarabeus) reavertm: just forget about some +kdeprefix +22:49 (@scarabeus) and problem is solved +22:49 (@scarabeus) really +22:49 (@scarabeus) we need it stable +22:49 (@scarabeus) for stabling kde4 +22:49 (@yngwin) yeah, dont make it more complicated than necessary +22:49 (@scarabeus) then it will be done in 7 months +22:49 (@scarabeus) s/done/gone +22:49 (+reavertm) then there's no point in exporting XDG_DATA_DIRS for kdeprefixed installs +22:49 (nirbheek) Oh, I see +22:49 (nirbheek) _that_ way +22:49 (@alexxy) scarabeus: thats why i suggest to mask kdeprefix from regular users +22:50 (@yngwin) i think once kde4 is in stable, there will be few kde3 users +22:50 (nirbheek) reavertm, yes, plz2don't export prefixed installs (except for default prefix?) +22:50 (+papillon81) also think about the issue with networkmanager-applet concerning different paths +22:50 (@scarabeus) papillon81: later later +22:50 (@scarabeus) now we are on kde3 +22:50 (@scarabeus) :] +22:50 (+reavertm) but it can be done :P +22:50 (@scarabeus) reavertm: can and must are 2 things +22:50 (@scarabeus) reavertm: and we have other things we need to have done +22:50 (@scarabeus) which are actualy more important than this +22:51 (+wired) if user has kdeprefix +22:51 (nirbheek) You guys have too much time and manpower :p +22:51 (+wired) we should just export +22:51 (@scarabeus) if user has kdeprefix, we dont bother with kde3 +22:51 (+wired) the ... higehr version one maybe? +22:51 -!- Sho_ [n=EHS1@kde/hein] <- quit [Read error: 104 (Connection reset by peer)] +22:51 (+wired) in XDG_DATA_DIRS +22:51 (+reavertm) there is a bug already - "kde4 apps not shown in gnome" or whatever +22:51 -!- Sho_ [n=EHS1@kde/hein] joins -> #gentoo-kde +22:51 (@scarabeus) reavertm: yep that is other thing, and that can be handled by, newest ap win +22:51 (+reavertm) (or the other way around?) +22:52 (@scarabeus) kde4 apps in gnome +22:52 (+wired) if user has -kdeprefix installed, only that one shows in other DEs, if he has only +kdeprefix then grab newer version (or stabler, whatever) +22:52 (@scarabeus) yep +22:52 (@scarabeus) but dont bother with it on kde3 +22:52 (@jmbsvicetto) tampakrap: we can't mask 3.5.9 monos until we get 3.5.10 marked stable +22:52 (@hwoarang) afaik there was another situation that kde3 apps didnt show on kde4 session +22:52 (+reavertm) what you have just written - how exactly are you going to implement? +22:53 (+reavertm) espeically "if he has only +kdeprefix then grab newer version (or stabler, whatever)" part +22:53 (@jmbsvicetto) tampakrap: That would cause issues for stable users +22:54 (+wired) reavertm: check in /etc/env.d/... ? +22:55 (@scarabeus) ok for kde3 i have two things +22:55 (@scarabeus) - kill arts, all misc apps needs it removed and be stabled before 3.5.10 stabling +22:55 (@scarabeus) - stable 3.5.10, all kde related misc apps needs to be revbumped/verbumped and stabled before it +22:55 (@scarabeus) anything to this +22:55 (@alexxy) jmbsvicetto: thats why i think its better to mask kdeprefix use flag to not confuse stable users at all +22:55 -!- jkt| [n=jkt@basa.flaska.net] joins -> #gentoo-kde +22:55 (@tampakrap) kde3 misc apps is up to me +22:55 (+reavertm) making kdeprefix is differnt topic :) +22:55 (@yngwin) i'd agree with masking kdeprefix useflag +22:55 (+wired) actually i agree with alexxy it should be masked +22:56 (+krytzz) me too ^^ +22:56 (@jmbsvicetto) alexxy: Unmasking a use flag is not something we should ask our users to do +22:56 (@scarabeus) reavertm: i think we will talk about it on the bug +22:56 (@tampakrap) i want someone to stable 3.5.10, i don't know the procedure for a list of packages +22:56 (@jmbsvicetto) alexxy: We already have it disabled by default +22:56 (+wired) too many users use +kdeprefix without knowing wth it is +22:56 (+wired) ohhh look shiny use flag +22:56 (@alexxy) jmbsvicetto: kdeprefix is topper to make kde 4.2 stabel +22:56 (@hwoarang) wired is right actually :) +22:56 (@scarabeus) jmbsvicetto: i dont mind having unmasked kdeprefix, when the kdeprefix issues are fixed +22:56 (@alexxy) jmbsvicetto: users can think that they want to have kde in /usr/kde/ and use kdeprefix +22:56 (@scarabeus) and users install it "by accident" +22:57 (@jmbsvicetto) wired: Gentoo is not a distro for "not smart" users +22:57 (+wired) jmbsvicetto: im with you 100% +22:57 (+wired) the users aint +22:57 (@jmbsvicetto) wired: We don't want to become Ubuntu ;) +22:57 (@alexxy) but it will cause troubles if they hav kde3 for example +22:57 (nirbheek) jmbsvicetto, Hey, you just Godwinned the conversation :p +22:57 (@yngwin) ok, maybe add an ewarn then +22:57 (+wired) there seems to be some general confusion regarding it +22:57 (+wired) maybe it needs to be documented better +22:57 -!- _Phlogi [n=quassel@168-18.77-83.cust.bluewin.ch] joins -> #gentoo-kde +22:57 (+reavertm) great, then I need volunteer to fix one bug - the one with picking live oxygen by kde 4.2 apps (both installed in kdeprefix) +22:58 (+reavertm) after that - I can call kdeprefix supported +22:58 (+reavertm) volunteers? +22:58 (+reavertm) if no - mask kdeprefix :P +22:58 (joost_op) we will have -kdeprefix in our next branch for sure +22:58 -!- bschindler [n=quassel@77-56-156-71.dclient.hispeed.ch] joins -> #gentoo-kde +22:58 (@jmbsvicetto) Let's improve our docs and make it *very* clear that users shouldn't enable kdeprefix unless they're ready to assume the support for their install +22:58 (joost_op) if it helps +22:58 (@scarabeus) jmbsvicetto: also evarn is not bad idea +22:58 (@scarabeus) ewarn +22:58 (@jmbsvicetto) No problem with that +22:58 (+wired) jmbsvicetto++ +22:58 (@scarabeus) something like I_KNOW_WHAT_I_AM_DOING variable +22:59 (+wired) and ewarn should be there as well +22:59 -!- Eythan [n=Eythan@AMontpellier-552-1-118-57.w86-197.abo.wanadoo.fr] <- quit ["Leaving"] +22:59 (+krytzz) yeah this one is great +22:59 (nirbheek) Why not just globally use.mask it? +22:59 (@jmbsvicetto) Although you all know just how much ewarns users tend to pay attention to +22:59 (nirbheek) People who want to use it can enable it +22:59 (@jmbsvicetto) scarabeus: no +22:59 (@yngwin) not another variable, then it'd be better just to mask the useflag +22:59 (+wired) also many users think kdeprefix is needed for kde3/kde4, we need to tell them thats no longer the case +22:59 (+reavertm) what's wrong with masking it until kdeprefix issues are fixed? +22:59 (dagger) nirbheek: global use.mask should be for stuff which is know to be broken. +23:00 (+reavertm) actually kdeprefix IS KNOWN to be broken :P +23:00 (@scarabeus) jmbsvicetto: i mean like live warning is handled +23:00 (@yngwin) well, it *is* known to break things +23:00 (nirbheek) dagger, isn't this known to be broken? :p +23:00 (@jmbsvicetto) reavertm: I use it here :P +23:00 (@scarabeus) jmbsvicetto: i just expresed myself poorly +23:00 (@scarabeus) jmbsvicetto: broken ktorrent.. +23:00 (+reavertm) it is broken when used with non-kde4 sessions . period +23:00 (dagger) is it broken for all installs? If you just use one kde (4.2) and no other version? +23:00 (@jmbsvicetto) scarabeus: I don't think we should require users to set a new use flag or to have to digg how to unmask use flags +23:00 (@scarabeus) jmbsvicetto: broken misc plasmoids... +23:00 (@scarabeus) jmbsvicetto: no useflag +23:00 (@alexxy) reavertm: if its known to be broken then it should be masked by default +23:00 (@alexxy) from regular users +23:01 (@scarabeus) jmbsvicetto: like the warning it is doing in live +23:01 (@jmbsvicetto) reavertm: You're talking about mixing kde versions or using other DEs +23:01 (nirbheek) dagger, then it's of no use, right? (if you only have one) +23:01 (@alexxy) people who want to play with it smart enough to unmask it +23:01 (+reavertm) both +23:01 (+reavertm) using other DEs with multiple KDE4's installed +23:01 (dagger) nirbheek: but I might like to have it in /usr/kde/4.2 location +23:02 (+reavertm) jmbsvicetto: ^ +23:02 -!- mode/#gentoo-kde [+v Kuja^] by scarabeus +23:02 (nirbheek) dagger, then why not make it default? :p +23:02 (dagger) use.mask unmasking is not documented and should not be used really +23:02 (nirbheek) kdeprefix is not documented, and should noe be used really (unless you know what you're doing) +23:02 (@tampakrap) kdeprefix is documented +23:02 (+reavertm) what else. use.force? +23:03 (+reavertm) (and it be overriden in /etc somewhere?) +23:03 -!- ELITE_x [n=quassel@quassel/user/elite] <- quit [Remote closed the connection] +23:03 (nirbheek) tampakrap, yeah, and my code is documented ;p +23:03 (@scarabeus) ok you guys are way of topic :} +23:03 (@scarabeus) we are suposed to talk about kde3 +23:04 (@scarabeus) so for now we have revbumping all misc packages and removing arts +23:04 (@jmbsvicetto) So let's focus again on KDE3 +23:04 (@scarabeus) anything else onto that topic? +23:04 (@tampakrap) yes +23:04 (@tampakrap) let me talk for a minute +23:04 (@yngwin) well, this kdeprefix mess should be decided before stabling 3.5.10 +23:04 (@jmbsvicetto) scarabeus: I don't think it's worthy to worry about arts, but if those working on KDE3 want to drop it now, I don't have a problem with it +23:04 (@scarabeus) jmbsvicetto: it is not working, again ton of bugs open +23:04 (@tampakrap) the original idea behind hacking kde3 eclasses was to have mostly a kde4 session with kde3 apps working +23:04 (@scarabeus) jmbsvicetto: so if we kill it we smash bugs +23:05 (@jmbsvicetto) scarabeus: well, it isn't a regression ;) +23:05 (@tampakrap) especially those that aren't still ready for kde4 +23:05 (@alexxy) kde3 works perfectly without arts +23:05 (@alexxy) =) +23:05 (@tampakrap) this issue is fixed, if wired and reavertm want to play more it is their issue, the stabilizattion can be proceeded normally +23:05 (@tampakrap) and i'm going to document it +23:05 (@tampakrap) objections? +23:05 (+reavertm) nope +23:06 (+reavertm) we can add some blocker anytime +23:06 (+reavertm) (if needed) +23:06 (@tampakrap) also +23:06 (@jmbsvicetto) tampakrap: I agree with that +23:06 (@yngwin) as long as kdeprefix is properly documented +23:06 (@tampakrap) the mess created in kde misc apps was expected, so nothing is fucked +23:06 (wilder_) hiall, qt-4.5.1 in portage does not contain http://websvn.kde.org/trunk/qt-copy/patches/0279-svg-rendering-regression.diff +23:06 (@tampakrap) we new from the beginning that most of them should be rebuilt to work and i am trying to revbump and stabilize the most popular ones +23:07 (@tampakrap) and close random bugs +23:07 (wilder_) ? +23:07 (@jmbsvicetto) tampakrap: At this point, I think we should have 2 goals with KDE3: working environment to those still resisting KDE4 and working KDE3 apps inside a KDE4 session +23:07 (@hwoarang) wilder_: it does. but we have a meeting now +23:07 (+krytzz) wilder_ please later, we are in a meeting currently +23:07 (@tampakrap) jmbsvicetto: both those work +23:07 (@scarabeus) so we can stable +23:07 (@scarabeus) goodie +23:07 (wilder_) sry +23:07 (+krytzz) np +23:07 (@jmbsvicetto) tampakrap: right, but we should be explicit that is what we'll support for KDE3 +23:08 (@jmbsvicetto) tampakrap: So people know what we're doing and what we're willing to support +23:08 (@tampakrap) i can document that +23:08 (+reavertm) if we disable XDG_DATA_DIRS for kdeprefixed kde4's - current kdelibs patch is sufficient +23:08 (+reavertm) (for kde3) +23:08 (@tampakrap) and also propose things to users so as to have a fully working kde4 env +23:09 (+reavertm) so only remaining issue is to fix kde4 session (kdelibs .desktop files loader) the same way as kdelibs3 one +23:09 (+reavertm) (I can do it) +23:09 (@tampakrap) not a major one but feel free +23:09 (@jmbsvicetto) I also propose we make it clear that upstream stopped working on KDE almost 1 year ago and doesn't show much concern about it anymore +23:09 (+reavertm) (a'ka fixing kde3 apps in kde4) +23:09 (@tampakrap) the major issue is to have them working, i don't care much if they aren't listed in kmenu :) +23:09 (@jmbsvicetto) So people worried about security should start thinking about upgrading +23:10 (+wired) actually them showing up is important +23:10 (@tampakrap) ok i'll prepare a new document about kde3 and kde3/4 +23:10 (@jmbsvicetto) That's another reason we need to press for KDE4 going stable +23:10 (+wired) so that patch reavertm is talking about is needed +23:10 (+reavertm) tampakrap: it will make them work - they need no special care apart from appending fullpath to executable +23:10 -!- pgega [n=pgega@tonbridgesecpay.force9.co.uk] <- quit [Remote closed the connection] +23:10 -!- Phlogi [n=quassel@24-167.77-83.cust.bluewin.ch] <- quit [Read error: 110 (Connection timed out)] +23:10 (@tampakrap) reavertm: feel free to do it no problem by me +23:11 (@scarabeus) ok i would say important things about kde3 are done +23:11 (@scarabeus) what is next... +23:11 (@scarabeus) KDE 4.3 +23:11 (@jmbsvicetto) tampakrap: So, should we try to define a timeline for 3.5.10? +23:11 (@scarabeus) oh +23:11 (@jmbsvicetto) scarabeus: just one sec +23:11 (@scarabeus) deadline? +23:11 (@tampakrap) what deadline? i can open the bug even now, the things i wanted to work are ready +23:12 (@tampakrap) i don't know from the open bugs view if this is possible +23:12 (@jmbsvicetto) ok +23:12 (@scarabeus) ok so lets say 15.6 is last day when we cc archies? +23:12 (@tampakrap) ok we have the kde3 thing settled +23:12 (@jmbsvicetto) So we'll open a stabilization bug for 3.5.10 asap? +23:13 (@tampakrap) yes ok +23:13 (@jmbsvicetto) Good :) +23:13 (@tampakrap) scarabeus: paste the summary so everyone can see it +23:13 -!- jmbsvicetto topic of #gentoo-kde ->> Gentoo KDE | meeting: Now - KDE4.3 | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU +23:13 (@hwoarang) http://archives.gentoo.org/gentoo-dev/msg_c5211b31c0fbff058bc767e3ac8ef077.xml +23:13 (@scarabeus) tampakrap: it is mess +23:13 (@scarabeus) tampakrap: i need to polish it later +23:13 (@scarabeus) dont worry summary will be +23:13 (@tampakrap) ok +23:13 (@tampakrap) next topic +23:13 (@scarabeus) libknotification is done +23:13 (+krytzz) ok for 4.3, i dont know for sure but i think the libnotification stuff is being merged into kdelibs later +23:13 (@scarabeus) it is pdepend in kdelibs +23:14 (@scarabeus) it will be merged in 4.4 +23:14 (+krytzz) ah ok +23:14 (@scarabeus) so for now it is best solution +23:14 (@scarabeus) also i dont get upstream +23:14 (@scarabeus) seriously +23:14 (@scarabeus) the lib is needed in half core packages +23:14 (@scarabeus) and they didnt add it +23:14 (@scarabeus) insane +23:14 (+wired) yes well +23:14 (@alexxy) yep +23:14 -> jmbsvicetto whistles +23:14 (+wired) at first they had it in extra gear +23:14 (+reavertm) abi/api changes probably +23:14 (+wired) LOLZ +23:14 (+wired) :p +23:14 (+reavertm) they wanted to workaround feature freeze :P +23:14 (+reavertm) simly +23:15 (+reavertm) so they invented "experimental" thing +23:15 (@alexxy) ohh +23:15 (@scarabeus) ok +23:15 (@scarabeus) what else we have for kde4.3 +23:15 (@alexxy) some additional deps +23:15 (@alexxy) like wicd +23:15 (@tampakrap) kopete will have facebook support :) +23:15 (+reavertm) and phonon +23:15 (@hwoarang) LOOOOLZ +23:15 (@alexxy) yep +23:16 (@alexxy) also non released phonon as dep +23:16 (+krytzz) well virtuoso isnt stable as trueg wrote +23:16 (@scarabeus) krytzz: it is not mandatory for 4.3 +23:16 (@scarabeus) :} +23:16 (+reavertm) or maybe we pull mplayer with mplayerthumbs? +23:16 (+reavertm) (it's pretty heavy dep) +23:16 (dagger) what's the status of policykit with 4.3? Do we need some extra docs? +23:16 (+krytzz) yes +23:16 (@scarabeus) ah +23:16 (@scarabeus) docs +23:16 (+krytzz) reavertm how do other package handle such deps? +23:16 (@scarabeus) definetly +23:16 (@alexxy) well +23:16 (+reavertm) (that's why I opted for making phonon snapshot evem if I use mplayer myself) +23:17 (@alexxy) policy kit used to control some privilegies like suspend/resume +23:17 (+reavertm) krytzz: you mean other distros? +23:17 (@yngwin) when is kde going to use qt's phonon? +23:17 (+reavertm) or whether it's compatible? +23:17 (+krytzz) reavertm no, i mean other packages who just call another binary +23:17 (@scarabeus) yngwin: hopefully with 4.6 +23:17 (+reavertm) yngwin: for us? never +23:17 (@scarabeus) yngwin: but we can just hope +23:17 (@yngwin) ok +23:17 (+reavertm) unless we package xine backend separately +23:18 -!- Pesa [n=Pesa@bluemchen.kde.org] <- leaves #gentoo-kde [] +23:18 (+reavertm) (btw, policykit panel crashes in kde trunk, anyone can confirm?) +23:18 (@scarabeus) reavertm: ok we will ship phonon snapshot +23:18 (@hwoarang) is this possible? does it worth the pain? +23:19 (@scarabeus) hwoarang: worth it is +23:19 (@scarabeus) because we wont have the blocker bugs +23:19 (+reavertm) pain it is not +23:19 (@hwoarang) ok then this sounds great ! +23:19 -!- Pesa [n=Pesa@bluemchen.kde.org] joins -> #gentoo-kde +23:19 (@alexxy) reavertm: in 4.2.87 it works +23:19 (@scarabeus) ok what state is the policykit anyway +23:19 (@scarabeus) is it usable +23:19 (@scarabeus) does it work? +23:19 (@scarabeus) is there something neede +23:19 (@scarabeus) d +23:19 (@scarabeus) (i am quite scared about it) +23:20 (@alexxy) scarabeus: polkit works +23:20 (+reavertm) krytzz: I haven't understood, sorry +23:20 (@alexxy) and its needed for some actions like suspend resume +23:20 (dagger) alexxy: isn't it controled by hal's policykit settings? +23:20 (@scarabeus) if it works then ok +23:20 (@alexxy) dagger: not sure +23:20 (+krytzz) reavertm hm forget it :p i think i missed something +23:21 (+reavertm) (in kubuntu thet did it well btw) +23:21 (@jmbsvicetto) scarabeus: about the blocks, I think we should add a kde use flag for qtscriptgenerator/qt-qt3support so that we can solve the phonon blocks. I talked about that in the bug +23:21 (@tampakrap) kde4 use flag +23:21 (@yngwin) we'll come to that +23:21 (dagger) jmbsvicetto: good point +23:21 (+reavertm) what about adding virtual for phonon? +23:21 (@scarabeus) ok so we will ship phonon snapshot in main tree +23:21 (@alexxy) ahh yes use flags +23:21 (@scarabeus) any objections +23:21 (@alexxy) =) +23:22 (@scarabeus) and i think virtual is better than useflag +23:22 (@hwoarang) +1 ^^ +23:22 (@yngwin) why? +23:22 (@scarabeus) it should work +23:22 (+reavertm) phonon in qt 4.5.1 is the same version as media-sound/phonon in tree +23:22 (@scarabeus) and we dont have to polute the qt ebuilds +23:22 (@jmbsvicetto) bug 270188 +23:22 (+reavertm) (just with no-go backend - gstreamer) +23:22 (Willikins) jmbsvicetto: https://bugs.gentoo.org/270188 "qt-phonon / phonon + phonon-kde block"; Gentoo Linux, Applications; REOP; jannisf@gmail.com:kde@g.o +23:23 (+reavertm) those blocks are mostly portage bugs btw +23:23 (@yngwin) yes +23:23 (@yngwin) well, if kde wants a virtual, i suppose that would work +23:23 (@scarabeus) yngwin: well i thinked about you +23:23 (@jmbsvicetto) hmm, how will the virtual solve the isue? +23:23 (@scarabeus) i dont mind poluting qt ebuilds +23:23 (@jmbsvicetto) issue* +23:23 (@scarabeus) but isnt virtual better for maintaining? +23:24 (+reavertm) || deps will be removed from ebuilds +23:24 (@jmbsvicetto) The virtual will have to prefer one implementation over the other - which one will we prefer? +23:24 -!- marco_ [n=marco@95.222.93.133] <- quit [Remote closed the connection] +23:24 (@scarabeus) media one +23:24 (+reavertm) || ( qt-phonon phonon ) deps +23:24 (@scarabeus) cause it is phonon + xine +23:24 (@jmbsvicetto) scarabeus: I don't think qt will want that +23:24 (+wired) i agree with jmbsvicetto, kde use sounds better +23:24 (@scarabeus) ok then we have to separate the xine +23:24 (@scarabeus) srsly i dont mind +23:24 (@scarabeus) so make it work :] +23:24 (@yngwin) we wont use the virtual if qt-phonon is 2nd choice +23:24 (@jmbsvicetto) scarabeus: Otherwise, we could just revert the deps on the qt ebuilds +23:25 -> hwoarang lost contact +23:25 (+reavertm) separating xine needs to be done anyway iho +23:25 (@hwoarang) qt-phonon+xine sounds better +23:25 (@hwoarang) n? +23:25 (@hwoarang) *no? +23:25 (@yngwin) that sounds like a better solution +23:25 (+reavertm) make it possible +23:25 (@jmbsvicetto) reavertm: What we really need to do is to force xine to qt upstream ;) +23:25 (@hwoarang) you cant +23:25 (+reavertm) xine is evil GPL +23:25 (+reavertm) no can do +23:26 (@jmbsvicetto) right, *evil* +23:26 (@yngwin) lol +23:26 (@scarabeus) ok so snapshot and spliting +23:26 (@hwoarang) the thing is, is it possible to ship xine separately? +23:26 (@scarabeus) the useflag i guess is ok +23:26 (@hwoarang) good +23:26 (+reavertm) hwoarang: shoud be possible +23:26 (@scarabeus) so lets use it for now +23:26 (@scarabeus) and later we just drop media-sound/phonon +23:26 (@scarabeus) problem solved +23:27 (@yngwin) hwoarang: you ok with USE=kde in qt ebuilds to prefer media-sound/phonon over qt-phonon? +23:27 (+reavertm) (what about -9999? live phonon frm qt is not really live phonon - media-sound/phonon-9999 will need to stay - virtual can come into play) +23:27 (@hwoarang) i dont mind +23:28 (+reavertm) hwoarang: and you need to strip gstreamer from qt-phonon as well +23:28 (@yngwin) ok +23:28 (@hwoarang) in case we have kde? +23:28 -!- d00p [n=d00p@srv3.nutime.de] joins -> #gentoo-kde +23:28 (@hwoarang) kde? -> media-sound/phonon and strip gstreamer? +23:28 -> hwoarang lost contact again :S +23:28 (+reavertm) xine and gstreamer backends could be split from media-sound/phonon +23:28 (@hwoarang) ok +23:29 (@jmbsvicetto) yngwin: can we have "kde? ( || ( media-sound/phonon x11-libs/qt-phonon )) !kde? ( || ( x11-libs/qt-phono media-sound/phonon ))" ? +23:29 (@yngwin) we can work out the details later +23:29 (@hwoarang) reavertm: so we ll use the split packages and strip the gstreamer from qt-phonon +23:29 (+reavertm) imho - qt-phonon should provide just phonon library - no platorm sound library +23:29 (@scarabeus) details later plz +23:29 (@hwoarang) ok +23:29 (+reavertm) ok +23:29 (@scarabeus) anything else for kde4.3 +23:29 (@scarabeus) this release seems fine +23:29 (@jmbsvicetto) That way we can add a dep on kde4 eclasses for x11-libs/qt-qt3support[kde] +23:29 (@scarabeus) if we have nothing else +23:29 (+reavertm) yeah, it's b0rked! +23:29 (@scarabeus) borked by upstream +23:30 (@scarabeus) but if there is something from our side +23:30 -!- helch [n=helch@212-41-73-167.adsl.solnet.ch] joins -> #gentoo-kde +23:30 (+reavertm) (bth, it's misusing kde USE flag - better something related to phonon, not kde) +23:30 (@tampakrap) phonon use flag? +23:30 (@hwoarang) we can work on that +23:31 (@hwoarang) kde4 sounds better to me . or kde +23:31 (@yngwin) kde it is +23:31 (@hwoarang) ok move on +23:31 (@jmbsvicetto) hwoarang: As we're talking about kde-4.3, let's spend a few minutes talking about the use flags +23:31 (+reavertm) kde, kde4? +23:31 (@hwoarang) as you wish :) +23:32 (@jmbsvicetto) hwoarang: We should drop the KDE4 use flag now and instead use KDE and KDE3 use flags +23:32 (@tampakrap) kde->kde3 and kde4->kde4 and we can document that too +23:32 (+reavertm) I expreessed my opition on -desktop ml +23:32 (@hwoarang) that discussion took place ages ago +23:32 (@tampakrap) why change the kde use flag? it is already used by kde3 +23:32 (@hwoarang) :/ i m not sure if we reached on some solution +23:32 (@jmbsvicetto) The KDE use flag should give users the best working version at each point in time - that means it should give users KDE4 now +23:32 (@scarabeus) kde = latest kde, for now kde4 +23:32 (@scarabeus) kde3 = kde 3.5 +23:32 (@yngwin) kde useflag means highest available version that is relevant to the package +23:33 (@jmbsvicetto) not exactly the latest. As long as a version is experimental, it makes sense to have one use flag for it +23:33 (@scarabeus) what i write +23:33 (+reavertm) I don't like idea of self-'migrating' USE flag +23:33 (@tampakrap) and what about kgtk for example that supports both? +23:33 (@scarabeus) reavertm: gtk2 gtk1 was pain +23:33 (+reavertm) "now we consider kde as KDE4, later it will be KDE5) +23:33 (@scarabeus) trust me self migrating is better +23:33 (dagger) jmbsvicetto: wouldn't it be less ambiguous to keep kde3 and kde4, so people will _always_ know what potential deps it might have/ +23:33 (@jmbsvicetto) reavertm: that's how it should be, imo +23:33 (+reavertm) dagger: my point +23:34 (@scarabeus) their issue +23:34 (@jmbsvicetto) dagger / reavertm: One can check the local use flags +23:34 (@scarabeus) they can track our anouncement +23:34 (@scarabeus) we have news +23:34 (@scarabeus) so we can sent it to their machine quite obviously +23:34 (@jmbsvicetto) That's why we can now have local descriptions to make clear what each flag does +23:34 (+reavertm) ok, what about compiz? +23:34 (dagger) jmbsvicetto: what if we suddenly change kde flag to old kde4. That will cause problems for users +23:35 (+reavertm) kde3 and kde USE flags? +23:35 (@jmbsvicetto) reavertm: I'll fix that one +23:35 (+reavertm) what about 'kde' meaning "general KDE support" +23:35 (@jmbsvicetto) reavertm: I haven't spend as much time with it as I would like +23:35 (+reavertm) what the heck is that? +23:35 (@scarabeus) dagger: nothing +23:35 (dagger) I really believe we shoudn't have kde and kde3, just kde4 and kde3. That way it's simple for people +23:35 (@scarabeus) they just read anoucnement +23:36 -!- Weaselweb [n=quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409] <- quit [Read error: 104 (Connection reset by peer)] +23:36 (dagger) scarabeus: do you read announcements? Most people don't +23:36 (@scarabeus) their problem +23:36 (@scarabeus) really +23:36 (@scarabeus) i read them +23:36 (@yngwin) indeed +23:36 (+reavertm) jmbsvicetto: I mean, there's choice to build against kdelibs:3.5 and kdelibs4 - it needs to be distinguished +23:36 (@hwoarang) wtf +23:36 (@jmbsvicetto) dagger: That way everyone will have to update their use flags to migrate between versions - I don't think that makes any sense +23:36 (@hwoarang) stop carying about lazy users +23:36 (+papillon81) scarabeus is right. kde should always refer to the latest version +23:36 (@jmbsvicetto) reavertm: yes, I know. I'll keep the 2 use flags, but they're going to become kde3 and kde +23:36 -!- pip_ [n=pip@e179240053.adsl.alicedsl.de] <- quit [Read error: 110 (Connection timed out)] +23:36 (dagger) jmbsvicetto: they will have to modify use flags anyway migrating from 3 to 4, as most use flags are different anyway +23:37 (@yngwin) most users will want/assume support for latest version +23:37 (+reavertm) "general KDE support" means compiling against some kdelibs +23:37 (@jmbsvicetto) dagger: that's a different thing, but kde will mean adding support for KDE +23:37 (+reavertm) there's no "general" kdelibs - it's particular kdelibs that will be pulled +23:37 (dagger) I don't want to wonder - what version might it be today ... and what will it be tommorow - and I'm pretty sure users don't want it as well +23:38 (@yngwin) it's pretty straightforward +23:38 (+reavertm) that being said = "support for KDE" is not clear enough +23:38 -!- LXj [n=lx@ip211-94.telenet.dn.ua] <- quit [Read error: 110 (Connection timed out)] +23:38 -!- wohnout [n=wohnout@kolej-mk-60.zcu.cz] joins -> #gentoo-kde +23:38 (+reavertm) stable users have kde 3.5 and support for kde means support for THEIR kde +23:38 (dagger) no it's not streaightforward. Some will assume - most recent, some will assume stable, some other wont have idea +23:38 (+wired) well one valid alternative would be to just ditch kde and keep kde3 and kde4 +23:38 (+reavertm) for me kde treacking latest kde in portage is no go +23:38 (+reavertm) never +23:39 (dagger) if we change kde to kde3 - we screw stable users and emerge -DN +23:39 (@yngwin) it's been that way for a long time, and for good reasons +23:39 -!- The_Ball [n=The_Ball@d58-106-136-240.sbr4.nsw.optusnet.com.au] joins -> #gentoo-kde +23:39 (dagger) unless you want to do the change when kde4 goes stable +23:39 (+reavertm) yes, my recommendation is to drop 'kde' and keep only 'kde3', 'kde4' and so on +23:39 (@yngwin) dagger: we dont need to change +23:40 (dagger) yngwin: I'm lost than. I thought kde will suppose to be for kde 4 +23:40 (@jmbsvicetto) dagger: I think you're missing an important point - the kde use flag is relevant for misc apps, not for base kde +23:40 (+spatz) will be symmetric with 'qt3', 'qt4', which makes sense to many people +23:40 (@tampakrap) can we vote? options: kde3-kde4 and kde-kde3 +23:40 (@scarabeus) ok +23:40 (@scarabeus) lets have vote +23:40 -!- thansen [n=thansen@c-76-27-110-194.hsd1.ut.comcast.net] joins -> #gentoo-kde +23:40 (@alexxy) reavertm: +1 +23:40 (+Civil) kde3-kde4 +23:40 (@tampakrap) i vote kde3-kde4 +23:40 (dagger) kde3-kde4 +23:40 (@yngwin) kde means kde support +23:40 (+krytzz) kde3-kde4 +23:40 (+wired) do we vote or dev-only? =] +23:40 (@scarabeus) on this only devs please +23:40 (@scarabeus) and use 1 2 +23:40 (+krytzz) oh :p sorry ignore mine +23:41 (@scarabeus) 1 for kde3-kde4 +23:41 (@scarabeus) 2 for kde3-kde +23:41 (@hwoarang) 2 +23:41 (@tampakrap) 1 +23:41 (@yngwin) 2 +23:41 (@alexxy) 1 +23:41 (@scarabeus) 1 +23:41 (@jmbsvicetto) 2 +23:41 (dagger) 1 +23:41 (@scarabeus) erm 2 +23:41 (@jmbsvicetto) scarabeus: I think you messe your vote ;) +23:41 (@scarabeus) i mean 2 +23:41 (@scarabeus) :D +23:41 (@scarabeus) idiot +23:41 (@jmbsvicetto) messed* +23:41 (@scarabeus) yup +23:41 (@yngwin) you pulled a ssuominen +23:41 (@scarabeus) 2222222 +23:41 (@scarabeus) i wont change it +23:42 (@alexxy) no!!!!!! +23:42 (@hwoarang) 2 it is :P +23:42 (@scarabeus) i just wanted to mark kde3-kde as one ; then i read it above +23:42 (dagger) scarabeus: lies! +23:42 (Viedzmin) ave \m/ +23:42 (dagger) scarabeus: ;) +23:42 (@scarabeus) ;[ +23:42 (@scarabeus) ;] +23:42 (@yngwin) so we stay with current practice +23:42 (@jmbsvicetto) ok, so let's move forward +23:42 (@scarabeus) yep +23:42 (@scarabeus) CODE +23:42 (@tampakrap) wait +23:42 -!- doobry [n=quassel@host86-169-175-149.range86-169.btcentralplus.com] <- quit [Read error: 104 (Connection reset by peer)] +23:42 (@yngwin) yes +23:43 (@tampakrap) who will do the change? +23:43 (@tampakrap) :) +23:43 (@yngwin) what change? +23:43 (@hwoarang) you +23:43 (@scarabeus) when you smile so much +23:43 (@scarabeus) guess twice +23:43 (+reavertm) thos who voted that is +23:43 (dagger) scarabeus: can you please explain magic CODE +23:43 (@scarabeus) dagger: you dont get something in it? +23:43 (@scarabeus) then ask +23:43 (@scarabeus) ok what code is +23:43 (@tampakrap) people wait the last topic isn't finished +23:43 (@scarabeus) it is list of things all kde team packages should comply +23:43 (dagger) scarabeus: I have no idea what " - enforcing CODE requirements everywhere" is about +23:43 (+reavertm) look at CODE file in Documentation +23:43 (@tampakrap) we need to grep the tree and change the flags who will do it??????????? +23:44 (@yngwin) tampakrap: NO NEED +23:44 (+reavertm) it's work in progress +23:44 -!- The_Ball1 [n=The_Ball@d58-106-26-133.sbr2.nsw.optusnet.com.au] joins -> #gentoo-kde +23:44 (@scarabeus) http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/CODE +23:44 (@yngwin) only when there is a choice between kde 3 and 4 support do you need to specify USE=kde3 +23:44 (dagger) scarabeus: ok, now I get you +23:44 (@jmbsvicetto) tampakrap: That needs only to be done for latest versions of misc packages that work with KDE4 +23:45 -!- termite47384 [n=me@cpe-066-057-082-106.nc.res.rr.com] <- quit [Read error: 60 (Operation timed out)] +23:45 -!- LXj [n=lx@ip211-94.telenet.dn.ua] joins -> #gentoo-kde +23:45 (+reavertm) ok, so CODE is set of commit policies/guides in overlay basically +23:46 (@scarabeus) in overlay and in tree too +23:46 (+reavertm) maybe some ebuild workflow will be recommended there as well +23:46 (@scarabeus) yup i want everyone to look on it and write some suggestions there and we will merge it +23:46 (+krytzz) repoman plugin for the CODE :p +23:46 (@scarabeus) krytzz: :D +23:46 (@hwoarang) lazy ppl +23:47 (@hwoarang) you can write a quick draft for kde ebuilds, just like i did for qt4 based ebuilds +23:47 (+reavertm) will be there +23:47 (+reavertm) as well as templates for blocks, etc +23:47 (+reavertm) anyway - one rule +23:47 (@yngwin) btw, i want $PN in commit messages for qting-edge as well +23:48 (@hwoarang) hm? +23:48 (+reavertm) everyone should respect them :) +23:48 (@jmbsvicetto) scarabeus: If we have a CODE file, I might add a few suggestions about ebuilds (the ones reavertm noted some time ago) +23:48 (@scarabeus) yep this one is draft +23:49 (@scarabeus) althrought i enforce it as-is +23:49 (@scarabeus) so please improve it +23:49 (@hwoarang) yngwin: what? you want a template for qting-edge commits? +23:49 (@scarabeus) and in next meeting it will be enabled as hard-forced +23:49 (@scarabeus) and we should punish not folowing it +23:49 -!- Red_Devil [n=red@lounge.datux.nl] joins -> #gentoo-kde +23:49 (@scarabeus) i know annoying, but reduces time needed for maintaining +23:49 (@hwoarang) indeed +23:49 (@yngwin) hwoarang: yes please start commit msg with $PN +23:50 -!- Red_Devil is now known as Guest36992 +23:50 (@hwoarang) thats sad. I really enjoyed funny commit messages +23:50 (@hwoarang) :D +23:50 (@yngwin) i dont mind funny :) +23:50 (@hwoarang) ok hold on +23:50 (+reavertm) ok, anything else? next? +23:50 (@yngwin) but i do want to see what pkg is affected +23:50 (@hwoarang) !herd qt && Pesa && spatz +23:50 (+wired) lol-cat/pn +23:50 (@hwoarang) ^^ +23:50 (@hwoarang) && wired +23:51 (Pesa) hwoarang: i'm here +23:51 -!- mode/#gentoo-kde [+vv Pesa spatz] by scarabeus +23:51 (+wired) hwoarang: seriously, we read it already +23:51 (+wired) :D +23:51 (@hwoarang) did you see what we said about commit messages? +23:51 -!- The_Ball_ [n=The_Ball@d58-106-141-118.sbr4.nsw.optusnet.com.au] <- quit [Read error: 110 (Connection timed out)] +23:51 (+spatz) yep +23:51 (@hwoarang) you did +23:51 (@hwoarang) ok +23:51 (+Pesa) yes +23:52 (@hwoarang) anything else about CODE kde ppl? +23:52 (@scarabeus) ok +23:52 (@scarabeus) code done +23:52 (@scarabeus) if noone has anything else +23:52 (Willikins) hwoarang: incorrect usage, ask for help using 'Willikins: help herd' +23:52 (+wired) lolz +23:52 (@hwoarang) yes baby whatever +23:52 (@scarabeus) next new pple in team etc/etc... +23:52 (@scarabeus) so if you move your eyes to voiced pple +23:53 (@hwoarang) we have plenty of them :P +23:53 (@scarabeus) those are our not-yet deved/herdtested resources +23:53 (@jmbsvicetto) hmmm, we're at around half of the agenda and we're hitting the 2 hour mark +23:53 (+wired) who did you call a resource!!! :D +23:53 (@yngwin) wired has finished quizzes, now it's up to recruiters +23:53 (@hwoarang) this meeting will last forever! +23:53 (@scarabeus) jmbsvicetto: too much spam about kde3 +23:53 (+krytzz) 1/4 if you add the qt stuff jmbsvicetto :p +23:53 (@hwoarang) \o/ +23:53 (@scarabeus) most is done +23:53 (+reavertm) jmbsvicetto: you know - it's merithorical meeting, not just fluff talk! :) +23:53 (@scarabeus) jmbsvicetto: kdeprefix is done +23:53 (@scarabeus) and so on +23:54 (@yngwin) i'm interjecting qt recruits now +23:54 (@scarabeus) ok so if you pple want to mentor someone +23:54 (+reavertm) scarabeus: I'd have some idea +23:54 (@scarabeus) or vice versa, if someone has urge became dev fast :D +23:54 (@scarabeus) reavertm: you dont count, you have resistance to becaming dev, althrought i dunno why ;D +23:54 (+reavertm) even if we have quite many HT's and contributors, I still feel we're understaffed in terms of tracking uptream patches +23:54 (@yngwin) Pesa has been very active with Qt already, and spatz is our newest recruit +23:55 (@hwoarang) \o/ +23:55 (+wired) woot +23:55 (@yngwin) they both are on their way to devhood +23:55 (+spatz) :D +23:55 (+Pesa) ;) +23:55 (@yngwin) there is another one, sping, not here now, he will join us after finishing GSoC +23:55 (@tampakrap) and me :D +23:55 (@hwoarang) we are growing fast +23:55 (@hwoarang) be carefeull +23:55 (@scarabeus) for kde team i would like krytzz and papillon81 to work on their ebuild quiz, cause you two are progressing :] +23:55 (+papillon81) scarabeus: i have the quiz ready :-) +23:55 (@scarabeus) great +23:56 (@scarabeus) papillon81: sent it by mail, and we will discuss the meeting about it +23:56 (+wired) yngwin: btw when should I expect a response? :) +23:56 (@scarabeus) later :} +23:56 (@hwoarang) soon wired +23:56 (+krytzz) i cant devote enough time currently to do serious stuff +23:56 (@yngwin) tampakrap: you may hear from sping (sebastian) as he is interested in qt3/kde3 maintenance +23:56 (@yngwin) wired: usually within a few days +23:56 (+reavertm) btw, what about 'assigning' some herd packages to particulat people? +23:57 (+reavertm) for example one would take kdepim, someone else kdebindings +23:57 (@tampakrap) not kde-base/* only extra packages +23:57 (@scarabeus) reavertm: it needs interest +23:57 (+reavertm) this way work is somewhat split +23:57 -!- mikkoc [n=mikko@host116-78-dynamic.17-79-r.retail.telecomitalia.it] <- quit [Remote closed the connection] +23:57 (+papillon81) scarabeus: it's mostly ready but already lying around for a year or so. will have to look over it +23:57 (+wired) yngwin: thnx +23:57 (@scarabeus) papillon81: no prob :} +23:57 (+reavertm) scarabeus: of course... unfortunately +23:58 (@scarabeus) ok i think that is all i wanted about recruits +23:58 (@jmbsvicetto) reavertm: That's against the spirit of herds +23:58 (@scarabeus) i wanted you to see them +23:58 (@scarabeus) and also whom is progressing i contacted +23:58 (@jmbsvicetto) reavertm: But nothing prevents one from adding himself to a package belonging to one of the herds +23:58 -!- dagger [n=dagger@gentoo/developer/dagger] <- leaves #gentoo-kde ["http://quassel-irc.org - Chat comfortably. Anywhere."] +23:58 -!- dagger [n=dagger@gentoo/developer/dagger] joins -> #gentoo-kde +23:58 -!- mode/#gentoo-kde [+o dagger] by ChanServ +23:58 (@scarabeus) anything else upon recruits? +23:58 (@scarabeus) anyone? +23:59 -!- The_Ball [n=The_Ball@d58-106-136-240.sbr4.nsw.optusnet.com.au] <- quit [Read error: 110 (Connection timed out)] +23:59 (@scarabeus) jokey: are you here? +23:59 (+reavertm) jmbsvicetto: I'm not talking about beaurocracy (adding to metadata) but real maintenance (periodically looking for some bugs in kde.org) +23:59 (+reavertm) or we can just rely on b.g.o +23:59 (@scarabeus) we are good at handling new bugs +23:59 (@scarabeus) really +23:59 (@jmbsvicetto) reavertm: Well, people can focus on particular areas +--- Day changed Fri May 22 2009 +00:00 (jokey) scarabeus: yep +00:00 (@jmbsvicetto) About bugs, we need to start paying extra attention to security bugs +00:00 (@scarabeus) jokey: so, what i need to do to be able to add pple to our git overlay +00:00 (@scarabeus) jokey: i can do for sunrise, so what is needed to be done for kde team ones +00:00 (@jmbsvicetto) you need to poke him :P +00:00 (@scarabeus) i know +00:00 (@jmbsvicetto) or rbu or robbat2 +00:00 (@scarabeus) directly i mean +00:00 (jokey) need to mess with robin, I'll poke you back +00:00 (@scarabeus) rbu cant touch git +00:00 (@jmbsvicetto) scarabeus: he can +00:01 (@dagger) scarabeus: he can +00:01 (@scarabeus) jokey: this workflow is unflexible :] +00:01 (@scarabeus) dagger: good update :] +00:01 (@scarabeus) okey i will handle this with jokey internaly then :] +00:01 (@scarabeus) the next topic is our guide +00:01 (@scarabeus) kde4 one +00:01 (@scarabeus) it neeeds update/cleanup +00:01 (@scarabeus) who will do it +00:01 (+reavertm) "handling cmake relwithdebuginfo compilation to please upstream..." ? +00:01 (jokey) internally? oO teh sekrit +00:02 (joost_op) guys can the sabayon point on the agenda be discussed at later time +00:02 (@jmbsvicetto) joost_op: hehe +00:02 (@scarabeus) reavertm: deffered +00:02 (@scarabeus) reavertm: thought about it +00:02 (@scarabeus) reavertm: not worth +00:02 (+krytzz) what?? +00:02 (+reavertm) yeah, agreed +00:02 (+papillon81) goooood +00:02 (@scarabeus) jokey: definetly +00:02 (@scarabeus) ;] +00:03 (joost_op) jmbsvicetto, i think it can be talked about off the record anyway +00:03 (@scarabeus) so the guide +00:03 (+krytzz) ok then lets discuss this later scarabeus +00:03 (@scarabeus) who +00:03 (@tampakrap) wait +00:03 (@tampakrap) about the guide +00:03 (@tampakrap) would you like a kde3/4 monolithic one? +00:03 (@jmbsvicetto) joost_op: sorry, that was meant for jokey +00:03 -!- pgega [n=pgega@77-99-66-168.cable.ubr01.tonb.blueyonder.co.uk] joins -> #gentoo-kde +00:04 (joost_op) oh +00:04 (@yngwin) tampakrap: i think it makes sense, with kde4 going to go stable +00:04 (@tampakrap) stating how to install kde4, how to install live/snapshots and how to install 3.5, and how we can mix them +00:04 (@tampakrap) i'll do the guide +00:04 (@tampakrap) agreed with the mixed guide? +00:05 (joost_op) scarabeus, let me know the outcome of the dicussion +00:05 (@tampakrap) boss? devs? hts? +00:05 (joost_op) if any +00:05 (@scarabeus) tampakrap: agreed +00:05 (@scarabeus) so quiet... +00:05 (@jmbsvicetto) tampakrap: Perhaps we could have a new doc that points to specific guides about KDE4 and KDE3 +00:05 (@scarabeus) what happend +00:05 -!- AntiXpucT [n=Skim@77.106.108.232] <- quit [] +00:06 (@jmbsvicetto) tampakrap: That doc would just focus on the integratio of 3 and 4 +00:06 (@yngwin) scarabeus: more beer, less talk ;) +00:06 (@hwoarang) lolz +00:06 (@jmbsvicetto) yngwin: I need to have some fun with work network yet, so no beer for me ;) +00:06 (@yngwin) heh +00:06 (+reavertm) if we focus guys - we'll finish earlier :P +00:07 (@hwoarang) ok with the guide? +00:07 (joost_op) +1 +00:07 (@hwoarang) shall we proceed? +00:07 (@hwoarang) tampakrap: ? +00:07 (@tampakrap) jmbsvicetto: the procedure to install kde3 and to install kde3/4 isn't different so i wouldn't agree :) +00:07 (@tampakrap) same sets, same keyword files... +00:07 (@jmbsvicetto) tampakrap: ok, feel free to work on it +00:07 (@yngwin) i say whoever writes the guide(s), gets to make the decision +00:07 (@tampakrap) ok move on then +00:08 (@scarabeus) ok yngwin you take over +00:08 (@hwoarang) what about kdebindings? +00:08 (@hwoarang) is this off as well? +00:08 (@scarabeus) eh +00:08 (+reavertm) lacks some ebuilds +00:08 (@scarabeus) right +00:08 (@scarabeus) bindigns +00:08 (@dagger) "kdebindings, lots of stuff missing there" +00:08 (@scarabeus) we lacks tons of stuff +00:08 (+reavertm) usually ruby and c# +00:08 -!- jmbsvicetto topic of #gentoo-kde ->> Gentoo KDE | meeting: Now - kdebindings | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU +00:09 (+wired) lol +00:09 (@yngwin) ok, whats the story with ruby for kde? does that depend on (currently broken) qt4-qtruby at all? +00:09 (+reavertm) nobody knows :) +00:09 (@scarabeus) ruby java c# php +00:09 (@scarabeus) so whom wants it +00:09 (+reavertm) - we need to try add those ebuilds +00:09 -!- ABCD [n=ABCD@wikipedia/ABCD] joins -> #gentoo-kde +00:10 (+reavertm) - maybe some ebuild name refactor for 4.3 +00:10 (+reavertm) anything else regarding kdebindings? +00:10 (@scarabeus) ok reavertm we will talk about it later +00:10 (@jmbsvicetto) scarabeus: no PERL? +00:10 (@scarabeus) reavertm: and delegate to other HTs +00:10 (@scarabeus) jmbsvicetto: no perl +00:10 (@jmbsvicetto) I suggest we hand JAVA to bonsaikitten :P +00:10 (@scarabeus) bindigns done +00:11 (@scarabeus) joost_op: do you want to talk about sabayon then? +00:11 (@jmbsvicetto) He's becoming too sane +00:11 (@scarabeus) D +00:11 (@bonsaikitten) jmbsvicetto: thank you :) +00:11 (@jmbsvicetto) bonsaikitten: we aim to please ;) +00:11 (@bonsaikitten) I aim to kill +00:11 (+papillon81) :D +00:11 (joost_op) well scarabeus i'm here +00:12 (+reavertm) go :) +00:12 (@scarabeus) shoot +00:12 (@scarabeus) :] +00:12 (@dagger) RUN! +00:12 (joost_op) from the sabayon side we want to shoulder the kde herd as much as possible +00:12 -!- Guest36992 [n=red@lounge.datux.nl] <- quit [Read error: 60 (Operation timed out)] +00:12 (joost_op) what we can offer would be something in the form off a repository that has experimental kde stuffs, built of the testing tree +00:12 (+reavertm) you already did with some automagic deps and doc verification +00:13 (joost_op) since i would maintain that tree, i could feedback about my findings +00:13 (+reavertm) binary packages you mean? i don't follow +00:13 (joost_op) nah +00:14 (joost_op) i built against a tree thats near full portage +00:14 -!- UT2K3 [n=UT2K3@212.86.209.81] joins -> #gentoo-kde +00:14 (joost_op) sabayon is near full portage +00:14 (+reavertm) yes, I know, what would be that experimental kde stuff? +00:14 -!- FlyingFoX [n=FlyingFo@137.226.140.67] joins -> #gentoo-kde +00:14 (joost_op) well, e.g. you are working on kde 4.3 +00:15 (joost_op) i could add this in a kde repository +00:15 (joost_op) and start working on this and feedback my findings +00:15 (UT2K3) hello guys, i'm using fglrx with dualscreen. When run kde its only on the notebook lcd and the right screen have no wm. Its possible to make it work? +00:15 (@hwoarang) why not use the ebuilds from kde-testing? whu starting a new repository +00:15 (joost_op) if you think it would help collect info +00:15 (@hwoarang) UT2K3: meeting now . laterz : +00:15 (@hwoarang) :) +00:16 (joost_op) hwoarang, we don't want that in our mainline repositories .. +00:16 (+krytzz) joost_op hm well duplicated work/ebuilds is always bad :p +00:16 (UT2K3) oh its still meeting ok +00:16 (@hwoarang) as krytzz said, duplicating ebuilds will lead to more compilcated results +00:17 (@dagger) UT2K3: yeah, but it shouldn't take long now +00:17 (joost_op) do you guys to start with see a benefit in me, or sabayon, help testing +00:17 (tdr) duplicated ebuild confuse people +00:17 (+reavertm) joost_op: you're free to do anything with ebuilds - and patches (those upstream I guess) are always welcome +00:17 (UT2K3) okay (= ty +00:17 (@jmbsvicetto) joost_op: If you want to cooperate, using something we provide would seem to be better for both projects than duplicating work +00:17 (joost_op) nono +00:17 (joost_op) your ebuilds +00:17 -!- panard [n=panard@2a01:e35:8a09:e130:2e0:61ff:fe11:7adb] <- quit [Read error: 104 (Connection reset by peer)] +00:18 (+reavertm) joost_op: you just need to find someone to take care of this - it's quite a bit of work +00:18 (joost_op) lol +00:18 (@jmbsvicetto) So you mean you could test ~arch ebuilds? +00:18 (joost_op) x86 and amd64 +00:18 (+krytzz) joost_op we had this already with kde-crazy and kde-testing, was a mess :p +00:18 (@jmbsvicetto) Then go for it, we'll be glad to get bug reports +00:18 (joost_op) i have a power machine to built +00:18 (@scarabeus) ok i will put it this way +00:19 (joost_op) i have testers AND users that report +00:19 (@scarabeus) bugs from ppl with @sabayonlinux.org will be handled legitimely as our bugs +00:19 (@scarabeus) and we can reflect them as HTs +00:19 (@jmbsvicetto) joost_op: although most of us run ~arch or stuff in kde-testing +00:19 (joost_op) i can filter whats important +00:19 (@scarabeus) just for internal herd needs +00:19 -!- Sho_ [n=EHS1@kde/hein] <- quit [Read error: 104 (Connection reset by peer)] +00:19 (@scarabeus) so we can rely for some info from them +00:19 (+reavertm) especially those automagic deps are welcome +00:19 (@scarabeus) yep +00:19 (+reavertm) :) +00:20 (@scarabeus) those made mine day great :] +00:20 -!- Sho_ [n=EHS1@kde/hein] joins -> #gentoo-kde +00:20 (joost_op) yeah in our staff meeting we talked about how to report anything back to gentoo +00:20 (@jmbsvicetto) ok, I'll have to leave in approximately 10 minutes +00:20 (@dagger) Qt stuff now? +00:21 (@scarabeus) jmbsvicetto: did you read what i wrote? +00:21 (@scarabeus) any objections to that? +00:21 (joost_op) anybody from our team uses @sabayonlinux.org +00:21 (@jmbsvicetto) joost_op: we discuss details later with you. We can even schedule some time +00:21 (joost_op) and each report has been dicussed in our team first +00:21 -!- panard [n=panard@banquise.backzone.net] joins -> #gentoo-kde +00:21 (joost_op) to not overload anybody +00:21 (joost_op) and to certainly not duplicate work +00:21 (@jmbsvicetto) scarabeus: no objection +00:22 (joost_op) allright +00:22 -!- helch [n=helch@212-41-73-167.adsl.solnet.ch] <- quit [Remote closed the connection] +00:22 (@jmbsvicetto) In some cases we might require some testing to duplicate the bug, but we'll address the bugs +00:22 (joost_op) i'm saying you can abuse me to get things in our yet to make repository +00:22 (joost_op) where we can heve people to test it +00:23 (joost_op) *have +00:23 (@jmbsvicetto) ok, thanks +00:23 -!- mpagano [n=mpagano@gentoo/developer/mpagano] <- quit ["cya"] +00:23 (@scarabeus) ok we will address this issue more at more comfy time :] +00:23 (@scarabeus) now lets get to the qt +00:23 (@hwoarang) \o/ +00:23 (@hwoarang) ************************** qt meeting ***************************** +00:23 (joost_op) allright, thx +00:23 (@hwoarang) wake up ppl +00:23 (+Pesa) :) +00:23 (@hwoarang) !herd qt +00:24 (+wired) hwoarang: seriously, we're all here +00:24 (Willikins) (qt) carlo, hwoarang, tampakrap, yngwin +00:24 (+wired) :D +00:24 (@dagger) bear time :) +00:24 (@hwoarang) spatz: ping +00:24 (+spatz) pong +00:24 (@dagger) (not ever beer :p) +00:24 (@jmbsvicetto) hwoarang: technically it's still the KDE *team* meeting ;) +00:24 (@hwoarang) well yes :P +00:24 (@yngwin) ok, first decision: next time separate qt meeting +00:24 (@hwoarang) i just wanted to wake them up +00:24 (@hwoarang) :D +00:24 (@yngwin) this is getting too long for some ppl +00:24 (+reavertm) I agree +00:24 -!- Sho_ [n=EHS1@kde/hein] <- quit [Read error: 104 (Connection reset by peer)] +00:24 (@tampakrap) for all +00:24 (@hwoarang) i think this is the first time the kde one took that long +00:25 (@scarabeus) yngwin: well the issue is due to we didnt have meeting in 2 months window +00:25 (+reavertm) we're technical, soory ;) +00:25 (@yngwin) i know +00:25 (@jmbsvicetto) yngwin: Do you think it's best to have split meetings or should we have more frequent/shorter meetings? +00:25 (@scarabeus) good Q +00:25 (@yngwin) more frequent + shorter +00:25 (+reavertm) split meeting is good anyway +00:25 (+papillon81) first of all we should go on with the topics +00:25 (@hwoarang) +1 yngwin +00:25 (+reavertm) no need to qt folks to attend to kde meeting anyway unless they're interested +00:26 (@jmbsvicetto) yngwin: I can live with both and if we keep having the same meeting, qt issues don't (shouldn't) be left for the end +00:26 (@hwoarang) meeting is supposed to be 'project' wise +00:26 (@hwoarang) not herd wise +00:26 (@scarabeus) jmbsvicetto: it is for this time +00:26 (@scarabeus) jmbsvicetto: next time i can shuffle the topics +00:26 (@jmbsvicetto) yeah, I'm just opening up other solutions in case people prefer them +00:26 (@scarabeus) and we can have the meetings often i dont mind :] +00:26 (@yngwin) alright, lets get on it +00:26 -!- Civil [n=Civilian@95-24-2-240.broadband.corbina.ru] <- quit [Remote closed the connection] +00:27 (@yngwin) we can discuss needs for next meeting tomorrow ;) +00:27 (@hwoarang) i think we can pass the recruit stuff +00:27 (@scarabeus) okey +00:27 (@yngwin) recruits i already mentioned +00:27 (@yngwin) qt status in tree +00:27 (@yngwin) 4.5.1 is goibng stable, but arches are slow +00:27 (@hwoarang) indeed :/ +00:27 -!- Displacer [n=tool@tool.gtn.ru] <- quit ["Leaving"] +00:27 (+wired) !earch qt-core +00:27 (Willikins) wired: x11-libs/qt-core 4.4.2[4]: 4.4.2-r2[4]: amd64 hppa ia64 ppc64 sparc x86 4.5.1[4]: alpha ~amd64 ~arm ~hppa ~ia64 ~mips ppc ~ppc64 ~sparc ~x86 ~x86-fbsd +00:28 (@hwoarang) there is a bug about the -platform . The addition on qt4-build-edge eclass seems to fix it +00:28 -> hwoarang searches the bug +00:28 (+wired) bug 266201 +00:28 (Willikins) wired: https://bugs.gentoo.org/266201 "Please mark x11-libs/qt-*-4.5.1 stable [also regression tracker]"; Gentoo Linux, Ebuilds; NEW; yngwin@g.o:qt@g.o +00:28 (@hwoarang) bug 270475 +00:28 (Willikins) hwoarang: https://bugs.gentoo.org/270475 "x11-libs/qt-4.5 configure guesses arch based on uname"; Gentoo Linux, Ebuilds; NEW; jokey@g.o:qt@g.o +00:29 -!- emera|d [n=smaragd@p579DE9E7.dip.t-dialin.net] <- quit [] +00:29 (@hwoarang) this bug ( and the proposed solution ) seems to fix the massive errors we had with ppc, chroots, distcc etc +00:30 (@yngwin) ok, i propose we add arches on that one, and ask their opinion +00:30 (@jmbsvicetto) It would great if you could get upstream to fix qt-webkit on sparc +00:30 (+papillon81) there is another patch for qt-gui (already in the qting-edge overlay), that fixes PPC graphics issues and should go to the treee ASAP +00:30 (@hwoarang) qt-gui is stable on ppc +00:30 (@jmbsvicetto) We won't be able to get KDE in sparc until qt-webkit is fixed or we can make KDE upstream make it optional +00:30 (@yngwin) bug number? +00:30 (+wired) yngwin: ^^ thats the one i've talked to you about +00:31 (@hwoarang) jmbsvicetto: dont expect this to happen soon +00:31 (@yngwin) i know, i still havent heard if its so important and why +00:31 (@hwoarang) upstream is really really slow +00:31 (+papillon81) yngwin: no bug # +00:31 (@hwoarang) i really dont think we should do a revbump just for a ppc patch +00:31 (@hwoarang) cause all other arches will upgrade for nothing +00:31 (@hwoarang) maybe we can put is 'silently' on stable qt-gui-4.5.1 +00:31 (@hwoarang) *s/is/it +00:31 (+papillon81) hwoarang: just add it silently :-) +00:32 (@yngwin) we need a proper bug report +00:32 -> papillon81 will do it +00:32 (@tampakrap) well, revbump and tell ppc to stabilize again +00:32 (@yngwin) because i still dont know what we're talkingf about +00:32 (@tampakrap) it won't break stable users anywayz +00:32 (@hwoarang) tampakrap: revbump is wrong +00:32 (@hwoarang) the rest of arches dont need to emerge qt-gui again +00:32 (@jmbsvicetto) yngwin / wired: are you asking the bug number for qt-webkit and sparc? +00:33 (@hwoarang) it is just a ppc patch that can go on the current qt-gui +00:33 (@tampakrap) i know but there is no other way +00:33 (@yngwin) ok, we can discuss that on the bug +00:33 (+wired) jmbsvicetto: no the patch for qt-gui and ppc +00:33 (@hwoarang) good +00:33 (@yngwin) jmbsvicetto: no, the ppc issue +00:33 (@jmbsvicetto) ok +00:33 (+wired) jmbsvicetto: it doesn't have a bug +00:34 (@tampakrap) two options, silent update or revbump and restabilize, choose one, i choose the second +00:34 (@yngwin) ok, other in tree issues? +00:34 (@hwoarang) scarc issue should go upstream but i am pretty sure it ll take forever even to accept it as valid +00:34 -!- ali_bush_work [i=cab44391@gateway/web/ajax/mibbit.com/x-e12143e624250926] joins -> #gentoo-kde +00:34 (@yngwin) yes, but we can do our duty and report +00:34 (@hwoarang) yes +00:34 (@hwoarang) of course +00:34 (@tampakrap) wait +00:34 (@tampakrap) the sparc issue is reported by me in gentoo bugzilla long time ago +00:34 (@tampakrap) i've made some research about it +00:35 (@hwoarang) yes but did you take it upstream? +00:35 (@tampakrap) there was actually a patch +00:35 (@hwoarang) can you ? +00:35 (@hwoarang) mmm +00:35 (@yngwin) bug # ? +00:35 (@tampakrap) but it broke ppc64 i think or something +00:35 (@jmbsvicetto) tampakrap: The patch wasn't accepted upstream +00:35 (@tampakrap) of course since it broke ppc64 +00:35 (@jmbsvicetto) tampakrap: And iirc, that bug may also affect alpha (or at least also interests them) +00:35 (@yngwin) we could apply the patch only on sparc +00:36 (@tampakrap) yes +00:36 (@tampakrap) exactly +00:36 (@hwoarang) sound like an easy work around +00:36 (@tampakrap) i own a sparc but it will take some time to update it to qt-4.5 +00:36 (@tampakrap) i'll contact sparc herd as well +00:36 (@hwoarang) ok +00:36 (@jmbsvicetto) tampakrap: tcunha and jmorgan might be willing to help out with it +00:37 (@tampakrap) bug 235685 +00:37 (Willikins) https://bugs.gentoo.org/235685 "x11-libs/qt-webkit-4.4.x sigbus on ~sparc"; Gentoo Linux, KDE; NEW; tampakrap@g.o:sparc@g.o +00:38 (@hwoarang) ok +00:38 (@yngwin) ok, if you can follow-up on that with sparc arch team +00:38 (@tampakrap) comment 7 says that it should not be restricted to sparc only +00:38 -!- B-Man1 [n=B-Man@cpe-098-024-241-139.ec.res.rr.com] joins -> #gentoo-kde +00:38 (@tampakrap) i don't know why +00:38 (+papillon81) bug 270769 +00:38 (Willikins) papillon81: https://bugs.gentoo.org/270769 "x11-libs/qt-gui-4.5.1 PPC endian fix"; Gentoo Linux, Ebuilds; NEW; chrschmitt@gmail.com:bug-wranglers@g.o +00:38 (@yngwin) tampakrap: could be interesing for other arches too, like alpha +00:39 (@yngwin) papillon81: tnx +00:40 (@hwoarang) are we done with bugs? +00:40 (@yngwin) no +00:40 (@yngwin) i'd like someone to look at bug 209626 +00:40 (Willikins) yngwin: https://bugs.gentoo.org/209626 "Patches for qt4.eclass and qt4-build.eclass to make them ready for eclass-manpages"; Gentoo Linux, Eclasses and Profiles; NEW; bugs@rennings.net:qt@g.o +00:41 (@hwoarang) I will take care of it +00:41 (@yngwin) thanks +00:41 (@hwoarang) anything else? +00:42 -!- andreax [n=andreaz@p57B94087.dip.t-dialin.net] joins -> #gentoo-kde +00:42 (@yngwin) and is there anyone interested in bug 224951 ? +00:42 (Willikins) yngwin: https://bugs.gentoo.org/224951 "[Tracker] dev-ruby/qt4-qtruby issues"; Gentoo Linux, Applications; NEW; unnamedrambler@gmail.com:ruby@g.o +00:42 -!- Friesia [n=speckius@212.113.107.78] <- quit [Remote closed the connection] +00:42 (@yngwin) it has been hardmasked (all versions) in tree for a while now +00:42 (@hwoarang) brrrrrrrrrrrrr ruby +00:43 (@yngwin) well, i think we should fix it or schedule for removal +00:43 (@hwoarang) we can ping ruby herd again +00:43 (@hwoarang) as reach a common decision +00:43 (@hwoarang) *and +00:44 (@yngwin) i started doing some testing on 2.x version, but didnt get far +00:44 (+wired) i could give it a try as well +00:44 (@hwoarang) we can add it on overlay and start playing +00:44 (@yngwin) i needs work (which means time) +00:44 (@yngwin) ok, i'll add what i have to overlay +00:44 (@hwoarang) ok +00:44 (+wired) =] +00:44 (@hwoarang) bug 236341 needs some love as well +00:44 (Willikins) hwoarang: https://bugs.gentoo.org/236341 "PyQt4 has automagic dependencies"; Gentoo Linux, Ebuilds; REOP; alessandro.guido@gmail.com:qt@g.o +00:45 (@hwoarang) i think me and Pesa will get this done soon +00:45 (+Pesa) i'm working on that one +00:45 (@yngwin) nice +00:45 (@hwoarang) sweet +00:45 (@hwoarang) i cant see anything else +00:45 (+Pesa) btw, bug 251997 was fixed some time ago +00:45 (Willikins) Pesa: https://bugs.gentoo.org/251997 "net-im/psi: pre-stripped files found"; Gentoo Linux, Ebuilds; NEW; flameeyes@g.o:welp@g.o +00:45 -!- andreax1 [n=andreaz@p57B9556B.dip.t-dialin.net] <- quit [Operation timed out] +00:45 (+Pesa) please mark as such :) +00:45 (@yngwin) ok, we can close that? +00:45 (@hwoarang) yes indeed +00:45 (+Pesa) yep +00:46 (+Pesa) fixed by a change in eqmake4 +00:46 (@yngwin) done +00:46 (@hwoarang) \o/ +00:46 (+Pesa) thanks +00:46 (@hwoarang) any other bugs? +00:46 (@yngwin) what about the embedded stuff +00:47 (@hwoarang) tricky +00:47 (@hwoarang) qt-embedded? +00:47 (@yngwin) esp https://bugs.gentoo.org/show_bug.cgi?id=43827#c9 +00:48 (@hwoarang) we can contact him +00:48 (@yngwin) maybe we should contact him and see if he still wants to maintain it +00:48 (@hwoarang) and ask him to be proxy mantainer +00:48 (@yngwin) then add it to overlay or tree +00:48 (@yngwin) indeed +00:48 -> hwoarang noted +00:48 (@hwoarang) I will contact him +00:48 (@yngwin) ok, on to overlay then? +00:49 -!- panard [n=panard@banquise.backzone.net] <- quit [Read error: 54 (Connection reset by peer)] +00:49 (@hwoarang) sorry? +00:49 (@tampakrap) yes +00:49 (@yngwin) next point on agenda +00:49 (@hwoarang) we are moving on? +00:49 (@hwoarang) ok +00:49 (@hwoarang) Pesa: spatz +00:49 (@hwoarang) are you guys using qt live ebuilds? +00:49 (+Pesa) no +00:49 (+spatz) nope +00:49 -!- Guest36992 [n=red@lounge.datux.nl] joins -> #gentoo-kde +00:49 (@tampakrap) i am +00:50 (@hwoarang) ok +00:50 (+papillon81) me +00:50 (+reavertm) i use qt-copy in chroot +00:50 (@hwoarang) so we need to see who maintains what +00:50 (@hwoarang) i do maintain 4.5.9999 (both qt-copy and nokias ) +00:50 (@yngwin) i use latest release +00:50 (+reavertm) but I'm no longer maintaing those... +00:50 (@hwoarang) that is 4.9999? +00:50 (@hwoarang) wired: is on 4.9999 +00:50 (+wired) i test 4.999 and 4.5.9999[-qt-copy +00:50 (@yngwin) 4.9999 is nokia qt git trunk +00:50 (+wired) i test 4.999 and 4.5.9999[-qt-copy] +00:51 -!- panard [n=panard@2a01:e35:8a09:e130:2e0:61ff:fe11:7adb] joins -> #gentoo-kde +00:51 (@hwoarang) so we are ok on that +00:51 -!- Polynomial-C [n=Poly-C@gentoo/developer/Polynomial-C] <- quit [Remote closed the connection] +00:51 (+wired) nokia +00:51 (+wired) 4.6 trunk and 4.5 trunk ^^ :) +00:51 -!- Hello_World [n=koukos@ip-83-212-218-40.adsl.aueb.gr] joins -> #gentoo-kde +00:51 (@hwoarang) ok so we re ok on qt libe ebuilds +00:52 (@hwoarang) *live +00:52 (+wired) we should discuss what will happen to the RDEPEND in qt4-edge-build +00:52 (@hwoarang) yes +00:52 (+wired) are we moving that in tree? +00:52 (@yngwin) is it tested enough? +00:52 (+wired) today tampakrap had yet another issue +00:52 -!- UT2K3 [n=UT2K3@212.86.209.81] <- quit [Remote closed the connection] +00:53 (@hwoarang) what about the paludis support +00:53 (+wired) yngwin: so far it seems safe on my tests +00:53 (+wired) paludis doesn't like it but thats only because ciaran doesn't want to implement blocks the same way portage does +00:53 (@yngwin) paludis seems to be broken at this point +00:53 -!- Polynomial-C [n=Poly-C@gentoo/developer/Polynomial-C] joins -> #gentoo-kde +00:53 (@bonsaikitten) hwoarang: why do we care? +00:53 (@hwoarang) cause i cant stand the trolls tomorrow +00:54 -!- bschindl [n=quassel@77-56-156-71.dclient.hispeed.ch] <- quit [Read error: 104 (Connection reset by peer)] +00:54 (+wired) no trolls +00:54 (@hwoarang) if you know what i mean +00:54 (+wired) actually +00:54 (@bonsaikitten) so ignore them +00:54 (@bonsaikitten) "WORKSFORME" is a great defense ;) +00:54 (+wired) this is one of the few cases where he didn't complain +00:54 (@hwoarang) in this case we can proceed +00:54 (+wired) i think the way this works is valid and paludis should adapt if it wants to work +00:54 (@hwoarang) the solution is pretty clean and easily revertable +00:55 (@hwoarang) yngwin: what do you think +00:55 (@yngwin) i dont think there is a better solution +00:55 -!- termite47384 [n=me@cpe-066-057-082-106.nc.res.rr.com] joins -> #gentoo-kde +00:55 -!- mode/#gentoo-kde [+v termite47384] by ChanServ +00:55 (@hwoarang) ok then we can proceed +00:55 (@yngwin) if we talk about eclass functionality anyway +00:55 (+wired) ok then it should go to qt4-build along with anything else we decide to migrate +00:55 (@yngwin) what about other stuff we want to move to tree +00:56 (@hwoarang) well +00:56 (@hwoarang) qt4-build can use -platform as discussed before +00:56 (@hwoarang) but that should take a while +00:56 (@yngwin) yes +00:56 (@hwoarang) we need to invite arches on that bug +00:56 (@hwoarang) i have nothing else to propose for qt4-build +00:57 (@hwoarang) i think this eclass has been reviewed recently +00:57 (@hwoarang) just before pushing qt-4.5.0_rc1 +00:57 (@yngwin) we need to remove custom-cxxflags when 4.5.2 goes in +00:57 (@hwoarang) yes +00:58 (@hwoarang) this use flag has been dropped on overlay. Works ok . +00:58 (@hwoarang) we are safe to drop it when 4.5.2 arrives +00:58 (@yngwin) good, let's not forget +00:58 -> hwoarang noted +00:58 (@yngwin) what about qt4.eclass +00:58 (@hwoarang) Pesa: here we are +00:58 (@hwoarang) :D +00:59 (+Pesa) heh +00:59 (@yngwin) we wanted qt4-edge -> qt4-ng or something? +00:59 (@hwoarang) i think that you pushed a default src_configure and src_install in the past +00:59 (@hwoarang) but you revert it +00:59 (@hwoarang) why? +00:59 (@yngwin) we had to +00:59 (@hwoarang) brakeages? +00:59 (@yngwin) it broke stuff all over the place +00:59 (@hwoarang) right +01:00 (@hwoarang) i cant understand how +01:00 (@hwoarang) since src_install is always overriden +01:00 (@yngwin) so i do want that back in, but we need it in a separate eclass, so existing ebuilds can be migrated slowly +01:00 (@hwoarang) but lets play it safe +01:00 (@hwoarang) ok +01:00 (+Pesa) isn't it possible to have a drop-in replacement? +01:00 (@hwoarang) meaning? +01:01 -!- smorg [n=quassel@75-168-239-242.mpls.qwest.net] <- quit ["http://quassel-irc.org - Chat comfortably. Anywhere."] +01:01 (+Pesa) a revised qt4.eclass, but maintaining backward compatibility +01:01 (@yngwin) no, because we require eapi-2 and have new default functionality such as src_configure in there +01:01 (@hwoarang) we cant +01:01 -!- smorg [n=quassel@75-168-239-242.mpls.qwest.net] joins -> #gentoo-kde +01:01 (@hwoarang) how about maintain eqmake4 on qt4.eclass and inherit that eclass on the new one? +01:02 (@hwoarang) just to avoid mantaining 2 eqmake4 +01:02 (@yngwin) hmm, i dont like the added level of complexity +01:02 (+Pesa) i agree with yngwin +01:03 -> hwoarang is thinking +01:03 (+spatz) is qt4-edge to be merged as-is? at least the translations stuff seems broken on many packages and fixing after merge can be problematic +01:03 (+Pesa) it'd be better to have a eqmake4.eclass inherited by both the new and the old qt4 eclasses +01:03 (@hwoarang) the translations part is experimental +01:04 (+Pesa) spatz: i don't think so +01:04 (@hwoarang) yngwin: cant we open a tracker +01:04 (@hwoarang) about the brakeages? +01:04 (+spatz) Pesa: which part? +01:04 (@yngwin) what breakages? +01:04 (@hwoarang) which are caused by the new eclass? +01:05 (@hwoarang) in case we push it as qt4.eclass +01:05 (+Pesa) spatz: well, src_configure() needs improvements imho +01:05 (@yngwin) only if we dont touch the original eclass, we can't break stable stuff +01:06 (@hwoarang) introducing the default src_configure and src_install will brake some packages +01:06 (@hwoarang) we can track them on bugzilla +01:06 (@hwoarang) on a special tracker +01:06 (@yngwin) what i propose is to add the new eclass, and mark the old one as deprecated and make a tracker for migration to new eclass +01:06 (+Pesa) yeah +01:06 (@tampakrap) ^^nice +01:06 (+wired) yngwin++ +01:07 (+wired) qt4-v2.eclass? +01:07 (@hwoarang) nah +01:07 (@hwoarang) we need a pretty cool name +01:07 (@hwoarang) :P +01:07 (@yngwin) we had qt4-ng in mind +01:07 (@hwoarang) -ng sounds ok +01:07 (+wired) keep in mind one day we might have another big-bad-ass revision +01:07 (+wired) lets stick a number in there +01:07 (@yngwin) yeah, so i'm open for suggestions +01:07 (@tampakrap) qt4-r1.eclass? +01:07 (+wired) -r1 isn't bad either +01:08 (@yngwin) inherit qt4-r1 +01:08 (@hwoarang) nah +01:08 (@hwoarang) ugly +01:08 (@hwoarang) :P +01:08 (@yngwin) i'm not sure i like that +01:08 (+wired) i prefer qt4-v2 +01:08 (+wired) inherit qt4-v2 +01:08 (kage-ookami) qt4-2nd +01:08 (@yngwin) qt4-edition2009 +01:08 (@hwoarang) .. +01:08 (@yngwin) just brainstorming +01:08 (+spatz) qt4-home_premium +01:08 (@tampakrap) qt4_pre20090521 +01:08 (+wired) lol +01:08 (@yngwin) well, that's bikeshedding, can be done tomorrow +01:09 (+wired) qt4-try2 +01:09 (+wired) :D +01:09 (@hwoarang) ok +01:09 (@tampakrap) qt4_thepreviousonewasFAIL +01:09 (@yngwin) but we agree on principle? +01:09 (@tampakrap) yes +01:09 (+wired) i think its the best approach yeah +01:09 (@hwoarang) ok +01:09 -!- joost_op [n=joost@86.92.194.222] <- quit ["Leaving"] +01:09 (+Pesa) i do, if my opinion counts +01:09 (@yngwin) it does :) +01:09 (@hwoarang) also Pesa and me are working on eqmake4 patch, to automatically guesses the project name so we can have a more generic src_configure +01:09 (@yngwin) translation stuff still needs work? +01:10 (@hwoarang) yes +01:10 (+Pesa) can be made more generic i think +01:10 (@hwoarang) i have two ebuilds that I still want to migrate on that +01:10 (@yngwin) ok, so lets work on it in overlay, and see in a few weeks time or so +01:10 (@hwoarang) Pesa: i ll add the second patch, then feel free to play :) +01:11 (@yngwin) anything about other packages in overlay? +01:11 (@hwoarang) the current status seems ok +01:11 (+Pesa) hwoarang: with '.' instead of ${S} though! +01:11 (@tampakrap) i can take care of live ones +01:11 (@hwoarang) yes :) +01:11 (@hwoarang) i ve moved many packages on tree +01:11 (@hwoarang) and kept the live ones +01:11 (+Pesa) fine then +01:12 (@yngwin) what about qtjambi +01:12 (@yngwin) shouldnt that go to tree as well? +01:12 (@yngwin) 4.5.0 that is +01:12 (+Pesa) i added 4.5.0_p1 to the overlay +01:12 (@hwoarang) does it work? +01:12 (@hwoarang) or it needs further testing +01:12 (+Pesa) worksforme :D +01:12 (@yngwin) it's java, how would i know if it works? +01:12 (+wired) lol +01:12 (@yngwin) :p +01:13 (+wired) yngwin: actually the correct answer would be +01:13 (@hwoarang) so what can we do with it +01:13 (+wired) its java, ofcourse not +01:13 (+Pesa) seriously, it has huge improvements over portage version +01:13 (+wired) :D +01:13 (@yngwin) who maintains it in portage again +01:13 -!- bschindler [n=quassel@77-56-156-71.dclient.hispeed.ch] <- quit [Read error: 110 (Connection timed out)] +01:14 (@hwoarang) !meta -v qtjambi +01:14 (Willikins) hwoarang: Package: dev-java/qtjambi Herd: qt, java Maintainer: qt, java +01:14 (@hwoarang) we do +01:14 (@hwoarang) :P +01:14 (+wired) lolz +01:14 (@dagger) lol ;) +01:14 (@yngwin) ali_bush it seems from changelog +01:15 (@yngwin) ok, maybe confer with him +01:15 -> hwoarang noted +01:15 (@yngwin) then we can bump +01:15 (@hwoarang) i ll poke him as long as he is available +01:15 (@hwoarang) *as soon as +01:15 (@hwoarang) stupid beer +01:16 (@yngwin) heh +01:16 (@jmbsvicetto) ok, I really need to leave now. See you later +01:16 -!- Guest36992 [n=red@lounge.datux.nl] <- quit [Read error: 60 (Operation timed out)] +01:16 (@hwoarang) bye bye jmbsvicetto +01:16 (@yngwin) ok, see you jmbsvicetto +01:16 -!- sean345 [n=quassel@c-76-105-5-254.hsd1.ca.comcast.net] joins -> #gentoo-kde +01:16 (+wired) bye jmbsvicetto +01:16 (@hwoarang) ok i think we are done with the overlay +01:16 (@yngwin) on to last point? +01:16 (+Pesa) bye jmbsvicetto +01:16 (ali_bush_work) you talking to me :) +01:16 (+spatz) have fun :) +01:16 (@hwoarang) ah +01:16 (@hwoarang) there he is +01:16 (@yngwin) ali_bush_work: yes, we have qtjambi-4.5.0_p1 in overlay +01:17 (ali_bush_work) cool. does it work +01:17 -!- Guest36992 [n=red@lounge.datux.nl] joins -> #gentoo-kde +01:17 (@hwoarang) lol :) +01:17 (@yngwin) [00:12:52] it's java, how would i know if it works? +01:17 (@yngwin) ;) +01:17 (@yngwin) but Pesa says it does +01:18 (ali_bush_work) i'll put it on my todo list :) +01:18 -!- anselmolsm [n=anselmo@200.184.118.130] <- quit [Remote closed the connection] +01:18 (@yngwin) alright +01:18 (ali_bush_work) ETC next century +01:18 (@hwoarang) goodie +01:18 (@hwoarang) no rush :P +01:18 (+Pesa) ali_bush_work: yes, demos and examples work, and also qtdesigner integration +01:18 (@yngwin) we can bump, and let you deal with the bugs :p +01:19 (@yngwin) but if Pesa says it works, i trust him +01:19 (+Pesa) ali_bush_work: and there are tons of other improvements +01:19 (ali_bush_work) ok cool. I will qa the ebuild just too make sure if follows our standards +01:20 (@hwoarang) sweet +01:20 (+Pesa) thanks +01:20 -!- geo27 [n=quassel@lns-bzn-56-82-255-250-237.adsl.proxad.net] <- quit [No route to host] +01:20 (@hwoarang) ok last topic +01:20 (@hwoarang) leader? :/ +01:20 (@yngwin) do we need an elected lead? +01:20 (@hwoarang) what for +01:20 (@yngwin) now that we're a fast growing team +01:21 (@tampakrap) jmbsvicetto is the project leader, scarabeus is KDE HT Lead and yngwin is Qt HT lead +01:21 (@yngwin) well, i thought i would put it before you +01:21 (@tampakrap) i think that is enough +01:21 (@hwoarang) i cant see the reason :) +01:21 (@yngwin) because i just assumed the position, when no-one was looking +01:21 (@hwoarang) i am pretty happy with the current situation +01:22 (@hwoarang) maybe we should discuss it again in July +01:22 (@yngwin) but if you guys are happy with it +01:22 (@hwoarang) before we leave +01:22 (kage-ookami) yngwin: sometimes it takes a person to just assume the position +01:22 (@yngwin) i know +01:23 (@hwoarang) so the answer is NO +01:23 (+spatz) if it works don't fix it +01:23 (@hwoarang) you ll stay the leader either you like it or not +01:23 (@yngwin) ok +01:23 (@hwoarang) +01:23 (+wired) yngwin QT leader woot =] +01:23 (@scarabeus) :D +01:23 (@yngwin) +01:23 (@scarabeus) okey +01:23 (@scarabeus) :D +01:23 (@hwoarang) ------------------- +01:23 (+Pesa) :D +01:23 (@hwoarang) omg +01:24 (@hwoarang) 3:30 hours +01:24 (@hwoarang) jesus! +01:24 (@yngwin) holy mother +01:24 (+wired) closer to 3 hours actually +01:24 (+spatz) back to homework :/ +01:24 (+wired) but still! +01:24 -> yngwin hands out more cookies +01:24 (+wired) scarabeus: you want log? +01:24 (@yngwin) wired: CC me as well please +01:24 (@tampakrap) does it need rendering? +01:25 (@yngwin) i'll do summary for Qt part +01:25 (@hwoarang) ohhhhhhhhhhhhhh +01:25 (@hwoarang) btw +01:25 (@hwoarang) for those who havent noticed +01:25 -!- tampakrap topic of #gentoo-kde ->> Gentoo KDE | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU +01:25 (@hwoarang) i ve wrote this guide http://www.gentoo.org/proj/en/desktop/kde/qt4-based-ebuild-howto.xml +01:25 (@hwoarang) so any additions etc are welcomed diff --git a/meeting-logs/20090618-summary.txt b/meeting-logs/20090618-summary.txt new file mode 100644 index 0000000..1a7b140 --- /dev/null +++ b/meeting-logs/20090618-summary.txt @@ -0,0 +1,51 @@ +Rollcall: +yngwin, scarabeus, tampakrap (delayed), hwoarang, spatz, Pessa, alexxy, reavertm, wired, patrick, jmbsvicetto (late) +Carlo: slackermark + +Topics: + +Formulate some kind of official policy for qt3 apps and their future +- Qt3 apps will follow the KDE3 example and will share one overlay for the stuff with it. Users will maintain it. +- Addition to main tree of new Qt3 apps is *highly* discouraged. +- Qt3 useflag is being marked as discouraged (removal from profiles and so on) since NOW :] +- A draft with ideas for it will be sent to the -dev ml by yngwin + +Solving the python issues within KDE4 - currently with +kdeprefix KDE 4.2 and 4.3 can't live next to each other due to packages installed into site-packages for python. +- the issues running new pykde with old pykde using apps must be tested (pykde from 4.3 and python apps from 4.2) +- if above test prove not working, KDE misc apps will be forced to look into slotted dir in site-packages folder +- will be done by reavertm and patrick +- this issue is a stabilisation blocker + +Solving the final question about kdeprefix. +- voting about kdeprefix mask in profiles (users can still unmask it, but kde is not as solid as with -kdeprefix) +For this vote our HT reavertm was allowed to vote since he is one of the few whom spent their time on it and are capable of handling kdeprefix. +reavertm = mask +scarabeus = mask +jmbsvicetto = can live with mask +patrick = abstain +alexxy = mask +- outcome was that it will be masked in profiles. +- alexxy will add the mask and adjust the guide. + +Handle the PyQt3 qscintilla dependencies +- it seems that the Qt team has not decided if there is an issue or not. :P +- it will probably be mostly fixed by removal of Qt3 from profile. See topic no. 1. +- amarok will have python useflag removed and needed scripts will be removed +- introduce blocker between PyQt and PyQt4 + +KDE 4 Stabilisation. +- Jorge decided to target 4.2 for stabilisation. +- stabilisation bug will have to be opened +- tracking bug will have to be opened and bugs wrangled (volunteers??) + +Review the useflags we enable by default in Qt herd +- rename gtkstyle to gtk in qt-gui +- drop IUSE defaults for useflags enabled by desktop profiles + +Progress of KDE3 mess and way how anyone can help (here we call even for non-kdeteam devs) +- KDE3 misc apps are slowly moving forward + mail to dev asking for help :] +- arts flag removal is also slowly moving + (scarabeus will remove optional dep on arts by blocking it in eclass if scarabeus get some time, or anyone else can do it) + mail the dev ml announcing its death, and asking maintainers for cooperation. +- mail the dev ml announcing we need some KDE3 dedicated dev diff --git a/meeting-logs/20090618.txt b/meeting-logs/20090618.txt new file mode 100644 index 0000000..96f0650 --- /dev/null +++ b/meeting-logs/20090618.txt @@ -0,0 +1,1064 @@ +Note: times are UTC+2 + +[20:59.03] *** Topic is 'Gentoo KDE | 18.6. @ 19:00 UTC = Meeting [http://dev.gentoo.org/~scarabeus/0906meeting_topics.txt] | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 ' +[20:59.03] *** Set by scarabeus on Thu Jun 18 20:40:41 +[20:59.04] but if you listen, we'll have to kill you +[20:59.07] it's custom the ops get to kick everyone except club members out when the meeting starts +[20:59.08] :P +[20:59.11] be ready.. +[20:59.33] the meeting starts with a customery kick-banning +[20:59.54] *** BCMM (n=bcmm@unaffiliated/bcmm) has joined #gentoo-kde +[21:00.01] and when the channel's empty, the discussion can begin +[21:00.35] meeting starts ;] +[21:00.39] !herd kde +[21:00.41] (kde) alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, patrick, scarabeus, tampakrap, tgurr +[21:00.42] !herd qt +[21:00.42] scarabeus: (qt) carlo, hwoarang, tampakrap, yngwin +[21:00.44] rollcall plz +[21:00.48] present +[21:01.16] tampakrap will be one hour late so his topic is last on the list (FTR) +[21:01.32] he might not make it +[21:01.35] carlo is absent as usual +[21:01.36] called me 3 hours ago +[21:01.41] hi btw +[21:02.06] and hi from here :) +[21:02.13] haavardw: ping +[21:02.17] hi hwoarang, yngwin, ayoy +[21:02.20] *** scarabeus sets mode: +v ABCD +[21:02.22] hwoarang: pong, I'm here -) +[21:02.25] goodie +[21:02.33] your recruits? ;] +[21:02.34] yngwin: ps, remember to set him up on qting-edge +[21:02.34] and hi haavardw +[21:02.41] hi all +[21:02.46] i wander one thing +[21:02.50] where the ... is the rest +[21:02.58] howdy +[21:03.01] aparently only qt is present +[21:03.08] heh +[21:03.21] ok, mask kde for removal; done +[21:03.26] :D +[21:03.27] *** BCMM (n=bcmm@unaffiliated/bcmm) Quit (Remote closed the connection) +[21:03.29] you failed +[21:03.29] LOL +[21:03.31] :p +[21:03.37] we'll rule the world +[21:03.43] meeting's over +[21:03.43] bonsaikitten: still arround i assume ;] +[21:03.51] actually i'm on kde 4.2.4 presently +[21:03.57] woooooooooow +[21:04.03] big step +[21:04.05] sabayon +[21:04.07] * alexxy here +[21:04.08] *** scarabeus sets mode: +v Sput +[21:04.22] *** hwoarang sets mode: +v ayoy +[21:04.24] *** scarabeus sets mode: +v lxnay|two +[21:04.29] *** hwoarang sets mode: +v haavardw +[21:04.42] *** hwoarang sets mode: +v Pesa +[21:04.43] *** yngwin sets mode: +v hwoarang +[21:04.51] ;) +[21:05.04] * scarabeus gives them 5 minutes, then he will be seriously unhappy +[21:05.11] lol +[21:05.41] who do we miss? +[21:05.43] jorge? +[21:05.46] tampakrap_: is off +[21:05.51] bonsaikitten: slacking +[21:05.54] !herd kde +[21:05.56] yngwin: (kde) alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, patrick, scarabeus, tampakrap, tgurr +[21:05.57] so pretty much everybody is here +[21:05.58] I almost forgot +[21:06.03] dagger +[21:06.05] reavertm: hello +[21:06.11] hi scarabeus +[21:07.03] hwoarang: well specialy when we vote on first topic it would be damn nice to have majority of kde devs here +[21:07.17] where is the agenda +[21:07.21] topic +[21:07.27] so for those who hadnt noticed yet, we have two new qt recruits present: ayoy and haavardw +[21:07.36] *** Skim[ihz] (n=skim@skim.static.corbina.ru) has joined #gentoo-kde +[21:07.40] yngwin: voice them +[21:07.50] hwoarang already did +[21:07.51] they are voiced +[21:07.56] ah +[21:07.57] :] +[21:07.58] of course +[21:07.59] didnt look :] +[21:08.00] * haavardw can talk +[21:08.04] bla bla +[21:08.10] ayoy, haavardw: then welcome guys :] +[21:08.17] thank you! +[21:08.20] :) +[21:08.24] thanks -) +[21:08.33] http://archives.gentoo.org/gentoo-desktop/msg_1ef792a71171a444d60ecb870a27e9f3.xml <- agenda +[21:08.41] http://dev.gentoo.org/~scarabeus/0906meeting_topics.txt +[21:08.45] just for the record +[21:09.02] yes +[21:09.09] scarabeus: we can change the topics order +[21:09.21] hwoarang: yes we can +[21:09.23] until kde devs are here +[21:09.34] but kde3 is last or at least until tampakrap show up +[21:09.35] we can start with qt topics if you like +[21:09.49] ok scarabeus . but as I said he mgiht not make it +[21:09.49] :/ +[21:10.04] then wired will be his replacement +[21:10.08] sweet +[21:10.11] where is he +[21:10.11] he hopefully tracked him +[21:10.17] wired: stupid boy +[21:10.29] ping pong +[21:10.31] i foresee that they blame the late announcement :p +[21:10.37] im here +[21:10.39] excuses +[21:10.41] for some weird reason +[21:10.43] :p +[21:10.53] ok shall we start with qt stuff then? +[21:11.11] ok lets start with the qt3 apps first +[21:11.14] I'm fine with this +[21:11.18] and ftr i am really not happy +[21:11.34] slackers +[21:11.38] ok what about the qt3 apps? +[21:11.49] btw, who's going to vote on kdeprefix? +[21:11.55] kde project devs +[21:11.58] i guess +[21:11.59] reavertm: devs, including you +[21:12.09] * alexxy +[21:12.13] reavertm: because you are one of few who can work on it +[21:12.30] * alexxy gonna vote for masking it +[21:12.33] well, last time it was not the case :P +[21:12.36] hwoarang: so lets start with second topic now +[21:12.42] ok +[21:12.53] yngwin: ping pong +[21:13.09] kde3 is scheduled to be removed early next year, right? +[21:13.15] yes +[21:13.20] to some special overaly +[21:13.25] so lets create one common overlay +[21:13.26] and kde3 is the biggest consumer of qt3 +[21:13.29] kde3 and qt3 crap +[21:13.36] instead of just ripping it off +[21:13.40] i agree +[21:13.44] and users can maintain themselves if they want +[21:13.44] fine by me +[21:13.48] otherwise we can throw it +[21:13.59] I wouldn't mind creating special overlay for qt4 and kde4 crap :P - to keep them away from main tree "{ +[21:14.11] oooh flamebite +[21:14.13] what about kde3/qt3 apps not yet ported to kde4/qt4? +[21:14.14] ok whom would update the kde team page reffering to the policy +[21:14.24] spatz: problematic, but hell for maintaining +[21:14.25] spatz: we dont care :) +[21:14.34] yngwin: hwoarang ^ +[21:14.38] the update... :] +[21:14.40] but some are widely used, like k3b +[21:14.42] scarabeus: do we need to update it? +[21:14.47] for what +[21:14.58] by users +[21:15.06] ping :) +[21:15.08] some of them fail to build with libpcre[-static-libs] +[21:15.09] i would like to propose that we officially discourage further usage of qt3: dont introduce new qt3 based apps, prefer qt4 over qt3 +[21:15.11] i hope k3b will see a stable release before the end of this year +[21:15.12] hwoarang: just that other knows +[21:15.17] spatz: k3b has already a kde4 version +[21:15.19] _alpha +[21:15.28] yngwin: good idea +[21:15.32] yngwin: +1 +[21:15.37] spatz: in 6 months ;] +[21:15.49] tanderson: ? +[21:15.57] i think qt3 useflag is enabled by desktop profile? that should be removed +[21:16.18] also good idea, but since when +[21:16.21] Any objections to me patching a kde 3 ebuild with fixes for the .desktop file ? +[21:16.27] tanderson: enjoy +[21:16.28] or JustDoIt ? :) +[21:16.37] tanderson: open kde.gentoo.org +[21:16.42] tanderson: search for CODE file +[21:16.45] tanderson: read it +[21:16.48] tanderson: answer is there +[21:16.59] * bonsaikitten present +[21:17.03] yngwin: aka when we switch the discouraging of qt3 useflag +[21:17.17] it can be even now but apps will be gone in the feb of 2010 +[21:17.21] i'd say immediately +[21:17.33] still we need to make the transission smooth +[21:17.38] scarabeus: aah ok +[21:17.40] i failed on spelling +[21:17.41] hmmm +[21:17.51] scarabeus: oh, did I interrupt your meeting? +[21:17.52] so as yngwin said , immediately +[21:17.57] tanderson: smart boy +[21:18.03] *** dipogon (n=dipogon@84.249.84.164) Quit (Remote closed the connection) +[21:18.09] tanderson: ;] +[21:18.12] qt3 is enabled in /usr/portage/profiles/targets/desktop/make.defaults +[21:18.13] scarabeus: I'm sorry, I'd have taken it to a query if I had known +[21:18.22] tanderson: no prob :] +[21:18.56] hwoarang: ok since you two agree just do it, i wrote it in summary :] +[21:19.02] ok +[21:19.09] afaik profile changes need announcement/discussion on dev ml, so i'll draft up something +[21:19.18] thanks yngwin +[21:19.34] it is strange, but I can't add my own language in system settings... l10n is installed, kde installed without "kdeprefix", some software is translated, but I still can't add my own language.... ;( +[21:19.40] Skim[ihz]: meeting time +[21:19.58] * scarabeus consider +m ;] +[21:20.03] -_- +[21:20.07] we can voice pple if they query us +[21:20.09] sorry +[21:20.10] stop considering +[21:20.17] just do it already +[21:20.18] *** scarabeus sets mode: +m +[21:20.20] :D +[21:20.22] should be done +[21:20.25] ok +[21:20.33] end of story +[21:20.44] scarabeus: moving forward? +[21:20.48] okey +[21:20.51] kde4 stabilization? +[21:21.01] bonsaikitten: patrick since you are here, can we talk about the pykde? +[21:21.10] we can +[21:21.21] *** gengor (n=gengor@gentoo/developer/gengor) has left +[21:21.41] you agreed to deprecate qt3 as of now, so i assume discussion on moving current packages to an overlay will be postponed? +[21:21.42] it is 5th topic for those whom wonder +[21:21.50] scarabeus: voice tanderson +[21:21.52] spatz: yes +[21:21.54] *** scarabeus sets mode: +v tanderson +[21:22.32] bonsaikitten: ok did you find any solution about the collisions in site-packages? +[21:22.42] not yet, but I haven't spent much time on it +[21:22.54] unprefixing of pykde is fine with us, but the issue is also in plasma-workspace now +[21:22.58] or plasma-addons not sure now +[21:23.11] either we allow to use a newer pykde with an older slotted kde (does that work?) +[21:23.20] (with python USE flag only) +[21:23.24] or we try to move the pykde package to versioned directories +[21:23.36] it's all depending on kdeprefix status +[21:23.37] but then packages trying to use it will most likely need some patching +[21:23.59] bonsaikitten: cant we somehow eselect correct site modules for what kde we start +[21:24.01] (no kdeprefix - no pytkde issue) +[21:24.20] *** pgega (n=pgega@77-99-66-168.cable.ubr01.tonb.blueyonder.co.uk) Quit (Client Quit) +[21:24.22] scarabeus: potentially yes, but might be very fragile +[21:24.34] eselect is not the answer here +[21:24.43] and as reaver say, if we agree we can just mask kdeprefix flag, which will be voted +[21:24.50] because without this the kde cant be stabled +[21:24.55] the collision would piss users +[21:24.56] anyway - either unslot or eselect - pykde4-9999 is likely to not work very well with kdelibs-4.2 +[21:24.57] someone still might want to run amarok1 in kde4 for example +[21:25.22] *** haavardw (n=haavardw@cm-84.208.110.202.getinternet.no) Quit (Read error: 104 (Connection reset by peer)) +[21:25.23] right, so we need versioned dirs in site-packages +[21:25.31] how many packages depend on pykde ? +[21:25.40] everything in kde with use python +[21:25.49] yngwin: I don't see it relevant (amarok1) +[21:25.58] (as it uses kdelibs3) +[21:26.06] and pykde3 +[21:26.07] I'm aware of marble plasma-workspace +[21:26.10] any others? +[21:26.10] *** haavardw (n=haavardw@cm-84.208.110.202.getinternet.no) has joined #gentoo-kde +[21:26.26] printing stuff +[21:26.30] (upcoming in 4.3) +[21:26.50] + guidance-power-manager (extragear) +[21:27.01] ok, tolerable amount to patch +[21:27.19] *** pgega (n=pgega@77-99-66-168.cable.ubr01.tonb.blueyonder.co.uk) has joined #gentoo-kde +[21:27.29] I don't worry about API differences here, rather ABI issues +[21:27.34] *** scarabeus sets mode: +v haavardw +[21:28.08] reavertm: the only thing that will suffer is the detection by other packages afaict, so we will have to frickel them to accept the changes +[21:28.22] besides nobody really tried yet mixing new pykde4 with 'old' apps (and we're preventing it so far) +[21:28.22] so if we have to tweak 5 packages that's an acceptable amount of work +[21:28.30] *** Phlogi_ (n=quassel@236-60.77-83.cust.bluewin.ch) Quit (Read error: 60 (Operation timed out)) +[21:29.12] (I guess we don't plan to support older pykde4 with newer apps - so just SLOT deps would be dropped if any) +[21:29.18] *** bertodsera (n=quasseul@95.133.248.44) has joined #gentoo-kde +[21:29.45] anyone willing to help? +[21:29.50] maybe you should test backwards compatibility of newer pykde4 then, as that would prevent the need for patching +[21:29.56] I did it partially in local branch +[21:30.43] Hi +[21:30.47] hey boss +[21:30.49] I'm sorry for being late +[21:31.16] yngwin: right, that will be annoying to test :) +[21:31.27] bonsaikitten: so you and reaver will do it +[21:31.43] *** Phlogi (n=quassel@10-175.0-85.cust.bluewin.ch) has joined #gentoo-kde +[21:31.49] ? +[21:31.52] *** scarabeus sets mode: +v Phlogi +[21:31.59] *sigh* :) +[21:32.06] I'll try to have a look on the weekend +[21:32.07] i take it as yes :] +[21:32.44] ok +[21:32.55] anything else to this topic? +[21:33.07] jmbsvicetto: o hi, i missed ya ;] +[21:34.09] ok, since there wont be more devs here around and since alexxy has pretty late hour i would like to go with his kdeprefix stuff +[21:34.12] alexxy: please +[21:34.22] the topic Solving the final question about kdeprefix. +[21:34.45] well +[21:35.34] One thing: I as a amd64 person won't let kde4 go stable on my architecture with kdeprefix available to my users +[21:35.49] :) +[21:36.01] he he =) +[21:36.03] It causes far too many problems +[21:36.08] tanderson: don't make us go behind your back ;) +[21:36.18] you even don't know about one problem I know of :P +[21:36.20] so kdeprefix will cause many headache to users +[21:36.27] it does already +[21:36.28] bonsaikitten: to whom? +[21:36.29] so lets mask it! +[21:36.29] (qt4 bug related to plugin loader) +[21:36.29] =) +[21:36.35] also the python issue +[21:36.42] plugin loader i personaly HATE +[21:36.49] tanderson: well, let me put it this way - you're not the only one on amd64 with a commit access ;) +[21:37.01] bonsaikitten: if we will mask it +[21:37.12] user can still unmask it +[21:37.17] people who want to use still can do it after unmasking +[21:37.19] and we already state it deemed evil +[21:37.20] bonsaikitten: I think I represent the others on my team +[21:38.01] :] +[21:38.03] scarabeus: I noticed in the back log ;) +[21:38.13] ok i think we should vote on it +[21:38.19] and if the vote will be keep unmasked +[21:38.30] the voting devs must promise to work on the issues with +kdeprefix +[21:38.34] aka they will focus on them +[21:38.42] not that I with -kdeprefix would fix them +[21:38.51] objections? +[21:39.06] tanderson: You're forgetting that you can even mask a use flag in a profile ;) +[21:39.20] tanderson: so you could always stable kde4 *without* kdeprefix +[21:39.34] jmbsvicetto: I am aware of that +[21:39.37] tanderson: and we're not voting on removing kdeprefix - but masking in profiles +[21:39.51] (as most of devs will unmask it anyway) +[21:39.51] why not just remove it? +[21:40.01] I never mentioned removing kdeprefix! I mentioned "being available to my users" +[21:40.04] because we use live and stable right now +[21:40.04] :) +[21:40.10] yngwin: aside +[21:40.11] scarabeus / reavertm: what issues do you want to fix by masking it? +[21:40.15] with help of +kdeprefix +[21:40.27] The pykde conflict and? +[21:40.28] jmbsvicetto: update strategy, collisions, broken plugins, user confusion +[21:40.39] jmbsvicetto: just decrease ^^^ impact on average users +[21:41.08] ok, I've became tired of fighting this war +[21:41.23] I'll let anyone else take this one if they want +[21:41.39] i would more of like to convince you rather than tire you :] +[21:41.44] But, just for the record, my +kdeprefix laptop is working fine :P +[21:42.06] jmbsvicetto: yeah because me and reaver spent quite stuff on prefix stuff, and it is still not 100% +[21:42.07] :] +[21:42.16] scarabeus: As I've said before, the real solution is to fix upstream build system to allow co-existence of different versions side by side +[21:42.18] fist stuff was to be time +[21:42.23] jmbsvicetto: you're free to go with +kdeprefix if you fix qt plugin loader to not pick oxygen.so from current kde session (and plugin cache stored in .config/Trolltech.conf) instead of using kde4-config --qtplugins +[21:42.25] yes on that i agree +[21:42.41] jmbsvicetto: well we wont remove it +[21:42.42] jmbsvicetto: that's no longer build system issue +[21:42.44] just mask in profile +[21:42.47] anyone can enable it +[21:42.50] scarabeus: this way someone might feel "pressured" to start that work ;) +[21:42.58] they can coexist +[21:43.09] there's problem with plugin loader +[21:43.14] jmbsvicetto: yeah it might motivate pple to work on it so it will get unmasked +[21:43.14] reavertm: I mean having them on the same dir, not on separate prefixes +[21:43.17] and of course with .desktop files +[21:43.33] ok guys we are far away from the subject +[21:43.35] (they all have relative paths in Exec=) +[21:43.36] it is mask/not mask +[21:43.46] * jmbsvicetto abstains +[21:44.01] in current state kdeprefix is NO GO +[21:44.21] one can not like it, but this is the fact +[21:44.25] jmbsvicetto: you cant you are lead :D +[21:44.31] ok please +[21:44.34] !herd kde vote +[21:44.39] !herd kde +[21:44.40] bonsaikitten: what about you? +[21:44.48] i hate that bot +[21:44.50] seriously +[21:44.51] scarabeus: Willikins doesn't have +v +[21:44.53] scarabeus: give me a minute +[21:44.55] rotfl +[21:44.57] *** scarabeus sets mode: +v Willikins +[21:44.57] *** jmbsvicetto sets mode: +v wired +[21:44.57] I've spent already too many hours working on it - if anyone doesn't like it, I'll be happy to pass the work to him +[21:44.59] !herd kde +[21:44.59] (kde) alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, patrick, scarabeus, tampakrap, tgurr +[21:45.04] O;] +[21:45.13] scarabeus: Yeah, blame the bot ;) +[21:45.15] jmbsvicetto: I prefer kdeprefix, but I don't care enough to fight for it +[21:45.20] ok +[21:45.26] i vote the mask +[21:45.39] scarabeus: How do you plan to mask it? +[21:45.40] i vote for mask this crap! +[21:45.45] * wired votes on his dev bug +[21:45.48] :D +[21:45.50] jmbsvicetto: via use.mask +[21:45.55] globaly in profile in use.mask +[21:46.00] base/use.mask ? +[21:46.02] I vote to mask it (for now) +[21:46.03] yes +[21:46.14] Can users unmask it in /etc/portage ? +[21:46.18] yes +[21:46.19] yes +[21:46.21] as it should have been done at the same begin +[21:46.24] iirc, last time one would have to do it in profiles/ +[21:46.28] ok +[21:46.34] so it would still be available for those who really want it +[21:46.40] I can live with the mask then +[21:46.56] jmbsvicetto: to unmask, put "-kdeprefix" in /etc/portage/profiles/use.mask +[21:47.15] ABCD: ok, thanks +[21:47.15] ok somebody around whom didnt vote? +[21:47.22] ABCD: ssshh, users will hear it :P +[21:47.24] * jmbsvicetto notices Patrick didn't +[21:47.25] just make sure the whole thing is properly documented +[21:47.46] well the guide will be updated, at least tampakrap_ promised he will do it +[21:48.00] ABCD: it's profile, not profiles, IIRC +[21:48.07] ...right +[21:48.17] I blame my IRC client +[21:48.17] bonsaikitten: so say mask/notmask plz +[21:48.25] ;) +[21:48.50] directory name is profiles, but calling it 'profile' is common :P +[21:48.57] scarabeus: abstain +[21:49.04] *** himikof_ (n=himikof@129.167.249.ozerki.net) Quit (Read error: 104 (Connection reset by peer)) +[21:49.04] :DDDD +[21:49.06] reavertm: directory name is profie - I just checked +[21:49.06] ok +[21:49.14] profile* +[21:49.18] *** himikof_ (n=himikof@129.167.249.ozerki.net) has joined #gentoo-kde +[21:49.23] (ah, you mean the one in /etc/portage) +[21:49.28] yes +[21:49.34] it's profile +[21:49.37] ok then it will be masked in profiles +[21:49.38] nm, so results? +[21:49.40] per vote +[21:49.42] great :P +[21:49.58] alexxy: please do the change and according documentation update in the guide +[21:50.19] sweet +[21:50.31] Now I can stable kde with a clear conscience +[21:50.32] he he =) +[21:50.41] there should be information. about being unable to load oxygen.so and the need of wiping ~/.config/Trolltech.conf +[21:50.57] so tommorow i'll mask it via profile +[21:51.03] alexxy: okey +[21:51.05] and update guide +[21:51.06] =) +[21:51.10] so this topic is done :] +[21:51.17] * alexxy realy tired and gonna sleep +[21:51.24] next one because we ocupied 2 in the row is for qt herd +[21:51.29] topic: Handle the PyQt3 qscintilla dependencies +[21:51.31] (maybe remove all traces of kdeprefix from guide :) +[21:51.33] alexxy: gn +[21:51.44] yngwin: hwoarang ^ +[21:51.49] what about it? +[21:51.56] it is your topic +[21:51.58] messy +[21:51.59] no +[21:51.59] gn =) +[21:52.09] i guess the problem is sip and PyQt-3? +[21:52.11] nn alexxy +[21:52.16] nn alexxy +[21:52.18] Pesa: no +[21:52.27] pyqt3 requires qscintilla-python[-qt4] +[21:52.30] so what is the problem? +[21:52.36] whilst Pyqt4 requires qscintilla-python[qt4] +[21:52.41] no it doesnt +[21:52.47] sorry? +[21:52.48] :) +[21:53.05] PyQt4 does not hard depend on qscintilla +[21:53.15] indeed +[21:53.16] the other way around +[21:53.30] if any.. +[21:53.53] if some app needs qscintilla-python[qt4], yes then there will be a blocker +[21:54.07] *** SaCu (n=quassel@213-172-122-045.dsl.aktivanet.de) has joined #Gentoo-KDE +[21:54.08] this blocker does not exist right now +[21:54.47] sort of, as you can only have qt4 or -qt4 set on qscintilla-python +[21:54.55] so the problem is that you can't have both qt3 and qt4 qscintilla installed? +[21:55.00] ye +[21:55.01] indeed +[21:55.31] adding qscintilla-python[-qt4] on PyQt +[21:55.37] creates a kind of mess +[21:55.44] meaning you can only have PyQt and PyQt4 side by side as long as nothing needs qscintilla-python[qt4] +[21:55.47] well , a mess that users dont get it +[21:55.51] yes yngwin +[21:56.17] *** wilder (n=quassel@host126-104-dynamic.21-87-r.retail.telecomitalia.it) has joined #gentoo-kde +[21:56.22] now that qt3 is removed this should happen less frequently +[21:56.36] it's not removed +[21:56.46] spatz: this wont happen until 2010 +[21:56.49] it will be soon, i mean +[21:56.59] we will remove qt3 use flag from desktop profile and that is all +[21:57.05] removed from desktop profile +[21:57.17] ok +[21:57.28] but still , the blocker is there +[21:57.34] users can have qt3 on make.conf +[21:58.24] what's the problem here? python bindings collision? +[21:58.41] qt3 itself resides in separate prefix than qt4 +[21:58.52] no +[21:58.54] qscintilla-python is fine +[21:58.55] you can build qscintilla-python only for qt3 OR qt4 +[21:59.01] the problem is qscintilla iirc +[21:59.11] it's buildsystem doesn't allow that or what? +[21:59.28] file collisions +[21:59.48] the buildsystem is simply not designed to do that +[22:00.03] adjust the build system +[22:00.04] simple +[22:00.04] it may indeed by qscintilla itself, not the python bindings +[22:00.17] scarabeus: patches welcome +[22:00.33] guys it is your bug :D +[22:00.39] (a'ka gfy :) +[22:00.43] then i say: mask for removal :p +[22:01.15] it's qt3, it's deprecated, i dont want to waste time on it +[22:01.28] yngwin: well you are the boss +[22:01.34] yngwin: and if hwoarang agree... :] +[22:02.07] a real day issue is having amarok-1.4 and eric4 +[22:02.20] this sounds to me like the most common blocker +[22:02.25] there are just a few apps that use PyQt-3, most importantly amarok:3.5[python] +[22:02.28] *** jefferai (n=quassel@amarok/developer/mitchell) has joined #gentoo-kde +[22:02.30] yes +[22:02.38] amarok is the big pain atm +[22:02.48] and many many ppl are using it +[22:03.02] and what for are the python bindings +[22:03.10] scripts i suppose +[22:03.12] *** scarabeus sets mode: +v jefferai +[22:03.12] scripts afaik +[22:03.28] jefferai: by any chance you know how important are python bindings in amarok 1? +[22:03.32] hwoarang: amarok-1.4 can be deprecated after we get amarok-2 marked stable +[22:03.43] that will take a while +[22:03.48] indeed +[22:03.51] scarabeus: there are python bindings in amarok 1? +[22:03.59] :D +[22:04.20] guys this is statement from upstream dev +[22:04.21] :D +[22:04.28] so maybe we can mask python useflag in amarok-1* ? +[22:04.30] so i think when they dont care why should we :P +[22:04.37] well, I'd have to ask +[22:04.42] yngwin: yep that i was thinking about +[22:04.43] the fact that I'm not aware of them doesn't mean... +[22:05.03] jefferai: too late :P +[22:05.08] heh +[22:05.10] python masking sounds good to me +[22:05.12] that'll get more users annoyed than having problems with qscintilla, imo +[22:05.16] *** etix (n=etix@videolan/developer/etix) Quit (Remote closed the connection) +[22:05.18] *** etix (n=etix@nala.l0cal.com) has joined #gentoo-kde +[22:05.27] jefferai: too late, python use flag has already been taken to the alley and beaten up^Dmasked ;) +[22:05.30] or have the useflag renamed and disabled by default +[22:05.46] as globally python is enabled by profile +[22:05.48] what's this for? +[22:06.14] jefferai: some bindings probably :] +[22:06.19] hopefully just bindings +[22:06.30] oh +[22:06.31] jefferai: we have a conflict between dependencies of PyQt3 and PyQt4, and amarok-1 is the biggest consumer of PyQt3 it seems +[22:06.33] webcontrol +[22:06.42] bah +[22:06.46] I don't know of anyone using it +[22:06.50] at least, that I've ever heard +[22:07.02] it's some random script that allows web control of Amarok -- I guess +[22:07.17] *** genewbie (n=genewbie@cpe-76-172-51-77.socal.res.rr.com) has joined #gentoo-kde +[22:07.17] take a look in the ebuild -- just make sure you keep that rm for the webcontrol script in there +[22:07.24] so that people don't file bugs asking why it doesn't work/run +[22:08.08] we are still on the qscintilla topic? ;P +[22:08.23] yes +[22:08.35] :] +[22:08.36] okey +[22:08.51] *** pgega (n=pgega@77-99-66-168.cable.ubr01.tonb.blueyonder.co.uk) Quit (Client Quit) +[22:09.04] *** pgega (n=pgega@77-99-66-168.cable.ubr01.tonb.blueyonder.co.uk) has joined #gentoo-kde +[22:09.14] so i propose useflag s/python/webcontrol/ in amarok-1* ebuilds +[22:09.43] jmbsvicetto: ^ +[22:09.53] yngwin: I'd suggest dropping the python flag and removing the scrpit +[22:09.55] script* +[22:10.07] either way +[22:10.24] yngwin: I think we should start hinting that users should start moving to amarok-2 +[22:10.45] yeah 2.1 is already usable on same level i think +[22:10.55] as long as it's not stable... +[22:11.28] it will be next topic +[22:11.28] :D +[22:11.36] just finish with this one +[22:11.40] anyway, that will make things easier +[22:12.18] with that one done, what do we think of mutual blocking of PyQt and PyQt4 to prevent portage tripping over the deeper deps issue? +[22:12.28] *** gengor (n=gengor@gentoo/developer/gengor) has joined #gentoo-kde +[22:12.37] yep that is good idea +[22:12.40] yngwin: what apps will that mask? +[22:12.42] the block between them +[22:12.54] sorry guys, my connection is lagging a lot +[22:12.57] s/mask/cause slot blocks/ +[22:13.00] it won't mask anything, just force users to choose +[22:13.15] yeah, I meant what apps will be affected by that +[22:13.28] !rdep PyQt +[22:13.29] jmbsvicetto: Too many packages have reverse RDEPEND on dev-python/PyQt, go to http://tinderbox.dev.gentoo.org/misc/rindex/dev-python/PyQt instead. +[22:13.30] !rdep PyQt +[22:13.30] !rdep PyQt4 +[22:13.31] jmbsvicetto: Too many packages have reverse RDEPEND on dev-python/PyQt4, go to http://tinderbox.dev.gentoo.org/misc/rindex/dev-python/PyQt4 instead. +[22:13.31] yngwin: Too many packages have reverse RDEPEND on dev-python/PyQt, go to http://tinderbox.dev.gentoo.org/misc/rindex/dev-python/PyQt instead. +[22:13.37] :) +[22:13.44] *** tbeadle (n=quassel@division.aa.arbor.net) Quit (Client Quit) +[22:13.55] yngwin: sorry, feeling lazy today ;) +[22:14.06] kelogviewer, releaseforge, kanyremote +[22:14.07] no important crap expect amarok i think +[22:14.25] hmm, hplip :\ +[22:14.36] hplip also has qt4 option +[22:14.49] hplip has qt4 option (and I have it installed, so I know it works) +[22:14.58] yeah, sorry just noticed it +[22:15.02] i think there's a bug about the new hplip version not really having qt3 support +[22:15.23] he he +[22:15.24] :D +[22:15.50] *** wired|quassel (n=quassel@athedsl-290085.home.otenet.gr) has joined #gentoo-kde +[22:16.01] *** wired|quassel (n=quassel@athedsl-290085.home.otenet.gr) Quit (Client Quit) +[22:16.17] *** wired|quassel (n=quassel@athedsl-290085.home.otenet.gr) has joined #gentoo-kde +[22:16.40] jmbsvicetto: in case you didnt look yet: http://bugs.gentoo.org/chart.cgi?category=-All-&subcategory=-All-&name=320&label0=Kde-Charting&line0=591&datefrom=&dateto=&action-wrap=Chart+This+List +[22:16.41] so does anyone have anything against the blocker? +[22:16.48] no prob here +[22:16.51] *** Skim[ihz] (n=skim@skim.static.corbina.ru) Quit (Client Quit) +[22:16.56] it looks fine when i compared +[22:17.06] i am on board +[22:17.34] ok, let's do it then +[22:17.52] next topic :) +[22:18.02] okey qt team can touch the amarok for this one i assume ;] +[22:18.12] KDE 4 Stabilisation. +[22:18.15] quite big +[22:18.41] but the bugs are ok, and now we agreed masking the prefix useflag only thing that remains is the kde4 apps out of the kde4 session +[22:18.53] reavertm: how we are standing on that bug, i was not paying much attention to it lately +[22:19.02] scarabeus: hmm, should I get a chart? +[22:19.14] jmbsvicetto: yes for me it draws nice chart +[22:19.19] jmbsvicetto: open in anything else than FF +[22:19.28] and second thing is what version we will stable +[22:19.29] so it only fails on FF? +[22:19.30] 4.2 or 4.3 +[22:19.30] wow that is fail +[22:19.31] *** etix (n=etix@videolan/developer/etix) Quit (Client Quit) +[22:19.41] jmbsvicetto: yes +[22:19.42] I'd say it depends when we get it done +[22:19.53] For the next 2 months I would bet on 4.2.4 and or 4.2.5 +[22:19.59] jmbsvicetto: well i am testing the 4.2.91 and i am damn impressed +[22:20.02] they would work with kdeprefix if qt plugin loader wasn't affected - with -kdeprefix (and ~.config/Trolltech.conf wiped out) they are fine +[22:20.23] another issue is with kde3 .desktop icons in kde4 session +[22:20.38] scarabeus: Yeah, but it's too early for it +[22:20.42] the guys are really working their asses to make it nice +[22:20.43] currently nothing is shown (because nothing would work) +[22:20.49] well it will be in 1 month around +[22:20.58] scarabeus: I guess users that have been waiting for 2 years, can wait another month or two for 4.3 ;) +[22:20.59] and you'll have to wait a month to stabilize it +[22:21.00] also the printing dialog is tempting +[22:21.14] jmbsvicetto: ok should we vote on the thing or we agree +[22:21.19] reavertm: what do you think :] +[22:21.40] scarabeus: does that printing dialog work for you? +[22:21.46] reavertm: nope ;D +[22:21.47] I guess I'll make an "executive decision" on this one :P +[22:21.48] (crashes in my cheoot) +[22:21.54] it says that it hate me +[22:21.58] it cant chat with cups +[22:22.02] scarabeus: printing is deferred until fixed :P +[22:22.04] even tho i am able to print +[22:22.18] jmbsvicetto: okey so decide +[22:22.29] (so no go for system-config-printer-kde and printer-applet) +[22:22.30] jmbsvicetto: fine with me you are elected lead, so you choose global policy:] +[22:22.41] 4.2.[4|5] for the next 2 months - after that we can talk about 4.3 +[22:22.42] reavertm: they are already in the tree by accident ;DDD +[22:22.53] well, masked they can be +[22:22.58] reavertm: some looser already opened bug about it has missing deps ;D +[22:23.08] because movetocvs just grab everything with nice version :D +[22:23.08] good +[22:23.21] scarabeus: we should also open the bug asap +[22:23.26] jmbsvicetto: ok whom will handle stabling of 4.2 then +[22:23.57] *** ebola_ (i=ebola@S0106066606660666.su.shawcable.net) has joined #gentoo-kde +[22:24.01] what is blocking it? +[22:24.10] most of kde4 issues +[22:24.10] the above thng only +[22:24.11] *** Skim[ihz] (n=skim@skim.static.corbina.ru) has joined #gentoo-kde +[22:24.12] :P +[22:24.23] running the kde4 apps out of the kde4 session +[22:24.25] kde-print? +[22:24.28] ah +[22:24.29] but it should be addressed already +[22:24.30] also kdm crashes +[22:24.40] yeah kdm is weird crap with -O3 +[22:24.53] scarabeus: KDE has had issues with -O3 since ever +[22:25.01] without -O3 as well (but works with new user) +[22:25.02] scarabeus: If you look in bugzilla there were a few reports about that +[22:25.13] *** ebola_ (i=ebola@S0106066606660666.su.shawcable.net) has left +[22:25.16] reavertm: are you sure it's not a graphics driver issue? +[22:25.19] *** InvaderNOP (i=ebola@S0106066606660666.su.shawcable.net) has joined #gentoo-kde +[22:25.28] if it works with new user... +[22:25.41] yeah, hmm config option? +[22:25.46] like? +[22:25.55] *** Civil (n=Civilian@95-24-130-90.broadband.corbina.ru) Quit (Remote closed the connection) +[22:26.02] anyway, stabilization bug could be opened to track issues +[22:26.09] tracker bug +[22:26.13] let's open the tracker then +[22:26.15] 1 for tracking 2 for stabling +[22:26.17] personally I wouldn't hurry with stabilization +[22:26.23] but whom will wrangle the stuff +[22:26.31] i guess tampy wont do second round +[22:26.33] everyone :P +[22:26.33] :] +[22:26.55] I suppose you want someone with -kdeprefix O:-) +[22:27.02] *** andreax (n=andreaz@p57B951A2.dip.t-dialin.net) has joined #gentoo-kde +[22:27.24] GRM +[22:27.37] btw i noticed sabayon is on +kdeprefix +[22:27.38] i am definetly sure that i will still target on closing bug than on wrangling them +[22:27.41] I'd take commit count :D +[22:27.47] i am allways depressed about wrangling +[22:28.06] yngwin: 5.0 branch is -kdeprefix +[22:28.09] scarabeus: oh, looking at bugs? we can all do it +[22:28.16] remember that we cooperate at sabayon +[22:28.18] ok good +[22:28.26] s/at/with/ +[22:28.34] yes, thats why i mentioned it +[22:28.37] !seen joost-op +[22:28.39] scarabeus: nope! +[22:28.53] !seen joost_op +[22:28.54] scarabeus: joost_op was last seen 4 days, 45 minutes and 54 seconds ago, quitting IRC (Remote closed the connection) +[22:29.28] i already discussed with him about it :] +[22:29.31] so problem solved :] +[22:30.03] ok i think we have stuff that is needed to be done +[22:30.15] and i guess each of us can wrangle some itching bug +[22:30.25] i think everything above normal must be assinged there +[22:30.25] *** haavardw (n=haavardw@cm-84.208.110.202.getinternet.no) Quit (Remote closed the connection) +[22:30.33] and rest is up to our decision +[22:31.26] anything else to this topic? +[22:31.28] *** ABCD (n=ABCD@wikipedia/ABCD) Quit (Client Quit) +[22:31.32] *** ABCD (n=ABCD@wikipedia/ABCD) has joined #gentoo-kde +[22:31.37] hmm,m what about phonon? +[22:31.38] *** scarabeus sets mode: +v ABCD +[22:31.44] already stable +[22:31.46] it will be blocker for 4.3 I guess +[22:31.57] ah this +[22:32.07] it is not issue for 4.2 stable bug for now +[22:32.17] even if we might transcendent to 4.3 it can be address later +[22:33.34] ok since everyone is silent lets go with next topic +[22:33.37] topic: Review the useflags we enable by default in qt herd +[22:33.44] yngwin, hwoarang: ^ +[22:33.51] (and in kde as well :P) +[22:33.59] i think the +gtkdialog is FKHE#(*%$YU#HR$(*%W#URJTN stupid +[22:34.03] it pulls gtk +[22:34.07] and that pulls X +[22:34.10] on -X install +[22:34.15] gtktheme you mean? +[22:34.16] so instead of 17 deps you have 55 +[22:34.20] oh theme right +[22:34.38] gtkstyle +[22:34.45] ah +[22:34.54] what ever ;] +[22:35.14] but that's in qt-gui which needs X anyway +[22:35.25] :) +[22:35.49] *** bbroeksema (n=bbroekse@cust-02-5286b4cb.adsl.scarlet.nl) Quit (Remote closed the connection) +[22:35.57] there's another topic in the agenda about this btw +[22:36.01] we could rename that to gtk, so it only get enabled by default in desktop profile +[22:36.17] was just about to say that +[22:36.22] Pesa: which one +[22:36.31] review the useflags we enable by default in qt herd +[22:36.33] rename to gtk and not have it on by default +[22:36.38] *** B-Man1 (n=B-Man@cpe-098-024-241-139.ec.res.rr.com) Quit (Client Quit) +[22:36.45] Pesa: thats what we're discussing now +[22:36.52] *** B-Man (n=B-Man@cpe-098-024-241-139.ec.res.rr.com) has joined #gentoo-kde +[22:37.05] ha +[22:37.09] i failed +[22:37.09] :P +[22:37.17] i'm getting angry with my ISP +[22:37.33] do we really need to enable something by default? +[22:37.37] but gtk isn't the only issue, also dbus, glib, qt3support and others +[22:37.44] they're all enabled by default +[22:37.54] dbus is already on profile +[22:37.56] qt3support disable guys i think +[22:38.01] glib can be disabled too +[22:38.06] i live without the later +[22:38.15] i cant recall why glib is on +[22:38.16] and the former we demand on kde but otherwise it is not needed right? +[22:38.29] i think +[22:39.08] the default should be off by default unless there's a good reason, not the way it is right that almost everything is on by default, IMHO +[22:39.20] i'm talking about all qt-* useflags +[22:39.36] yes +[22:39.39] the reasoning why i enabled most of those is to have the default qt4 install have all the functionality that most users would want +[22:40.04] define: all the functionality +[22:40.05] most users of qt will have a desktop profile and/or have all the useflags they want enabled +[22:40.05] :P +[22:40.26] desktop profile enables most of them anyway +[22:40.42] i would suggest remove all + and see what it does +[22:40.48] and introduce only where really needed +[22:40.49] yes, so we can drop those that the desktop profile enables +[22:40.54] re-introduce +[22:40.57] the current behavious is useless to the average user and annoying to those actually having a benefit from split ebuilds +[22:40.59] qt3support is enabled by desktop +[22:41.10] useless?? +[22:41.10] scarabeus: I don't quite agree +[22:41.24] yes, because he has those useflags enabled anyway +[22:41.30] jmbsvicetto: see above +[22:41.32] scarabeus: default use flags allow us to drop most use flags from profiles +[22:41.33] it doesn't affect him at all +[22:41.34] jmbsvicetto: the flag is in profile +[22:41.41] more superfluous than useless +[22:41.47] i was damn angry having +qt3support on sever +[22:41.51] yes +[22:41.53] so i had to edit useflag list +[22:41.56] bad choice of words +[22:42.06] spatz: nothing prevents you from adding - to your /etc/portage/package.use[/*] config file(s) +[22:42.34] mm +[22:42.46] of course, but useflags should be opt-in, not opt-out in the general case +[22:42.48] scarabeus: yes, but instead of removing default use flags because they're enabled on profiles, we should be dropping use flags from profiles and moving them to default use flags +[22:43.03] so let's drop the + on the useflags that are already in profiles +[22:43.11] +1 +[22:43.12] that would be a good start +[22:43.13] jmbsvicetto: really? why? +[22:43.15] and rename gtkstyle to gtk +[22:43.24] *** Kame2 (n=manuel@port-92-196-126-246.dynamic.qsc.de) Quit (Remote closed the connection) +[22:43.36] because that would prevent users from getting all the crap they get from profiles with ton of use flags like qt, kde, gtk or gnome +[22:43.45] tons* +[22:43.46] jmbsvicetto: i really like that i have different useflags on case like server/desktop based on profile +[22:44.01] and for the qt it really made me sad +[22:44.02] yeah, but desktop profiles currently have too many use flags +[22:44.25] maybe the desktop profile needs to be split, but that's out of scope +[22:44.28] scarabeus: the first thing I add to my servers is USE="-X -gtk -gnome -kde -qt" ;) +[22:44.39] yeah yeah but i need qt on mine server +[22:44.40] maybe desktop profile should be divided into subprofiles +[22:44.43] quassel ;\ +[22:44.45] ;] +[22:45.10] so? +[22:45.10] No, I don't think it's out of scope. Instead of spliting profiles or moving flags from packages to profiles, I think we should be going the other way around and dropping use flags from profiles back to packages +[22:45.16] and you shouldn't use the desktop profile on your server :) +[22:45.19] you can still have quassel with -qt +[22:45.42] jmbsvicetto: mail the idea to the -dev :] +[22:45.42] per profile is more appropriate than per package +[22:45.45] spatz: I don't use the desktop profile on my workstations ;) +[22:45.45] jmbsvicetto: well, that's stuff for a wider policy discussion +[22:45.51] that was also agreed last week on -dev, iirc +[22:45.56] yngwin: indeed +[22:46.08] that's what i meant by "out of scope" +[22:46.16] *** scarabeus sets mode: +v wired|quassel +[22:47.07] Anyway, I think kde should retain default use flags for most optional support features that upstream enables by default +[22:47.26] well, i dont have a string preference here, but it looks like my qt brothers do +[22:47.32] strong* +[22:48.10] http://archives.gentoo.org/gentoo-dev/msg_d676d199747afac881bbf444dac478ea.xml +[22:48.48] ok lets continue this topic there +[22:48.56] rather on the meeting :] +[22:49.16] wired: are you around? +[22:49.25] yes +[22:49.33] * bonsaikitten gone +[22:49.34] *** geo27 (n=quassel@lns-bzn-30-82-253-130-209.adsl.proxad.net) Quit (Remote closed the connection) +[22:49.36] jmbsvicetto: upstream enabled by default everything that's autodetected +[22:49.39] wired: did you tracked the tampakrap what he is doing with kde3? +[22:49.48] hence, it's bad approach imho +[22:49.50] only the eclass part +[22:49.53] ah +[22:49.59] scarabeus: btw i talked to him a few minutes ago +[22:50.04] *** geo27 (n=quassel@lns-bzn-30-82-253-130-209.adsl.proxad.net) has joined #gentoo-kde +[22:50.05] where is he +[22:50.10] he missed the meeting because he was traveling to athens +[22:50.19] and can he get online now? +[22:50.24] only to give us status info? +[22:50.32] /report +[22:50.33] hmm +[22:50.39] let me call him and ask +[22:50.42] 1min +[22:50.51] yngwin: so let's do what you decided and check back in while +[22:51.27] reavertm: They don't autoenable everything +[22:51.31] jmbsvicetto: they do +[22:51.36] gtkstyle->gtk, remove default on all flags enabled in desktop profile +[22:51.37] scarabeus: he'll be in here in 15m +[22:51.38] jmbsvicetto: if they detect package, they enable it +[22:51.44] reavertm: For instance kopete doesn't enable by default all protocols and plugins +[22:51.47] do we change them now or on next release? +[22:51.56] there are some exceptions, yes +[22:51.59] *** mrpouet (n=mrpouet@gentoo/developer/mrpouet) Quit (Client Quit) +[22:52.00] ok guys how much you want to read last topic +[22:52.19] scarabeus: ok? =] +[22:52.33] wired: well it depends on others +[22:52.41] i cant hold them here for another 20 minutes ;] +[22:52.45] yngwin: would that require re-stabilizing? +[22:52.46] the meeting already lasts 2 hours +[22:53.02] hmm, good question +[22:53.03] spatz: nope, archies are supposed to test various use flags +[22:53.13] wired: he can login when he can and put a short status message here +[22:53.21] so i guess not :) +[22:53.29] if not than we should do it now, imo +[22:53.36] otherwise we'll forget :) +[22:53.37] *** hkBst (n=hkBst@gentoo/developer/hkbst) Quit (Read error: 104 (Connection reset by peer)) +[22:53.40] *** himikof_ (n=himikof@129.167.249.ozerki.net) Quit (Remote closed the connection) +[22:53.55] 4.5.2 shouldn't be too far +[22:53.58] *** NSaibot (n=quassel@dslb-094-217-110-040.pools.arcor-ip.net) has joined #gentoo-kde +[22:53.58] in that case we can also drop custom-cxxflags useflag as we decided before +[22:54.02] yngwin: it can change the installed package, so it should go through the revbump process +[22:54.20] ok +[22:54.23] then wait for 4.5.2 +[22:54.31] i agree +[22:54.37] for everything or just custom-cxxflags? +[22:54.42] everything +[22:54.42] everything +[22:54.55] ok +[22:55.27] of course we can already do it in the overlay, where applicable +[22:55.29] next topic? +[22:55.43] *** bearsh (n=quassel@80-219-1-239.dclient.hispeed.ch) Quit (Remote closed the connection) +[22:55.45] btw, what about libX11 dep in qt-core? +[22:56.02] that's good to go into the tree +[22:56.20] should we do the same for qt-dbus? +[22:56.21] those deps should be added to qt-gui and friends, no? +[22:56.35] ah good call +[22:56.35] Pesa: it works for me +[22:56.48] can you commit to overlay? +[22:56.53] those that do depend on libX11 and libXext should get it +[22:57.16] make sure all modules are ok and checked for those +[22:57.34] *** himikof_ (n=himikof@129.167.249.ozerki.net) has joined #gentoo-kde +[22:57.35] *** DeSoVoDaMu (n=deso@77-21-66-33-dynip.superkabel.de) Quit (Read error: 113 (No route to host)) +[22:58.03] i might not have time to do it in the overlay because of my exams :/ +[22:58.10] so we need to revbump those packages anyway +[22:58.54] then we might as well do the useflag change, unless 4.5.2 is released very soon +[22:59.04] right +[22:59.18] ok, great +[22:59.55] *** papillon81 (n=papillon@f053145102.adsl.alicedsl.de) has joined #gentoo-kde +[23:00.05] scarabeus: shall we close the meeting then? +[23:00.06] *** scarabeus sets mode: +v papillon81 +[23:00.18] well we can wait 8 minutes and tampy will be here +[23:00.23] it is up to you +[23:00.31] you forget he's greek +[23:00.42] for what topic? (i forgot) +[23:00.43] what does it mean +[23:00.51] Progress of kde3 mess and way how anyone can help (here we call even for non-kdeteam devs) +[23:00.52] 8 minutes could mean anything +[23:01.23] *** scarabeus sets mode: +v wohnout +[23:01.33] *** Gabrys (n=Gabrys@77-254-190-150.adsl.inetia.pl) has joined #gentoo-kde +[23:02.02] wired: ok tell him not to rush, and he will have to sent us the mail onto the kde@ and qt@ alliases or onto -desktop +[23:02.24] ok i hereby close the meeting +[23:02.30] and btw someone create log +[23:02.30] well he should be here shortly, but ok :) +[23:02.36] *** scarabeus sets mode: -m +[23:02.55] i'm here +[23:02.57] aghr +[23:02.59] *** tampakrap_ is now known as tampakrap +[23:03.02] you are joking :D +[23:03.04] lol +[23:03.05] *** scarabeus sets mode: +m +[23:03.06] no i am here +[23:03.15] welcome :) +[23:03.15] yeah i see :] +[23:03.16] ok +[23:03.33] welcome indeed +[23:03.34] what's the deal +[23:03.36] ? +[23:03.41] lol +[23:03.48] kde3 +[23:03.54] we want to know +[23:03.59] Progress of kde3 mess and way how anyone can help (here we call even for non-kdeteam devs) +[23:04.00] state/progress what is to be done +[23:04.02] what is done +[23:04.16] ok +[23:04.31] kde3 misc apps need slotmove and stabilization this will take some time +[23:04.34] as i have no help +[23:04.35] yngwin: hehe +[23:04.39] Heya Theo +[23:04.44] koffice is my playground, i'll fix eclass +[23:04.47] tampakrap: hey i did about 5-10 apps +[23:04.51] *hello hello* +[23:05.00] not the stabilization part though +[23:05.07] so i still have to take care of the list +[23:05.13] and kde-base/*3.5.10* +[23:05.20] has many *stupid* bugs +[23:05.22] tampakrap: i would suggest to switch all misc apps +[23:05.25] that i have no motivation to fix +[23:05.26] and then open 1 stable bug +[23:05.33] this can't be done +[23:05.40] they don't have the same keywords +[23:05.40] why not +[23:05.44] no problem +[23:05.45] and it is against the rules :) +[23:05.48] just make list for each arch +[23:06.02] we do it in X when we stable all the stuff +[23:06.09] this isn't easier for me +[23:06.13] okey +[23:06.16] as pleases you +[23:06.19] since you do the work +[23:06.20] i slotmove package, check bugs and open bug +[23:06.34] anything else? +[23:06.41] what did you say about the stabilization? +[23:06.44] of kde4 +[23:06.55] KDE 4 Stabilisation. +[23:06.55] - Jorge decided to start with 4.2 stabilisation. +[23:06.55] - stabilisation bug will have to be opened +[23:06.55] - tracking bug will have to be opened and bugs wrangled (volunteers??) +[23:06.59] this is summary +[23:07.08] ok +[23:07.11] we need tracker again +[23:07.18] ah how about asking for help with kde3 misc stuff on -dev +[23:07.25] *** Skim[ihz] (n=skim@skim.static.corbina.ru) Quit (Client Quit) +[23:07.26] i volunteer with bug wrangling +[23:07.37] ssuominen did probably great job with removing arts usefla +[23:07.38] g +[23:07.44] how is its progress +[23:07.49] *** scarabeus sets mode: +v ssuominen +[23:07.59] well we can say that kde3 is *open* for anyone +[23:08.09] media-sound cat. is clear of all arts deps +[23:08.10] !rdep arts +[23:08.10] scarabeus: Too many packages have reverse RDEPEND on kde-base/arts, go to http://tinderbox.dev.gentoo.org/misc/rindex/kde-base/arts instead. +[23:08.14] media-libs half way +[23:08.14] not for maintaining but for random bugfixing +[23:08.16] *** [Enrico] (n=chiccoro@host224-36-dynamic.16-79-r.retail.telecomitalia.it) Quit (Read error: 104 (Connection reset by peer)) +[23:08.21] media-video undone +[23:08.31] 785 packages +[23:08.34] * scarabeus is sad +[23:08.41] the media-sound apps left on the list are masked for removal or similar +[23:08.43] yeah +[23:08.51] *** g1lt (n=quassel@203-79-94-158.cable.telstraclear.net) has joined #gentoo-kde +[23:08.52] just set allways arts never when there is optional in ebuild in eclass? +[23:08.56] that might close few? +[23:08.57] there's lots to be done, i can handle it by opening some bugs for teams +[23:09.05] to speed it up +[23:09.20] did similar when i killed gtk+-1.2 from 50%+ pkgs the another summer +[23:09.24] :P +[23:09.32] death to arts +[23:10.09] can we quick vote on "let's remove arts from use defaults immediately?" +[23:10.12] ;) +[23:10.19] ssuominen: voted allowed already +[23:10.21] just do it +[23:10.24] * ssuominen does +[23:10.35] ssuominen: will you be our asignee for arts thing? you seems to enjoy it ;} +[23:11.49] don't mind handling it so why not +[23:11.56] okey +[23:12.04] i will sent you the eclass update then +[23:12.08] for arts removal +[23:12.18] btw how much packages probably has arts HARDDEP? +[23:12.21] can it be found out? +[23:12.22] over the half way, there will always be a maintainer or two who attacks you for removings on false grounds (hit few of those on the gtk+-1.2 road) +[23:13.04] you see how much it hurts mine heart? ;] +[23:13.05] well in media-sound i've fixed about 50% pkgs to not dep on arts anymore +[23:13.08] so painfull ;] +[23:13.10] it was totally false +[23:13.29] well they can state it to us, probably anouncal on -dev might be good +[23:13.30] and removed about the optional dep on 25% and remaining 25% got punted +[23:14.13] but i guess there's no hurry +[23:14.21] but giving it a small boost won't hurt +[23:14.23] ;) +[23:14.24] yes +[23:14.26] :] +[23:14.48] *** mikkoc (n=mikko@host161-90-dynamic.0-87-r.retail.telecomitalia.it) Quit (Remote closed the connection) +[23:14.52] *** Devrethman (n=quassel@209.90.234.102) has joined #gentoo-kde +[23:15.29] anything else we have for kde3? +[23:15.37] *** YaCK (n=brayan@unaffiliated/yack) Quit (Client Quit) +[23:15.38] kill it? +[23:15.48] *** geo27 (n=quassel@lns-bzn-30-82-253-130-209.adsl.proxad.net) Quit (Remote closed the connection) +[23:16.13] look ppl i told you i have no motivation in this thing any more, what i did was to make sure it can work with kde4 +[23:16.29] tampakrap: ok we should recruit someone for that +[23:16.41] since this thing works, we have to tell ppl *asap* that we have no motivation for maintaining it any more +[23:16.43] tampakrap: i really agree that you dont have to push it so hard forward if you dont have the motivation +[23:16.49] it started not to compile you know :) +[23:17.02] And to have security issues! +[23:17.04] tampakrap: open the requirement on the stuffing needs +[23:17.18] scarabeus: nope, add it to our project page +[23:17.19] no, no, kde3 doesn't need maintainer +[23:17.25] it would be best to have it handled by some dev determined to stay with kde3 +[23:17.29] just various bugfixing by ppl who use it +[23:17.43] yeah somebody determined using it would be nice +[23:17.43] at least in kde team there is none... +[23:17.49] :) +[23:17.52] well carlo... +[23:17.58] last seen on february +[23:18.09] when he broke quite few packages with wrong eapi2 bump +[23:18.45] well, nobody is as experienced in eapi2 bumps like we are :P +[23:18.49] so we reaaaally need someone +[23:18.52] reavertm: yeah :D +[23:18.57] we are masters :D +[23:19.07] *** Skim[ihz] (n=skim@skim.static.corbina.ru) has joined #gentoo-kde +[23:19.21] sping is interested +[23:19.40] who is sping +[23:19.44] where is sping +[23:19.51] give us sping! +[23:19.53] jmbsvicetto: will you use your hat and send an email to -dev plz? +[23:19.59] sebastian ping, currently doing GSoC +[23:20.02] scarabeus: just drop 'packages up for grab' list on gentoo-dev with `200 kde3 ebuilds that kde team doesn't care about anymore :D +[23:20.07] *** sean345 (n=sean345@c-76-105-5-254.hsd1.ca.comcast.net) has joined #gentoo-kde +[23:20.10] *** BCMM (n=bcmm@unaffiliated/bcmm) has joined #gentoo-kde +[23:20.16] rofl +[23:20.21] jmbsvicetto: could we do it? +[23:20.22] :DDDDDD +[23:20.27] pipping* +[23:20.38] *** Varox (n=Varox@p4FD46B43.dip.t-dialin.net) has joined #gentoo-kde +[23:20.38] the PackageMap guy +[23:20.48] oh i see +[23:20.54] and is he on irc from time to time? +[23:21.07] yes +[23:21.12] but i assume he is uberbusy with gsoc on the other hand +[23:21.17] yes +[23:21.30] he will return to recruitment after gsoc +[23:22.17] tampakrap: about kde3? ok +[23:22.39] jmbsvicetto: wait for summary i have 2 mails for you probably :D +[23:22.39] scarabeus / reavertm: no :\ +[23:23.02] ok we are probably done about the topic for now, at least until gsoc is over +[23:23.05] no (no we can't drop kde3 on maintainer-needed) +[23:23.17] that was joke :) +[23:23.31] i can supervise the commits +[23:23.34] jmbsvicetto: it was really joke :] +[23:23.41] *** spatz (n=spatz@unaffiliated/spatz) Quit (Remote closed the connection) +[23:23.44] but for bugfixing i doubt it +[23:23.57] ok i anounce the meeting over then :] diff --git a/meeting-logs/20090820-summary.txt b/meeting-logs/20090820-summary.txt new file mode 100644 index 0000000..280f93b --- /dev/null +++ b/meeting-logs/20090820-summary.txt @@ -0,0 +1,41 @@ +Roll-call: +pesa - excused (no net) +tampakrap - excused (family issues) +scarabeus, ABCD, ayoy, patrick, dagger, jmbsvicetto, revartm, wired, yngwin + +KDE-3: +- As discussed before, the KDE team is going to move all KDE3 ebuilds to an overlay. The new +overlay hasn'te been named yet, but will probably be called kde-junk, kde-sunset or something +similar as we plan to use it for KDE stuff that is removed from the tree. +KDE3 is going to be moved to the overlay either after KDE-4.4 is out if nothing evil happens, +or after we get 2 KDE4 minor versions marked stable - which likely means around the end of +the year. +- We are still looking for KDE maintainers. It seems sping might be interested - yngwin will +talk to him. +- Due to the current state of the KDE3 tree source, the lack of support by upstream and the +increasing security concerns, it's likely that we'll mask KDE3 soon. We're delaying the mask +until we get a version of KDE4 marked stable - unless more security issues crop up. +We plan to make an anouncement on Gentoo homepage and to write a news item about the status +of the KDE3 tree and the security implications. +We plan to keep KDE3 around in the tree until KDE-4.4 is released (but it will likely remain +masked) until it's moved to the new overlay. +- Before we remove KDE3 from the tree, we plan to have a news item, planet blog entries, forums +thread and front page announcement about it so the kde3ers won't scream for help all over the +place - jmbsvicetto. + +KDE-4: +- It was decided by a vote not to ask for 4.2.4 stabilization. It will be dropped from the tree. +- Instead, the current plan is to get 4.3.1 marked stable. For that, we need to focus on the +bugs in the tracker[1] and everyone needs to work on it. + +QT4-TNG eclass: +Will be sent for review onto -dev in a week with the -tng name. No better name found out. + +Future projects: +- Documentation polishing +- Branding the KDE +- Fix upstream buildsystem to allow install of different versions into a shared prefix + +Sets: +. Adjust it as for bug #272488 or from the ground up for exact specs we need - +jmbsvicetto (we need to poke him about it often so he won't forget to do it) diff --git a/meeting-logs/20090820.txt b/meeting-logs/20090820.txt new file mode 100644 index 0000000..ad6bf17 --- /dev/null +++ b/meeting-logs/20090820.txt @@ -0,0 +1,545 @@ +[20:55:28] 57 secs +[20:55:40] =] +[20:56:45] okey +[20:56:50] i guess we will have to wait +[20:57:05] since 3 devs; 2 hts and 2 exherbos are not exactly desired combo +[20:57:18] I'm here +[20:57:19] lol +[20:58:00] --> bonsaikitten (i=quassel@gentoo/developer/bonsaikitten) has joined #gentoo-meetings +[20:58:02] --> dagger (n=quassel@gentoo/developer/dagger) has joined #gentoo-meetings +[20:58:12] that helped... a bit :) +[20:58:23] --> yngwin (n=yngwin@gentoo/developer/yngwin) has joined #gentoo-meetings +[20:58:25] --> Ingmar (i=ingmar@exherbo/developer/ingmar) has joined #gentoo-meetings +[20:58:33] --> ayoy (n=ayoy@cs78245237.pp.htv.fi) has joined #gentoo-meetings +[20:58:43] here +[20:59:10] ok +[20:59:14] looks better :] +[20:59:19] so for the tampakrap +[20:59:21] http://www.pastebin.cz/b594e8e991906a +[20:59:30] i count him as excuses due to personal matters +[20:59:41] --> Gentoochild (n=bla@vpn5.rz.tu-ilmenau.de) has joined #gentoo-meetings +[20:59:43] please read the above paste +[20:59:50] pesa has no internet currently +[21:00:35] and ayoy is being grilled by his recruiter +[21:01:03] ok +[21:01:16] anyone said that he will be late? +[21:01:32] otherwise i just wrote up our roll-call, i count everyone whom joined as here +[21:01:34] not that i know +[21:01:42] ok +[21:02:08] ok so i would say lets start with topic 1 +[21:02:12] i'm having a headache, so i'd like to keep this short on my end +[21:02:37] for that i count as relevant tampakraps opinion, and reavertm's they are the last one working on it +[21:02:51] so since tampakrap said it in mail i would ask reavertm if he has something to add +[21:02:52] scarabeus: I'll talk to tampakrap, but 2 things about the KDE3 overlay +[21:03:07] scarabeus: 1. Let's call it kde-junk, kde-sunset, or something like that. +[21:03:27] jmbsvicetto: no problem i have all powers about gitosis +[21:03:36] scarabeus: 2. We can't drop any ebuilds from the tree before at least the end of the year +[21:03:37] just sent me after decided name +[21:03:51] with 2 i agree +[21:03:56] The reason is that we shouldn't tie an overlay to a specific kde version +[21:03:57] i would start it after 4.4 +[21:04:01] if nothing evil happen +[21:04:17] At least not before we get 2 KDE4 minor versions marked stable +[21:04:22] I is here, mostly :) +[21:04:38] So if we got 4.2 and 4.3 marked stable, then we could consider dropping 3.5 from the tree +[21:04:38] we'll probably need an announcement and a news item and any other possible means of communication to alert current kde3 users that they have to add the overlay if they want kde3 +[21:04:59] a few months before we remove it +[21:05:04] that is simple news item +[21:05:13] ad it can go hand in hand with mask :] +[21:05:23] i think 3 month mask for this is good idea :] +[21:05:26] I think we should make such news after first kde4 goes stable +[21:05:32] its simple but it can also be devastating if we forget :p +[21:05:44] and before i forget "DID ANYONE FIND SOME CONTRIBUTORS?" +[21:06:10] I suppose we'll find some gentoo devs still with 3.5 +[21:06:13] iirc sping showed some interest before the summer +[21:06:37] he's resuming recruitment process now +[21:07:00] will you talk to him and find out? +[21:07:07] *mind +[21:07:08] i can yes +[21:07:28] I don't know if my opinion counts, but I really agree to dagger, you should announce that even befor kde4 is marked as stable. It may be very painful for some users to make the change. +[21:07:49] he has point ^ +[21:08:16] scarabeus: kde3 packages moved to overlay won't be subject of package.mask, will they? +[21:08:17] some people dont like kde4 and we wont change it. We just need to make sure they've got enough time to get use to overlay +[21:08:28] (they shouldn't imho) +[21:08:29] we just need to make sure that people will have the overlay added before we remove the ebuilds +[21:08:32] reavertm: wont +[21:08:39] and i agree we reavertm we shouldnt mask it +[21:08:40] I would suggest announcing loudly and often, in many venues so that (hopefully) very few users are taken by suprise +[21:08:41] (just have keywords dropped probably) +[21:08:44] and it needs to be stable before it is marked stable +[21:08:46] scarabeus: news item, planet blog entries, forums thread, front page announcement, ... ;) +[21:09:04] jmbsvicetto: sounds good +[21:09:40] jmbsvicetto: can you do it, please please our PR farry +[21:10:22] i'd wait with too widespread announcements until there is a stable candidate +[21:10:45] indeed +[21:11:00] well i was not saying NOW i mean when the time will come +[21:11:04] (which movesus towards second topic) +[21:11:04] that moves us to point no 2 +[21:11:25] wait a bit, i have one problem with kde3 +[21:11:44] i have seen that debian ship more patches marked as security for kde3 than we even have as bugs +[21:11:55] --> ahf (i=ahf@irssi/staff/ahf) has joined #gentoo-meetings +[21:12:14] we need people now to start maintaining kde3 +[21:12:49] or mask it right after we stable first kde4, dont say remove just mask for sec-issues +[21:13:17] kde3 is dead end. I think we need to decide how long are we going to maintain it +[21:13:26] users wont be happy, but i have to agree +[21:14:04] I'd suggest faster gentoo stable releases so that we can keep up with stable version being the one actually yet supported by upstream +[21:14:08] i think we can write some news item onto the homepage/spread as news +[21:14:20] and if noone will volunteer to work on it in 7 days... +[21:14:22] for example 4.2 branch is no longer mainataned... +[21:14:26] scarabeus: ok +[21:14:30] scarabeus: About the news +[21:14:48] i agree, we need to recruit kde3 maintainers immediately +[21:14:49] --> tampakrap (n=tuxicity@gentoo/developer/tampakrap) has joined #gentoo-meetings +[21:15:04] tampakrap: you, here, how, why +[21:15:11] go home! +[21:15:14] just for logs bye +[21:15:14] reavertm: What do you mean about the package.mask? Do you mean masking KDE3 ebuilds now or after they're moved to the overlay? +[21:15:16] ^^ +[21:15:58] jmbsvicetto: he was worried if we would keep the mask in tree after we move it to the overlay, which is NO +[21:16:13] what scarab said +[21:16:19] if we mask it, we might as well move it +[21:16:40] scarabeus / reavertm: I see and I agree with you - no +[21:16:55] no, users sometimes hate overlays, unmasking is simple +[21:17:00] or we actualy can let them decide +[21:17:10] But we shouldn't mask it until some time after we get KDE-4 marked stable +[21:17:14] i would start with the anouncing call for maintainers on homepage and on all pcs +[21:17:27] then we will know if someone cares +[21:17:32] we can recruit the peeps +[21:17:35] we have the powah +[21:17:37] :] +[21:17:37] I'm sorry, but half my brain is being pulled to #gentoo-userrel +[21:17:55] jmbsvicetto: yes that we mentioned too, after at least 1 kde4 stabled +[21:18:48] but if there are security issues that nobody is fixing, we may need to mask earlier +[21:19:04] jmbsvicetto: anouncement on homepage and as newsitem if noone reply in timely manner (week) then after +[21:19:04] kde4 is stabilised we will right away mask it as security threat. then it will live until +[21:19:04] kde4.4 but masked/or in overlay (to be decided). +[21:19:16] this is my braindead summary +[21:19:51] agreed +[21:19:55] I would say make kde4.a stable, than make kde4.b stable and mask kde3 +[21:20:23] unless critical bugs will force us to make it earlier +[21:20:30] dagger: there must be security ones +[21:20:32] mask* +[21:20:49] just browse debian patches +[21:20:51] another thing to consider when ditching KDE3 is whether all kde3 apps are available for kde4 (like k3b) +[21:21:06] k3b for kde4 works perfectly +[21:21:10] Gentoochild: security has privilege +[21:21:13] (was jsut an exampolke) +[21:21:14] dagger: not really +[21:21:14] mythtv seems to be a problem +[21:21:30] I wonder whether leaving kdelibs:3.5 + some apps would be a problem +[21:21:32] reavertm: I'm using it 2-3 times a week for cd dvd5/9 - all fine +[21:21:43] reavertm thats what i was thinking as well +[21:22:00] maybe we can leave kdelibs3 and a few apps around for a little longer (like +6 months) +[21:22:10] yngwin: I wouldn't mask it, but after we get one KDE4 version marked stable, we should start warning users *publicly* to the status of KDE3 security +[21:22:13] dagger: try writing udf image wth verify - it will lock on 50% on disk eject, but that's off topic +[21:22:29] jmbsvicetto: what are those security issue? khtml? +[21:22:37] yngwin: If that upsets upstream, I don't care. Maybe it might lead someone to start fixing issues +[21:22:41] reavertm: khtml as starters +[21:22:42] jmbsvicetto: no it's very simple: if there are security issues they need to be fixed or the affected packages masked +[21:22:47] there was some more in kdelibs and parts +[21:22:56] simple tracking debian can work +[21:22:57] maybe it's easier just to dump kde desktop (along with affected apps) and leave kdelibs + some apps that are known to work +[21:22:59] but we need that maintainer +[21:23:23] I use Kile very often, and the kde4 version of if is far far away to be usable... +[21:23:35] --> ABCD_ (n=ABCD@gentoo/contributor/abcd) has joined #gentoo-meetings +[21:23:53] yngwin: As a Gentoo policy, you're right. But in that case we should probably have masked KDE-3 a few months ago +[21:24:03] yes +[21:24:11] jmbsvicetto: yes but now we will have stable replacement +[21:24:14] so let's try to make things right asap +[21:24:29] <-- ABCD (n=ABCD@gentoo/contributor/abcd) has quit (Nick collision from services.) +[21:24:32] i would say wait with this decision we can wait for the anouncement and proceed if noone appears +[21:24:33] could someone PM me the logs from " this is my braindead summary" through my re-joining? +[21:24:48] <-> ABCD_ is now known as ABCD +[21:24:50] I suppose masking the only stable kde release is not an option so please make sure we have one left :P +[21:25:08] sure hold on +[21:25:45] reavertm: if no maintainers step up, that is currently our only option +[21:26:38] yngwin: ok +[21:26:48] then we should do as scarabeus said +[21:27:07] can we make a poll on forums, to see how many users still use kde3 and how many moved to kde4? +[21:27:33] yngwin: but we should all be aware that even when kde-4 gets marked stable, it's very unlikely that any arch besides x86, amd64, ppc and ppc64 will get it marked stable soon +[21:27:34] yes we can +[21:27:35] dagger: well usage is not our issue, we need maintainers +[21:27:37] of course it will represent only small percentage of users, but should give us some guidelines +[21:27:51] hey there +[21:27:54] jmbsvicetto: i bet on hppa +[21:28:01] jmbsvicetto: sure, i dont think it will be marked stable soon on any arch +[21:28:09] yngwin: so masking kde-3 will upset quite a few users from these arches, but it will also upset people in the other arches +[21:28:35] scarabeus: Don't forget ia64 or sparc +[21:28:42] so the key is to get some ppl to step up and maintain&fix +[21:28:55] yes +[21:29:01] so exactly what i said +[21:29:05] scarabeus: sparc is still tied to qt-webkit dying with alignment issues +[21:29:20] so no cookies for sparc +[21:29:32] jmbsvicetto: i agree it is bad solution, but it is worse to leave it rot around +[21:29:40] at least 1 maintainer +[21:29:48] it is not so hard, the ebuilds are mostly cleaned and fixed +[21:29:56] they just need the patches and testing +[21:29:57] scarabeus: And unfortunately, it seems each day KDE upstream is more concerned with Windows,OS/X than with Linux alternative arches +[21:30:15] i expected that one +[21:30:34] scarabeus: I'm not arguing against your proposal. I'm just making a few "warning" ;) +[21:30:46] so you can show the logs when they blame you :P +[21:30:48] :DDDDD +[21:30:58] they can still unmask or use overlay if they want kde3 +[21:31:02] i would say lets go for next subject +[21:31:22] agreed +[21:32:06] i summarised it really nicely and jorge as boss can tweak it more to reflect us so we all write our proposals for it +[21:32:15] jmbsvicetto: one Q, did you see carlo lately? +[21:32:31] jmbsvicetto: he did kde3 commits when he was around, so that is why i ask :] +[21:33:18] the awkard silence... +[21:33:36] okey so for the 4.2 stabling i would say vote? +[21:34:04] i vote hell no +[21:34:05] i say we go for 4.3 +[21:34:10] hell no +[21:34:13] so no =] +[21:34:21] 4.3 is the way to go +[21:34:25] I vote.. wait for 4.3.1 +[21:34:34] -*- yngwin is with reavertm +[21:34:45] there's one 'problem' +[21:34:51] yeah, 4.3.1 sounds like the best candidate +[21:34:53] you know my opinion but for the record 4.3 +[21:35:00] kde 4.3 will need phonon-4.4pre +[21:35:08] the snapshot is stable +[21:35:11] where is the issue +[21:35:20] what snapshot +[21:35:21] which is good as it works very well, just doen't look official (and it's not, it's our snapshot) +[21:35:26] phonon +[21:35:39] reavertm: i would say it is ook +[21:35:46] it works peachy for everyone around here +[21:35:49] second thing - akonadi-server sqlite USE flag could be masked in profile +[21:35:59] reavertm: why? it is so borked? +[21:36:04] i didnt get time to test it yet +[21:36:13] scarabeus: ok +[21:36:13] scarabeus: carlo? no +[21:36:13] no prblems with phonon +[21:36:42] scarabeus: I'll have to double check, but I think he's got under undertakers view +[21:36:42] no idea, works for me, but upstream says sqlite threads support is broken sometimes and may cause data loss when using sqlite backend +[21:36:47] scarabeus: meaning is subject to retirement for inactivity +[21:36:54] jmbsvicetto: understood +[21:37:00] and I think would just need better testinb whether it's really the case +[21:37:04] About KDE4, 4.2.4 +[21:37:08] data loss = mask it +[21:37:15] If we wait for 4.3, time will fly by us +[21:37:35] 4.2.4 is not stable, boss +[21:37:35] (mysql is enabled by default for now and sqlite is marked as experimental in pkg_postinst anyway) +[21:37:40] 4.3.0 has some nasty bugs that upstream has admitted already and 4.3.1 shouldn't be out before 1st or 2nd week of September +[21:37:42] neither is 4.3.0 +[21:37:48] jmbsvicetto: yes and no. 4.2 is no longer maintained, and 4.3.1 will give us some time to fix some bugs in 4.3 +[21:37:58] Add at least 1 month to that for asking for it to be marked stable and we'll be getting very close to the year's end +[21:38:38] yep, but i think we need 1 month to fix all the issues we have in the tracker anyway +[21:38:39] yngwin: I think 4.2.4 is not a perfect release, but it's getting very close and will allow us to have a stable version almost 2 months before 4.3 +[21:38:52] I believe having 4.3.1 stable by the time 4.3.3 is released sounds good +[21:38:55] of course before anyone thinks of any kde4 stabilization, blocker bugs needs to be fixed first +[21:38:59] 4.2.4 is usable, but certainly not stable +[21:39:13] 4.2.4 is my vote - but majority rules ;) +[21:39:23] yeah we rule and you rock :] +[21:39:28] (you know the joke right?) +[21:39:35] -*- reavertm knows +[21:39:35] 4.3.0 is more stable than 4.2.4 ;) +[21:39:45] -*- scarabeus confirm +[21:39:50] If i can vote, I vote on 4.3.1, 4.3.0 crashes sometimes... +[21:40:03] much more than 4.2.4 in fact +[21:40:09] actually stability wise i have never had plasma crash yet on 4.3.9999 (and there were some on 4.2 for me) +[21:40:16] i never had a crash on 4.3.0, but saw some bugs about it +[21:40:36] i'm having plasma issues with both 4.2.4 and 4.3.0 +[21:41:05] my vote is to go with 4.3.1 (or 4.3.0 with some patches added) and if so - remove 4.2.4 from tree +[21:41:18] well, not on 4.2 anymore as i upgraded both boxes now +[21:41:24] the only plasmoid which crashes plasma for me is microblogging = 100% crash rate +[21:41:30] reavertm: I don't mean a plasma crash, but dolphin crashes, konqueror crashes sometimes, and plasma crashes :D but it isn't often and it "recover" itself all the times here +[21:41:56] I doubt anyone still uses 4.2 - adding 4.3 umasked was epic kill for idea of stabilizing 4.2 +[21:42:01] on 4.2.4 i had plasma crashes completely freeze up X +[21:42:23] i am for that removal +[21:42:26] 4.2 +[21:42:27] so, do we need to count the votes than? +[21:42:36] dagger: no need, only boss was for 4.2 +[21:42:36] or is it decided +[21:42:40] yngwin: i can be video drivers issue, I have never had a X freeze up with kde 4.2.* +[21:42:49] nvidia +[21:42:53] yngwin: ati +[21:42:59] nvidia, worksformetm +[21:43:08] what reavertm said +[21:43:10] btwwho is working on stable bugs? +[21:43:20] i saw only reaver commenting on them and i closed few +[21:43:24] but the list is still large +[21:43:29] intel 4500hd and nvidia here. Nvidia doesn't like new kernel and heci (from staging) driver +[21:43:34] i need to ask you to pick 1-2 from there and fix them +[21:43:39] some of them are gfx driver issues +[21:43:54] yeah, we need them fixed asap +[21:44:16] ok, can we move on? +[21:44:33] i want to hear that they read what i wrote ^ +[21:44:39] :D +[21:44:57] summary of no. 2 please :) +[21:45:32] http://www.pastebin.cz/22046 +[21:45:34] here you are +[21:45:50] --> Coopy (n=Coop@p4FEDA352.dip.t-dialin.net) has joined #gentoo-meetings +[21:46:01] looks good +[21:46:28] yngwin: next topic is yours +[21:47:07] ok, we're ready to add qt4-tng.eclass to portage, no alternative names have been proposed +[21:47:39] i plan to do a review this weekend and send it to -dev ml for rfc +[21:48:06] qt4-superstar could go? +[21:48:09] qt4-meh +[21:48:11] :] +[21:48:12] lol +[21:48:15] qt4-blah ? +[21:48:17] qt4-v2 ? +[21:48:23] qt5 +[21:48:25] :D +[21:48:26] qt4-thisistheoneyouwant +[21:48:27] im a bit worried about tng, it sounds good and all +[21:48:31] ayoy: LOL +[21:48:39] <-- |Francis| (n=kvirc@AGrenoble-152-1-28-162.w82-122.abo.wanadoo.fr) has quit (Remote closed the connection) +[21:48:48] but what if we want to replace it again in the distant future +[21:48:59] what is tng? +[21:49:01] qt4-tng sounds a lil bit like star trek, but I think we can live with it ;p +[21:49:04] well, you can send bikeshedding proposals once the rfc is on ml +[21:49:04] well you can live with one damn eclass like us +[21:49:08] it doesnt sound like it +[21:49:10] Ronis_BR: the next generation +[21:49:11] it is startrek +[21:49:12] :p +[21:49:16] O_o +[21:49:30] wierd :) +[21:49:39] to baldly go where no-one has gone before +[21:49:44] --> |Francis| (n=kvirc@AGrenoble-152-1-28-162.w82-122.abo.wanadoo.fr) has joined #gentoo-meetings +[21:49:48] -*- wired wonders if after tng we'll have the-empire-strikes-back or something +[21:49:51] :P +[21:49:55] to baldly compile what noone else was able to do +[21:50:03] wired: lol +[21:50:08] wired: good name for kde3 overlay maybe? +[21:50:13] :D +[21:50:16] lol +[21:50:21] yngwin: i am open for proposals +[21:50:27] and i have strong feelings for this one +[21:50:31] :} +[21:50:32] eheheh +[21:50:38] but isn't qt4-tng or whatever meant to replace the old qt4.eclass? +[21:50:47] eventually yes +[21:51:00] qties4.eclass +[21:51:01] :D +[21:51:07] we can't just dump the old one and put the new one in place +[21:51:11] no +[21:51:12] you cant +[21:51:13] dagger: sure +[21:51:17] you would break the ebulds +[21:51:22] *current +[21:51:22] yep +[21:51:24] yes we need a migration +[21:51:30] you guys should really "learn" how to make drastic eclass changes in place like we do :D (with no new eclasses involved) +[21:51:33] qt4-tng is a gentoo version with patches or not? +[21:51:36] unless you want to check all ebuilds that use qt4.eclass wrt new functionality +[21:51:39] reavertm: see this is reason why i slapped you everytime for backcompat +[21:51:50] scarabeus: with kde-misc? :P +[21:51:58] its TNG folks +[21:52:05] does picard look like kirk to you? +[21:52:07] :D +[21:52:10] reavertm: yep :] +[21:52:20] kirk had better chicks +[21:52:22] they had skirts +[21:52:23] ok, back to the point please +[21:52:24] <-- Coopy (n=Coop@p4FEDA352.dip.t-dialin.net) has quit ("Leaving") +[21:52:29] ok ok +[21:52:33] i think tng is done +[21:52:49] as far as i'm concerned yes +[21:53:02] or just qt4-0.1.eclass +[21:53:10] (then 0.2 for next revision :P) +[21:53:13] "Backcompat is to still commit in the present the errors commited in the past" +[21:53:15] jmbsvicetto: you should push your versioned eclasses idea +[21:53:28] ok anyway +[21:53:36] the last thing is bit brainstorming +[21:53:42] what shoudl we focus on in future +[21:53:45] too bad you can't do it in place +[21:54:32] I remember seeing an agenda item in some email about the unversioned sets +[21:54:35] sorry guys - mind at userrel +[21:55:11] ABCD: i was waiting on jorge to come back so i left it as totaly last +[21:55:19] scarabeus: ok +[21:55:21] scarabeus: That idea wasn't mine, I just pulled it out of the dust ark ;) +[21:55:38] :] +[21:55:46] ok any ideas/proposals what we should focus +[21:55:51] we will have new recruits +[21:55:51] scarabeus: The versioned eclasses +[21:55:58] jmbsvicetto: i understood +[21:56:07] and for them we need something creative to do +[21:56:12] we cant just leave them fix bugs +[21:56:14] same for us +[21:56:22] if i would only fix bugs i would went insane +[21:57:10] in qt team we are actively looking at adding new qt4-based packages all the time +[21:57:13] i had idea about branding, but then i cant draw +[21:57:22] :) +[21:57:33] so someone else would have to mentor the idea +[21:57:34] documentation could use more work too +[21:57:49] I had an idea of qt-based portage gui +[21:57:56] but then I wouldn't use it +[21:58:00] :D +[21:58:06] ayoy: noone would I think :p +[21:58:09] :) +[21:58:10] scarabeus: There's always the "fix upstream build system" idea ;) +[21:58:21] there was a kde(3?) one iirc +[21:58:21] scarabeus: branding is actually a lovely idea, remember that gentoo kstart icon quantumsummers had? +[21:58:24] we need artists +[21:58:25] I have some task, not sure whether suitable for newcomers +[21:58:40] i have tasks not suitable for myself :D +[21:58:44] so go on +[21:58:45] :] +[21:58:47] I need eclass for odbc driver management +[21:59:01] supporting iODBC and unixODBC interfaces +[21:59:35] well that is totaly not beginner work +[21:59:37] ok, next +[21:59:40] I'm sorry guys, but I will have to leave you now. I need to pick up my wife. +[21:59:48] registering/unregistring drivers, in similar way like in debian, (but separately - one for iODBC and one for unixODBC) +[21:59:56] c ya dagger +[22:00:21] (it should be easy, mostrly it's just invocation of unixodbc tool with creating some files in /etc) +[22:00:33] well if you find interested recruit go for it +[22:00:36] --> Francois (n=francois@193.253.141.72) has joined #gentoo-meetings +[22:00:50] reavertm: question. how is your reviewing going by? +[22:01:08] I'm lazy to send fixed quizzes +[22:01:25] gosh +[22:01:31] please do so +[22:01:34] sooon +[22:01:35] :] +[22:01:35] nevermind +[22:01:47] ok last topic is SETS +[22:01:53] I hate the current state +[22:01:56] i preffer metas more +[22:02:12] so we need someone to write proper specs for what we need from sets +[22:02:12] <-- |Francis| (n=kvirc@AGrenoble-152-1-28-162.w82-122.abo.wanadoo.fr) has quit (Read error: 104 (Connection reset by peer)) +[22:02:21] and talk about it with zac +[22:02:27] and even better help him implementing +[22:02:34] jmbsvicetto: ^ ? +[22:02:38] oh yes, have anyone read bug 272488 ? +[22:02:40] am i right? +[22:02:53] https://bugs.gentoo.org/show_bug.cgi?id=272488 +[22:03:04] i did i liked +[22:03:08] reavertm: That sounds like an eselect and not eclass (odbc) +[22:03:09] you volunteer? +[22:03:29] scarabeus: I'll take this one +[22:03:47] scarabeus: I've been meaning to write about it for a *long* time, but I keep postponning it +[22:03:48] jmbsvicetto: use teh bug as base, i like the idea +[22:03:57] scarabeus: Can I ask you to poke me about it until I do? ;) +[22:04:54] jmbsvicetto: hmm, not really, it would be eclass for packages that provide odbc driver +[22:04:55] reavertm: I know the bug. My plan is to get back to the basics about sets +[22:05:07] it's not about switching between iodbc vs unixodbc +[22:05:07] if you promise you wont mark me as your counter person for next lead vote ;] +[22:05:09] :D +[22:05:11] ok can do +[22:05:13] (it's determined at compilation time) +[22:05:18] I wonder when gentoo guys will look at https://bugs.gentoo.org/show_bug.cgi?id=268891 +[22:05:18] reavertm: ok, then I misunderstood. sorry +[22:05:46] scarabeus: Are you affraid instead I'll point to you when it gets time for the next election? ;) +[22:06:04] :D +[22:06:20] okey +[22:06:28] anything else for the sets, we will leave them to you +[22:06:32] and poke you about it :] +[22:06:42] jmbsvicetto: I think 2.2 style sets are dead end +[22:07:02] confusing syntax +[22:07:39] what i want is kde-latest-release sets +[22:07:58] that is quite hard to make but i see the point :] +[22:08:00] so that 4.2.4 would be automatically updated to 4.3.0 +[22:08:19] yngwin: that's basically unversioned sets ;) +[22:08:21] also i think we should stop encouraging set usage in docs +[22:08:24] yes +[22:08:33] the unversioned sets work like that :) +[22:08:39] they dont +[22:08:44] too much package fuzz movement +[22:08:52] / +[22:09:07] scarabeus: they do - the problem is our "non-stopping" upstream ;) +[22:09:42] ok, anything else for the meeting? +[22:10:01] scarabeus: They have what we call here "bicho de carpinteiro". They can sit still for a minute and thus keep moving packages left and right, adding new ones, killing old ones and finding new and better ways to make distros life harder ;) +[22:10:11] do you guys think we should move the plasmoids from kde-testing to the tree? +[22:10:13] The can't sit still* +[22:10:24] wired: we can +[22:10:30] wired: How good do you think they are? +[22:10:32] just test them for leaks +[22:10:36] and crashes +[22:10:38] everytime +[22:10:40] plasma is core +[22:10:44] if it crashes it is PITA +[22:10:48] jmbsvicetto: some of them are pretty good, others i have no idea +[22:10:59] wired: then add the one you like +[22:11:00] i mostly test that they build and occasionally that they load +[22:11:09] wired: I don't see a problem with adding good ones +[22:11:21] but you really have to test them +[22:11:24] and what scarabeus said ;) +[22:11:31] ok so on a per-plasmoid basis +[22:11:36] kk +[22:11:55] well, kde developers doesn't test their code sometimes, so we should +[22:11:56] you have already discussed about kdeprefix i think, haven't you? +[22:12:15] Ronis_BR: that was decided long ago, not matter of this meeting +[22:12:15] Ronis_BR: yes, it's dead (for now) +[22:12:24] ok +[22:12:30] too bad, but ok :) +[22:12:40] Ronis_BR: we accept patches +[22:12:40] :D +[22:12:54] Ronis_BR: that was decided at the June meeting :) +[22:13:12] ok i would like to dismiss the meeting for this moth +[22:13:14] any objections? +[22:13:25] ABCD: sorry, it is the first time that I hear about gentoo meetings :) +[22:13:39] scarabeus: Before we go, when should we have the next meeting? +[22:13:41] Ronis_BR: kde.gentoo.org its on the page, logs+summary +[22:13:53] I suppose we don't need more meeting recently - just people eager to work on issues :P +[22:13:54] 17.9. +[22:13:57] jmbsvicetto: ^ +[22:14:02] 3rd thursday in the month +[22:14:09] 19:00 utc +[22:14:15] if noone found it really evil or bad +[22:14:17] right +[22:14:33] Oh!!! +[22:14:38] scarabeus: i will be on holiday that week +[22:14:39] scarabeus: actually we could just meet in two weeks to evaluate work done +[22:14:40] One last item I forgot to add to the meeting +[22:14:50] Anyone willing to help solar about the 10.0 release? +[22:15:00] I'll have to check my class schedule for Fall semester again, but I think that will work (it does fall in the middle of the day here, though) +[22:15:10] jmbsvicetto: what kind of help +[22:15:15] I want to help with KDE (and if I can compiz), but it would be great if more people could help +[22:15:18] -*- scarabeus busy with x11stabling/overlays rework +[22:15:54] yngwin: solar and a few others are working on catalyst specs to build a live-dvd with x86/amd64 to celebrate Gentoo's 10th birthday +[22:16:08] catalyst.... +[22:16:22] well thats release team work +[22:16:23] jmbsvicetto: can they add ~ packages? +[22:16:35] yngwin: there is no such team iirc +[22:16:36] :D +[22:16:37] they could add kde 4.3 :) +[22:17:11] -*- yngwin sends thunderbolts scarabeus' way +[22:17:13] because if kde3 will be there, we can simply grab sabayon, it will be more promotial +[22:17:23] and polished :P +[22:18:15] scarabeus: There's an release team +[22:18:26] But this is a "special edition" +[22:18:39] scarabeus: The point is to have KDE4, not 3.5.10 +[22:18:40] solar or agaffney? +[22:19:33] <-- Francois (n=francois@193.253.141.72) has quit (Client Quit) +[22:20:27] ...? +[22:20:36] release tem +[22:21:30] http://www.gentoo.org/proj/en/releng/ +[22:22:24] ok guys anyway i have to run +[22:22:31] here is the summary: http://dev.gentoo.org/~scarabeus/0908summary.txt +[22:22:33] do logs yourself +[22:22:36] jmbsvicetto: ^^ +[22:22:39] download it NOW +[22:22:44] :D +[22:23:08] scarabeus: ok +[22:23:12] <-- tbeadle (n=quassel@division.aa.arbor.net) has left #gentoo-meetings ("http://quassel-irc.org - Chat comfortably. Anywhere.") +[22:23:34] * scarabeus has changed topic for #gentoo-meetings to: "Rem tene, verba sequentur || Keep to the subject and the words will follow" +[22:23:50] scarabeus: can't find the file in packer +[22:23:54] pecker* +[22:24:29] jmbsvicetto: it downloads, its in public_html probably :D +[22:24:48] jmbsvicetto: i have logs, do you need them? +[22:24:51] -*- yngwin out +[22:25:14] scarabeus: please ignore me +[22:25:32] wired: I can't connect through http at the moment, but thanks +[22:25:55] wired: I got it from Tomas. I was just showing signs of my "split brains" :\ +[22:26:03] heheheh +[22:26:09] no problem +[22:26:20] did you log the meeting or you want me to give you my log? +[22:26:57] <-- ABCD (n=ABCD@gentoo/contributor/abcd) has left #gentoo-meetings ("http://quassel-irc.org - Chat comfortably. Anywhere.") +[22:27:50] jmbsvicetto: ^^ +[22:29:25] wired: I didn't log +[22:29:36] wired: Thanks for reminding me I forgot to add a rule to my irssi about this +[22:31:37] <-- ayoy (n=ayoy@cs78245237.pp.htv.fi) has left #gentoo-meetings ("kbai") +[22:32:27] jmbsvicetto: yw +[22:32:42] jmbsvicetto: so where do you want log? pecker? +[22:35:05] jmbsvicetto: ~wired/kde/200908_meeting.log +[22:36:24] wired: thanks +[22:40:10] :) +[22:41:49] scarabeus: I have another request for you - starting Saturday, poke me for the logs/summary ;) +[23:10:08] \part +[23:10:16] <-- Gentoochild (n=bla@vpn5.rz.tu-ilmenau.de) has left #gentoo-meetings ("Konversation terminated!") +[23:17:09] btw you can leave now, next on the list is gnome meeting, and i dont think you want to slack around that ;D +[23:27:43] gnome meeting? nice diff --git a/meeting-logs/20090917.txt b/meeting-logs/20090917.txt new file mode 100644 index 0000000..5cbdcf5 --- /dev/null +++ b/meeting-logs/20090917.txt @@ -0,0 +1,572 @@ +[22:01:31] *** Joins: wired (n=wired@gentoo/developer/wired) +[22:01:32] *** Joins: ayoy (n=ayoy@cs78245237.pp.htv.fi) +[22:01:55] *** Joins: dabbott (n=david@gentoo/developer/dabbott) +[22:02:07] *** Joins: toralf (n=toralf@g224122197.adsl.alicedsl.de) +[22:02:33] *** Joins: Battousai (n=bryan@maduin.southcape.org) +[22:03:44] * wired makes sure logging is on +[22:04:59] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) +[22:05:07] I'm here +[22:05:09] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) +[22:05:39] scarabeus: jmbsvicetto? +[22:05:44] *** Quits: ABCD (n=ABCD@gentoo/developer/abcd) (Read error: 104 (Connection reset by peer)) +[22:06:02] *** Joins: ABCD (n=ABCD@gentoo/developer/abcd) +[22:07:24] *** Quits: |Francis| (n=kvirc@AGrenoble-152-1-48-33.w82-122.abo.wanadoo.fr) (Remote closed the connection) +[22:07:35] wasn't it moved to friday? :P +[22:08:02] scarabeus sent "correction" email +[22:08:02] :p +[22:09:06] oh, I was already here +[22:09:08] yeah +[22:09:11] didn't i hilight you? +[22:09:18] :P +[22:09:25] scarabeus said he might not make it, who else is late? +[22:09:25] I'm not sure how well my connection is going to hold up, so... +[22:09:29] Yeah, but I had forgot I was around here +[22:10:27] * jmbsvicetto makes mental note - win 76 +[22:10:29] Anyone logging? +[22:10:37] everytbody +[22:10:43] i am +[22:10:55] yngwin won't be coming, scarabeus too +[22:10:56] ok +[22:11:02] we're missing patrick, tampakrap +[22:11:11] and some more qt representatives +[22:11:26] ayoy spatz and Pesa are here +[22:11:33] hwoarang is on long devaway +[22:11:36] Let's give them a few more minutes? +[22:11:38] yngwin is away too +[22:11:47] we're waiting for bonsaikitten? +[22:12:05] i pinged them +[22:12:07] *** Joins: bonsaikitten (i=quassel@gentoo/developer/bonsaikitten) +[22:12:08] good, on his way :) +[22:12:19] *** Joins: tampakrap (n=tuxicity@gentoo/developer/tampakrap) +[22:12:29] good +[22:12:43] So, who wants to chair this one? +[22:13:01] I could use the break to get ready another thing I'm working on +[22:13:34] hello +[22:14:14] jmbsvicetto: i'll do it +[22:14:45] good, do we have decisive power? +[22:14:46] lets get going, first topic, 4.3 stabilization +[22:14:58] wired: thanks +[22:15:04] to vote stuff and such? it's quite few of us +[22:15:26] wired: roll call first +[22:15:47] here +[22:15:58] reavertm: I don't think we have much to vote today. It's more about getting processes started +[22:16:02] here +[22:16:04] that was done, but present yourselves for the record if you want :) +[22:16:26] here +[22:16:38] here +[22:16:46] i am +[22:16:56] ok, wired, move on +[22:17:20] first topic, kde 4.3 stabilization +[22:17:26] are we still going with 4.3.1? +[22:17:34] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) +[22:17:38] here +[22:17:52] yaah, we're going with 4.3.1, I wanted to bring this topic to... +[22:18:14] gather some manpower to fix blocker bugs (or talk about dropping some blockers) +[22:18:38] are there any specific blocks we should focus on? +[22:18:50] https://bugs.gentoo.org/show_bug.cgi?id=277868 +[22:18:50] is there a list/tracker? +[22:18:54] this is bug +[22:19:09] btw meeting agenta: http://archives.gentoo.org/gentoo-desktop/msg_1abe5bf232579eabb51aadc3d80b397b.xml +[22:19:15] wired: yes +[22:19:18] in case you don't have the mail available +[22:20:10] 12 bugs +[22:20:18] One thing we need to do ASAP is adding the patches being sent to the packagers ml +[22:20:28] i agree +[22:21:14] if we could focus these 2 weeks ideally we could request stablereq right after the 1 month period +[22:21:26] yes +[22:21:38] *** Joins: [Enrico] (n=chiccoro@gentoo/contributor/Enrico) +[22:21:49] I've already set java as default backend so one bug less (about redland crashing) +[22:21:58] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) +[22:22:03] great +[22:22:03] and there's postinst message +[22:22:35] so guys please do your best so we can finally have kde4 in stable :D +[22:22:43] We should also start opening stabilization bugs for deps: automoc, strigi, soprano, phonon. Anything else? +[22:23:04] are we stabling the phonon snapshot? +[22:23:22] yes, it works fine +[22:23:30] (it has unstable API) +[22:23:44] well it'll have to do if thats all we've got +[22:23:58] it's known to work anyway +[22:24:05] ok +[22:24:08] what's the minimum working version? +[22:24:25] * wired looks ar reavertm +[22:24:29] at +[22:24:38] And we need to get it stable or there'll be no stable KDE-4.3.1 +[22:25:12] 4.3.1 should od +[22:25:23] do +[22:25:33] but... mplayerthumps would need changes +[22:25:48] By the way, we're including KDE-4.3.1 in the 10.0 livedvd, so we should try to get it stable around October 4th +[22:25:49] (disabling phonon backend - as it only works with latest phonon) +[22:25:59] otherwise kde would pull mplayer... +[22:26:22] reavertm: can 't we leave it out? (mplayerthumbs) +[22:26:39] why should we? part of kdemultimedia +[22:27:00] whats wrong with having mplayer as a dep (besides an extra dep)? is it not working ok? +[22:27:44] reavertm? +[22:27:45] I suppose it is, whatever if you like one could go with 4.3.1 phonon and that change in mplayerthumbs +[22:28:08] reavertm: I mean if it's too much trouble to get it working with current deps, we can leave it out for now and get it marked stable later (perhaps even on 4.3.2 or later releaes) +[22:28:11] I won't die for this cause, 4.4pre is just not worse than 43.1 +[22:28:34] jmbsvicetto: well we have tested the phonon snapshot extensively +[22:28:47] wired: ok +[22:29:04] as long as its an exception (snapshots) ;) +[22:29:10] I even asked some kde devs about it :P +[22:29:36] jmbsvicetto: is there an issue with stabling it +[22:29:36] ? +[22:29:43] ok +[22:29:52] * wired kicks isp for lag +[22:30:07] anyone else wanna say anything about stabilization? +[22:30:25] apart from get to work? :) +[22:30:30] yeah +[22:30:43] it isn't possible to have it fully stabilized until october 4th +[22:30:58] well, we need more stable testers ... +[22:31:42] *** Joins: alexxy (n=alexxy@gentoo/developer/alexxy) +[22:31:48] alexxy :) +[22:31:51] hi all! +[22:31:53] bonsaikitten: I use stable system :P +[22:31:59] sorry that i'm late +[22:32:02] ooh :) +[22:32:14] (with exceptions for kde and its deps) +[22:32:15] isnt meeting was schedulet for tommorow? +[22:32:22] initially it was +[22:32:24] alexxy: scarabeus sent a correction email +[22:32:25] the problem is that the one month period is beyond that date +[22:32:28] he failed at the date +[22:32:31] nevermind, you missed nothing +[22:32:43] not to mention the time that arch teams need +[22:33:15] tampakrap: no its not, you added the ebuilds on sept 1st +[22:33:15] the problem is getting archs to stable it in 3 days +[22:33:15] assuming we have fixed bugs +[22:33:33] one month with no open bugs +[22:33:50] wired: 4.4_pre? Preferably we should do 4.3.1 instead, but if 4.4_pre solves other issues, let's go with it +[22:33:54] i hope i'm wrong on this one... +[22:34:16] tampakrap: sure, but we can start the work to get it marked stable asap +[22:34:30] jmbsvicetto: 4.4_pre20090520 yeah, thats the one we have in ~testing now +[22:34:50] tampakrap: we can file an "early request" bug +[22:35:00] tampakrap: it's up to arch teams whether they want to mark it stable or not +[22:35:02] ah ok then +[22:35:07] and we also have one extra motive +[22:35:09] tampakrap: and for the livedvd we only need amd64/x86 +[22:35:10] livedvd +[22:35:33] ok let's hope this will work then +[22:35:47] I recommend we do a mini meeting next week +[22:35:56] may be +[22:35:57] to check on the state of bugs +[22:35:59] tampakrap: Besides, I think we're starting to have many amd64/x86 users on KDE-4 +[22:36:00] nice idea +[22:36:16] wired: good idea +[22:36:49] same day next week? 24th? +[22:37:20] fine by me +[22:37:35] great, i'll send the email, we can adjust if needed +[22:37:36] wired: sure +[22:37:57] lets do our best and close all bugs :D +[22:38:07] ok enough with this then, lets proceed +[22:38:17] kde3.5, kde-sunset +[22:38:28] who's taking care of this and can give us an update? +[22:38:33] tampakrap?/ +[22:38:41] there is no progress in that subject +[22:38:59] apart from the fact that scarabeus created the overlay :P +[22:39:01] On that spirit, I'd like to ask all of you interested in the livedvd to join #gentoo-ten get the ISOs, test them and fix any KDE bugs +[22:39:06] so nobody is interested - good :) +[22:39:19] reavertm: heh +[22:39:20] I'm "owing" an email about it +[22:39:28] jmbsvicetto: lol click send +[22:39:48] The official email putting the "death seal" on KDE-3.5 +[22:39:51] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) +[22:39:55] ah that one +[22:40:25] is anyone else interested in helping make the move to kde-sunset? +[22:40:39] besides tampakrap? :P +[22:40:45] no! +[22:40:53] it should rot and die +[22:40:56] hehe +[22:40:56] reavertm: think positive, we'll get rid of it from the tree +[22:40:58] :D +[22:40:58] i agree noone else is needed +[22:41:07] we just need to stabilize kde4 and kill 3 +[22:41:08] wired: I can help move the ebuilds there +[22:41:22] great +[22:41:34] not sure if we need scarabeus to give us access to it or if he added us all +[22:42:03] ok, next item +[22:42:06] kdeprefix +[22:42:09] wait +[22:42:12] about kde3 +[22:42:15] yeah? +[22:42:26] i have set some rules before moving ebuilds to kde-sunset +[22:42:49] you should make Documentation/CODE +[22:42:50] i sent them in the previous meeting through scarabeus because i wasn't present then +[22:42:55] ah ok +[22:43:05] nice idea #2 +[22:43:25] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) +[22:43:29] OK +[22:43:34] anyone else anything about kde3? +[22:44:06] moving on then +[22:44:08] kdeprefix +[22:44:18] not sure what scarabeus had in mind when he added it to agenda +[22:44:32] perhaps removing it completely? +[22:44:49] I think there's no need to drop it from eclass +[22:44:51] to much work :P +[22:44:59] well its not usable in current state +[22:45:06] and its masked +[22:45:08] and it causes much more bugs +[22:45:22] wired: I asked him to add this point to the agenda +[22:45:25] so let it stay masked =) +[22:45:33] we explicitly don't support any kdeprefixed installations +[22:45:41] jmbsvicetto: ok, what did you have in mind? +[22:46:09] The point is we should send an email letting those using kdeprefix of the new breakage and warning them they should really move out of +kdeprefix +[22:46:25] I think we should still keep code in mind that it may be enabled as some point +[22:46:25] +know +[22:46:36] but this mail is needed +[22:47:07] jmbsvicetto: ok, but they should know already, portage should have screamed when we masked it +[22:47:28] but an email (and perhaps a blog post, i could do that) would help +[22:47:42] That's all I'm after +[22:47:44] a news item maybe? +[22:47:50] post a sticky in the forums, many go there +[22:48:05] I think it is mentioned already +[22:48:13] in stick in Desktop Environment +[22:48:33] okay.. who wants to send the email? +[22:48:52] Gentoo KDE Lead volunteered, no? :) +[22:49:10] *** Parts: [Enrico] (n=chiccoro@gentoo/contributor/Enrico) +[22:49:10] hehe +[22:49:11] (jmbsvicetto) The point is we should send an email +[22:49:16] I did +[22:49:30] :) +[22:49:31] ok +[22:49:34] I'll write a blog post +[22:49:57] anyone else have anything on kdeprefix? +[22:50:18] * reavertm will add one quick point to agenda later +[22:50:18] moving on +[22:50:26] qt 4.5 +[22:50:43] some people (and some qt devs apparently?!) say its broken with gcc 4.4 +[22:50:54] is everyone aware of the problem? if not, then qt-4.5 may break with 4.4 +[22:50:58] wired: i dont see any breakages +[22:51:00] do we have any evidence? +[22:51:03] with gcc-4,4 +[22:51:07] not any im aware of +[22:51:11] (apparently when strict aliasing is enabled) +[22:51:36] well +[22:51:39] gcc-4.4. is officially not supported (well, not listed in supported), for 4.5 +[22:51:57] I remember someone reporting breakage with 4.4, and Sput confirming it's known to break, but I personally use it successfully +[22:52:00] isn't it in stabilization process though? +[22:52:03] All I can say is that I haven't noticed any KDE-4.3.1 program crashing with qt-4.5.2 and gcc-4.4 +[22:52:06] and portage already spits QA warnings with gcc-4.3.2 +[22:52:11] does ANY of you have issues with qt 4.5 and gcc 4.4{,.1}? +[22:52:11] cause so far its all blah blah blah +[22:52:11] but no evidence +[22:52:38] i say its FUD until proved otherwise by bug reports +[22:53:07] no problem here, but gcc's warnings are quite scary +[22:53:24] Pesa: what warnings? :) +[22:53:27] I'll ask thiago about details and get back on next meeting (should have done it already..) +[22:53:33] about strict aliasing +[22:53:36] reavertm: alright +[22:53:42] i still think we need proof of breakage +[22:53:45] mhm +[22:54:02] *** Quits: toralf (n=toralf@g224122197.adsl.alicedsl.de) (Client Quit) +[22:54:23] ok, but... +[22:54:34] if let's say it's horrible breakage, what then? +[22:54:44] (and proven) +[22:55:09] is it fixed in 4.6? +[22:55:12] reavertm: The point is that if it's true, we can't get KDE-4.3.1 marked stable +[22:55:16] who thinks we can hold back gcc-4.4 stabilization (with all those ricers around) until 4.6 is out? :P +[22:55:22] well if its strick-aliases, can't we disable it? +[22:55:30] strict* +[22:55:40] jmbsvicetto: as of current stable gcc 4.3.2 we can +[22:57:00] jmbsvicetto: it's not a matter of kde but qt4 (already stable :P) +[22:57:19] hehe +[22:57:28] qt? Who's that? ;) +[22:57:39] jmbsvicetto: want to remove Qt from tree and see if kde works? +[22:57:40] :D +[22:58:25] anyway, we'll need to look into this +[22:58:39] we need to work some procedures in case it's breakage :P +[22:58:44] i wonder if enforcing something like -fno-strict-aliases would work, then again i have no idea of the problem or what causes it +[22:59:14] can we filter flags for anything that builds against qt4? +[22:59:34] I mean *anything* +[22:59:40] nope +[22:59:42] not really +[22:59:44] (with qt4 itself) +[22:59:56] but maybe building the libs with that flag would be enough +[23:00:01] so if anyone encounters random runtime failures ... +[23:00:04] we really need more info and test cases +[23:00:15] wired: nope, there are templates :) +[23:00:21] unfortunately some code may be inline... templates +[23:00:34] QVector for example +[23:00:41] then we have to try to find more info and failure cases +[23:01:00] the problem, I think, is in 2 headers installed by Qt; the flag would have to be added to every package that uses either header +[23:01:05] and I think thiago talked about QVector suffering from aliasting for example +[23:01:16] i suggest we look for info ( reavertm please ask like you said ) and we talk about this *important* issue on mini-meeting as well +[23:01:26] even sooner in chat if we have updates +[23:01:55] ok +[23:01:58] on my TODO, next? +[23:02:05] great +[23:02:08] if the problem is limited to only some classes, is there a patch we can backport? +[23:02:24] Pesa: well sput said that they're not willing to fix it +[23:02:35] O_O +[23:02:40] we can create one :P (with workaround maybe - like some gcc directive :P) +[23:02:56] but this whole ordeal looks like fud to me, if its serious they will have to fix it +[23:02:56] we can check other distros using gcc 4 +[23:02:56] 4.4 +[23:02:56] for custom patches +[23:03:03] I think that's because there are too many changes 4.5<->4.6 +[23:03:20] i see +[23:03:34] i'll try to see what other distros with gcc-4.4 (if any?! :P) do - if they do anything at all +[23:03:44] they may not know +[23:03:52] you never know +[23:03:53] (kde devs may no know even) +[23:04:00] or there might really be not issue at all +[23:04:04] :) +[23:04:17] next fedora and next ubuntu have gcc 4.4 afaik +[23:04:35] maybe current fedora too +[23:04:43] ok +[23:04:43] wired: well, like you say, if was critical, they would have fixed it +[23:04:52] ayoy: yes thats what i believe as well +[23:04:52] and Qt 4.6 comes out ~December maybe +[23:04:56] fedora has bleeding edge svn gcc version +[23:05:06] they wouldn't leave their only stable release broken +[23:05:09] i hope +[23:05:10] since its test ground for rhel +[23:05:14] exactly +[23:05:21] ok, next please +[23:05:27] right +[23:05:28] it's QVector and QMap that are the issues, I think +[23:05:28] /usr/include/qt4/QtCore/qmap.h:588: warning: dereferencing pointer 'y' does break strict-aliasing rules +[23:05:28] /usr/include/qt4/QtCore/qvector.h:315: warning: dereferencing pointer 'pretmp.11332' does break strict-aliasing rules +[23:05:29] btw, new OpenSuSE uses 4.4 iirc +[23:05:46] we're dwlling on this, lets do our research and return +[23:05:49] dwelling +[23:05:55] wtf is wrong with me today +[23:06:10] next item +[23:06:19] next topic - Qt 4.5.2 stab (ilization) +[23:06:22] yeah +[23:06:28] do it! +[23:06:57] I mean - now - it fixes several issues with kde (including webkit crashes in quassel) +[23:06:59] i don't see why not +[23:07:14] also it makes kdevelop katepart faster (using raster) +[23:07:18] is the exceptions flag issue fixed in the tree already? +[23:07:25] no +[23:07:32] and there's no issue with exceptions in 4.5 +[23:08:02] ayoy: is there a reason to touch exceptions in intree 4.5 ebuilds? +[23:08:05] please leave 4.5 alone +[23:08:26] well, what was the thing that we tested in overlay? +[23:08:30] don't touch, cc arches :) +[23:08:32] not 4.5-related?... +[23:08:50] ayoy: you mean 4.6 tech preview 1? +[23:09:03] i really don't know why we added that flag for 4.5 +[23:09:03] xml-patterns dependent on core w/exceptions +[23:09:05] is it for 4.6? +[23:09:08] yes +[23:09:08] thats 4.6 +[23:09:11] aahhhh +[23:09:12] 4.5 doesn't need it +[23:09:13] sorry :) +[23:09:28] any outstanding bugs in 4.5.2 im unaware of? +[23:09:41] *** Joins: tkmorris (n=unknown@201-66-183-55.paemt704.dsl.brasiltelecom.net.br) +[23:09:47] (how is sip/pyqt4 btw?) +[23:09:48] i don't see any +[23:10:25] reavertm: bug 284707 +[23:10:42] http://bugs.gentoo.org/show_bug.cgi?id=284707 +[23:11:15] very well +[23:11:23] we need Wilkins here +[23:11:56] ok, are we done iin this topic? +[23:12:11] ok then who wants to open the stablereq bug? +[23:13:00] wired: seems like you +[23:13:05] heheh +[23:13:08] alright +[23:13:12] i'll do it +[23:13:16] next item +[23:13:24] eclass unitests +[23:13:32] yeah, I think we could use some +[23:13:39] in kde world at least +[23:14:05] to verify blocks/dependencies,- in general kde-functions +[23:14:41] just a general idea, what do you think +[23:15:03] sounds interesting as for me +[23:15:11] tests to make sure blocks/deps are correct? +[23:15:16] yes +[23:15:16] unit tests are usually a good idea for regression testing +[23:15:26] sounds good +[23:15:26] sto avoid further breakages in eclasses +[23:15:54] sorry guys, I'm being swampped elsewhere. Please poke me if you need anything from me +[23:16:01] sure +[23:16:06] jmbsvicetto: np, whats your thought on unittests? :P +[23:16:36] so.. reavertm you're on this? +[23:16:45] I think nobody really objects, just someone will need to do it +[23:16:54] i may start wriing simple tests +[23:17:03] a headstart would be nice +[23:17:08] ok, next item +[23:17:14] great +[23:17:15] jmbsvicetto: sets :) +[23:17:16] sets +[23:17:48] https://bugs.gentoo.org/show_bug.cgi?id=272488 +[23:17:56] I filed following bug ^ +[23:18:05] it's one of ways +[23:18:16] wired: They're always a good idea +[23:18:19] sets +[23:18:30] i think it's generally accepted fact that current sets doesn't fit best +[23:18:33] sorry, wired I meant about unittests +[23:18:40] reavertm: agreed on that +[23:18:46] jmbsvicetto: ok, reavertm will do the start +[23:19:05] reavertm: yeah i've read that bug, its interesting +[23:19:09] This is another email I'm "owing" us +[23:19:10] so,I wanted to bring your attention on discussion about sets +[23:19:12] but it seems the whole sets thing is "stale" +[23:19:25] is anything being developed by zac/portage team? +[23:19:46] wired: no interest - no need to make progress +[23:20:13] if we present strong interest in some idea, zac may start coding +[23:20:41] PROPERTIES=set has this nice feature that most of syntax is already there and may need a litlle work just to get it done +[23:21:00] (with no operators supported - operators have been disabled from sets anyway) +[23:21:21] s/a little/little/ +[23:21:42] so, please read this bug, form some opinion and comment on this bug +[23:21:48] I think this is everything from me +[23:22:12] anyone any ideas/comments? +[23:22:22] reavertm: I think PROPERTIES="sets" has some interesting points and may be useful in some cases, but I still think the "original" sets are in general better for KDE +[23:22:37] reavertm: very interesting idea +[23:22:48] jmbsvicetto: only for live maybe +[23:22:53] Pesa: it's zac idea :P +[23:23:03] reavertm: I do need to write something about it and until I do, I should shut up as I'm not providing ideas for others to be able to comment on +[23:23:21] jmbsvicetto: ;) +[23:23:29] jmbsvicetto: you did have another idea, no? :) +[23:23:59] properties set would only need us to maintain 'metapackages' +[23:24:25] and i personally don't need anything else (even as a maintainer) +[23:24:49] wired: my main point is that a list of package atoms can be more versatile +[23:25:05] jmbsvicetto: USE flags? +[23:25:10] wired: just to give you an example, I think that would be a clever way to fix the PDEPEND problem of QT +[23:25:20] or dedicated USE_EXPAND variable? +[23:25:26] jmbsvicetto: maybe instead of trying to write a spec, you could write a short comment @ reavertm's bug to get discussion going? +[23:25:38] reavertm: I know what you mean and that's where optional deps would need to be supported by sets +[23:25:41] (comment with a short description of what you're thinking) +[23:26:11] wired: I'm not planning to write a spec, but I need to tie myself to a chair and write a few ideas before I can get people talking about them ;) +[23:26:18] heheheh +[23:26:28] you could trying the other way around +[23:26:36] start a discussion and let it tie you to the chair to answer +[23:26:38] :) +[23:26:53] you mean trolling? :) +[23:27:13] throwing ideas to each other isn't necessarilly trolling :) +[23:27:44] reavertm: maybe you could ask zac to make a sample implementation of properties +[23:27:48] if its easy to implement +[23:28:21] for us to verify it's usefulness? :P +[23:28:30] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) +[23:28:41] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) +[23:28:46] if its easy to implement yeah, itd be nice to have some hands on and might give us more ideas +[23:29:24] wired: just imagine metapackage that pulls everything it's listed there even when uninstalled :P +[23:29:31] some new portage guy could also do it for excersice :P +[23:29:31] exercise +[23:29:41] reavertm: That's what metapackages already do ;) +[23:29:44] this is what properties=set is +[23:29:54] jmbsvicetto: uninstalled... +[23:30:04] or reemerged +[23:30:20] reavertm: The new behaviour is for meta packages to pull all packages when they're already installed and or to remove all packages when uninstalling +[23:30:37] reavertm: ok, you meant uninstalling +[23:30:43] 'new behaviour'? never heard of it +[23:31:25] reavertm: I mean that the goal of the PROPERTIES="set" proposal is to have the PM do that with those meta-packages - thus it's a new behaviour +[23:31:27] yes, so it's easy to imagine how it works +[23:31:36] sure +[23:31:42] wired: ^ :P +[23:31:52] :) +[23:32:03] ok so we didn't get anywhere with sets +[23:32:10] of course, for official implementation it will need GLEP and such +[23:32:15] It doesn't address the optional deps (and I don't mean the use deps) and or set operations (math set operations) +[23:32:34] which could be very useful +[23:32:45] jmbsvicetto: what is 'optional deps'? USE_EXPAND variable wouldn't work? +[23:32:58] let me give an example +[23:33:05] operators - of course - we could use those +[23:33:13] (but not really blocker for me :P) +[23:33:27] let's say we want to have in the @kdebase set, kdebase-startkde as the only required dep (with all of its deps) +[23:34:07] So anyone having @kdebase in their system could remove at will any package in the @kdebase set and the PM would respect it, except if it was kdebase-startkde or one of its deps +[23:34:46] So emerge -uDav @kdebase would only update the installed packages - would work by default as emerge -uDav @kdebase/@installed +[23:34:49] so 'install all by default' but allow uninstall +[23:34:55] yes +[23:35:20] please comment on bug :) +[23:35:21] For instance, I might want to have the @kdenetwork set, but I really hate krfb and I don't want it around +[23:35:25] hehe +[23:35:34] how do you reemerge the whole set? +[23:35:39] @kdebase/@all ? +[23:35:45] wired: ^^ See, I'm already being asked to tie myself to chair ;) +[23:35:53] jmbsvicetto: yeah, it worked +[23:35:55] jmbsvicetto: :D +[23:36:04] jmbsvicetto: keep going! =] +[23:36:40] wired: That would need some discussion and documentation, but I could see emerge -uDav @ only updating the installed (and required deps) and emerge -av @ installing all packages in the set +[23:36:43] --keep-going +[23:36:50] you can attach channel log :P +[23:36:52] --jobs=5 +[23:36:58] -jobs=512 +[23:37:05] no @ oeprators +[23:37:19] keep it simple and stupid :P +[23:37:30] alright, so this should continue in bug, we should all ping jmbsvicetto once a day to tie him to the chair +[23:37:33] :D +[23:37:42] The tricky part is that the PM will need to store sets and need to use them for dep resolution +[23:37:50] hehe +[23:37:52] but is there. just needs attention +[23:38:04] bug* +[23:38:22] reavertm: another example - emerge -C @kdebase - 3 years from now when the sets are long gone ;) +[23:38:50] EAPI="10" ? :) +[23:39:06] but we should start to make people forget about '@' :P +[23:39:38] alright +[23:39:43] ok, anythig else +[23:39:44] we're closing in 2 hours +[23:39:52] reavertm: you wanted something extra to discuss about? +[23:40:10] ah yes +[23:40:18] versioning eclasses +[23:40:35] I think we really need that +[23:40:42] but just as 'stamp eclass version to be able to guess from 'environment' which eclass is really used +[23:41:19] some EVERSION_kde4_base=number (incremented with every file.eclass commit) would work +[23:41:27] reavertm: versioned eclasses were a good idea that never took off +[23:41:37] I could be even posisble to do it as pre-commit hook +[23:41:50] reavertm: that sounds doable +[23:42:02] reavertm: hmm, let me check something +[23:42:04] jmbsvicetto: I only would like to stamp version, not use for dependencies or such +[23:42:18] reavertm: what for then? +[23:42:25] reavertm: what you want is already there - # $Header$ +[23:42:44] reavertm: what we need is a way to put that in the environment.bz2 +[23:42:45] jmbsvicetto: but it's not in environmeny as varianle +[23:42:52] yes, I understand +[23:42:59] reavertm: but there might be a way to get it +[23:43:35] reavertm: hmm, thinking a few more seconds about it, are you sure it's not there? +[23:43:46] reavertm: iirc, the complete eclass is supposed to be in environment.bz2 +[23:44:15] with all comments stripped +[23:45:06] export "EVERSION_${ECLASS//-/_}"=1 +[23:45:15] for simple manual approach +[23:45:30] some quick thinking, could we have eclass wrappers loading "custom-versioned" eclasses based on ebuild PN/PVs? +[23:45:32] (pre-commit hook would be more clever) +[23:45:37] reavertm: right +[23:45:46] reavertm: maybe we could ask Zac to keep the version in the file +[23:45:57] reavertm: It seems to me it would be very useful for other cases as well +[23:46:08] how would he gather such info? +[23:46:14] He already does +[23:46:33] i mean, eclass version +[23:46:48] what he he does is checking some timestamp I suppose +[23:46:49] environment.bz2 picks the used eclasses. Currently the comments are being stripped, but it seems it could be useful to keep the 3rd line in the eclass +[23:47:23] reavertm: I'm going after a "simpler" solution +[23:47:32] avoid using anything CVS specific as we might want to move away from that one day +[23:47:35] yeah, and may even be sufficient +[23:47:53] if that was doable we could have kde4-meta in ebuilds, kde4-meta-1 and kde4-meta-2 for example and kde4-meta would inherit per case, wouldn't that be easy to implement and practical? +[23:48:02] jmbsvicetto: actually it won't +[23:48:17] reavertm: why not? +[23:48:35] jmbsvicetto: or at least we should set out own header in pre-commit anyway +[23:48:57] spatz: The current discussions include using the git md5 for similar purpose +[23:49:00] (as overlay eclasses are usually copy-paste to tree, so don't have cvs version signature) +[23:49:16] reavertm: but the minute you commit an eclass to the tree, it gets a version +[23:49:32] reavertm: and we could be using commit hooks in the overlay for the same goal +[23:49:33] jmbsvicetto: the point is I don't want to work it only with tree +[23:49:49] yes, ^ +[23:50:08] "or at least we should set out own header in pre-commit anyway" +[23:50:09] I'm not arguing against commit hooks, just saying that for the tree we already have it ;) +[23:50:12] jmbsvicetto: reavertm is what im saying doable? +[23:50:41] * reavertm reads +[23:50:49] wired: I'm too tired to think about it and am I'm no expert, but I think invariancy rules don't allow that +[23:50:57] -am +[23:51:22] wired: but it includes some eclass dependencies +[23:51:28] wired: or you'll have to use the "safe vars" to do that if/case +[23:51:29] sure it's easy to be done +[23:51:51] think eclass bumping, big version changes would not affect old ebuilds/eclasses if that worked +[23:52:00] and we don't need to get eclass versioning in portage +[23:52:29] anyway, are we done for tonight? +[23:52:34] it's just a matter what inherit depending on PV +[23:52:40] I think we are +[23:52:43] reavertm: i know, i wonder if portage would like it +[23:52:46] we are +[23:52:50] unless anyone wants to add something +[23:52:53] reavertm: PV is one of the "safe vars" ;) +[23:53:14] its seems noone wants +[23:53:19] dismissed +[23:53:20] jmbsvicetto: it's not safe unless it's marked readonly :) +[23:53:33] :) +[23:53:34] meeting ends, until next thursday :) +[23:53:49] wired: can you please upload the log to the kde project space? +[23:53:56] I can do the summary in the weekend +[23:54:35] jmbsvicetto: cvs? sure +[23:58:48] *** Parts: ayoy (n=ayoy@gentoo/developer/ayoy) diff --git a/meeting-logs/20090924.txt b/meeting-logs/20090924.txt new file mode 100644 index 0000000..d82099c --- /dev/null +++ b/meeting-logs/20090924.txt @@ -0,0 +1,230 @@ +[22:07:55] sooooo +[22:07:59] who's here? +[22:07:59] that would rock :) +[22:08:16] meetings are quite understaffed recently :P +[22:08:21] yeah i have a feeling +[22:08:23] here +[22:08:24] blame scarabeus +[22:08:26] we'll be missing a lot today +[22:08:27] I'm here +[22:08:35] ROLLCALL :D +[22:08:52] * ABCD is here +[22:08:57] * reavertm reporting +[22:08:58] <--tampakrap but due to family issues i may leave without notice +[22:09:29] *** Joins: alexxy (n=alexxy@gentoo/developer/alexxy) +[22:09:36] hi all +[22:09:42] yo +[22:09:44] heya alexxy +[22:09:46] hey alexxy +[22:09:50] shouting brings ppl +[22:09:52] * wired is impressed +[22:10:08] it's good you're here alexxy because I've planned last minute agenda topic that is sort of related to you :) +[22:10:13] lol +[22:10:23] he wont be happy +[22:10:24] :p +[22:10:33] I think in longer run he will +[22:10:39] :) +[22:10:39] hehe +[22:10:46] omg =) +[22:10:49] so lets wait 5 more minutes +[22:11:09] maybe jmbsvicetto and bonsaikitten will show up +[22:11:41] we're also missing spatz +[22:12:53] * wired orders some food +[22:13:38] btw i have a rather unstable internet connection these days, so i may disappear in the middle of the meeting :( +[22:14:40] jmbsvicetto mentioned to me he might not make it +[22:14:59] and I'm present, but not conscious +[22:15:10] * reavertm slaps bonsaikitten +[22:19:25] alright +[22:19:30] lets begin +[22:19:35] Hi +[22:19:38] w00t +[22:19:42] that's timing +[22:19:42] :p +[22:19:48] yeah +[22:20:02] hey boss +[22:20:14] but i'll leave sorry +[22:20:34] cya +[22:20:59] Hi everyone +[22:21:04] jmbsvicetto: :) +[22:21:04] hi :) +[22:21:10] I'm also present, but not very "conscious" +[22:21:33] maybe we should look into that, it seems to be spreading +[22:21:33] :p +[22:21:43] ok.. +[22:21:54] lets start with kde stabilization +[22:22:07] can someone please outline the current bugs state? +[22:22:26] there are a few left +[22:22:57] two java (some hotspot issue with non-sun jvms) related, two grub issues (patch is attached to one of them) +[22:23:14] some deps are also pending stabilisation +[22:23:42] I've eliminated two more today (one as test-request and second marked as not blocking stabilization) +[22:24:15] anything we can't solve in the following days, or something we should focus on? +[22:24:21] *** Parts: nim_ (n=nim@adsl14-107.lsf.forthnet.gr) +[22:24:32] Pesa: one is probably yours? (consolekit and dbus related) +[22:24:58] yep, it shouldn't block stabilization imho +[22:25:07] it's not a regression afaik +[22:25:11] one could try to applyt hat grub patch from bug 242736 and see whether it works +[22:25:21] i'll try that +[22:25:36] We need to apply all the patches sent to the packagers ml +[22:25:44] jmbsvicetto: in overlay +[22:25:44] it's nice to see policykit went stable on x86/amd64 +[22:25:55] In particular the ones that prevent some kdepim packages from crashing and kmail from eating imap mails +[22:26:04] reavertm: Great! Thanks +[22:26:06] https://bugs.gentoo.org/show_bug.cgi?id=241638 - also sci team would need to add some pkg_postinst +[22:26:13] nice +[22:26:20] jmbsvicetto: only ldap. I yet to see imap crash patch posted +[22:26:40] reavertm: hmm, I could swear I noticed an email about that +[22:27:04] well, my 4.3.9999 branch is still crashing occasionally so it's not fixed +[22:27:37] reavertm: <200909131956.22847.mcguire@kde.org> <- mailid +[22:28:01] please someone slap sci team to add that pkg_postinst message about the possible need to reemerge cln and/or libqualculate in case some linking problems appear +[22:28:49] reavertm: I've forward the mail to you +[22:28:56] jmbsvicetto: ah, that one, yeah +[22:29:43] jmbsvicetto: i dont see any problems with kmail related to imap +[22:29:55] * alexxy uses it on dayly basis +[22:30:05] alexxy: its something about moving folders +[22:30:07] neither do I (use it all the time on 2 PCs) +[22:30:08] and its ugly +[22:30:09] it sometimes crashes kmail on exit +[22:30:22] iirc you can lose a folder full of emails :P +[22:30:26] alexxy: It's an upstream commit +[22:30:39] (the patch) +[22:30:39] hmm +[22:30:56] my kmail can handle imaps folders with 100k+ mails +[22:30:59] the only problem I can see with kmail/kontact is that it sometimes lunches two instances on startup and when you close any of them it crashes +[22:31:09] someone needs to bump doxygen 1.6.1 to fix bug https://bugs.gentoo.org/show_bug.cgi?id=282598 +[22:32:06] https://bugs.gentoo.org/show_bug.cgi?id=275326 can be probably maked as non-blocker since java is now enabled by default (and there's postinst message warning that redland is known to not work) +[22:32:19] (btw it seems to be fixed in trunk soprano) +[22:32:45] sounds good +[22:33:05] reavertm: mind adding all the bugs you know about as blockers to the stabilization bug? +[22:33:29] jmbsvicetto: I'm just reading this list +[22:33:38] about doxygen - if nerdboy doesnt bump it in the next few days we can do it i guess +[22:33:48] if there are some new 4.3.1 issues that should be maked as blockers, then wel... +[22:33:53] Also, can anyone please open bugs for the KDE deps (automoc, strigi, soprano, phonon, etc), assign it to us and cc amd64 / x86? +[22:34:34] I'll create stabilization list for 4.3.1 +[22:35:33] ok +[22:35:35] separate bug for each dep? +[22:35:49] jmbsvicetto? +[22:35:53] In this case, we can have a single bug for all deps +[22:36:54] I'd like someone (or more of you) to take a look at recent 4.3.1 bugs that may be considered blockers +[22:36:55] alright +[22:37:29] if you're bored that is :) +[22:37:31] i'll have a look this weekend +[22:37:47] reavertm: I want to start looking at some, but work is leaving me dead tired when I finally get home :\ +[22:38:03] jmbsvicetto++ i have the same issue and this weekend im working... +[22:38:06] stupid deadlines +[22:38:23] ok, I think that's it when it comes to kde stabilization, anything else here? +[22:38:29] alright, anything else pending for stabilization? +[22:38:43] lets move on to Qt +[22:38:47] before we talk about gcc +[22:38:53] quick update on stabilization +[22:39:07] after talking with yngwin i pushed news item in -dev +[22:39:13] about the use flag changes +[22:39:26] i'll request stabilization after I've added the news item +[22:39:38] probably on saturday +[22:39:46] since i need to wait 72 hours +[22:39:53] nice :) +[22:39:55] cool +[22:40:05] sooooo +[22:40:21] did anyone get any info, crashes or anything else on qt 4.5 w/ gcc 4.4 combo? +[22:40:26] gcc and qt4.. +[22:40:32] no! +[22:40:39] ftr no crashes for me +[22:40:47] nope +[22:41:00] nope. I'm using 4.4.1 and 4.5.2 and all is fine +[22:41:02] it may not be that severe considering no other distros I looked into made any patches for aliasing +[22:41:14] reavertm: did you talk with upstream? +[22:41:16] wired: still no noticeable crashes here +[22:41:35] anyway - it affects all template classes like QHash, QList, QMap, QVector and maybe some other +[22:41:40] also no crasghes here with qt-4.5.x +[22:41:46] well +[22:41:51] if no one can replicate crashes +[22:41:57] worksforme +[22:42:02] :) +[22:42:06] it may be enough to add -fno-strict-aliasing somewhere to make it even less severe +[22:42:28] we could +[22:42:31] other way (thiago asuggested) is to simply (providing it's simple) - backport those classes from 4.6 +[22:42:44] but why bother touching something +[22:42:45] that works +[22:42:48] keep in mind +[22:42:52] that users are best testers +[22:42:56] and we don't have bug reports :) +[22:42:59] thats a good sign :P +[22:43:05] * alexxy has several crashes with qt-4.6 and kde4 and amarok +[22:43:21] well, yes, we may need to wait for some fireworks because maybe it's not really needed +[22:43:41] where would you add -fno-strict-aliasing? remeber those classes are templates... +[22:43:44] Oh, let me thank whoever has been doing the latest taglib{-extras} and amarok bumps +[22:44:09] if we wake one morning and bugzilla is full of Qt4 crash duplicates we'll worry about it, but seriously this is fud, there's no way they wont fix it if it ever breaks +[22:44:31] wired: fine with me +[22:44:47] well, this may not be a fud, but we've seen several aliasing-related warnings on gentoo for multiple packages +[22:44:59] so it's not a reason for panic +[22:45:19] alright +[22:45:28] so, let's wait for user/testers feedback, hmm? +[22:45:31] thats settled until a storm comes then +[22:45:39] :) +[22:45:39] ok +[22:45:44] reavertm: your floor :) +[22:45:50] last (hidden) agenda item :) +[22:46:00] I've had a couple of crashes that might be related, but I can't be sure +[22:46:25] ABCD: gather coredumps and/or just backtraces then +[22:47:06] last agenda item - stop shipping unstable svn snapshots - several reasons: +[22:47:26] - they need to be repacked (not really an issue) +[22:47:38] - they are known to be broken +[22:48:10] - they somewhat distract users from using tagged packages in portage (4.3.1) and such +[22:48:47] i dont really mind, but yeah, especially the early ones could be avoided +[22:48:51] for users' sake +[22:48:55] (of course we're not talking about dropping beta1, beta2, rc1, rc2 .. releases as those have some tagging involved, not just auto-tagging) +[22:48:57] what about providing only beta/rc version? +[22:49:06] lol nvm +[22:50:07] alexxy: you used to bump them, what do you think about not doing it anymore? :) +[22:51:37] well there some people who relay use them =) +[22:52:03] alexxy: apart from yourself? :) +[22:52:12] yep +[22:52:26] sorry, phone +[22:52:33] I say if someone wants to do them let's have snapshots +[22:53:02] as long as we have alexxy to make em eh? :P +[22:53:05] the point is, people come here and report that they are broken (like pykde4 + some temporary svn issues) and expect us to fix it +[22:53:28] and I'd prefer kde devs were not bothered with this :P +[22:53:57] oh, and they makes repoman full takes longer :) +[22:54:18] we could add ewarn-that-no-one-reads to snapshot ebuilds *** NO SUPPORT ANYWHERE *** :P +[22:54:21] reavertm: then simply add something like +[22:54:22] (whatever this means in english :P) +[22:54:35] reavertm: I agree with bonsaikitten, but we should add a note that may have been lost with time - let's add a pkg_postinst for those ebuilds telling users not to report bugs to Gentoo +[22:54:42] snapshot is known to be broken so report all busg about them to bugs.kde.org +[22:54:43] =) +[22:54:46] to eclass +[22:54:53] omg +[22:55:03] something like that, yes +[22:55:10] they'll come down to us with grenades man +[22:55:11] lol +[22:55:15] also - less versions - less synchronization work +[22:55:17] okay with me, so long as it's conditional on [[ -z ${I_KNOW_WHAT_I_AM_DOING} ]] :) +[22:55:28] (the message, that is :) ) +[22:55:31] I know not all of you do ebuild synchornization work but.... :) +[22:55:58] and I don't mind dropping those versions, either :) +[22:56:13] at least I'm not going to touch them anymore +[22:56:59] and I don't want to see blocks involving 4.3.56 -> 4.3.57 changes in ebuilds :P +[22:57:11] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) +[22:57:12] so lets leave it at "as long as someone is interested lets keep em and add a fat warning in eclass" +[22:58:03] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) +[22:58:12] great +[22:58:15] actually we should only provide blocks that involve versions that are going to be in tree +[22:59:11] pesa [21:57:13] so lets leave it at "as long as someone is interested lets keep em and add a fat warning in eclass" +[22:59:40] fine with me, thanks :) +[22:59:57] i don't really use them +[23:00:34] reavertm: why? if something has rdep "! so, anything else left for today? +[23:01:18] i think we're good +[23:01:22] assuming all goes well +[23:01:35] next week we'll be ready +[23:01:47] ABCD: it's about always increasing bloat and complexity of those blocks +[23:01:48] whoever closes the last blocking bug should bug all the rest +[23:02:06] and begin stab(ilization) procedures :) +[23:02:29] reavertm: that's why I created a add_blocker function that takes care of all that stuff [except that I was told I shouldn't use it yet...] +[23:02:39] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) +[23:02:52] ok, then I'm going to do something "stupid" like watching tv or playing a stupid psp game ;) +[23:02:55] I know +[23:03:23] jmbsvicetto: yay! heheh, i'll fire up my xbox :P +[23:03:45] :) +[23:03:48] later +[23:03:53] meeting end! +[23:04:00] jmbsvicetto: i'll add log same place :) +[23:04:24] wired: thanks diff --git a/meeting-logs/20091119.txt b/meeting-logs/20091119.txt new file mode 100644 index 0000000..7f1c17b --- /dev/null +++ b/meeting-logs/20091119.txt @@ -0,0 +1,959 @@ +[20:45:05] toum toum +[20:46:51] sssh +[20:48:34] *** scarabeus changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 1: Upstream split packages (per kde-scm-interest mail i told you to read)' +[20:52:39] *** Joins: zizo (n=Zizo@host214-182-dynamic.4-87-r.retail.telecomitalia.it) +[20:52:59] *** Parts: zizo (n=Zizo@host214-182-dynamic.4-87-r.retail.telecomitalia.it) +[20:56:35] *** Joins: PSYCHO___ (n=scarabeu@gentoo/developer/scarabeus) +[20:56:35] *** ChanServ sets mode: +o PSYCHO___ +[20:57:05] darn 3g con +[20:59:38] so... meeting time? :) +[21:01:16] yup +[21:01:19] indeed +[21:01:27] anyone can record the histroy? +[21:01:38] i cant log, because quassel is not entirely cooperating right now +[21:01:39] * wired logging +[21:01:48] for the log <- scarabeus +[21:02:04] ok so lets start with rollcall +[21:02:05] even if I seem down my znc/bouncer will keep logging, im on a 3g connection right now (dsl is down) +[21:02:33] *** Joins: spatz (n=spatz@gentoo/developer/spatz) +[21:03:18] *** Joins: ayoy (n=ayoy@gentoo/developer/ayoy) +[21:03:39] *** Joins: mrpouet (n=quassel@gentoo/developer/mrpouet) +[21:03:45] ok so anyone else here? +[21:04:02] *** Joins: wohnout (n=wohnout@88.86.113.238) +[21:04:02] me +[21:04:09] you are so lame +[21:04:11] me +[21:04:12] !herd kde +[21:04:13] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, ssuominen, tampakrap, tgurr, wired +[21:04:13] * wired here +[21:04:13] and me +[21:04:17] !herd qt +[21:04:18] (qt) abcd, ayoy, carlo, hwoarang, spatz, tampakrap, wired, yngwin +[21:04:18] PSYCHO___: stop talking and start working +[21:04:19] roll call +[21:04:22] present +[21:04:22] :D +[21:04:24] I'm here +[21:04:27] HERE +[21:04:46] only qt people +[21:04:52] spatz: it is required only to say it once +[21:04:53] mostly present +[21:04:58] while(1) printf("HERE\n"); :D +[21:05:03] PSYCHO___: here :D +[21:05:04] okay ==> [ ] +[21:05:34] some get kde 3.5 killer... errr.... ssuominen here as well! :P +[21:05:43] ok thats not exactly attendance i expected +[21:06:10] scarabeus: lets wait at least 5 more minutes +[21:06:42] im also worried that some people might show up in an hour or so... +[21:06:46] ok +[21:06:59] because of DST? +[21:07:04] *** Joins: Sput (n=sputnick@quassel/developer/sput) +[21:07:04] yeah +[21:07:15] happened last time +[21:07:23] they can use date -u +[21:07:29] so thats not exactly excuse +[21:07:45] no'ones trying to excuse them +[21:07:47] dst stinks +[21:07:47] :P +[21:07:56] * spatz uses date -u +[21:09:17] so? +[21:09:28] so +[21:09:28] agenda? +[21:09:30] time's up, lets go! +[21:09:42] yngwin: agenda is on -desktop-ml in that mails +[21:09:43] scarb has first item @ /topic +[21:10:00] i will put them onto the topic as we will be going +[21:10:03] thats scattered +[21:10:22] * wired fixes agenda +[21:12:07] ok +[21:12:09] agenda: http://dpaste.com/122485/ +[21:12:30] thanks +[21:12:32] read it while i clean it up a bit +[21:13:00] what about starting from Qt since KDE has a lot to talk about? +[21:13:52] Ingmar: btw are you around? +[21:14:14] updated agenda: http://dpaste.com/122486/ +[21:14:36] ok lets roll +[21:14:51] 21.15 already +[21:14:58] true +[21:15:03] PSYCHO___: are you presiding? +[21:16:02] ok so lets start +[21:16:06] i was smashing my net a bit +[21:16:48] internet has swine flu +[21:17:26] yeah looks so +[21:17:29] * wired whistles +[21:17:36] !herd kde +[21:17:37] PSYCHO___: (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, ssuominen, tampakrap, tgurr, wired +[21:17:38] aarfff dinner time :( +[21:17:42] so listen up +[21:18:08] anyone of you did read that mail from Ingmar? or you just idled like usual? +[21:18:21] yes we did +[21:18:22] * spatz read it +[21:18:25] * wired did read it +[21:18:27] i did +[21:18:36] http://article.gmane.org/gmane.comp.kde.scm-interest/724 +[21:18:46] there is my response to that mail thread +[21:19:06] give us a min to read +[21:19:08] it is how i imagine layout that would suit us packagesr best +[21:20:29] *** Joins: j0 (n=quassel@g227216073.adsl.alicedsl.de) +[21:20:29] anyway the question that waits here: "Is anyone willing to work on this?" +[21:21:15] yes +[21:21:26] did you get any response from upstream? +[21:21:33] nope, this mail is last in that thread +[21:22:16] so we are waiting until upstream responds to that first, or not? +[21:22:39] actualy nope, i expect someone coordinate with ingmar and prepare full proposal to them +[21:22:55] because my 6 lines about layout are not exactly "full proposal" +[21:23:00] upstream surely knew we have split kde +[21:23:11] yes they do +[21:23:12] the real question is, do they really want to take this route? +[21:23:40] well some stated that they would like it, some otherwise +[21:23:48] i've also seen discussions about splitting in the past going nowhere (two at least) but never mind +[21:24:10] well this time they are migrating to another SCM so it might have better chance to win :] +[21:24:18] agreed +[21:24:42] does Ingmar (ping) have anything else to say in this topic? (apart from what you said in the mail?) +[21:25:19] well he is aparently not around, so the interested person will have to mail him or irc him at some better time +[21:25:30] do binary distros (pretty much everybody) have split packages or monolithic ones? +[21:25:46] debian has them split +[21:25:52] after compilation tho +[21:25:56] hello +[21:26:05] they compile them in monolithic way and ship them in split way +[21:26:08] hey Ingmar +[21:26:09] scarabeus, tampakrap hi +[21:26:18] hello +[21:26:54] doesn't matter how they do it, only whether they do it. if this change forces everybody to split their packages whereas now they have monolithic ones we might face some opposition +[21:26:56] scarabeus: as you said, i'd like to see upstream move to a buildsystem layout more similar to what xorg has +[21:27:19] scarabeus: i'm less interested in splitting out the libs, or base, but the debian packager i talked to found that more important than anything else +[21:27:34] spatz: other distros follow upstream's way, so they will be forced to change it +[21:27:36] presumably because they can easily split the rest after buil +[21:27:39] d +[21:27:45] s/can/can & already do/ +[21:28:21] well from what we can say the initiative to do the thing will have to cover 2 areas) explaining what to do and how ) showing some example repo done that way +[21:29:04] yeah +[21:30:04] so ANY volunteers for this? +[21:30:09] yes +[21:30:21] and you? +[21:30:29] Ingmar: also i would like to see at least one relevant upstream guy acking that we are not just wasting our time +[21:30:30] I am, obviously :) +[21:31:01] well, let's start with a proof of concept for one module +[21:31:04] i myself will try to help +[21:31:48] i'd put together a proof of cencept first & see what they say on the relevant mailinglists +[21:32:01] ok that sounds reasonable +[21:32:12] splitting kdenetwork or kdeedu might be quite easy +[21:32:24] Ingmar: did you get any affirmative responses from other packagers (and more importantly) by any upstream developer? +[21:32:51] scarabeus: i was thinking kdenetworok, so yeah :) +[21:33:09] tampakrap: packagers yes (debian & gentoo, didn't ask anyone else), didn't ask any specific upstream devs +[21:33:20] ok +[21:33:33] Ingmar: also we should steal some irc channel to have it covered, i guess we cant chit-chat on g-kde or e-kde since its bit offtopic :] +[21:33:36] on the kde-scm-interest ml, some were in favor, and some where against +[21:34:16] any name ideas? :] +[21:34:39] #kde-split +[21:34:41] /j #kde-build-split :) +[21:34:48] ok +[21:35:01] *** Parts: wohnout (n=wohnout@88.86.113.238) +[21:35:23] anything else on the subject? +[21:35:36] i would say that for meeting we covered it +[21:35:46] i personaly will try to motivate few more people +[21:35:52] but that is non-meeting subject :] +[21:36:03] Ingmar: apart from kde-scn-interest ml, any other mailing lists you'd like to see us subscribed? +[21:36:55] kde-buildsystem +[21:37:08] well, if you have more minions, you know where to send them :) +[21:37:20] okz +[21:37:41] ok i think we're done with this for now +[21:37:48] next topic plz? +[21:37:54] first topic plz :) +[21:37:55] tampakrap: now something qt i would say +[21:38:00] since there is more qters +[21:38:09] scarabeus: lets just do the agenda?! +[21:38:27] as you wish +[21:38:33] ok documentation +[21:38:41] *** scarabeus changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 1: Documentation' +[21:38:43] stabilization first +[21:38:44] *** scarabeus changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 2: Documentation' +[21:38:54] http://dpaste.com/122486/ +[21:38:56] *** scarabeus changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 1: stabilisation' +[21:39:35] ok so since only samuli is working on it with me has anyone looked on the bug +[21:39:43] or attempted to fix blocker bugs +[21:40:04] bug # plz? +[21:40:15] * wired hasn't looked at kde 4.3.3 bugs lately, but will +[21:40:25] bgu 292455 +[21:40:26] bug 292455 +[21:40:28] spatz: https://bugs.gentoo.org/292455 "KDE 4.3.3 stabilization request"; Gentoo Linux, Applications; NEW; ssuominen@g.o:kde@g.o +[21:40:41] bug 2: Documentation +[21:40:43] erm +[21:40:43] PSYCHO___: https://bugs.gentoo.org/2 "How do I attach an ebuild."; Gentoo Linux, Ebuilds; RESO, FIXE; tneidt@fidnet.com:hallski@g.o +[21:40:45] damn this +[21:40:49] as spatz said +[21:40:51] lolz +[21:41:02] lol +[21:41:28] so 13 bugs +[21:41:47] i can try to help this weekend +[21:41:50] i want each member of kde team to fix at least 1 +[21:42:28] 12 bugs, 3 stable req and 1 keyword req +[21:42:29] also i want someone to look on current open bugs +[21:42:40] and decide which should be blocking the stabling +[21:42:50] and on this i want volunteer that will actualy do it +[21:43:05] and also close the remaining kde3 bugz +[21:43:13] we can't really do much with keyword/stable requests +[21:43:43] are still there are normal bugs, and not all bugs are now blocking the stabilisation even if they should +[21:43:47] so who will do it +[21:45:13] ok i'll do it since noone is interested +[21:45:19] meaning the bug wrangling +[21:46:11] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 2: documentation' +[21:46:12] ok +[21:46:19] next topic +[21:46:41] as i stated +[21:46:54] I want devoted person focusing on updating our documentation with nedy +[21:47:02] as wired I can try to help this week end (I've an exam tomorrow and I've to finish a project) +[21:47:04] yes but i disagree with that +[21:47:45] tampakrap: so how would you do the documetnation +[21:47:53] everyone of us should just realize that documentation is *VERY* important and write two words before a major update or whatever +[21:48:01] apart from that i have another idea that you may like +[21:48:31] *** Joins: ssuominen (n=ssuomine@gentoo/developer/ssuominen) +[21:48:38] speak up :] +[21:48:43] since guidexml requires gorg in order to have a fully rendered (human readable) doc +[21:49:15] i have created an svn repo in my home server that checks out through a hook to a gorg-accessible path +[21:49:22] so it can be read immediatelly +[21:49:48] i can give access to the team here to my home server so we can *ALL* (and i mean ALL, even HTs) develop the guide +[21:49:56] no excuses about permissions etc +[21:50:13] unless you can provide us such a hook, since you have access in overlays.g.o +[21:50:14] well that was done even on git server remember +[21:50:16] I agree, so +1 +[21:50:27] i wrote complete guide in overlay as non-dev +[21:50:59] yes but i'm talking about an immediate co to an xml gentoo.org-like site +[21:51:17] which makes things easier +[21:51:25] this once again shows the shortcomings of guidexml +[21:51:42] well ok +[21:51:48] tampakrap: you then write up something and enforce it +[21:52:01] well, i don't agree with that, it shows that noone cares about docs which is sad +[21:52:38] come on, i just stated something, we can proceed in voting i guess, or go in your way then +[21:53:20] well i am willing to use it, problem is that noone else will edit it, its the same problem as is now +[21:53:36] we can give it a shot +[21:53:37] we can keep those guides in our public_html folders to see it right-away +[21:53:39] until next meeting +[21:53:42] but noone edit it anyway +[21:53:50] that's not the same +[21:53:56] but we should *also* have someone in charge +[21:54:18] well i wanted someone in charge +[21:54:22] so he can say +[21:54:26] that someone would check other commits and will _in_time_ get closer to the docs team +[21:54:30] sorry I'm late; I forgot about the time change :( +[21:54:31] i could be in charge of docs since i am the main editor a while now, but i don't like this idea +[21:54:36] You XY wrote module for AB but did not document it, so do it now. +[21:55:12] so actualy devs introducing something new will be somehow forced to do the docs +[21:55:38] because "anyone does docs and we are happy" simply is NOT working +[21:55:43] the problem is that we don't update the docs BEFORE the change (minor or major) +[21:56:31] well that would be responsibility of doc master, to point when and what needs to be changed +[21:56:35] and that won't change by itself, even if we could write the docs in speech-to-text app +[21:57:22] i dont expect the lead to do the work, but delegate to other devs, and if those wont document, i am even willing to remove them from team +[21:57:31] okay i could do that but i'd expect from the members to respect more the documentation part +[21:58:31] okay if noone has a problem with that then i'll take charge of this position +[21:58:40] *** Quits: ayoy (n=ayoy@gentoo/developer/ayoy) (Remote closed the connection) +[21:58:52] tampakrap++ +[21:58:53] *** Joins: ayoy (n=ayoy@cs78245237.pp.htv.fi) +[21:58:53] ok +[21:59:06] i'll also introduce my system to gentoo-desktop mailing list (i hope devs+HT's are subscribed there) +[21:59:09] PSYCHO___: huh ? remove them from team ? for that ? (I agree document is an important thing does not matter) ... but blame them instead +[21:59:23] while we're on the docs subject, note that I'm taking care of Qt docs +[21:59:27] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 3: upstream coordination' +[21:59:32] mrpouet: it is even more important that coding +[21:59:42] just recall what hapened when we masked kdeprefix +[21:59:46] I meant it's a bit....excessive +[21:59:51] mrpouet: its seriously important for users +[21:59:56] mrpouet: and we present our work to users +[22:00:00] tampakrap: I said that I was agree :] +[22:00:02] mrpouet: we need to be 100% covered there +[22:00:22] (document is important) but the consequence is.... excessive imho +[22:00:41] mrpouet: now noone cared, so i will be really evil until they start to care +[22:00:52] well +[22:00:55] i must say +[22:01:04] docs have always been one huge strength of gentoo +[22:01:08] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) +[22:01:13] and lately they're degrading fast +[22:01:15] PSYCHO___: sadistic :P +[22:01:17] so I like this initiative +[22:01:29] lets bring them back :) +[22:01:42] hello :) +[22:01:49] ok so lets loko onto the next toppic +[22:01:51] second late to the party +[22:01:57] :D +[22:02:01] as i can see some people had really the problem with TZ +[22:02:02] :D +[22:02:05] Pesa: hi :) +[22:02:12] Pesa: or you know that you are 1h late? :P +[22:02:17] uhm... +[22:02:20] 1h :O +[22:02:25] he does not +[22:02:27] date -u +[22:02:29] Pesa: ^^ +[22:02:32] damn! timezone :s +[22:02:43] Pesa: I had the same issue :D +[22:02:43] sorry +[22:02:50] ok so lets get to the topic :] +[22:02:56] you'll read logs, lets go! +[22:03:09] who is willing to track upstream patches, and apply them where required +[22:03:10] yep +[22:03:30] wired: or do like me, have a linux clock setting up to UTC :D +[22:03:43] this requires also requesting backports from TRUNK to branch on upstream +[22:04:50] PSYCHO___: you meant a unique guy ? other devs can't import patches from upstream ? +[22:05:03] (it's ambigous) +[22:05:11] they can, but should coordinate with him +[22:05:14] (at least for me with my fuc*$*$$* english) +[22:05:16] it can be even more people +[22:05:29] the point is that we would have the patches applied where needed +[22:05:34] in both overlay/tree +[22:05:57] PSYCHO___: mhhh... personally I could be interested +[22:06:01] Hello +[22:06:05] boss! +[22:06:06] sorry for being late +[22:06:08] jmbsvicetto: hi +[22:06:09] :) +[22:06:09] currently we mostly wait on upstream to release new version +[22:06:11] welcome jmbsvicetto +[22:06:14] hello boss +[22:07:09] Hi everyone +[22:07:16] ok, come on guys, he is half gnome, at least one more volunteer ;] +[22:07:20] its not that hard job :] +[22:07:30] i could help but not that much +[22:07:36] because i am mostly trunk user +[22:08:00] PSYCHO___: what's up? +[22:08:08] :( +[22:08:10] PSYCHO___: it's not an argument :p +[22:08:16] jmbsvicetto: you want log so far? +[22:08:17] Am I 1 hour late?? :| +[22:08:18] i want someone to coordinate patches with upstream :] +[22:08:20] I'm half gnome... and ? :D +[22:08:21] someone dedicated :] +[22:08:22] jmbsvicetto: you are :P +[22:08:49] * jmbsvicetto failed to read UTC :\ +[22:09:05] wired: yes, please (logs) +[22:09:30] jmbsvicetto: ok i'll wgetpaste then hold on +[22:09:49] PSYCHO___: reavertm and ABCD would be perfect for this i guess +[22:09:49] ABCD: how about you? dont want to do this? :] +[22:10:02] tampakrap: exactly my thinking, but reaver is not around now +[22:10:47] the silence after i ask someone something :D hilarious +[22:11:12] PSYCHO___: that would mean I'd actually have to figure out if commits to trunk are relevant/apply on the 4.3 branch... +[22:11:22] (which means more work :( ) +[22:11:26] btw, after this topic, I've another one (tiny) +[22:12:00] trunk after .70 is 90% incompatible with current branch +[22:12:19] (I'm pretty sure you will agree, but I wanted to talk about that during meeting anyway) +[22:12:28] jmbsvicetto: http://dpaste.com/122503/ +[22:12:30] ABCD: i mean more watch what bugs they fix, and ask them to patch it for branch too +[22:13:02] something like "i know you fixed crash X for trunk, but the error is in branch too, so could you fix it too so others dont have to wait for 4 months?" +[22:13:05] wired: thanks +[22:13:28] and second responsibility would be just applying what users add to bugzilla as patches from upstream +[22:13:39] deciding if it is worth or not and so on +[22:13:45] PSYCHO___: so long as someone files a Gentoo bug, and mentions the upstream bug; otherwise I'd never find it :) +[22:13:48] i dont expect that person to review all commits +[22:13:59] ABCD: thats the idea :] +[22:14:09] i dont expect you to browse the upstream one ;] +[22:14:20] in that case, it shouldn't be too difficult +[22:14:58] i know, i just want someone to do it +[22:15:07] so i wont meet 20 days open bug with patch from upstream +[22:15:29] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 4: kde3 removal' +[22:15:39] ssuominen: around? +[22:15:50] ok as you might noticed kde3 is going away +[22:15:56] next topic, ssuominen is in progress of it :P +[22:15:57] its quite flawless i can say +[22:16:04] * tampakrap points at #-commits +[22:16:09] http://dev.gentoo.org/~scarabeus/kde3almostgone.png +[22:16:09] wave your hands while you still can +[22:16:19] its going awayyyyyyyyyyyy +[22:16:19] this is what it did to our bugs +[22:16:27] so i want to hear one thing only here +[22:16:34] is something more required on that matter from us? +[22:17:17] nothing i can think of +[22:17:26] me neither +[22:17:30] ssuominen is really doing a great job with this +[22:17:31] thats why i wanted ask others +[22:17:40] bye-bye bugs :D +[22:17:57] wontfix closing is fast :P but dont get used to it :D +[22:18:10] :D +[22:18:20] lets go to RDEPENDs +[22:18:22] * tampakrap is waiting for kde5 - kde4-removal +[22:18:41] tampakrap: go ahead and write kde5 then! +[22:18:42] jmbsvicetto: boss its your area +[22:18:52] jmbsvicetto: so elaborate why rdepend use deps are bad +[22:19:30] *** Joins: pontecorvo (n=pontecor@93-183-229-187-dynamic.retail.datagroup.ua) +[22:19:36] okeey, anyone else? :] +[22:19:41] :P +[22:19:51] i personally like use flags for rdepends +[22:20:06] but i'd like to hear why they're bad from those who don't +[22:20:13] * PSYCHO___ dont care, einfo was always enough for me +[22:20:17] wired: well it is poluting the ebuild +[22:20:21] they are not entirely required +[22:20:27] its not pollution +[22:20:31] so einfo with install X for feature Y +[22:20:42] its only a few words and its helping you do things pre-emerge +[22:20:50] wired: if you stabilise package, it is polution, if you have to wait on optional rdepend to be stabilised +[22:21:07] in that case +[22:21:12] lets work on a per case basis +[22:21:41] for example, obvious or important rdepends could go in use flags, others in info +[22:21:46] that actualy might work +[22:22:33] if an rdepend disables/enables half the package's functionality, it should definately have a USE +[22:22:45] if its a hidden option in the 3rd menu from the right +[22:22:53] it could live without it :P +[22:22:56] *** Quits: pontecorvo (n=pontecor@93-183-229-187-dynamic.retail.datagroup.ua) (Remote closed the connection) +[22:23:35] but we *must* make sure we have einfo if we don't have USE +[22:23:36] make it policy +[22:23:41] thats sound sane +[22:24:05] agreed +[22:24:12] add to CODE maybe? +[22:24:15] yeah +[22:24:27] oh sorry +[22:24:30] *** Joins: pontecorvo (n=pontecor@93-183-229-187-dynamic.retail.datagroup.ua) +[22:24:30] yeah, *docs* man +[22:24:40] ok someone can grab it from summary later then +[22:24:41] :D +[22:24:41] :] +[22:24:41] sorry, reading backlog +[22:24:51] i would kick you now, but we are in meeting +[22:25:04] jmbsvicetto: not entirely smart thing to do during continuous meeting :D +[22:25:16] PSYCHO___: It isn't that rdepend use flags are bad, it's just that there are too many +[22:25:34] at least it used to be too many -> quanta was the best/worst(?) example +[22:25:53] yes, because we are following upstream +[22:26:24] jmbsvicetto: well thats why it is per decision basics +[22:26:33] svn plugin can be controled by svn useflag +[22:26:34] wired / PSYCHO___: I'm not sure they cause so many issues when marking it stable +[22:26:46] we can always have a use flag masked in a profile +[22:26:50] jmbsvicetto: I DO, i try to stable such package right now +[22:27:05] :P +[22:27:09] PSYCHO___: I was trying to catch something ;) +[22:27:16] i think what i said above is good as a rule of thumb +[22:27:43] devs should decide per case depending on the importance of the deps +[22:27:47] so we don't end up with 30 RDEPEND USE flags +[22:27:48] :p +[22:27:54] I don't have a problem with a case-by-case, but then we'll get a bug for each package that we don't provide a use flag :P +[22:28:18] wontfix, because that's how we want it +[22:28:34] or fix, because we did a second thought +[22:28:38] * jmbsvicetto puts user cloak: I want use flag X for installing package Z when I install package Y!!! +[22:28:46] http://www.pastebin.cz/26457 +[22:29:06] jmbsvicetto: we already have wontfix bugs like that +[22:29:08] Ingmar: I'll try to poke you later, but I'm also interested in upstream's work on splitting KDE +[22:29:11] its up to us, not user decision +[22:29:16] yes, I know +[22:30:28] ok, i guess we covered our last point +[22:30:34] so lets move to qt issues :] +[22:30:37] w8 +[22:30:39] wait plz +[22:30:49] mrpouet has sth to add +[22:31:04] hm? +[22:31:11] or had :P +[22:31:15] mrpouet: u here? +[22:31:21] i have to say something too +[22:31:36] tampakrap: then speak :] +[22:31:38] go ahead +[22:31:42] i'll start since mrpouet is somewhere else :P +[22:32:13] recently i fixed a bunch of live ebuilds, reported issues, patches etc +[22:33:07] since i recompile kde and qt live packages very frequently, i would like your permission to create a doc which will track live ebuilds' upstream and downstream bugs, etc +[22:33:15] which are broken and need love etc +[22:33:43] if you think that a doc is not appropriate i could do a page in gentoo-wiki for example +[22:34:11] tampakrap: go ahead, try to motivate some non-team people to help you +[22:34:18] tampakrap: so you can recruit your minions ;P +[22:34:30] on that note, we could create a script +[22:34:31] no way, you are the ht lead +[22:34:34] that picks up your daily rebuild +[22:34:44] and generates a webpage of what failed and what worked +[22:34:45] :p +[22:34:52] you mean something like dirk-dashboard? +[22:34:52] ;] +[22:34:57] contonuous integration +[22:34:57] or something like bump-tool? +[22:35:07] http://dev.gentoo.org/~scarabeus/vystup.html +[22:35:08] something like buildbot? +[22:35:27] a script that takes logs and uploads them somewhere +[22:35:29] something like that PSYCHO___ +[22:35:45] like the thing gnomies have +[22:35:49] tampakrap: well do it if you want it +[22:35:55] i can create a custom script if we don't have something ready +[22:36:03] we don't +[22:36:05] ok ok +[22:36:09] covered +[22:36:11] just give me the logs :P +[22:36:28] ok so lets moove to the qt since mrpouet is not around +[22:36:36] wait a minute +[22:36:47] it seems not covered +[22:37:06] wired: the script would be usuable if it could automatically take the build.logs from the failed packages +[22:37:11] and upload them somewhere +[22:37:33] tampakrap: its not entirely meeting material, and we have meeting already for 1h30minutes... just discuss this with wired on -kde afterwards :] +[22:37:33] yeah +[22:37:37] and we can add a comment next to each one of them, like upstream bug or whatever +[22:37:39] we'll talk about it off list +[22:37:43] off meeting* +[22:37:43] ok ok +[22:37:51] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic QT 1: qt mono package' +[22:37:58] !herd qt +[22:38:00] (qt) abcd, ayoy, carlo, hwoarang, spatz, tampakrap, wired, yngwin +[22:38:14] surprisingly i am here +[22:38:21] one of our biggest issues +[22:38:26] with the split ebuilds +[22:38:29] the USE flag madness +[22:38:31] is now solved +[22:38:38] because anything < 4.5.3 is off the tree +[22:38:41] \ö/ +[22:38:41] lol, when? +[22:38:54] i still see people struggling with it +[22:39:03] because they are updating to 4.5.3, not? +[22:39:11] yes +[22:39:12] yay +[22:39:19] once they update, we're done with this shit +[22:39:29] so its solved from our side +[22:39:50] the only thing left is the Qt update blocker madness +[22:40:01] but i think people are beginning to understand that b blocks are autosolvable +[22:40:05] but we'll still have to support latecomers for a long time +[22:40:28] we'll have to support latecomers no matter what +[22:40:39] yngwin: agreed, but that doesn't really change anything if we merge splits into a monolithic +[22:40:45] s/anything// +[22:41:05] it would, but anyway +[22:41:28] i mean, they'd still have to do some migration work +[22:41:38] like update with no blockers +[22:41:40] :) +[22:42:06] yes, but that would be clearer than the current mess with blockers and useflags - portage is just not giving very clear feedback to users +[22:42:20] i agree with the feedback thing +[22:42:45] but with the useflags issue _mostly_ gone, do you feel the blockers are good enough a reason to change things? +[22:42:52] well, we could say that that's a portage bug ;) +[22:43:09] it is mostly a portage problem yes +[22:43:16] xorg packages, for example, don't have blockers for maximum versions, only minimal, so users see less blockers +[22:43:18] well portage should shut up about autosolved blocks +[22:43:20] but we'll have to work with portage +[22:43:29] i dont understand why it writes them out +[22:43:36] qt has both maximum and minimum version blockers and that's creating weird issues +[22:43:39] most users get only confused +[22:43:43] imo the right way to do this is fix portage +[22:43:58] i really want to get into portage development but i just can't these days +[22:44:01] *** Joins: tampakrap_ (n=tampakra@ppp-94-66-145-248.home.otenet.gr) +[22:44:01] why do we need maximum version blockers? +[22:44:04] i am considering doing so in the future +[22:44:16] downgrading Qt isn't really supported anyway +[22:44:31] Sput: you can't mix Qt versions +[22:44:35] Sput: to make sure user has exactly the same version of all packages +[22:44:35] Sput: mixing versions anyhow is neither +[22:44:36] period :P +[22:44:46] wired: i'd like to too ;) +[22:44:51] yes, but the common case is upgrade, yes? +[22:45:01] again, see xorg use case +[22:45:01] to my mind this shows why we need monolithic +[22:45:06] something like MDEPEND +[22:45:07] downgrading doesn't usually work either +[22:45:08] so minimum blockers would be enough to force all qt packages be updated if one is updated +[22:45:12] if package is around then require this version +[22:45:16] otherwise do not care +[22:45:18] so called +[22:45:22] MAGIC DEPENDENCY +[22:45:29] :) +[22:45:38] with only minimum blocks users won't get blockers +[22:45:49] come on its exactly what you want, that might be actualy easy to do with current code +[22:45:55] it will just need new eapi :/ +[22:46:24] PSYCHO___: current code can't do it, i've tried to express it with complex bash but it still shells out blockers +[22:46:27] we need new depend type +[22:46:30] anyway, we said we'd discuss it on ML, which as far as i can see has not happened +[22:46:43] it did not +[22:46:44] wired: i said so, new depend type MDEPEND +[22:46:49] PSYCHO___++ +[22:46:57] who wants to start the ML discussion? +[22:46:58] and it is easy to adjust +[22:47:00] the portage code +[22:47:04] about this +[22:47:13] yngwin: I can +[22:47:19] great +[22:47:22] next topic +[22:47:35] status of qt-tng +[22:47:42] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic QT 2: Status of new qt-tng.eclass' +[22:47:56] I've been reviewing it for last 1,5 hours +[22:47:59] hwoarang said he couldnt continue with this because of circumstances +[22:48:10] i think it's ready +[22:48:12] yes so are we happy with it enough to post it in -dev? +[22:48:26] provided that we remove prepare_translations? +[22:48:45] this one seems not so handy +[22:48:52] tries to address a common case +[22:48:58] let's prepare the eclass for qt@ before sending it off to -dev +[22:48:59] but the common case doesn't really exist +[22:49:06] except there isn't a common case :) +[22:49:14] so lets remove that +[22:49:21] I will +[22:49:23] yes, we already said that +[22:49:38] ok +[22:49:47] ok, ayoy, can you finalize the eclass and send it to qt@ ? +[22:49:47] hey, btw +[22:49:48] *** Quits: tampakrap (n=tuxicity@gentoo/developer/tampakrap) (Read error: 54 (Connection reset by peer)) +[22:49:56] yngwin: yes I can +[22:50:15] great +[22:50:18] then we can all have a look and comment if needed, then send it to -dev +[22:50:21] are we all happy with the eclass name? +[22:50:26] * ayoy is not +[22:50:29] not really +[22:50:36] ayoy: i talked with picard the other day, he said he liked it +[22:50:36] you already voted on it, but didnt decide anything +[22:50:39] i am not but i don't really care +[22:50:41] qt4-edge kicks testicals very hard, I like it +[22:50:51] not -edge +[22:50:54] we need that for overlay +[22:51:03] qt4v2 +[22:51:03] else we'll have to start overriding and crap +[22:51:11] wired: you mean that qt4-edge will stay in overlay? +[22:51:17] we need eclass versioning dammit +[22:51:26] yngwin++ +[22:51:31] ayoy: yes, we need to keep developing there, don't we? :P +[22:51:37] we do +[22:51:43] yngwin: indeed +[22:51:44] indeed, wired is right +[22:51:53] I propose qt4-next :/ +[22:51:58] qt42morow +[22:51:58] better :) +[22:52:03] qt4-v2 +[22:52:08] read it ^ +[22:52:10] qt4evar +[22:52:11] in english +[22:52:16] PSYCHO___: we did :P +[22:52:33] :] +[22:52:41] qt4-blesmrt +[22:52:42] :] +[22:52:43] qt4-r2 +[22:52:45] ok, let's not waste time on bikesheds +[22:52:50] ^^ in the gentoo spirit +[22:52:54] lol +[22:52:56] :) +[22:53:09] i like that, wired +[22:53:10] this meeting is already taking 2 hours :/ +[22:53:16] let's move on +[22:53:17] * spatz likes it too +[22:53:23] :D +[22:53:25] * ayoy too +[22:53:25] so name unchanged +[22:53:27] ? +[22:53:28] ok, qt4-r2.eclass +[22:53:30] no, changed +[22:53:41] next topic +[22:53:46] w00t, we got rid of startrek +[22:53:47] ok 3. +[22:53:50] #gentoo-qt +[22:53:52] do we want it? +[22:53:58] plz no +[22:54:01] no +[22:54:02] i dont see the need +[22:54:02] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic QT 3: #gentoo-qt' +[22:54:05] I'd say we rather need a separate meeting +[22:54:09] than a separate channel +[22:54:11] its already registered and when i was bored I added permissions +[22:54:18] so if you ever feel like it +[22:54:18] :) +[22:54:24] ok, but plz no +[22:54:26] :) +[22:54:47] i think -kde is fine as well, but its there if we need it +[22:54:50] ok, so we all agree on 'no' +[22:54:57] neeeext +[22:55:01] let's keep it +[22:55:01] ok, we have a backup for a nuclear war or sth +[22:55:06] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic QT 4: einfo mess' +[22:55:12] 4. +[22:55:13] but we'll continue to use -kde for the time being +[22:55:18] it was already cleared out yesterday +[22:55:23] by wired +[22:55:23] btw DONT RUSH +[22:55:32] :D +[22:55:37] the messages only show for qt-core now +[22:55:37] qt-core only +[22:55:37] ? +[22:55:38] so I think it's better +[22:55:41] awesome +[22:55:41] tommy[d] complaint many times about this warning overload +[22:55:48] tampakrap_: i already fixed it +[22:55:51] confined it to qt-core +[22:55:54] yes, change was committed yesterday +[22:55:56] ok, I love it +[22:56:02] cool +[22:56:05] we can (and should) shorten the text, but it's much less spam now +[22:56:10] yeah +[22:56:10] if any more cutting is needed, let us know +[22:56:15] like 11 times less +[22:56:18] lol +[22:56:19] :) +[22:56:21] great, so next +[22:56:24] 5. +[22:56:25] gitorious +[22:56:30] wait +[22:56:32] we could look at the text again +[22:56:38] see if it can be shortened +[22:56:40] only downside is no commit bot coolness +[22:57:02] yngwin: i can do it +[22:57:09] i also like the suggestion to put it in out docs and refer in einfo to our docs page +[22:57:34] wired: ok, do it and let us know what you come up with +[22:57:34] thats not bad either +[22:57:38] k +[22:57:41] will mail qt@ +[22:57:47] i'll do the docs btw +[22:57:48] oooh I like that +[22:57:53] alright +[22:57:53] ok then +[22:57:55] no one thought otherwise :) +[22:57:57] why not github? +[22:58:04] next topic +[22:58:11] tampakrap_: i'll do the Qt docs +[22:58:13] many ppl don't have github accounts but want overlay access +[22:58:17] keep it split so we actually do something +[22:58:24] they can create +[22:58:25] or die +[22:58:37] and gitorious is the new black, or something +[22:58:45] oh +[22:58:48] * ayoy checks +[22:58:53] i like gitorious because you an have more people administer the repo +[22:59:03] can* +[22:59:06] it's better in most ways, except cia.vc integration +[22:59:12] I like the bot we have in #-kde +[22:59:13] the only real disadvantage is cia +[22:59:17] do we care enough? +[22:59:17] i am now the bus factor for github +[22:59:18] yngwin: good point +[22:59:38] no +[22:59:40] i mean kde doesn't have cia either, big deal +[22:59:41] I do only a bit +[22:59:58] not really, cia bot is nice, but there are other ways +[23:00:04] i like the cia wow factor as well, but if gitorious is better/more reliable/more popular +[23:00:09] like capslock +[23:00:11] my commit number got too high because of qting-edge, i almost lost my gentoo/slacker cloak +[23:00:13] lets go there and switch the hooks to keep github in sync +[23:00:25] hey hey +[23:00:26] btw +[23:00:26] ! +[23:00:36] if we switch to gitorious +[23:00:41] we still have github as a backup, no? +[23:00:47] we still have the bot +[23:00:50] period. +[23:00:54] right +[23:00:56] touche +[23:00:58] ayoy++ +[23:00:58] heh right +[23:01:00] new ppl who only have gitorious access won't be able to push to github +[23:01:02] lol +[23:01:02] :) +[23:01:10] spatz: no issues, we'll push for them +[23:01:10] so not really +[23:01:13] so vote for it +[23:01:22] yes, vote +[23:01:27] as in topic it is named as voting for gitorious as main repo +[23:01:28] gitorious +[23:01:30] +1 gitorious +[23:01:40] ok then, +1 gitorious +[23:01:46] gitorious +[23:01:46] gitorious + github as backup +[23:01:54] * spatz switches url order in .git/config +[23:02:17] ABCD? +[23:02:29] abstain +[23:02:33] ok +[23:02:37] btw can we do the same trick with kde-testing to get cia bot there as well? +[23:02:53] lol +[23:03:00] only if people actually push to gitorious as well +[23:03:06] better poke PSYCHO___ to fix it +[23:03:07] :p +[23:03:08] you mean github +[23:03:12] yeah +[23:03:13] :D +[23:03:22] if git.o.g.o has cia integration you don't have to +[23:03:23] ok last topic +[23:03:25] s/gitorious/github/ +[23:03:26] so we need to make an announcement about that, to push to gitorious as main repo, and change layman url +[23:04:05] any volunteers? +[23:04:12] announcement in like -dev? qt2? +[23:04:13] qt@? +[23:04:21] qt@ +[23:04:27] i'll do it +[23:04:30] no big deal :) +[23:05:08] im Qt PR +[23:05:09] :p +[23:05:09] last topic: removal of changelogs from overlay +[23:05:15] that one was mine +[23:05:17] also proj page +[23:05:39] lets remove them, they keep breaking my nerves, git logs are enough! +[23:05:48] NO +[23:05:48] wired++ +[23:05:58] seriously +[23:06:02] why not? +[23:06:05] i can't stand them, overlays shouldnt have changelogs +[23:06:10] duplicate info +[23:06:15] qting-edge is also a training area for new recruits / devs-to-be +[23:06:35] yngwin: most overlays are +[23:06:37] it's good practice to get used to using echangelog +[23:06:43] yngwin++ +[23:06:44] yngwin: repoman will scream anyway +[23:06:53] repoman wont scream +[23:06:57] it doesn't +[23:06:58] I think that's the least of the recruit's problems +[23:07:01] yes, that is why my policy is to use echangelog in all overlays +[23:07:02] spatz++ +[23:07:07] it doesn't scream, it warns +[23:07:10] *** Quits: nirbheek (n=nirbheek@gentoo/developer/nirbheek) ("Gone.") +[23:07:10] repoman ignores changelogs for distributed scms +[23:07:14] spatz: ^ +[23:07:17] PSYCHO___: i meant in cvs +[23:07:20] recruits should be taught to read repoman's warnings :) +[23:07:22] spatz: i wrote the code to portage, so i know about its behaviour +[23:07:32] I mean when they commit to the tree +[23:07:36] as long as portage is using cvs and echangelog, i want us to use it in the overlay +[23:07:47] i really don't like it, i forget it because this is the only overlay we use changelogs +[23:07:47] from the ones i use +[23:07:51] echangelog that is, not cs :p +[23:07:55] cvs* +[23:07:59] lol +[23:08:15] can we vote or do you veto? +[23:08:19] for the record i agree with wired +[23:08:21] :D +[23:08:27] i'd like a vote for this +[23:08:28] :) +[23:08:40] also, for users who checkout the overlay, they may expect changelogs +[23:08:45] i would, anyway +[23:08:56] no overlay has changelogs, so why would they? +[23:08:57] *** Quits: krakonos (n=krakonos@kangaroo.kolej.mff.cuni.cz) (Client Quit) +[23:09:07] I'm for changelogs in the overlay +[23:09:09] yngwin: well users are educated to git log or visit gitweb these days, thanks to kde-testing :P +[23:09:14] because portage does +[23:09:47] besides, git log is blazingly fast, its not like you have to cvs log :p +[23:10:02] echangelog in git is also fast +[23:10:06] ;] +[23:10:07] most users dont know how to handle git +[23:10:20] plz vote and end, i want to go to shower +[23:10:23] ayoy: sure, but when you don't echangelog in most overlays +[23:10:24] they can use the gitorious web-ui +[23:10:27] you tend to forget +[23:10:37] wired: then add echangelogs to other overlays +[23:10:39] PSYCHO___: s/vote/veto/ +[23:10:42] :) +[23:10:56] meh +[23:11:02] yngwin: me dont care you are no longer subproject and you are lead, so it is up to you +[23:11:17] yngwin: 2 months ago i could veto your veto but now it is entirely up to you :D +[23:11:22] lol +[23:11:24] lol :D +[23:11:35] i want better arguments than "I'm too lazy" +[23:11:36] yngwin: we hate you +[23:11:44] yngwin: its not im lazy +[23:11:48] tampakrap_: i'm honoured +[23:11:53] it's that i am lazy +[23:11:54] yngwin: fucked up 3way merge strategy +[23:11:58] its dup info, no real advantages :) +[23:12:03] anyway +[23:12:12] we dropped it because it breaks merges a lot +[23:12:17] it was invented to overcome VCS shortcomings we no longer have +[23:12:27] who merges anything in qting-edge? +[23:12:29] we still have in portage +[23:12:34] I've seen it once maybe +[23:12:39] yngwin: portage is cvs, we need it there +[23:12:45] yes, better spend the echangelog time to help portage to move to git i'd say :P +[23:12:45] because it still has to deal with those shortcomings - we don't +[23:13:09] when the tree moves to git the changelogs would probably be thrown out the window +[23:13:11] wired: yes, and i want the overlay to be similar +[23:13:25] then we will remove them as well +[23:13:27] ofc.... +[23:13:29] * PSYCHO___ throws the orange duck from one hand to another and looks on the clock +[23:13:32] still, cvs commit progress is *very* different from git commit process +[23:13:38] PSYCHO___: it's yellow! +[23:13:46] not this one +[23:13:49] yngwin: if recruits can't handle that difference between qting-edge and cvs, then they shouldn't be devs, really :P +[23:13:51] it's Czech duck +[23:14:10] hmm, there is something to that +[23:14:13] so it has weird dots and lines all over and above it? +[23:14:58] ok i have to go, don't care that much about this subject :P +[23:15:01] ok, let's give yngwin time to think about this and wrap this party up +[23:15:09] yngwin: http://dev.gentoo.org/~scarabeus/0911-meeting_summary.txt fix the FIXME parts, me blobs to shower +[23:15:10] yes, ok +[23:15:10] alright +[23:15:15] yngwin: its up to you, next meeting +[23:15:17] let's continue this topic on ML! :D +[23:15:19] yay! +[23:15:31] wait! +[23:15:35] you all FREEZE! +[23:15:40] wut? +[23:15:45] i'll think about it, and we can discuss it again later, ok? +[23:15:48] lets discuss our project page a bit +[23:15:50] yngwin: OK +[23:15:50] don't forget do update your qting-edge/.git/config to new pushurls :D +[23:15:52] * PSYCHO___ does the squeek sound with his duck +[23:16:05] spatz: send a mail to qt@ about it +[23:16:07] can somebody shut up that PSYCHO? +[23:16:10] lol +[23:16:14] he said freeze +[23:16:29] if you need to go, you can go +[23:16:44] i wrote up a first version, but I'd like feedback from all of you +[23:16:49] stuff that should be there +[23:16:51] stuff that should go +[23:17:06] we can continue discussing this after the meeting, we don't need to hold everybody up +[23:17:11] i do want to ask qt devs if thet would prefer a separate meeting, as these combined meetings take long +[23:17:19] ++ +[23:17:19] no +[23:17:22] YES +[23:17:34] if +[23:17:38] we keep it to 2-3 hours combined +[23:17:40] im fine +[23:17:44] issues concern both teams usually +[23:17:45] a pity is that half of the team will have just 2 meetings +[23:17:47] kde and qt one +[23:18:06] tampakrap++ +[23:18:28] i'll write a mail to kde@ and qt@ and we can discuss it then +[23:18:38] or just desktop +[23:18:40] if we started at 18 UTC or started with Qt stuff I'd be fine +[23:18:42] btw, okay to import my patch in phonon ? :] +[23:18:43] desktop mailing list +[23:18:54] mrpouet: good morning! +[23:19:11] i'm not sure everyone is on desktop ml +[23:19:11] *** Quits: ayoy (n=ayoy@gentoo/developer/ayoy) (Remote closed the connection) +[23:19:19] should be +[23:19:19] wired: did you smoke something ? +[23:19:24] *** Joins: ayoy (n=ayoy@cs78245237.pp.htv.fi) +[23:19:30] mrpouet: lol no i don't smoke ;) +[23:19:45] :p +[23:19:48] have to go bye +[23:19:50] :/ +[23:19:52] bai +[23:19:57] bye tampakrap_ +[23:20:00] cya +[23:20:04] *** Quits: tampakrap_ (n=tampakra@gentoo/developer/tampakrap) (Remote closed the connection) +[23:20:07] wired: what your sentence has to do with my question ? :D +[23:20:07] we're wrapping up anyway +[23:20:31] wired: good job on the project page, I'm sure there will be improvements/additions over time +[23:20:33] mrpouet: i asked you to talk about your issue a while back but you didn't respond :P +[23:20:57] * mrpouet has a girl-friend :( +[23:21:01] yngwin: indeed. thanks +[23:21:11] a girl friend is boring you know.. :D +[23:21:17] mrpouet: so do I, but now its sacred... errr meeting time! +[23:21:28] lol +[23:21:43] wired: aaarfff I know !! :( +[23:22:28] i think we can wrap this up now +[23:22:28] :p +[23:22:38] ok, last call +[23:22:40] mrpouet: tell em about your patch +[23:22:45] before they all leave +[23:22:45] :p +[23:22:51] * mrpouet setups a sighandler for SIGGIRL-FRIEND +[23:23:02] ... +[23:23:09] ohhh better +[23:23:15] ignore signal :D +[23:23:23] ==> [ ] +[23:23:25] ^^ +[23:23:27] mrpouet: you have 2 minutes +[23:23:58] 30s gone +[23:24:07] okay so, I wrote a patch in order to add a support for external subtitles (files) +[23:24:07] lalala +[23:24:39] it works just fine, sandsmark approved it (on upstream) +[23:24:56] it would be nice then to patch kaffeine&dragon +[23:25:10] but before we need to import my patch in phonon +[23:25:24] see https://bugs.kde.org/show_bug.cgi?id=213710 +[23:25:31] m-s/phonon or qt-phonon or both? +[23:25:33] for technical details +[23:25:40] yngwin: m-s/phonon +[23:25:46] ok +[23:26:35] currently we can : auto-detect patch (recursively in the media directory), load a patch manually, setting up the subtitle encoding +[23:26:47] rrraaahhh !!!! fucking shit !!! +[23:26:57] auto-detect subs * +[23:27:03] lol +[23:27:06] s/patch/subs +[23:27:08] o_O +[23:27:15] * mrpouet stabs himself +[23:27:39] you're putting quite a show +[23:27:47] :D +[23:27:50] :D +[23:27:51] looks to me the patch has merit, but i'm not kde herd, and i think PSYCHO___ has left +[23:28:02] the patch work +[23:28:02] s +[23:28:08] pretty well +[23:28:12] :) +[23:28:12] * wired tested it +[23:28:30] so i suggest you open a bug and poke kde team +[23:29:34] there is already a bug :) +[23:29:36] ok, meeting closed +[23:29:38] ------------------------------------- diff --git a/meeting-logs/20100225-summary.txt b/meeting-logs/20100225-summary.txt new file mode 100644 index 0000000..38e8cd4 --- /dev/null +++ b/meeting-logs/20100225-summary.txt @@ -0,0 +1,66 @@ +1) New KDE Team Leader elections: +Scarabeus is the new leader with the majority of votes, congratulations + +2) Review work flow for KDE minor bumps and improve collaboration with arch teams +We decided to skip this topic for next meeting, after preparing some documentation +on how arch teams can approach packages in the kde overlay. For the record, scarabeus +proposed this model: (1) BUG (2) keywordlist (3) portage addition (4) touching profiles +while jmbsvicetto proposed first to ask arch teams to test new deps in the overlay, if +they don't want to use the overlay, try to add a snapshot or an early release masked in +tree and ask them to keyword it, then follow scarabeus' policy. + +3) KDE-4.3.5 stabilization +The KDE team is ready on this, we are just waiting for arches to finish. When they +do, we will remove both 4.3.3 and 4.3.4 from tree. + +4) KDE-4.4 status +4.4.0 seems very unstable, people are hitting crashes with krunner and plasma, and +the virtuoso migration was not smooth for everyone. Thus, we agreed that 4.4.1 or +4.4.2 will be a stable candidate, depending of the status of 4.4.1. + +5) amarok / mysql-5.1 status +jmbsvicetto reported that it seems to work for most people for the past three days as +noone complained. Just amarok[embedded] needs a libmysqld.so as mysql-5.0 did. Jmbsvicetto +said he resumed his work to get a working patch again. + +6) enterprise useflag for kdepim stuff (a use flag to follow the enterprise branch of the +kdepim repo, only for trunk) +The problem is that kdepim in trunk currently is broken, more specifically kmail as mail +storage is being migrated to akonadi, and it seems it will stay broken for a while. Tampakrap +tried to package the enterprise branch a week ago, but some packages failed to compile, so +it may need more work. There is also an enterprise switch in CMakeLists.txt, but since we are +splitting the module, we need a new batch kdepim ebuilds that will block the current kdepim ones. +This will allow us to have an always working kdepim though. It seems a lot of work that noone +seemed interested to do, so we decided to announce it in gentoo-desktop mailing list and call +for help. Tampakrap will do it. +Speaking of trunk, we also discussed about the 4.5 snapshots, and if we should provide them. We +decided that since kdepim is broken, we won't package them yet, until version 4.4.70. Alexxy +will take care of them. + +7) koffice status +Scarabeus said that current koffice needs review of its depedencies based on CMakeLists.txt. +Tampakrap will do it and bump it in tree. + +8) knetworkmanager status +Tampakrap said that knetworkmanager seems crashy, but people want it, so we will ask dagger to +create snapshot, as he is the networkmanager maintainer. + +9) documentation status +Documentation seems fine, reavertm proposed to remove kdeprefix and maybe sets refference from +the guide. Tampakrap will take care of it. +Scarabeus with the help of jmbsvicetto will clean up the member list. + +10) drop prefixes from kde ebuilds (like kdeartwork etc) +Noone agreed on this. + +11) change kde-meta (and @kde-*) to include all modules (plus the developer specific ones) +Tampakrap proposed to have every single KDE module in kde-meta (including the developer ones +like kdesdk and kdewebdev). Many members were opposed, so the idea of a developer USE flag +for kde-meta was introduced. The discussion will be continued in gentoo-desktop mailing list. + +12) stabilization of misc kde apps +Wired owes us a script that checks for stable candidates in tree. + +13) patches of kde-packager +Jmbsvicetto and ABCD will take care of applying or opening bugs about patches that were +announced in kde-packager mailing list and need to be applied. diff --git a/meeting-logs/20100225.txt b/meeting-logs/20100225.txt new file mode 100644 index 0000000..04fa9dd --- /dev/null +++ b/meeting-logs/20100225.txt @@ -0,0 +1,612 @@ +[21:27:14] ok let's start +[21:27:23] roll call plz +[21:27:26] !herd kde +[21:27:28] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, ssuominen, tampakrap, tgurr, wired +[21:27:48] here +[21:28:17] . +[21:28:43] here +[21:28:56] * alexxy here or there +[21:29:00] alexxy: indeed :P +[21:30:19] . +[21:30:25] Sput: we need you for this one, present? +[21:31:03] lets start with kdepim +[21:31:14] jorge is going to be around in ~10 minutes +[21:31:22] hmm +[21:31:26] so the relevant tasks even for him should be that way preserved :] +[21:31:31] TOPICS: http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/meeting-2010-02-25;h=dafe5aa85c43ba9737c783576af83c972ea82afa;hb=594ec14216daa0f2f331295d4baff3e0f6d78a5c +[21:32:14] ok about kdepim and enterprise useflag +[21:32:32] also can we discuss snapshots for 4.5 pre alphas? +[21:32:33] =) +[21:32:50] ohnoes +[21:32:51] sure, along with this +[21:33:11] *** Quits: j0hu (~quassel@quassel/contributor/j0hu) (Read error: Connection reset by peer) +[21:33:19] also using lxc as testbead for testing kde builds +[21:33:25] the kdepim issue is about the trunk kde i don't know if anyone of you is interested in it +[21:33:30] * alexxy prepared some containers +[21:33:55] tampakrap: what issue? +[21:34:01] kmail is broken in current trunk, i tried to package the enterprise branch which is supposed to work +[21:34:26] why we should care about trunk? +[21:34:31] afaik the enterprise branch should be available for releases as well +[21:34:39] reavertm: because that's what's going to be in 4.5 +[21:34:44] enterprise branch should be availible for everything +[21:35:01] scarabeus: jmbsvicetto and i talked with a kde dev [cant recall his name right now] who told us enterprise branch is what they really care about +[21:35:24] we should just monthly generate our own kdepim tarball from that branch +[21:35:27] and be done with it +[21:35:34] maybe even forgot about non-enterprise :] +[21:35:36] considering the [crappy] state of kdepin right now, thats a good idea +[21:35:39] two packages failed to compile from enterprise stuff, plus a flag isn't possible for trunk as ebuilds are different +[21:35:40] kdepim* +[21:36:28] 1) there is enterprise related cmake switch in cmakelists.txt - maybe it should be used when bulding enterprise branch +[21:36:47] am i right that kmail is broken because of mail storage migrartion to akonadi? +[21:36:49] 2) still don't see why we should care :P +[21:37:02] reavertm: enterprise should actually work OK +[21:37:08] and kde devs care about it not breaking +[21:37:17] at least thats what we've been told +[21:37:18] :p +[21:37:22] i agree with reavertm, too much work, maybe we should just wait +[21:37:28] too much work for nothing +[21:37:29] problem is it does not follow kde release schedule +[21:37:44] it is released with each even release +[21:37:51] especially if apparently they're going to merge it eventually? +[21:38:40] no its not going to be merged +[21:38:49] now, I've not tried to build it yet - is it possible to use our ebuilds? +[21:38:59] or it differs too much so that it's impossible? +[21:39:04] okay, i am having hardware issues with my trunk machine and don't know when it will be back, so i can't work on it any more +[21:39:10] it differs too much +[21:39:21] it's not impossible, it is way too much work +[21:39:21] Hello +[21:39:26] tampakrap: you are talking about trunk, we are talking about releases +[21:39:28] hey jmbsvicetto +[21:39:34] sorry for being late +[21:39:37] i'm talking about enterprise itself +[21:39:40] I confused the hour again :\ +[21:39:52] * spatz is back +[21:40:16] and my opinion is the same for the snapshots, way too broken to be provided to users +[21:40:45] i can announce it and blog it, whatever, that we can't provide them if you agree +[21:40:49] other issue, how are we going to provide it? split like kdepim? +[21:41:15] yes, it needs different branch of ebuilds +[21:41:44] anyone willing to work on it? +[21:41:54] and probably blocking kdepim... +[21:42:01] or just postpone it for next meeting? +[21:42:03] exactly +[21:42:17] ok i personaly cant promise i will devote time to it :/ +[21:42:30] so it would need some maintainer, even non dev +[21:42:39] just in overlay so we see the potential +[21:42:44] and then we can put it into tree +[21:42:48] agreed +[21:42:50] i could announce it +[21:43:28] ok we should anounce global call if we find someone interested, i think we can help with basics but are busy enough to do it ourselves +[21:43:38] tampakrap: so could you sent it to dev-anounce and desktop mls? +[21:43:45] although i doubt there will be someone willing to do so much work for nothing +[21:43:47] I'm not interested in kdepim, so I won't be working on it +[21:44:05] yes, even blog the whole kdepim problem in trunk +[21:44:34] and thus i'm against providing the snapshots ( alexxy ) yet +[21:45:02] yeah no snapshot until .70 as with 4.4 should be done +[21:45:16] *** Joins: Civil (~Civilian@95-27-138-158.broadband.corbina.ru) +[21:45:16] .85 I would say even :P +[21:45:21] haha +[21:45:25] no =) +[21:45:27] .70 +[21:45:28] .70 is enough for ricers :D +[21:45:28] beta 1 :P +[21:45:30] 4.5.1? :P +[21:45:33] aka alpha0 +[21:45:34] =) +[21:45:36] btw, word of warning +[21:45:45] when kmail is ready i'd say +[21:45:52] dev.ge.o will migrate to new hardware soon, so expect a day or two of confusion +[21:46:02] thats good to know :] +[21:46:07] thanks patrick +[21:46:33] ok i think we should get back on track with topic one :] +[21:46:38] i think we are ready on this (btw i'm writing summary as soon as we speak) +[21:46:55] so we dont jump over those carefully written numbered topics in chaotic order :] +[21:47:08] ok back to topic one: new leader elections +[21:47:26] candidates: jmbsvicetto, scarabeus, plz vote (devs only) +[21:47:28] bring it on! +[21:47:48] I vote yes ;) +[21:47:52] DrEeevil: you cant +[21:47:53] pick +[21:47:55] i vote scarabeus (sorry jorge :) ) +[21:48:11] DrEeevil: :P +[21:48:12] I'd like to hear manifesto from both! ;) +[21:48:17] * reavertm runs +[21:48:22] lol +[21:48:23] tampakrap: no hurt feelings ;) +[21:48:45] not to break kde and keep it working for everyone of us :] and provide my qa tools for kde +[21:48:49] i vote for scarabeus =) +[21:48:53] scarabeus: nothing prevents us from having more than one lead, but let people choose +[21:48:58] note that this manifesto wont change for me if not voted for :] +[21:49:03] hmm +[21:49:09] what qa tools? +[21:49:11] or lets have two leads +[21:49:12] =) +[21:49:20] if its possible +[21:49:22] i have quite few scripts that checks x11 state +[21:49:25] i like that idea too +[21:49:26] no, just one to rule them all :) +[21:49:32] and i can adjust it for kde +[21:49:38] no, one leader is enough +[21:49:39] which i plan for month or so already :D +[21:49:42] we are a large herd +[21:50:00] actualy multiple leads are weird, just pick guys +[21:50:08] it does not matter to jorge or me who wins :] +[21:50:16] we just comply to the 1 year election rule :] +[21:50:21] how many members with voting power are here? +[21:50:33] lets vote and find out +[21:50:34] ;p +[21:50:39] 9 +[21:50:56] sorry 10 +[21:51:12] what about 5:5 ? +[21:51:22] reavertm: that would not amuse me +[21:51:36] ok, let's hear it +[21:51:47] in case 5:5 i'll change my vote :P +[21:51:47] * ABCD votes scarabeus +[21:51:55] * reavertm votes scarabeus +[21:51:56] * alexxy votes scarabeus +[21:52:03] scarabeus: I'll break the tie ;) +[21:52:03] * tampakrap votes scarabeus +[21:52:11] * wired votes scarabeus +[21:52:14] * spatz votes scarabeus +[21:52:15] * jmbsvicetto votes in scarabeus +[21:52:20] lol +[21:52:23] ok ok ok +[21:52:23] nice +[21:52:25] i get it +[21:52:38] like it or not you're lead +[21:52:38] :p +[21:52:39] * scarabeus votes for jmbsvicetto :] +[21:52:39] congrats now abuse your powah :P +[21:52:40] I said before I would prefer to have someone else being lead ;) +[21:52:47] scarabeus: No!!!! :P +[21:52:48] * wired remembered +[21:53:04] Congratulations Tomas +[21:53:13] scarabeus: \o/ congrats :) +[21:53:22] Now everyone i guess we should drink something good in favor of our good benevolent now-ex lead. So on Jorge :] +[21:53:38] and thanks, lets i will try to not doom us all :] +[21:53:59] * wired has a beer open =] +[21:54:05] * scarabeus too +[21:55:02] ok little girls you played enough for today, now let's move on +[21:55:15] Review work flow for KDE minor bumps and improve collaboration with arch teams +[21:55:48] 1) BUG +[21:55:48] 2) keywordlist +[21:55:48] 3) portage addition +[21:55:48] 4) profiles touching +[21:56:00] this should be workflow from now-on so we dont touch anyones toes +[21:56:13] scarabeus: The Founder Power has been bestowed on you for #gentoo-kde ;) +[21:56:22] * ssuominen votes scarabeus +[21:56:28] abcd * gentoo/xml/htdocs/proj/en/desktop/kde/index.xml: We have a new lead! +[21:56:36] :P +[21:56:57] ssuominen: ha ha ha :D +[21:57:10] all cards have been played already ;) +[21:57:15] scarabeus: I propose something different +[21:57:31] jmbsvicetto: i just wrote this one after start with jer, and then i got distracted +[21:57:38] jmbsvicetto: how does your approach look? +[21:57:43] if its better just make it policy +[21:57:44] :] +[21:58:01] its once per 6 months, and it wont hurt to have written down somewhere in Documentation/ +[21:58:14] good idea, whatever we decide on this should be forwarded as a global policy +[21:58:23] scarabeus: 1) Ask arch teams to test new deps in the overlay. 2) If they don't want to use the overlay, try to add a snapshot or a early release masked in the tree and ask them to keyword it +[21:58:35] scarabeus: then your policy +[21:59:06] i don't like this approach +[21:59:18] well, your 3) would be done before, so it could be 3) unmask in the tree +[21:59:18] what if they do something stupid while using the overlay? +[21:59:56] tampakrap: I might not have been clear, I meant to let them try the ebuilds from there and for us to add their keyword +[22:00:07] tampakrap: I'm not giving commit access +[22:00:07] jmbsvicetto: sounds sane +[22:00:18] altho i dont think about that snapshot into main tree +[22:00:20] i was not clear +[22:00:26] deps can go if released +[22:00:28] but not the kde +[22:00:33] I don't like snapshots in tree either +[22:00:33] it is annoying 280 packages +[22:00:38] i meant what if they use other testing ebuilds while using the overlay? +[22:00:42] its 4 hours commit +[22:00:47] (even if those are kde deps just) +[22:00:58] scarabeus: The snapshot as a last resort if upstream doesn't have a release 2 weeks / 1 month before getting the new version in the tree +[22:01:27] but only for deps +[22:01:32] no touching of kde-base/ itself +[22:01:35] I'm only talking about new deps +[22:01:35] there is problem - we have no arch team members in kde team +[22:01:40] we have +[22:01:42] for amd +[22:01:43] :D +[22:01:48] only ssuominen, but we would need some for other archs +[22:01:58] me stable for amd64 from time to time +[22:02:00] i can keyword arm and mips +[22:02:01] =) +[22:02:09] scarabeus: It's 30 minutes if you commit at category level. +[22:02:38] Philantrop: i know, but i managed to clash 3x already with someone else :] +[22:02:42] if you commit in 10 threads then it takes about 5 minutes +[22:02:45] even when i announced it :D +[22:02:46] to commit whole kde +[22:02:54] and since keywording kde is quite a bottleneck .. kde dev (which clearly uses kde) could do it faster +[22:02:56] hmm i could thread bump tool indeed +[22:03:13] scarabeus: force commit and kick anyone interfering from the herd. That's what I did. :-> +[22:03:30] scarabeus: i added kde 4.4.0 in about 5-7 minutes to tree +[22:03:35] * ABCD is x86-linux and amd64-linux +[22:03:38] working with 10 threds +[22:03:48] *threads +[22:04:05] ok lets write out the rules on the Documentation +[22:04:09] and i will thread the bumptool +[22:04:11] its quite simple +[22:04:44] <- not a part of amd64, just have stable chroot for xfce/kde/xorg/base-system/media +[22:05:05] i also stable only when i have long night :D +[22:05:19] but people mostly dont complain if qa guys stable on archs they can test :] +[22:05:53] i would say this topic should be reviewed on next meeting with respective prepared documentation for approach in the overlay, anyone some additions? +[22:06:33] no problem in this, i just hope there will be something prepared until next meeting +[22:06:59] ok kde-4.3.5 then :] +[22:07:01] i think we can use lxc containers instead of chroots +[22:08:03] so we are waiting on archies only, are there any issues with it? +[22:08:35] what's advantage of lxc over chroot? +[22:08:49] (which I can boot to natively as well) +[22:08:58] it run separate system in separate namespace +[22:09:10] so its more closer to vms +[22:10:28] VM's +[22:10:29] =) +[22:10:38] ok back to topic +[22:10:46] so we are waiting on archies only, are there any issues with it? +[22:11:25] anyone? +[22:11:35] not that I've seen, as an archie :D +[22:11:55] ok next one +[22:12:03] *** Joins: aboow (house5@gateway/shell/bshellz.net/x-vhnffmhwlxzbhinj) +[22:12:05] tampakrap: won't be really online until in about 1 hour +[22:12:06] sitting in the train currently with shaky net +[22:12:24] just one addition, dont remove 4.3.4, just wipe out 4.3.3 and 4.3.4 in one step when 4.3.5 is ready :] +[22:12:34] if anyone gets remove ideas :P +[22:12:35] Sput: ok we can talk then +[22:12:51] kde 4.4 status +[22:12:51] s/anyone/alexxy/ +[22:12:59] * alexxy has remove idea of old kde's +[22:13:00] :) +[22:13:01] :D +[22:13:15] referring to kdepim: if we found a way to package the current 4.4 kdepim in a way that it works with -9999 (no idea, copying the ebuilds from 4.4 into some overlay and renaming them to -9999) that should be more or less easy +[22:13:21] as 4.4 kdepim is supposed to work with trunk kde +[22:14:22] Sput: we can talk about it later, the other members have already expressed their opinions and you are messing with the topics now :) +[22:14:34] back again to kde 4.4 +[22:14:46] any known problems? blockers? +[22:14:55] yeah it is slightly flaky +[22:14:57] archies =) +[22:15:02] i got few crashes in kwin and plasma +[22:15:24] also, congrats scarabeus :) +[22:15:25] few crashes in krunner and plasma +[22:15:27] me too, so i guess 4.4.1 will be the stable candidate +[22:15:30] also the virtuoso migration is not exactly funky working out of the box for some +[22:15:36] 4.4.1 or 4.4.2 +[22:15:41] 4.4.2 most likely +[22:15:42] we shall see after 4.4.1 release +[22:15:51] ok +[22:15:51] i would rather wait too +[22:15:58] judging from the past... +[22:15:59] anything else on 4.4? +[22:16:20] i guess not +[22:16:32] jmbsvicetto: amarok and mysql 5.1 status +[22:16:32] *** Joins: hwoarang (~mystical@gentoo/developer/hwoarang) +[22:16:49] poor Jorge +[22:17:03] oh wait, akonadi is indifferent... +[22:17:26] virtuoso migration failed for me +[22:17:31] amarok works with mysql 5.1 +[22:17:33] ok +[22:17:38] if it compiled with -FPIC +[22:17:42] so, amarok and mysql-5.1 +[22:18:01] Fortunately it's way better than I feared when I added it to the agenda +[22:18:32] The ebuilds have been updated and no one complained for the past 3 days(?) so it seems users are getting used to it ;) +[22:18:43] AIUI, amarok[-embedded] should work just fine - amarok[embedded] has the same problems with 5.1 that it did with 5.0 - namely, that we need a libmysqld.so again +[22:18:50] A few people are still following the bug, but we can live with it as is +[22:19:03] ABCD: exactly +[22:19:52] there's another quirk, preserved-libs will keep the libmysqld.so for those upgrading, which does allow amarok to work (it happened here), until we have an abi / api incompatible change +[22:20:32] that is for amarok to work with mysql-5.1 - but that might cause serious issues "sooner than later" +[22:20:56] in any case, I've resumed my work to get a working patch, so let's see if I can do this before we have to elect a new lead ;) +[22:21:31] :D +[22:21:40] thank you x-boss +[22:21:47] how about we stop supporting the embedded part :] +[22:21:51] and just force full amarok +[22:21:58] patch-- +[22:21:58] ? +[22:22:00] like akonadi does +[22:22:01] ^^!! +[22:22:08] let them have it! +[22:22:20] that should teach those bastards :P +[22:22:30] :D +[22:22:38] ok anything else? serious? +[22:22:42] ok lets go for koffice +[22:22:47] i guess i should answer that one +[22:22:59] problem with koffice is that expect graphic tools it is totaly unusable +[22:23:00] * reavertm fixed kword recently +[22:23:02] go on +[22:23:11] and it needs all deps reviewed and updated based on cmakelists +[22:23:36] i personaly use only krita and dont care about rest of the bunch so it needs some dedicated guy whom will actualy use the stuff +[22:23:49] i will take this one but i may need your help +[22:24:01] query still works :] +[22:24:19] *** Quits: aboow (house5@gateway/shell/bshellz.net/x-vhnffmhwlxzbhinj) (Disconnected by services) +[22:24:49] anything else? +[22:24:57] nop, nothing from me to add +[22:25:13] ok knetworkmanager +[22:25:19] scarabeus: no harm in keeping embedded for now +[22:25:25] jmbsvicetto: oky +[22:25:33] ok we need snapshot +[22:25:40] and monthly refreshed snapshot probably +[22:25:43] scarabeus: if I can get a patch for mysql, we can make it simple again +[22:25:45] knetworkmanager crashes plasma here, i didn't prepare a snapshot i just tested with live ebuild +[22:25:46] who is willing to take that one out :] +[22:25:59] tampakrap: well plasmoid can be disabled +[22:26:07] tampakrap: most people are interested in kcm module +[22:26:22] we need monthly refreshed snapshot from svn +[22:26:23] i didn't use the plasmoid +[22:26:31] only the system tray item +[22:26:35] the same thing +[22:26:39] sure +[22:26:40] kcm is in systemsettings +[22:26:45] tampakrap: is it working? +[22:26:53] kcm wasn't working though :) +[22:26:58] ok +[22:27:03] so anyone uses NM these days +[22:27:07] or are we all on wicd? +[22:27:16] i guess i didn't have time to test it since it was crashing +[22:27:43] i can prepare a snapshot but it will need a lot of testing and i'd prefer if someone with non-crashing results would do it +[22:27:58] i'm on openrc init scripts and wpa_gui +[22:28:18] *** Joins: jmrk_ (~jmrk@dslb-088-064-075-227.pools.arcor-ip.net) +[22:28:19] tampakrap: ok just add it masked to main tree +[22:28:25] and lets ask users for testing and feedback :] +[22:28:29] anyone else? no? +[22:28:50] good question, there is quite few more team members :P +[22:28:55] who is willing to do this one? :] +[22:29:36] ABCD / reavertm? +[22:29:51] there is also DrEeevil whom enjoy the user feedback anyway :D +[22:30:04] I don't use NM +[22:30:19] tampakrap: i got it +[22:30:22] tampakrap: coordinate with dagger +[22:30:28] tampakrap: afterall he is maintainer of NM +[22:30:34] ah yes +[22:30:39] ok next topic +[22:30:45] * reavertm does have static network +[22:31:14] the documentation is fine, i updated it about a month ago, if you all want can take a look and propose fixes +[22:31:19] two issues though: +[22:31:32] 1) jmbsvicetto promised to clean up the member list +[22:31:48] which will be probably my task now :/ +[22:32:01] 2) i have an open bug about xdm configuration which i don't like, i'd like your feedback +[22:32:09] i will sent mail to everyone who does not have 5 commits month into kde cat +[22:32:13] scarabeus: I sorted it asciibetically for you (except your name is at the top) :D +[22:32:34] ABCD: lovely, you earn the big plus point :P +[22:32:50] http://bugs.gentoo.org/attachment.cgi?id=220755&action=view +[22:33:08] scarabeus: also plz remove qt members they are still there +[22:33:34] tampakrap: yeah +[22:33:44] tampakrap: I'll talk to scarabeus about that +[22:33:46] a small note: i didn't add the usefull links in the guide as jmbsvicetto pointed as they are not that useful :P +[22:34:00] tampakrap: recommend dejavu and droid fonts for christ sake +[22:34:26] tampakrap: other than that you should point to x11 guide which should describe xdm config iirc +[22:34:39] cool +[22:34:43] i like that +[22:35:26] last point: i'm going to blog about kde3 removal and the kde-sunset existence, so that ppl will hopefully stop filling stupid kde3 bugs anymore +[22:35:38] its only gnu_andrew +[22:35:45] and he will fill them anyway just to annoy us +[22:36:05] heh +[22:36:07] i don't have to say anything else about the docs, just i am waiting for you to take a look plz +[22:36:24] remove kdeprefix from docs +[22:36:31] kde guide is way too red +[22:36:45] funny, i agree on that +[22:36:51] friendly 'notes' everywhere +[22:37:10] it's impossible to follow +[22:37:11] :D +[22:37:22] yeah just wipe out kdeprefix from docs is good idea +[22:37:34] about kde3 and kde-sunset, my opinion is that we did one thing wrong +[22:37:49] also maybe sets... +[22:37:56] my initial goal was never to make kde-sunset a "dumping ground" to be mastered by users alone +[22:38:01] info about sets - remove as well? +[22:38:14] reavertm: i think we can have a note about sets, but keep metas as the default option +[22:38:27] nah sets are weird +[22:38:31] they are bbd now +[22:38:32] jmbsvicetto: i'm sure everyone knows that, but you can't force devs to work on it :) +[22:38:39] jmbsvicetto: i'm still following the kde-sunset commits +[22:38:43] I'd rather have an overlay with commits just by devs and trusted committers (akin to sunrise) and another overlay with free access by users +[22:38:55] jmbsvicetto: well your idea assumes devs are interested +[22:38:59] but now it's too late, so we'll have to live with it as is +[22:38:59] jmbsvicetto: we have none of those +[22:39:00] :p +[22:39:15] * jmbsvicetto cries for sets +[22:39:34] jmbsvicetto: not in this implementation, sorry +[22:39:34] I know (devs and KDE3) +[22:39:55] ok, i guess we are done +[22:39:56] pretty much all gentoo devs have commit access to that overlay.. +[22:40:48] the following two topics are long time ideas i had +[22:40:54] drop prefixes from kde ebuilds (like kdeartwork etc) +[22:40:59] I use NM with the plasmoid and both work great +[22:41:01] trunk though. +[22:41:22] if anyone dares to remove the plasmoid from -9999 I will keel him +[22:41:23] :) +[22:41:23] tampakrap: things like kdebase-data... you think it should just be "emerge data"?! +[22:41:45] well no +[22:41:48] drop prefixes? no +[22:41:51] but for kdebase-startkde yes +[22:41:56] add prefixes? more likely :P +[22:41:58] or for the artwork ones +[22:42:01] please no another dev-haskell/ +[22:42:09] try emerge opengl or emerge x11 +[22:42:20] startkde makes sense +[22:42:20] or zlib for that matter +[22:42:23] or chromium :) +[22:42:29] same with emacs +[22:42:35] yeah i think it is not worth the gain +[22:43:11] whatever I try to install, it tells me that I need to choose between sam app-emacs/XXX and /XXX +[22:43:15] we dropped -plugin- from xfce-extra/'s for a long time, and I can tell you... it was, nothing but a pain +[22:43:29] tampakrap: oh, and kdeartwork-kscreensaver can't be "kscreensaver", because kde-base/kscreensaver is kdebase-workspace +[22:43:34] scarabeus: you wanted to add prefixes some time ago +[22:43:41] ok i got your point +[22:44:04] to have module precede package name - like kdegames-sth +[22:44:22] reavertm: i thought of it bit more, and it would just take too much time :] +[22:44:22] reavertm: it's the same i guess, too much pain, doesn't worth it +[22:44:29] so that one can easily know what module is this withour reading ebuild +[22:44:41] grep KMMODULE is simple :D +[22:44:47] or KMNAME +[22:44:48] :] +[22:44:53] yest, misleading +[22:44:55] well, i don't want to emerge kdepim-kmail +[22:45:04] module = kdepim, not subdir in kdepim +[22:45:20] KMMODULE is a bit unfortunate name... +[22:45:39] never mind +[22:45:43] indeed, sadly i dont want to redesing the eclass again :D +[22:45:52] reavertm: i bet you dont want either +[22:45:52] we have one convention already +[22:46:01] we all agreed i guess not to touch anything +[22:46:06] next? +[22:46:21] for those that are in multiple module, we have plasma-apps, plasma-workspace, plasma-runtime +[22:46:25] same with solid- +[22:46:35] let's just keep it when needed +[22:46:40] change kde-meta (and @kde-*) to include all modules (plus the developer specific ones) +[22:46:44] reavertm: sure +[22:46:52] i dont get what are you proposing with this topic :P +[22:47:08] it should include even kdesdk? +[22:47:11] thats baad idea +[22:47:24] 99% of users dont want it +[22:47:31] they just emerge kde-meta cause they are lazy +[22:47:45] that's what i'm proposing yes +[22:47:54] -1 +[22:48:07] and how is kdewebdev more useful? +[22:48:23] on the other hand, we don't get bugreports for them because nobody is using this +[22:48:25] how about a developer something flag? +[22:48:33] exactly! +[22:48:43] (less bugs -> more fun) +[22:48:53] hm tampakrap useflag would be bad, not supported on sets right? +[22:49:00] sorry -1 from me +[22:49:00] tampakrap: developer useflag could work on meta +[22:49:03] but what for sets +[22:49:06] its baad idea +[22:49:15] if user wants it he can merge kdesdk-meta +[22:49:19] or kdewebdev-meta +[22:49:29] kdewebdev is already in kde-meta +[22:49:41] introduce a new set? kde-lazy? :p +[22:49:47] kde-meta shouldn't be used by users +[22:49:53] why? +[22:49:59] at least i think sets should include them all +[22:50:01] +1 for tampakrap's proposal, we should have everything in there. +[22:50:11] i except kde-meta to install everything +[22:50:32] expect* +[22:50:33] wired: I hope you "expect", not "except" :D +[22:50:39] expect gr +[22:50:43] for me kde-meta is http://websvn.kde.org/trunk/KDE/ +[22:50:54] a "recommended" USE flag could be introduced to skip stuff not needed by users +[22:50:55] ABCD: he uses qt with the "exceptions" use flag ;) +[22:51:10] kdeexamples O_o? +[22:51:23] if you add the kdebindings stuff to kde-meta, I'm sure we'll get a few interesting bug reports ;) +[22:51:44] (wom 96 +[22:52:01] ok then, i'll rephrase: how about a developer something use flag in metas and include everything in sets? +[22:52:10] we can have kdefull-meta +[22:52:13] or somethingl ike +[22:52:14] at least for sets it makes sence, users can create their own +[22:52:17] kde-burnmycomputer +[22:52:27] but not kde-meta +[22:52:35] it is full blown working kde desktop +[22:52:37] not full kde +[22:52:44] i still prefer the use flag idea +[22:52:57] lets discuss this on alias +[22:53:06] well, we can have kde-meta installa all, but advice to use kdebase-meta instead +[22:53:08] in gentoo-desktop +[22:53:14] or that +[22:53:23] but there will be duncan +[22:53:24] ok let's discuss it in the mailing list, i'll start the thread +[22:53:28] and who is going to read that :D +[22:53:32] i won't +[22:53:36] i have work to do +[22:53:43] you know +[22:53:52] gmail used to automatically clasify duncan as spam +[22:54:12] cool next topic +[22:54:14] 13 - stabilization of misc kde apps +[22:54:17] :P +[22:54:25] qa scripts can help with that +[22:54:27] wired promised a script :) +[22:54:32] for qt also +[22:54:34] but we have quite too much packages +[22:54:39] in kde +[22:54:43] it takes some time to compute +[22:54:43] L:D +[22:54:48] oioi i had to do that for kde as well ^_^ +[22:54:57] wired: okey your job :P +[22:55:01] ok i'll repromise to the new lead as well +[22:55:03] show us cookies on next meeting :D +[22:55:06] i have a todo file now! +[22:55:08] :P +[22:55:11] next week plz +[22:55:13] max +[22:55:20] scarabeus: kick him please :D +[22:55:26] last topic shut up +[22:55:28] 14 - patches of kde-packager +[22:55:57] i was kinda busy with exams last month i was not following the ml +[22:56:08] reavertm maybe knows anything? +[22:56:19] ABCD is suposed to apply kde-packager patches +[22:56:22] or jmbsvicetto i think he brought up the subject +[22:56:28] as was decided on one of the former meetings +[22:56:42] well, there are some and they need to be applied as they appear.... +[22:57:00] yeah, there have been a few patches sent to the packagers ml that didn't go applied +[22:57:00] ABCD: will you handle it? +[22:57:12] I lag here a bit (also due to limited time recently) +[22:57:14] anyone else willing to help on this? +[22:57:15] I think there are 3 for 4.4 by now +[22:57:26] I hadn't be able to get on the list until very recently, so I haven't seen those patches yet +[22:57:50] i am qute busy in x11 tracking so i cant do such pernament task for kde sadly :/ +[22:57:53] ABCD: I thought I had asked for everyone to be put in the ml +[22:58:18] I'll try to follow the ml +[22:58:29] ok, jmbsvicetto / ABCD will you handle this? +[22:58:34] in the least I can open a bug with the patch / patch link +[22:58:42] sure that too +[22:59:15] scarabeus should be able to add new people to the ml, but in any case I can always poke rdeiter and the kde infra team to get it done +[22:59:22] I'll look into it too +[22:59:28] great +[22:59:39] alexxy: what did you want to talk about? +[22:59:46] jmbsvicetto: thx for the hint, be sure i will ask anything i would not know how to do :] +[22:59:58] scarabeus: any time you need +[23:00:26] alexxy: ping +[23:00:47] i have 1 thing: we need another kde HT lead, i cant do herd testers lately due to limited time, and it would be sad if we loose that nice recruit count, dont you think? +[23:00:52] anyone wants to pick that one up? +[23:01:38] which are the requirements? +[23:02:00] tampakrap: be on irc, actively follow the new recruits and help them +[23:02:03] and motivate them +[23:02:09] like devrel said, a few children and 'mature' attitude ;) +[23:02:11] come on you saw me in action as one of the closest +[23:02:18] you know what i did :] +[23:02:23] ok i'm not good at it +[23:02:39] *** Quits: willikins (~rbot@gentoo/bot/Willikins) (Read error: Operation timed out) +[23:02:51] i tend to insult ppl like wired three times per day before food +[23:03:14] good training is actualy teaching :] +[23:03:29] ok we keep it as-is and i will anounce on alias :] +[23:03:40] reavertm: I'm on devrel ;) +[23:03:47] tampakrap: pong +[23:03:48] =) +[23:03:57] alexxy: topics you wanted to discuss? +[23:04:00] ok /me has to disappear +[23:04:02] so have fun +[23:04:03] make it quick plz +[23:04:06] and dont break a shit +[23:04:07] :D +[23:04:11] reavertm: I guess I'm "old enough" at least ;) +[23:04:16] hehe +[23:04:18] seems we already discussed them all +[23:04:19] =) +[23:04:24] cool +[23:04:27] meeting closed +[23:04:32] i'll prepare the summary +[23:04:32] yep +[23:04:52] it was cool to moderate you all, next time don't bring your dolls plz +[23:05:55] * tampakrap joke fail +[23:05:59] dolls? I didn't knew I had to bring mine!! +[23:06:51] o_O +[23:12:24] *** Quits: reavertm (~quassel@gentoo/developer/reavertm) (Remote host closed the connection) +[23:15:20] *** Joins: reavertm (~quassel@bsb151.neoplus.adsl.tpnet.pl) +[23:15:21] *** Quits: reavertm (~quassel@bsb151.neoplus.adsl.tpnet.pl) (Changing host) +[23:15:21] *** Joins: reavertm (~quassel@gentoo/developer/reavertm) +[23:22:53] *** Parts: spatz (~spatz@gentoo/developer/spatz) +[23:23:37] reavertm: ping +[23:23:59] hmm? +[23:24:23] sorry for doing this, yngwin requested to add to topics the desktop profile split but i failed to push :P +[23:24:45] is there anything we should discuss (in ml i guess) or can we proceed on this? +[23:24:53] no, please do +[23:25:14] we voted on this already, no? +[23:25:19] yes +[23:28:02] *** Quits: jmrk_ (~jmrk@dslb-088-064-075-227.pools.arcor-ip.net) (Quit: Konversation terminated!) +[23:35:05] tampakrap: does this mean it is going to be implemented now, or? +[23:35:13] yes +[23:35:19] i will do it +[23:35:22] ok, tnx +[23:35:27] i 'll write it in summary too +[23:35:34] so you can have proof :) +[23:35:36] good :) +[23:36:02] otherwise i will just remove the ridiculous mysql requirement from desktop profile myself ;) +[23:36:04] sorry for not bringing this up, i thought i pushed it diff --git a/meeting-logs/20100318-summary.txt b/meeting-logs/20100318-summary.txt new file mode 100644 index 0000000..1c4f5db --- /dev/null +++ b/meeting-logs/20100318-summary.txt @@ -0,0 +1,38 @@ +1) Removal of innactive KDE team members +Since there were no objections last month for scarabeus' draft, he'll proceed in +removing some members that don't follow the rules. The draft is at +http://dev.gentoo.org/~scarabeus/kde-team-rules.html + +2) Review work flow for KDE minor bumps and improve collaboration with arch teams +Nothing more was to be said from the last meeting, both scarabeus and jmbsvicetto's +proposals were accepted. + +3) KDE-4.4 status +4.4.1 seems to be a good release, with not many problems so far. Also, there were +people working on the kdebindings which was suffering mostly. It will be a stable +candidate, and the bug will be openned at start of next month. + +5) enterprise useflag for kdepim stuff (a use flag to follow the enterprise branch of the +kdepim repo, only for trunk) +The call for help didn't bring in any volunteers, so there was no progress on this. Sput told +that this is very important to be fixed, as kdepim may not be ready for KDE 4.5. Tampakrap will +try again to raise the issue in ml. + +7) koffice status +KOffice still is in bad status, tampakrap and wired will work on this. + +8) change kde-meta (and @kde-*) to include all modules (plus the developer specific ones) +Following last meeting's discussion on this, tampakrap opened a mail asking for people's +opinion on this in the gentoo-desktop mailing list, and many people liked the idea. So, +with scarabeus' permission, tampakrap will add this to kde-meta ebuilds. Kdebindings will +stay out for now until they all compile. + +9) patches of kde-packager +No actions were done on this, jmbsvicetto said he'll try to take care of it. + +10) Split desktop profile +After a long discussion in gentoo-dev and gentoo-desktop mailing lists, and with the +approval of the gnome and qt teams (the leads mostly, leio and yngwin), tampakrap +will finally split the desktop profile to kde and gnome subprofiles. Leio raised the +need of a better profile system that will support mixed profiles. Tampakrap liked the +idea and is willing to work on this, but it is going to be long-term diff --git a/meeting-logs/20100318.txt b/meeting-logs/20100318.txt new file mode 100644 index 0000000..52960de --- /dev/null +++ b/meeting-logs/20100318.txt @@ -0,0 +1,206 @@ +[22:02:03] alexxy / bonsaikitten / dagger / jmbsvicetto / lxnay / mrpouet / reavertm_ / scarabeus / spatz / wired +[22:02:05] meeting time +[22:02:12] http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/maintainers/meetings/meeting-2010-03-18;h=b056be61645fbd793cf07cb9d0eb968e961cb2c1;hb=HEAD +[22:02:21] who is here? +[22:02:25] mesa here +[22:02:29] me +[22:02:39] boss around +[22:02:44] although my connection is flaky +[22:02:47] ping me when it gets to subprofile stuff I guess. Preoccupied 30 more mins +[22:03:00] leio: i was about to ping me +[22:03:07] ok let's skip it for now +[22:03:12] s/me/you +[22:03:18] well, in that agenda it's last item anyway.. +[22:04:11] let's wait another 10 mins, many ppl are away +[22:04:31] -*- alexxy here ;) +[22:05:54] I will start with the lighter thing +[22:06:00] since there were no objections to new rules +[22:06:01] --> willikins (~rbot@gentoo/bot/Willikins) has joined #gentoo-meetings +[22:06:10] woohaa bot is back +[22:06:13] !herd kde +[22:06:16] i will start enforcing them +[22:06:36] where is the draft first of all? +[22:06:39] so i will thin up team list probably +[22:06:40] and why isn't it in git? +[22:06:52] what for my rules? +[22:06:55] i sent you mail +[22:07:06] ok, commit it in git :) +[22:07:36] http://dev.gentoo.org/~scarabeus/kde-team-rules.html +[22:08:04] i would have to find that rst first :P +[22:08:15] pong +[22:08:28] ok let's start now +[22:08:29] I just need a minute to put my things down and I'll be back +[22:08:34] again who is here? +[22:08:51] scarab +[22:09:09] -*- spatz ← +[22:09:09] !herd kde +[22:09:26] (it responds to pm at least) +[22:09:36] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, tampakrap, tgurr, wired +[22:09:57] -*- wired o/ +[22:10:25] -*- alexxy partialy there or here or somwhere else +[22:11:09] scarabeus: go on with the removal of members plz +[22:11:18] what's the news on this? +[22:11:28] well you didnt complain +[22:11:35] so i will put down a list, and clean up +[22:11:46] you had 1 month to write objections to my rules list :] +[22:12:14] just to note, it has nothing against the named developers, i just preffer that people know who is maintaining it +[22:12:59] here +[22:13:02] anything else on this? +[22:13:31] only if you have questions +[22:13:58] questions? anyone? +[22:14:52] so, people are going to be removed from the team, i repeat: questions? +[22:15:13] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, tampakrap, tgurr, wired +[22:15:38] let's move on +[22:15:46] Review work flow for KDE minor bumps and improve collaboration with arch teams +[22:15:49] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, tampakrap, tgurr, wired +[22:15:51] scarabeus: ^^? +[22:16:09] it was written last time, wasn't it? +[22:16:56] we were going to continue the discussion today +[22:17:10] unless nothing new is going to be said +[22:17:14] jmbsvicetto: ^^? +[22:17:39] tampakrap: iirc I had only one change and it was accepted +[22:18:42] ok +[22:18:43] next +[22:18:54] KDE-4.4 status +[22:19:09] 4.4.1 is out, you said that ppl reported problems with 4.4.0 +[22:19:14] i didn't have any at least +[22:19:22] i saw few people working on bindings finaly in overlay +[22:19:25] which is great +[22:19:41] indeed +[22:19:57] can we have 4.4.1 as a stable candidate? regressions? blockers? +[22:20:02] It's working great here +[22:20:10] I don't have kdepim or kdebindings, though +[22:20:28] kdepim is great, kdebindings needs work +[22:20:40] I've got full kde-4.4.1 and it's good. I had problems migrating from 4.3.x with kmail, but it's all ok now +[22:20:50] i guess we should pay attention on this and if there are no further problems we can have it as a stable candidate +[22:21:02] schedule? +[22:21:33] 4.4.1 works great here too - and on colleague's system as well (users are best test :P) +[22:21:50] i guess start of next month? scarabeus? +[22:22:06] ok, i saw no more issues too +[22:22:18] just check regressions against 4.3 -> 4.4 migration +[22:22:19] фдыщ нуы +[22:22:23] and ok for 4.4.1 patch +[22:22:24] yep +[22:22:31] 4.4.1 works great +[22:22:41] also we use it at university +[22:22:45] as De for students +[22:23:06] scarabeus: start of next month is ok? +[22:23:25] yup +[22:23:26] meaning two weeks from now? +[22:23:36] no, stable bug +[22:23:43] sorry misread :P +[22:23:44] yes +[22:24:14] unless there aren't any other things here, we can move +[22:24:21] --> dilfridge (~quassel@gateway.maximilianeum.mhn.de) has joined #gentoo-meetings +[22:24:34] enterprise useflag for kdepim stuff (a use flag to follow the enterprise branch of the kdepim repo, only for trunk) +[22:24:54] nobody sent any mail or word about working on it +[22:24:58] so we should move it to todo +[22:25:04] until someone feels motivated enough +[22:25:04] i lack the hardware to proceed on this, plus i asked for help, noone answered +[22:25:19] Sput: anything you want to say on this? +[22:25:36] i dont know anything about it, but would like to get some information. what's different in enterprise branch? +[22:26:04] does enterprise branch contain support for Openchange/libmapi? +[22:26:27] (that's required for propler M$ exchange 2003/2007/2010 support) +[22:26:31] enterprise branch for kdepim is the actual branch were kde developers care about +[22:26:39] since kdepim trunk is broken right now +[22:26:47] it's supposed to stay stable while everything else is being ported to akonadi (and broken in the meantime) +[22:26:47] dagger: it is the branch that is more stable/solid, developers care about that one, because they are payed for that branch +[22:27:14] so I guess it's not part of "default" kdepim right? +[22:27:20] ok, we'll move this topic for next meeting, since there is no progress +[22:27:22] right +[22:27:50] let's move +[22:27:52] koffice status +[22:28:10] new koffice is released, i did a simple rename, and it currently is in hilarious status +[22:28:18] some packages don't even compile +[22:28:53] -*- scarabeus told you so +[22:29:04] i'll try to fix it, but i'll need help, anyone willing to help me is welcome +[22:29:16] i might +[22:29:25] current ebuilds are hardmasked in overlay, tarball is not released yet +[22:29:31] okie +[22:29:55] and we should be quick on this and try to have a schedule for stabilization too +[22:30:17] as it also new packages +[22:30:34] btw i can help with quick-ish stabilization on amd64 +[22:30:42] sure +[22:30:47] tampakrap: enterprise branch is based on pre-akonadi kdepim and supposedly works +[22:30:56] but a USE flag isn't gonna cut it, the packages are too different +[22:31:20] also we might have to check what they have outside of kdepim, I think they even ship a hacked kdelibs +[22:31:26] o_O +[22:31:33] kdelibs-lite! +[22:31:34] ;p +[22:31:37] (but Paul Adams told me it should work fine with 4.5) +[22:31:41] yes, we need a different branch for this +[22:32:01] there was a mail recently on kde-scm-interest where steveire detailed how branches work +[22:32:23] kdepim is in the process of moving to git (as the rest of KDE) +[22:33:05] in any case, the enterprise5 branch is going to be based on KDE 4.5, the enterprise4 branch is based on KDE 4.4 +[22:33:47] ok thanks i'm going to add those info in a mail and try to revive the issue to users +[22:34:19] moving to next one +[22:34:19] also, it seems like KDAB doubts that they manage to get kdepim fixed in time for KDE 4.5 +[22:34:34] there will be a meeting in a few weeks where they are going to decide what to do +[22:35:11] one problem is that they got their branching all wrong and lost tons of commits for kmail trunk +[22:35:25] because people were comitting to the wrong branch... +[22:35:45] okie +[22:35:50] next one +[22:35:56] change kde-meta (and @kde-*) to include all modules (plus the developer specific ones) +[22:36:12] there were some ppl in the mail i send that liked my idea +[22:36:21] so i'd really like to move on this +[22:36:24] scarabeus: ^^? +[22:36:29] with useflag you can go ahead +[22:36:29] im still in favor of this if we use a USE flag +[22:36:31] I still don't like that +[22:36:49] At least not in kde-meta without a use flag +[22:36:51] dev || sdk +[22:36:59] both are nice use flags :) +[22:37:01] jmbsvicetto: what i said above :P +[22:37:05] :P +[22:37:34] ok, i'll add sdk useflag to kde-meta +[22:37:47] and leave sets as they are +[22:37:52] not as IUSE default :P +[22:37:54] i don't care about sets anyway +[22:37:58] of course not +[22:38:00] lol +[22:38:02] +1 +[22:38:27] sdk will contain bindings, kdewebdev and kdesdk? or should i leave bindings for now? +[22:38:53] do they work? +[22:39:03] they do not mostly] +[22:39:09] do they build? +[22:39:12] there are ppl working on them, so i guess they will in the near future +[22:39:20] scarabeus: which bindings do not work? +[22:39:31] csharp afaik +[22:39:35] if they build i vote on adding them, get people's attention :) +[22:40:11] ok, i'll leave them out for now then, and add them later when they all build +[22:40:24] afaik we don't even have a meta for bindings +[22:41:19] thank you for this, next one is patches of kde-packager +[22:41:32] jmbsvicetto / ABCD(absent): any news on this? +[22:42:18] tampakrap: sorry not yet +[22:42:34] so i guess you need help on this? +[22:42:39] I'll focus on this for 4.4.1 onwards +[22:42:40] any more ppl willing to help? +[22:43:07] i have to work on something different, so i have to blob out, so enjoy the rest of the meeting, i will reply to pongs, but wont read +[22:43:07] for latest topic i am with lieo (malformed for no highlight) +[22:44:10] no worries +[22:44:15] scarabeus: is it something with leads that makes them be away all the time? +[22:44:20] :D +[22:44:27] j/k ofc, c ya later +[22:44:46] let's raise the topic in next meeting to see if there will be any progress then +[22:45:05] last topic and most important +[22:45:10] split of desktop profile +[22:45:21] leio / yngwin: your attention plz :) +[22:45:47] :) +[22:46:40] leio: as i told you before, i really like the idea of mixed profiles and i am willing to work on it +[22:47:08] I like that idea as well +[22:47:11] but i can't have an eta as i don't have a stable schedule atm and i don't even know how much time it wants to be finished +[22:47:16] me too, but i expect that will take a while to implement +[22:47:23] --> pesa (~Pesa@host124-126-dynamic.52-82-r.retail.telecomitalia.it) has joined #gentoo-meetings +[22:47:27] so i'd really like to proceed on commiting the patches i have prepared +[22:47:50] so any objections? something wrong with them before i commit? +[22:48:48] no objections +[22:49:38] i haven't tested them (and i don't use the desktop profile :p) but i really like the idea, +1 +[22:51:06] <-- pesa (~Pesa@host124-126-dynamic.52-82-r.retail.telecomitalia.it) has left #gentoo-meetings ("Konversation terminated!") +[22:51:20] leio seems away, so if you want you anything more you can pm me +[22:51:38] i'll commit it this sunday fyi, i'll be out of town the next two days +[22:52:10] well, you know what I think +[22:52:26] (was here at start, but had a phone call afterwards) +[22:53:36] cool, i'd take it as a :thumbup from the gnome team and proceed +[22:53:42] we have had the single desktop profile situation for, what? four years? So even waiting 3 months more to get the better method implemented would sound fine in my book, but as I can't work on that myself, I can't well argue against more subprofiles meanwhile +[22:55:00] point taken +[22:55:32] i guess the meeting is over, I'd also like to inform you i have updated docs, please check for any issues diff --git a/meeting-logs/20100604-summary.txt b/meeting-logs/20100604-summary.txt new file mode 100644 index 0000000..dcd7c9b --- /dev/null +++ b/meeting-logs/20100604-summary.txt @@ -0,0 +1,21 @@ +Meeting topics: +0) roll-call +ABCD, alexxy, dilfridge, wired, scarabeus, deathwing00, patrick, jmbsvicetto +1) KDE 4.4 Stabilisation process. - creating stable team within kde team +We will add 4.4.4 to main tree, and start the required processes 7 days from that point. +No stable team since noone volunteer. +2) KDE 4.5 KDEPIM approach + a. give developers one week to express what they feel about kdepim and to see if anyone volunteers to work on it + b. if that fails or we can't find anyone willing to do it, make a public announcement about the issue, explain it and give a few options to users: + b.1 have interested parties show up and work in the overlay to get it done - (what can be given as option to the community) + b.2 have users vote for us to just ignore kdepim until it gets working + b.3 give the above 3 options for someone to work on +3) Koffice 2.2 and designated maintainer choice +we shall try same approach as for kdepim to see if anyone is interested +4) Accepting major patches that alter stable branch (pulseaudio) [vote] +so lets keep status "if you keep it backported and polished you can have it..." together with the old "you break it, you fix it" +5) People in the team and their inactivity +Everyone in team is asked to reconsider their status. If they are not really active team members they should just remove themselves. +Everyone with no evident work on kde packages for last 2 months will be removed from the team. +Anyone who wants to join back or just join is welcome and just need to ask and be active. +6) open floor \ No newline at end of file diff --git a/meeting-logs/20100604.txt b/meeting-logs/20100604.txt new file mode 100644 index 0000000..3f12f31 --- /dev/null +++ b/meeting-logs/20100604.txt @@ -0,0 +1,282 @@ +[21:59:58] * scarabeus has changed topic for #gentoo-meetings to: "Gentoo meetings | KDE Team meeting | topics: http://paste.pocoo.org/show/222007/" +[22:00:43] -*- ABCD is here +[22:00:45] lets get slowly started +[22:00:51] so step 0: roll call +[22:00:51] -*- dilfridge is here +[22:00:52] -*- wired suprizingly here +[22:00:52] who is around +[22:01:02] --> krytzz (~quassel@quassel/user/krytzz) has joined #gentoo-meetings +[22:01:17] thats all? +[22:01:22] lol +[22:01:34] --> deathwing00 (~deathwing@gentoo/developer/Deathwing00) has joined #gentoo-meetings +[22:01:37] -*- ABCD is here (again, because I said it before roll call started) +[22:01:38] w00t? +[22:01:50] wot? +[22:01:52] ok, before anyone brings up any topic +[22:01:56] let me say just one thing +[22:02:39] my commit access will be disabled starting this month June 2010 and will be re-enabled July 2011, as I will be doing an MBA that will take most of my time away, besides I was promoted to team leader in Flumotion and that adds me even more workload +[22:02:48] said that, good luck guys :) +[22:02:58] deathwing00: cheers, and happy birthday :] +[22:03:01] you really think you won't have time for 1 commit? hehe +[22:03:15] good luck to you too :) +[22:03:35] --> mschiff (~mschiff@d000042.adsl.hansenet.de) has joined #gentoo-meetings +[22:03:37] :) +[22:03:38] !herd kde +[22:03:38] thanks +[22:03:38] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, tampakrap, tgurr, wired +[22:03:43] wake up rest of you +[22:03:47] there is more than 10 people +[22:04:16] scarabeus: laters then :) +[22:04:24] I'll still be around in jabber ;) +[22:04:25] hmm... time for small talk... +[22:04:27] <-- deathwing00 (~deathwing@gentoo/developer/Deathwing00) has quit (Quit: Leaving.) +[22:04:47] ok, lets get started, and i will kick their asses later +[22:05:02] so 4.4 and its stabilisation +[22:05:08] rrrrrrringdingding! +[22:05:12] the bug is not moving anyhow promisingly +[22:05:36] many things are there since 4.3.x times +[22:06:10] yes the main quesiton is +[22:06:16] how about we put 4.4.4 to main tree +[22:06:21] and ask for stabilisation in 1 week +[22:06:25] no matter what is left +[22:06:43] sounds fine to me - 4.4.4 should just be bugfixes on 4.4.3, right? :D +[22:06:46] but basic thing i would like to say is that i would like to see designated team that would handle the stables +[22:06:49] probably not better nor worse than 4.4.3 +[22:06:52] they will run the stable +[22:07:05] and will be responsible for proactively stabling and pestering us all for fixing stable bugs +[22:07:12] -*- dilfridge hears some coconuts in the background +[22:07:48] well who else besides me runs 4.4.[34] here still? +[22:08:15] i have 4.4.3 +[22:08:16] sorry, got distracted +[22:08:16] :] +[22:08:18] -*- ABCD doesn't because his hard drive broke +[22:08:28] jmbsvicetto: by accident you dont run stable huh? ;} +[22:09:40] I runn 4.4.4 +[22:09:46] also good +[22:09:48] So any other ideas how to handle this situation? +[22:09:51] run* +[22:10:09] well the only other alternative would be to stable 4.4.3 +[22:10:10] scarabeus: about the 1 week we must be ready for arch teams to tell us they'll wait the usual month +[22:10:31] nah, they wont get to that bug before the month will come anyway +[22:10:37] in any case, I think the most important issue is the deps. Are we sure all 4.4.4 deps are marked stable? +[22:10:50] expect amd64 and x86 which mostly will do what we ask them +[22:10:52] did the deps change from 4.4.3? +[22:11:17] dependecies were not changed +[22:11:22] ABCD: 4.4.3 isn't stable, right? iirc, the latest stable is 4.3.5 +[22:11:29] yes +[22:11:34] scarabeus: and no, I don't run stable +[22:11:55] also, what about kdepim? Will that only affect 4.5? +[22:11:58] jmbsvicetto: i think our problem is that we all rock on ~ or even further +[22:12:01] -*- dilfridge has a fully stable x86 chroot rotting somewhere +[22:12:10] jmbsvicetto: kdepim is affected only 4.5 and it is next topic :] +[22:12:20] jmbsvicetto: it isn't, but if its deps were stable, then there shouldn't be much of an issue +[22:12:21] dilfridge: sadly you are not dev yet whom can fill those requests :] +[22:12:30] scarabeus: that's to be expected +[22:12:35] (us running ~) +[22:12:41] yes +[22:12:49] but then we would expect archies to fill stablerequests +[22:12:56] we have tons of various packages just in ~ +[22:13:00] but anyway ~ is better than ~+pmasked +[22:13:03] because nobody ever bothered to fill the bugs +[22:13:15] it's up to us to ask for packages to be marked stable, but it's up to arch teams to take care of it +[22:13:31] (and to wait for 30days...) +[22:13:36] yes, and who else would have better motivation to ask for stables than people running it +[22:13:40] I'm planning to add a request for amarok soon +[22:13:56] but I need to check the status of the deps +[22:14:16] I'll probably go for 2.3.0.90 or 2.3.1 directly and then drop all the older versions +[22:14:50] sounds sane :] +[22:14:56] I'm also likely to merge amarok and amarok-utils as I don't see any interest on amarok-utils +[22:15:10] so i guess my plan with arch team wont work since we dont have anyone interested in it :P +[22:15:21] so only question left is which version 4.4.3 or 4.4.4 +[22:15:31] devs plz pick :] +[22:15:35] jmbsvicetto: sounds also sane :] +[22:15:39] well, most of us already have the blessing to do the work for amd64 +[22:16:05] I'd say 4.4.4 if we can convince the archies to do it in 7 days instead of 30 +[22:16:06] at this point, we can probably target 4.4.4 +[22:16:16] ok +[22:16:28] 3 out of 5 attending devs +[22:16:32] added to summary +[22:16:37] next topic then +[22:16:40] kdepim 4.5 +[22:16:45] ugh +[22:16:49] ABCD: past history has showed that it takes a bit more than 1 or 2 weeks since we plan to ask for a package to get marked stable and to the request get to the arch teams ;) +[22:17:12] i also vote for 4.4.4 +[22:17:19] btw we can stable amd64 ourselves +[22:17:26] --> raxas (~raxas@charybdis-1-pt.tunnel.tserv6.fra1.ipv6.he.net) has joined #gentoo-meetings +[22:17:28] besides, has anyone hit any regression from 4.4.3 to 4.4.4? +[22:17:28] yes yes +[22:17:33] no +[22:17:47] one last thing before we move on to kdepim +[22:17:48] I haven't, but I didn't check the kdm user thing yet +[22:17:56] No regressions from 4.4.3->4.4.4 here +[22:18:14] we will probably be drowned in akonadi problems when 4.4.x gets stable +[22:18:25] dilfridge: aware of that :/ +[22:18:29] hmm, I did restart kdm on my desktop and it's working, so I don't think that's an issue afterall +[22:18:41] (i was always too lazy to file a bug, but on my 3 machines it never started working properly) +[22:18:57] -*- scarabeus does not even have kdepim installed +[22:19:00] too big pile of... +[22:19:06] anyway +[22:19:10] we have 3 options at our hands +[22:19:12] I like(d) it... +[22:19:15] dilfridge: if you mean about kdepim, I don't have it installed locally :P +[22:19:22] ship kdepim from trunk with 4.5 releases, our tarballs +[22:19:30] make 4.5 work with 4.4 kdepim +[22:19:36] or finaly package enterprise branch +[22:19:48] scarabeus: Perhaps we should start by making 2 questions: +[22:19:59] 1. Which devs care or want to "mess" with kdepim +[22:20:06] second is probably the easiest, as all distros wil do that right? +[22:20:32] krytzz: second is indeed easiest +[22:20:39] 2. and depending on that we can just start a vote on the forums/mls/* explaining the issue to the users and getting a "vote" on how to proceed +[22:20:42] jmbsvicetto: alexxy was interested but sadly is not here +[22:20:55] i am definitely not interested in kdepim +[22:20:59] if that part of kde disappeared +[22:21:01] i would be happy man +[22:21:10] among with semantic-desktop team +[22:21:11] :D +[22:21:21] I don't plan to touch kdepim too +[22:21:23] -*- dilfridge would probably skip that release then as he need kdepim +[22:21:42] dilfridge: pst, we switched to claws and thunderbird, they works +[22:21:49] hehe +[22:22:01] I've always used FF and TB, so no change for me ;) +[22:22:11] ok so seems noone is interested in this topic +[22:22:18] so lets postrpone it, i will sent mail to alias +[22:22:23] and i will pray that someone reply +[22:22:24] scarabeus: what about my proposal? +[22:22:27] what about reavertm, he did some work with pim :p +[22:22:37] jmbsvicetto: the forums are good idea, but first we need to pass step 1 +[22:22:43] scarabeus: we could set a plan like the following: +[22:23:09] 1. give developers one week to express what they feel about kdepim and to see if anyone volunteers to work on it +[22:23:43] 2. if that fails or we can't find anyone willing to do it, make a public announcement about the issue, explain it and give a few options to users: +[22:24:11] 2.1 have interested parties show up and work in the overlay to get it done - (what can be given as option to the community) +[22:24:18] ok +[22:24:25] 2.2 have users vote for us to just ignore kdepim until it gets working +[22:24:26] will 4.5 be released one month afterwards? in that case you could postpone the whole 4.5 release for 1 month? +[22:24:26] from what I heard, kdepim may show back up in 4.5.1 or 4.5.2 +[22:24:28] that sounds like nice sumup +[22:24:37] 2.3 give the above 3 options for someone to work on +[22:25:23] ABCD: with shitload of bugs +[22:25:40] that's beside the point :D +[22:25:41] jmbsvicetto: added your approach to summary, since it sounds like only sane :] +[22:25:45] that's what 4.5.3456 will be for +[22:26:02] koffice-2.2 +[22:26:09] dilfridge: i saw you working on it :] +[22:26:18] yes and it works afaik +[22:26:21] That's another thing I don't plan to work on +[22:26:24] so wanna be designated maintainer? +[22:26:38] puh... I'm not actively using it so bad choice... +[22:26:53] (whenever I tried ooo did the job better) +[22:27:13] but I can look after it a bit yes +[22:27:33] scarabeus: we could perhaps use this chance to ask for volunteers to work on koffice and kdepim +[22:27:50] (not that I expect a horde to show up) +[22:28:19] well we need 2.2.0 in main tree stabilised asap +[22:28:26] because 2.1 is seriously useless +[22:28:29] I'd rather volunteer for some kdepim stuff than koffice... +[22:28:49] :DDD +[22:28:55] <-- brk (~brk@r9dq22.net.upc.cz) has quit (Ping timeout: 260 seconds) +[22:28:57] dilfridge: s/and/and or/ +[22:29:00] lets try same approach as for kdepim then +[22:29:27] NEEEXT :D +[22:29:44] so dagger sent me mail +[22:30:01] if we would accept pulse patches +[22:30:01] that makes it work in kmix +[22:30:02] for now on we have policy that we dont backport patches +[22:30:41] so lets vote about wheter to accept patches or be strictly what upstream sends +[22:30:57] scarabeus: since when? we always tried to follow upstream as closely as possible, but if someone is willing to apply a back-port and to keep it working, why not? +[22:31:03] -*- alexxy here =) +[22:31:07] just write upstream/distro-patches based on what you want (only devs) +[22:31:15] jmbsvicetto: acutaly we declined quite few backports +[22:31:39] jmbsvicetto: for konsole in example +[22:31:42] as long as we don't want to do it and there's no one in the team willing to do it, it's ok by me +[22:31:57] scarabeus: iirc, ssuominem applied that patch again +[22:32:27] I don't follow commits closely, but by reading the bugzilla mail, I think a few have been applied +[22:33:12] so lets keep status "if you keep it backported and polished you can have it..."? +[22:33:17] backports++ from me if they fix stuff ;) +[22:33:32] scarabeus: together with the old "you break it, you fix it" ;) +[22:33:43] jmbsvicetto thats a must :P +[22:34:05] ok added to summary +[22:34:13] now the topic that is quite important +[22:34:23] oh and about pulseaudio, I no longer care!! /me is using phonon-vlc :) +[22:34:37] lol +[22:34:42] so inactive people in team +[22:34:45] what the f**k is everyone doing +[22:34:51] there is 17 people in the team +[22:34:54] -*- jmbsvicetto goes hidding in the back +[22:34:55] ... +[22:34:56] :D +[22:35:14] scarabeus: I guess the other 16 guys are very active :P +[22:35:14] on this meeting we have star attendance of 5 developers +[22:35:24] very very active +[22:35:24] well +[22:35:40] he he =) +[22:35:50] scarabeus: you're to blame for this instance +[22:35:58] you chose FRIDAY EVENING +[22:36:05] failday for meeting :p +[22:36:09] i dont mind attendance for meeting +[22:36:11] scarabeus: talking for myself, I took a lot of work when things were stalled, then you guys all started doing so much, I got used not needing to do too much ;) +[22:36:16] its beerday +[22:36:16] =) +[22:36:24] but there is almost no activity on tree or ovelray by team members in kde area +[22:36:29] right... only people without friends are online now +[22:36:38] not counting few active ones +[22:36:45] krytzz: thanks :P +[22:36:48] so since joining team is really simple +[22:36:50] \o/ +[22:37:10] i would like to ask all those who are not really into working at least bit on kde remove themselves from herd +[22:37:17] they are mostly active in other areas of gentoo +[22:37:31] scarabeus: Now you know how fun it is to have the pointy hat ;) +[22:37:36] and it would at least show me list of people i can count in +[22:37:56] scarabeus: thats not going to work, most of them aren't even here :P +[22:38:11] and i will forceremove everyone who dont have at least 1 commint in last 2 months +[22:38:17] wired: it will be on summary +[22:38:36] they can join in back and be active +[22:38:51] or just commit here and there with our permission as other nonteam devs do now +[22:39:14] bonsaikitten: that counts you too ;] +[22:39:35] scarabeus: ok, let me be clear about my commitment: I plan to do amarok as long as no one takes it out of me, I'm interested in phonon-vlc for the moment, I also have an interest on kdenetwork. I try to look at bugs and I get interested on stuff sent to packagers. I do however have a few other areas where there aren't active people on, so they sometimes take priority +[22:39:40] <-- ABCD (~abcd@gentoo/developer/abcd) has quit (Ping timeout: 265 seconds) +[22:40:03] jmbsvicetto: you do commits in packages that have herd kde +[22:40:19] jmbsvicetto: there are people that didnt do any commit in those 2 named months back any of that +[22:40:21] scarabeus: yeah, that's fine with me +[22:40:23] yeah, but I know I don't do many commits +[22:40:26] (i did some research) +[22:40:33] -*- alexxy plays with beta/rc/snaphsots stuff +[22:40:34] jmbsvicetto: but you do something :] +[22:40:34] I'm mostly honorific member ;) +[22:40:51] the last thing i did was fix koffice 2.1.81 +[22:40:51] ;p +[22:40:55] there is thin line between something and nothing +[22:41:27] -*- jmbsvicetto gives a swift kick in bonsaikitten's honorific *slacker* member :P +[22:42:04] jmbsvicetto: you sound fat! +[22:42:08] you know I was looking at the slacker definition the other day and it said also known as bonsaikitten or patrick +[22:42:11] ;p +[22:42:12] bonsaikitten: :P +[22:42:22] wired: hehe +[22:42:31] =) +[22:42:50] ?D +[22:42:52] ok +[22:42:58] =P +[22:42:59] wired: He has a bit to learn to catch some champs ;) +[22:43:00] i guess that is all of mine topics +[22:43:03] omg +[22:43:04] so +[22:43:08] you have something to discuss +[22:43:19] http://paste.pocoo.org/show/222014/ +[22:43:19] a 40 minutes meeting? O_O +[22:43:23] also here is current summary +[22:43:25] my 50 cents about kdepim +[22:43:29] i planned 10 minutes for each +[22:43:34] we were faster +[22:43:52] i plan to package tarballs for 4.5.0 +[22:43:54] =) +[22:44:14] nice +[22:44:18] alexxy: that is mostly too late :P now you will have to work with others over mail : +[22:44:19] ] +[22:44:29] reavertm: what are you planning to do with the cmake-utils eclass and was there any reason for the revert? +[22:45:52] alexxy: also remember that people will want to kill you if you blow up their mail client :D +[22:46:03] 1 thingie, anyone did log? +[22:46:06] for the log... +[22:46:07] :] +[22:46:12] i have just summary +[22:46:14] sure +[22:46:19] i have log +[22:46:21] =) +[22:46:45] so do i \ No newline at end of file diff --git a/meeting-logs/20100902-summary.txt b/meeting-logs/20100902-summary.txt new file mode 100644 index 0000000..ff368de --- /dev/null +++ b/meeting-logs/20100902-summary.txt @@ -0,0 +1,37 @@ +1) KDE 4.5 status and plans to put it in Portage + +We agreed that KDE 4.5.1 is suffering of some important bugs, and after +a long discussion we decided to put it in portage, but it will never +make it to stable branch. We are mentioning the upstream bugs, as we +think that users should be aware of them before updating: + +- https://bugs.kde.org/show_bug.cgi?id=247144 +- https://bugs.kde.org/show_bug.cgi?id=246931 +- https://bugs.kde.org/show_bug.cgi?id=230247 <-The most important + +Also, keep in mind that KDE SC 4.5 lacks the KDEPIM suite, so users +should use KDEPIM 4.4.5 instead, which is also stable in portage tree. +In case of an update it should be smooth. + +2) KOffice 2.2 status + +There are a few issues with it. The bump to 2.2.2 won't be so easy, +and most of the linking taking place in koffice-libs is not perfect. +dilfridge and tampakrap will take care of it, but it may not happen soon. + +3) KDEPIM beta packages are released + +This was skipped as alexxy, our snapshots master, was absent. It will +be discussed in gentoo-desktop mailing list + +4) Open Floor + +- dilfridge reported that digikam is almost ready, he cleaned up the +patches a lot and will tell reavertm when to move them upstream +- tampakrap reported that he is going to unmask knetworkmanager +- reavertm encouraged people working with live and tagged ebuilds to use +kde-misc/kde-overlay-servicemenus. It is a simple Compare/Merge service +menu, to avoid manual copy paste. +- tampakrap, as substitute leader, is going to remove some inactive team +members, as there were a lot of notices in the past. + diff --git a/meeting-logs/20100902.txt b/meeting-logs/20100902.txt new file mode 100644 index 0000000..4da84bc --- /dev/null +++ b/meeting-logs/20100902.txt @@ -0,0 +1,234 @@ +[21:14:55] roll call +[21:15:02] 1 +[21:15:05] 2 +[21:15:07] 3 +[21:15:18] we lost abcd +[21:15:28] 4 +[21:15:34] and i am number five +[21:15:55] i would like to have a small talk about amarok in the +end if jmbsvicetto manages to find us +[21:15:59] either way: +[21:16:02] not even a quorum (for most definitions of "quorum") +[21:16:08] +http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/maintainers/meetings/meeting-2010-09-02;h=e5a2764f178127e3f04e3311c12563b68a1b8dbe;hb=HEAD +[21:16:15] here's the agenda +[21:16:23] 1) KDE-4.5 status and plans to put it in Portage +[21:16:29] reavertm: you can start +[21:16:39] ok, here it is: +[21:17:04] there are following issues I'd consider a blockers +[21:17:26] (unless we say - screw you users - upstream) +[21:17:53] https://bugs.kde.org/show_bug.cgi?id=230247 +[21:18:47] hmm here everything works fine _since_ the upgrade to +4.5.0 +[21:19:02] result - you need to start any akonadi-client app twice +in order to use it (first start will make akonadi start bug won't detect that +it started) +[21:19:18] but I'm not logging in/out very often +[21:19:38] one blocker - kwin FBO bug has been fixed (commit +reverted as I requested) +[21:19:56] remaining ugly bugs: multiple plasma glitches in system +tray +[21:20:20] plasma glitches were highly reduced in 4.5.1 +[21:20:31] not seen for a while +[21:20:37] https://bugs.kde.org/show_bug.cgi?id=246931 +[21:20:45] if the akonadi bug is the only blocker i'd say let's +put it in tree, and let the people know about it +[21:20:46] no, they are still there +[21:21:02] tampakrap: and spam out bugzilla for no reason? +[21:21:20] ah that yes that is still there... I got used to that +bug... +[21:21:27] https://bugs.kde.org/show_bug.cgi?id=247144 - another +plasma glitch (folderview) +[21:21:39] and most important - memory leaks in plasma-desktop +[21:21:49] (minor leaks, but they are there) +[21:22:19] dolphin tooltips issues as well as nepomuk related +crashes seen to be gone at least +[21:22:49] i'd suggest let's put it in tree, but announce those +bugs and make it clear that it's not going to be stabilized +[21:22:50] oh, and one bug present in 4.4 alteady - +https://bugs.kde.org/show_bug.cgi?id=247204 +[21:23:07] i'm getting enough spam on IRC already, and i think it +is usuable enough +[21:23:21] that's my opiniion, but it is your call mostly +[21:23:24] with that state I don't think *any* 4.5 patch release is +going to be stabilized, I won't allow it +[21:23:31] there are regressions in every major release but that's why +we have testing. 4.5.1 seems good enough for tree +[21:23:50] seconded (I personally can work with it fine) +[21:23:53] unless we clearly communicate - "we know it's broken - +we reported bugs and they keep being ignored" +[21:24:17] reavertm: give me a list of the bugs, i can put them on +the meeting summary +[21:24:18] 4.4 took a lot of time to be stabilized because of +regressions too, that's how kde works, apparently +[21:24:26] and put the summary on my blog on planet gentoo and kde +[21:24:32] I won't wrange any 4.5 bugs in our bugzilla, I want to +make it clear :P +[21:25:09] spatz: plasma devs utilized 'Broken Development Model" +that's why +[21:25:31] I'm not pointing fingers, just stating facts :) +[21:26:05] ok, we made our points, reavertm: your call +[21:26:13] tampakrap: fine, but you'll blog about it :) (with bug +links there) +[21:26:14] since you fixed a couple of upstream bugs +[21:26:23] aah, one more blocker +[21:26:32] but on our side - handbooks handling +[21:26:38] yes that is true +[21:26:51] something is seriously broken there +[21:27:01] bug #? +[21:27:28] bug 296345 +[21:27:29] since 4.5 - docbooks are no longer bundled - so for +every +handbook we need to pull docbook stuff like for kdelibs +[21:27:30] dilfridge: https://bugs.gentoo.org/296345 "kde 4.4.4: +Compilation error when creating help search index - bad xslt pattern"; Gentoo +Linux, KDE; NEW; ashl1future@gmail.com:kde@g.o +[21:27:49] ah different problem +[21:27:52] err, i meant different handbook issue +[21:28:40] if there is no bug #, let's open one, fix that first +and then put 4.5.1 to tree +[21:29:12] I can fix it anyway (my handbook isse) - for instance by +introducing KDE_HANDBOOK eclass variable instead of +handbook in IUSE (that +could hold additional handbook dirs as well) +[21:29:41] ok +[21:29:49] anything else on this? +[21:30:10] I think this is it wrt kde 4.5 +[21:30:29] i have one more thing to say about it +[21:30:36] not so relevant +[21:31:11] ? +[21:31:12] http://bugs.gentoo.org/show_bug.cgi?id=335123 +[21:31:43] hmm, works for me... +[21:31:45] these patches don't apply to kdepimlibs 4.5.0 and i +don't know if by applying them to 4.4.5 only will break 4.5 as well +[21:31:59] i can reproduce here and the patches worked on my 4.4.5 +laptop +[21:32:23] so, any ideas? +[21:32:36] does it affect only kde 4.5 + kdepim 4.4? +[21:33:00] or it's some general bug? +[21:33:01] the patches are meant for 4.4.5 only, haven't tested to +4.5 +[21:33:32] but i don't want to introduce a new bug by applying the +patches to kmail 4.4.5 and not to kdepimlibs 4.5.x +[21:34:08] I'd prefer them to appear in svn.. +[21:34:13] never had this problem here +[21:34:51] ah they are not taken from svn +[21:34:54] nice point +[21:35:04] ok thanks +[21:35:10] next issue i guess +[21:35:20] 2) KOffice 2.2 status +[21:35:35] -*- reavertm shuts up +[21:35:46] i was away because of my thesis and vacations for too +long, anyone knows the blockers of keeping this away from tree? +[21:35:48] needs bump to 2.2.2 (I had no time yet but that should +not be difficult) +[21:36:10] there is a "workaround" +[21:36:13] -*- reavertm disagrees, he saw multiple cmake changes and file/dir +additions/removals +[21:36:24] ok have not checked yet +[21:36:58] considering kchart +[21:37:10] I see when do svn update in koffice occassionally, it +needs someone to closely follow up - and in our case when it's been abandoned +for a while - full review from scratch likely +[21:37:27] The libraries do not link if kchart is not built at the +same time, so what I did was +[21:37:48] do make a dummy ebuild for kchart for the meantime. +[21:37:51] KMCOMPILECONLY can be used +[21:38:06] well it is done in koffice-libs +[21:38:17] but I wanted to keep something named kchart in portage +[21:38:26] so later upgrade remains painless +[21:38:42] is it standalone app? +[21:38:55] so, now koffice-libs also installs kchart, and kchart +does, well, nothing +[21:39:13] no I think only library +[21:39:37] i see +[21:39:43] apart from that nobody gave me negative feedback on +2.2.1 yet +[21:39:50] i'd appreciate if there were more comments on the bug +[21:39:56] http://bugs.gentoo.org/show_bug.cgi?id=322147 +[21:39:59] then should be in koffice-libs imho - I'd like to avoid +creating excessive libraries like used to be in kdepim +[21:40:00] --> pesa +(~Pesa@host169-125-dynamic.52-82-r.retail.telecomitalia.it) has joined +#gentoo-meetings +[21:40:02] and i could help you with it +[21:40:20] i agree with that +[21:40:48] fine with me... but the plan is that kchart can be +built separately again with 2.3 +[21:41:33] is it already done in the live ebuilds? +[21:41:47] did not check yet +[21:41:51] ok +[21:41:51] maybe they'll just add some host for that kpart, then +kchart ebuilds will be justified, (but libkchart should still be in +koffice-libs imho) +[21:42:28] it can be embedded in any koffice app after all +[21:43:07] ok, i'm done with it, dilfridge any further comments? +[21:43:15] I'm kind-of-away from tomorrow for a week, so if +anything should be done quickly I'm out +[21:43:30] but I guess its not that urgent +[21:43:34] -*- reavertm needs to remember how it was decided - koffice-libs +contains full functionality and kword for instance only word processor +application (but kpart is provided by koffice-libs) - or installing kword +makes kpart available +[21:43:35] indeed +[21:44:08] if the kpart is used by other ebuilds too it should be +in koffice-libs +[21:44:15] else the split makes no sense +[21:44:35] we can find that out with the dependencies / linking +[21:44:47] since now all apps are for sure compiled after kchart +[21:44:52] no, kparts are runtime-only things mostly +[21:45:03] ok true +[21:45:20] (well, buildtime+runtime, but can be missing at runtime) +[21:45:45] i'd say we could give 2.2.1 a try +[21:45:59] -*- dilfridge keeps fingers crossed +[21:46:11] ok +[21:46:24] next? +[21:46:27] fine, but I'd suggest full review of them (for instance +to check whether all koffice subdirs are packaged in ebuilds) +[21:46:54] reavertm: teach me how to do that, please! :) (in two +weeks) +[21:47:35] ok next +[21:47:49] for next issue i would like alexxy but he seems not to +be here +[21:47:57] simple - take a look at koffice/ and check subdirs one +by one against koffice ebuilds (KMEXTRA, KMCOMPILEONLY, KMEXTACTONLY) +[21:48:25] ok +[21:48:48] 3) KDEPIM beta packages are released +[21:48:51] i'll skip it +[21:49:00] and add a gentoo-desktop thread instead +[21:49:05] we just want whole koffice covered (or some parts +*intentionally* skipped) +[21:49:14] ok +[21:49:27] skip it please +[21:49:36] I don't want kdepim betas in overlay :P +[21:49:47] (there are live ebuilds already) +[21:50:11] sebas stated in his blog that upgrade and downgrade +would be easy since configs don't affect each other +[21:50:50] either way, we'll discuss it in gentoo-desktop +[21:50:55] 4) open floor +[21:51:20] about digikam +[21:51:41] the patches are cleaned up a lot, but it's not +completely finished yet +[21:52:02] <-- spatz (~spatz@gentoo/developer/spatz) has quit (Ping timeout: +276 seconds) +[21:52:23] reavertm: if you want to have a look at it go ahead, +but dont send anything upstream yet. +[21:52:46] at least 1.4.0 should now build fine +[21:53:04] I'll talk with the sci guys about clapack. +[21:53:11] I'll wait +[21:53:21] i'm also going to unmask knerworkmanager very soon, +please test +[21:53:34] i'm a bit worried about the versioning though +[21:54:47] ah, as of open floor - I encourage people working with +live and tagged ebuilds to use kde-misc/kde-overlay-servicemenus +[21:55:07] what does it do? +[21:56:00] I've added simple Compare/Merge service menu - in +dolphin select two files one by one to have them open in kompare (where you +can interactively sync them) +[21:56:15] to avoid manual copy paste +[21:56:17] w00t +[21:56:19] nice +[21:56:43] last issue, i'm going to remove a few inactive people +from the team +[21:57:14] and if there is not anything else, i guess i should +close the meeting +[21:57:33] thanks +[21:58:08] meeting is over diff --git a/meeting-logs/20110210-summary.txt b/meeting-logs/20110210-summary.txt new file mode 100644 index 0000000..c38edf6 --- /dev/null +++ b/meeting-logs/20110210-summary.txt @@ -0,0 +1,107 @@ +Present: alexxy, dilfridge, jmbsvicetto, scarabeus, tampakrap +Absent: ABCD, spatz +HTs: krytzz, papillon81 + +0) Elect new lead + +nominees: +Accepted: bonsaikitten, dilfridge, reavertm, tampakrap +Refused: alexxy, jmbsvicetto, scarabeus + +results: +scarabeus -> tampakrap +dilfridge -> tampakrap +bonsaikitten -> tampakrap +tampakrap -> reavertm +alexxy -> tampakrap +reavertm -> tampakrap +jmbsvicetto -> tampakrap + +tampakrap is the new KDE Team Lead + +1) Status regarding hal + +Since KDE SC 4.6 is out, we don't need it anymore. As soon as 4.6 +gets stable, hal can die. + +2) Should we try to form a "stable KDE devs" team? Meaning just call for volunteers on the dev ml? + +dilfridge stated that since most of the kde team members use ~arch, +stable seems to lag behind. The problem is very obvious now, mainly +because we haven't stabilized 4.4. The problem will go away as soon +as 4.6 gets stable though. +Apart from main kde, the misc apps are also slow in stabilization. +We expect users to request for stabilizations in bugzilla. + +3) kde-git/eclasses migration and status, move kdepim 4.6 beta in tree masked + +reavertm, Sput, and scarabeus did a major cleanup in our eclasses +and added git support to eclasses and ebuilds. In order to migrate +the eclasses to tree we will need to get git-2.eclass in tree first +(it is now in kde overlay as well). ETA: not less than a month. As a +side note, we decided to remove koffice-specific codeout of the eclasses. + +4) Shall we drop useflags kdeenablefinal and/or kdeprefix to simplify code? + +First of all, both useflags are masked. We agreed to keep kdeenablefinal, +since it is an upstream feature. About kdeprefix, the problem is that +bindings are not prefixed, and a possible fix (proposed by reavertm) +would be to slot sip. tampakrap said he'll work on this, and bring the +topic back in next meeting. + +5) Dropping of semantic-desktop useflag with guide update (mostly even kdebase needs it on now) + +This entry is invalid, semantic-desktop is not needed by kdebase. +The problem is in our ebuilds (plasma-workspace is semi broken, +kdeplasma-addons is completely broken). We have open bugs for those, +the problem is clearly in our side. + +6) Making +consolekit and +policikit or removing the useflags as whole (non working stuff run-as is annoying) + +scarabeus and dilfridge are in favour of dropping them, since it +caused a lot of trouble debugging various user reports. reavertm +prefers adding it to IUSE defaults. No consensus was succeeded, +the topic will be continued in the gentoo-desktop mailing list. + +7) HT/overlay/bugzie access policy + +Since we don't have a clear list of who is an HT and who isn't, we +decided to compile a list, and state what priviledges the HT has. +(HT = Herd Tester). Some people don't have time/motivation to complete +their ebuild quiz, thus we'll have two groups of people: + * full HTs (overlay access, editbugs, access to ktown, IRC cloak) + * overlay commiters +We decided to drop the KDE HT Lead title, seems rather useless. + +8) LiveDVD issues + +LiveDVD comes with KDE SC 4.6 as default DE, and we called likewhoa +(the guy behind it) to report any issues. He said that everything +seems to be fine, but random users wanted the cool gentoo graphics +to be applied to in-tree ebuilds as well. The KDE Team is willing +to do that, likewhoa said he'll provide us some artwork and we'll +discuss again the USE="branding" issue. + +9) documentation status + +There has been a major improvement in the guide, added some 4.6 specific +tips and troubleshooting parts, we need to add a hal->udev migration +guide, and migrate some texts that are in kde overlay to guidexml. + +10 & 11) 4.6 (and misc apps with 4.6) status , Early discussion about 4.6 stabilization + +KDE SC 4.6 is going fine, we all agreed that 4.6.1 could be a good +candidate, we'll discuss it again after its release. About a 4.6 +KDEPIM version, no idea yet, we'll have to wait on upstream moves first. +Most misc apps seem to be fine with 4.6 as well. + +*) Open floor + +One major issue is digikam, it comes with lots of bundled libraries, +which violates the Gentoo QA Policy. We heard that Debian has same +thoughts on the matter, we'll have to bring them to table. Relevant +bug report: https://bugs.kde.org/show_bug.cgi?id=265328 + +Desktop Summit! We were invited last year to Akademy to give a talk +about Gentoo-KDE, noone made it. Some of us expressed interest for +this year's event, which combines GUADEC and Akademy. \ No newline at end of file diff --git a/meeting-logs/20110210.txt b/meeting-logs/20110210.txt new file mode 100644 index 0000000..8adcf02 --- /dev/null +++ b/meeting-logs/20110210.txt @@ -0,0 +1,566 @@ +[21:01:20] lets roll +[21:01:27] rollcall lads +[21:01:29] !herd kde +[21:01:29] (kde) abcd, alexxy, dilfridge, jmbsvicetto, patrick, reavertm, scarabeus, spatz, tampakrap +[21:01:32] wait wait +[21:01:43] ohhh +[21:01:47] -*- jmbsvicetto hides +[21:01:54] i completely forget about meeting +[21:02:30] tampakrap: sup +[21:03:14] need to ping more people +[21:03:22] here +[21:03:24] so lets wait on tampy +[21:03:53] bonsaikitten: you are around? +[21:04:01] aye aye captain +[21:04:11] he is square =) +[21:04:26] (not for much longer i hope) +[21:04:41] anyway, let's go +[21:05:39] --> krytzz (~quassel@quassel/user/krytzz) has joined #gentoo-meetings +[21:06:36] so there are two guys whom can be lead +[21:06:38] --> papillon81 (~papillon8@g230050057.adsl.alicedsl.de) has joined #gentoo-meetings +[21:06:41] bonsaikitten and tampakrap +[21:06:45] greets +[21:06:50] so guys do you accept nomination? +[21:07:14] yes, and i nominate you and jmbsvicetto as well +[21:07:21] no!! +[21:07:33] -*- papillon81 nominates scarabeus, too, but knows he can't vote +[21:07:46] -*- scarabeus humbly does not accept the nomination, cause he does not use this mess anymore :) +[21:07:52] LOL +[21:07:55] -*- reavertm nominates scarabeus +[21:08:00] GUYS! +[21:08:20] -*- jmbsvicetto nominates scarabeus as well - just to be consistent +[21:08:22] ok i nominate reavertm +[21:08:23] lol +[21:08:25] --> dilfridge (~quassel@gentoo/developer/dilfridge) has joined #gentoo-meetings +[21:08:36] i also nominate dilfridge +[21:08:45] because i like his hair style +[21:08:48] scarabeus: I guess we won't have a vote without a second candidate, so yes +[21:09:26] grr sorry having slight dsl problems +[21:09:27] -*- alexxy also nominates scarabeus and tampakrap =D +[21:09:30] grr sorry having slight dsl problems +[21:09:37] err +[21:09:37] ok, so we have nominations for: tampakrap, bonsaikitten, scarabeus, jmbsvicetto, reavertm and dilfridge. Anyone else? +[21:09:47] ah +[21:10:01] here +[21:10:09] tampakrap and bonsaikitten accepted. I refused. Others? +[21:10:30] i refuse +[21:10:32] -*- reavertm nominates alexxy for good behaviour and tree bumps +[21:10:44] no!!!!!! +[21:11:02] so, reavertm and dilfridge, do you accept your nominations? +[21:11:10] alexxy: I'm counting you as refusing +[21:11:19] yep =) +[21:11:23] jmbsvicetto: you write summary>? +[21:11:28] no, i will +[21:11:29] scarabeus: NO!! :P +[21:11:34] ook i am +[21:11:40] scarabeus: just helping to summarize points +[21:11:48] I'm not gonna refuse, but I'm not the best choice... I may drop offline for a while at any point because of real-life workload +[21:11:50] I WILL WRITE THE SUMMARY +[21:11:53] well, I can accept but be advised I'm not active any more as I used to +[21:12:04] scarabeus: who's going to protect the children now that you won't be lead? +[21:12:19] so it seem we have 4 candidates: tampakrap, bonsaikitten, reavertm and dilfridge +[21:12:30] seems* +[21:12:46] so, how do we vote? +[21:12:53] Should we open an "election window" so everyone in the team can cast their vote? +[21:13:02] nopes +[21:13:03] here +[21:13:03] huh? +[21:13:04] now +[21:13:06] attending +[21:13:06] one way would be to vote to the kde alias or gentoo-desktop ml +[21:13:11] jmbsvicetto: dilfridge said no +[21:13:28] he said he is NOT going to refuse +[21:13:29] scarabeus: I read it as "I'm not going to refuse" +[21:13:39] jmbsvicetto: correct +[21:13:48] ah +[21:13:51] so 4 candidates +[21:13:52] ok, how do we vote? only one choice? +[21:14:10] poll? +[21:14:10] yeah one choice +[21:14:16] one choice +[21:14:31] Do you want to vote by email / irc / votify? Do we want a public or private election? +[21:14:39] oh dear +[21:14:43] just asking +[21:14:55] I can vote now, by irc +[21:14:57] I don't have any preference +[21:15:08] now over irc one person +[21:15:08] Do we have enough KDE team members around to do it? +[21:15:11] kthx +[21:15:13] yes we do +[21:15:14] no preference here either +[21:15:17] good +[21:15:19] by irc =) +[21:15:21] i watch this stuff +[21:15:29] !herd kde +[21:15:30] (kde) abcd, alexxy, dilfridge, jmbsvicetto, patrick, reavertm, scarabeus, spatz, tampakrap +[21:15:50] please acknowledge your presence :) +[21:15:51] to get elected someone needs to get 5 votes - at least on the first vote count. Agreed? +[21:15:52] abcd and spatz seem to be missing +[21:15:54] abcd and spatz missing or not active +[21:16:15] abcd present but inactive +[21:16:32] 5 out of 9 - to get > 50% +[21:16:38] ok +[21:16:56] so, shall we vote? +[21:17:28] -*- reavertm present and active +[21:17:34] present +[21:17:38] present +[21:17:42] present +[21:17:44] present +[21:17:47] present +[21:18:02] that's at least 7 as far as I can tell +[21:18:19] present +[21:18:37] means we can do irc vote now +[21:18:47] public vote acceptable? I am indifferent +[21:18:55] just go public +[21:18:58] why to hide +[21:19:03] (come on as retiring one ic +[21:19:04] yes, any opposition? +[21:19:09] an just decide that) +[21:19:11] not from me +[21:19:14] no opposition here +[21:19:17] public +[21:19:24] go ahead public +[21:19:30] so, votes? +[21:19:41] vote: tampakrap +[21:19:42] -*- dilfridge votes tampakrap +[21:19:54] -*- bonsaikitten votes for tampakrap +[21:20:00] -*- tampakrap votes reavertm +[21:20:05] -*- alexxy votes for tampakrap +[21:20:06] -*- reavertm votes tampakrap +[21:20:31] tampakrap: +[21:20:39] -*- jmbsvicetto votes tampakrap +[21:20:43] that's 6 for tampakrap already, which is a simple majority +[21:20:46] I guess that counts as a majority +[21:20:56] tampakrap: Congratulations ;) +[21:20:58] yep +[21:21:03] thank you ladies +[21:21:03] congrats +[21:21:04] I like efficiency :) +[21:21:10] i'm going to dissapoint you for sure +[21:21:24] that's why we voted you ;) +[21:22:01] =D +[21:22:06] which means 9% of the agenda is DONE! Yeah! +[21:22:26] ok i'm going to chair the rest of the meeting +[21:22:35] 1) status regarding hal +[21:22:55] it is dead, not needed in 4.6, i'm going to convert samuli's forum post to guidexml +[21:22:59] anything else to say here? +[21:23:01] anyone still running hal here? +[21:23:01] well, when 4.5 is ouot, we won't need it anymore +[21:23:18] (and 4.4) +[21:23:38] ok +[21:23:41] anything else about it? +[21:23:49] I'd say wait for 4.6.1 and then remove 4.5 from tree, then HAL can die +[21:24:02] discussion about the future of 4.6 is later in the list +[21:24:10] ah, 4.4... +[21:24:14] ook we need to keep it until 5 +[21:24:17] 4.6 is stable +[21:24:22] typo with the 5 +[21:24:36] http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/maintainers/meetings/meeting-2011-02-10;h=3d4869e4043c080750c68b2c7da66cfaf10f3c0d;hb=298fad1df1839ec400a346a9c60036a96e0b440e +[21:24:40] topics here btw +[21:24:51] ok we're done with hal, next +[21:24:56] 5 2) should we try to form a "stable kde devs" team? meaning just call for volunteers on the dev ml? +[21:25:01] 2) should we try to form a "stable kde devs" team? meaning just call for volunteers on the dev ml? +[21:25:07] that was my idea +[21:25:17] please elaborate +[21:25:18] basically many of us are running 9999 +[21:25:46] and right now the distance between 9999 and stable is so huge that it can be difficult to test stable bugfixes +[21:25:52] my opinion is we don't need it, we usually stabilize fast, with the great exception of 4.5 +[21:26:03] by '9999' you mean 4.x.9999 as well? +[21:26:07] the problem may go away on its own with 4.6 +[21:26:08] we dont sta le +[21:26:12] misc apps are slow +[21:26:15] seriously +[21:26:24] some of them were stabilised by me with the last cleanup +[21:26:29] who cares? i will stabilize them on user request +[21:26:31] other than that nobody bothers opening bugs +[21:26:38] and by me and dilfridge as well +[21:26:48] we may forget about this point if we get a 4.6 stable soonish +[21:27:07] and if we drop older releases +[21:27:13] again, discussion about 4.6 future is later in the list, so let's skip this point for now +[21:27:20] dilfridge: agreed? +[21:27:23] but as long as we want to keep 4.4 still around, we should ask for some "stable testers" on the dev-ml +[21:27:24] yes +[21:27:27] agreed +[21:27:29] anything else here? +[21:27:34] no +[21:27:43] noone? +[21:27:48] ok, next: +[21:27:52] 3) kde-git/eclasses migration and status, move kdepim 4.6 beta in tree masked +[21:28:13] reavertm / Sput / scarabeus (i don't know who else) did some cleanings in the eclass +[21:28:13] ok i cleaned a mess we had in eclass +[21:28:17] now reaver is focused on it +[21:28:21] how is its status? can it be merged? ETA? +[21:28:30] sput is main person responsible for packages from my PoV +[21:28:34] aka he tests +[21:28:42] (but he is on date now) +[21:28:46] eta is upstream is insane +[21:28:52] cause it will take quite some time +[21:28:52] ? +[21:28:54] ok +[21:29:03] we need git-2 in tree first (what else do you mean by 'merge'?) +[21:29:15] yeah git-2 is progressed as we speak +[21:29:22] migrate, not merge +[21:29:23] i need to talk with ulm a bout some variale names +[21:29:48] ok, so 1) git-2 in tree 2) review/test 3) move to tree +[21:29:53] can we have an ETA? +[21:30:14] and anything specific we should test? +[21:30:20] git2 14 days +[21:30:29] i want to hear if all features are implemented +[21:30:34] and if we lack something +[21:30:40] (i want to keep that mess minimal) +[21:30:48] i might to remove 2 cloning apoproaches and keep only one +[21:30:52] (the submodules one( +[21:31:10] kde4-* seems to work - I don't think anyone will ever implement KMEXTRA-aware kde4-meta_src_unpack for git though +[21:31:53] has anyone tried koffice? +[21:31:58] yes +[21:32:02] it works +[21:32:05] dilfridge: wfm +[21:32:19] but with that calligra /&/&%(/& its prbably getting more complicated again +[21:32:21] i could complain about integration of tha tone shit +[21:32:22] ok good +[21:32:26] but go ahead +[21:32:37] we can get koffice out +[21:32:47] sure, do it +[21:32:49] actually I think that it should go out +[21:32:56] once I have the time... +[21:33:01] yes, i agree, i can help +[21:33:07] ok cool +[21:33:08] do you want to move the code to ebuilds directly? +[21:33:29] I have not made any plans at all +[21:33:32] so far +[21:33:49] but I think the only real issue is unpack/prepare +[21:33:50] anyway, moving the koffice bits out of the eclass is very wise thing to do +[21:33:55] reavertm: idea on how to do it? +[21:34:09] i already removed most bits sunshines +[21:34:20] of koffice? +[21:34:20] good +[21:34:26] yeah +[21:34:30] i didn't notice +[21:34:34] ok cool +[21:34:36] even better! +[21:34:51] so, ETA? scarabeus? +[21:34:53] a month? +[21:34:55] less? +[21:35:19] there's still some koffice stuff in kde4-meta though +[21:35:39] i need to work on git-2 first +[21:35:43] so not sooner than month +[21:35:58] ok, if you can compile a list of todo for that we could help +[21:36:03] I think deadlines would be unreliable anyway +[21:36:12] for the record mostly +[21:36:17] no deadlines just planning +[21:36:36] anyway, i think we are done here +[21:36:46] 4) Shall we drop useflags kdeenablefinal and/or kdeprefix to simplify code? +[21:36:56] shall we vote on this? +[21:37:00] no +[21:37:05] i really object +[21:37:09] the impementors should tell us +[21:37:14] kdeprefix - jorge +[21:37:18] we have about 10 bugs about kdeenablefinal, no big deal +[21:37:19] kdeenable - reaver +[21:37:25] my opinion: keep kdeenablefinal (it's upstream stuff), drop kdeprefix (it fills up our eclasses with cruft) +[21:37:25] and i want kdeprefix +[21:37:27] please keep kdeenablefinal at least (it's cheap) +[21:37:40] kdeenable final should stay i agree +[21:37:45] the guy that filed the bugs for kdeenablefinal provided patches +[21:37:46] but kdeprefix i dont see anyone using it +[21:38:00] i plan to do it actually +[21:38:21] i want to switch back to live as my main desktop +[21:38:31] and i don't want a chroot as i did in the past +[21:38:34] some packages cannot be kdeprefixed (bindings for instance) +[21:38:41] hmm +[21:38:42] i plan to work on them +[21:38:50] no, they can't +[21:38:51] why we still need kdeprefix? +[21:39:00] it will confuse end users +[21:39:05] it's a feature, we don't "need" it +[21:39:13] reavertm: why they can't? +[21:39:18] it makes our eclasses way too complicated +[21:39:36] -*- reavertm doesn't think kdeprefix is complicated +[21:39:52] why can't they be prefixed? i haven't looked at the code yet +[21:39:52] it definitely isn't like it used to be +[21:39:57] i suppose you did +[21:39:59] it is qutie clear +[21:40:07] but qutie few apps are not kdeprefix aware +[21:40:09] (misc one) +[21:40:19] and it has quite few bugs noone attendet to +[21:40:25] *ded +[21:40:52] ok then, give me time till the next meeting to test it and i'll report back +[21:40:55] tampakrap: actually bindings may work but sip files needs to be slotted +[21:41:08] i plan to work on the misc apps and python packages +[21:41:25] judge 1st it's worth your time +[21:41:31] -*- reavertm thinks it isn't +[21:41:37] no, having to maintain a chroot is +[21:42:12] well i use live on my laptop +[21:42:22] and its only DE here +[21:42:37] anyway, do we all agree to keep kdeenablefinal and kdeprefix and bring the topic back again? +[21:42:38] -*- dilfridge thinks a laptop can crash in more than one way anyway :D +[21:43:05] mumble... ok +[21:43:44] i see no objections, next: +[21:43:51] 5) Dropping of semantic-desktop useflag with guide update (mostly even kdebase needs it on now) +[21:44:06] i fixed it for plasma-workspace +[21:44:09] i would reat +[21:44:13] i had to write an upstream patch +[21:44:16] rather preffer it to be still availible +[21:44:25] virtuoso and semantic stuff is not something most might want +[21:44:46] our ebuilds are broken, upstream still has support for the useflag +[21:45:11] plasma-workspace along with libplasmaclock causes trouble with kdepimlibs due to our splitting +[21:45:16] i'll dig in more +[21:45:16] tampakrap: your fix suck +[21:45:17] does anyone know how this will develop for 4.7? +[21:45:32] tampakrap: i dont want libkdepim as harddep for it +[21:45:38] it doesn't, it was approved by aseigo +[21:45:44] what harddep? +[21:45:49] what are you talking about? +[21:45:56] wait wait, libkepim != kdepimlibs +[21:46:03] and what happens when kdepim-4.6 goes in tree? +[21:46:50] https://projects.kde.org/projects/kde/kdebase/kde-workspace/repository/revisions/5701ee97f896bf25de5dfbcc2699695794f25b34 +[21:47:06] this is the patch, where do you see a harddep? +[21:48:11] anyway, our affected ebuilds are plasma-workspace/libplasmaclock and kdeplasma-addons +[21:48:19] ah i am talking about plasma workspace +[21:48:21] :) +[21:48:22] i saw the code, the problem is in our side +[21:48:27] first of all, libkdepim is from KDEPIM, and it's not kdepimlibs +[21:48:33] the patch is in plasma-workspace +[21:48:59] anything else needs kdepimlibs? +[21:49:11] nothing needs it, it is still optional +[21:49:30] why do we have this agenda item then? :P +[21:50:00] --> dilfridge_ (~quassel@gentoo/developer/dilfridge) has joined #gentoo-meetings +[21:50:01] i have no idea, i am just pointing out that the item is invalid, the problem is in our side +[21:50:06] <-- dilfridge (~quassel@gentoo/developer/dilfridge) has quit (Ping timeout: 240 seconds) +[21:50:16] ok in that case ebuilds need fixing +[21:50:22] before we can stable 4.6 +[21:50:26] yes, we have open bugs and i am working on it +[21:50:49] 6) Making +consolekit and +policikit or removing the useflags as whole (non working stuff run-as is annoying) +[21:51:00] no idea about this one +[21:51:12] thats from me +[21:51:26] if those two are not around most of the user perms stuff is not working +[21:51:31] so users might complain a lot +[21:51:31] I remember from some upstream bug report that one of them is now required +[21:51:41] so i would go and just make it required +[21:51:42] really +[21:51:51] if not it is just broken (not supported anymore) +[21:52:02] <-> dilfridge_ is now known as dilfridge +[21:52:04] <-> dilfridge is now known as dilfridge_ +[21:52:06] <-> dilfridge_ is now known as dilfridge +[21:52:37] is it too much load if we make them harddeps? +[21:52:42] nope +[21:52:45] like 5 more deps +[21:52:48] sure then +[21:52:49] people will whine, as usual +[21:53:04] it kind of forces a more modern system, but makes debugging for us easier +[21:53:04] for sure +[21:53:11] what about macos? +[21:53:19] do they have different KAuth backend? +[21:53:37] http://techbase.kde.org/Development/Tutorials/KAuth/KAuth_Basics +[21:53:47] -*- dilfridge thinks the weird guys should be handled later +[21:54:19] i don't see anything arch specific there +[21:54:33] no, because it may determine we can't harddep them +[21:54:43] do we have them enabled by default? +[21:54:48] if not, can we do this instead? +[21:55:40] people should know that they need some things as deps to have a DE like KDE run normally +[21:55:47] tampakrap: https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/show/kdecore/auth/backends +[21:56:21] yeah +[21:56:38] so, should we ask upstream? +[21:56:47] i could mail those guys listed in the changelog +[21:56:59] no need +[21:57:06] or we could enable it by default for everything but mac +[21:57:08] I'd add IUSE defaults +[21:57:20] reavertm: please not +[21:57:30] people WILL try to switch it off +[21:57:42] it does not help +[21:57:45] yes +[21:57:55] it doesn, then we can say - screw you, you disabled it +[21:58:08] yeah, elog +[21:58:14] reavertm: it's a use flag so people think its optional +[21:58:16] endofstory +[21:58:24] and we have wasted time trying to find the problem and added additional cruft to the eclass +[21:58:31] and elog gives me the right to invalid their bug +[21:58:38] it's also enabled by default which means there's some thinking behind it +[21:59:12] we may be in the land of infinite options but not in the land of infinite support manpower +[21:59:37] i agree with IUSE defaults ftr +[21:59:50] maybe use.force :P +[22:00:02] god just drop it and let the 4 people complain +[22:00:05] reavertm: that's ok I guess +[22:00:06] (someone can use.mask if one wants) +[22:00:09] come on we threw mysql their way +[22:00:11] and nobody whine +[22:00:12] d +[22:00:15] nowdays +[22:00:16] :D +[22:00:19] drop it! +[22:00:51] reavertm: your call :P +[22:01:02] i don't care much +[22:01:40] -*- reavertm thinks the one who is going to do the job, should decide +[22:02:37] I'm prefer not to drop use flags though +[22:02:39] reavertm: ok your call +[22:02:52] reavertm: tampakrap is the one who decide in the end nowdays :) +[22:03:02] it's not really a harddep if one wants just kdelibs + misc stuff +[22:03:13] yeah i don't like dropping the useflag +[22:04:04] does use.force have precedence over use.mask? +[22:05:02] (I mean, is it possible for etc/portage/*/use.mask to disable use.forced flag? +[22:05:17] no idea +[22:05:55] anyway, it is taking too long, let's decide in the mailing list instead +[22:06:02] -*- reavertm votes for use.mask +[22:06:08] use.force* +[22:06:11] i'll send the mail, we can get some feedback from users as well +[22:06:21] ok +[22:06:30] use.force is easily done and reversible +[22:07:20] and should be hard enough for users to switch off +[22:07:24] dilfridge: agree to continue in the ml? +[22:07:29] ok +[22:07:36] thank you +[22:07:39] 7) AT/overlay/bugzie access policy +[22:07:43] this is mine +[22:08:07] scarabeus: i need a clear list on who has access to the overlay, who has editbugs privs and who is a KDE AT +[22:08:11] and compile a page +[22:08:38] and i need to define a rule for ATs, and get all those priviledges together +[22:08:40] tampakrap: ahem you have access to the list +[22:08:41] do you agree? +[22:08:46] i dont have it +[22:08:53] and i upgraded everyone to at already +[22:08:56] lol, i know, i'm just saying +[22:08:58] who can potentially have elevated rights in bugzie? +[22:09:04] only real devs? +[22:09:11] even users +[22:09:19] which we are watching +[22:09:31] "arch testers", "overlay committers" +[22:09:32] the one who has finished ebuild quiz, has gone through an AT/HT review session and someone is watching him +[22:10:14] so, define two groups of people in addition to ATs? +[22:10:28] hmm? +[22:10:39] what two groups? +[22:12:14] ATs, overlay commiters +[22:12:20] is that what you just said? +[22:13:06] nono I was just trying to make a point to papillon81 +[22:13:44] ah k +[22:13:53] scarabeus: i need your idea on what to do here +[22:14:03] in effect, the two groups would be "overlay committers" and "bugedit", but I'm not sure if it would make sense to make just one group for that +[22:14:08] i have no idea how to clean up this mess +[22:14:11] simplifies things +[22:14:25] eg Sput refuses to become an AT, doesn't want ot finish ebuild quiz +[22:14:40] just have two groups, access ; access + bugedit which == AT +[22:14:44] we could have overlay commiters and full ATs but i don't like it +[22:15:48] anyway, i'll compile the list first and bring the topic up again +[22:16:04] who is going to be AT lead now? or should we drop the title? +[22:16:15] i find it a bit useless, like every lead position :P +[22:16:45] drop it +[22:17:16] no volunteers :P +[22:17:23] next: +[22:17:25] 8) livedvd issues +[22:17:28] who knows, AT lead does more recruiting work imho +[22:17:31] likewhoa: anything to say here? +[22:17:47] reavertm: do you want the position then? +[22:17:50] nothing really just a few request made by users +[22:18:11] tampakrap: hell no +[22:18:27] thought so :) +[22:18:33] i added an icon to the kde start menu and some users wanted to know if kde can make use of it, also some users wanted to know if there were any gentoo centric kde themes +[22:18:37] likewhoa: shoot now that we are all here :) +[22:18:57] -*- dilfridge runs +[22:19:06] -*- likewhoa pulls dilfridge back with some cookies +[22:19:22] well, tbh i need someone to do some graphics work if we are going to implement branding +[22:19:33] and i couldn't find anyone the last two years +[22:19:49] tampakrap: poke a3li +[22:19:59] he hates kde +[22:20:11] i can also do graphics but won't be available for that until mid march +[22:20:30] tampakrap: i made the wallpapers for the livedvd, not the one on the desktop but the others ones +[22:20:37] i think jmbsvicetto used one for FOSDEM +[22:21:25] well, if you are willing to help here i'm all in add it to the tree +[22:21:29] but a kde gentoo centric theme would be ideal and can be part of the branding USE flag +[22:21:35] sure +[22:21:46] let's do some work first and bring the topic back again +[22:21:56] ok +[22:22:08] anything else? +[22:22:13] no +[22:22:19] cool thanks +[22:22:28] please everyone test the dvd :) +[22:22:31] in #gentoo-ten +[22:22:44] use zsync so you don't waste bandwidth on new releases +[22:22:51] net-misc/zsync that is +[22:23:03] next: +[22:23:06] 9) documentation status +[22:23:16] pretty please everyone read the documentation +[22:23:36] help me to complete the tips and troubleshoot with 4.6 specific parts +[22:24:09] i wanted to say something more about this one but i forgot it +[22:24:19] anyway, i'll merge the last two topics: +[22:24:26] 10) 4.6 (and misc apps with 4.6) status +[22:24:33] 11) early discussion about 4.6 stabilization +[22:25:03] i'm listening, i vote early for 4.6.1 stabilization :) +[22:25:16] stabilize 4.6 as quick as possible. 4.6.1 +[22:25:41] i need more feedback about misc apps though +[22:25:57] stabilize early. 4.6.1 should be fine. +[22:25:57] for example, knetworkmanager is broken and i lack the hardware to test currently +[22:25:58] knetworkmanager is waiting for ubuntu +[22:26:12] sorry? +[22:26:27] 4.6... doesn't feel worse than 4.5 +[22:26:34] i talked with wstephenson about it yesterday +[22:26:39] strange, I know +[22:26:40] do we want to wait for kdepim? if we say "stabilize fast" that means no +[22:26:50] i don't get you at all, sorry +[22:26:56] it is waiting for ubuntu to do what? +[22:27:11] tarball release /me thinks +[22:27:38] well, let's wait for kdepim to get a proper release first :) +[22:28:14] kubuntu are 'a bit worried' that it will be before KNM is ported to 0.9 +[22:28:49] tampakrap: what exactly is broken in you opinion? +[22:28:59] i have no idea, i saw a bug report +[22:29:07] but my laptop is off now and i can't test +[22:29:12] something about kwallet i think +[22:29:25] i would like more to know though about this +[22:29:35] well. i can look into it. also there are some nice patches from the pardus guys +[22:29:36] eg dilfridge: how is digikam/koffice in 4.6? +[22:29:42] fine +[22:29:56] reavertm: printing? +[22:29:59] any progress? +[22:30:02] 2.2.2 (stable) is broken but 2.3.1 is good +[22:30:36] printing.. some people report it works +[22:31:02] since when is kde supposed to do printing? =) +[22:31:09] since 4.4 +[22:31:15] "supposed" +[22:31:27] I thought that feature was disabled with 4.0 ... +[22:31:40] I bump scp usually on time, scp-kde - I'd prefer it to be still in ~arch +[22:32:00] the feature was not ported to kde4 at all, you're right +[22:32:55] anyway, we can discuss it next month after 4.6.1 gets a release +[22:33:08] i remembered what i wanted to say about documentation +[22:33:10] http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=tree;f=Documentation;h=d7e234375abd5fc61c4d7dae47adaf57d9efcac1;hb=HEAD +[22:33:12] nothing to discuss here, printing will not go stable +[22:33:36] i'm going to port them to guidexml (CODE, README etc) or merge them with the guide +[22:33:47] good idea +[22:34:00] i'll need feedback to the documentation though (pretty please) +[22:34:15] i think we are done +[22:34:21] *) open floor +[22:34:32] did anyone of you hear from the digikam guys? +[22:34:45] dilfridge: i am talking with will (suse) +[22:34:54] to shutup him abvout the opensuse argument +[22:34:56] so wait a bit +[22:34:58] ok... what's the general feeling there +[22:35:00] ok +[22:35:01] cross distro coord takes lot time +[22:35:03] what argument? +[22:35:25] so opensuse doesn't mind slotting and bundled libs? +[22:35:27] tampakrap: "opensuse likes the libs bundled" +[22:35:35] yeah good idea +[22:35:46] https://bugs.kde.org/show_bug.cgi?id=265328#c6 +[22:35:57] plus debian and others already agreed not to ship digikam2 +[22:36:05] if the issue is not resolved +[22:36:09] scarabeus: please bring svuorela to the table +[22:36:19] reavertm: he? +[22:36:21] ah +[22:36:32] debian guy +[22:36:43] we met him in fosdem +[22:36:49] scarabeus: remember? +[22:36:53] yep +[22:37:01] that s why i said ah +[22:37:07] anyway will do so +[22:37:07] will anyone join me in desktop summit this year? :) +[22:37:14] aug 6th berlin +[22:37:15] where it is? +[22:37:21] http://www.desktopsummit.org/ +[22:37:29] likely not me, other plans... +[22:37:42] if i make it (99% i will) i'll apply for a gentoo talk +[22:37:53] last year we were invited to do the talk +[22:37:59] oh, Berlin. that's good +[22:38:04] berlin sounds good +[22:38:15] but i would need to couchsurf somewhere :) +[22:38:27] reavertm: how about you? +[22:38:39] very unlikely +[22:39:18] hmm, August... who knows.. +[22:40:05] ok ladies, i think that's all +[22:40:47] thanks \ No newline at end of file diff --git a/meeting-logs/20110331.txt b/meeting-logs/20110331.txt new file mode 100644 index 0000000..84ecd70 --- /dev/null +++ b/meeting-logs/20110331.txt @@ -0,0 +1,370 @@ +[20:07:42] !herd kde +[20:07:42] (kde) abcd, alexxy, dilfridge, jmbsvicetto, patrick, reavertm, scarabeus, spatz, tampakrap +[20:07:43] -*- alexxy here +[20:07:47] roll call please +[20:07:49] -*- dilfridge here +[20:07:57] here +[20:08:00] -*- scarabeus blurps +[20:08:14] dilfridge: wanna chair? +[20:08:17] for change +[20:08:21] uh oh +[20:08:36] err ok +[20:09:01] hehe the topic still links to last meeting +[20:09:16] so... +[20:09:26] let's look at the agenda. +[20:09:42] 1) kde-git/eclasses migration and status +[20:09:58] since I dont do live, what's the status? +[20:10:23] scarabeus: ^^ git eclass status? +[20:10:47] -*- ABCD can't stay too long +[20:10:48] i got nice hint from exherbo guys and currently am attempting it to make bare checkouts even with submodules +[20:10:57] so if i manage to do that it would be epic +[20:11:17] oook, I remember the discussion on the ml +[20:11:20] but i didnt have time to focus on it lately +[20:11:22] can i get an option to use non-bare checkouts instead? +[20:11:25] as i blaged +[20:11:42] it is easy to override those commands as-is already +[20:12:07] i guess the more interesting question is does it still work then +[20:12:34] -*- dilfridge can symlink /bin/echo to /usr/bin/portage +[20:12:55] but anyway +[20:13:33] the hard question: scarabeus: what's your guess how long this will take? very roughly? +[20:13:52] few days when i work on it so i can test everything +[20:14:18] afaik kde eclasses don't need anything, we are only waiting for git-2 to hit tree first +[20:14:26] correct me if i'm wrong +[20:14:54] if it is so it is quite easy to make them git.eclass dependant +[20:15:17] since there are no live ebuilds in main tree it does not affect anything by default +[20:15:18] meaning they would also work with current git.eclass? +[20:15:32] ah ok +[20:15:51] yeah, i'll prefer those eclasses to hit tree before 4.6.2 +[20:16:07] so we can get proper testing from the stable candidate +[20:16:07] that could be pretty soon (today is official tagging day) +[20:16:26] yeah, this week +[20:17:11] do you want to selectively patch the main tree eclass or just copy everything from overlay (better)? +[20:17:14] can you paste us the link of the topics please? +[20:17:38] http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/maintainers/meetings/meeting-2011-03-31;hb=HEAD +[20:17:48] i'd like a quick review first, a patch in the alias or in -desktop would be preffered +[20:18:03] ok +[20:18:22] I'm asking because we "collect differences" between tree and overlay +[20:18:46] i would like to hear from reavertm before merging them +[20:18:47] at some point it would make sense to sort this out +[20:18:50] true +[20:18:54] we could ask for comments on -dev as is +[20:19:01] i don't know if he had any todo for the eclasses we are missing +[20:19:07] or that +[20:19:09] at least you others could work on the stuff people point out +[20:20:01] so, summarizing: we should do a review of the current overlay eclasses... +[20:20:08] yup +[20:20:10] * figure out what actually depends on git-2 +[20:20:15] why +[20:20:18] that does not matter +[20:20:26] i can move it to git.eclass in 20 secs +[20:20:32] git-2 is not showstopper +[20:20:35] ok +[20:20:40] even better +[20:21:20] * collect a todo list (or make reavertm send us his) +[20:21:37] * and review the current differences between tree and overlay +[20:21:53] any volunteers? :D +[20:22:28] i'm not the eclass expert +[20:22:39] anyway +[20:22:48] back to teh agenda +[20:23:01] 2) move kdepim 4.6 beta in tree masked? +[20:23:07] opinions? +[20:23:13] no +[20:23:18] 1) it is outdated +[20:23:24] true +[20:23:24] 2) it depends on updating eclasses first +[20:23:27] 2) there is no eclass support for it yet :P +[20:23:30] true +[20:23:39] but anyway, it is too outdated +[20:23:49] anyone in favour? +[20:24:07] and upstream kdepim will create new kdepim snapshots when a core kde developer asks to +[20:24:13] huge mess +[20:24:22] wtf +[20:24:27] they should release that shitz :D +[20:24:28] i could create our own snapshots, but i don't care enough to be honest +[20:24:34] I guess that answers the question +[20:24:36] most people are getting annoyed :) +[20:24:47] any news about an official release (schedule)? +[20:25:14] no +[20:25:21] :( +[20:25:26] tampakrap: is there any kdepim version that can work with 4.5.5, 4.6* ? +[20:25:28] kde* +[20:25:28] they said about an rc1 but apparently it didn't make it +[20:25:35] yes, 4.4.10 +[20:26:12] tampakrap: so we can use kdepim-4.4.10 with kde-4.5.5/4.6 to move forward? +[20:26:32] seems so +[20:26:40] and sorry for anticipating the next point +[20:26:42] if you are talking about a stable candidate, yes, 4.4.10 is fine +[20:26:55] yes +[20:27:20] ok... following the logical order of things instead of the numerical one... +[20:27:32] 5) 4.6 status / stabilization / important bugs +[20:27:48] apart from the blockers list on the tracker, no idea +[20:27:53] major is that akonadi integration in basic pkgs +[20:28:01] and i guess that tracker catched everything +[20:28:05] we have 5 or 6 major blockers, i am aware of all of them +[20:28:13] what akonadi integration? +[20:28:28] given the current status with upstream about 4.6, anyone sees any reason to delay getting 4.5.5 marked stable instead of keep waiting for a possible 4.6 stable candidate? +[20:28:30] the -semantic-desktop failure bug? +[20:28:33] yep +[20:28:57] 4.5.5 is completely broken +[20:29:23] general question: how many of you get akonadi errors on login? +[20:29:40] i don't +[20:29:49] and i use kdepim and kdepimlibs master +[20:30:03] tbh, I never checked +[20:30:33] I always get and have not been able to solve that... maybe I should start collecting info... +[20:30:37] ok +[20:30:44] I use what I was forced to use with 4.6.1 (having to enable semantic-desktp) +[20:30:56] let's have a quick look at the blockers +[20:31:19] three of them are about -semantic-desktop and -kdepimlibs support +[20:31:28] one is about kdepim 4.4.10 translations +[20:31:34] i don't remember the others +[20:31:42] Bug 353048 +[20:31:44] dilfridge: https://bugs.gentoo.org/353048 "kdebase/kwin-4.6 USE=-opengl does not compile"; Gentoo Linux, KDE; NEW; sefi:kde +[20:31:51] this is fixed upstream +[20:32:05] and the fix may be in 4.6.2 if it is backported in 4.6 branch +[20:32:34] Bug 353726 +[20:32:35] dilfridge: https://bugs.gentoo.org/353726 "kde-base/plasma-workspace-4.6.0 should not depend on kdepimlibs"; Gentoo Linux, KDE; REOP; ikandros:kde +[20:32:41] yeah i mentioned that +[20:32:56] i'm on it +[20:33:16] Bug 353730 +[20:33:19] dilfridge: https://bugs.gentoo.org/353730 "kdeplasma-addons-4.6.0 USE=-semantic-desktop fails to build without akonadi/semantic-desktop"; Gentoo Linux, KDE; REOP; KeithBHarrison:kde +[20:33:23] this is probably related +[20:33:25] and that +[20:33:41] Bug 357545 +[20:33:43] dilfridge: https://bugs.gentoo.org/357545 "kde-l10n-4.6.1 wants to overwrite kde-misc/konq-plugins-4.4.0-r1 files"; Gentoo Linux, KDE; NEW; panard:kde +[20:33:53] no idea, scarabeus^^ +[20:33:56] that should HOPEFULLY be fixed with 4.6.2 +[20:34:02] as it is pretty trivial +[20:34:11] tampakrap: i told you that they have to use konq-plugins-4.6.1 +[20:34:19] tampakrap: if they do so no clashes +[20:34:28] ok, so we should adjust deps +[20:34:33] dilfridge: plz2fix +[20:34:34] they got the release of 4.6.1 completely screwed up there +[20:34:50] later +[20:35:03] Bug 357959 +[20:35:04] no blocker, remove it from the list please +[20:35:05] https://bugs.gentoo.org/357959 "kde-base/nepomuk-4.6.1: nepomuk service stub crashes after update"; Gentoo Linux, KDE; NEW; dilfridge:kde +[20:35:09] or lower severity +[20:35:30] done +[20:35:41] your nepomuk bug, can't reproduce +[20:35:42] that one is pretty annoying but an upstream problem +[20:35:46] a user reported something +[20:36:09] yes but I dont think it is gentoo-only +[20:36:18] hey, upstream says it is fixed +[20:36:32] yes 462 +[20:36:34] good +[20:37:40] Bug 359979 +[20:37:41] dilfridge: https://bugs.gentoo.org/359979 "media-libs/xine-lib crash with MKV WebM"; Gentoo Linux, Applications; ASSI; rezbit.hex:media-video +[20:37:44] a bit obscure +[20:37:47] huh? +[20:37:52] vlc is default +[20:37:55] kde upstream says it's a xine-lib bug +[20:38:10] probably this should not be a blocker either +[20:38:15] oh guys +[20:38:16] I think we should close all phonon-xine bugs as CANTFIX +[20:38:23] i would make phonon-gstreamer default +[20:38:26] not the vlc +[20:38:28] blocker removed +[20:38:35] i find bit stupind to demand videoplayer +[20:38:36] for that +[20:38:41] not phonon-gstreamer, please +[20:38:46] -*- dilfridge bangs on the table... open floor is later :) +[20:39:03] ok back to the actuall agenda +[20:39:05] dilfridge: open floor is for people outside the team ;) +[20:39:17] jmbsvicetto: so you rather pull in the vlc? +[20:39:18] :) +[20:39:29] xine does not work +[20:39:34] scarabeus: I think that's what upstream expects us to use as default +[20:39:40] so do we agree we should consider 462 as "potential stable candidate"? +[20:39:43] (I'm not sure though) +[20:39:45] scarabeus: if you consider webkit part of the environment, then you'll need a video player ;) +[20:39:47] i didnt see it yet +[20:40:02] jmbsvicetto: gstreamer can manage over phonon +[20:40:07] jmbsvicetto: and i use mplayer +[20:40:11] I don't think we should see 462 as a stable candidate +[20:40:19] jmbsvicetto: well we have to +[20:40:22] one magic word +[20:40:23] HAL +[20:40:29] why not? +[20:40:30] :| +[20:40:33] +1 +[20:40:39] that releases will be broken forewer +[20:40:39] hal should be dropped +[20:40:45] just take look on what upstream does :) +[20:40:52] because I don't believe they'll be able to "not break" kdegraphics on this release +[20:40:55] so we just have to bite it and sadly release somehow +[20:40:58] +1, unless upstream breaks 4.6.2 even worse +[20:41:09] It's not about "stability" or it working, but about KDE being able to package the release +[20:41:33] well 4.6.1 works pretty well +[20:41:37] yes but I expect that the kde git migration will take another century or so +[20:41:46] alexxy: minus the semantic-desktop stuff ;) +[20:41:47] (while we dont even start...) +[20:41:53] yeah +[20:42:02] I don't expect it to *ever* be completely done -- see kde-wallpapers +[20:42:02] also we still need kdepim stuff +[20:42:06] hey, infra is busy +[20:42:38] oook +[20:42:39] tampakrap: My only issue with 4.6.2 is that I expect us to get a broken release (packaging wise). If the regressions about akonadi/pimlibs get fixed, I have no issue with it being marked stable +[20:42:40] and they again doing something with git,kde.org and projects.kde.org +[20:42:46] i said already kdepim 4.4.10 is fine along 4.6, don't make me repeat it in caps +[20:42:58] I still antecipate we may get some "angry" users, but there's little we can do about it +[20:43:15] we'll always get some angry users +[20:43:18] those are issues with the sponsors, even we have those kind of issues +[20:43:21] actualy now i see how childish i was when i look on the tiny issues with 4.5 ;P +[20:43:21] don't confuse things +[20:43:24] anyway +[20:43:32] we can talk about that again in three weeks +[20:43:35] i could've stabled some of that :) +[20:43:48] yes. +[20:43:50] nah i would give it 14 days for the stablebug if everything works +[20:44:06] we are behind schedule for that stuff for freedesktop stuff +[20:44:14] 3 weeks is 1 week after tagging, 2 weeks after release +[20:44:20] yep works +[20:44:23] well given that kde-462 will take another week or so, we can for sure have another meeting before the stablebug filing +[20:44:38] ok +[20:44:42] we are not behind if samuli is acting like a maniac about hal without proper documentation / announcements +[20:44:49] true +[20:44:53] <+willikins> New bug: https://bugs.gentoo.org/?????? Marked KDE-4.6.2 stable (URGENT) - HAL needs to die +[20:44:57] scarabeus: ^^ ? ;) +[20:45:08] DIE DIE DIE +[20:45:09] jmbsvicetto: something like that +[20:45:19] btw we can smash in solid4.6 +[20:45:19] :D +[20:45:25] and pretend everything is perfect xD +[20:45:37] so +[20:45:41] now for the optional stuff +[20:45:45] scarabeus: you mean solid-4.5? +[20:45:46] also there can be another issue +[20:45:55] because of nm-0.9 stuff +[20:45:59] nm? +[20:46:05] networkmanager +[20:46:07] what about it? +[20:46:09] jmbsvicetto: nah, hal is out since 4.6 :) so we can stable just solid :P +[20:46:11] new api +[20:46:14] totaly different +[20:46:18] but it does not matter +[20:46:23] current solid will not work with it at all +[20:46:23] since knetworkmanager is already working on it +[20:46:27] and it wont use solid at all +[20:46:43] ok +[20:46:46] i know +[20:46:52] scarabeus: right, so you want to kill solid-4.5 :P +[20:46:57] and they working on solid backend for it +[20:47:11] jmbsvicetto: 4.4 +[20:47:11] better to kill kde < 4.6 +[20:47:19] jmbsvicetto: we talk about stable :D +[20:47:38] what alexxy said +[20:48:37] so, summary: need some stable kde-4.6 in the near future, as the pressure is rising(tm) +[20:49:08] next point +[20:49:16] 3) Shall we drop useflag kdeprefix to simplify code? +[20:49:16] "The problem is that bindings are not prefixed, and a possible fix (proposed +[20:49:16] by reavertm) would be to slot sip. tampakrap said he'll work on this, and bring +[20:49:16] the topic back in next meeting." +[20:49:39] any news? +[20:49:41] can i get another month please? +[20:49:45] busy with gsoc proposal +[20:49:49] does any of us use kdeprefix? +[20:49:58] i started using it +[20:50:05] you're the boss, but does anyone actually use it? +[20:50:05] but i'm still stuck on my 4.6 +[20:50:08] hmm +[20:50:26] it's masked i don't see why you want to drop it +[20:50:33] for testing better to use VMs +[20:50:34] if we drop kdeprefix, we can simplify a *lot* of things -- including slotmoving everything to :4 +[20:50:38] like lxc or xen +[20:50:52] no it isn't better +[20:50:53] and the eclasses will be much simpler +[20:50:55] alexxy: or even just a chroot +[20:50:59] i will have to maintain to boxes then +[20:51:11] its simple +[20:51:20] share binary packages across them +[20:51:23] My feeling for a long time is that kdeprefix also needs to die +[20:51:30] it's not simple +[20:51:34] use KSM to save your memory +[20:51:36] and so on +[20:51:38] different use flags different configurations +[20:51:46] it's not a resource problem +[20:51:57] it'a a pain in the neck having to maintain an extra box +[20:52:05] wait, sorry, I mean kdeenablefinal, not kdeprefix +[20:52:08] its not too hard +[20:52:30] I liked kdeprefix, but as it needs upstream work and we can't get their collaboration, I no longer object to killing it +[20:52:30] ok, let me disagree +[20:52:45] anyway, i want that useflag but if you guys want we can go on a vote +[20:52:59] -*- alexxy running many VM's @works to test new stuff (like experimental gromacs patches and so on) +[20:53:02] -*- ABCD votes to kill it +[20:53:09] -*- alexxy also +[20:53:12] -*- dilfridge votes to kill it +[20:53:57] -*- jmbsvicetto abstains +[20:54:29] I'd say since that is less than 50% of the team we dont change anything for now. +[20:54:43] make vote over ml so everyone state the opinion +[20:55:10] for now decision postponed again +[20:55:17] next point +[20:55:26] 4) Making +consolekit and +policikit on by default or removing the useflags as whole (non working stuff run-as is annoying) +[20:55:26] "No consensus was reached, the topic will be continued in the gentoo-desktop mailing list." +[20:55:26] Mailing list query resulted in two user voices for "default on but still configurable" +[20:55:30] I have to leave now, as I have a meeting in ~1 hour that's ~55 minutes away +[20:55:38] cya +[20:55:41] cu +[20:55:44] about the flags, people want them +[20:55:59] additionally people want udev deps optional as well +[20:56:00] yes but do we want to maintain them? +[20:56:22] i still support the profile/kde and use.force solution +[20:56:33] udev deps at least have to be removed with USE=prefix +[20:56:39] tampakrap: udev and policykit optional deps needed to have kde on kernels other than linux +[20:56:58] and prefix can't do udev/polkit/consolekit +[20:57:14] I don't see a point for the kde profile, but I just use linux/amd64/10.0 +[20:57:25] *bsd/solaris/hurd cant have udev +[20:57:44] polkit may still work +[20:58:16] dilfridge: are the above sufficient to you? +[20:58:22] anyway. are there any objections to making +consolekit and +policykit on by default in the ebuilds, and forcing them in the kde profile? +[20:58:28] so if we will have udev deps unconditional we should drop prefix/*bsd and all non native linux stuff +[20:58:48] dilfridge: I don't have an issue with IUSE defaults and don't use the kde profile +[20:58:59] yeah no objections +[20:59:01] dilfridge: its good idea +[20:59:07] ok +[20:59:13] alexxy: I'd prefer to maintain prefix compatiblity, if possible +[20:59:25] then we go with that I'd say +[20:59:32] last point +[20:59:35] open floor +[20:59:53] anything else to discuss? +[20:59:56] also gentoo prefix can be used instead of kdeprefix =D +[21:00:10] well +[21:00:28] alexxy: that is actually interesting... gentoo on gentoo :))) +[21:00:28] we again have problems with arches like x86-fbsd ppc* +[21:00:45] -*- alexxy uses prefix on rhel4 cluster +[21:01:09] alexxy: ppc is still recovering from their lost boxes +[21:01:13] what problems? +[21:01:26] unkeyworded deps as usual +[21:01:30] I need to resume my discussion from council with arch teams +[21:01:42] oh +[21:01:50] yeah but xarthisius is pretty helpful and responsive +[21:01:52] that's their problem, not ours +[21:02:28] last time i masked some use flags or whole kde release on arm ppc ppc64 and x86-fbsd +[21:02:28] it's mainly about giving a friendly poke if something is really needed I think +[21:03:17] I dont know nothing about x86-fbsd +[21:03:46] i dont know anybody who is using it +[21:03:48] ok +[21:04:00] but kde has ~x86-fbsd keywords +[21:04:03] dilfridge: aballier +[21:04:29] yes but aballier afaik was only contact to a user somewhere +[21:04:45] !bug 357403 +[21:04:46] https://bugs.gentoo.org/357403 "[KDE] Please keyword kde-4.6 deps to unmask needed useflags"; Gentoo Linux, Ebuilds; NEW; alexxy:kde +[21:05:04] dilfridge: he lost his bsd boxes +[21:05:06] well i can setup x86-fbsd VM +[21:05:14] ok +[21:05:46] If I find time to reconfigure my home network I can do arm at some point +[21:05:48] i may already have one +[21:05:49] http://choqok.gnufolks.org/2011/03/choqok-is-going-to-leave-kde-for-gnome/ +[21:05:52] he would like to resume his work on bsd +[21:06:04] dilfridge: what arm board do you have? +[21:06:11] openrd +[21:06:57] so, summary: about keywords nothing really changed :] +[21:07:06] anything else? +[21:07:21] or shall we call it a day? +[21:08:14] -*- dilfridge takes this as "no, and yes" +[21:08:26] I'll post the log +[21:08:33] could one of you please make the summary? +[21:08:40] i'll handle the summary +[21:08:43] ok cool +[21:08:46] tomorrow, i'm about to pass out +[21:08:49] :) +[21:09:16] cheers and thanks for being here :D diff --git a/meeting-logs/20110602-summary.txt b/meeting-logs/20110602-summary.txt new file mode 100644 index 0000000..772a257 --- /dev/null +++ b/meeting-logs/20110602-summary.txt @@ -0,0 +1,44 @@ +rollcall +ABCD, alexxy,dilfridge,tampakrap,jmbsvicetto + +1) KDE SC 4.6.80 bump + +jmbsvicetto and alexxy did a great job so far about it, with ABCD +forward-porting the commits to the live ebuilds. It is not ready yet though, +and we'd not recommended to users yet, unless they know what they are doing. +Upstream split some of the tarballs in order to follow the repos for 4.7. We +were very lucky so far, and upstream's split was very similar to ours, apart +from kdebindings, which we'll have to re-package to follow them. + +2) Drop of kdeprefix useflag + +The kdeprefix USE flag is announced to be dropped this Monday. As a result, +we'll have to move all ebuilds to slot 4. We could move them to 0 as well in +order to drop the slotting entirely, but since most of them are already 4 it +will prevent us from doing another massive slotmove. + +3) Useflags in kde profile + +It was decided these useflags to be added to the kde profile: declarative, +dri, kipi, phonon, plasma, semantic-desktop, xcomposite, xinerama, +xscreensaver + +4) KDE SC 4.6.3 stabilization + +First of all, dilfridge deserves congratulations for taking care the +heavy job of doing the 4.6.2 stabilization, along with Qt 4.7 and a large +number of other Qt and KDE applications. Keep in mind that this was a really +hard job to do, since the previous stable version was 4.4.5. Things are now +back in order now, with 4.6.2 fully stabilized and 4.4 completely removed +(finally). 4.6.3 is the next stabilization target, to keep stable tree up to +date. + +*)Open floor + +Andreas said he is interested in doing some cups work, which we hope to affect +KDE and desktop users in general. + +We lost scarabeus, one of our top developers. Thus, +we'd like to remind anyone that we always appreciate the help of new people. +If you are one of the guys that already has access to the overlay, time to +complete your ebuild and end quiz then! diff --git a/meeting-logs/20110602.txt b/meeting-logs/20110602.txt new file mode 100644 index 0000000..19ab44d --- /dev/null +++ b/meeting-logs/20110602.txt @@ -0,0 +1,553 @@ + ok let's start + !herd kde + (kde) abcd, alexxy, dilfridge, jmbsvicetto, patrick, reavertm, +spatz, tampakrap + roll call + 1 + 2 +-*- dilfridge hears bonsaikitten munching in the distance + 3 + +http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/maintainers/meetings/meeting-2011-05 + agenda ^^ + jmbsvicetto: here? + until he shows up, anyone familiar with the status of 4.7 so far? + nope + here + so, 4.6.80 + can you give us a brief summary of the betas please? +-*- alexxy here + I think I got most of kdebase, kde-utils, kde-graphics, +kde-games and kde-network working + alexxy then bumped the rest + about the status of the upstream tree / tarballs: + most problematic is kdebindings + I think no package is working + status of upstream tree / tarballs: + about kdebindings... I vaguely remember an e-mail longtime ago +when kde-4.7 was started, where the new split was explained + i recall that too + kdebase was split on 3 tarballs - kdebase, kde-runtime and +kde-workspace + do you think we should rename our metas? + the info is available in the readme.modularization of the +tarball + http://old.nabble.com/kdebindings-split-td30617636.html + http://paste.pocoo.org/show/399690/ + The question is will they stick to the names or not + at this point I think they haven't made up their minds yet + but they have the repos ready + don't they follow their repo naming schema? + alexxy: ^^ + I'm not sure they're doing it consistently + >:| + for example, smoke (which I think is a single repo) was split +into 3 tarballs +--> Skiarxon (~quassel@ppp091138207078.dsl.hol.gr) has joined #gentoo-meetings + smokegen, smokeqt, smokekde + sec + like in the deptree + can i have a list of the bindings tarballs? + I'm not sure as I didn't had the time to go after the repos. I +based my work in the existing tarballs and on the live ebuilds - which were in +very good shape!!! + i'd like to compare with the repos right now + I can give you the tarballs names for them. I still think +there's a missing krosspython, but after 3 emails I've yet to get a proper +reply + i follow the list, yes + so as I said: smokegen, smokeqt and smokekde + jmbsvicetto: I'd hope the live ebuilds were in good shape -- I use them +myself :) + here are the repos for referrence: +https://projects.kde.org/projects/kde/kdebindings + smoke is consistent so far +-*- alexxy also use live =) but now gonna switch to betas + perlqt, perlkde, qtruby, qyoto, korundum, kimono and pykde4 + tampakrap: ok, then the live ebuilds need to be updated as well + perl is consistent + should we pkgmove smoke to smokegen, or just add a block on +smokegen to smoke? + everything is checked + block, because we're not changing :4.4 and :4.6, I'd think :) + the tarballs are consistent to the names in the +README.MODULARIZATION file + ruby is consistent + ABCD: only 4.7 is involved + dilfridge: everything is + :) + tampakrap: pkgmove moves *every* version unconditionally + so, to get kdebinding we need to start by spliting smoke. I +wasn't sure if the live ebuild was ok or not, so I didn't start that + (you *cannot* use a versioned atom in that spot) + so, we follow upstream's repos for kdebindings since the tarballs +and repos, do we all agree? + yes + ABCD: correct, i got you wrong + yes + seems a good idea + and I'm for blocker, not move + also seems we need something to do with kross* modules + If no one beats me to it, I'll work on it this weekend + blocker is one way + alexxy: what about them? where are the tarballs? :) + tampakrap: no tarball for krosspython + mia + tampakrap: dunno =) + if you want, prepare the live ebuilds then + tampakrap: the README mentions the pykde4 tarball, but it no +longer includes any code + i believe they'll follow the repo names as the rest of the module + this is about the only really crucial piece of binding because of +plasma... + jmbsvicetto: sorry? + where is the pykde4 code then? + sorry, I'm mixing tarballs + ok, we're done with bindings + jmbsvicetto: give us the modules that are monolithic please + kdepim is one of them, what else? + kdegames + kdeutils + kdenetwork + those haven't migrated yet correct? + kdenetwork + kdemultimedia +-*- tampakrap checks + kdetoys + kate (kinda), kde-baseapps, kde-runtime, kde-workspace, +kdeaccessibility, kdeadmin, kdeartwork, kdegames, [kdelibs], kdemultimedia, +kdenetwork, kdepim, kdeplasma-addons, kdesdk, kdetoys, kdeutils, kdewebdev + kdesdk + kdegames, kdeutils, kdenetwork, knemultimedia, kdesdk are still in +svn + oh yeah, kate was also fun + also kdetoys, kdeaccessibility, kdeadmin, kdeartwork + kate is now the name of the module, so I had to update the +eclass as we hadn't "predicted" that case and the src_unpack was failing + so, i'd say let's keep them as they are + kdelibs is something we need to watch out. There's some doubt +whether it'll be split kdelibs and kdelibs-experimental + one by one please + don't mix them + kdelibs-experimental is not going to be a tarball + it is an experimental repo + yes, but kdelibs-4.6.80 had a dep on libs from it. Dirk ended up +"smashing" it all together in kdelibs-4.6.80 + ...one that's currently *required* by kdelibs proper + yeah + which was a mistake +--> devurandom (~devu@unaffiliated/devurandom) has joined #gentoo-meetings + there was a discussion in the ml whether that dep was a mistake +or not. I don't recall the conclusion + so, about the ones that haven't migrated yet + anyone knows if this will be done during 4.7? + it's likely + causing more mess? + of course :) + we're fsck'd then + oh well + probably with kde-5.0 they'll move to mercurial... + anyway + lol + what about the kde-* ones? should we change our metas? + kde-baseapps kde-runtime kde-workspace + What's the name of the repos? + the same + personally i'd prefer sticking to the repos name + and tarballs name of course + in that case it would make sense - unless they decide to rename +it again + no they won't + we could perhaps wait for next beta release, just to be sure ;) + sure + of course, that means we'll have to check for `has_version +kde-base/kdebase-runtime-meta || has_version kde-base/kde-runtime-meta` +everywhere + i think we covered all the monolithic/not converted yet tarballs +so far + yes + it is a major change + at this point I don't think krosspython will be fixed on this +release (Dirk already said a kdepim issue would have to wait for next release) + ok + so, what about kate? + it should be working now +--> ni1s (~ni1s@1-1-4-36a.dre.sth.bostream.se) has joined #gentoo-meetings + do you also fix the 4.7 lives? +<-- ni1s (~ni1s@1-1-4-36a.dre.sth.bostream.se) has left #gentoo-meetings + I actually forgot to test it on my test box :\ + I started by touching 4.6.80. I think ABCD and alexxy applied +the changes to 9999 now + I don't know anything about 4.7.9999 + there is no 4.7.9999 yet + because upstream hasn't branched + lol? + they tagged from master? + yeah -- just like they usually do for the betas :) + ok that sucks + so, how's 9999 then? + alexxy probably knows best + 9999 is fine -- I forward ported most of the -4.6.80 changes so that we +can bump 4.6.85 (or whatever) from 9999 -- note that okular-4.6.85 will be +coming from its own tarball, not the "monolithic" kdegraphics-4.6.*.tarball + (or it should be -- they just finished that split) + great, thanks + speaking of kdegraphics + so, anything else on monolithiks/no migrated yet + heh. also i think we can drop eclass foo from all :live tarballs + before proceeding to the splitted/migrated ones? + the kdegraphics libs are tagged from the same branch as the ones +distributed with digikam + since we now know how they will be packaged + alexxy: the if blocks? + meaning with 4.7 the incompatibilities will go away + sure, I already did it for 4.6.80 ebuilds + yeah + so we should do it for :live + ABCD: did you push those changes to 9999? + alexxy: already done -- 4.6.9999 keeps it, though + jmbsvicetto: yeah + also i'm going to make universal ebuild for kde-l10n (that should +support :live and regular tarballs) + good + dilfridge: yours + ? + you were saying that kdegraphics... + fyi, if/when slotting gets dropped, 4.x.9999 will become something like +4.x.49.9999 to keep versions in order + the kdegraphics libs are tagged from the same branch as the ones +distributed with digikam + so our problems with digikam will go away + cool + ABCD: what do you mean? + slotmove everything back to 0? + tampakrap: yeah + are you crazy?? + not 4? + tampakrap: that would seem to be the goal of dropping the +slotting + i don't see a reason to do that + i think it makes sense + the main reason we had slots to begin with was +kdeprefix -- kdeprefix +will be gone as of Monday next week + dilfridge: if we want to drop kdeprefix, we should drop the +slots + jmbsvicetto: yes that is what I mean + we should definitely drop the slots + yeah, but 4.x.49.9999 doesn't + dilfridge: I don't know if we should use :0 or :4 :) + 0 or 4 is all the same + and why are slot 4 so bad? + not when 5 comes along :) +<-- devurandom (~devu@unaffiliated/devurandom) has left #gentoo-meetings + then you admit to introduce kdeprefix later? :P + 4.x.49.9999 makes actually a lot of sense + tampakrap: 4.x.11 < 4.x.49.9999 < 4.x.80 (4.{x+1} beta 1) + 4.x.80 (4.{x+1} beta 1) < 4.x.9999, which means that portage would see +it as a downgrade + what is the big problem with slot 4 anyway? + yes, 4.x.49.9999 sounds good, even though we could argue that +4.x.49 would be the same + i don't understand + jmbsvicetto: given the differences between kde-3 and kde-4, I +would not rule anything out with kde-5 + tampakrap: I don't have a problem with slot 4. I'm just saying +that have slot=4 or slot=0 is all the same for the PMs + tampakrap: the idea is to get the versions in some sort of order, such +that 4.x.y, where y < 50 is KDE 4.x, and 4.x.y where y > 50 is KDE 4.{x+1} + ABCD: I agree, but as I said, 4.x.49 would be as good as +4.x.49.9999 + there should never be any 4.x.49 release - or they'll have to +modify their release numbers ;) + except at some point maybe someone will introduce a 9999-magic in +portage... + jmbsvicetto: 4.x.49.9999 makes it a bit more obvious that it's live +(and I think at least one PM assumes that it can't be a live ebuild if it +doesn't have "9999" in the version) + and the 9999 use is a "design" option, not a requirement + repoman does that similarly + PMS doesn't acknowledge 9999 as special, afaik + repoman is based on eclass inheritance, iirc + I think paludis does (I remember hearing something about that) + I know portage uses inherit() to determine what "live" is + in any case I don't have anything against 4.x.49.9999 + ok + i must admit i still don't understand + I just fell 4.x.49 is smaller and if it works as well (which I +think it should) we may want to use that + but since the rest of the team does, i step aside + tampakrap: what part don't you understand? + tampakrap: what don't you understand? The ordering? + 1) why slotmove a million ebuilds to 0 again 2) what is 49? + tampakrap: why slotmove? it makes upgrading *much* easier (no more +nasty blockers) + well i think we still should have slots =) + please no slots anymore + ok + it makes life so much simpler and without kdeprefix there is no +real reason for it + there will be kde5 next year + not sure + so we should have at least one slot + tampakrap: as we're dropping kdeprefix, there won't be any more +reason to have different slots for each version + yes, that's ok + I'd go for "move everything to 4" + +1 + 2) what is 49? It's less than 50, which is the arbitrary cutoff used to +determine if 4.x.y is part of KDE SC 4.x or KDE SC 4.{x+1} + tampakrap: and if we put all packages in the same slot, we can +simplify the eclasses + ok + about slot=0 or slot=4, that is something that only has meaning +to humans, not to the PM + put everything to 4 then? + quick vote + 0 or 4 + whatever slot you want to use + +1 for :4 slot + 4 + 4 +-*- ABCD doesn't care + I can live with both. 0 would be more "accurate" if we don't +want to have kdeprefix anymore, 4 otherwise + i don't intend to slotmove all the kde-misc ebuilds again + by dropping slots, we need to update all deps to use versions +and not slots + and we won't have kdeprefix (the actual flag might live for a short +while longer, but if it does, it will just be to do pkg_setup() { use +kdeprefix && die ....; ....; }) + jmbsvicetto: they already do -- except when USE=kdeprefix + ABCD: about 49, since 4.x.80 are 4.x+1, why not just use this? + and deal with an extra number? +-*- ABCD isn't sure what you're trying to say, tampakrap + tampakrap: the idea is that the first release KDE will ever do +of a new version is 4.x.50 + that's what they've written in their release "rules" + yes, but the tarballs are shown after 4.x.80 + before that there is only live ebuilds + sure, but since 4.x.50 is a new version, 4.x.49 should be used +as the last version of a version + tampakrap: they've released tarballs for alphas before, with lower +numbers + they won't anymore though + bah, terrible language :\ + they said that interested parties can get the tarballs from +redmine or gitweb + tampakrap: why take the chance? + i don't think there is a chance here but anyway + 49 it is + tampakrap: 4.x.50 should never be used for version 4.x - +recently the most they've been getting is 4.x.7 anyway, right? + true + anyway, i think we all agree here + and 49 is just an arbitrary number that is definitely between the last +4.x release but before the first 4.{x+1} release (and I've hardcoded the +4.x.50 assumption in other places) + ok + next + the "50 limit" is already in the eclass + jmbsvicetto / alexxy status of migrated/ split modules? + yeah + do we follow upstream there? should we? + besides the missing krosspython, everything else should be +working + I think we should + (follow upstream) + actualy most of migrated and splited modules has same spliting as we +do + on 4.6.80 we're already doing it + one by one + kde edu, check? + https://projects.kde.org/projects/kde + kdeedu we are 100% following upstream + kde graphics, check? + the split on our end is complete + for both + kde base + kdegraphics, they didn't finish splitting in time for 4.6.80, but +should be done for 4.6.85 + (we might want to package the new mobipocket repo, though -- I'll look +into that) + kdebase is consisted of three monolithic and two split repos as i +see + so we're fine here +- {Day changed to Fri Jun 3 00:00:00 2011} + plus one more (kinda) monolithic repo: kate :D + kwrite moved from kde-baseapps to kate + kdepim/kdepim-runtime is monolithic, check + yeah + how are we on that area? + tampakrap: they may split it + kate/kwrite i mean + kdepim is NOT going to get split + and nothing that migrated is going to change + kdepimlibs/kdelibs are monolithic on both sides + last question: + is the bump ready from our side? + should i announce it? update docs? + bump of what? + 4.6.80 + in general + tampakrap: we should run more tests and still need to fix some +stuff + tampakrap: its NOT ready + what's missing please? + tampakrap: upstream to release a kross-interpreters tarball :D + if you speak now you may get more help :P + yeah, apart from that :) + kdebindings + =) + kdebase + kdegraphics + kdemultimedia + kdenetwork + kdeedu + +kdegames + kdetoys + (most of) kdeutils, should work + afaik kdebindings is broken. I don't know kdepim status + assuming that you disable anything that needs krosspython (pykde4 +probably should work, I would think) + ok, so i suppose i should not recommend people to update to it at +all + pykde4 build on my test system. I haven't tested it though + jmbsvicetto: kdepim should work + not at this stage + I'd wait for a krosspython release (probably next beta) + ok, so what's needed from our side? + tampakrap: for the above list, I can say my testing system is +running. I'm not using too many kde apps on it though + I'm using it mostly as a build box, some browsing (FF), kwrite, +kopete and general DE use + cool + thank you guys for handling it + good job + I haen't tested the games or kdeedu apps yet + i don't have to say anything else on 4.7, if anyone has to say +something speak now + sorry for the commit noise, but I'm a "old grumpy" dev ;) + we'll kick your ass later + dilfridge: next topics are yours + ho hum + use flag defaults for kde subprofile (bug 365251) + tampakrap: https://bugs.gentoo.org/365251 "Use flag defaults for +the desktop/kde profile"; Gentoo Linux, KDE; CONF; dilfridge:kde + ok... all that I listed were (as far as I remember) not in the +desktop profile + maybe we just go quickly through use-flags and vote whether they +should be enabled in the kde profile (NOT forced of course) + 1) cups - I think this is a clear usability improvement + isn't the system-config printer broken? + and hardmasked? + eww + possibly + as I stated when the kde profile was created, I don't like the +idea too much, but as I don't use it, I don't care + cups: no + we'll come back to that topic later ("open floor") + ok + 2) dri, xcomposite, xinerama + +1 + since kwin heavily relies on all that stuff + 3) -gnome + no + this is to avoid problems like the recent glib-networking desaster + don't need it -- I don't think desktop/ sets +gnome anyway :) + ok then not + true + 4) nsplugin + since konqueror provides a plugin container + no opinion + no strong opinion here either, so maybe lets forget about it + 5) semantic-desktop :) + yes! + as it is needed by kdepim + 6) xscreensaver + to provide more eyecandy + +1 + opengl + gles + -1 on gles, I think + (unless I'm mistaken) + opengl +1, gles -1 + as I thought that gles was primarily for embedded, or something like +that + but +1 on opengl + kwin will work with it better then with opengl + opengl is already in desktop + there we go :) + if you use gallium drivers + that's not a reason to force it in every kde user + ok that's it for me on this topic, I summarize: + these are defaults, not forced :) + we add the following flags to the default use flags in the kde +subprofile: + wait i want more + ok + qt, qt4 + qt4 is in desktop + qt? + not + qt is old apparently + declarative + yes + kipi + yes + phonon? + is that enabled already? + no + we should add it + ok + and qt3support? + is this being dropped by upstream? + in desktop + i know + if it's being dropped of 4.7 we should consider dropping it from +desktop + good question, I know they are working in that direction + ah and plasma + is that enabled? + no, I'll add it to the list. qt3support maybe worth a mail to the +releaseteam + ok + that's all + "declarative dri kipi phonon plasma semantic-desktop xcomposite +xinerama xscreensaver" + ^ any further comments? + ok then with your ok I'll add this later to the profile + no, i want to announce it first + ah ok + fine + anything else? + next topic would be kdeprefix status + we already discussed it i suppose + yes + ok next... + kde-4.6.3 + should be fine, i don't see bugs :) + I would like to file a stablereq in a week or so (30days etc), +just so stable keeps up + bug reports that is + ok... if there are any problems or if you have any objections, +talk to me please :) + that's all? + from the agenda, yes + *) open floor + open floor- one point from me + shoot + i was kind of crazy enough to mail tgurr about cups-1.4 +stabilization + basically I can go ahead sorting the remaining bugs etc + this may take some time, but at some point I hope we'll have some +news there + that's all + ok + and one point from me: + we lost scarabeus, we need new people + i mean, what comes next? losing jmbsvicetto? +-*- jmbsvicetto slips away + we should all move on to qa and recruit diego for kde :D + actually, he was a kde guy long ago + did not know that + tampakrap: all I can say about that is that I'm trying to use my +council hat to ensure we fix the issues that affected Tomas motivation + Diego and Dan Armak started kde on Gentoo, I think + if not, they maintained kde on gentoo for many years + we need scarabeus and ssuominen back + at this point and unless people change, that seems unlikely + btw, meeting closed, thanks for coming diff --git a/meeting-logs/20110831.txt b/meeting-logs/20110831.txt new file mode 100644 index 0000000..b935c55 --- /dev/null +++ b/meeting-logs/20110831.txt @@ -0,0 +1,479 @@ +[00:13:23] !herd kde +[00:13:23] (kde) abcd, alexxy, dilfridge, jmbsvicetto, mschiff, patrick, reavertm, spatz, tampakrap, thev00d00 +[00:13:28] meeting start +[00:13:32] First topic: KDE 4.7.0 stabilization (without kdepim) +[00:13:43] +1 +[00:13:45] +1 +[00:13:45] dilfridge: reason to do so? we usually stabilize after the .0 release +[00:13:50] no bugs +[00:13:57] fyi i object, i have plenty +[00:14:04] the upgrade went perfectly smooth here +[00:14:34] and there are also no significand new things on bugzi +[00:14:35] tampakrap: I haven't hit any more bugs than usual +[00:14:39] but bugs is a general problem of kde not only 4.7.0, I am running 4.7.49.9999 here +[00:14:42] fwiw kdepim works fine here as well, why don't we stabilize this one as well? +[00:14:53] maybe with .2 ` +[00:14:55] ? +[00:15:09] I'll leave kdepim for those of you that actually use it :P +[00:15:18] i use kdepim-4.4 +[00:15:28] kdepim 4.4 is obsolete, no bugfixes, no security updates +[00:15:29] kdepim is special: I think there the newest version is better these days +[00:15:35] can't we keep them both and just notify users? +[00:15:39] sure +[00:15:40] and let them decide on what they want +[00:15:41] (speaking of the *2 versions) +[00:15:56] but i still object on stabilizing .0, i have some plasma regressions +[00:16:04] like? +[00:16:08] and of course we don't get such bugs, since they are upstream +[00:16:17] i have problem on focus +[00:16:17] I guess .1 is not far away right? +[00:16:24] has there ever been a version without plasma regressions? +[00:16:31] another i have is that taskbar entries are not highlighted correctly +[00:16:32] tagging tomorrow, technically +[00:16:44] release sept 6 isnt it? +[00:16:50] I have som eprobs here too: a windows that had a notify, tends to keep that status in the window bar +[00:17:04] but maybe messed up because of 2 migratet categories +[00:17:22] ok +[00:17:26] so +[00:17:29] mschiff: I have the same, sticky red quassel for example +[00:17:39] consensus seems to be more, stabilize 4.7.1 +[00:17:41] my opinion is to stabilize .1 (after a meeting decision) WITH kdepim +[00:17:46] Thev00d00: exactly, I think its what tampakrap also meant +[00:17:52] but let the users know first +[00:17:59] document everything etc +[00:18:08] news item maybe +[00:18:08] maybe even put a news item out as well +[00:18:20] ok fine with me +[00:18:29] +1 for .1 with pim +[00:18:38] anyone else? +[00:18:53] But 4.4 should stay in tree for some time +[00:18:58] yes +[00:19:07] I'll take care of it as good as possible +[00:19:15] +1 for .1 +[00:19:24] ok +[00:19:32] then +[00:19:34] ok, prepare a news item, and take care of the documentation then, and after next month's meeting we'll decide on 4.7.1 +[00:19:48] anything else? +[00:20:05] so not stabilize .1 as its available? +[00:20:11] next topic then +[00:20:28] no, after meeting +[00:20:36] tampakrap: I'd try to decide the stabilization by email +[00:20:53] no problem +[00:20:54] mschiff: at earliest 30days after release, so we have lots of time +[00:21:02] anyway, next topic +[00:21:06] 2) Road towards KDE 5 - what news is there from the Desktop Summit? +[00:21:16] who was at the Desktop Summit? +[00:21:20] ah that was me!! +[00:21:21] you +[00:21:44] so, i learned there that Qt 4.8 is NOT going to be split +[00:21:51] Qt 5 will +[00:21:58] into what? +[00:22:03] and we have plenty of time to worry about KDE 5 +[00:22:09] into small parts +[00:22:10] =) +[00:22:14] even atoms +[00:22:22] even Thiago didn't tell me details +[00:22:26] oh dear, radiation alert +[00:22:29] I'd *really* like split tarballs +[00:22:36] tampakrap: is there any eta for kde5? +[00:22:39] a 200M download when you need 10M is a bit sad +[00:22:46] about a year or so? +[00:22:51] not yet, but we have plenty of time +[00:22:52] work started in kdelibs +[00:23:00] framework branch +[00:23:07] and they won't do big changes like the 3->4 transition +[00:23:41] that's what some core KDE developers (like Aaron Seigo and David Faure) said in their presentation +[00:23:59] will there be a kde 4.8? +[00:24:03] yes +[00:24:11] but Alex has been talking about using the bump to get some ABI incompatible changes +[00:24:31] also seems something is going to happen with nepomuk +[00:24:33] that has been mentioned multiple times in the release ml +[00:24:37] that was the plan, it changed somewhere in the middle +[00:24:45] hmm +[00:24:52] unless you are talking about something else +[00:25:15] I heard some rumour about kdelibs basically remaining at 4.7? +[00:25:46] i also took part in a release team BoF along with Slackware, Fedora, openSUSE packagers and a GNOME release team guy +[00:25:58] chaired by Sebastian Krugler and Dirk Muller +[00:25:59] Alex also worked on getting all KDE cmake files that were ok for kitware into 4.8.0 (?) and created the new cmake-extras packages +[00:26:02] package* +[00:26:20] they talked about the splitting of modules, how to handle it and about future KDE releases +[00:26:28] dilfridge: They've been saying there won't be a kdelibs-4.8 +[00:26:36] ok +[00:26:41] so nothing big is expected +[00:27:04] are you talking about the superbuild package? +[00:27:20] No, that was their "reply" to slackware +[00:27:46] no idea what you're talking about then +[00:27:57] afaik there will be kdelibs 4.8 and KDE SC 4.8 +[00:27:59] The cmake-extras package is a package that Alex has "sponsored" to have all cmake files that can't be accepted into cmake by kitware +[00:28:09] ah yes +[00:28:13] i recall now +[00:28:18] tampakrap: that's not what has been talked in the kde relase ml +[00:28:21] what does have to do with us? +[00:28:21] Alex ? +[00:28:33] but I haven't talked to anyone about this nor was I at the Desktop summit :P +[00:28:33] Alexander Neundorf, main buildsystem guy +[00:28:35] ah +[00:28:50] i follow the kde release team, never saw such thing :/ +[00:29:15] tampakrap: What I'm saying is that they've talked about doing incompatible changes. I hear from you that is not what they're going to do +[00:29:36] they were, but things changed in Qt, thus in KDE +[00:29:42] that's what i know so far +[00:30:13] but they had also decided on not having KDE/ branches and just branches and now in the kde-scm ml they're almost reverting that because of the talks other KDE devs had on kde-core-devel that appearantly didn't follow the kde-release or kde-scm mls +[00:30:27] tampakrap: ok +[00:30:49] anyway +[00:31:03] if big changes are going to come we'll know them in time +[00:31:07] we always did +[00:31:08] true +[00:31:44] https://plus.google.com/photos/116381667574498856310/albums/5637225108859383905 <-- and here are the photos for those who haven't seen them, to make you jealous +[00:31:50] :D +[00:31:59] anything else here? +[00:32:12] not from me +[00:32:29] or me +[00:32:57] ok +[00:32:57] 3) The NetworkManager-0.9 mess +[00:33:03] hehe +[00:33:05] no idea here +[00:33:09] the basic summary is +[00:33:23] A gnome-3 requires networkmanager-0.9 +[00:33:37] B kde does not support networkmanager-0.9 +[00:33:52] A seems to be set in stone +[00:33:57] dilfridge: knetworkmanager works fine with nm09 +[00:34:04] B is being worked on +[00:34:07] yes +[00:34:14] and i use this combination on my laptop +[00:34:16] dilfridge: wasn't the delay on solid? +[00:34:27] also in git master of kdelibs there is a stub for nm09 +[00:34:33] for solid +[00:34:38] what alexxy is using and what we have in the tree now is the nm09 branch +[00:34:38] I don't use knetworkmanager, nor networkmanager, so I don't know anything about it +[00:35:00] that is basically sponsored by fedora, as they have the same problem +[00:35:04] and it seems to work ok +[00:35:13] it mostly works +[00:35:16] excetp wimax +[00:35:17] =) +[00:35:34] so my cell modem and wifi + vpn works fine +[00:35:43] didn't someone put a masked knetworkmanager 0.9 compatible in tree? +[00:35:46] the only problem with it is that the knetworkmanager developers do not really support it but have different plans (or lack of motivation) +[00:35:52] tampakrap: yes me +[00:36:04] basically it is a fedora-fork +[00:36:09] dilfridge: no +[00:36:15] its different approcah +[00:36:30] fedora has patched nm09 with nm08 compatibility layer +[00:36:41] nm or knm? +[00:36:46] nm +[00:36:52] knetworkmanager developers were in summit, why didn't you tell me earlier to talk to them? :/ +[00:36:53] strange +[00:36:59] anyway +[00:37:01] and its own patched version of knm +[00:37:21] oh dear :-/ +[00:37:21] probably the best thing is to just stick to the nm09 branch +[00:37:23] there 3 impletation of nm09 support in knm +[00:37:34] first one is fedora +[00:37:45] second nm09 branch from knm devs +[00:37:52] and third libqtnm +[00:38:00] that is worked on +[00:38:08] we use second one +[00:38:15] since its only working +[00:38:15] what's libqtnm? +[00:38:34] i dont remember how its called correctly +[00:38:40] anyway +[00:38:45] but they want to create qt lib fro nm +[00:38:45] alexxy: shall we continue using nm09 branch, what do you think? +[00:38:45] since it works, and it is in tree +[00:38:49] what is the problem? +[00:39:02] tampakrap: there is no real problem +[00:39:08] dilfridge: i think that it will be best chois at this time +[00:39:25] the purpose was only to make people aware that this may become problem at some time +[00:39:34] but right now I agree with alexxy +[00:39:42] summarize the problem please, i'm confused +[00:39:59] dilfridge: there will be no problems with migration +[00:40:09] since nm settings are stored by nm +[00:40:10] chaotic situation, many different approaches, no clear upstream +[00:40:15] and not by applet +[00:40:47] alexxy: ok +[00:40:53] so summary: no problem +[00:40:57] :D +[00:40:57] but we have something that works at the moment, so let's just wait for upstream to fix their mess +[00:41:13] ok +[00:41:16] next point? +[00:41:18] next issue +[00:41:31] meh it's me again +[00:41:34] 4) Does anyone still have an overview of the glib-networking/libproxy problem? +[00:42:05] pacho was quite insistent that we have a look at this +[00:42:15] because it blocks a big fat sec bug +[00:42:58] i don't use that app at all +[00:43:49] it's pulled in eg by firefox +[00:44:15] I went through the >100 comments and tried to make sense of it yesterday +[00:44:20] dilfridge: I can't help as I don't use it as well +[00:44:30] I never had the problem myself either +[00:44:34] which flag in firefox? +[00:44:45] dont remember sorry +[00:44:57] a guy put a summary there did you look at it? +[00:45:14] yes, me :]... I *believe* the problem is fixed +[00:45:22] but believing = not knowing +[00:45:31] does anyone else know anything? +[00:45:54] I do not have it installed +[00:45:58] I recommend the gnome guys just go ahead... +[00:46:04] any dupes? any activity in the bug? +[00:46:21] not anymore for a while (that's why I think it's ok now) +[00:46:42] go on then +[00:46:56] ok I'll tell them to just go ahead +[00:47:08] next topic +[00:47:21] 5) Suggestion - splitting the Gentoo KDE Guide into two pages +[00:47:21] 1) main page: main tree, stable and ~arch things only +[00:47:21] 2) poweruser page: overlay, live ebuilds, sets, kde-sunset +[00:47:31] who added this topic? +[00:47:33] my suggestion +[00:47:38] and I'd be willing to do it +[00:47:45] but only if you think it's good +[00:47:47] that's a no :) +[00:48:02] from the very beginning i wanted that guide to be monolithic +[00:48:14] else there will be a lot of duplication +[00:48:40] plus readers will be able to jump from one topic to another (eg see the existence of the overlay quickly, and maybe prefer the live ebuilds or snapshots) +[00:49:01] there are tags there as well, append #kde4_6 and similar +[00:49:02] I think it should always be clear what the guides refers to: ~arch or stable +[00:49:11] it is +[00:49:45] -*- dilfridge is slightly distracted by some dirndls walking past the window +[00:49:47] people don't go by branch, they go by KDE version +[00:50:39] anyway, anything else here? +[00:50:42] no +[00:50:48] the guide needs update +[00:51:09] what kind of update? +[00:51:15] hald +[00:51:18] -- +[00:51:23] the removal instructions +[00:51:33] live branches +[00:51:37] not correct +[00:51:52] true, give me a patch :) +[00:52:08] I hald really still being used? +[00:52:15] and maybe some info from the upgrade 4.4 guide +[00:52:24] mschiff: no +[00:52:33] j0hu: are you willing to update it? +[00:52:45] should we kill the upgrade guide and merge some info into the main guide? +[00:52:50] will do after finishing the quizz +[00:53:08] merge info: yes, kill the upgrade guide: not yet +[00:53:31] anything else? +[00:53:50] go ahead +[00:53:59] not here +[00:54:11] 6) Build system architecture bug +[00:54:15] +s +[00:54:24] bug 358059 +[00:54:26] tampakrap: https://bugs.gentoo.org/358059 "cmake-utils.eclass PREFIX is not defined"; Gentoo Linux, Eclasses and Profiles; CONF; meka:kde +[00:54:45] no idea about the consequences +[00:55:02] I was kind of hoping that reavertm would turn up +[00:57:06] if it is defined either way +[00:57:12] why defining it earlier is a problem? +[00:59:02] but wha does the patch kill the /usr default? +[00:59:15] I dont understand problem nor solution +[00:59:28] I only looked at the patch +[00:59:40] mschiff: see line 7 +[01:00:01] I'm more concerned about lines 32/33 +[01:00:29] why suddenly add the prefix at a place where it was not needed before?! +[01:01:20] hm, seems a bit strange to me +[01:01:40] this is wrong indeed +[01:01:44] seems like $libdir must not be set this way +[01:01:46] the rest is fine imho +[01:02:10] if it was set to /usr it will end up in /usr/usr/lib +[01:02:45] ok shall we kill the 32/33 chunk and test the rest in the overlay? +[01:03:03] not sure +[01:03:08] me neither +[01:03:08] we need more eyes indeed +[01:03:19] CC scarabeus and reavertm there and ask them +[01:03:22] I'll try to persuade scarabeus +[01:03:25] yes +[01:03:36] next one +[01:03:44] the rest ist nothing special +[01:03:54] 32/33 is the only real change +[01:04:07] ok +[01:04:09] next +[01:04:13] bug 356681 +[01:04:15] tampakrap: https://bugs.gentoo.org/356681 "Please remove media-libs/phonon dependency from kde-base/kdelibs"; Gentoo Linux, Ebuilds; CONF; hwoarang:kde +[01:04:32] i don't like this one, and i am not willing to work on this +[01:04:45] jmbsvicetto: is it a good solution to create a virtual/phonon? +[01:05:41] I fear that the number of problem sources could explode with more than one implementation :| +[01:05:56] sorry, I was looking at the patch for the previous bug +[01:06:01] YEEEHAH +[01:06:03] can we hide it under a kde flag? +[01:06:09] btw, the only "real change" in there seems to be the following: +[01:06:10] - SET (CMAKE_INSTALL_LIBDIR ${libdir} CACHE PATH "Output directory for libraries") +[01:06:11] ...sorry I missed most of the meeting (I just got back from a family dinner, which I was rudely informed was more important than this :D) +[01:06:11] err sorry +[01:06:13] + SET (CMAKE_INSTALL_LIBDIR ${PREFIX}/${libdir} CACHE PATH "Output directory for libraries") +[01:06:22] -*- dilfridge just read "CURRENT STATUS OF MANUSCRIPT: Editorially approved for publication" +[01:06:53] jmbsvicetto: thats what I was saying +[01:06:57] -*- alexxy still waits for similar resolution from jpcs +[01:06:59] about phonon, are they compatible now? +[01:07:00] and in the eclass: +[01:07:04] # Eclass respects PREFIX variable, though it's not recommended way to set +[01:07:04] # install/lib/bin prefixes. +[01:07:04] # Use -DCMAKE_INSTALL_PREFIX=... CMake variable instead. +[01:07:22] cause qt-phonon was behind phonon for a long time +[01:07:39] no idea about qt-phonon +[01:07:43] and i don't care tbh +[01:07:56] I'll see what I can do about this one +[01:08:14] I still think we should prefer media-libs/phonon to x11-libs/qt-phonon, though +[01:08:15] i'm asking if a virtual is fine, or if we can do this but introduce a kde useflag there so that media-libs/phonon is default +[01:09:03] we could say something like " kde? ( media-libs/phonon ) !kde? ( virtual/phonon ) " +[01:09:17] dilfridge: kdelibs? +[01:09:23] f.ex. +[01:09:31] yes, in other kde apps as well +[01:09:34] if that is possible and even works +[01:09:35] i like it +[01:09:46] dilfridge: if so, how's that any different from the current || ( media-libs/phonon x11-libs/qt-phonon ) ? +[01:09:58] anyone willing to work on these? (virtual/phonon AND qt-phonon for kdelibs) +[01:10:15] with !kde you can run kdelibs also with qt-phonon then +[01:10:20] not me +[01:10:20] a guy with -kde can get qt-phonon +[01:10:22] tampakrap: I'll have to check, but we used to support qt-phonon on kdelibs. We just defaulted to phonon +[01:10:37] I'll work on it +[01:10:45] ok cool +[01:10:46] dilfridge: then someone dropped the old conditional +[01:10:49] ok, have a look at both the virtual and the kde flag +[01:11:10] tampakrap: I don't know if we gain anything with the virtual (for KDE) +[01:11:30] i believe we are +[01:11:41] not only for kdelibs, but for other kde apps +[01:12:00] put virtual/phonon there instead of the conditional you pasted earlier +[01:12:03] seems cleaner +[01:12:20] until you think how to prefer media-libs/phonon over x11-libs/qt-phonon +[01:12:53] that's for kdelibs (solved by the flag) +[01:13:08] other kde or non-kde apps don't need to prefer anything +[01:13:08] I'll look at it and then talk to you +[01:13:13] sure +[01:13:28] bug 332829 +[01:13:30] tampakrap: https://bugs.gentoo.org/332829 "Inconsistency between distro's KDE4WorkspaceConfig.cmake and the actual layout"; Gentoo Linux, Library; CONF; cheepeero:kde +[01:13:50] i talked about it with reavertm, someone needs to work on it +[01:13:54] 99% it will work +[01:14:16] tampakrap: tell me if you need chroot testing +[01:14:33] not sure if anyone wants to do this in his main system first +[01:14:37] i can't work on it, someone else has to do it +[01:14:59] volunteers? +[01:15:08] whats this about? +[01:15:28] the internal configuration of the kde build variables is somehow messed up +[01:15:53] it makes problems for building apps outside portage +[01:16:27] that's about my whole understanding +[01:16:42] so do we have some qt developer in the team? +[01:16:54] dilfridge: that whole deal of building apps outside of portage, is something we should probably talk about again +[01:16:57] oh +[01:17:03] -*- Sput forgot to check this channel +[01:17:07] ABCD: ^^ wanna work on it? +[01:17:20] Sput: do you use kdevelop? +[01:17:23] mschiff: that needs cmake understanding, not Qt +[01:17:33] it is easy to test, there is a patch there already +[01:17:50] when we started with kde-4.X, we were clear that we supported portage and building packages with our ebuilds (we have ebuilds for all releases, snapshots and live) and that we wouldn't bother with supporting people that want to install software outside portage +[01:17:57] I still think that should be our stance +[01:18:06] tampakrap: yeah I meant someone who is gerneally developing something with qt or kde... +[01:18:32] jmbsvicetto: yes but if someone wants to use kdevelop? +[01:18:40] dilfridge: RESO:CANTFIX; KDE4WorkspaceConfig.cmake can only be installed by one package (for hopefully obvious reasons), yet must change when other packages are installed (breaking checksums) :) +[01:19:01] like, use the application to program something? +[01:19:11] dilfridge: if I understand the issue, get upstream to do a release +[01:19:56] dilfridge: if the problem is with testing applications built with kdevelop, I'd say the real issue is cmake +[01:20:00] jmbsvicetto: no, I mean if upstream is using gentoo?! +[01:20:15] dilfridge: I know how much KDE developers hated auto-tools, but this is a price you pay for using cmake +[01:20:37] well... it's not really my problem +[01:20:55] what I could do is feed the patch into a chroot and rebuild kde +[01:21:00] and look at the result +[01:21:09] ok +[01:21:34] do you think that would be enough testing? +[01:21:46] the package is libkworkspace, file is /usr/lib/cmake/KDE4Workspace/KDE4WorkspaceConfig.cmake +[01:21:54] and build kdevelop from source +[01:21:55] dilfridge: I've talked with Diego about the next bug, and even though we shouldn't be setting RPATH to /usr (KDE), if I understood the issue correctly, that alone won't fix the issue as the other applications (kdevelop?) are setting RPATH themselves +[01:22:34] bug 380415 +[01:22:37] dilfridge: https://bugs.gentoo.org/380415 "Qt and KDE libs and plugins should not have an RPATH"; Gentoo Linux, KDE; CONF; realnc:kde +[01:22:49] we could also drop the /usr/qt4 RPATH for QT as it's part of LDPATH +[01:22:56] tampakrap: could this be fixed in qt? +[01:23:04] i can't decide +[01:23:18] hehe agenda topic for next qt meeting +[01:23:27] One issue I talked to Diego but didn't understand is what kind of impact this might have for security +[01:23:27] sure, can you test beforehand? +[01:23:31] -*- dilfridge pushes the pile of papers to the next guy +[01:23:39] just reading backlog... fwiw, I've been using nm09 with knetworkmanager and USE=nm09 for quite a while, it works fine +[01:24:06] if anyone tells me how to disable RPATH in qt, yes +[01:24:27] and there won't be a kdelibs-4.8 release (the master branch is frozen now, and people are working in the frameworks branch) +[01:24:53] The user on that bug seems to want the QT/KDE libs built without RPATH so that if he builds and installs an app in /usr/local and (as I understand it), he adds a plugin to /usr/local the lib will "link" to that plugin - my question is won't that allow having system libs linking to user-controlled paths? That sounds dangerous +[01:25:21] jmbsvicetto: only if they are in LDPATH I guess +[01:25:29] jmbsvicetto: the point with Qt's RPATH of /usr/lib*/qt4 is that the qt team was going to *drop* it from LDPATH as soon as was practical +[01:25:35] The issue is that they are not in LDPATH +[01:25:56] better put, that is the complaint and what Diego was pointing out. If it's not in LDPATH it won't "magically" work +[01:26:00] and if someone is adding a local dir to LDPATH before system dir, that is his own stupidity +[01:26:25] ABCD: understood. That means the request cannot be fulfilled then +[01:26:40] dilfridge: sure +[01:27:04] dilfridge: but what they wanted was the libs to have no rpath so they could "link" to a lib anywhere - that's what sounds dangerous to me +[01:27:22] dilfridge: the default actually puts /usr/local/lib first before everything else (note, /usr/local/lib64 isn't mentioned until after /lib64 and /usr/lib64) +[01:27:32] dilfridge: and I don't use KDevelop at the moment +[01:27:39] dilfridge: even though, from what Diego told me, that won't work as without RPATH the system will only look under LDPATH +[01:27:39] /usr/local/lib is still root:root +[01:27:41] see /etc/env.d/00basic +[01:27:49] true :) +[01:28:44] ok I guess this is effectively going to be decided by the qt team +[01:28:48] so I don't know enough about this, but hope any change we do won't open any unwanted "doors" +[01:29:47] any more thoughts about this? +[01:29:52] dilfridge / tampakrap: No comments or objections from me to the next 2 (final) items +[01:30:42] the last two items are the simple ones +[01:30:51] no objections from me either +[01:31:16] my opinion: a) add libXkbfile globally, b) remove the useflag +[01:31:43] yes and yes +[01:31:43] do the libs/progs with RPATH set also have RUNPATH set? If so, then LD_LIBRARY_PATH overrides it anyway, so... :D +[01:32:56] (I think cmake uses the proper ld(1) options that make the linker set DT_RPATH *and* DT_RUNPATH) +[01:32:56] as for the Qt5/KDE5 thingy: Qt5 will be released next spring or so, KDE will take longer... work on kdelibs is going on in the framework branch +[01:33:04] >:| +[01:33:24] we need the qt herd to provide us with Qt5 ebuilds soonish (and I hope the eclasses still support proper slotting) +[01:33:44] I think some eclass magic is needed to make kdefoo 4.8 depend on kdelibs >= 4.7.0 +[01:33:48] Sput: argh... which gets back to the last issue +[01:33:48] Sput: i thought frameworks is going to be kdelibs 4.8 +[01:33:55] ABCD: yes but that is doable +[01:34:01] tampakrap: no, frameworks is not going to be 4.8 +[01:34:10] there won't be a kdelibs-4.8 +[01:34:10] dilfridge: that is "I think I'm going to have to write some eclass magic ..." +[01:34:12] and what is it going to be then? +[01:34:46] ABCD: or fakebump kdelibs to 4.8 :) +[01:34:51] well, probably what we call "KDE 5" although I'm sure the KDE promo team is going to come up with yet another naming scheme in time :P +[01:34:54] tampakrap: too much work :D +[01:35:07] Sput: there is no KDE 4, so how could there be a KDE 5? :) +[01:35:11] Sput: indeed +[01:35:18] ok let's wait then +[01:35:22] KDE is a community, you can't attach a version number to something like that :) +[01:35:22] ABCD: exactly +[01:35:22] Bulshytt! +[01:35:26] tampakrap: that's why last time there was a talk on #-kde about this I said we were going to have some fun like in the early KDE-4 days +[01:35:56] the frameworks branch ist going to be the next incarnation of kdelibs, currently they work on reorganizing/cleaning up/splitting kdelibs, as soon as Qt5 is released they'll port it over +[01:36:01] tampakrap: we're going to have kde-4.8 depending on kdelibs-4.7 and we may even have kdeA-4.8, kdeB-4.9, etc +[01:36:03] the rest of KDE will follow suit only later +[01:36:28] jmbsvicetto: that's only assumptions, just wait for the release +[01:36:29] if upstream slots things properly, I think we should slot; otherwise everything goes in :4 (which we might want to make :0 instead :D) +[01:36:37] there will be more kdelibs-4.7.x releases, but I don't think a 4.8 ever unless they changed plans again +[01:36:50] ABCD: nononono, what with :4 and :5 then? :O +[01:37:11] we certainly will have to slot Qt versions +[01:37:14] -*- dilfridge thinks we cannot really predict the upcoming chaos +[01:37:16] ABCD: no gain in moving to :0 again +[01:37:17] not sure about KDE +[01:37:26] ABCD: besides, don't forget some people still use kde-3.5 ;) +[01:37:44] Enable auto-destruct sequence +[01:37:50] Sput: qt is slot 4, isn't that sufficient? +[01:38:05] some people dont know how to remove 3.5 :P +[01:38:05] tampakrap: it is, if slotting still works in the eclasses +[01:38:26] it is, why shouldn't it? :) +[01:38:35] anyway, people, don't panic +[01:38:43] tampakrap: well, we've removed proper slotting support from the KDE eclasses +[01:38:48] who knows what the qt herd did :) +[01:38:51] you are all making assumptions here, just wait for the next release to show up +[01:38:55] tampakrap: because it hasn't been tested in a long time ;) +[01:39:06] lol +[01:39:15] tampakrap: well, Qt5 is already under development (and I will start working with it in a few days), I'd love to be able to install it into Gentoo +[01:39:23] (without removing qt4 obviously) +[01:39:46] Sput: unless we get ABI deps, I suspect you're going to have *great* pain trying that +[01:40:07] true, nothing's going to be so smooth for sure +[01:40:09] unless every binary sets the correct RPATH :P +[01:40:14] major versions ahead, red flag +[01:40:34] jmbsvicetto: well, used to be the case that just calling the correct qmake version would set everything up correctly... +[01:41:01] this is going nowhere +[01:41:02] I'm just saying, we need to be aware of Qt5 being right around the corner already +[01:41:06] let's just wait and see +[01:41:12] it's not something that'll hit us in a few years +[01:41:18] tampakrap: no need for anyone to stuck his head in the ground, but it's probably wise to look over the ship's border in case a huge wave rocks the boat ;) +[01:41:20] dilfridge: this is open floor, of course it's not going nowhere :) +[01:41:33] -*- dilfridge gets himself a drink +[01:41:39] -*- Sput has a beer +[01:41:49] -*- tampakrap drunk his already +[01:41:52] meetings are long, eh :) +[01:41:57] -*- Sput has moar in the fridge +[01:41:58] and btw, MEETING IS OFF +[01:42:08] summary tomorrow diff --git a/meeting-logs/20120116-summary.txt b/meeting-logs/20120116-summary.txt new file mode 100644 index 0000000..bb34fcd --- /dev/null +++ b/meeting-logs/20120116-summary.txt @@ -0,0 +1,70 @@ +1. Roll call +alexxy, jmbsvicetto, dilfridge, johu, mschiff, tampakrap, Thev00d00 + +2. Electing a new team leader +Since one year is not over yet, it will be skipped for the next meeting. + +3. What shall we do with kdepim-4.4 +KDEPIM 4.4 is not supported any more by upstream, but on the other hand +KDEPIM2 is still too buggy. We had a discussion if we should remove it +completely or if we should continue maintain it, despite the compatibility +bugs that started to emerge with newer KDE versions. Final decision is that we +will continue support it as long it works with newer KDE SC releases. We'll +keep the kdepim-l10n split package to provide the translations for it. + +4. kdeenablefinal revisited +Since upstream doesn't seem to care about it much, plus it doesn't make much +sense now that there are many split tarballs, we decided to remove it the next +day after the meeting. + +5. phonon-xine removal +KDE upstream acknowledged that this is not maintained anymore. It's already +masked since 2011/12/01. Will be last rited and removed 15 days afterwards. + +6. Qt 4.8 +We expect no big issues with it. Kdenlive is the only known application that +does not build at the moment and will be patched. kde-base/kstyles-4.7.* needs +to be rebuilt after the upgrade, which we'll solve with a combination of +revbump/dependencies (otherwise KDE apps using oxygen style crash). + +7. Dropping RPATH from installed binaries +Postponed for next meeting, need more info from reavertm and/or hardened herd. + +8. To eselect Boost or not to eselect boost +No final decision was taken, discussion will be moved to -dev mailing list. + +9. Bugs +* dev-util/cmake picks always the latest boost. +* Fix in overlay since 13. Dec. Move to tree? +https://bugs.gentoo.org/show_bug.cgi?id=335108 +see 8. + +* cmake-utils.eclass PREFIX is not defined, any progress? +https://bugs.gentoo.org/show_bug.cgi?id=358059 +Postponed for next meeting + +* Remove hard dep on media-libs/phonon from kde-base/kdelibs +https://bugs.gentoo.org/show_bug.cgi?id=356681 +https://bugs.gentoo.org/show_bug.cgi?id=388041 +Although it is possible to build kdelibs against qt-phonon, it is not +recommended by upstream. Decision postponed for next meeting. + +* Eclass problem with handbook without LINGUAS. +https://bugs.gentoo.org/show_bug.cgi?id=372457 +Needs more analysis. Postponed. + +* MacOSX request for cmake-utils.eclass: Remove force of +* CMAKE_BUILD_WITH_INSTALL_RPATH=TRUE +https://bugs.gentoo.org/show_bug.cgi?id=398437 +That was a request by the Gentoo Prefix team, and is accepted + +* Revise the change "semantic-desktop? -> semantic-desktop=". Why was the +* change needed. +https://bugs.gentoo.org/show_bug.cgi?id=396491 +We had split opinions on this. Skipped for next meeting, as we need +reavertm's input on this. + +10. Open floor +Tampakrap will make a KDE SC 4.8 release party in Prague, more info coming soon. +Qt meeting on Thursday 26th Jan. +See you at fosdem :) diff --git a/meeting-logs/20120116.txt b/meeting-logs/20120116.txt new file mode 100644 index 0000000..aa6bc0d --- /dev/null +++ b/meeting-logs/20120116.txt @@ -0,0 +1,630 @@ + meeting starts now + roll call again please: alexxy / ABCD / jmbsvicetto / dilfridge / +johu / mschiff / Thev00d00 +-*- johu here + here +-*- alexxy here +-*- alexxy here again and again =D + here +-*- alexxy like quantum particle here and not here with non zero probability + first topic: elect new lead + nominations? +-*- johu nominates tampakrap + Do we really want to do it at this meeting? + raise your complain please + Nothing prevent us to anticipate the election, but that means +the 2011 term had only 11 months and that for the future the election will +happen before FOSDEM + we could vote whether we want to vote + or we could just vote by acclamation at fosdem :D + When dilfridge mentioned this topic at IRC, I got the impression +the point was to talk about the election, not to have it today + i dont care, maybe I just misunderstood + me dont care too + If no one has any reason to do it today, I'd have us wait 3 +weeks + lead is bad for your health anyway + ok, skipped for next meeting + you guys can pick Theo at FOSDEM and then we can do a mail tally +just to record it + hehe + he he + next topic +-*- alexxy seems like cannot participate fosdem this year + As in the past, I'll keep abstaining from kdepim issues :P + What shall we do with kdepim-4.4 (15 minutes) + * Discuss/vote: At the moment KDEpim-4.4 is still fully +functional, no known + regressions. Functionality of KDEpim-4.7 is slowly stabilizing, +with occasional + pains. Do we want to keep KDEpim-4.4 in the main tree? + dilfridge: yours + well... + I'm happy with how it is now + means, keep 4.4 for the moment, but also keep stabilizing newer +4.[78] versions + i dont care about kdepim 4.4 as long its work we can maintain it + right + at the moment it's zero work + to maintain it + it's just about giving people a choice + It's up to you, but if that's what you think, I see no reason to +change the status quo + if it's zero work, why remove it then? + a note from upstream they want to change migration to import ... + rumors + if this feature will come we can think about removing + hmm? + dilfridge: how about use kde-4.[78] kde-l10n for old kdepim-4.4? + you'll have to explain why... + to not keep separate kdepim-l10n + alexxy: this doesnt work as i know + it partly works, some translations are broken afterwards + alexxy: I don't think that'll work + alexxy: the l10n of kdepim-4.4 and kdepim-4.7 is not compatible + well then we should add kdepim-l10n to rdeps then + and its not much work to create the kdepim-l10n + ok =) + good + any additions? + then we should add kdepim-l10n to rdeps for all kdepim packages + final resolution: we keep it there, we'll have to create l10n +though + to make it pull kdepim-l10n + alexxy: wasn't there a kdepim-base package? + alexxy: that could be added there + sorry very late guys, reading backlog + Or did that become kdepimlibs? + kdepim-meta pulls kdepim-l10n with nls useflag + http://paste.pocoo.org/show/535829/ + same as kde-meta pulls kde-l10n with nls useflag + dilfridge: i have this flag + can we make that nls flag global in kde packages then? + and i dont have kdepim-l10n installed + ok + tampakrap: why make it a use flag for all packages? + i mean, global like semantic-desktop, put it in every kde package + alexxy: we'll sort this out + because i for example want only konsole and am an xfce user + tampakrap: I'd try to add it to a base package - like kdelibs +for non-pim packages + but i also want translations of konsole + or that, kdelibs is also acceptable + he he =) + +1 for tampakrap + alexxy: thanks :P + +1 from me + dilfridge / jmbsvicetto: nls in kdelibs, acceptable? + we could do the following: have the eclass add kde-l10n and if +needed kdepim-l10n to rdeps if any lingua is set + tampakrap: yes but that does not solve the kdepim-l10n problem + adding the rdep in the eclass is better + tampakrap: that's what I suggested :P + dilfridge: rdep via use flag + =) + =D + ok fine, add useflag to all kde packages: if "nls" is set, pull +*-l10n + dilfridge: Is there no base kdepim package that we could do the +same as in kdelibs? + no, unfortunately not + Please don't add it to all kde packages + Why do we want a use flag to all packages when all it does is +pull one dep? + kdepimlibs would be a candidate, but it's not really used by all +afaik + well + It would make sense to add it to all packages if the packages +tarballs add the l10n stuff and we could enable/disable for each package + kdepimlibs is separate from kdepim + err + sorry + libkdepim + yes, that works + Don't all kdepim packages depend on libkdepim? + so, kdelibs for kde-l10n and libkdepim for kdepim-l10n, +acceptable? + let's try that, yes. + s/add/had/ + tampakrap: yes + alexxy / johu ^^ + tampakrap: yep + good, i'll do it + excellent. + actually, i'll assign it to a non-dev to do it + :D + for practice + he he + for idella4? + anything else here? + he is very active + =) + no, i have a list of interested people, don't worry + he is indeed + =) + never mind + anything else here? + next topic: + 4. kdeenablefinal revisited (15 minutes) + * Discuss/vote: See last test run bug #353246. Should we +provide this + feature anymore? What is the purpose nowadays, in fact of +upstream keep + going split the huge packages (kde frameworks, kdepim)? +-*- johu had a kernel panic :-/ + dilfridge: ^^ yours again + not mine + no its mine + i want get rid of this mess + well, add your names next to the topic next time people + tampakrap: https://bugs.gentoo.org/353246 "[Tracker] +kdeenablefinal build failures"; Gentoo Linux, KDE; CONF; dilfridge:kde + tampakrap: last time we agreed to let it be as esigra was doing +all the work and we just left the bugs alone ;) + tampakrap: is it still works? + or do we still need this + upstream do not maintain it active + and it seams only one user uses it + most upstream devs don't even know about its existance + and i do not see the purpose + tampakrap: I still have no interest in it and won't shed any +tears if we drop it +-*- dilfridge does not care either way + but anyway, it doesn't make much sense that now most packages are +split in separate git repos + so lets kill it + =) + yes! + like we did for kdeprefix + =) + ok, do it + thanks +-*- Thev00d00 woops + hehe + anything else? +-*- dilfridge wants to close the bugs + ok will purge it tomorrow + and closes the bugs as well + next topic: + 5. phonon-xine removal (5 minutes) + * Discuss/vote: Upstream declared it as dead. Already masked +since 1. Dec + 2011. We have two other working and maintained backends. +Current open bugs + #359979, #397585. + who? + i + write your name next time or i'll come to germany and choke you + kill it =D + eofl + *rofl + is this still the latest? or are they resuming development since +xine-1.2 is out? + But yeah bitrot should be removed + dilfridge: I was going to ask about it + have a look at p.k.o + johu: did you ask any upstream devs about it? + dilfridge: the reason for the p. mask was that we thought it was +completely dead, but now it seems there are people working on t + it* + i'm not aware of anything official + tampakrap: it was announced as dead with kde 4.6.0 + johu: yes, but xine itself was considered to be dead. Now it +seems it might not be + jmbsvicetto: well, 3 commits in 12 months... + we have to ask in #phonon + I've moved to phonon-vlc a long time ago, so I have no direct +interest in xine/phonon-xine + dilfridge: hmm, that doesn't seem to active to me + * #phonon: Cannot join channel (+i) - you must be invited + in any case, I think we should make sure before we kill it + thats why we mask it + wait people + i'll ask apachelogger + if xine is still dead, then let's kill phonon-xine. Otherwise, +we can keep phonon-xine for a few more weeks / months to see if anything turns +out of it + i asked apacheloger, depending on the answer i get we'll act +accordingly + apacheloger = upstream phonon dev + acceptable? + yes + I also asked on #kde-multimedia, let's see + dilfridge: seems like #phonon is redirecting to #kde-multimedia + anything else here? + next: + 6. qt-4.8 (5 minutes) + * Short discussion about potential problems. + i updated to 4.8, everything seemed fine apart from kdenlive + no glitches, no compilation failures + ! + anyone here who updated with kde-4.7.x ? + i'll switch if it in tree + yes, i updated to qt 4.8 and kde 4.7.4 + I updated 3 machines, no problems at all with kde-4.8 beta/rc + kokeroulis: if you want to speak just do it + on Qt 4.8 there is an issue with the pointers + dilfridge: I'm just running ~arch these days + they are not killed + but updating a running kde-4.7.4 made all kde programs segfault in +oxygen style until I rebuilt kstyles + there is a post on plasma-devel ML + ok + let's see + johu: you could help us (qt) about it + wired should know better + and pesa + tampakrap: you can ask me to join the herd :P + i'll send you an invitation + kokeroulis: how serious is that issue? + and how much does it affect us? + I suggest we make two revs of kstyles-4.7, one requiring qt-4.7, +one requiring qt-4.8 ---> forces a rebuild, one problem solved + +1 + +1 + +1(external) + tampakrap: it seems a alot. Because some upstream devs has +mention that the KDE 4.8 should be shipped with Qt 4.8, so we will fix it +until the major upgrade of the binary distros. Otherwise all the binary distro +will ship KDE with this issue on their major version + dilfridge: how are you going to manage the revision numbers? + jmbsvicetto: by hand... -r0 & -r10 ... + I'll figure somethign out + it only requires talking to qt + just put one in overlay until 4.8 is out + exactly + and mask it together with qt-4.8 + dilfridge: sure, but I meant the numbers. So we can use 9 +revisions for kde-4.7. OK :) + kokeroulis: do you have a link to the ml post? + dilfridge: +http://mail.kde.org/pipermail/plasma-devel/2012-January/018493.html + ook +-*- dilfridge librarian mode + tampakrap: shall we move to RPATH ? + there are more about this conversation but the web archives have +some issue about that + dilfridge: i found it. +http://lists.kde.org/?t=132630064900003&r=1&w=2 + jmbsvicetto: dunno + anyway, is it so important to discuss it now? can we continue the +discussion in the mailing list or next meeting? +-*- wired is here :) + next meeting^ + tampakrap: wired: any plans to move qt-4.8 to the main tree (even +masked)? + wired: issues with qt 4.8? + dilfridge: unmasked, prolly sometime next week (near end), unless you +kde guys have any serious issues with it + heh + wired: no only kdenlive failed to build + that makes the priority a bit higher + mmmmmm qt-4.8-y goodness + wired: afaik no serious problems + it appeared to be a tiny fixable problem + at least I'm running it + I have not hit the problem yet that kokeroulis mentioned + wired: issues/tracker to help? + omg + it's starting + what? + tampakrap: hadn't had the time to do anything yet, no major issues +afaik, just opportunities to fix things :) + [21:55:23] ago * gentoo-x86/app-misc/strigi/ +(strigi-0.7.7.ebuild ChangeLog): + [21:55:23] Stable for amd64, wrt bug #396359 + [21:55:23] (Portage version: 2.1.10.41/cvs/Linux x86_64) + [21:55:26] CIA-4: https://bugs.gentoo.org/396359 "KDE +4.7.4 and dependencies stabilization"; Gentoo Linux, Keywording and +Stabilization; CONF; dilfridge:kde + https://bugs.gentoo.org/396359 "KDE 4.7.4 and dependencies +stabilization"; Gentoo Linux, Keywording and Stabilization; CONF; +dilfridge:kde + lololol + dilfridge: you will get a lot of highlights now + right. + wired: i have not used the Qt 4.8, so i don't know if there is +any big issue.... + ok good + kokeroulis: i've installed it on my two main workstations and it works +fine, however I don't have KDE anywhere ^) + anything else here or shall we move? + move + move it baby + wired: talk to me please before you bump qt + 7. Dropping RPATH from installed binaries (5 minutes) + * Short discussion- any objections to testing this in the +overlay eclasses and later + moving it to the main tree if it works? + dilfridge: sure, was planning to anyway :) + this is mine + we already removed the RPATH from qt libraries successfully + with no real benefit probablhy + ;p + it's possible because we add the qt library dir to /etc/ld.so.conf + whats the purpose? + well, all binaries built by qmake not also have no RPATH + dilfridge: I don't agree with dropping RPATH from binaries on +Linux + I'd say simplifying things + what can break? + we do not need two pointers to the lib dir + dilfridge: and by dropping it from the Qt eclass we were +supposely telling the linker to use what KDE defined - and not building +binaries with empty RPATH + dilfridge: just leave #gentoo-commits for a while :) + no, the plan was to get rid of the RPATH entirely + dilfridge: the issue is that binaries with empty RPATH have an +higher security sensitivity + err... why? + dilfridge: the reason we set the RPATH is to ensure that a user +is not able to "subvert" a legitimate binary by having it use libraries on a +exploited dir + dilfridge: if you have a binary A that uses library B and you +allow the user to specify the library dirs in which A should check for B, you +allow the user to add a "compromised" B library to a dir he controls and with +that you allow A to be compromised + dilfridge: at least that's my understanding. I might be wrong + LD_LIBRARY_PATH is ignored for setuid + and you could always copy a normal binary and set its RPATH + jmbsvicetto: with LDPATH and LD_LIBRARY_PATH i wonder if RPATH is +really preventing what you're talking about + wired: but LDPATH is controlled by root, right? + system files as well + dilfridge / wired: in any case, if you guys are not sure, I +think we should talk with the hardened team before dropping RPATH from +binaries + and with the prefix team probably :| + that has to happen before qt 48 goes to main tree + we should track down diego + I'll try to talk with Diego about it + ah, he's coming to fosdem + he's alive and kicking @twitter ^_^ + anything else? + I haven't caught him on jabber in a while :-\ + move? + move, decision postponed + 8. To eselect Boost or not to eselect boost (10 minutes) + We need to figure out what is actually the best desired +behaviour :| + who? + dev-zero + :] + newest info was that eselect goes away + see comments in the bug + we need to discuss this on the mailing list + but boost maintainers seem to prefer always building against +newest version + so lets talk to dev-zero and if this not help dev ml +-*- tampakrap is confused + ok now i get it + so move? + no move + at least not to tree + move to next topic i mean + yeah^ + * dev-util/cmake picks always the latest boost. + * Fix in overlay since 13. Dec. Move to tree? + https://bugs.gentoo.org/show_bug.cgi?id=335108 + I still think this should be moved to the gentoo-dev ml + tampakrap: this is the same^ + This is far more involving that just kde, and can affect any +package using cmake - like mysql-5.5 ;) + * cmake-utils.eclass PREFIX is not defined, any progress? + https://bugs.gentoo.org/show_bug.cgi?id=358059 + johu: raise the topic in the ml then? + tampakrap: seems that this my part + @boost + [22:14:00] dilfridge: pxine is dead + [22:14:09] no plans to revive + johu: the arguments from dev-zero about the use of boost should +also be discussed as boost should be compared to gcc, python, ruby, etc + dilfridge: so we can remove it + fine with me + johu: I think so, yes +-*- johu will do this + i will send a 10 days last rite + hey guys I am very sorry, I slept away two hours ago... :-/ + " * cmake-utils.eclass PREFIX is not defined, any progress?" + the last comment from this bug was that reavertm want to investigate, +but nothing happend + johu: use the usual 15 days, please + jmbsvicetto: its masked since start of dec + johu: otherwise someone will complain about it and we'll get in +an argument that will likely be less useful than just waiting 15 days ;) + johu: I know, but mask is not the same as last-rite and I +believe it's more productive to wait 5 more days than get in an argument for +not having followed policy + jmbsvicetto: fine with me + move to next? + see some lines above + the cmake PREFIX bug + johu: that one will require work with the prefix team, no? + jmbsvicetto: it would be good if reavertm were here + maybe he have infos about that + johu: That won't be easy as grobian is not a fan of cmake and it +does seem to have base flaws to support prefix + jmbsvicetto: not really afaik + that is not something related to "Gentoo prefix" + more like, cmake build magic + dilfridge: sorry, then I must be thinking at another bug + jmbsvicetto: yeah you think about the other cmake bug + the macosx request + ok, can we skip that then for next meeting? + reavertm is not here today + Ah, now I recall this bug + I still don't see what that patch actually fixes + That patch assumes prefix is defined and if it's empty it +doesn't add /usr + yes + I still think that patch is wrong + better still, that patch moves the definition of prefix to the +start and then does the same as it was doing before + so the only real change there is the following: + - SET (CMAKE_INSTALL_LIBDIR ${libdir} CACHE PATH +"Output directory for libraries") + + SET (CMAKE_INSTALL_LIBDIR ${PREFIX}/${libdir} +CACHE PATH "Output directory for libraries") + everything else is just a "format" change + ok + so the question is whether libdir should or should not be +relative to prefix + tampakrap: anyway, we can move to next bug :) + thank you + * Remove hard dep on media-libs/phonon from kde-base/kdelibs + https://bugs.gentoo.org/show_bug.cgi?id=356681 + https://bugs.gentoo.org/show_bug.cgi?id=388041 + Has upstream fixed the bug that made us add the hard dep? + no + iirc, knotify would stuck if we didn't had phonon in the system + phonon still requires at least a backend to work + and taking out phonon from kdelibs is not possible + so WONTFIX / UPSTREAM ? + so we have to postpone this to kde frameworks? + can you build kdelibs against qt-phonon? + so, kdelibs still needs phonon and we can't substitute it with +qt-phonon yet + no, we asked upstream already + dilfridge: and i think you did actually :) + I only asked if you need a backend to phonon + not if qt-phonon were a substitute to phonon + you are in the channel, ask them about it now then :) + I would like us to be able to drop the phonon dep, but upstream +doesn't allow us to present that choice to users :-\ + so resolution? + let's ask upstream first + but i'm 99,99% sure it's not possible + and if not, close it as UPSTREAM + ok move on + just did + * Eclass problem with handbook without LINGUAS. + https://bugs.gentoo.org/show_bug.cgi?id=372457 + idella4: do you have find something out? + that's an obscure one + ^ + ?? + about this bug? + yes + well you caught me on the hop + I seem to remember working it + I had it compile effectively without LINGUAS set from memory + but -handbook was causing the flaw + that must be around a week ago + maybe I left some good comment in the bug +-*- dilfridge gets a drink + ok, is there anything to discuss here? + no + * MacOSX request for cmake-utils.eclass: + Remove force of CMAKE_BUILD_WITH_INSTALL_RPATH=TRUE + https://bugs.gentoo.org/show_bug.cgi?id=398437 + -> can easily be done, because the FORCE affects only prefix +anyway + jmbsvicetto: here we go^ + jmbsvicetto: ^^ is that the one you confused earlier? + no reason to drop that hard requirement + yes + bah, sorry. I meant to say, no reason *not* to drop that hard +requirement + so let's do what prefix asked + thats sound reasonable + move on? + fine with me + we've reached kde-base/kcolorchooser by now +-*- johu is watching the chat monitor + * Revise the change "semantic-desktop? -> semantic-desktop=". + Why was the change needed. + https://bugs.gentoo.org/show_bug.cgi?id=396491 + dilfridge: if you want, we can highlight you a bit on +#gentoo-kde ;) + yeah well reavertm is still not here + hehe + i am fine with dropping the '=' + so, I never liked that semantic-desktop? -> semantic-desktop= +move, but it was done with the argument that we were getting strange and +unexplicable bug reports and that it was causing issues in the upstream bug +tracker + I dont see why we should allow "?" + because nobody gains from it + +1 @ dilfridge + once you have kdelibs with semantic-desktop, you have all the +dependencies + dilfridge: As I don't want semantic-desktop at all, being able +to just enable it where I'm forced, would be a plus. But I think we should try +to be consistent + but dont you need kdelibs[semantic-desktop] for any +semantic-desktop enabled package? /me confused + can we skip it for next meeting? + sure + yawn + good + OPEN FLOOR + there were real reasons that we agreed with to have +semantic-desktop= back then (we as in the kde team, even if I disagreed) + dilfridge: ? allows that + yes + dilfridge: the point with = was that I would have to had every +kde package built with semantic-desktop if just a single one required +semantic-desktop + scarabeus was the one to push that decision + tampakrap: talk to scarabeus in office about that + tampakrap: I feel like were starting to have a "memory issue" in +the KDE team. We got enough new people recently that some of the old issues +are being raised again as the team (or a substantial part of the team) doesn't +know the history behind them + jmbsvicetto: i believe that is reasonable though, things change, +new decisions are taken + tampakrap: that means we should probably start thinking about +providing better documentation for decisions so that people know sometime +later whey they were done + technically it should be in the meeting logs + i agree with the documentation, and it is entirely my fault + i'll do my best from now on though + open floor: cleaning up herd? + again? + tampakrap: I don't think it's a bad thing. I'm just stating that +I've noticed it and that we should perhaps rethink a few things in how we +operate ;) + i did that in less than a year :( + jmbsvicetto: +1 + !herd kde + (kde) abcd, alexxy, dilfridge, jmbsvicetto, johu, mschiff, +patrick, reavertm, spatz, tampakrap, thev00d00 + spatz? + patrick? + tampakrap: Hey, at this point in time I'm the "oldest" kde dev +around ;) + patrick is special + yes, let's kick jmbsvicetto out + meow + :D + tampakrap: hehe, "special" ;) + tampakrap: I've told you at this point I only care about amarok +and related packages :P + johu: i'll talk to spatz, ok + can somebody make me wise? +-*- jmbsvicetto blesses johu with wiseness + thx + :) + Patrick I suspect is soon to wake up + another topic for open floor: + !time bonsaikitten + dilfridge: I don't know where bonsaikitten is, (s)he should use +!time set / to let me know + idella4: I can finally make fun of Patrick at some hours without +risking him replying to me ;) + China + when the Cat's away + I'm doing a kde release party here in prague a week after fosdem, +probably at suse office, you are all invited + idella4: He used to be more time online than me :) + he is on-line alot + see he is in my timezone + tampakrap: It seems I'm too "heavy" to catch the fiber optic to +your office :P + tampakrap: travelling already that weekend, sorry + tampakrap: otherwise I would take your invitation and go check +the "blankets" ;) + you loose + oldies + anyway, meeting closed + i'll do the summary, someone upload the log please diff --git a/meeting-logs/20120322-summary.txt b/meeting-logs/20120322-summary.txt new file mode 100644 index 0000000..478887b --- /dev/null +++ b/meeting-logs/20120322-summary.txt @@ -0,0 +1,76 @@ +1. Roll call +alexxy, dilfridge, johu, mschiff, scarabeus, tampakrap + +2. Electing a new team leader + +nominees: +Accepted: dilfridge, johu +Refused: tampakrap, scarabeus + +results: +johu -> dilfridge +dilfridge -> johu +tampakrap -> dilfridge +alexxy -> dilfridge +mschiff -> dilfridge +scarabeus -> dilfridge +---------------------- +dilfridge:5 - johu:1 +---------------------- +dilfridge is the new KDE team leader with the majority of votes. +Congratulations!!! + +3. Dropping RPATH from installed binaries +Add a RPATH entry for every library dir that is not in the system library +directories in ld.conf are not automatically considered as system library +dirs, but only some static list of dirs. +Everyone agreed on RPATH removal. We will introduce a patch with KDE SC 4.8.2 +to remove the RPATH and move it to the main tree. + +4. Bugs +* Remove hard dep on media-libs/phonon from kde-base/kdelibs +https://bugs.gentoo.org/show_bug.cgi?id=356681 +https://bugs.gentoo.org/show_bug.cgi?id=388041 +Upstream says "technically you can replace phonon with qt-phonon, but that's +just stupid because you lose functionality". Another argument against it, is +that qt-phonon will be removed with qt5. We wont fix the bug and keep phonon as +hard dep. johu will take care of the bug after meeting summary is available. + +* Eclass problem with handbook without LINGUAS. +https://bugs.gentoo.org/show_bug.cgi?id=372457 +The handbook eclass code is pretty confusing for all in meeting present +members. It was written by reavertm. We decided that we will mail reveartm to +fix handbook eclass code, because he has the most knowledge in it. dilfridge +will take care of contacting him, it's his first lead task. + +* Revise the change "semantic-desktop? -> semantic-desktop=". +https://bugs.gentoo.org/show_bug.cgi?id=396491 +Some packages rely on semantic-desktop capabilities in other ones. tampakrap +is volunteers to take care of the bug. + +5. Open floor +* KDE 4.8 stabilization +KWin does not build anymore without opengl support. kde-base/kmail-4.8.1 +crashes, but upstream patch can be backported. KDE SC 4.8.1 has tons of +bugfixes, compared to to 4.8.0. The majority votes for KDE 4.8.1 as stable +candidate. johu will prepare stabilization. + +* Test failures +creffett brought up dbus-related test failures. johu recommended to get +virtual-dbus eclass running. dilfridge suggested if one or two test fails +or restrict. The problems with virtual-dbus is that you can't run bash +commands in it's environment. creffett will be responsible for this. + +* New members +Welcome to three new members of the project: creffett, kensington and +dastergon. They are in the process to become gentoo developer and mentored by +tampakrap. creffett and kensington have already open 'new developer' bug. +dastergon doesn't have an open bug yet. + +* Comeback +scarabeus re-joined KDE herd. Welcome back!!! + +* Reduced work time +mschiff mentioned that he will not have much time for the KDE herd due to +real life priorities, he will be back in may. tampakrap will spent most of his +time for gentoo infra team. diff --git a/meeting-logs/20120322.txt b/meeting-logs/20120322.txt new file mode 100644 index 0000000..63e1ef7 --- /dev/null +++ b/meeting-logs/20120322.txt @@ -0,0 +1,282 @@ + so let the party begin + 1. Roll call +-*- tampakrap here + ABCD, alexxy, bonsaikitten, dilfridge, jmbsvicetto, mschiff, scarabeus, +tampakrap, Thev00d00 +-*- dilfridge here +-*- alexxy +1 +-*- mschiff here +-*- johu of course too + yo + ok lets move on + 2. Electing a new team leader +-*- johu nominates tampakrap + I decline + other proposals? + yes, dilfridge + why not + scarabeus are you interested? + he he + may be scarebeus? + johu: are you interested? + =D + are you guys insane + why the hell i would like to be lead :) + i would have to start actually care + scarabeus: because you are veteran + scarabeus: didnt you care? or you turned to m$ win camp? +-*- tampakrap nominates johu and dilfridge + ok lets vote if no other proposals show up + scarabeus: so you agree for nomination? + nop not accepting :) + let someone new do it +-*- johu votes for dilfridge +-*- dilfridge votes for johu + hmm +-*- creffett stays out of this one + cycle dependency? + :D + maybe we could recompile one with USE="-doc" to fix it +-*- tampakrap votes for dilfridge + +1 for dilfridge + +1 dilfridge + dilfridge++ + ok 5:1 + bless the new lead + (nothing against johu i just want to see dilfridge enjoy my post +:P) + :P + the post is mine + thx tampakrap for your work as lead + thanks guys + you are welcome + congrats dilfridge!! + yeah thanks tampakrap +-*- tampakrap kicks dilfridge + ow + =P + 3. Dropping RPATH from installed binaries (5 minutes) + * Short discussion- any objections to testing this in the overlay +eclasses and later + moving it to the main tree if it works? + ghmm + may it hert someone? + dropped rpath should work as is, so do it + +1 + doesn't debian disable it too + I dont see any problems + hmmm + +1! then + lets give the removal a try from me + it's basically a patch in kdelibs afaik + to one of the cmake files + I can prepare that, I've looked into the thing before + (but have not tested the result before) + why was it introduced? + it's default in the kde buildsystem + and imho a bug in cmake + i think it was here for sloted kde versions + the logic is: + * add a RPATH entry for every library dir that is not in the +system library directories * + the cmake bug, in my opinion, is: + * directories in ld.conf are not automatically considered as +system library dirs, but only some static list of dirs * + our qt4 is in a "non-default path", usr/lib(64)/qt4 + so cmake adds it to the RPATH + but that's not needed because we add it already to ld.conf with an +environment file + s/ld.conf/ld.so.conf/ + any objectiosn from the crowd? + fine by me + kill it =D + ok we move on + we can introduce the patch with 4.8.2 and move it to the main tree +then + 4. Bugs (30 minutes) + * Remove hard dep on media-libs/phonon from kde-base/kdelibs + https://bugs.gentoo.org/show_bug.cgi?id=356681 + https://bugs.gentoo.org/show_bug.cgi?id=388041 + dilfridge: yes its next week + ok I'll make the patch for 481, it should apply just the same to +482 + qt-phonon will be removed with qt5... + or should it bee || x11-libs/qt-phonon ? + upstream says "technically you can replace phonon with qt-phonon, +but that's just stupid because you lose functionality" + (kde upstream) + reasonable^ + so maybe ewarn if qt-phonon is there but accept it + we should go the other way + i think we get into a lot of trouble with not much gain + remove qt-phonon if desired + but not the other way around + exactly, I believe we should keep phonon as is +-*- johu votes for as is +-*- dilfridge votes for as is and close bug as wontfix + I mean if someone knows what he does and *wants* qt-phonon? + I wonder why Markos added that bug... + find me one first + alexxy: your opinion? + otoh if it will be dropped soon... ok +1 for keep it as is + i dont think its good idea + we should keep it to make kdelibs functional + ok i will take of the bug after meeting summary + * Eclass problem with handbook without LINGUAS. + https://bugs.gentoo.org/show_bug.cgi?id=372457 + anybody had a deeper look in to this? + no... it's pretty confusing code + the handbook code is quite magic :) + you need reavertm to explain that + we need reavertm in every team meeting :D + skip for next meeting? mail reavertm? + dilfridge: your first lead task + hehe + I'll try + next bug + * Revise the change "semantic-desktop? -> semantic-desktop=". + Why was the change needed. + https://bugs.gentoo.org/show_bug.cgi?id=396491 + dilfridge: Mission directive for you: Find reavertm and make him fix +handbook =D + was before my time + scarabeus: ^ that's for you + johu: the goal was to enforce it everywhere + it is ment to be global useflag only + so set in make.conf or not set at all + some packages rely on semantic-desktop capablities in other ones + and this was easiest way how to ensure that user wont fuckup + and this is valid today + I approve that change + it should still be + ok tampakrap you are the volunteer for that bug + ack + 5. Open floor (15 minutes) + kwin does not build anymore without opengl support (or at least +gles) + yes + tampakrap: so what with the stabilisation + fwiw, I'll become upstream of kportagetray and hopefully +plasma-emergelog, I'll work on those next week and probably will release stuff + scarabeus: i would suggest 4.8.2 + dMaggot: cool + what stabilization? + ah, kde sc + what's still bad in 481? + I would suggest 4.8.1 asap, it has tons of bugfixes + many crashes as well + I would stabilize it asap imho + I mean I'm running it and it seems to work finr + 4.8.2 has some important fixes too + fine + each version have important fixes + the keywords not restored so far + question is: are those regressions since 4.7 + definitely not + scarabeus: no =D + scarabeus: in kmail, I think + it only features + and keywords is johu's job :D + no, kmail got much more stable again + tampakrap: and you have the query for the bugs :) + kmail works with lkml imap dir + kmail 4.8.1 is already heaven comapred with 4.7.4 + with 300k+ mails + trust me i am runnig stable kde now + and sometimes it does interesting stuff + don't trust him, he is running opensuse + scarabeus: stable?! + lol + see my stabling of akonadi-server :) + anyway + to solve some bugs + https://bugs.gentoo.org/show_bug.cgi?id=407709 + ahh opensuse =D +-*- tampakrap votes for 4.8.1 with passion + its not stable =D +-*- dilfridge votes for 4.8.1 +-*- johu votes for 4.8.2 + johu: see this is regression, if 4.8.1 goes stable just shovel the +patch to 4.8.1 + alexxy: i run stable gentoo , hardened stable gentoo + +1 for 4.8.1 + Linux arcarius 3.2.2-hardened-r1 #8 SMP Thu Mar 22 12:23:02 CET +2012 x86_64 Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz GenuineIntel GNU/Linux + scarabeus: hardened desktop? + alexxy: yep, same as dilfridge +-*- johu will prepare stabilisation + hmmm + i may try it on laptop =D + johu: lemme know when you have list, i can showel it to my desktop +and test + though I dont use hardened kernel yet... but I'll change that soon + scarabeus: did you enabled grsec? or you use only pax? + any other topics in the open floor? + am I allowed to bring one up? + sure + (if it hasn't been discussed at a meeting previously), what to do +about all of the dbus-related test failures? + sigh + its open floor so anyone allowed + ignore them? + because with a lot of them, we're patching out tests to the point +where the test suites are pointless + honestly I dont know what to do there + alexxy: both + many of the testsuites are not even used by upstream devs + my personal suggestion would be: + which is really ssad + the best solution for the test failures woold be to get virtual-dbus +eclass running + * if only one test / two tests of many fails, disable with patch + I was looking at that + * otherwise restrict + if you can make it work, that would be great + but I've given up hope a bit + also, + the problem with virtual-dbus is that we'd have to dig into the kde +eclasses + because you can't run a bash command in the virtual-dbus +environment + dbus is a communication tool, so the tests need something to talk +to (i.e. a kde desktop environment) + which means the tests may want to start up an entire desktop +environment in the virtual session + :| + I also have a quick topic when you finish with the dbus tests + I haven't got anything else on the matter + creffett: if you get this to work, great... + OK my topic: + dilfridge: I'll keep poking, no promises :P + tampakrap: go ahead + welcome new members: creffett (he has open bug), kensington ( he +has open bug as well), dastergon (he doesn't have open bug yet, but he has the +priviledge to be my friend) + :) + and welcome to scarabeus + another ugly greek :P + :) welcome! +-*- creffett waves + welcome ;) +-*- mschiff has another little one: I am a bit short of time working in kde +herd because we are building our new home here... but this will calm down in +May, so I hope to have more time again then... + scarabeus: the greek community is growing fast !! + yeah, now that I left :( + any other topics? + another short one + I'm going to stop doing kde things and spend 99% of my gentoo time +in infra +-*- dilfridge sets linewidth in tampakrap's irc client to 20chars + since mentees are shortened out and I don't have the leader +position any more + sad + :*{ + hey we'll miss you! + not really, you don't need me + scarabeus: kick him from me in the office + :D + 3 + 2 + 1 + meeting is over diff --git a/meeting-logs/20120419-summary.txt b/meeting-logs/20120419-summary.txt new file mode 100644 index 0000000..267ca5b --- /dev/null +++ b/meeting-logs/20120419-summary.txt @@ -0,0 +1,41 @@ +1. Roll call +alexxy, dilfridge, kensington, johu, scarabeus, tampakrap, thev00d00 + +2. KDE SC 4.8.2 stabilization after it is 30 days in tree? +KDE SC 4.8.1 is stable for amd64 and x86, ppc is still pending. We decided to +skip the stabilization for KDE SC 4.8.2 to reduce the work load for the arch +teams. Scarabeus suggested that we can stabilize other kde herd related +packages in the meantime. No objections, so we will walk over the packages, +search for candidates and file stable bug requests. + +3. Calligra 2.4.0 stabilization after it is 30 days in tree? +We are getting more and more bugs related to koffice. Calligra is the +successor of koffice. Qt 4.8.1 stabilization will be needed before, as a build +requirement for calligra. No arguments or objections against stabilization, +which will end up in replacement of koffice with the normal last rite +procedure. + +4. Do we want to stabilize KDE SC 4.9.x on arm? +The number of arm gadgets will go up more and more, while ppc machines are +falling apart. KDE SC should work on arm. Sabayon would benefit by +stabilization too. We will need Qt 4.8.x stable on arm before. Unfortunately +none of the kde herd members have the hardware to test it. So we will need +volunteers/testers for that. Additionally we could think about packaging +plasma-active too. Dilfridge will ask arm herd about the idea, if they like +it, he will blog about it. + +5. Remove tar command ewarns in eclasses? +They are useless and anoying nowadays. Scarabeus acknowledged that they can be +removed. + +6. Open bugs +* Bug #358059 - cmake-utils.eclass PREFIX is not defined +Scarabeus acknowledged that the patch is correct. We will test it in kde +overlay first. + +* Bug #372457 - doc dir is not correctly disabled by kde4-functions.eclass if +NOT kde-base and LINGUAS is unset +Chris Reffet found a solution. We will test it in kde overlay first. + +7. Open floor +* Tampakrap mentioned that SLES will have KDE 4.8 soon. diff --git a/meeting-logs/20120419.txt b/meeting-logs/20120419.txt new file mode 100644 index 0000000..a8b0471 --- /dev/null +++ b/meeting-logs/20120419.txt @@ -0,0 +1,169 @@ + ok that's 5min warning... so let's do quick roll call + i didnt tryed ppc + =) + !herd kde + (kde) abcd, alexxy, dilfridge, jmbsvicetto, johu, mschiff, patrick, reavertm, scarabeus, tampakrap, thev00d00 + arm and mips yes + roll call please :) + here + here + here + ay for the captain + :P +-*- kensington waves +-*- alexxy hides in superstrings continium =d + oh dear + p-branes + lol + ok... since we dont actually have much agenda... + 1) what do we do with kde-4.8.2? file stablerequest as soon as the 30days are done? + too much load for the arch teams, I'd suggest to skip one version + Personally I think we may as well wait for .3 + ok + Is it still due May 1st? + I'm fine with both + yes + so next stabilization would be 483 end of may + and we can maybe add some patches to single packages if there are super-ugly bugs + ok + anyone against "next is 483"? +-*- johu is here + i would like to ask you to open bugs for misc apps + they are often working in testing and completely weird in stable + so please jump over our herd packages and fill stablereqs where fit + sounds reasonable + scarabeus: volunteer? + how is euscan doing with the kde packages? + working good + euscan is great + but iksaf still didnt include my request to differ between versions in testing and in stable + eg green only when latest is in stable + otherwise orange + get it + good idea, no volunteer so far, we'll all have to do a bit each + dilfridge: i do it every week on mo/tue + but i cheat + i dont open bugs + :D + i ahve stable boxes + so i stable right away + you can automate that + ok + there is one more question from me, and then I have all off my heart: + 3) is anyone against a stablereq for calligra-2.4.0 ? (after the magic 30days) + no bug reports so far + NO please do it + lets get rid of the koffice foo + and it would be awesome to get rid of koffce + is it dead? + koffice ist kaput + there were some discussions to move it to SC + it is life, Jim, but not as we know it... + did you read in the last year any news update in koffice? + more like zombie + even the last blog posit of tzander was a year ago + tampakrap: that suggestion led to a lot of opposition, it was seen as some scheme to give koffice a more official status than calligra + but I stopped following the fuss at some point + ok seems like nobody opposes + anyone else has anything else? + yes kde481 is table + :) + hehe + at least for amd64, x86 + yeah pretty nice chair it is + 4) arm stable in kde 49x? + is qt stable in arm? + 472 + 474 in porgress + johu: I actually like the idea, but I dont have an arm machine that could run kde decently + 48x not decided yet + hm ok nvm + I mean, the number of arm gadgets will go up more and more + while ppc machines are falling apart + we can do this for sabayon folks + we could also think about packaging plasma-active + how about asking in a blog post for volunteers? + i dont see sane to run gentoo on arm machines right of the box now :) + scarabeus: at least kde runs pretty well, people say (with hw graphics accel) + tampakrap: what should the volunteers do exactly? + arch testing + obviously :) + ok + dilfridge: do you got any answer from reavertm abouy the open issues/questions? + yeah well it's an idea + johu: no + hm :-/ + tampakrap: I'll ask the arm guys about this, if they like the idea I'll blog + ah yes I remember one more thing + what you guys want from Maciej? + 5) the ewarns about the tar commands, they are completely useless even for devs. can they go away again? + ask reavertm :) + :) + they can go away + scarabeus: most questions are eclass related + :D + poor you :P + but wait were there someone else with me working on that + i know, JORGE! + bug 358059 + dilfridge: https://bugs.gentoo.org/358059 "cmake-utils.eclass PREFIX is not defined"; Gentoo Linux, Eclasses and Profiles; CONF; meka:kde + that is actually the only one left + all the rest is imho done + linguas + or i missed something? + kensington has found the problem I think + we just need to doublecheck the solution + dilfridge: ack on the patch + ok + it actually fixes stuff i wrote there in first place :D + it was creffett + ok sorry + scarabeus: I'll try to understand it myself over the weekend, and then... + |:] + basically now the prefix is defined on 5 places + this defines it on one place + and then just uses such var + so it is correct + only weird line is this one: + -SET (CMAKE_INSTALL_LIBDIR ${libdir} CACHE PATH "Output directory for libraries") + +SET (CMAKE_INSTALL_LIBDIR ${PREFIX}/${libdir} CACHE PATH "Output directory for libraries") + "but when i think of it ; it looks correct + we can always test in overlay + nah rest of the patch is harmless + just check one package if it puts shit into /usr/usr/lib64 + and if not it is correct + hehe + ok + anything else to discuss? + 6) open floor + SLED will have kde4.8 "soon" + cough + cough + ok + that means they consider kdepim-4.8 stable enough? + isn't it? :) + on my work desktop it's ok + tampakrap: i dont think there is plan to build kdepim too :P + it's built already + the obs repo is linked from the opensuse 12.1 one + suse ich will sie nicht nimm duse + lol + it + seems + like + we + can + close + the + meeting? + next time i have to organize the meeting it seems + :P + hehe thanks in advance! + no, give it to a new guy + who writes summary? + whoever asks first :P + go away + ok I'll do it + cheers & thanks everyone + thx for chairing + byes diff --git a/meeting-logs/20120517-summary.txt b/meeting-logs/20120517-summary.txt new file mode 100644 index 0000000..463ee86 --- /dev/null +++ b/meeting-logs/20120517-summary.txt @@ -0,0 +1,73 @@ +1. Roll call +alexxy, creffett, dilfridge, johu, kensington, reavertm + +Welcome new developers kensington and creffett. Thanks to JoseJX for +participating as member of the powerpc team. + +2. Add LINGUAS support to cmake-utils.eclass +Agreed to add a loop like that in qt4-r2.eclass to reduce ebuild code. It +expands the contents of LANGS to IUSE as linguas_*. A generic linguas handling +is not planed yet. + +3. Live KDE ebuilds have tests restricted +The usefulness of tests on live ebuilds was brought into question, since there +are enough problems with tests on normal releases. Agreed to enable tests when +I_KNOW_WHAT_I_AM_DOING is set. + +4. KDE 4.8 stabilization and PowerPC +The stabilization and keywording was pending up to the team meeting date, +because of gcc47 as requirement to restore the keywords on ppc/ppc64. This +blocker was mistaken added. PowerPC needs just Qt 4.8.1 to keyword KDE 4.8. +So there are no reasons the discuss to drop the ppc support from kde-base. +We never stabilized a KDE version on ppc64, because ppc64 has problems with +the size of the table of contents for ELF function calls that will be fixed +with gcc 4.7. johu ask for voting on dropping ppc64 at all. No real +majority/opinions about it. JoseJX prefers that ~ppc64 not be dropped from KDE +keywords. Agreed that JoseJX would keyword ~ppc, and if there were no problems +would also keyword ~ppc64, topic will be revisited. + +5. Bugs +* Trying to change full name in KDE System Settings results in error or crash +https://bugs.gentoo.org/380899 +There is an existing workaround to disable the change full name functionality. +kensington will talk to upstream about the issue, and if there is no good +response in 2 weeks' time, we will apply the workaround. + +* app-cdr/k3b: use media-libs/musicbrainz:3 instead of :1 +https://bugs.gentoo.org/410347 +Agreed that musicbrainz:1 is obsolete and that k3b does not appear to actually +use musicbrainz even when enabled. Dependency on musicbrainz will be dropped. + +* dev-util/cmake: FindPythonLibs behaviour broken by Gentoo patches +https://bugs.gentoo.org/405181 +Dilfridge said that we should remove the patches and use command-line defines +to force specific python versions, agreed to test that. + +* kde-misc/networkmanagement-0.9.0 and kde-misc/networkmanagement-0.8_p20110714 +wrong doc dir specified - https://bugs.gentoo.org/410139 +Nobody has been able to reproduce the bug. Dilfridge suggested asking for more +information and will investigate further. + +* kde-misc/interceptor - KDE4 Plasmoid - intercept (catch) the log info from +the syslog - https://bugs.gentoo.org/383733 +creffett suggested dropping this request because it requires too many big +configuration changes for a plasmoid. Agreed to remove kde from CC list and +suggest taking the ebuild to sunrise. + +* dev-util/cmake-2.8.6-r4 - stop Xvfb after failed test phase +https://bugs.gentoo.org/406353 +Need input from gentoo-portage team about what phase could be used to clean up +xvfb after test failures. Kensington mentioned that the same issue will affect +virtualdbus. + +6. Open Floor +* KDE 4.9 Beta +Dilfridge reported that KDE 4.9 beta is coming out soon. + +* Groupdav calendar bug in kdepim-runtime +Discussed whether to stabilize kdepim-runtime base version or -r2, which has a +possible fix for https://bugs.gentoo.org/show_bug.cgi?id=415401 but no +positive feedback. Agreed to go with -r2. + +* creffett away +creffett will be out for a month on a trip with little internet access. diff --git a/meeting-logs/20120517.txt b/meeting-logs/20120517.txt new file mode 100644 index 0000000..6a87757 --- /dev/null +++ b/meeting-logs/20120517.txt @@ -0,0 +1,324 @@ + 1. roll call + !herd kde + (kde) abcd, alexxy, creffett, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, tampakrap, thev00d00 +-*- johu is here +-*- dilfridge here +-*- creffett is somewhere around here +-*- kensington of course + 2. Add LINGUAS support to cmake-utils.eclass + kensington: looks like itterative process which should coverage + hehe +-*- alexxy here + :P + err there's one more part for 1. :) + first of all a big welcome for our new team members kensington and creffet :D +-*- creffett waves +-*- johu applaudss + ok that was it from me :D + kensington: what would your linguas implementation cover? + kensington, how did you forget to add "make everyone congratulate us" to the agenda? + creffett: I wrote that before we finished recruiting, so that's my excuse :P + basically, just copy straight out of qt4-r2, so need to stick an ugly loop adding linguas_X in packages that need them + *no need + for x in ${LANGS}; do + IUSE+=" linguas_${x}" + done + hm ok would reduce some ebuild code + any objectsion to that? + is there an standard handling for the linguas handling planed? + no idea + it would be nice, but I do not know of any + but the code looks everywhere the same + just use a "safely unique" variable name for x and unset it afterwards again + do we need to send to -dev about it too? + i have no objections + no objections + no objections... hic... + 3. Live KDE ebuilds are unconditionally test restricted + btw may be we can write generic linguas.eclass? + kensington: but gentoo-dev can not hurt + alexxy: there was already a discussion about that on -dev?! + alexxy: nice idea but that needs to be bikeshedded on -dev + generic eclass would be nice, but I don't know if there's much beyond those three lines that are portable between build systems / packages ? + johu: yep it was about a year ago + probably not. + ah ok, dont remember + re 3: I say leave them as restricted, because we have enough trouble already with the official release tests + well... anyway. I think whoever runs live kde with tests seriously needs some disruptions. + :D + but, from a practical point of view, creffett is right + he he + i use 9999 on my laptop + but i didnt enabled tests =D + i would say enable them with the magic var! + its not a bug deal + I_REALLY_REALLY_KNOW_WHAT_I_AM_DOING + big + haha + dilfridge: I like that idea :P + ynauv + yet not another useless variable^ + how about we just add it to the usual I_KNOW_WHAT_I_AM_DOING ? + who sets this should be able to handle the fallout + test enable on I_KNOW_WHAT_I_AM_DOING + dilfridge: better to use YEP_I_REALY_REALY_SURE_THAT_I_WANT_BIG_HEADACHE + ... AND_I_PROMISE_TO_NEVER_EVER_FILE_BUGS + can we become serious? :) + Yessir. :) + I_KNOW_WHAT_I_AM_DOING___SERIOUSLY + test enable on I_KNOW_WHAT_I_AM_DOING + agreed + I agree with johu + +1 + sounds fine, +1 + reavertm nice to see you sir + :) + 4. KDE 4.8 stabilization and powerpc + ok thats my topic + i added it because gcc47 was dep to keyword it + elaborate on it please :) + but JoseJX told me some hours ago that he will keyword it tonight + it was a mistake with gcc47 + cool + but they need qt 481 + i think b) can be seen as obsolote + Hey + ok sounds good + I'm the PowerPC rep I guess + hey JoseJX :) + but we should discuss if ppc64 make sense + I'd really like to not drop keywords if possible + JoseJX: whats your opinion about that? + KDE still runs well on my G5 + I can see the argument for dropping ppc64 from stable, but keeping unstable, since we don't really have the manpower to handle it. + There's also the fact that most of our users are not running ppc64, even on ppc64 machines + Most are set up with a 32bit userland (the ppc keyword) + I think that already happened some time ago, at the moment we only have stable "amd64 ppc x86" + scarabeus said that ppc64 are serve machines + dilfridge: I think that's reasonable + but if the gcc-4.7 problem is gone, we should try to keep things as they are (ppc ~ppc64) + That's what I'm aiming for now + ppc/~ppc are definitely fine + but makes ppc64 realy sense? + I'm still working on testing ~ppc64 + thats the first question we should find a answer + I do know that we might have some TOC issues, which might make this all moot anyway on ppc64 + But those will be fixed when gcc-4.7/4.8 is ready + is there any ~1line summary for that? /me does not have a clue + I'll try to explain + ELF on ppc builds tables of function calls, but on ppc64, the tables get too big and the TOC runs out of space because the pointers are 2x bigger. + but gcc-4.7 stable will hapen maybe 2013... + Basically linking > 32MB (I think that's the size) doesn't work on ppc64 because the jumps are too big + We can work around it with --minimal-toc and that's what we have been doing. + That's the short version + JoseJX: are there lot of desktop systems with ppc64? + ok... what's the problem with (for kde) global --minimal-toc ? + dilfridge: None that I'm aware, but ranger would be the better one to ask. + ok + johu: Honestly? No. + johu: I run it on my G5, but I'm sure I'm an edge case + ok, makes no sense to me to keep ppc64 then + johu: but ~ppc64 is not really a problem... + I think that's where I'm at too + anyone else has an opinion? + I agree there's no need for stable keywords, but if possible, I'd like to keep the unstable ones. + ok please vote on keep ~ppc64: + -1 + +1 + 0 + 0 + or keep ~ppc64 + i dont currently have any ppc hw + 0 + so i cannot test + meh + seems we cant find a decision here so lets keep it... + Well, how about this. If everything is working when I do the ~ppc keywording later today, I'll also mark ~ppc64. If not, I'll let it drop. + +1 + +1 + i will raise this issue again for sure ;) + +1 + =D + why not, +1 + johu: That's fair. I don't see what dropping unstable keywords helps with though? + JoseJX: because server systems != desktop systems + I've tried already to build a ppc/ppc64 qemu chroot but right now this fails because of a qemu-static bug + and KDE is for sure a desktop/tablet env + johu: Only new ppc64 machines are server systems, but in the past, we had the PS3/G5 both which definitely were not server systems +-*- dilfridge thinks mips tablet and runs fast... + did someone say mips? :D +-*- creffett hands dilfridge a cobalt raq2 + keywords all the archs! + JoseJX: ok i think you can do your job tonight ;) + JoseJX: and big thanks for that + Okay! Thanks guys. I have to get back to work, but I'll probably be doing the keywording around midnight EST. + Just for a heads up! + JoseJX: if the work load is to big to stable 483 you can wait for 484 + johu: No worries + When is 4.8.4 expected? + Would it be better for us to wait? + 484 is tagged end may + it's always one month later + In either case, we need to go forward with the unstable keywords first, so that won't change + so we will start with stable mid june + makes sense + Okay, we'll probably target 4.8.4 for stable on ppc then, figure one month in unstable gets us to June anyway + yes + As long as that's fine with you guys + its totally finee + sure + Great! + :) + JoseJX: thanks for being here + kensington: procede pls + No worries, later! + 5. Bugs + bug #380899 + kensington: https://bugs.gentoo.org/380899 "Trying to change full name in KDE System Settings results in error or crash"; Gentoo Linux, KDE; UNCO; gentoobugzilla:kde + there is a workaround that disables that feature from ubuntu, do we want to apply that? (looks like upstream doesn't care about the bug) + kensington: i saw a other solution, fallback to nickname on reviewboard + kensington: you have good connections to upstream try to talk to them + johu: if we are thinking of the same patch, it didn't work + still crashed + hmm + seems like the feature does not work, why not disable it + I suspect once the code is fixed our patch will not apply anymore and we will notice + https://git.reviewboard.kde.org/r/104965/ + kensington: this one?^ + johu: no, I was thinking of a different one, sorry + does that really fix the same problem? + i am not realy sure +-*- dilfridge confused + I don't think so, the issue from the bug is systemsettings hangs because it can't talk with chfn properly + i would suggest try to talk to upstream and if you get no good answer or proper response disable it + +1 + say 2 weeks time limit + ok who's going to do it? + ok I will + ok next pls + bug #410347 + kensington: https://bugs.gentoo.org/410347 "app-cdr/k3b: use media-libs/musicbrainz:3 instead of :1"; Gentoo Linux, Applications; CONF; pacho:kde + reavertm: you probably know more about this one + we can probably just drop musicbrainz altogether + last time I checked there was no musicbrainz:3 support at all in k3b (but it was long time ago) + well k3b has not changed much lately + mhm, that's what the comments on the bug indicate + (I mean, there's api difference between those two) + I agree with creffett, I couldn't find any evidence that musicbrainz is actually being used anymore + in gentoo terms k3b would be maintainer-needed + :1 is obsolete + drop it + ack + bug #405181 + kensington: https://bugs.gentoo.org/405181 "dev-util/cmake: FindPythonLibs behaviour broken by Gentoo patches"; Gentoo Linux, KDE; CONF; gentoo-bug:kde + meh + i hate it + the best way woudl be to + * remove the patches + * and force cmake onto a specific python version via commandline defines + that _should_ work + but I have not tried yet + sounds good, should we try that then? + yes, but no guarantees it'll work + bug #410139 + kensington: https://bugs.gentoo.org/410139 "kde-misc/networkmanagement-0.9.0 and kde-misc/networkmanagement-0.8_p20110714 wrong doc dir specified"; Gentoo Linux, KDE; UNCO; gritoo:kde + cant never reproduce this... + ditto + couldn't see how it might be run into, looking at the eclass :( +-*- creffett guesses funny user settings + we could ask for the environment and the eclass debug log + maybe it was fixed with the eclass changes that we introduced? + but I dont have any other ideas + (maybe funny variables in make.conf?) + ok I can try to take care of this one, it's obscure enough to be interesting + RESOLVE NEEDINFO + hehe + bug #383733 + kensington: https://bugs.gentoo.org/383733 "kde-misc/interceptor - KDE4 Plasmoid - intercept (catch) the log info from the syslog"; Gentoo Linux, Ebuilds; CONF; fitzadam:maintainer-wanted + this one's mine +-*- johu dont need the package and have no interest in it :P + basically, it's a plasmoid that requires an init script and modifications to the system's syslog configuration + I also thinks it's overkill and potential security problem + and there's continuing trouble with using the FIFOs required + so, I suggest we resolve wontfix + but we could show it to recruiters as replacement for w... + haha + nah, it's not quite _that_ bad + rating 65% + creffett: not talking about your ebuild, just about the general problem :D + wontfix, or just take us off cc and suggest sunrise? + latter + maybe someone will pick it up + bug #406353 + kensington: https://bugs.gentoo.org/406353 "dev-util/cmake-2.8.6-r4 - stop Xvfb after failed test phase"; Gentoo Linux, KDE; UNCO; toralf.foerster:kde + good catch + if tests die, virtualx can't kill Xvfb it started + will be a problem too for virtualdbus (coming soon!) + is there any phase we could use to clean it up? + i'm asking in #-portage + kensington: are you making any progress on virtualdbus? + I looked at it some, but couldn't figure out a way to make it work for bash commands + I had the same problem, but it seems to work by just exporting the appropriate envvars + oh? + I'll talk to you about it later, then, but I'd love to hear your progress + creffett: this is my work in progress http://dpaste.com/749504/ which is working reliably for the package I've been testing with, systemsettigns + cool, I'll have a look later + k + seems we might need some input from zmedico et al here + let's see if any of them responds + next topic! + 5. open floor + dilfridge: whats the arm state? You wanted to ask the guys + no really definite response yet + only people that replied did not have fast enough machine + hm + (remember this is many gadgets and embedded stuff) + ok postponed + my open floor is ^, I'll bring it up again when there's no more calls to ugly_hack() + hehe + anyone else? +-*- dilfridge hears the silence + yes + kde-4.9 beta is coming out soon + kde 483 stable and the last outstanding bug + the dav foo! + right + anyone has a dav-based calendar server? + do we want to stable -r2 which have the upstream "fix" but no positive feedback or just use r0 which is fucked up for sure + -r2 in case of doubt imho + someone will be unhappy either way + some feedback on the upstream bug saying it's still not fixed, but it might be a different but similar bug + yes i read this too + the other people have different problems + +1 on -r2 then + so if noone raise objections i give ago the go tomorrow after keywording ppc/ppc64 is done... + awesome + cool, anything else? +-*- johu needs more beer + meeting over then :P + organization question, who writes the summary? + +1 + always whoever asks first :D + always johu i guess + creffett: make a draft i review it! + next time creffett is chairing + :D + dilfridge: if 7 days over i do it for sure on my own as last time with you lazy guy :P + dilfridge: out of contact at the time, sorry + hehe + creffett: ah yes have a great time, when does your trip start? + which reminds me: I'm disappearing from the 20th through june 15th + ^^ + creffett: set your devaway then please + I will + and I'll forward my gentoo mail to the email address I get to use on the boat which doesn't cost me money to use, but I won't be committing or anything + enjoy your trip + I'll try + and dont think about gentoo in this time + we will save some bugs for you + thanks :P + s/save/make/ + 3 + 2 + 1 + end diff --git a/meeting-logs/20120621-summary.txt b/meeting-logs/20120621-summary.txt new file mode 100644 index 0000000..6f246e9 --- /dev/null +++ b/meeting-logs/20120621-summary.txt @@ -0,0 +1,39 @@ +1. Roll call (4 minutes, 5 minutes planned) +Present: alexxy, dilfridge, scarabeus, tampakrap + +2. Move KDE 4.8.4 to the tree, and in which variant? (1 minute, 5 minutes planned) + It seems that the problems have been solved with a) newer soprano or b) reverted commit. + Which way do we want to go? +All in favour of reverting the commit in kdelibs and pushing 4.8.4 to the tree to work +with "old" soprano. + +3. Once it's out, should we move KDE 4.9.0 to the tree? (3 minutes, 10 minutes planned) + Currently 4.8.90 looks quite solid, so this is a real option. +All in favour of adding 4.9.0 to the main tree as ~arch + +4. Udisks2 (8 minutes, 5 minutes planned) + On request from Samuli I've added the Udisks2 patch from RedHat to kdelibs. This + *replaces* the udisks:0 solid backend with a new udisks:2 version. Has according + to Wulf (Philantrop) still some issues. + Feedback? Experiences? Keep for 4.9.0 or (temporarily) ditch again? +No decision, some discussion with alexxy and Philantrop about the problem. We'll keep +watching Fedora's code and talk to the Fedora maintainers. + +5. Bugs (1 minute, 30 minutes planned) + * app-cdr/k3b: Excessive use of REQUIRED_USE (and wrong combination USE="lame"+"encode") + REQUIRED_USE was added, otherwise USE="-encode lame" does nothing + Options: + 1. Revert to original behaviour - we don't care that USE="-encode lame" does nothing + 2. Keep the REQUIRED_USE, but rename lame -> mp3 + 3. Drop the encode flag, but move the optional RDEPS to an elog + 4. Drop the encode flag and keep optional RDEPS (current behaviour) + https://bugs.gentoo.org/show_bug.cgi?id=417235 +Postponed since the principal actors involved were absent. + +6. Open floor (10 minutes, 15 minutes planned) +tampakrap asks for more speakers and workshop organizers at the Gentoo miniconf October in +Prague. Some ideas are thrown around, nothing definite yet. + +[21:34:02] meeting closed +[21:34:13] i think we just made a new speed recoed +[21:34:19] :) diff --git a/meeting-logs/20120621.txt b/meeting-logs/20120621.txt new file mode 100644 index 0000000..f34603e --- /dev/null +++ b/meeting-logs/20120621.txt @@ -0,0 +1,143 @@ +[21:08:37] !herd kde +[21:08:39] (kde) abcd, alexxy, creffett, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 +[21:08:40] ok +[21:08:41] roll call +[21:08:49] -*- alexxy +[21:08:52] -*- dilfridge +[21:08:56] -*- scarabeus +[21:09:00] -*- tampakrap :) +[21:09:06] :) +[21:09:14] (:) +[21:09:16] dilfridge: so you have two lazy ex-leads :D +[21:09:19] hehe +[21:09:31] not counting those so lazy that they dont attend :D +[21:09:46] alexxy: btw summer camp looks intruging so far, working on convincing gf to go with me there :P +[21:10:05] scarabeus: I said I accept +[21:10:08] scarabeus: if you need invitation i can create one +[21:10:26] tampakrap: wanna go to russia mid summer to see gentoo summer camp?; i forgot to ask ya at office +[21:10:41] tampakrap: and for the above sentence you can say goodbye to your left arm +[21:10:47] hehe +[21:10:56] ok let's do this quick and painless +[21:11:04] point 2) +[21:11:10] move 484 to tree +[21:11:35] dilfridge: move it =) with reverted changes to kdelibs +[21:11:37] i suggest *revert the kdelibs commit that needs newer soprano, *move to tree, *stable as usual if nothing happens +[21:11:39] yes +[21:12:06] adn scarabeus said same, so basically we have 100% agreement +[21:12:12] cool +[21:12:16] next point +[21:12:21] 3) 490 +[21:12:31] so far I'm really happy with 4.8.90 +[21:12:32] it should be in tree +[21:12:35] as ~arch +[21:12:37] what do you think? +[21:12:49] i'm running it on laptop +[21:12:52] me too +[21:12:54] we agreed to add last rcs only back +[21:12:55] its pretty stable +[21:13:15] scarabeus: ? dont understand +[21:14:18] few year back we decided to add only last rc if desired +[21:14:36] scarabeus: nah I dont mean 4.8.90, but 4.9.0 +[21:14:57] and that should be fine for sure +[21:15:00] ah sorry for the fuzz then +[21:15:02] yep +[21:15:11] ok that's 3 yes :) +[21:15:11] i can give ya spin on stable when you decide to roll that +[21:15:19] yeah +[21:15:30] next point +[21:15:34] 4) udisks2 +[21:15:53] nothing really to decide yet, but please test +[21:16:00] 4.8.90 and later has the patch +[21:16:13] Philantrop says it has performance issues +[21:16:17] it works (tm) +[21:16:22] ok +[21:16:33] worst case we revert that in 490 +[21:16:46] dilfridge: well if we ask pva to test, he will find tonns of bugs +[21:16:48] alexxy: Check your .X.errors or whatever it's called. Doesn't it have a *ton* of devices being listed? +[21:16:50] hehe +[21:16:59] since he has funny karma +[21:17:03] devnum: 66305 dev file: "/dev/md127p2" +[21:17:03] devnum: 64512 dev file: "/dev/dm-0" +[21:17:03] devnum: 66306 dev file: "/dev/md127p3" +[21:17:03] devnum: 64512 dev file: "/dev/dm-0" +[21:17:28] Adding device "/org/freedesktop/UDisks2/block_devices/md127p3" +[21:17:28] Adding device "/org/freedesktop/UDisks2/block_devices/md127p4" +[21:17:28] Adding device "/org/freedesktop/UDisks2/block_devices/nbd0" +[21:17:28] Adding device "/org/freedesktop/UDisks2/block_devices/nbd1" +[21:17:30] and so on +[21:17:31] dilfridge: Exactly. That stuff slows down file requesters pretty badly if you have more than a handful. +[21:17:32] well i have all my lvm2 volumes listed +[21:17:49] ~12 volumes +[21:17:52] on my laptop +[21:18:05] dilfridge: That happens *every* time a file requesters is opened. +[21:18:11] and i cant say that adding usb flash drive works slow +[21:18:14] let's hope the RH guys fix it up, they should be interested in it too +[21:18:29] I'll watch the fedora repo really hard +[21:18:34] alexxy: You don't notice any difference in performance? +[21:18:59] Philantrop: yep i dont see any *visible* difference +[21:19:10] alexxy: Interesting. Which KDE version? +[21:19:19] 4.8.90 +[21:19:26] alexxy: Hm... 4.8.4 here... +[21:19:42] *4.8.3 actually. +[21:19:57] well... let's just test... but one user on #gentoo-kde also reported slowdown +[21:19:59] 4.8.4 has same kdelibs +[21:20:20] alexxy: True. Are you guys applying any other special patches? +[21:20:26] -*- dilfridge wonders what happens if you still have /dev/fd0 +[21:20:28] dilfridge: its like infamous kernel iowait bug +[21:20:41] it may depend on hw +[21:20:44] not really, no, imho +[21:20:52] dilfridge: cannot access /dev/fd0: No such file or directory +[21:20:59] Philantrop: yep i have some special patches in kernel +[21:21:13] but they are for mm subsystem +[21:21:20] dilfridge: Do you notice any slowdown? +[21:21:21] like memory deduplication +[21:21:24] and so on +[21:21:32] alexxy: Ok, and for KDE? +[21:21:45] I only upgraded today, so the kile that I started with the agenda was the first app to use it... +[21:21:49] kde from kde overlay +[21:21:55] nothing special +[21:22:20] alexxy: Weird... I wonder what's causing it then. +[21:22:27] -*- alexxy uses texmaker +[21:22:33] the list of patches for kdelibs looks harmless +[21:23:10] ok anyway +[21:23:14] next point +[21:23:21] 5) +[21:23:23] bugs +[21:23:33] I think we should postpone this since kensington is not here +[21:23:46] any objections? +[21:24:24] seems not +[21:24:47] which brings us already to the very last point, +[21:24:51] 6) open floor +[21:24:56] anyone has anything to discuss? +[21:25:04] -*- dilfridge gets a sandwich, brb +[21:25:10] yes +[21:25:37] don't forget the gentoo miniconf please, I desperatedly need speakers +[21:25:58] yeah +[21:26:23] is there already anything desktoppy? +[21:26:49] -*- alexxy can talk something about hpc and clusters +[21:26:50] whatever you want +[21:26:59] but i'm not sure if i will take part +[21:27:03] I'd prefer a workshop where people can participate +[21:27:08] but a talk is also fine +[21:27:09] i'll come, just not sure about time for preparation +[21:27:12] we have our own room +[21:27:39] tampakrap: simple workshop - how to crate smal cluster with rm in 30 minuts +[21:27:40] =) +[21:27:46] packaging plasmoids for fun and profit +[21:28:30] both sound awesome +[21:29:09] -*- scarabeus haz to cook, cya laterz lads +[21:29:19] ok lets think about this a bit, but we will organize something for sure +[21:29:50] alexxy: +1 +[21:30:15] -*- alexxy still not sure about visum +[21:30:20] or I could tell something about LinuxGPIB and lab device control with Perl, but that's not for participation, only coolness factor +[21:30:44] yeah the old problem :| +[21:31:21] actualy its simple one =) +[21:31:32] ? +[21:32:24] anyway +[21:32:27] anything else? +[21:33:08] -*- dilfridge listens to the silence +[21:33:42] perfect +[21:33:47] that's it then cheers! +[21:34:02] meeting closed +[21:34:13] i think we just made a new speed recoed +[21:34:19] :) \ No newline at end of file diff --git a/meeting-logs/20120816-summary.txt b/meeting-logs/20120816-summary.txt new file mode 100644 index 0000000..b68e32f --- /dev/null +++ b/meeting-logs/20120816-summary.txt @@ -0,0 +1,95 @@ + +KDE team meeting summary + + +1. Roll call +KDE team members present: +ago, creffet, dilfridge, jmbsvicetto, johu, tampakrap, thev00d00 + + +2. KDE SC stabilization: discuss/vote on the following options: +a) First 4.8.5 as decided in a former meeting, then 4.9.1 / 4.9.2. +b) Skip 4.8.5, start with 4.9.0 / 4.9.1 directly. +c) Other? + +After some discussion, a vote resulted in 5 votes for a), 1 vote for b). 4.8.5 +has two remaining (upstream) issues (da translation error and a missing theme +for ksplashx) which will be locally addressed in time before stabilization. + +Ago suggested that we should follow the Kernel crowd, and only ever stabilize a +late release in every KDE series ("x.x.7/8"). Most of the other team members +were against that idea, since +* we'd find Gentoo-specific problems only very late then (when the large crowd + migrates) +* and people will complain if we wait with stable upgrades too long. +As a compromise we settled on "4.9.0 will never go stable, we talk about 4.9.1 +when it's out for a while". + + +3. Solaris patches: We apply many patches to support Solaris, but there seems to +be no prefix keyword. Does anyone know anything about them? If we are supporting +Solaris, Kensington would like to push these patches upstream. Does anyone have +access to a box to test if they are still useful? + +Nobody present had any opinion or cared about the solaris stuff. As a result it +was decided to drop the patches. + +On #gentoo-prefix this was ack'ed later by darkside for the prefix team. ryao +noted there that Qt is broken on Prefix at the moment, and that the KDE patches +could become relevant again after that is fixed. + + +4. KDE stable subproject: Ago proposed a "KDE stable subproject" some time ago +via mail. The idea is that the subproject members test KDE stable candidates on +an otherwise completely stable system as soon as we decide on a stable +candidate, to make fast and bug-free stabilization possible as soon as its +30days in the tree. + +Discussion led to various points: +* Ago is mainly thinking of Gentoo-specific stable candidate QA. +* The "stable subproject" obsoletes the (dead) "herd testers" subproject which + we tried to start up some time ago. +* No quiz required for participation. +* Johu suggested a more upstream-oriented direction ("like kdepim bug day"), + which however seems like a different endeavour. +* In the end, there were no objections, Ago takes care of establishing that + group of people and updates our site. + + +5. Bugs + +5a. Bug 417235: app-cdr/k3b: Excessive use of REQUIRED_USE +Majority decision was to keep the REQUIRED_USE, but rename lame -> mp3 + +5b. Bug 430608: cmake-utils.eclass: add support for dev-util/ninja +It was decided to apply the patch and make building with ninja possible; +however, if the build fails a message about using an unsupported backend +should be logged (if possible). + +5c. Bug 427910: app-office/calligra-2.4.3: move fonts to separate packages +and related bug 427914: www-client/rekonq-1.0: please move Nunito-Regular.ttf +to separate package +Most people present did not really care. Consensus was +* Find out if there is any license problem with the status quo. +* If yes, talk to upstream and try to solve the problem with them. +Nobody volunteered to research the license situation. + +5d. Bug 430858: net-libs/libkolabxml-0.8.0[php] fails +The cause here appears to be that FindPHP4.cmake does not look in +/usr/include/php5.*. (and there is no FindPHP5.cmake). This potentially means +that every search for PHP in cmake is broken (though it appears that nothing in +kde-base at least has IUSE="php", explaining this not being caught). Consensus +was to provide upstream with a FindPHP5 module and ask for inclusion. + + +6. Open floor + +6a. Further discussion about the stable subproject +Tampakrap notes that for recruiting devs a subproject with overlay access is not +the most efficient way, since people tend to be happy with overlay access and +are reluctant to go through the actual recruiting process. We should try to +motivate people to become full developers. In addition he offers to mentor +people. + +6b. Default KDE_SCM +Johu proposes to switch this to git. Noone opposes. diff --git a/meeting-logs/20120816.txt b/meeting-logs/20120816.txt new file mode 100644 index 0000000..c6ea614 --- /dev/null +++ b/meeting-logs/20120816.txt @@ -0,0 +1,539 @@ + 1. Roll call + !herd kde + (kde) abcd, alexxy, creffett, dilfridge, jmbsvicetto, johu, +kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 + you're repeating yourself +-*- creffett is still here +-*- johu is here +-*- dilfridge is here +-*- tampakrap is here + tampakrap wanna rejoin? + no +-*- dilfridge thinks we should just do it + jmbsvicetto / Thev00d00 ? +-*- ago here too + :D + ok meeting opened + 2. KDE SC stabilization (15 minutes) + * Discuss/vote the options: + a) First 4.8.5 as decided in a former meeting, then 4.9.1 / 4.9.2. + b) Skip 4.8.5, start with 4.9.0 / 4.9.1 directly. + c) Other? + tampakrap: do you know anything about kde-stable subproject? + here + isn't 4.8.5 mostly bugfix? + yes + problem is, noone of the team is running it + yes we can stable it realy fast because of no new deps... + judging from prior experience, we should probably skip 4.9.0 + and all ~arch users have already upgraded to 4.9 + dilfridge: wrong i run 4.8.5 on netbook + dilfridge: I'm here to run it + ok cool & cool :) + there are 2 issues: da translation and a missing theme for splashx + the translation compile error should occure on kdepim-l10n as we split +this up + are there fixes / workarounds? + if we decide on option b) i would start with 4.9.1 as upstream done a +lot of bug fixing since 4.9.0 + dilfridge: yes we can patch it + both? + for l10n + my question is whether it fixes any bugs that are relevant to us + with the theme i hadnt a look so far + creffett: which version? + johu: 4.8.5 + we had two fixed tracking bugs as i remember right + any opinions about the direction a) b) c)? + A imho +-*- dilfridge votes a) + ++a, then on to 4.9.1 +-*- johu votes a) + I'm here FYI + Thev00d00: then use your voice :P +-*- Thev00d00 reading backlog + a) + After the vote I would just add a note, plese give me a voice when I can + ago: can we do 485 faster than the 30 days? + johu: sure, for amd64 and x86 + b) + but scarabeus can do it on ppc :P +-*- ago hides + ago: feel free to do and say whatever you want... btw if you leave +and rejoin you'll be op in #gentoo-kde :] + dilfridge: thanks... + speaking of scarabeus... + summary: majority is for 485 and continue with 491/492 afterwards + dilfridge: no need to leave - /cycle + ah ok + 3. Solaris patches (5 minutes) + * We apply many patches to support Solaris, but there seems to be no +prefix + keyword. Does anyone know anything about them? If we are supporting +Solaris, + Kensington would like to push these patches upstream. Does anyone +have + access to a box to test if they are still useful? + that was kensingtons topic but we can talk about it +-*- dilfridge wanders off in search of a beer +-*- johu personally dont cares about minor arches in kde point of view... + ok, is know that every +1 releases is better than the precedent, but in +this case I would copy kernel's team strategy about stabilization, they +stabilize always non the first release, e.g. x.x.7/8 so, since the stable kde +works pretty good, how sound think to stabilize a major release of 4.9? + e.g. 4.9.4 + instead aof proposed 4.9.1 + ago: the past has shown that with start of stabilization we fixed a lot +of bugs + and .1/.2 are in common the most valuable releases + johu: yes, sure, but for me, go to 4.8.5 to 4.9.1(in that case) seems +like a regression, since there will be a lot of bugs + I don't prefer agos idea + Thev00d00: reason? + ago: which bugs to you mean " since there will be a lot of bugs"? + /s/to/do/ + I think ago means upstream bugs + johu: mean usually bugs of first release + dilfridge: yes + thats why i prefer not to stable a .0 release + we're more concerned about finding Gentoo / packaging bugs, and +having two runs of stabilization inside one 4.X cycle helps there + johu: me too, but I'm only said to increase that .0 :P + ok we are finished now with 2) ? + ago: the kernel moves a lot faster than kde and they used to +have parallel development + jmbsvicetto: yes, but is just the concept to stabilize not the first +release + ago: thats what we are doing :D + ago: kde basically throws away the previour minor release when +they launch a new one. So it's very unlikely we'll get a 4.8.6 with any fixes +and 4.9.4 will likely take around 4 / 5 months + I think we should target .1 ... usually we go for .2 anyway then +:D + people will moan + they like fast fast stabilisation + :-) + keep ppc please in mind... + Thev00d00: who wants a newer kde, go to ~arch + the stable users expect minor bugs as possible + thats right! + 3. Solaris patches (5 minutes) + * We apply many patches to support Solaris, but there seems +to be no prefix + keyword. Does anyone know anything about them? If we are +supporting Solaris, + Kensington would like to push these patches upstream. Does +anyone have + access to a box to test if they are still useful? + that was kensingtons topic but we can talk about it + ago: how about this, + we now decide "490 will never go stable, we talk about 491 when +it's out for a while" + dilfridge: fine + and then we can always still say we wait for a later release + if it's too buggy. + the one problem with testing is, +-*- johu is chairing + many problems for users occur when they upgrade major version +-*- creffett suggests hitting people with the gavel until they move on + so, many problems we will only see once many people upgrade to 4.9 + but anyway, this is not urgent now + so let's continue + so where are the dinosaurs? + [21:40:05] 3. Solaris patches (5 minutes) + [21:40:05] * We apply many patches to support +Solaris, but there seems to be no prefix + [21:40:05] keyword. Does anyone know anything +about them? If we are supporting Solaris, + [21:40:05] Kensington would like to push these +patches upstream. Does anyone have + [21:40:05] access to a box to test if they are +still useful? + [21:40:07] that was kensingtons topic but we can +talk about it + whats about the solaris stuff? +-*- creffett votes "no opinion" + well reavertm is obviously logging but away, I sent scarabeus a +reminder but got no reply yet + jmbsvicetto? +-*- dilfridge thinks "remove the patches if noone is interested in a keyword" + johu: solaris? I don't know anything about it + ok then we can give kensington the go to drop it + johu: I'd ping the prefix team about that. If we get no reply, +drop them and wait for someone to cry about them ;) + ? + jmbsvicetto: good statement lets move on + 4. KDE stable subproject (10 minutes) + * Discuss the new KDE stable subproject, as proposed by ago. + ago: its your turn :P + well + I explain all in a mail sent to all, anything not clear? + or everyone didn't look at it? + how many ppl do you have gathered so far? +-*- johu likes the idea but testers are not very long term motivated in +general + johu: this is the point of start for new developers interested to join +kde + in gentoo obviously + I think we can always use more people who run stable/stable +candidate and fix bugs there + because most kde devs run 9999 + I honestly don't see if there's much to gain from having +separate sub-projects for HTs and stable KDE, but if there are enough people +wanting to do stable kde work and not general HT work, then go for it + ok, since there is the time, let me re-explain for all :) + well, we don't really have an active HT group last I checked... + creffett: yes + jmbsvicetto: the HT project seems dead + creffett: but what would prevent anyone from being a member of +HT and do stable work? + obviously :D + [21:49:39] dilfridge: The last I heard, Qt was broken on +Prefix. Once that is fixed, the solaris patches should become relevant. + so the goal of kde-stable is involve people without doing ebuild quiz + jmbsvicetto: I have no problem with that, but we kind of need to +restart the project first + ago: I understand, but I don't think there's much to gain from a +stable sub-project. If you get people interested on that, I won't object, +though + Now the quiz for arch/herd tester has been changed, but I remember When +I did it for arch tester...is a pita + creffett: jmbsvicetto: johu: we could see it as an alternative +approach to HT + dilfridge: HTs did a more general job + ok + dilfridge: they also helped with patches, testing stuff, +following upstream (live) commits + jmbsvicetto: when members counts our HT project? + but to be clear, I don't have anything against a stable +sub-project. If you can gather people wanting to do that, great :) + I just find ago's idea very useful, because our kde team work is +often much focussed on the bleeding edge, and only the one guy leading the +stabilization runs the candidate + +1 dilfridge + i would vote for a more upstream oriented direction + like kdepim bug day + johu: I think there are a lot of people interested in kde (in general), +we do it for improve QA on gentoo +-*- dilfridge gets a headache hearing "kdepim bug day" + take a aspirin :P + how about we start by re-establishing a KDE herd-testing group + @all: which members counts ht project? + and from there, if we have time, inclination, and interest, we make +a sub-group for stable + I know many people and AT that runs kde, they will happy to help + creffett: better not, we should really focus this on "stable" + dilfridge: why not general testers first? + so let me summarize: we have no objections, ago takes care of +establishing that group of people and updates our site + creffett: because it's getting to "undefined"... + any additions? + vague + johu: ok, I'm just asking about HT, if there are no people, we just make +it as dead? + ago++ + yes + yes + ++ + last chance, any additions? + yes + [21:57:12] dilfridge: dunno. feel free to drop all +non-upstreamed stuff. + kde-stable probably will inherit things from HT, e.g. you can ask a test +to any member and/or similar, we can document it + so, see it as an improvement from HT without quiz + sounds reasonable I think + fine + agreed + 5. Bugs (30 minutes) + * app-cdr/k3b: Excessive use of REQUIRED_USE (and wrong combination + USE="lame"+"encode") REQUIRED_USE was added, otherwise USE="-encode +lame" + does nothing. https://bugs.gentoo.org/show_bug.cgi?id=417235 + Options: + 1. Revert to original behaviour - we don't care that +USE="-encode lame" + does nothing + 2. Keep the REQUIRED_USE, but rename lame -> mp3 + 3. Drop the encode flag, but move the optional RDEPS to an elog + 4. Drop the encode flag and keep optional RDEPS (current +behaviour) + kensington is not here, any opinions? + #2 + 2 + tampakrap: you wanna rejoin? :D +-*- dilfridge has no opinion + I said no! + :D + _ /msg Chanserv add #gentoo-kde tampakrap ... + i am so forgetful +-*- johu votes for 2 + 2 is fine + * cmake-utils.eclass: add support for dev-util/ninja + https://bugs.gentoo.org/show_bug.cgi?id=430608 + do we want to support two different build systems? + i would vote for an new eclass that inherits cmake.eclass + I'd suggest we only allow this with I_KNOW_WHAT_I_AM_DOING + AFAIK ninja just generates make files? + nope it's a make alternative + cmake generates the files for ninja, as it generates Makefiles for +make + oh I see + actually, before we decide on this one someone should try to build +whole kde with the new generator :D + and no, I'm not volunteering +-*- johu has a lot of things to compile as x86 arch member, no interest + we can add this to the eclass + I am willing to build/test stuff + +1 for applying the patch + but the generator variable should only be respected if +I_KNOW_WHAT_I_AM_DOING is set + but not willing to fix or patch anything + to avoid an insane number of bugs + imho + if there is anything to compile give me a list + :D + same as tampakrap here + I don't think I_KNOW is needed + yeah after all it needs to be set in ebuild or make.conf + but make should be preferred + even if ninja is present + for sure + agreed then? + yes + can we at least have some elog about untested backend? + or einfo + elog spam FTL + how about, + we only output a message if the build fails + must be possible somehow + then telling "please use make backend before reporting bug" + yeah, sounds good + bad idea, elog beforehands is sufficient + * app-office/calligra-2.4.3: move fonts to separate packages + https://bugs.gentoo.org/show_bug.cgi?id=427910 + for every make based package? :( + *make + didnt I close that one already + dilfridge: i know you closed the bug but i want to discuss this + argh android + ok +-*- creffett thinks it's pointless to split off a few small files here for no +appreciable gain + is there an license breakage? + isn't there a license violation by splitting oxygen-icons? :) + we dont split it :P we remove svgas + tampakrap: not really since we use the bindist useflag I think... + dilfridge: I think there would be a license violation if we +didn't provide a way to get the official tarball + dilfridge: but we should probably ask licenses@ about that + from technical point of view this is a totally senseless bug.... + there is no purpose at all (you save some kbs on HD) and get with new +bumps maybe more work + we could extend LICENSE var if its needed... + the overall reaction to this bug seems to be a definite "meh." + mhm + "we are not debian" :P + le sigh + [22:24:41] New bug: https://bugs.gentoo.org/431680 +"app-office/calligra-2.5.0 has dev-db/mysql automagic"; Gentoo Linux, KDE; +CONF; nikoli:dilfridge + * www-client/rekonq-1.0: please move Nunito-Regular.ttf to separate +package + https://bugs.gentoo.org/show_bug.cgi?id=427914 + this is the related bug to the last one... + its ONE file! + same reaction + recruit the guy to do those things by himself + the question is, are these fonts already somewhere else... + tampakrap: do it + he is in #gentoo-kde btw + but even then, if versions differ we're creating the bugs from +hell + tampakrap: yes we know :] + so summarize? + summary: RESOLVED DONTCARE + cleanest way would probably be "the fonts are already in a +dedicated font package, so we depend on it and delete them locally" + but creating a new font package for one file, NO + creffett: ++ :D + and if versions differ that may lead to strange problems + so I think I'm with creffet + whats about the license problem? + that needs to be spelled out in detail first + who asks license@? + as long as we dont even know if there is a license problem, ... +-*- creffett files a bug to add "DONTCARE" as a bugzie option + RESOLVED MEH + this log is public... + dilfridge: how about to involve upstream? + good luck + we can do it, and calligra upstream is usually responsive, but +before that we need to figure out if there actually IS a problem + and a gain by the move + so, anyone figure out if there is a license problem, and a gain by +the move, + and then I can talk to calligra upstream (who know me) + anybody interested? + ok i take that as no + * net-libs/libkolabxml-0.8.0[php] fails + https://bugs.gentoo.org/show_bug.cgi?id=430858 + The cause here appears to be that FindPHP4.cmake does not look in + /usr/include/php5.*. (and there is no FindPHP5.cmake). This +potentially means + that every search for PHP in cmake is broken (though it appears that +nothing + in kde-base at least has IUSE="php, explaining this not being +caught) + my turn + I've upstreamed this one, but just wanted to see if anyone else has +opinions on it + this issue is connected to kde491 stable :P + it is? + sounds good to push this upstream + its a dep of kdepim-runtime, if we solve this properly we can servce +users the feature + mmkay + well + question 1: does anyone know of a KDE package that actually +uses/deps on PHP? + not that i know.... + yes + a kdevelop plugin + kdevelop parts + yes + hm, I'll look at that + and it's working pretty well actually + tampakrap: i miss you + but basically what happens here is libkolabxml calls +FIND_PACKAGE(PHP4 5.3 required) or something to that effect + <3 + because there is no FindPHP5 module + but regardless of that, our PHP is in /usr/lib/php${PV} + there is no module in official cmake or kde packages you mean? + or noone ever wrote one? + tampakrap: no official module + a google search turned up a couple custom ones, but basically all +they did was replace "php4" with "php5" which still doesn't solve things + then ask kensington to try to push one upstream + since he is pretty known in buildsystem now + my concern here is that I don't know if there's a nice way to do +this for Gentoo's PHP style + is there a nicer way to specify the paths available than listing +every PHP minor version? (e.g. 5.3, 5.4, 5.5 when it comes out...) + creffett: good proposal from tampa, kensington knows a lot of cmake +stuff + johu: okay, will shoot him a note + creffett: not sure about that, I still remember the FindBoost pain + listing every minor version does not look dirty to me tbh + tampakrap: we then have to bump the modules every time a new PHP +comes out + other distros don't slot their php generally + if you want to avoid that, then you need to write a proper build +system first + 6. Open floor (15 minutes) + I know, deal with it + tampakrap: "deal with it" wasn't quite what I was hoping to hear :P + life is hard :) + http://dev.gentoo.org/~dilfridge/shirts-from-hell-small.jpg + so, regarding open floor, and since I missed the discussion for HT +and stable subproject + may I revive the topic? + is ago still here? + ago is chuck norris + ago: ^ + he is everwhere + (ago's highlight works only with the :) + ok so + in short + scarabeus I think invented to have HTs back then, with the first +candidate being me + but it turned out to be a failure as an idea, since people that +wanted to do ebuild stuff were fine with just overlay access + and the HT status offers a cloak only, which is bullshit + so, I decided in a previous meeting to stop that and just have a +list with overlay committers + indeed :) + and try to make them directly developers + so, if you are going to invent any sub-project again or whatever +-*- johu wants reviewboard or similiar for overlay access by users + don't put any paperwork there, and try to motivate people to get +dev status directly + johu: clone the repo in gentoo's github account, there's your +reviewboard + tampakrap: that doesnt solve the problem that they can push the +official overlay + don't follow + they can send merge requests, they can easily get account without +quiz (just by asking) + so what's the problem? + just go for a moment in another place :) + btw kde is one of the best-staffed projects I know at the +moment... + anyway, I think I made my point regarding the HT subproject, feel +free to ping me for anything regarding getting new contributors + I'm interested + either to provide experience or mentor people + tampakrap: the goal is have more testing, not just rename HT project + tampakrap: my + arg + ignore me + _ /ignore johu + done + :D + ago: you want to create a project that does what exactly? + sorry for asking but you had internal discussion I suppose instead +of doing it in gentoo-desktop ml :) +-*- johu will prepare kde 485 next week + take care of testing next stable version on a completely stable +environment + ok, my personal opinion is that you don't want a subproject or a +new team for that + you need to document procedure, write intergration tests maybe, +and put it somewhere under QA + and make it more general, as it doesn't seem to me something that +can be kde only + alternatively: + KDE upstream have a QA team now that test the betas when they come +out, you could ask for their suggestions and ways of working + and cooperate in order to have a good set of products BEFORE the +next major release hits distros (and ours as well) + tampakrap: but we're NOT talking about KDE betas here + tampakrap: wait, you can't know more details about it, let me explain :) + true, we are talking about QA tests before stabilization + which is something that I'm doing professionally the past 8 months +:) + we're talking about all the problems that always ONE guy had to +fix, the one gentoo-kde dev who is overseeing the stabilization and the only +one still running that version :P + tampakrap: now we have decided t ostabilize 4.8.5, so when johu will +prepare a list I will start to test and use it in the next time but I can't +ask to other member/tester to use beta or software that have potentially bugs, +because they will use it ~ as a primary system +-*- dilfridge thinks we should close the meeting, his laptop battery is giving +up... + yeah sorry + dilfridge + + + we can move the discussion in gentoo-kde + no no + i have topic too + Quassel for android needs nick completion... + Thev00d00: ++ + Sput: ^ + i will start with moving defaulting KDE_SCM to git + err sorry, wrong person + any objections? + no, sounds ok + what is still in svn? + 1/3 i would guess + there you go then :-) + we'll probably have portage in git before they finish + Thev00d00: afaik it has if you long-tap the search button or something + kdegames for example, but svn2git rules are heavily in construction + since the upstream migration is far over 50% then, I see no +problem with switching default + ok thanks] + Sput: it works! my word :-) + meeting is over, thanks to all + johu: thanks for chairing :D + G'nite all diff --git a/meeting-logs/20120927.txt b/meeting-logs/20120927.txt new file mode 100644 index 0000000..256c308 --- /dev/null +++ b/meeting-logs/20120927.txt @@ -0,0 +1,260 @@ +[21:02:16] http://wiki.gentoo.org/wiki/Project:KDE/Meeting/2012-09 +[21:02:21] !herd kde +[21:02:22] (kde) abcd, ago, alexxy, creffett, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, tampakrap, thev00d00 +[21:02:25] 1. roll call +[21:02:26] present +[21:02:32] hello boys +[21:02:33] -*- johu here too +[21:03:56] --> scarabeus (~scarabeus@gentoo/developer/flyingspaghettimonster/scarabeus) hat #gentoo-meetings betreten +[21:04:03] so what is turnabout today? +[21:04:20] 4 ppl as last time... +[21:04:24] nice cloak. +[21:05:06] if i look to the herd member list there is something wrong +[21:05:17] I even announced it this time +[21:05:22] iknow +[21:05:29] well some cant attend, like jorge +[21:05:35] --> tampakrap (~tampakrap@gentoo/developer/tampakrap) hat #gentoo-meetings betreten +[21:05:38] ahoj +[21:05:43] nazdar +[21:05:58] nadrazi +[21:06:16] thats, railwaystation +[21:06:20] I know +[21:06:23] good +[21:06:35] pristi zastavka, nadrazi liben +[21:06:45] or pristi stanice +[21:06:54] never managed to separate them +[21:07:12] --> B-Man (~aaron@108.171.119.130) hat #gentoo-meetings betreten +[21:07:13] they are synonyms +[21:07:16] so they are the same +[21:07:23] but mhd says zastavka +[21:07:32] the teacher told me that one is the subway station and the other is ground station (metro, bus) +[21:07:57] tehcnically stanice could be a building and zastavka something small like the box with the sign +[21:07:59] so yea +[21:08:26] and what does the metro say btw? +[21:08:43] fucking not sure +[21:08:43] --> Thev00d00 (~v00d00@gentoo/developer/TheV00d00) hat #gentoo-meetings betreten +[21:08:48] hello +[21:08:50] i ignore it for few years already +[21:08:52] hello Ian +[21:08:55] sorry I'm late +[21:09:00] Jsem černý řidič +[21:09:02] anastum? +[21:09:13] johu: nerozumim +[21:09:45] a nastup, found it +[21:10:11] johu: I am black driver? :D +[21:10:18] scarabeus: yes +[21:10:38] google translate +[21:10:44] Ukončete prosím výstup a nástup, dveře se zavírají +[21:11:54] i always wanted after this message see emergency hydraulic close as i seen on tank +[21:12:01] woosh, click, scream, blood, ... :D +[21:12:23] bullshit +[21:12:43] <-- B-Man (~aaron@108.171.119.130) hat das Netzwerk verlassen (Quit: Konversation terminated!) +[21:13:07] but it closes so slowly :-) +[21:13:30] --> mrueg (~mrueg@rueg.eu) hat #gentoo-meetings betreten +[21:13:41] drunken ppl approved +[21:15:00] johu: i would say you wont get more people ;) +[21:15:15] !herd kde +[21:15:17] (kde) abcd, ago, alexxy, creffett, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, tampakrap, thev00d00 +[21:15:20] 1. roll call +[21:15:58] present +[21:16:04] ahoj +[21:16:04] . +[21:16:07] here +[21:16:34] ! +[21:16:38] beep +[21:16:48] hi +[21:16:51] 2. Elect new herd lead +[21:17:30] cue question of how many herd leads to have +[21:17:35] any nominees beside mee? +[21:18:01] johu: you still want to find someone else to do it huh? :D +[21:18:27] scarabeus: sure! +[21:18:29] johu: If you want not much active lead I can do it, but be sure I wont be proactive :D +[21:18:36] not me. +[21:18:54] ok second nominee scarabeus +[21:19:04] scarabeus and johu both lead would be awesome +[21:19:05] I vote johu +[21:19:16] how about have two leads? +[21:19:24] how about 6? +[21:19:25] scarabeus is to old and grouchy +[21:19:29] we'll have plenty of backups +[21:19:41] -*- johu votes for scarabeus +[21:19:55] ago: you need only one for the outside comunication, with devrel, recruiters, etc +[21:20:30] Thev00d00: the word is Grumpy :P +[21:21:23] -*- tampakrap votes for johu +[21:21:42] -*- tampakrap points out that scarabeus is saying *censored*, no leads are required actually +[21:21:55] tampakrap: do you re-joined? +[21:22:01] -*- creffett votes for johu +[21:22:04] tampakrap: only LEAD can approve new members for recruitement +[21:22:14] no idea, I was highlighted for the meeting :) +[21:22:18] tampakrap: and that is the reason why we started with leads :D +[21:22:22] plus I have nothing to do right now :) +[21:22:28] tampakrap: ok your vote will be counted +[21:22:30] in 2k9 with jorge +[21:22:37] we didnt have one for like 2 years before :P +[21:22:50] I really have to disagree, even team members is vague +[21:22:56] scarabeus / ago please vote +[21:23:06] -*- scarabeus votes johu +[21:23:15] -*- ago votes johu +[21:23:26] johu: didn't help ya :P +[21:23:29] for example, you've been doing heavy kde work (eg wrote the cmake eclass) way before joining as official developer +[21:23:31] i see +[21:23:41] -*- mschiff votes johu +[21:23:51] how does your opinion in that state count less than any other (inactive?) member +[21:24:20] ok vote finished +[21:24:30] 3. KDE 4.9 stabilization (15 minutes) +[21:24:40] Possible blocker, please discuss and vote: +[21:24:45] kde-base/konsole-4.9.0 - freezes on double-click (bug #430286) +[21:24:46] johu: https://bugs.gentoo.org/430286 ">=kde-base/konsole-4.9.0 freezes on double-click"; Gentoo Linux, KDE; UNCO; Martin.vGagern:kde +[21:24:51] - kde-base/nepomuk-core-4.9.1 - constantly segfaults after login into kde (bug #435112) +[21:24:52] johu: https://bugs.gentoo.org/435112 "kde-base/nepomuk-core-4.9.1 constantly segfaults after login into kde"; Gentoo Linux, KDE; UNCO; bu9zilla:kde +[21:24:56] kde-base/kmail-4.9.1 - problems creating imap folder (bug #434156) +[21:24:58] johu: https://bugs.gentoo.org/434156 "kde-base/kmail-4.9.1: Problems creating imap folder"; Gentoo Linux, KDE; CONF; dilfridge:kde +[21:25:18] so vote finished without celebration? +[21:25:22] you must be kidding me +[21:25:34] my gf will celebrate me +[21:25:41] -*- tampakrap CONGRATULATES HIS MENTEE JOHU AND OPENS ANOTHER KOZEL!!! +[21:25:54] congrats johu ;) +[21:26:01] thanks +[21:26:25] tampakrap: kozel means what? +[21:26:27] johu: we can give you a badge :P +[21:26:31] johu: beer brand +[21:26:38] johu: first two are blockers +[21:26:47] johu: the kmail is not critical even tho annoying +[21:27:17] then i have 2 bad messages from upstream no progress on the 2 blockers for 492 +[21:27:36] johu: good luck as lead =) +[21:27:51] ago: sure, i will need it +[21:28:21] johu: so, I'd say to wait 493 +[21:28:50] ago: or wait for fix and backport to 492 if there is a solution in the meantime.... +[21:29:05] not a bad idea.. +[21:29:18] well i would like 4.9 as it fixes few bugs i am experiencing +[21:29:25] in all cases we need upstream fix before decide and do anything +[21:29:41] but not over everything, so the blockers could be backported but we should not proceed without them +[21:30:20] scarabeus: 100% ack +[21:30:56] ok, i will watch upstream and ping back if there is a fix +[21:31:07] a cannot reproduce 430286 here +[21:31:48] mschiff: me neither but its acked by arch users as well, happens from time to time +[21:32:10] * Status report of kde stable subproject (ago / creffett ) +[21:32:39] well +[21:32:51] the page project is up and appears complete +[21:32:53] http://www.gentoo.org/proj/en/desktop/kde/kde-stable/index.xml +[21:33:19] I asked via query feedback to johu creffett scarabeus tampakrap Thev00d00 and seems fine +[21:33:45] I want to raise two objections here though +[21:33:48] And using current git kdepim (well two days old or three) and akonadi 9999 I cannot reproduce 434156 +[21:34:04] I will fix it time to time If I will notice there is e.g. the same thing not clear for more than one people +[21:34:13] 1) this subproject does NOT need a separate alias, it does NOT need an alias even, just use gentoo-desktop ml +[21:34:47] tampakrap: what is the "cost" associated with making a new alias? +[21:35:01] no cost, and I am not talking as infra now +[21:35:08] I'm talking as a guy interested in that stuff +[21:35:09] tampakrap: this subproject can also ack on other kde-* stable request +[21:35:30] so, my opinion is that all the moves of those guys should be 100% public, thus ml is the best option here +[21:35:57] (which is a principal of gentoo) +[21:35:58] ago: sorry, I don't understand what you mean +[21:36:03] or I don't see your point +[21:36:22] tampakrap: if we have people interested in this stuff, why they must follow gentoo-desktop? +[21:36:47] instead of read only the possible mail sent from bugzilla +[21:36:54] you see it totally wrong +[21:36:57] let me elaborate +[21:37:15] there is a number of guys interested in testing/doing basic qa in kde +[21:37:26] they can 1) follow the kde bugzilla account +[21:37:36] 2) coordinate their efforts in #gentoo-kde channel +[21:37:50] 3) communicate in gentoo-desktop mailing list +[21:37:58] this way you have the following advantages: +[21:38:07] 1) people follow the official gentoo-kde team work +[21:38:23] 2) people use the same communication means as the gentoo-kde team does +[21:38:40] tampakrap: for first 1 you mean add them on kde@gentoo.org ? +[21:38:46] 3) people don't have private communication media, so all of their work is public +[21:39:12] having them to follow the official getnoo-kde work and media makes them closer to the team, thus closer to becoming full getnoo devs which is the goal +[21:39:35] and NO I am not talking about adding them to kde alias, following the kde bugzilla account is different than adding them to the kde alias +[21:40:22] that's all from me, flame on +[21:41:07] ago: i updated the page as we talked about the english +[21:41:32] tampakrap: probably you know that the bureaucreacy in gentoo is not well at all. So the goal here is take advantage of the normal user that using kde and 1) don't like to become a dev 2)don't have the time or don't want follow the ML and IRC +[21:42:11] I strongly disagree here, the procedure in becoming a gentoo developer is one of the best things we have imho +[21:42:26] and I prefer it 100% to the one that for example upstream kde has +[21:42:55] me too, but there are a lot of people that disagree with you and me +[21:42:55] and I still don't see your point, if they don't want to become full developers they won't, noone is pointing guns to heads +[21:43:31] let me explain the point +[21:44:02] if you want become a dev, usually you are interested to follow IRC, bugzilla, ML +[21:44:33] if you are not interested to do it and we say: you must follow them, the response from the user will be: do it by yourself +[21:45:28] and nobody will populate the subproject +[21:45:46] from kde parent herd i want to get feedback of the subproject, if you can handle that i am fine with the non-standard communication +[21:46:23] I see it now, you are creating a project for people that are not interested in becoming gentoo developers +[21:46:34] tampakrap: yes +[21:46:38] and with that project you don't want to motivate or change their mind +[21:46:52] then sorry but I will have to go on the other side an not support your project +[21:47:12] who are interested to do it can start with arch tester or directly with dev +[21:47:15] if people don't care about becoming gentoo developers (which in my little blue eyes means "no interest in the distro") +[21:47:21] then I don't care about them either +[21:48:00] sorry, still disagree with that move +[21:48:06] tampakrap: I'm thinks the same but you need to think at one point. +[21:48:44] If I can 'devolve' to gentoo 2h per day, I can think to become a dev +[21:49:12] If I have not time to do it, but I can help using everyday KDE unstable, I can contribute without lose time +[21:50:01] sorry, don't agree +[21:50:19] and I said why I don't agree, and I don't want to repeat myself +[21:50:55] this is fine, but does not mean we will not do it +[21:50:59] so, good luck with that, I see your point of creating that project, but I am making it clear that I don't want to support it +[21:51:19] no, that means that you are going forward normally, and I will shut up +[21:51:25] ok anything else, beside that? +[21:52:54] tampakrap: we have a lot of way to join gentoo and go to become dev, this is the only one that will not do it. We will see what will happen, and in case change the rules or what is needed +[21:53:00] lets see how this is working when we have the next stable candidate +[21:53:30] 4. EAPI 5 eclass support (15 minutes) +[21:53:41] Discuss the needed changes. +[21:55:13] scarabeus: you are council member and have a good overview about the eclasses and the new features +[21:58:21] sub slots and slot operator deps are new +[21:58:22] johu: you guys dont need to change much +[21:58:58] only the slot operators might be usefull and implemented +[21:59:20] but basically enhancing the eapi case for 5 will break nothing +[21:59:50] ok i will enable it after 492 bump in overlay +[22:00:36] is it implemented in portage yet? +[22:00:42] is there an example of the slot operators? +[22:00:46] Thev00d00: yes +[22:01:32] I was looking at: http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=blobdiff;f=eapi-cheatsheet.tex +[22:01:40] alpha130 and the appropiate ~version +[22:02:49] 5 Bugs (10 minutes) +[22:02:58] dev-util/cmake-2.8.6-r4 - stop Xvfb after failed test phase (bug #406353) +[22:02:58] This occurs because VIRTUALX_COMMAND could be a bash function that dies, and virtualx.eclass does not use nonfatal. +[22:02:58] Discuss the patch - could there be any fallout? +[22:02:59] johu: https://bugs.gentoo.org/406353 "dev-util/cmake-2.8.6-r4 - stop Xvfb after failed test phase"; Gentoo Linux, KDE; UNCO; toralf.foerster:kde +[22:03:47] if you dont disaggree, i think this can be skipped was added by kensington and has already the ack from x11 herd and a user (Franz Fellner) +[22:06:00] silence = ack for the patch? +[22:06:39] no opinion here, didn't look all that closely +[22:07:26] looks sensible to me +[22:08:51] same as creffett +[22:09:04] kde-base/kdebase-pam should use system-local-login instead system-auth in their pam.d files (bug #422495) +[22:09:04] User session is not created when using systemd +[22:09:04] Discuss and vote on proposed changes in duplicated bug (bug #433173) +[22:09:15] johu: https://bugs.gentoo.org/422495 "kde-base/kdebase-pam should use system-local-login instead system-auth in their pam.d files"; Gentoo Linux, KDE; UNCO; egorov_egor:kde +[22:09:17] johu: https://bugs.gentoo.org/433173 "kde-base/kdebase-pam please enable systemd seat using system-local-login"; Gentoo Linux, KDE; RESO, DUPL; eulenreich:kde +[22:09:52] -*- Thev00d00 has no opinion on this one +[22:10:27] has anybody tested if there were any impacts when not using systemd? +[22:10:58] the question is is anybody using systemd and can do the positive test? +[22:14:02] mschiff: is not stable atm I'd say no +[22:16:19] hm] +[22:17:53] ok we will add this after 492 in overlay and ask for testing +[22:18:05] any objections? +[22:18:18] <-- creffett (~creffett@gentoo/developer/creffett) hat das Netzwerk verlassen (Ping timeout: 240 seconds) +[22:19:19] sounds sensible. I guess the guys on the bug can report the positive, we can check without sysd +[22:19:38] go ahead +[22:19:39] johu: no +[22:19:44] ok +[22:20:01] last but not least +[22:20:02] Open floor (15 minutes) +[22:20:11] 6 +[22:20:12] Thev00d00: we will found a way to test :=) +[22:21:34] and i rush for bed i wake up early tmrw +[22:21:36] so cya +[22:21:45] sweet dreams +[22:22:57] --> creffett (~creffett@gentoo/developer/creffett) hat #gentoo-meetings betreten +[22:23:12] i will do the summary (first time in wiki) +[22:23:29] <-- reavertm (~reavertm@gentoo/developer/reavertm) hat das Netzwerk verlassen (Ping timeout: 246 seconds) +[22:23:52] will need feedback because we have to port the old summaries to the wiki after that too +[22:24:48] anything else? +[22:24:55] can't we just link to them? seems like wasted effort toporrt +[22:25:01] to port +[22:25:23] but nope +[22:25:27] i dont want to have 2 places for that... +[22:25:58] you don't, you have a current and an archive :-) +[22:27:23] i will find a minio..eh volunteer for this work +[22:28:35] -*- creffett volunteers kensington +[22:28:51] last chance to raise your voice +[22:29:46] ok next meeting in 3 weeks, maybe with a new stable candidate... +[22:30:49] thanks all meeting is over \ No newline at end of file diff --git a/meeting-logs/20121108.txt b/meeting-logs/20121108.txt new file mode 100644 index 0000000..2735ef7 --- /dev/null +++ b/meeting-logs/20121108.txt @@ -0,0 +1,119 @@ +[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 diff --git a/meeting-logs/20130117.txt b/meeting-logs/20130117.txt new file mode 100644 index 0000000..b01d24d --- /dev/null +++ b/meeting-logs/20130117.txt @@ -0,0 +1,212 @@ +[19:58:11] * dilfridge has changed topic for #gentoo-meetings to: "Gentoo Meetings | FOSDEM talk -> #gentoo-fosdem ! | KDE team meeting 17 Jan 1900 UTC http://wiki.gentoo.org/wiki/Project:KDE/Meeting/2013-1" +[19:58:46] --> creffett (~creffett@gentoo/developer/creffett) hat #gentoo-meetings betreten +[20:04:33] (kde) abcd, ago, alexxy, creffett, dastergon, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 +[20:04:38] 1. roll call +[20:04:46] -*- dastergon is here +[20:04:51] -*- mschiff here +[20:04:52] -*- dilfridge here +[20:05:02] -*- creffett is here +[20:05:50] -*- alexxy partialy here +[20:06:05] wow, we actually reached our minimum for a meeting +[20:06:11] I may faint. +[20:06:35] I'll give a couple more minutes for any stragglers, then we'll get started +[20:08:41] -*- alexxy need some sleep, group theory is cool but... +[20:08:49] I'm here and late :-) +[20:09:04] also cooking ;-) +[20:09:11] good enough for me, let's get this show on the road +[20:09:32] 2. Keywords +[20:09:59] <-- EM3RY (~quassel@204.12.167.10) hat das Netzwerk verlassen (Ping timeout: 248 seconds) +[20:10:07] we dropped ppc64, but do we want to add any stable/testing keywords? +[20:10:36] -*- creffett would be interested in getting arm stabilized at some point +[20:11:38] --> dMaggot (~user@201.227.175.3) hat #gentoo-meetings betreten +[20:13:17] creffett: +1 +[20:15:23] 3. CMake minimum requirement +[20:15:35] kdelibs-4.10 will require CMake 2.8.8 as a minimum. Should we bother enforcing this (given that 2.8.9 is already the lowest version in-tree)? If so, where - kdelibs, KDE eclass, or even CMake eclass? +[20:16:12] err sorry got distracted +[20:16:23] arm is great +[20:16:51] re 3) I'd say kde eclass +[20:16:54] just to make sure +[20:17:21] +1 for 3 +[20:17:48] cmake-utils.eclass says CMAKE_MIN_VERSION="${CMAKE_MIN_VERSION:-2.8.4}" +[20:17:58] maybe it's reallly easiest there +[20:18:09] (change the default min version to 2.8.8) +[20:19:01] sounds good to me, I'll go make that change +[20:19:03] +1 +[20:19:24] +1 +[20:19:44] 4. Bugs +[20:19:56] --> lmiphay (~lmiphay@86-45-44-228-dynamic.b-ras2.prp.dublin.eircom.net) hat #gentoo-meetings betreten +[20:19:58] x11-themes/oxygen-gtk: Rename x11-themes/oxygen-gtk to x11-themes/oxygen-gtk2. Import x11-themes/oxygen-gtk3 from the overlay or we keep x11-themes/oxygen-gtk with 2 slot and rename x11-themes/oxygen-gtk3 to x11-themes/oxygen-gtk. +[20:20:21] basically, split it or slot it? +[20:21:07] what does gnome team say? +[20:21:21] I don't know if we've asked gnome team +[20:21:35] they should know best +[20:21:55] okay, will ask them +[20:21:55] x11-libs/gtk+ itself uses slots.. +[20:22:40] I know that some packages have weird methods of handling gtk+ 2 vs. 3 +[20:22:57] *shrug* +[20:23:12] we'll ask GNOME team about it +[20:23:17] media-libs/qt-gstreamer - split out QtGlib (bug #439198) discuss, vote +[20:23:38] I wrote upstream about that +[20:23:53] and another question I had (basically gstreamer 1.0 support) +[20:24:02] unfortunately haven't got a reply about it +[20:24:09] okay +[20:24:19] I actually have a similar problem +[20:24:29] I'm using gstreamer 1.0 from the gnome overlay +[20:24:37] and haven't been able to update telepathy ever since +[20:25:00] I personally am not in favor, my comments are on the bug but basically I think that it's making things needlessly complex and if upstream eventually does split it out we'll write an ebuild then +[20:25:08] can we differ this decision at least for a coumple of weeks? +[20:25:18] I'll try to ping upstream about this again in the weekend +[20:25:32] sounds good to me +[20:25:41] any further comments on this one? +[20:25:50] I'll take that item and will inform of any updates +[20:26:11] okay +[20:26:19] kde-misc/polkit-kde-kcmodules: Store polkit configuration changes to /etc instead of /usr (bug #438790) Discuss/vote: long-term solution +[20:26:24] -*- creffett shudders at this one +[20:26:53] here, the main question is "what does upstream think" +[20:27:14] there was a thread about it on the release list some time ago +[20:27:18] mhm +[20:27:33] there was no response on the upstream bug itself +[20:27:51] imo nothing but the package manager should ever change anything in /usr +[20:28:33] I think I summarized the responses from the list a couple meetings ago, but the general idea was that a bunch of distros have their own custom patches to change things, and upstream basically said "uh, why are we still doing this if everyone patches it out" +[20:29:41] and sometimes they learn from it and fix it +[20:30:16] and they said that in Frameworks 5 you'll be able to export XDG_CONFIG_DIRS to specify these things +[20:30:32] there are actually two issues here, since kdm does the same thing +[20:31:33] and for that, a number of distros just symlink /usr/share/config/kdm to /etc/kde/kdm +[20:32:33] that's because kdm doesn't use kconfig for its settings +[20:33:00] --> toralf (~toralf@d227155.adsl.hansenet.de) hat #gentoo-meetings betreten +[20:34:16] <-- toralf (~toralf@d227155.adsl.hansenet.de) hat das Netzwerk verlassen (Quit: Konversation terminated!) +[20:34:35] note that all of the proposed solutions were for main KDE, not polkit-kde-kcmodules, the general consensus on that one was "we're not shipping it" +[20:34:41] so...opinions on what to do? +[20:36:30] does it fix a bug? +[20:36:48] https://bugs.gentoo.org/show_bug.cgi?id=438790 +[20:37:50] it has a temporary fix of CONFIG_PROTECT, but no long-term fix +[20:38:36] how about symlinking this to somewhere in /etc? +[20:38:49] could work +[20:38:55] I'll experiment with that and report back +[20:39:19] Change the default DB backend for app-office/akonadi-server (bug #441596) Discuss/vote: there are some comments that the mysql backend brings improved stability/performance +[20:40:03] any input here? this seems like one that needs reavertm's input +[20:40:36] I've found that mysql is much better +[20:40:49] that is on a high power desktop +[20:41:01] but stability wise much nicer +[20:41:29] I am using postgres as backend... but I would not make that the default ;) +[20:41:43] you all know the kde wiki page about this? +[20:41:50] I don't +[20:41:53] moment +[20:42:20] http://techbase.kde.org/Projects/PIM/Akonadi/Database +[20:43:50] okay +[20:44:00] hmm well I would say make mysql default +[20:44:01] only real problem with the "full databases" as mysql or postgresql is that e.g. a laptop crash (dead battery) may leave you with a broken database +[20:44:14] agreed +[20:44:17] but then, you basically only lose a cache, so why bother +[20:44:24] vote: make mysql the default backend? +[20:44:25] +1 +[20:44:27] +1 +[20:44:35] not with goto settings, no +[20:44:42] s/goto/good/ +[20:44:56] mschiff: what do you mean? +[20:45:06] YOu can configure postgres to be safe +[20:45:25] --> tampakrap (~tampakrap@gentoo/developer/tampakrap) hat #gentoo-meetings betreten +[20:45:26] to be protected agains broken database +[20:45:33] hi +[20:45:37] ah ok +[20:45:40] hi dad +[20:45:43] because of battery problem etc +[20:46:02] hi tampakrap +[20:46:36] mschiff: ok so you say, the crash problem is not fundamental +[20:46:43] I had mysql running for quite a long time with akonadi on my laptop and never had an issue with it +[20:46:46] ok +[20:46:48] right +[20:47:23] and I *had* cases where it crashed or I had to switch it off the hard way +[20:47:26] so again +[20:47:31] vote: make mysql the default backend? +[20:47:37] +1 +[20:47:40] +1 +[20:47:50] +1 +[20:47:57] +1 +[20:48:00] cool +[20:48:16] remember changing the default useflag settings in the ebuild... +[20:48:23] I'll note it on the bug +[20:48:37] -*- dilfridge thinks this will improve our relations to the kdepim guys +[20:49:05] is it that bad? 8-) +[20:49:06] dilfridge: and maybe with the improved relations you can do something about kmail? ;) +[20:49:14] sigh +[20:49:20] what do you want, a miracle? +[20:49:39] app-office/akonadi-server-1.9.0: add Qt 5 support (bug #450412) How do we want to start rolling out qt5 support in general? +[20:49:47] I already thought of porting kmail-4.4 to kdepim-4.10 +[20:50:17] I am looking at the git logs of kdepim quite often... they are really doing a lot in fixing bugs since some time... +[20:50:53] our overlay has a kmail-4.4.11.1-r100.ebuild, that is my personal playground +[20:51:03] (does not build right now) +[20:51:05] as I understand it, qt4 versus qt5 has to be global, you can't have both at once +[20:51:29] bastards +[20:51:52] haven't tried qt5 yet (I masked it) but I don't think one blocks the other (in terms of ebuilds, don't know about builds) +[20:52:17] there are some comments in the bug about how you can't have, say, qt5 libs and a qt4 consumer +[20:52:45] question number 1: should we start adding qt5 support? +[20:52:49] right, that's the type of issues I would expect: you probably would have to rebuild everything to use one or the other +[20:53:00] <-- ABCD (~quassel@gentoo/developer/abcd) hat das Netzwerk verlassen (Ping timeout: 245 seconds) +[20:56:02] any comments? +[20:56:18] --> ABCD (~quassel@gentoo/developer/abcd) hat #gentoo-meetings betreten +[20:56:38] how? +[20:57:04] adding the USE flag to packages that have support? +[20:57:05] what? +[20:57:23] but KDE SC itself will not support qt5 right? +[20:57:33] (4.xx) +[20:57:53] did qt team say anything how they want the useflags? eg. either qt4 or qt5, or only a qt5 useflag that disables qt4 support, or... ? +[20:58:09] -*- creffett adds this one to the "talk to other teams" list +[21:00:00] 5. Open floor +[21:00:05] afterwards kde will need akonadi[qt4] or akonadi[-qt5] +[21:00:07] yeah +[21:00:18] someone please tell the qt guys not to be ridiculous +[21:00:29] a category "qt" is a joke +[21:00:30] -*- creffett nominates kensington in his absence +[21:00:43] "qt-base" if anything :D +[21:00:50] no, the joke is suggesting dropping the qt-prefix +[21:01:00] noooo at is much better +[21:01:05] bug 450818 is goint to bite our... well, you know, our feet +[21:01:10] *qt +[21:01:23] qt/core, qt/dbus, etc., etc....sure, let's just drop a bunch of name collisions into the tree +[21:01:33] there's still no nswer fro teh qt team, from qt upstream, etc +[21:03:43] dMaggot: pesa's question should be answered (re: where is it from, has it been upstreamed) +[21:04:47] https://bugreports.qt-project.org/browse/QTBUG-29082 +[21:05:05] <-- ABCD (~quassel@gentoo/developer/abcd) hat das Netzwerk verlassen (Ping timeout: 245 seconds) +[21:06:08] works for me +[21:06:42] creffett: right, I should have updated the bug with that info +[21:06:50] dMaggot: just done +[21:07:00] what else do we have for open floor business? +[21:07:26] cookie distribution +[21:07:36] fine +[21:07:40] cookies to all who attended +[21:07:56] -*- dilfridge munching +[21:07:57] and some cookies for tampakrap's baby +[21:08:10] plasma-active is about half packaged in my local overlay so far +[21:09:03] --> ABCD (~quassel@gentoo/developer/abcd) hat #gentoo-meetings betreten +[21:09:27] I'm still trying to figure out how to package "maliit", which is a dep of one of the packages which provides the input method framework (if anyone has a good example of a package that is configured by way of qmake, please let me know) +[21:10:39] eww +[21:10:42] but other than that it's nearly ready to hit the overlay, though I'm not going to package the patches until the next Active release because they don't apply to latest KDE and I really don't want to respin a few hundred line long patch +[21:10:56] I'll probably be putting it in category plasma-active +[21:11:13] push it! and then write to -dev and request kde-active category... +[21:11:40] it can wait until we've actually tested the packages :) +[21:11:58] plasma-active is less easier understood than kde-active I'd say... +[21:12:09] yeah, but the official name upstream is plasma active +[21:12:20] :| +[21:12:27] eh, we can bikeshed it once I'm finished packaging +[21:12:28] they are really branding specialists +[21:12:48] mhm +[21:13:09] any other business for open floor? we still have time +[21:13:19] kde-plasma-active? +[21:14:08] Is anybody else using the 49.9999 packges? +[21:15:15] mschiff: no but I'm already on .98 +[21:15:25] k +[21:15:34] just for the record +[21:15:58] I had a good time using 4.9.49.9999 and will keep to do so with 4.10 (already do) +[21:15:58] mschiff: kensington: btw the pykde4 patch that I added does not help, I still get a sandbox violation +[21:16:08] in pykde4-4.9.98 +[21:16:20] there is one more commit that could cause it +[21:16:28] -> weekend or anyone else +[21:16:59] kensington is working on porting all python dependencies to python-r1.eclass btw +[21:17:09] nice +[21:19:39] I don't envy him that +[21:20:58] nothing else? /me finds a gavel +[21:21:17] *bam* meeting adjourned +[21:21:27] yeah yeah yeah :) +[21:21:46] ;) +[21:21:53] * dilfridge has changed topic for #gentoo-meetings to: "Gentoo Meetings | FOSDEM talk -> #gentoo-fosdem !" \ No newline at end of file diff --git a/meeting-logs/20130321.txt b/meeting-logs/20130321.txt new file mode 100644 index 0000000..98ea3da --- /dev/null +++ b/meeting-logs/20130321.txt @@ -0,0 +1,368 @@ +[20:02:32] !herd kde +[20:02:32] (kde) abcd, ago, alexxy, creffett, dastergon, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 +[20:02:41] roll call: +[20:02:47] -*- ago obviously here +[20:02:51] * dilfridge has changed topic for #gentoo-meetings to: "Gentoo Meetings | KDE team meeting Thu 21/Mar/2013 19:00 UTC, agenda http://wiki.gentoo.org/wiki/Project:KDE/Meeting/2013-03" +[20:03:00] -*- dilfridge obviously here +[20:03:08] -*- creffett here +[20:03:11] -*- dastergon here +[20:03:39] is needed a minimum number of people to start? +[20:03:44] 5, I think +[20:03:52] not really, more something like a minimum 5min waiting :D +[20:03:57] Do you guys need anything from me? +[20:04:09] ok, we are jmbsvicetto probably a vote for the lead +[20:04:14] err +[20:04:20] s/ok, we are// +[20:04:24] jmbsvicetto: nothing specific I think +[20:04:32] Are we voting for a new lead? +[20:04:44] yes no maybe +[20:04:47] I guess so? +[20:04:49] Shouldn't that have happened on last FOSDEM? +[20:05:12] jmbsvicetto: no +[20:05:14] we should indeed reintroduce that tradition +[20:06:20] ok, next roll call at 19:15 +[20:06:48] --> lmiphay (~lmiphay@86-45-45-142-dynamic.b-ras2.prp.dublin.eircom.net) hat #gentoo-meetings betreten +[20:07:19] kensington, creffett: since you handle the announce of the meeting in the lists, please cc kde-stable next time. +[20:07:29] well, I've been away for a long time, so you're all more qualified than me about the kde issues. I trust your opinion and will go with the majority vote +[20:07:36] lol +[20:07:52] ago: okay +[20:08:10] --> scarabeus (~scarabeus@gentoo/developer/flyingspaghettimonster/scarabeus) hat #gentoo-meetings betreten +[20:08:17] pookaboo +[20:08:24] -*- jmorgan1 here +[20:08:31] whoaa, our flyping spaghetti monster is here? O_O +[20:08:40] even the *flying* ;) +[20:09:25] -*- creffett wonders why we always have such good turnout when someone besides me sends the email :P +[20:09:26] jmbsvicetto: and we too need to plan out delivery of your camera finaly :D i am still walking around it and puting it to various shelfs... it still does not fit into czech republic :D +[20:09:50] scarabeus: hehe +[20:09:52] scarabeus: sorry about that +[20:10:11] scarabeus: If things go as well as I hope, I'll be asking you soon to send it to me ;) +[20:10:20] splendid :-) +[20:11:27] anyway, I'm sorry guys but I need to leave now. Have a good meeting +[20:13:32] ago: roll call no2 ? +[20:14:17] dastergon: just wait another min +[20:14:22] i guess ago is waiting for the clock to strike 20:15 :] +[20:14:52] http://www.portale.it/orario.php :D +[20:14:58] im going to add myself to herd +[20:15:05] any objections? +[20:15:26] !herd kde +[20:15:26] go for it +[20:15:26] (kde) abcd, ago, alexxy, creffett, dastergon, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 +[20:15:30] 2° roll call: +[20:15:30] nope not here, go for it +[20:15:36] -*- ago here +[20:15:38] -*- dilfridge present +[20:15:45] jmorgan1: you can add, but still pretty female would make me more happy :D +[20:15:46] -*- dastergon here +[20:15:46] jmorgan1: you are welcome +[20:15:50] -*- scarabeus around +[20:15:51] here +[20:16:04] <-- ABCD (~quassel@gentoo/developer/abcd) hat das Netzwerk verlassen (Read error: Connection reset by peer) +[20:16:21] --> ABCD (~quassel@gentoo/developer/abcd) hat #gentoo-meetings betreten +[20:16:38] ok, we are 5, we can go ahead? +[20:16:46] ok we're 6, we go ahead +[20:17:06] 1) Project lead (5 minutes) +[20:17:30] any volunteers? +[20:17:32] Last time the vote was between johu_ and scarabeus....so is scarabeus available to do it? +[20:17:38] is there someone else? +[20:17:54] well +[20:18:04] I could, I guess +[20:18:42] creffett: go for it, everyone deserves the hat from time to time :P +[20:18:46] if the only alternative is that the current situation continues, I could do it, but I'm not infinitely happy about it +[20:19:05] creffett: excellent! +[20:19:18] ok, creffett for the lead is fine for me: +1 +[20:19:33] -*- dastergon votes creffett :) +[20:19:37] creffett++ +[20:20:07] jmorgan1: feel free to approve disapprove also if you are fresh here +[20:20:38] i concure +[20:20:40] creffett: take my sentene as ++ for you :-) +[20:20:51] okay then. +[20:20:53] jmbsvicetto: still here for the vote? +[20:21:14] that's a comfortable majority already +[20:21:31] congrats creffett ! +[20:21:36] -*- creffett bows +[20:21:40] autokick in -kde done :P +[20:21:42] cheers +[20:22:09] next point +[20:22:14] 2) KDE 4.10.1 stabilization (10 minutes) +[20:22:46] I'm all for it, it works nicely +[20:22:49] this is a rapid bug search https://bugs.gentoo.org/buglist.cgi?quicksearch=4.10.1&list_id=1622108 +[20:23:05] dilfridge: vincent/peratu reports that does not work for him on ppc +[20:23:20] i filed one bug on ppc64 +[20:23:22] and jmorgan1 reports a failure of rocs +[20:23:24] we should add the kwin (window unref) patch, it is in stable branch +[20:23:26] ;) +[20:23:52] ok, the ppc situation is a big regression +[20:23:59] the rocs problem, we cannot do much about it, it's a gcc ICE +[20:24:16] you should show it to vapier +[20:24:18] https://bugs.kde.org/show_bug.cgi?id=316988 +[20:24:25] 4.9.5 works on ppc/ppc64 +[20:25:00] jmorgan1: could you try gcc-4.7 ? +[20:25:25] sure, for rocs failure? +[20:25:28] yes +[20:25:29] jmorgan1: I usually saw this kind of error on machine with broken hw..how's the status of your? +[20:25:31] ok +[20:25:52] I will check too on my chroot +[20:26:09] yes, i'll look into both hw and gcc-4.7 +[20:26:16] any progress for arm? is the time to do it? +[20:26:55] jmorgan1: is this bug reproducible on ppc64? https://bugs.kde.org/show_bug.cgi?id=316988 you are able to use the session? +[20:27:46] eww +[20:27:50] I know that backtrace +[20:28:17] ago: i'll take a look this evening +[20:28:19] dMaggot: ^ please have a look, does that look familiar to you too? +[20:28:26] dilfridge: checking... +[20:28:38] dMaggot: you are upstream? +[20:29:44] ago: I fixed that crash in other archs +[20:30:07] the question is, why is it still around on ppc? +[20:30:19] or is it a similar but different problem? +[20:30:26] ok, I merged 4.10.1 on 2 machines...looks ok for both...my vote is yes for amd64/x86 and not now for ppc/ppc64/arm +[20:30:40] +1 +[20:30:52] +1 +[20:30:57] -*- ABCD is alive (and forgets when meetings are because they always are when he's normally supposed to be at work) +[20:31:04] sounds good (after adding kwin patch), +1 +[20:31:07] +1 +[20:31:31] +1 +[20:32:02] awesome. +[20:32:03] scarabeus: ? +[20:33:05] next +[20:33:18] wait +[20:33:26] who will open and generate the list? =) +[20:33:31] creffett: could you? +[20:34:00] ago: sure, I'll handle it tonight +[20:34:17] creffett: please also grab the kwin patch from git KDE/4.10 branch +[20:34:20] ah +1 from me +[20:34:28] i am still half page to the log :D +[20:34:33] creffett: ok, please send me and I check it with repoman before open the bug +[20:34:43] will do +[20:34:50] 3) Remove -Wl,--fatal-warnings ??? (5 minutes) +[20:35:16] that's mine +[20:35:20] It gave problems? +[20:35:30] basically we get build failures every now and then +[20:35:40] not frequently, most are on arm +[20:35:40] there have been a couple bugs lately that come from that being enabled +[20:35:56] it will NOT be removed upstream +[20:36:19] -*- dilfridge had a discussion with a couple of kde bigshots about it +[20:36:49] dilfridge: how sounds enable it with a var? +[20:36:49] usually, the linker warning should be fixed in the package, not ignored +[20:36:59] so who has problem is able to drop it +[20:37:35] not easy, because it is fixed in cmake files installed by kdelibs +[20:38:45] technically developer profile should enable it +[20:38:52] we should not enable it on desktop profile +[20:38:54] we could add some magic to the eclass that patches package cmake files and disables it on request, but that may be more pain than before +[20:38:55] ok, I have not particular vote for it, if it is needed, do it +[20:39:14] scarabeus' idea sounds ok, the question is how to best do it +[20:39:41] easiest way would be to conditionally patch kdelibs with a useflag +[20:39:50] that applies to all kde packages then +[20:42:01] -*- creffett is a bit nervous about conditional patching like that +[20:42:04] however that is not really elegant and does not do it "the Gentoo way" +[20:42:24] dilfridge: nope, just remove it from the cmake files +[20:42:30] and then append it in profile ldflags +[20:42:38] but discussion on -dev prior enabling it treewide +[20:42:44] all the linking issues are actual errors +[20:42:49] so fixing them is benefitical a lot +[20:42:56] makes sense +[20:42:58] +1 +[20:43:21] I vote with the majority +[20:43:29] -*- dilfridge thinks we need diego back before we can ever enable it treewide +[20:44:26] dilfridge: the tbox script are public :) +[20:44:40] ok, suggestion by scarabeus: remove -Wl,--fatal-warnings from cmake files and start a discussion to enable it in the dev profile treewide +[20:44:43] opinions? +[20:44:47] +1 from me +[20:45:07] +1 with the majority (as I said) +[20:45:13] you can run tbox stuff yourself, just commit it to qa-reports git repo with proper script calls, the box is done it executes by-cron everything required +[20:45:19] +1 sounds fine with me, disscussion is good +[20:45:30] what is tbox? +[20:45:49] tinderbox +[20:45:59] automated build test system +[20:46:12] +1 from me +[20:46:38] tinderbox the fear of the gentoo dev :P +[20:46:47] creffett: ^ +[20:46:58] cool, i'll look into it +[20:47:07] ago: no opinion +[20:47:09] 0 +[20:47:57] that's three yes and two "0", I guess that is a yes +[20:48:06] ok, scarabeus's suggestion is approved +[20:48:29] scarabeus: mind start the discussion on -dev? +[20:49:37] there is just an update for the ppc crash: https://bugs.kde.org/show_bug.cgi?id=316988#c3 +[20:49:44] does anyone use the dev profile? +[20:50:13] -*- dilfridge looks somewhere else +[20:50:16] creffett: I will ask vincenti if works for him, if yes I can ask qt@ if we can stabilize that version and open the bug +[20:50:40] ago: okay +[20:50:41] jmorgan1: I use default +[20:50:53] jmorgan1: not many, but still you can also add that to the default LDFLAGS in your make.conf +[20:51:00] 4) [semantic-desktop=] (5 minutes) +[20:51:08] <-- dMaggot (~user@201.227.175.3) hat das Netzwerk verlassen (Remote host closed the connection) +[20:51:10] i'll test qtcore upgrade as well, i have both ppc, ppc64 +[20:51:47] ago: no subscription to -dev +[20:51:51] ago: so i can't start the chat +[20:51:55] --> dMaggot (~user@201.227.175.3) hat #gentoo-meetings betreten +[20:52:13] ago: scarabeus: I'll do it +[20:52:34] scarabeus: subscriptions are open :P +[20:52:47] 4) [semantic-desktop=] (5 minutes) +[20:53:03] so the = on semantic desktop was because it was needed due to broken deps +[20:53:10] nowdays it is pointless as everything was fixed +[20:53:14] so you can switch to ? +[20:53:20] ok excellent +[20:53:25] anyone objecting? +[20:54:03] go for it +[20:54:11] maybe we do that with 4.10.2, so nothing big changes before the stabilization +[20:54:11] sounds good +[20:55:04] good +[20:55:14] dilfridge: +1 you right +[20:57:01] have to change rooms, brb +[20:57:10] ok cu +[20:57:12] next on the agenda? +[20:57:27] 5) Remove obsolete news entries +[20:58:12] fine for me. I'd say to leave at least the last 2011-05-22-kdeprefix +[20:58:44] if people haven't upgraded from kdeprefix by now... +[20:58:47] we should remove it, because getting kdeprefix news on a *NEW INSTALLATION* is stoopid +[20:59:10] right to +[20:59:14] o* +[21:00:32] besides kdeprefix use flag was masked since 2009 +[21:00:54] +1 for removing the listed items +[21:01:14] +1 +[21:01:26] +1 +[21:02:47] +1 +[21:03:01] Like +[21:03:56] dastergon: ^ +[21:05:17] +1 from me, cleaning old stuff sound fine +[21:05:28] s/sound/sounds +[21:05:44] ok, next point +[21:05:54] Bugs (10 minutes) +[21:06:08] x11-themes/oxygen-gtk opinion? +[21:06:31] do it the same way as gtk+, i.e. two slots +[21:10:02] sorry I don't understand it at all +[21:10:21] we already have 2 slots in tree, what we should import from the overlay? +[21:10:28] Rename x11-themes/oxygen-gtk to x11-themes/oxygen-gtk2. Import x11-themes/oxygen-gtk3 from the overlay or we keep x11-themes/oxygen-gtk with 2 slot and rename x11-themes/oxygen-gtk3 to x11-themes/oxygen-gtk. +[21:11:29] indeed you are correct +[21:11:59] probably the only thing that should be done here is delete the live ebuild in the overlay +[21:12:11] that bug it was also a topic in January's meeting +[21:12:24] ok, probably we forgot to delete it +[21:12:28] -*- creffett has to move buildings, back in 10 or so +[21:12:55] hmm when I move buildings that usually takes longer, need to find a forklift first... +[21:16:18] ok, probably all of us is busy? I don't see an active partecipation, maybe we want discuss about bugs in the next meetings ? +[21:16:23] err +[21:16:40] ago: just keep pushing :) +[21:16:44] <-- creffett (~creffett@gentoo/developer/creffett) hat das Netzwerk verlassen (Ping timeout: 255 seconds) +[21:18:12] kde-base/kde-meta ebuild improvement proposal (bug #456248, bug #460634) +[21:18:13] dilfridge: https://bugs.gentoo.org/456248 "kde-base/kde-meta ebuild improvement proposal."; Gentoo Linux, KDE; RESO, WONT; voron1:kde +[21:18:16] opinions? +[21:19:04] the attachment is not a diff :P +[21:19:06] wth +[21:19:31] the question has been asked and silence has fallen +[21:20:08] I agree with the quote "if you don't want all kde packages, you shouldn't use kde-meta". +[21:20:32] ok, real diff for all: http://bpaste.net/show/85433/ +[21:20:37] imho we could add (few, 1-2) useflags, as eg. "games" +[21:21:00] nah, too much +[21:21:21] ago: it makes sense if the useflag switches stuff off across several metas +[21:21:24] I agree with jmbsvicetto, so leave as is for me +[21:21:40] --> iamnr3 (~quassel@78.142.111.42) hat #gentoo-meetings betreten +[21:21:40] e.g. disables all games in all packages (not just kdegames) +[21:21:50] but just disabling one sub-meta makes not much sense +[21:21:55] yeah +[21:22:04] so, maybe just leave it as it is now +[21:22:10] +1 +[21:22:34] we can improve documentation to explain that +[21:22:54] or not :D +[21:23:17] scarabeus: ^ ? +[21:23:28] --> creffett (~creffett@gentoo/developer/creffett) hat #gentoo-meetings betreten +[21:24:07] -*- creffett back if meeting is still going on +[21:24:29] we couldn't end the meeting without the lead :p +[21:24:33] creffett: it is... just talking about useflags in metas +[21:24:34] i dont like uses on this +[21:24:37] oh, this one +[21:24:45] but i let you guys pick whatever rocks on your day +[21:24:53] we should prolly just propagate custom sets +[21:24:56] what was our original rationale for "no uses in meta packages"? +[21:25:01] no sets please +[21:26:53] back +[21:27:20] ok I think the best conclusion is "no additional useflags now" +[21:27:43] yes +[21:27:55] 5) +1 - remove old items +[21:28:10] -*- dastergon agrees with dilfridge +[21:29:02] +1 no useflags, I guess +[21:30:33] yo +[21:30:34] next +[21:30:44] Add 'app-arch/unzip natspec' to profiles/targets/desktop/kde/package.use (bug #457934) +[21:30:45] dilfridge: https://bugs.gentoo.org/457934 "Add 'app-arch/unzip natspec' to profiles/targets/desktop/kde/package.use"; Gentoo Linux, Eclasses and Profiles; UNCO; wyatt.epp:kde +[21:31:07] makes sense imho +[21:31:15] go for it +[21:31:22] kensington is adding useflags there anyway +[21:32:02] any further opinions? +[21:32:08] 1, +[21:32:11] 2, +[21:32:14] 3, +[21:32:17] yes +[21:32:18] seems not. +[21:32:20] yes +[21:32:41] ok +[21:32:45] remaining bugs +[21:32:47] dilfridge: is natspec enabled only for the kde profile? +[21:33:09] it would be only for the kde profile, yes, anything else needs discussion with more people +[21:33:40] I guess it should be enabled when people use kde also with other profiles, what do you think ? +[21:33:40] 5 more bugs to go, then we're finished +[21:34:04] ago: well, if we depend anywhere on unzip, we could just depend on that useflag too +[21:34:41] but we don't +[21:34:45] not in kde-base +[21:34:55] i think we should support kde profile not just kde use flag +[21:35:26] ok +[21:35:27] next bug +[21:35:41] Bug 435584 - kde-base/kdelibs - patch to fix directory icon breakage for NFS mounts since KDE 4.7.4 +[21:35:42] dilfridge: https://bugs.gentoo.org/435584 "kde-base/kdelibs - patch to fix directory icon breakage for NFS mounts since KDE 4.7.4"; Gentoo Linux, KDE; UNCO; nitro:kde +[21:36:03] basically nfs and samba are treated as slow filesystems, and icon loading is turned off. +[21:36:12] use reqests to revert that commit +[21:36:35] no real opinion here +[21:37:21] dilfridge: as said, maybe we can discuss this with more people partecipation +[21:37:24] :) +[21:37:26] ok +[21:37:36] in the grand scheme of thigns, I don't think this one matters enough to merit a patch +[21:37:39] I have a proposal as open floor +[21:37:52] so...I'd say resolve wontfix and point out that we already do support epatch_user +[21:37:59] ago: slacker marks for kde meetings? +[21:39:02] dilfridge: ahaha no. the herds contain 14 people, but in the meeting there are always few. So probably we can make a file where someone can say the time preference and in case we can review the meeting time ? +[21:39:10] e.g. kensington is unable to partecipate +[21:42:06] ok shall we close the meeting and continue next month? +[21:42:13] one more item +[21:42:18] open floor ?? +[21:42:28] im looking to stable kde-4.9.5 on ppc64 +[21:42:34] ok +[21:42:48] i think ppc is already stable +[21:43:14] bugs can be assigned to me if needed +[21:43:58] objections? +[21:44:20] jmorgan1: do it to me :) I will handle as kde-stable +[21:44:33] then since it will be stable, you are welcome as ppc64 member +[21:44:40] ago: ok, cool +[21:44:45] oh, to kde-stable? +[21:45:06] you can add as x86_64 too then +[21:45:19] jmorgan1: but, since we will stabilize 4.10.1 in few time and remove 4.9.5, make sense stabilize 495 now? +[21:45:42] well, let me test qtcore upgrade to fix rocs issue +[21:45:51] if that works, then no stable 4.9.5 +[21:45:54] just 4.10.1 +[21:46:14] i'll check in the next 24h or so +[21:46:20] jmorgan1: ok.... +[21:46:21] have an answer +[21:46:42] thx +[21:46:55] dones +[21:48:30] anything else for open floor? +[21:48:36] yeap +[21:48:36] nothing here +[21:48:48] dastergon: go ahead +[21:48:58] last weekend I put up somre repos for qt-gstreamer +[21:49:06] that split the qt-glib thing from qt-gstreamer +[21:49:14] kensington is following on the bug reports upstream +[21:49:20] no news from upstream yet +[21:49:30] for those who didn't know I joined bugday team and I am trying to revive that day +[21:49:59] I'd like to enable the bugday flag in any bugs that you think +[21:50:23] it would be good +[21:50:29] to close them that day +[21:51:55] what do you think about some herd's bugs ? +[21:52:44] -*- dilfridge thinks it's too late to think +[21:52:56] -*- creffett thinks the same, and it's only 5PM here :) +[21:53:30] i think its a good idea assuming the bugday team has reasources to resolve/track them +[21:55:36] i have to drop off - next meeting +[21:57:25] anything else for open floor? +[21:58:35] nope +[21:59:12] I'm good +[21:59:12] ago: wanna close the meeting? +[22:01:21] ok +[22:01:28] -*- dilfridge bangs on the table +[22:01:30] meeting closed \ No newline at end of file diff --git a/meeting-logs/20130523.txt b/meeting-logs/20130523.txt new file mode 100644 index 0000000..7048a7b --- /dev/null +++ b/meeting-logs/20130523.txt @@ -0,0 +1,407 @@ +[21:01:12] Hello +[21:01:16] hola +[21:01:17] I am here +[21:01:23] Hallihallo +[21:01:26] --> scarabeus (~scarabeus@gentoo/developer/flyingspaghettimonster/scarabeus) hat #gentoo-meetings betreten +[21:01:32] sup +[21:01:36] though I may be going soon, so lets get this party started :) +[21:02:50] 1. roll call +[21:03:01] !herd kde +[21:03:01] (kde) abcd, ago, alexxy, creffett, dastergon, dilfridge, jmbsvicetto, jmorgan, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 +[21:03:07] here +[21:03:12] here +[21:03:15] here +[21:03:15] here +[21:03:16] -*- johu here +[21:03:18] -*- alexxy here +[21:03:32] wow, 6 people :D +[21:03:45] +scarabeus +[21:03:53] 2. Optional semantic-desktop support +[21:04:18] Some parts of KDE upstream no longer have optional support for semantic-desktop. We currently work around this by using ugly hacks but it is fragile causing bugs like bug #468104 and bug #465322. It is apparently easy to disable semantic-desktop features at runtime. +[21:04:19] johu: https://bugs.gentoo.org/468104 "kde-base/plasma-workspace-4.10.2 build error with Nepomuk2"; Gentoo Linux, KDE; CONF; christopher.smith:kde +[21:04:24] the herd is populated by 15 people...I wondering if we need to talk about the hour preference of the meeting +[21:04:29] Options: +[21:04:29] Do nothing and add more fixes/hacks as bugs crop up +[21:04:29] Track upstream more closely and support optional semantic-desktop only where supported by upstream (noting that find_package() can be controlled these days unless it explicitly has a REQUIRED) +[21:04:30] Drop semantic-desktop USE flag completely +[21:05:00] ago: wrong topic +[21:05:08] -*- dilfridge suggests "drop useflag completely and focus efforts on more worthwhile issues" +[21:05:09] -*- Thev00d00 votes for: Drop semantic-desktop USE flag completely +[21:05:17] TBH, I have kde on my netbook because of -semantic-desktop, with semantic-desktop enabled it was too much slowly...so I'd like to see it as -is +[21:05:35] ago: just disable the file indexer, then you are fine +[21:05:37] but you can disable it on runtime +[21:05:43] go with dropping +[21:05:47] nowdays it is not so broken +[21:05:50] ok lets vote +[21:05:52] and the off switch finaly works +[21:05:53] I'm also not really using semantic-desktop +[21:06:06] who is for drop? +[21:06:11] -*- ago votes do nothing +[21:06:12] -*- dilfridge is for drop +[21:06:24] -*- johu +drop +[21:06:48] and clearly also scarabeus and Thev00d00 as seen above +[21:06:59] do nothing +[21:07:23] (better would be to kill semantic-desktop, but that isn't an option) +[21:07:27] i guess kensington is for it too because he bring it up on the table +[21:07:36] ok, so lets drop +[21:07:49] jmbsvicetto: the switch now really works, so you have it built but disabled :-) +[21:07:50] ok whats the course of the action then? +[21:07:59] do we need an news item? +[21:08:06] remove the useflag in -4.10.49.9999 +[21:08:15] no in 9999 +[21:08:18] johu: no because no action on user part is required +[21:08:29] scarabeus: yeah and I also should systemd when I build udev, but don't have to use it ... +[21:08:37] -*- jmbsvicetto refrains from making more comments +[21:08:58] -*- dilfridge does not want to hear the word systemd anymore today... +[21:09:00] i would suggest to drop it with 4.11 +[21:09:16] ++ +[21:09:26] we could blog about how to disable it at runtime +[21:09:32] time enough to get the people informed by news item etcs +[21:09:36] dilfridge: good idea +[21:10:18] ok i will blog about it +[21:10:48] we can decide on a news item in the next meeting (june) +[21:11:49] any other actions we need to do for the drop? +[21:12:21] simplify code, afterwards +[21:12:35] check dependencies in external packages +[21:12:54] [semantic-desktop] -> [semantic-desktop(+)] +[21:13:06] (we can already do that now) +[21:13:25] yes +[21:13:47] 3. Drop oldpim? +[21:14:12] yes / no / maybe +[21:14:12] mask now immediately? +[21:14:12] See also this link http://dilfridge.blogspot.de/2013/05/personal-experience-and-opinion-kmail2.html +[21:14:12] against +[21:14:19] yes +[21:14:20] i.e. no +[21:14:36] sorry, -EDON'TCARE +[21:14:36] we do not gain much by dropping it +[21:14:47] -*- Thev00d00 -EDON'TCARE +[21:14:57] (the only real cruft is the -l10- splitting) +[21:15:16] its not much effort to keep it in tree, so also EDON'TCARE +[21:15:19] impact on eclasses is 0 +[21:15:33] real question, is there someone that uses it? +[21:15:42] me :) +[21:15:45] from the comments yes +[21:15:57] --> reavertm (~reavertm@gentoo/developer/reavertm) hat #gentoo-meetings betreten +[21:16:10] dilfridge: what is the state about the bugs you blogged before? +[21:16:21] kleopatra works fine again +[21:16:26] ago: I don't use kdepim and only have parts of it installed because of semantic-desktop +[21:16:34] the other stuff still exists but is nonfatal +[21:16:45] I meant if there is someone apart dilfridge +[21:17:01] only real bug is that you can't set sent mail folder per identity anymore +[21:17:09] --> mschiff (~mschiff@gentoo/developer/mschiff) hat #gentoo-meetings betreten +[21:17:16] ^ ^ +[21:17:51] --> Guest43157 (46c082af@gentoo/developer/creffett) hat #gentoo-meetings betreten +[21:17:54] i would suggest as everytime it comes on table, lets wait until its not working with new kde sc release +[21:18:18] any objections, if not i move to the next topic +[21:18:21] ? +[21:18:41] yep. postpone. if anything pops up, assign bug to me with kde in cc +[21:18:46] <-> Guest43157 heißt jetzt creffett|mobile +[21:19:04] 4. Handling of systemd patches +[21:19:10] let's just agree on a consistent way of handling it (as long as noone from kde team runs systemd) +[21:19:19] I run it +[21:19:23] :) +[21:19:25] Yay +[21:19:25] -*- creffett|mobile is here, sorry. Dinner running late +[21:19:40] i already run it on my netbook +[21:19:43] If there is somthing to test, feel free to cc me everytime +[21:19:43] BUT +[21:20:20] what i miss in the whole discussion is the fact that systemd is about standardization +[21:20:33] and not about boot time +[21:20:36] My general opinion about systemd unit files is that we should wait / let it up to upstream +[21:20:56] and if we add thousands of patches downstream the goal is totally failed +[21:21:03] I personally am unwilling to work on it (kde or elsewhere on Gentoo) +[21:21:19] well +[21:21:33] and we never add patches to add new features in kde packages... +[21:21:45] I'd suggest also to forward upstrem the patch we see in the bugzilla +[21:21:50] let kde upstream handle the stuff +[21:21:53] I also don't like getting tons of bugs to add systemd support to X, Y, Z. Those wanting systemd should be convicing X, Y and Z to support it +[21:22:06] how about "feel free to add patches that have been accepted upstream" +[21:22:50] whats the point to backport this when the release is in 8 weeks? +[21:23:24] dilfridge: If the patch is going to be added by upstream, if someone else (not me) is doing that work and it doesn't break or affect those running openrc, no objection from me +[21:23:56] jmbsvicetto: ++ +[21:24:24] jmbsvicetto: well, that comment was intended as "reply to our systemd guys" +[21:24:35] But people will still complain "I gave you the file, it's trivial to add" +[21:24:42] I use systemd +[21:24:56] I am happy to support the systemd patches/unit files +[21:25:03] possibly with ago +[21:25:16] I think we're running into the same trap as the dev ml +[21:25:24] creffett|mobile: I think that we need to check if thservice start +[21:25:27] We should not worry too much about small support files +[21:25:43] apart kdm do we have a lot of packages that installs an init script? +[21:25:46] but just add them if they are helpful and do not hurt otherwise. +[21:25:49] we dont need to discuss the small unit files.... +[21:26:16] the only thing worth discussing are significant patches for code +[21:26:18] its already added in kde-base/kdm +[21:26:45] and i add the gentoo unit file in upstream bug +[21:26:52] last kdm works for me +[21:28:15] if we start to add not reviewed source code patches i will leave the herd for sure +[21:28:38] its not about systemd, its about the correct way +[21:29:04] johu: we suggest to add the code to kde codereview, if it is accepted then we will include +[21:29:23] ++ +[21:29:26] ++ +[21:29:28] ago: thats what i have done in the bug +[21:29:53] ok let me try to summarize: +[21:30:19] So this means we as a herd from now on will only apply patches that have been accepted upstream? +[21:30:24] johu: and that's the correct way, so let's continue +[21:30:41] but if our packages does not install a init script, we don't need to discuss anymore +[21:31:32] "Small support files as e.g. unit files that affect only systemd but do not interfere with other software can be added locally but should eventually be upstreamed. Patches for adding functionality should be accepted upstream first." +[21:31:41] sounds ok? +[21:32:01] dilfridge: so long as this is not only for systemd +[21:32:01] sound like music +[21:32:01] yes +[21:32:10] good here +[21:32:20] Thev00d00: basically it's already the policy... +[21:32:21] ++ +[21:32:47] refreshing a policy is a good thing +[21:33:01] 5. Bugs +[21:33:16] bug 438790 +[21:33:18] johu: https://bugs.gentoo.org/438790 "kde-misc/polkit-kde-kcmodules: Store polkit configuration changes to /etc instead of /usr"; Gentoo Linux, KDE; IN_P; nikoli:kde +[21:33:27] sigh +[21:33:58] Nothing from upstream yet on that +[21:34:31] didn't other distros patch that? maybe we could attach someone's code to that bugreport... +[21:34:39] By the time they have a fix frameworks 5 will be out and this will be irrelevant +[21:34:40] who was working on that bug, it was in my off time +[21:34:47] Me +[21:34:57] i think this is fixed in fedora +[21:35:52] there was a thread about it on the release-team ml I think (but I dont have my archive here) +[21:36:21] I believe so, but am not sure, and it worries me that most dostros said they don't ship that module +[21:36:46] http://pkgs.fedoraproject.org/cgit/kdelibs.git/tree/kdelibs-4.6.90-kstandarddirs.patch +[21:37:47] err +[21:37:53] that was the link posted in the ml thread +[21:37:54] ... +[21:37:54] how do I get that page to show code? +[21:38:33] maybe they have dropped it in the meantime +[21:38:43] http://pkgs.fedoraproject.org/cgit/kdelibs.git/tree/kdelibs-4.10.0-kstandarddirs.patch +[21:38:46] more useful +[21:38:51] I will try that patch when I return from vacation and we can include it in the next bump +[21:39:22] is there an chance to get it upstreamed? +[21:39:34] we're just falling into our own trap :D +[21:39:39] creffett|mobile: ^ +[21:41:37] Well yeah +[21:41:42] when the bug is not in hurry we could try to get it in before 4.11 +[21:42:17] actually that looks small enough so it's realistic +[21:42:17] But this is a fairly major issue +[21:42:47] And I repeat that most distros do not ship this module +[21:43:01] yes, which lets me wonder why +[21:43:10] (does fedora?) +[21:43:13] yeah we could drop the package... +[21:43:27] -*- Thev00d00 votes drop it +[21:44:24] I think it isn't officially released +[21:45:21] no opinion here +[21:45:28] I vote make it no longer a kdelibs dep +[21:46:07] thats not a complete solution +[21:46:21] either we fix it or we drop it +[21:46:22] what does the package actually do? +[21:47:33] ^ ^ +[21:47:33] i guess you can manage the polkit rules +[21:47:37] Not sure tbh +[21:48:03] so we're going through a lot of pain because of something buggy that noone uses or even knows what it's good for. awesome. +[21:48:39] lastrite? +[21:48:51] vote! +[21:49:11] options? +[21:49:31] 1. get fedora patch upstream +[21:49:45] (and patch polkit-kde-kcmodules as required for that) +[21:50:17] 2. get rid of it +[21:50:34] 3.? +[21:50:53] 3. drop it as kdelibs dependency and drop it to ~arch +[21:51:03] -*- ago votes 1 +[21:51:04] 3 +[21:51:15] -*- dilfridge does not care +[21:51:15] -*- johu votes 1 +[21:51:30] --> creffett (~creffett@gentoo/developer/creffett) hat #gentoo-meetings betreten +[21:51:33] there we go +[21:51:36] much better +[21:51:59] <-- creffett|mobile (46c082af@gentoo/developer/creffett) hat das Netzwerk verlassen (Disconnected by services) +[21:52:12] scarabeus, jmbsvicetto ? +[21:52:24] alexxy? +[21:53:00] I reluctantly vote punt it, with the caveat that we should make sure that punting it doesn't completely hose KDE before we send the lastrite +[21:53:31] not for me to decide +[21:53:38] you guys just voted to have policy upstream first +[21:53:39] :D +[21:53:45] so you cant just rape it right away +[21:53:47] :D +[21:54:00] it was never realy released :P +[21:54:34] ^^ +[21:54:41] perhaps retire it to kde overlay only? +[21:54:50] thats option +[21:54:56] wipe it from stable ebuilds would work +[21:54:58] bugs persists in overlay too +[21:55:05] people shouldn't have this in their world files to start with, the only thing pulling it in is kdelibs +[21:55:22] yes, but for most people it won't matter anymore +[21:55:44] creffett: you started to work on the bug you can decide on you own as lead ;) +[21:56:02] we will cover your decision with full force +[21:56:04] -*- creffett puts his lead hat on +[21:56:16] -*- creffett thinks that we need a nice pope hat or something to mail around between leads +[21:56:18] anyway +[21:56:27] bug 444952 +[21:56:29] johu: https://bugs.gentoo.org/444952 "Add KDE Plasma Active support"; Gentoo Linux, KDE; CONF; creffett:kde +[21:57:02] unless someone seriously objects, I say move polkit-kde-kcmmodules to overlay, remove kdelibs dep, and re-evaluate if and when they get their act together upstream +[21:57:15] creffett: the lead gets a beer stein on the head at fosdem... +[21:57:25] whats the state? why we need to discuss this? +[21:57:29] plasma-active was added to the overlay under kde-active category +[21:57:43] why not kde-base/ +[21:57:48] if anything needs to be discussed, it's basically "when and how to move it to tree" +[21:58:05] scarabeus: no real reason besides it not strictly being part of the KDE SC or whatever they call it these days +[21:58:12] scarabeus: because it's not strictly part of KDE SC? +[21:58:19] nice timing. +[21:58:41] kde-frameworks wont be part of kde sc too.... +[21:58:44] it's not really KDE is the thing, it's a plasma product +[21:59:04] (which is a sub-product of KDE, I know) +[21:59:21] the kde thing is going away anyway... we should already prepare renaming ourselves... +[21:59:21] well how many packages it is +[21:59:28] no new category unless it is more than 10 +[21:59:42] ...9. +[22:00:03] next question, what's a more appropriate category? do we agree that it should go in kde-base? +[22:00:15] kde-active is fine. +[22:00:28] creffett: you could package the telepathy active client... +[22:00:38] then you would have 10 +[22:00:40] hehe, then it's 10 +[22:00:53] that's the other thing, it's not entirely ready because there are a lot of related products that aren't fully packaged yet +[22:00:54] okey you suckers are covered here +[22:00:55] :P +[22:01:04] lets keep it in testing in cvs +[22:01:08] more eyes more bugs +[22:01:18] not ready to be moved yet +[22:01:36] since I haven't had the time to go through all of the stuff on the website listed as "supporting plasma-active" +[22:01:43] oh, and I honestly haven't actually had the chance to test it :P +[22:01:58] my proposal, keep it in overlay +[22:02:08] it completely screws up the display of my laptop, and I don't have a mobile device I can sacrifice to the cause +[22:02:15] make an wiki article/howto and all is fine +[22:02:29] okay +[22:02:39] and maybe even put a little traffic on -desktop for once? :P +[22:02:46] email out a request for testing +[22:02:50] yeah or blog about it +[22:03:16] bug 456750 +[22:03:18] johu: https://bugs.gentoo.org/456750 "kde-base/plasma-desktop[-rss] unintuitive dependency on kde-base/libplasmaclock[-holidays]"; Gentoo Linux, KDE; UNCO; alpine.art.de:kde +[22:03:30] I need to leave. See you guys later +[22:03:42] jmbsvicetto: thanks for your presence +[22:03:48] cu +[22:04:19] I g2g in a minute also, anything else left on the agenda? +[22:04:27] yes bugs +[22:04:40] (and open floor) +[22:04:48] the use should be renamed +[22:04:53] i never understood why we call it rss :D +[22:05:10] scarabeus: propose a name +[22:05:22] -*- creffett has no idea what these use flags actually control +[22:05:23] $(cmake-utils_use_with rss KdepimLibs) +[22:05:29] aha! +[22:05:33] it enables fucking semantic desktop +[22:05:41] just bind it in +[22:05:41] lol +[22:05:44] AHAHA old topic +[22:05:51] then yeah, calendar/semantic-desktop might be more appropriate +[22:05:53] call it semantic-desktop and hard-enable it in 4.11 :) +[22:06:11] just to more spam +[22:06:13] rss? ( +[22:06:13] we get rid of it when we do -semantic-desktop +[22:06:14] $(add_kdebase_dep kdepimlibs 'semantic-desktop?') +[22:06:16] $(add_kdebase_dep libplasmaclock 'holidays') +[22:06:17] ) +[22:06:19] !rss? ( $(add_kdebase_dep libplasmaclock '-holidays') ) +[22:06:20] it was even automagic there :D +[22:06:21] why does holidays actually need a use flag? +[22:06:25] thats reasonf or the - +[22:06:46] creffett: it crashed when you had kdepimlibs without semantic and libplasmaclock and holidays +[22:06:53] ah. +[22:06:55] okay +[22:07:06] ok we will solve it with 4.11 ;) +[22:07:14] i will take of it +[22:07:16] care +[22:07:39] bug 461684 +[22:07:40] johu: https://bugs.gentoo.org/461684 "kde-base/kwin: backport patch to remove tearing on Intel systems"; Gentoo Linux, KDE; UNCO; mike:kde +[22:08:32] yeah do it +[22:08:36] we have this up for discussion because... +[22:08:52] ... because it's large and intrusive +[22:08:57] ah +[22:09:07] that is an absurdly long discussion upstream +[22:09:09] also see https://bugs.kde.org/show_bug.cgi?id=307965 +[22:09:12] "I am not sure if this is a good idea since there is upstream discussion about specifically avoiding KDE/4.10 branch due to the invasive nature of the patch and potential for regressions." kensingtion +[22:09:31] i would vote against it! +[22:09:46] we should just add it into the next 4.10.X release, and if there are problems we could always revbump without the patch again +[22:10:03] so it gets some time in ~arch for testing +[22:10:11] -*- creffett has no opinion here +[22:10:12] Its going to be in 4.11 so any issues will get to use soon enough +[22:10:27] no strong opinion here either +[22:11:21] stay with upstream +[22:11:22] users can always use user patches with kde packages... +[22:11:39] ok let's leave it out then +[22:11:50] mm, true, and we do support userpatch +[22:12:32] bug 468002 +[22:12:34] johu: https://bugs.gentoo.org/468002 "kde-base/kdelibs-4.10.2 ELOG output includes Your homedir is set to ${HOME}/.kde4"; Gentoo Linux, KDE; CONF; rich0:kde +[22:12:38] fast vote +[22:12:40] punt it +[22:12:41] can be removed +[22:12:42] -*- johu ++ +[22:12:44] punt +[22:12:48] kill it +[22:12:52] ok thanks +[22:12:56] -*- Thev00d00 loves the word punt +[22:13:02] on second thought... +[22:13:09] nah, kill it. :) +[22:13:12] bug 468894 +[22:13:14] johu: https://bugs.gentoo.org/468894 "Please restore kde-base/plasma-workspace-4.10.1 because of a bug"; Gentoo Linux, KDE; UNCO; gentoo:kde +[22:13:16] fast vote +[22:13:18] there is absolutely no reason for people to see that message anymore :P +[22:13:27] no +[22:13:31] no +[22:13:31] -*- creffett votes no +[22:13:39] NI! +[22:13:41] also looking forward to the KDE long-term support release :P +[22:13:52] wrong topic :D +[22:14:33] eh, it's related, since it's talking about keeping older versions +[22:15:09] the bug he mentioned was already in 4.9 +[22:15:23] true +[22:15:25] -*- creffett shrugs +[22:15:39] 6. Open floor +[22:15:57] cmake-utils now has inlined patching support in overlay +[22:16:27] going to eapi-bump the last few EAPI < 2 packages myself soon since it's been plenty of time for the maintainers to do it +[22:16:50] which reminds me to remind you to make a tracker out of the monolithic bug mess +[22:17:08] and that reminds me to say "meh, I'm bumping it all myself" +[22:17:33] fine but in the future make TRACKER bugs.. +[22:17:38] will do +[22:18:04] i have at least 2 more topics +[22:18:42] i dont like that kde-stable is not using our mail alias +[22:19:33] all the things that tampakrap mentioned when the sub-projects are true in my opinion +[22:20:10] hmm? anything I missed? +[22:21:03] you can read the log from last october again, its only my opinion no need for action at the moment +[22:22:13] and additionally i had the feeling that the stabilization of 4.10.1 was to early for the 4.10 +[22:22:58] so enough bad vibrations: +[22:23:27] as you may noticed i am back with full force as you may noticed in the last weeks +[22:23:37] who are you, again? ;) +[22:24:50] kensington's offtopic: There is a prototype reviewboard instance setup for use with the KDE overlay[1] +[22:25:01] http://astralcloak.net/~kensington/rb/ +[22:26:12] i would rather see running gerrit gentoo instance for all projects +[22:26:19] *like to +[22:27:02] gerrit++ +[22:27:33] we could ask kensington if he wants to host a test gerrit instance +[22:27:40] to compare +[22:27:43] gerrit is overcomplicated +[22:27:47] imho +[22:28:13] patches of patches of patches +[22:28:21] dilfridge: not really +[22:28:24] worked with both +[22:28:29] and gerrit is actually easier +[22:28:38] for usage on both sides +[22:28:41] reviewer and submitter +[22:28:48] ok +[22:28:53] no opinion here +[22:29:09] in lo i just do "gerrit push" and "gerrit review id" if i feel like not using gui +[22:29:22] and on web interface i can inline comments and approve commits directly +[22:29:28] so i can do that even from tablet +[22:30:21] ok +[22:30:29] so who is setting up a test instance? :D +[22:30:35] lets ask kensington to host a gerrit instance to test it and compare with reviewboard and then decide which we want to push into gentoo infra +[22:30:57] btw did anything come from that gitlab discussion? +[22:31:05] theo didnt mind if someone is willing to maintain it +[22:31:58] hm he should care about his hom(i)e herd +[22:32:24] any other topics? +[22:32:28] nothing here +[22:33:04] FYI git kdenetwork migration is in progress +[22:33:39] thank you all +[22:33:42] meeting closed +[22:33:52] g'nite +[22:34:51] nn +[22:35:02] 'night +[22:35:02] <-- creffett (~creffett@gentoo/developer/creffett) hat #gentoo-meetings verlassen +[22:35:39] nite \ No newline at end of file diff --git a/meeting-logs/20140329.txt b/meeting-logs/20140329.txt new file mode 100644 index 0000000..d8a842a --- /dev/null +++ b/meeting-logs/20140329.txt @@ -0,0 +1,456 @@ + 1. Roll call (5 minutes) + !herd kde +-*- creffett|irssi here + (kde) ago, alexxy, creffett, dastergon, dilfridge, jcallen, jmbsvicetto, jmorgan, johu, kensington, mrueg, mschiff, patrick, reavertm, scarabeus, thev00d00 +-*- scarabeus beeps + hi + pong. +-*- johu here + 2. EAPI 4 kde4.eclasses deprecation (10 minutes) + - KDE overlay is fully migrated to EAPI 5 and all older EAPI's are banned + - No issues known with EAPI 5 + - Discuss and vote + question: I know we've handled this in-overlay, but what's the state of packages in-tree? +-*- jcallen is here + i bumped alot to EAPI 5 + let me check. + (would be nice if pkgcore worked enough to give us the EAPI-by-eclass breakdown) + so its only a question of stable requests and some packages not maintained by us + pkgcore-9999 works good enough now + and it fixed on qa-reports I think + yes qa-reports is fixed + really. + thats why i started to do the tree EAPI 5 work + news to me + we should ban it in the overlay and in the tree once that's cleaned up + kde-base: 21, kde-misc: 20 eapi 4 packages (eapi per cat) + so...bump the requirement in-overlay, news item on -dev or -dev-announce, file bugs? + http://qa-reports.gentoo.org/output/eapi-per-eclass/kde4-base.eclass/4.txt + ^^ most of them have already EAPI 5 rev bumps + cool + then stablereq and request cleanup + yup + around 20th april we can start mass stabilization and see whats left + so eapi4 ban would mean drop kdepim 4.4.x, right? + mrueg: I wish + nope + are those not EAPI 5? + we just bump them to EAPI 5 + yeah + i poked dilfridge about it already and he wants to do it + probably no need for a revbump, tbh + creffett|irssi: just checked for knotes still eapi=4 + kk + creffett|irssi: it's stable packages + kensington: blarg + anyone who wants to keep EAPI 4? + punt it + ok vote: + no need to keep, but what is the need to punt it? + I know it's stable, but I doubt the bump will actually change installed files, and those aren't using any eaapi features, afaik + just progress? + +1 burnintae + *burninate + +1 + mrueg: for 4 -> 5 not much, but eg. it might let us assume subslot support for something in the future + should be fine for 4->5 so +1 + creffett|irssi: we have already subslots implement for kde-base in the eclass + johu: oh, right, forgot about those + revbump it is. + kensington: i just wonder if ebuilds in overlays will fail because eclass disallows in the past, dropping <3 let us clean up a lot of junk from the eclasses + *non-kde + overlays + mrueg: not our problem + they will, that's their problem, we will announce as per usual + we announce it + they fix their own + okay sounds good. :) + +1 + I did a couple of the 'major' ones for the las ttime + we make a tracker for the packages not maintained by us + yup; I can do that if you'd like + creffett|irssi: lets do it after the mass stabilization + it would be nice to get a repoman error if eapi is deprecated for used eclass + okay + mrueg: that would require eclasses have a DEPRECATED_EAPIS sort of variable + which would be nice, admittedly + creffett|irssi: raise that topic in qa please + yep + :) + johu: in portage, actually :P + mrueg: file a bug :) + probably talk to TomWij + or file a bug ;) + will do. + next topic + I would look into it if I had time in the next...two months. + 3. KDE overlay contribution model (10 minutes) + mmkay + - We have a github mirror, which offers pull requests, reviews and comments + - Allows us to get more QA for user contributions + - Proposal: Drop all user ssh keys from overlay and promote the github contribution model (for example with a overlay news item) + - Discuss and vote +-*- creffett|irssi is in favor of switching to github/pullreq model and dropping users' keys + I am against dropping all user ssh keys +-*- mrueg wants to wait until infra deploys gitolite-3 on gogo + mrueg: what offers gitolite-3? + johu: easier mirroring + we should encourage pullreqs for more user contributions, but I think some users is fine to commit directly + kensington: hmm, that's valid + kensington: but where you draw the border + that said, there have been a couple problematic commits as of late + one user drop one not + I don't think we even have a list of who has access + thats easy question for infra... +-*- creffett|irssi asks + right now mirroring means someone with access to both repositories does this on git push and pull, right? + dastergon can probably help with that + mrueg: yes, no server automation is currently supported + so we come back to the question of who we want to have access + infra won't do a hook, and github need to contact their support to have them mirror + kensington: please propose the criteria which user can proceed to commit and who not + imho it should be consistent + the thing is that most commits I've seen have been devs; of non-devs, there have only been a couple committing regularly, and at least one of those has been subpar + iow, we don't have a high non-dev commit rate to start with I think + we could allow only pushes to a non-master branch for users and merge it regularly + it's impossible to have a list of checkboxes + in general, makes enough patches that are good seems like a good rule, it worked in the past + nah just do it simple, they start with pull requests and if they are good they get the commit access directly, if they screw up they loose it + scarabeus++ + good enough for me + that's what we used to do anyway, except with patch on bugzie instead of pull request + but do we keep everyone's access? + also *lose... :D + for those interested: + 13:28 <@a3li> hi creffett|irssi, I'd have this list of additional keys besides all developers for you: caleb christian civil creffett cryos dastergon dessa devurandom dmaggot eliasp genstef helgc + idella4 johu kensington krytzz letharion lxnay mattepiu mrueg mschiff mva okias ronis_br skiarxon spatz sput terietor tgurr travlr wizzleby wohnout yngwin + I...uh..have no idea who half of those people are. + :P + and the other half is people that went on to be devs :p + yup + so do we want to keep all of those? + i raised this topic to make the contribution easier for non-devs and as github is generally accepted i think this is the consistent way + for example clean up wiki page with contribution info + remove hackers file etc etc + yeah +-*- johu thinking in long term to a git migrated tree :D + johu: heh. +-*- creffett|irssi drinks + can anyone add a instruction how to mirror both repositories? + last time i tried to merge a pull request on my own overlay, it went all mad. + so for the moment, any objections to leaving current contributors with access and switching to encouraging everyone else to use github pullreqs? + ++ + fine by me + mrueg: I personally use github "merge on command line" instruction, then rebase and push + otherwise you can merge in github ui, pull, then push to gogo + mrueg: you have to add another remote to you local git clone + kensington, scarabeus: any objections? + jcallen: and you + creffett|irssi: no, since this is the current process anyway :p + kensington, johu: an example gitconfig would be nice. ;) + well, that's a majority + johu: your turn + mrueg: http://bpaste.net/show/195334/ + http://dpaste.com/1763251/ + thanks + looks like i did something wrong here. http://bpaste.net/show/pqp20cn2F7hNvn7aQjWI/ ;) + so please vote on the general plan + I have no problem with cleaning up at least some of the access list, I agree there have been some 'interesting' commits lately + with the exception of not dropping keys at once + +1 + +1 + +1 + ok i will prepare a news item and send it to kde + @ + we can optimize it then + sounds good + next topic + 4. KDE Frameworks 5 (15 minutes) + yay! + Overview: KDE Frameworks + New kde-frameworks eclass needs internal review/feedback. It's not yet ready for -dev ml due to potential major changes for workspaces and applications. + It appears (final strategy not confirmed yet) that rather than one SC as seen in KDE 4 there will be 3 groups released separately: frameworks, workspaces, and applications. We should consider how this should be categorised. kde-frameworks is currently approximately 60 packages, with the potential for future 30+ additional packages. Potential scheme which is consistent with existing categories (see gnustep for -libs precedent): + frameworks -> kde-frameworks/kde-libs + workspaces -> kde-base + applications -> kde-apps + See Naming scheme, Dicuss and vote + wheeeee + what about kde-misc? + people are going to complain about us having three categories. + there's precedent, see gnustep + didn't say no precedent, said there will be complaining ;) + i would follow naming scheme from upstream-> frameworks -> kde-frameworks + a lot of frameworks stuff is designed to be not so kde-specific, so I think they deserve their own category + that said, the suggested split sounds good to me + -workspaces -> kde-workspaces + -applications -> kde-apps + we also may want to consider doing something with kde-misc, but that's a different question for a different day + kde-misc stuff doesn't fit into any of those other categories + kensington++ + I mean more like there's a lot of cruft in there + that I doubt anyone uses + like I said, different question for a different day + yeah, it could use some testing, I last-rited a youtube package in there that is probably broken for years + johu: that means for the mean time 5 categories, right? + kde-apps, kde-base, kde-frameworks, kde-misc, kde-workspaces + I agree with johu, but I think we will get a lot of pushback on -dev + yup. + i think it is a good idea to seperate the release groups + just move the two proposals to -dev + and see how it turns outr + question: when is kde 4 set to stop getting releases + creffett|irssi: when there is a stable kf5 based release + kde-{workspaces,apps} + creffett|irssi: maybe there's also a trinitiy project for that + do we want to support kde sc 4 and kf 5 installed in parallel? + frameworks is about to hit beta, and workspaces is about to hit alpha + kf5 is almost co-installable with kdelibs + kde-runtime will be co-installable, kde-workspace will not + well, at least we have time before the tree move to get flamed + who raises the cat discusion to -dev + ? + just think about a package depending on kwin for example + I would like to have some team agreement, because the runtime/workspaces split is about to happen and I want to package asap + +1 from me + mrueg: kwin will not be co-installable, but not much depends on it anyway + i have no objections, please dont re-introduce a kde-prefix again + also, I volunteer kensington for emailing the ML :P + kensington: just thinking if we want to deal with slots or categories + ooh! + kde-prefix! + so kde-base/kwin:4 or kde-base/kwin because kwin:5 will be in kde-frameworks or somewhere else. + all kde5 stuff is already in slot 5 + vote on: kde-frameworks, kde-workspaces, kde-apps + +1 + +1 + if -dev is against it we should go with kde-apps, kde-libs, kde-base + kde-base for kde4, kde-misc for everything else + probably eclass can use the category to decide which release group the package is + so we don't need anything like TIER=1 inside of the ebuild + mrueg: it's all in split repos + TIER=foo was only for frameworks stuff when it was still in kdelibs + ack + kensington: ah okay + didn't know that :) + anything left to discuss for now on kf5? + yup + lately there was a discussion to merge qt-overlay and kde-overlay? + if anyone has a free moment, check the eclass, there are a few design decisions that could use a review + what about the ebuild naming scheme? + mrueg: i dont see the purpose, the split was decided with the herd split and thats totally fine + johu: i don't know, can't both sides profit from a shared repository? + there's not much crossover + the only commonality, really, is qt5 + mrueg: there was a time where no qt herd exists and the qt stuff was maintained by kde + I actually did not know that + and then the split was decided because of the reason that there is no much crossover + though that explains the large number of qt people in our repo's access list :P + but what would be the drawbacks of a joint repository? + because kde is just one consumer + the effort to merge it and people migrating to it I guess + we have high kde commit rate because of the monthly releases and someone who dont want to have extra kde stuff but newest qt stuff is pushed to get all those changes... + johu: probably we can work on seperate branches and with a joint master branch + naming scheme is important if we end up using kde-base for kde5 stuff +-*- johu is against a re-joined qt-kde repo + mrueg: eww + and if not it would be nice to not have to manually pin ebuilds to a branch they don't match + okay :) + i see we better stay at status-quo :) + kensington++ + so, we can either just update the sets (eg. kde-live pulls in kcalc-9999 and kwin-4.12.49.9999) or make fake versions like 4.9999 + sets sounds more reasonable + ++ + ++ + but this decision is a little bit influenced by the cat discusion on -dev + yeah + yup + also, I think kde-workspaces will end up to be not many packages + maybe kde-base fits here okayish + it's being split into 12 repos, probably only that many packages + kensington: i would suggest to write the -dev mail as soon as possible and then do the reasonable move! + johu: I will wait 1 or 2 days until the split is done, to get an accurate number of packages + if 12 repos = 12 packages, a new category for that will be definitely be rejected + we could discuss this per mail if it is realy urgent and needs a fast decision + johu++ + I will mail a draft to the alias depending on what happens upstream + ++ + ++ + anything left on kf5? + otherwise I guess it will just be kde-frameworks/libs + kde-base + btw kensington thank you for your great work + mhm + btw, mimetypes is fixed upstream in case you didn't see :-) + kensington++ + 5. Bugs (15 minutes) + bug 445392 + johu: https://bugs.gentoo.org/445392 "kde-base/konsole-4.9.3, x11-terms/xterm: backgroundcolor is not reset when scrolling"; Gentoo Linux, Applications; UNCO; toralf.foerster:kde + RESO NOTOURBUG + ++ + c7 + ++ + ++ + hello + i dont want to do upstream work + hi ago + hey ago + sorry for the delay, I had a prob. + good enough, will mark it + bug 456360 + johu: https://bugs.gentoo.org/456360 "kde-base/print-manager looking for org.fedoraproject.Config.Printing"; Gentoo Linux, KDE; CONF; kirelagin:reavertm + erm : bug 445392 vanished away / was solved in the mean while (at least with 4.12.3+4.11.7) + https://bugs.gentoo.org/445392 "kde-base/konsole-4.9.3, x11-terms/xterm: backgroundcolor is not reset when scrolling"; Gentoo Linux, Applications; UNCO; toralf.foerster:kde + toralf: that's good news + johu: that bug confuses me. + printer stuff needs gnome bla to get full working, so there was a proposal to split stuff up + but i got lost by all those user comments + is reavertm around lately? + haven't seen reavertm, no + in the last years not realy + I guess the real solution is to improve the splitting, we can see how other downstreams do it + add a minimal useflag to system-config-printer-gnome and activate that in kde profile by default? + minimal useflag triggers the patch + mrueg++ + it would be cleaner to do the split + but this would be more effort + mrueg: volunteer? + johu: maybe upstream accepts the patch + if eta is 1 month + x, i can take a look at it + otherwise, i'm short on time + it's all one package upstream I think? + i guess yes + bug 482652 + johu: https://bugs.gentoo.org/482652 "[kde overlay] dev-db/virtuoso-server-7.0.0 fails to integrate with akonadi/nepomuk"; Gentoo Linux, KDE; CONF; johannes.hirte:reavertm + do we realy need virtuoso-7? + nope + nepomuk is going away + \o/ + BOOM + lets keep the bug open and then last rite virtuoso when nepomuk is gone... + +1 as virtuoso comaintainer :P + does it work on x86 anyway? + nope + nope! + virtuoso upstream stoped caring about...pretty much anything + so I'm fine with burninating + we can close that bug, there's no new development of nepomuk obviously + 14:22 < johu> mrueg: volunteer? + oops, sorry + stupid putty paste buffer + kensington: yeah but you will always get version bump requests even when it makes no sense + lets move on then + but i am fine with it to drop the stuff + there's still the other bug about it open + bug 490600 + johu: https://bugs.gentoo.org/490600 "kde 4.11.3 missing oxygen theme after update"; Gentoo Linux, KDE; CONF; nikhatzi:kde + this is re-occuring with kstyles/qt updates + what is there that we can do? + how about to just add a einfo/ewarn? + johu++ + yeah + we would need a eclass/portage mechanism to get this proper fixed + I'm still not sure exactly which package is triggering the breakage though + i guess qtgui + bug 497314 + johu: https://bugs.gentoo.org/497314 "No standard directories created after login to KDE"; Gentoo Linux, KDE; UNCO; oldium.pro:kde + kensington: whats to discuss there? + what (if anything) to do + do we want to add a useflag for that? + if we do /etc/skel we have to coordinate with other desktops + kensington: please do + its the proper way + or we can copy the env thing from hnome + copy & paste is dirty + please do the skel way + what package do we put it in? + kde-env + ? + sgtm + sure + we might as well just copy the gnome env file then, it's less copy-and-paste then manually creating a bunch of directories + /usr/portage/gnome-base/gnome-session/files/10-user-dirs-update-gnome-r1 + ok if you say its easier faster and not that dirty, "Just do it" + make it so! + 6. Elect new lead (10 minutes) + i'll have to leave now + !herd kde + (kde) ago, alexxy, creffett, dastergon, dilfridge, jcallen, jmbsvicetto, jmorgan, johu, kensington, mrueg, mschiff, patrick, reavertm, scarabeus, thev00d00 + nominees + I will go again if nobody desperately wants the role + creffett|irssi++ + i nominate johu too + thanks accepted + Xfce has the same code as /usr/portage/gnome-base/gnome-session/files/10-user-dirs-update-gnome-r1 in startxfce4 + at upstream level (where it really belongs) + creffett|irssi, but, but, I was hoping you'd be portage lead...;) + dol-sen: NOPE. + ssuominen: what is your opinion on what we should do, as the resident freedesktop expert :D +-*- dol-sen goes back into hiding in the corner + do we have any more nominees? + i would nomintate dilfridge but i guess he has enough work with council + and he is not here to dis-/agree + yeah + all right + ok do we want to do this via mail? + then let's vote + I have no preference + i have the feeling that to less people are here... + mrueg just left the building + okay, then I'm good with email voting + ++, I have to go too + kensington: got nothing unexpected to say :) I'd add the file like gnome has, but at the same time, also write a patch that does the same and file upstream ticket + creffett|irssi: check please the kde mail alias with herd members...there are some not following the mails + johu: uh, I can't right now, but off the top of my head reavertm isn't on the list + and possibly dastergon? + creffett|irssi: scarabeus too i guess + scarabeus isn't I think + and mschiff maybe too + yeah + so better check + ssuominen: ok, I'll go ahead with that, thanks +-*- creffett|irssi can't do that until tomorrow night + creffett|irssi: yeah lets say let us do the vote within 10 days + kk + 7. Open floor + nothing here + kde 4.12.x target + kensington: the problem is that desktops have started relying upon these directories in very early start, so xdg-user-dirs upstream refused the xdg .desktop autostart file for it, with notes that it would then execute too late in the process + kensington: so thats why we are stuck at calling the executable like this... otherwise i would have added the .desktop file long time ago + johu: .3 then .5 later? + good enough for me + just 5? :D + + whatever kde-workspaces it is + well, probably arch teams will struggle to do .4 as well + do we have any serious blocker left for .3? + not afaik + keywording for minor archs :p + as maintainer we can always decide to drop stable keywords + the problem is we have no stastics who realy uses kde on ppc,ppc64 + every time we try to drop we get a couple people complaining + i dont think it is useless to have them stable, as the kde-stable team has no test plan just a OK and ago only makes build tests on it + I suggest we go ahead with kde-stable asap then CC archs in a week or so + kensington: but the good question is which arches? :) + the current ones, we can discuss dropping them if they are still lagging when we want to remove 4.11 + i dont want to add kde-stable anymore + there is no real benefit from the sub-project + I saw some conflict no previous stable bugs + in either case I think we should be good to CC archs ones the 30 days is up + it is working well here, and there have been no bug reprots + will create a list +-*- johu when nobody cries at home + heh. + anything left for open floor? +-*- creffett|irssi needs to get going, later folks + thanks all + johu: thank you for running the meeting :) + don't forget to review kde-frameworks.eclass, or otherwise be stuck with my awful design until kde 6 :-) + kensington: i always review commits + kensington: kde-misc/akonadi-git-resource for kde overlay + johu: where does it display it? + kensington: extra folder in the left tree view + interesting, I will check it out + oh, kmail... + kensington: http://ctrlv.in/311477 + I will try kmail again with baloo some time + 9999 :) + in my opinion we should rename 9999 to 666 :) \ No newline at end of file diff --git a/meeting-logs/20140810.txt b/meeting-logs/20140810.txt new file mode 100644 index 0000000..fde8e8a --- /dev/null +++ b/meeting-logs/20140810.txt @@ -0,0 +1,389 @@ + 1. Roll call + !herd kde + (kde) alexxy, creffett, dastergon, dilfridge, jcallen, jmbsvicetto, jmorgan, johu, kensington, mrueg, mschiff, patrick, reavertm, scarabeus, thev00d00 +-*- alexxy here +-*- kensington here +-*- johu here too + pong + me too + good 5 is enough to start + 2. kde4-*eclass GCC minimum version (10 minutes) + Please discuss and vote on raising gcc minimum version to 4.7 + Open Bugs: + bug #462550 - [4.6/ICE] sys-devel/gcc-4.6.3 Segmentation fault (program cc1plus) compiling kde-base/rocs-4.10.1 on ppc64 + bug #471770 - =kde-misc/homerun-1.0.0 - fails to build with bug #508324 - kde-base/kig-4.13.0 fails to build with johu: https://bugs.gentoo.org/462550 "[4.6/ICE] sys-devel/gcc-4.6.3 Segmentation fault (program cc1plus) compiling kde-base/rocs-4.10.1 on ppc64"; Gentoo Linux, KDE; CONF; jmorgan:toolchain + johu: https://bugs.gentoo.org/471770 "=kde-misc/homerun-1.0.0 - fails to build with johu: https://bugs.gentoo.org/508324 "kde-base/kig-4.13.0 fails to build with 3rd bug is one of the stable blockers +-*- dilfridge|mobile here + we did it in kde5.eclass and already there was a complaint + kensington: why do people complain? + only one... + nah we do these rises quite periodically + mrueg: because it unconditionally required it for every package + and people complain + but still they should use latest-stable anyway + kensington: okay, i don't consider that relevant. + do it + and gcc 4.7 is stable for >few months + raise it + its bare minimum + so its good to raise it to 4.7 + ok official vote: + or there are some arch that dont support it? +-*- alexxy vote for gcc 4.7 in deps + +1 + +1 + +1 + ok fine + 2. KDE SC 4.13.3 stabilization (15 minutes) + bug #517344 - KDE SC 4.13.3 + KDE Workspace 4.11.11 stabilization + semantic-desktop refactoring (old semantic stack -> nepomuk use flag, new semantic stack -> semantic-desktop use flag): Are we happy with it? Do we need an news item? + Baloo alternate KCM: Now that upstream provides an option to disable indexing in their KCM, do we still want to hack the alternate KCM into the baloo ebuild? + Please discuss and vote to stabilize KDE SC 4.13.3 + https://bugs.gentoo.org/517344 "KDE SC 4.13.3 + KDE Workspace 4.11.11 stabilization"; Gentoo Linux, Keywording and Stabilization; CONF; johu:kde + i would disable the hack otherwise +1 + ack with scarabeus + not sure about news item + Same here + if there is possibility to disable indexing using upstream kcm then there no need to hack alternative one + can we do a news item conditional on installed with -semantic-desktop ? + i dont care about the alternate kcm + i want to punt alternate kcm hack from ebuild, it's still around if someone wants to install it himself + fine by me^ + fine^^ + are we happy about baloo performance? + only have ssd to test on laptop + it's improved over nepomuk + EDONTCARE + any objections to 4.13.3? + no, it's a good target + No + use flag refactoring was OK? + sgtm + ok first vote on the topic: 4.13.3 is our next stable candidate + refactor worked out well, i think everything was converted + ++ + +1 + + + + + ok now about the procedure + kde-stable looks dead to me + no mail after ago's reitrement + so i will add arches directly + so should we dissolve the project? + fine, it's been very quite release in ~arch anyway + which leads to the question which arches @-dev mail about ppc/ppc64 + or can we reactivate them for kde5 somehow? + Talk to pl + ppc + Ask them + who was elected to be lead of the 2 herds? + Imho we don't need ppc stable + But if they want... + johu: jmorgan iirc + Gotta go, have fun... + ok i will contact him when we have the stable list in place + which will require some work to catch up all pkgs about the use flag refactoring + ppc 32 bit is a dead arch + its only exist in routers + don't they need to go stable at the same time anyway? + yes thats why they have to be IN the list + alexxy: ack + so it may be safe to drop them + i will ask them if they want to keep stable keywords + if x86 32bit somehow alive since some still use it + even if there no processors which run only 32bit mode for 10 years + yeah some ppl install still 32 env on 64 systems... + however x86 32bit can be considered dead in quite near future + ok last question in this topic if there is no objections on this. Do we need a news item? + johu: they still wann be paladins and play necromants games + +1 for news item + ++ + + + +1 + there was some confusion about 2 use flags when it hit ~arch + ok volunteer? + users should know or they will scream + kensington: native speaker, you wanna do this? + sure + ok fine, so in some weeks we will have a new stable kde + next topic + 4. KDM (5 minutes) + jmbsvicetto suggested to rethink kde-base/kdm as a dependency in kde-base/kdebase-meta:4, as kdm will not exist after KDE 4 and users might have already migrated to something else. Do we want to add IUSE="+display-manager" with RDEPEND="display-manager? ( || ( x11-misc/lightdm-kde x11-misc/sddm kde-base/kdm ))"? If so, which order? + Please discuss and vote to make kdm optional (and if yes on the proposed solution/order) + kill'em =D + make it optional, add display-manager IUSE, order: not sure about it. + sounds reasonable -> RDEPEND="display-manager? ( || ( x11-misc/lightdm-kde x11-misc/sddm kde-base/kdm )) + kde upstream supposed to use sddm? + right? + for kde5+ + may be it good to create virtual/display-manager + for kde4 let's keep the default the same + yeah the order for kde4 should be untouched + and for :5 i would vote for sddm + as upstream is heavily contributing to sddm + we can worry about :5 later, we don't even have meta packages for it yet + kensington: is on my long todo list + kensington: i'll create them =D + i'm run it @work + anything to add before vote? + tbh dm shouldn't even be pulled in kde 5 meta pacakge; we don't pull in xorg-server + also sddm should work for wayland + that i wanna give a try + on laptop + OK please vote on making dm optional and keep current order untouched for :4 + +1 + +1 + +1 + there is no current order, it's just kdm + just put there or with kdm first + "s/current order/kdm default" + makes more sense kdm use flag then + since kdebase-meta is just a list of kdebase packages + display-manager sounds more generic + and sddm isn't even stable + we just need one stable in the RDEPEND options ;) + thats not the problem + any other opinion about the use flag name? + ok, silence + So please vote on use flag name: a) display-manager b) kdm +-*- kensington doesn't care about flag name + so let's go with display-manager + fine + does it mean kde:4 display-manager? ( kdm ) or display-manager? ( || ( kdm lightdm sddm ) ) +-*- kensington votes for the first one + i'd be okay with both +-*- creffett|irssi here + and i think jmbsvicetto, too. + display-manager + i would say give freedom to the ppl: display-manager? ( || ( kdm lightdm sddm ) ) + iirc he just wanted an option to disable kdm there + Gentoo is all about choices + don't use a meta package for pulling in kdebase packages then + its outlined in our official guide +-*- creffett|irssi passes johu a drink + you can still choose what you want, but the kdebase-meta pulls in all kdebase-packages + wallpapers use flags pulls in kde-wallpapers, not || ( kde-wallpapers gnome-wallpapers ) + ok all arguements on the table? + vote on a) only kdm controlled by the use flag b) even more options, like lightdm sddm gdm? + a + b + a + all those sleeping birds + creffett|irssi, alexxy, scarabeus? + b + b + lightdm[kde] or just lightdm? ;) + come on scarabeus say a then we have a draw + suggest we do || ( kdm virtual/display-manager) then + ++ + += + last chance to object^ + there's no virtual/display-manager ? + 5. Phonon backend (5 minutes) + mrueg: thats an good argument + kensington: where do you find it? + it doesn't exist yet, alexxy suggested to create it + fine by me, but please do it fast as it needs to be stabilized too + otherwise i would vote for kdm only + and do the long track for 4.14 + sgtm + ok next topic, + 5. Phonon backend (5 minutes) + The current default backend is gstreamer, the same as in Kubuntu, and has the greatest number of features. However, upstream now chooses VLC as the default. Should we switch or remain the same? + Please discuss and vote on switching to vlc as default backend + switch to vlc + vlc + vlc + no opinion + p-gstreamer has such a low commit rate + also 1 vlc is nicer than 100 gstreamer-badugly-foo + btw. what about phonon-qt7? + homepage is dead, last snapshot in tree is from 2011 + +vlc + mrueg: if you want last rite it and see what happens + mrueg: i look forward to punting it along with all other unmaintained prefix kde stuff + http://quickgit.kde.org/?p=phonon-quicktime.git looks deadish + kensington: please do so :) + there was complaints last time i tried...but still nobody would even test it + so probably it will disappear when kde4 is gone + kensington: try it again + 6. KDE 5 + a) Categories (10 minutes)[edit] + kde-frameworks has already been approved on gentoo-dev. Plasma 5 is currently 23 packages, should it go in its own category (kde-workspaces?)? If so, we would likely need a new category for applications (kde-apps?) and eventually remove kde-base (and kde-misc?). +-*- kensington doesn't know + why not use kde-misc instead of kde-apps? + kde-frameworks, kde-workspaces, kde-misc + it will have official kde and third party applications in the same category then + kde-plasma? + its the official wording for the DE so why not following it for the category + and then would make kde-apps sense to me + otherwise i would stick to kde-base + kensington: post pone this topic? + i guess + b) Moving to tree (10 minutes) + Qt 5 will be in the tree soon (masked). Are we happy to move KF5 / Plasma 5 after that's done? + kde-workspaces looks better + its good to move +-*- johu is for KF5 tree, plasma 5 overlay when qt5 hits the tree + at least releases + kf5 are nonsence without apps and plasma + so its like all or nothing + its not the best user experience when almost all kde apps are not ported + yeah + but we can keep it masked + that's a feature, not a bug + alexxy: wrong tomahawk already uses a kf + so if someone wanna use it they will + it's expected behaviour to use kde4 apps and porting will be slow + i guess at christmas time big porting will happen + arroundish + will plasma-active get into the tree somewhere in the near future? + oh sorry. + nvm + OK vote 1) When Qt5 hits the the KF5 will be added too + tree + ++ + ++ + johu: kf5 + plasma + otherwise ++ + ++ + (without plasma) + 2) When Qt5 hits the tree Plasma 5 will be added too + -1 + -- + ++ + ++ for plasma-5.1 + 4.0 was the same story + plasma is pretty stable though + but the kde4 apps looking ugly + kensington: is the package splitting done? + kensington: +1 i use it as default DE @work + i didn't notice, maybe we have different themes + only porblem is that it doenst work with 2 monitors + mrueg: which splitting? + and there are a lot of usability issues unresolved + kensington: dolphin:5 etc.? + 2:2 + mrueg: we didn't work on it yet, hoping upstream will split repos + there's not even release schedule yet so we've got some time + i take my lead head on and say lets revisit the topic with 5.1 release + kensington: i'd say get it into the tree, when this is done + we have no hurry to rush at the moment + mrueg: applications are on a different release cycle to plasma + kcalc may well be released at a different time to dolphin eg. + kensington / alexxy are you fine with postpone the plasma decision? + yep + fine, probably 5.1 will be released before qt5 in tree anyway + he he =D + or 6.1.... + 7. Bugs (15 minutes) + first one: 456360 + bug 456360 + johu: https://bugs.gentoo.org/456360 "kde-base/print-manager looking for org.fedoraproject.Config.Printing"; Gentoo Linux, KDE; CONF; kirelagin:reavertm + was this discussed last meeting? + i think so, don't remember the outcome + ok then we need to grep the last log and see what we are going to do + bug 492434 + johu: https://bugs.gentoo.org/492434 "lib-net/libnm-qt should depend on systemd or consolekit (was: kde-misc/plasma-nm should depend on kdm[consolekit])"; Gentoo Linux, KDE; UNCO; cruzki123:kde + not much we can do unless someone volunteers to do the package split + i think it was me to check whats going on, but haven't found time for that + RESOLVED WONTFIX imho as networkmanager already provides those flags + which one actually requires it? libnm-qt or networkmanager + plasma-nm is not useable without consolekit/systemd + but it depends on libnm-qt which depends on networkmanager + and networkmanager already provides the requested use flags... +-*- kensington no opinion + its dependency chain + as plasma-nm is the only consumer of libnm-qt + so libnm-qt should depend on nm with any of this use flags + can't libnm-qt depend on || ( networkmanager[consolekit] networkmanager[systemd] )? + yeah we can add that^ + fine RESOLVED FIXED soon (tm) + bug 497314 + johu: https://bugs.gentoo.org/497314 "No standard directories created after login to KDE"; Gentoo Linux, KDE; UNCO; oldium.pro:kde + kensington: last comment from you + meh + do we even want to do something downstream? + if its a hack no + if its doable without hack fine by me + kensington: what about comment 4? + but at least some progress on this would increase user experienc + sounds good. + mrueg: we can do it, it's kind of hacky but it works + kensington: is this for plasma5 needed too? if yes i would vote for an upstream action! + as we want to get rid of such things + yeah + samuli mentioned /etc/skel solution, i'll ask him about that too + ok lets see if the bug is unresolved next meeting ;) + I dont care about dirs acutaly + bug 497734 + johu: https://bugs.gentoo.org/497734 "www-client/rekonq-2.4.0 should RDEPEND on kde-base/kdebase-kioslaves"; Gentoo Linux, KDE; CONF; rossi.f:kde + kensington: last comment from user responded to your question, so whats left here to get a RESOLVED? + i could reproduce with my config, but not his + so we can 1) add the dep 2) too bad use runtime-meta 3) tell upstream not to use ioslaves to display a blank page + 2) + +3) + or 1) + ok seems i have no opinion on that + does kdebase-kioslaves add many dependencies? + (if you're using gnome and want rekonq as a browser) + not much beyond kdelibs + okay, then 1) + 3) + ^ + ++ + bug 511570 + johu: https://bugs.gentoo.org/511570 "[kde overlay] KDE Frameworks requires gcc 4.5, not 4.8"; Gentoo Linux, KDE; UNCO; matthew:kde + topic 2) revisited for KF5 + well we did raise it to gcc-4.7? + (for kde-4) + 1. too bad 2. conditional on package type + yeah we did + if we raise for kde4 to gcc47 its fine to have gcc48 for kf5 + Is there a need for 4.8? + i guess we would get a lot of bugs if we lower it to gcc45 + why not use 4.7 for both (if it works) + plasma 5 requires 4.8 + ah okay + the 4.8 is fine + thats the reason^ + (just asked because 4.7 is stable, 4.8 is testing) + WONTFIX imho + +1 + 4ю8 шы ашту + sorry + 4.8 is fine +-*- alexxy on 4.9 already +-*- johu too + kensington: did you test kf with 4.5? :) + no, it's just the upstream claim + i don't even have 4.5 installed + 4.5 is too old + i guess nobody will test it from herd as we already on newer + newer version more interesting + kensington: so thats a closing reason for it, we dont have the manpower to support such old setup + bug 514384 + johu: https://bugs.gentoo.org/514384 "cmake-utils.eclass: please deprecate all those fancy cmake-utils_use_*"; Gentoo Linux, Eclasses and Profiles; CONF; mgorny:kde + yeah, it's less relevant anyway since we move to 4.7 + -- + no problem to add the function he wants, but a lot of the existing functions are useful + kensington:++ + same opinion + maybe we can grep to see if there's some old unused function to remove + and dilfridge already expressed his opinion in the bug + yeah do it so + 8 Open floor (15 minutes) + kde member of the month: kensington for his great effort on KF5/Plasma5 and upstreaming + cheers + and next month it may be pesa to get Qt5 into the tree + i did a big reshuffle of cmake-utils in overlay, it tests ok locally for ages so i'd like to move that + it's mostly cosmetic + we are almost done with EAPI4, do we need to announce it on -dev? + <10 pkgs + don't think it's required, maybe some overlay users care + ok i need to leave, my food is ready + Thank you all + johu++ \ No newline at end of file diff --git a/meeting-logs/kde-herd-meeting-log-20071013.txt b/meeting-logs/kde-herd-meeting-log-20071013.txt deleted file mode 100644 index 720381e..0000000 --- a/meeting-logs/kde-herd-meeting-log-20071013.txt +++ /dev/null @@ -1,338 +0,0 @@ -[Sa Okt 13 2007] [20:00:44] Join tgurr has joined this channel (n=tgurr@hbrn-590f7fff.pool.einsundeins.de). -[Sa Okt 13 2007] [20:00:54] !herd kde -[Sa Okt 13 2007] [20:00:57] Philantrop: (kde) caleb, carlo, centic, cryos, deathwing00, genstef, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, troll, vanquirius -[Sa Okt 13 2007] [20:01:00] here? -[Sa Okt 13 2007] [20:01:03] yes -[Sa Okt 13 2007] [20:01:19] Is it 18:00 hours already? -[Sa Okt 13 2007] [20:01:22] yes -[Sa Okt 13 2007] [20:01:24] cryos|laptop: Yes. :-) -[Sa Okt 13 2007] [20:01:33] At least in UTC. :-) -[Sa Okt 13 2007] [20:01:34] 20:00 in germany :) -[Sa Okt 13 2007] [20:01:40] 20:01! -[Sa Okt 13 2007] [20:01:44] I make it 14:01. -[Sa Okt 13 2007] [20:01:58] cryos|laptop: You're *way* behind! ;-) -[Sa Okt 13 2007] [20:02:03] hi all :) -[Sa Okt 13 2007] [20:03:12] Any objections against waiting for two or three more minutes? Deathwing00 told me he would be here. :-) -[Sa Okt 13 2007] [20:03:43] yes -[Sa Okt 13 2007] [20:03:49] * cryos|laptop murmurs about German efficiency :D -[Sa Okt 13 2007] [20:03:52] just start -[Sa Okt 13 2007] [20:05:17] Ok, let's go then. -[Sa Okt 13 2007] [20:05:47] 1. Update to the project page - are we happy with it now that it's been updated? Any additions, etc? -[Sa Okt 13 2007] [20:06:55] i'm happy with it :) -[Sa Okt 13 2007] [20:07:03] We, jmbsvicetto, keytoaster and myself have added what we thought was appropriate and it seems we all agree on it, atm. :-) -[Sa Okt 13 2007] [20:07:29] So that task from the last meeting is done. :-) -[Sa Okt 13 2007] [20:07:50] 2. Review of the project page is done, too, aunless anyone objects now. :-) -[Sa Okt 13 2007] [20:08:11] Nope. -[Sa Okt 13 2007] [20:08:34] 3. Process improvement - NeddySeagoon can't make it today, it seems. -[Sa Okt 13 2007] [20:08:48] It doesn't seem as if much can be done about it anymore anyway... -[Sa Okt 13 2007] [20:09:02] yup -[Sa Okt 13 2007] [20:09:19] 4. Miscellaneous - bump to KDE 3.5.8 -[Sa Okt 13 2007] [20:09:53] As I'Ve mailed to all of you, I've set up a git repository to collaborate on it. So far, jmbsvicetto, Ingmar^, tgurr and myself worked on it. -[Sa Okt 13 2007] [20:10:12] I've gotten exactly zero feedback to my mail about it. :-) -[Sa Okt 13 2007] [20:10:33] Are you manually bumping it? Sorry - I have been mostly offline these last few weeks/months. -[Sa Okt 13 2007] [20:10:49] i couldn't answer because i'm currently not at home and running windows :( -[Sa Okt 13 2007] [20:11:13] cryos|laptop: we've bumped the monolithic ebuilds manually, yes. The splits were initially done by the script and are now being combed through manually. -[Sa Okt 13 2007] [20:11:47] Philantrop: OK - sounds good. We always used to just mask and bump - why the git repo now if I may ask? -[Sa Okt 13 2007] [20:12:20] cryos|laptop: The last bump was critisized by many as rushed and bad. I wanted to avoid that this time. :) -[Sa Okt 13 2007] [20:12:26] Masking allowed us to get the arch teams on board and give them access to the tarballs before release via dev.gentoo.org and gentoo-core. -[Sa Okt 13 2007] [20:12:44] Then we could just unmask after the official release. -[Sa Okt 13 2007] [20:12:46] cryos|laptop: Furthermore, like this, interested users like Ingmar^ could help, too. -[Sa Okt 13 2007] [20:13:01] cryos|laptop: And, of course, we'll put them into the tree and package.mask soon. :-) -[Sa Okt 13 2007] [20:13:26] Philantrop: thanks for your mail, was very good :) -[Sa Okt 13 2007] [20:13:34] Philantrop: is there a release date scheduled yet? -[Sa Okt 13 2007] [20:13:41] Just seems to be making the process more hassle for arch teams to get involved with and interested users can send patches. I have been away so I am mainly asking. -[Sa Okt 13 2007] [20:13:50] genstef: Yes, it's to be released on the 16th. :-) -[Sa Okt 13 2007] [20:14:36] cryos|laptop: Well, yes, they could but why not combine both? We can still do the p.mask/tarball stuff (like tomorrow :-) ) *and* let others help directly. -[Sa Okt 13 2007] [20:14:46] I always worry about the trend towards overlays and separate repos making it harder to see and track stuff. -[Sa Okt 13 2007] [20:14:58] Just my opinion though - I know others like it. -[Sa Okt 13 2007] [20:15:24] cryos|laptop: My main point is: People like Ingmar^ are very, very good dev "material" and training them on the job helps, IMHO. -[Sa Okt 13 2007] [20:15:29] cryos|laptop: right, but this stuff isnot meant to be public by upstream -[Sa Okt 13 2007] [20:15:31] I have very little right to criticise anything due to my recent inactivity anyway. -[Sa Okt 13 2007] [20:16:01] cryos|laptop: No, that's wrong. You have *all* the right to critisize. I'd just like to *convince* you. :-) -[Sa Okt 13 2007] [20:16:15] * cryos|laptop will be quiet - I can see the reasoning. -[Sa Okt 13 2007] [20:16:45] well, but cryos is right. Last time the mail went to gentoo-core and every dev was able to test iirc -[Sa Okt 13 2007] [20:17:19] Anyway, I intend to put the stuff into the tree by tomorow (in p.mask) and inform -core. :-) -[Sa Okt 13 2007] [20:17:25] Any objections? -[Sa Okt 13 2007] [20:17:37] Philantrop: right, sounds cool! Enough time for the arch teams to test then :) -[Sa Okt 13 2007] [20:17:54] genstef: Yes, I hope so. -[Sa Okt 13 2007] [20:18:10] I don't think, though, we'll make it to 2007.1 or do you think we can/should? -[Sa Okt 13 2007] [20:18:25] Into stable, I mean. -[Sa Okt 13 2007] [20:18:34] When is the snapshot date? -[Sa Okt 13 2007] [20:18:37] * genstef does not care about releases -[Sa Okt 13 2007] [20:18:48] everyone runs emerge --sync anyways .. -[Sa Okt 13 2007] [20:18:58] xxxxxxxxxxxx - Initial snapshot -[Sa Okt 13 2007] [20:18:58] xxxxxxxxxxxx - Final snapshot -[Sa Okt 13 2007] [20:18:58] xxxxxxxxxxxx - Release -[Sa Okt 13 2007] [20:19:21] well, imo stable the earlier the better -[Sa Okt 13 2007] [20:19:25] cryos|laptop: ^^^ -[Sa Okt 13 2007] [20:19:34] It would be silly to try and make those dates, but I totally agree with genstef. -[Sa Okt 13 2007] [20:19:40] Stable the earlier the better. -[Sa Okt 13 2007] [20:20:03] but 19th will not happen I think -[Sa Okt 13 2007] [20:20:04] genstef: Yes, same here. I just wouldn't want to tell the release guys now we'll make it and possibly delay them if we don't. Opinions? -[Sa Okt 13 2007] [20:20:11] sorry, we are having dinner now, i'll read the conversation when i'm back -[Sa Okt 13 2007] [20:20:17] ok -[Sa Okt 13 2007] [20:20:36] Philantrop: so we will not make it -[Sa Okt 13 2007] [20:20:50] Philantrop: I wouldn't tell them we would make it - the 9th is too tight a schedule really. -[Sa Okt 13 2007] [20:21:25] In some ways it is a shame - would be good to have 3.5.8 GRPed. -[Sa Okt 13 2007] [20:21:33] Ok, let's say we can *try* but if we don't, the world will not stop spinning. I will *not* inform the release guys about us making it in time. -[Sa Okt 13 2007] [20:21:53] sounds good to me -[Sa Okt 13 2007] [20:21:58] I'm home -[Sa Okt 13 2007] [20:22:02] Sorry for the delay -[Sa Okt 13 2007] [20:22:06] jmbsvicetto: Welcome back! :-) -[Sa Okt 13 2007] [20:22:28] Ok, next point: "Changing to split ebuilds by default? That would mean going through all KDE ebuilds and changing the dependency order." -[Sa Okt 13 2007] [20:22:47] * genstef is against it. -[Sa Okt 13 2007] [20:22:56] * Philantrop is against it, too. -[Sa Okt 13 2007] [20:23:05] But if you must for 4.0, you can -[Sa Okt 13 2007] [20:23:27] I don't see the need but maybe there are other opinions? -[Sa Okt 13 2007] [20:23:34] I would rather see us do it for 4.0 and leave 3.5 well enough alone. -[Sa Okt 13 2007] [20:24:10] yeah, not for 3.x -[Sa Okt 13 2007] [20:24:12] The apache herd screw around lots inside minor releases and it hasn't made them very popular... -[Sa Okt 13 2007] [20:24:21] cryos|laptop: That sounds like a good idea. genstef, what do you think? -[Sa Okt 13 2007] [20:24:31] May be not lots, but when they have it has been painful at times. -[Sa Okt 13 2007] [20:24:33] and better kill monolithic stuff for 4.0 altogether -[Sa Okt 13 2007] [20:24:42] jakub: That's one more point later. :-) -[Sa Okt 13 2007] [20:24:43] jakub: sounds good -[Sa Okt 13 2007] [20:25:04] Philantrop: well, just a suggestion... :) -[Sa Okt 13 2007] [20:25:15] * cryos|laptop adds a here, here. -[Sa Okt 13 2007] [20:25:22] but yeah, messing with the (last?) 3.5.x release in this way will piss off users -[Sa Okt 13 2007] [20:25:36] So, we keep the current dep order for now but change it to split as default for >=4.0? -[Sa Okt 13 2007] [20:26:05] Philantrop: right, because split definitely has advantages, with many patches coming in -[Sa Okt 13 2007] [20:26:19] I would like to see us go to split by default -[Sa Okt 13 2007] [20:26:21] Philantrop: and 4.0 I expect to get many bugreports+patches early :) -[Sa Okt 13 2007] [20:26:23] genstef: Indeed. :-) -[Sa Okt 13 2007] [20:26:34] Philantrop: as said, you really want to keep monolithic stuff for 4.0? -[Sa Okt 13 2007] [20:26:41] sounds just like maintenance overhead to me -[Sa Okt 13 2007] [20:26:49] jakub: hey, leave the lead to Philantrop! -[Sa Okt 13 2007] [20:27:01] genstef: We already get them for the 4.0 overlays. Which leads us to the next point: KDE4 in the overlays. :-) -[Sa Okt 13 2007] [20:27:07] genstef: hey, gimme a beer! :P -[Sa Okt 13 2007] [20:27:17] I can live with split for >= 4.0, though -[Sa Okt 13 2007] [20:27:26] jmbsvicetto: Ok, that's decided then. :-) -[Sa Okt 13 2007] [20:27:30] * genstef paurs some beer into the wire to jakub's glass -[Sa Okt 13 2007] [20:27:44] anyway, the point - users are horrible confused by the blockers b/w monolithic/split, they've never grokked it -[Sa Okt 13 2007] [20:27:52] and really makes the eclasses/ebuilds a mess -[Sa Okt 13 2007] [20:28:08] KDE4 in the overlay is doing well. People are reporting bugs, installing it and using it. We currently have both monolithic and split ebuilds. -[Sa Okt 13 2007] [20:28:40] and you have a special project and channel for it :) -[Sa Okt 13 2007] [20:28:42] jakub: I got a block earlier because I tried to emerge kdesdk-3.5.8 and kdevelop-3.5 -[Sa Okt 13 2007] [20:28:46] Personally, I'd like to keep the monolithic ebuilds. We usually follow upstream and we give our users the freedom of choice. :-) -[Sa Okt 13 2007] [20:28:54] Philantrop: if you could make zmedico into sticking ranged deps into EAPI-1 by the KDE4 release time, that'd be awesome :P -[Sa Okt 13 2007] [20:28:58] jakub: We should really have a way to prevent that -[Sa Okt 13 2007] [20:29:23] jakub: We need ranges and sets -[Sa Okt 13 2007] [20:29:48] jmbsvicetto: well, for sets, you can workaround in a semi-reasonable way by the metabuilds... -[Sa Okt 13 2007] [20:29:52] jakub: That would allow us to drop the meta / meta use flags -[Sa Okt 13 2007] [20:29:54] for ranged deps, the hacks are insane :/ -[Sa Okt 13 2007] [20:30:23] Let's assume for now that we won't get ranged deps/real sets in time for 4.0. :-) -[Sa Okt 13 2007] [20:30:46] Philantrop: gah, torture Zac to do it! :> -[Sa Okt 13 2007] [20:31:25] hehe -[Sa Okt 13 2007] [20:31:27] jakub: :-)) I can't. I only torture soon-to-be devs. Not grizzled veterans. ;-) -[Sa Okt 13 2007] [20:31:34] jakub: I thought your preferred method involved beer ;) -[Sa Okt 13 2007] [20:31:51] jakub: even kegs of beer -[Sa Okt 13 2007] [20:32:01] jmbsvicetto: heh, if that fails, you need something more... effective :D -[Sa Okt 13 2007] [20:32:31] Guys, KDE4 and monolithic ebuilds - to keep them or not to keep them. That's the question. What's your answer? Mine is: Keep them. :-) -[Sa Okt 13 2007] [20:32:56] !herd kde -[Sa Okt 13 2007] [20:33:00] Philantrop: (kde) caleb, carlo, centic, cryos, deathwing00, genstef, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, troll, vanquirius -[Sa Okt 13 2007] [20:33:11] * genstef did not write those -[Sa Okt 13 2007] [20:33:23] so I just go with philantrop on that matter :) -[Sa Okt 13 2007] [20:33:38] Philantrop: As long as we can start the work for split from the meta, we might as well keep them -[Sa Okt 13 2007] [20:33:44] but the splits should be default by then -[Sa Okt 13 2007] [20:33:53] tgurr: Agreed. -[Sa Okt 13 2007] [20:33:53] tgurr++ -[Sa Okt 13 2007] [20:34:23] shrug; you're going to maintain the stuff :P -[Sa Okt 13 2007] [20:34:36] Three times "yes" so far: Philantrop, genstef, tgurr (splits will be default). cryos|laptop? -[Sa Okt 13 2007] [20:34:49] like: kdebase and kdebase-mon? ;) instead of kdebase-meta? -[Sa Okt 13 2007] [20:35:23] I would get rid, but don't object that much to keeping. -[Sa Okt 13 2007] [20:35:24] -mon? :) -[Sa Okt 13 2007] [20:35:25] kdebase is going to be split in two, right? -[Sa Okt 13 2007] [20:35:31] So I vote no. -[Sa Okt 13 2007] [20:35:37] kdebase and kdebase-plasma(?) -[Sa Okt 13 2007] [20:35:59] masterdriverz: Any thoughts? :) -[Sa Okt 13 2007] [20:36:13] cryos|laptop: Thanks, noted. :-) -[Sa Okt 13 2007] [20:37:05] Ok, so it's 3:1 for keeping the monolithic ebuilds for KDE4. -[Sa Okt 13 2007] [20:37:17] Anything else on KDE4? -[Sa Okt 13 2007] [20:37:37] jmbsvicetto: From our side we have runtime, workspace and apps in kdebase -[Sa Okt 13 2007] [20:37:43] * jakub still offers a keg for getting sets and ranged deps in b4 KDE4 :D -[Sa Okt 13 2007] [20:37:51] Sho_: sorry, that's it - kdebase and kdebase-workspace -[Sa Okt 13 2007] [20:38:28] Sho_: That's what Ingmar^ said, iirc -[Sa Okt 13 2007] [20:38:47] jmbsvicetto: ^^ ding ding - motivation above! :) -[Sa Okt 13 2007] [20:38:54] jmbsvicetto: Ingmar^ is a great fan of splitting. He might do even more. :-) -[Sa Okt 13 2007] [20:38:57] :) -[Sa Okt 13 2007] [20:38:57] anyway, /me out for a couple of plops, have fun guys :) -[Sa Okt 13 2007] [20:39:14] Quit tibix_ has left this server (Read error: 110 (Connection timed out)). -[Sa Okt 13 2007] [20:39:17] Ok, the point for KDE4 should be done then. :-) -[Sa Okt 13 2007] [20:39:46] Join tibix_ has joined this channel (n=tibix@host86.200-45-178.telecom.net.ar). -[Sa Okt 13 2007] [20:39:48] Next point: I'm going to document the procedure of bumping to the minor KDE revisions. Any help is welcome. I'll present a draft soon. -[Sa Okt 13 2007] [20:40:05] jakub: If we need you, we'll send you a *SIGBEER* ;) -[Sa Okt 13 2007] [20:40:58] Anything I should take special care of when documenting possible bump procedures? -[Sa Okt 13 2007] [20:42:01] Ok, obviously not. :-) -[Sa Okt 13 2007] [20:42:11] Philantrop: Sorry, but since you're talking about documentation, most people are likely to need some kde4 crash course - in particular to cmake -[Sa Okt 13 2007] [20:42:29] s/most/some/ -[Sa Okt 13 2007] [20:42:31] jmbsvicetto: ok, sounds like a deal :) -[Sa Okt 13 2007] [20:42:56] jmbsvicetto: :-) Well, yes, but there's not much we can do about it, I think. Self-education should be most effective unless you have a better suggestion. :) -[Sa Okt 13 2007] [20:43:40] jmbsvicetto: Unless you want to install a "re-education camp". ;) -[Sa Okt 13 2007] [20:43:46] hehe -[Sa Okt 13 2007] [20:44:13] hmmm, camp... steaks... _beer_ -[Sa Okt 13 2007] [20:44:19] Philantrop++ -[Sa Okt 13 2007] [20:44:21] Well, I guess I'll need to reeducate myself, since I haven't seen kde4 in a while ;) -[Sa Okt 13 2007] [20:44:31] jmbsvicetto: I'll add this to the summary, though. Maybe someone has an idea or helpful link. :-) -[Sa Okt 13 2007] [20:44:52] jakub: I thought more along the lines of a prison camp. ;-) -[Sa Okt 13 2007] [20:44:59] Philantrop: it would be cool to explain why it is best to have the non-working ebuilds in the git to allow external help and afterwards in gentoo-x86 to allow internal testing :) -[Sa Okt 13 2007] [20:45:32] genstef: It doesn't have to be git, just an overlay -[Sa Okt 13 2007] [20:45:46] jmbsvicetto: right -[Sa Okt 13 2007] [20:45:46] genstef: But git is good a choice -[Sa Okt 13 2007] [20:46:10] git would be cool for the portage tree imo. Just pull from external contributors :) -[Sa Okt 13 2007] [20:46:16] well, * >> cvs :) -[Sa Okt 13 2007] [20:46:36] genstef: You know how the cvs/svn/git/* debate ended last time ;) -[Sa Okt 13 2007] [20:46:48] genstef: We don't *have* to do it in a git repository for all times. This was just one approach. :-) -[Sa Okt 13 2007] [20:47:07] jmbsvicetto: well yeah, it's not gonna get anywhere... -[Sa Okt 13 2007] [20:47:11] jmbsvicetto: ok, better not discuss it then ;) -[Sa Okt 13 2007] [20:47:20] jmbsvicetto: we'll be stuck w/ cvs until we switch infra first -[Sa Okt 13 2007] [20:47:53] jakub: I wouldn't say that. I think robbat2 is close to accept git -[Sa Okt 13 2007] [20:48:06] !herd kde -[Sa Okt 13 2007] [20:48:09] Philantrop: (kde) caleb, carlo, centic, cryos, deathwing00, genstef, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, troll, vanquirius -[Sa Okt 13 2007] [20:48:09] switch infra! -[Sa Okt 13 2007] [20:48:10] Anything else we should discuss? :-) -[Sa Okt 13 2007] [20:48:11] jakub: He has worked on it to supress the shortcommings -[Sa Okt 13 2007] [20:48:16] * jakub really out now... oh btw, getting the new eclasses eclass-manpages friendly would be nice :) -[Sa Okt 13 2007] [20:48:26] jakub: Yes, that's in the making. :-) -[Sa Okt 13 2007] [20:48:48] Philantrop: if you want help, poke me ;) -[Sa Okt 13 2007] [20:48:55] Philantrop: What about the cmake eclass? -[Sa Okt 13 2007] [20:49:00] jakub: Thanks, I surely will! :-) -[Sa Okt 13 2007] [20:49:26] jmbsvicetto: We have one more showstopper in it: cmake-utils-src_test. We need to work on that before I re-submit it. -[Sa Okt 13 2007] [20:49:26] Philantrop: Has it been merged to Portage or is it still on the overlay? -[Sa Okt 13 2007] [20:49:36] jmbsvicetto: It's still in the overlay only. -[Sa Okt 13 2007] [20:49:37] Philantrop: Oh and one final issue - ATs/HTs! -[Sa Okt 13 2007] [20:49:43] waah, cmake.eclass is not yet in the tree? -[Sa Okt 13 2007] [20:49:56] urrx, should be imo -[Sa Okt 13 2007] [20:50:12] genstef: Unfortunately, no. People had lots of suggestions. We've done most of it but that one remains. -[Sa Okt 13 2007] [20:50:28] genstef: I'm going to try to get it in next week, though. -[Sa Okt 13 2007] [20:51:45] jmbsvicetto: ping -[Sa Okt 13 2007] [20:51:55] The problem is: cmake-utils' src_test is mostly a copy of the one in ebuild.sh but we currently need it to check whether it's an in-source or out-of-source build. -[Sa Okt 13 2007] [20:52:05] Any help on this would be greatly appreciated. -[Sa Okt 13 2007] [20:52:37] jmbsvicetto: "ATs/HTs". What's your suggestion about them? -[Sa Okt 13 2007] [20:52:51] Well, glep41 http://www.gentoo.org/proj/en/glep/glep-0041.html created ATs and HTs -[Sa Okt 13 2007] [20:53:01] jmbsvicetto: so, config ata is sompiled into the kernel, same as config ide -[Sa Okt 13 2007] [20:53:03] I think kde would benefit from having a HT team -[Sa Okt 13 2007] [20:53:10] jmbsvicetto: Yes, but it has been rejected by the council in its current state. :) -[Sa Okt 13 2007] [20:53:19] shade: We're in the middle of a meeting. Give us a few minutes, ok? Thanks -[Sa Okt 13 2007] [20:53:34] Philantrop: Not rejected. It hasn't been implemented -[Sa Okt 13 2007] [20:53:36] jmbsvicetto: ok, np:) -[Sa Okt 13 2007] [20:53:51] Philantrop: And ATs get official recognition -[Sa Okt 13 2007] [20:53:55] jmbsvicetto: I thought so, too. Look at the relevant meeting's log, though. :) -[Sa Okt 13 2007] [20:54:21] Philantrop: What hasn't been accepted is the @g.o email addresses. Everything else was accepted -[Sa Okt 13 2007] [20:54:32] Philantrop: So, can I be a kde ht? -[Sa Okt 13 2007] [20:54:40] We use HTs in the sci herd quite successfully. -[Sa Okt 13 2007] [20:54:42] jmbsvicetto: There's nothing to say against Herd Testers, though. :-) -[Sa Okt 13 2007] [20:54:57] Philantrop: Pretty, pretty please? -[Sa Okt 13 2007] [20:55:04] ;) -[Sa Okt 13 2007] [20:55:05] cryos|laptop: Oh? That's good to know. Never heard about them before. :) -[Sa Okt 13 2007] [20:55:05] I got them boosted bugzilla powers and access the overlay. -[Sa Okt 13 2007] [20:55:23] Philantrop: Quite a few went on to become devs later too. -[Sa Okt 13 2007] [20:55:32] cryos|laptop: How's the procedure to make them HTs? -[Sa Okt 13 2007] [20:55:55] I think I was supposed to make a web page about this stuff. -[Sa Okt 13 2007] [20:56:01] cryos|laptop: :-)) -[Sa Okt 13 2007] [20:56:05] Philantrop: Anyway, "personally" I won't gain anything I don't have yet, with the exception of showing up in the kde team page. But other people could get official recognition -[Sa Okt 13 2007] [20:56:27] jmbsvicetto: Well, there's precedent, it seems and it makes sense... -[Sa Okt 13 2007] [20:56:31] I just used to talk to someone who I have forgotten now who was in charge of the AT project about getting bugzie sorted. -[Sa Okt 13 2007] [20:56:34] yeah, I like the idea -[Sa Okt 13 2007] [20:56:41] cryos|laptop: hparker ;) -[Sa Okt 13 2007] [20:56:43] cryos|laptop: That would be hparker. -[Sa Okt 13 2007] [20:56:48] Yes jmbsvicetto! -[Sa Okt 13 2007] [20:56:54] cryos|laptop: hparker -[Sa Okt 13 2007] [20:56:57] It has been a while :) -[Sa Okt 13 2007] [20:57:08] So, do we want Herd Testers? I support the idea. Others? -[Sa Okt 13 2007] [20:57:20] I think it works well and would support the idea. -[Sa Okt 13 2007] [20:57:35] cryos|laptop: s/would/will/ !!! ;) -[Sa Okt 13 2007] [20:57:57] masterdriverz, tgurr: Your vote? -[Sa Okt 13 2007] [20:58:04] sure :) -[Sa Okt 13 2007] [20:58:08] It is a great chance for people to get a bit of a taste of being a dev and decide if it is for them. Some only ever want the HT position and others drift away again,. -[Sa Okt 13 2007] [20:58:43] Means when people go on to become devs they are usually more certain about actually wanting to do it too. -[Sa Okt 13 2007] [20:58:56] Ok, so we have four "yes" (genstef, cryos|laptop, tgurr, Philantrop) and no objections. :-) -[Sa Okt 13 2007] [20:59:04] cryos|laptop: Yes, sounds really good to me. :-) -[Sa Okt 13 2007] [20:59:21] I'll talk to hparker about it. -[Sa Okt 13 2007] [20:59:24] so we need some amendment to the project page about that, right? -[Sa Okt 13 2007] [20:59:39] genstef: Yes, thanks for volunteering! ;) -[Sa Okt 13 2007] [20:59:45] including the procedure of how a herd member goes about promoting someone to HT :) -[Sa Okt 13 2007] [20:59:50] ok :) -[Sa Okt 13 2007] [20:59:58] genstef: You would add a section listing the HT members and some documentation on how to become one -[Sa Okt 13 2007] [21:00:06] right -[Sa Okt 13 2007] [21:00:29] genstef: So you'd be willing to make a draft for that? Maybe for the next meeting (or earlier)? :) -[Sa Okt 13 2007] [21:00:30] genstef: I'm probably going to have to do something similar for sparc ATs, so if you want, I can work with you on that -[Sa Okt 13 2007] [21:01:02] jmbsvicetto: ok, cool! -[Sa Okt 13 2007] [21:01:14] Philantrop: will send it to kde@gentoo.org then -[Sa Okt 13 2007] [21:01:27] genstef, jmbsvicetto: Thanks, guys! I'll add that to the summary, too. -[Sa Okt 13 2007] [21:01:44] Anything else, gentlemen? -[Sa Okt 13 2007] [21:02:43] Philantrop: About six-sigma, are we still interested in trying it on kde? -[Sa Okt 13 2007] [21:02:55] Philantrop: If so, do we leave that for a future meeting where NeddySeagoon can help? -[Sa Okt 13 2007] [21:03:12] jmbsvicetto: Good question. Opinions? -[Sa Okt 13 2007] [21:03:36] six-sigma? -[Sa Okt 13 2007] [21:04:07] tgurr: Oh, right. That was before your dev time. It's a process improvement thing. -[Sa Okt 13 2007] [21:04:25] tgurr: I'll forward you a mail about it. -[Sa Okt 13 2007] [21:04:47] re -[Sa Okt 13 2007] [21:05:00] I'd say we invite Neddy to our next meeting and see about it then. Any objections? -[Sa Okt 13 2007] [21:05:07] Philantrop, thanks :) -[Sa Okt 13 2007] [21:05:14] keytoaster: Welcome back! :-) -[Sa Okt 13 2007] [21:05:27] :) -[Sa Okt 13 2007] [21:05:29] Anything else? -[Sa Okt 13 2007] [21:06:29] I'll make a summary of our meeting and export a log from Konversation. I'll mail it around to kde@g.o and if it's fine, I'll ask keytoaster to add it to our project page. Ok? -[Sa Okt 13 2007] [21:06:33] Philantrop: Maybe just a heads-up about next meeting date? -[Sa Okt 13 2007] [21:06:39] Philantrop: thanks :) -[Sa Okt 13 2007] [21:06:41] Philantrop: sure -[Sa Okt 13 2007] [21:07:08] If I'm not mistaken, next meeting will take place at 13/11 -[Sa Okt 13 2007] [21:07:28] Ok, then. The next meeting will take place on November, 10th, 2007 at 18:00 UTC here in #gentoo-kde. :-) I'll mail reminders again and poke you guys on IRC whereever I find you. :-) -[Sa Okt 13 2007] [21:08:04] Sorry, 10/11 -[Sa Okt 13 2007] [21:08:15] Philantrop, uhm, could we do that on another date -[Sa Okt 13 2007] [21:08:25] keytoaster: What's wrong with that date? :-) -[Sa Okt 13 2007] [21:08:43] i just found out that my family visits my friend every second saturday of the month as well... -[Sa Okt 13 2007] [21:09:02] so we'll probably be having dinner at this time, just like today -[Sa Okt 13 2007] [21:09:14] so i will most likely never be able to attend the whole meeting -[Sa Okt 13 2007] [21:09:17] first saturday then? :) -[Sa Okt 13 2007] [21:09:22] fine for me -[Sa Okt 13 2007] [21:09:28] hehe -[Sa Okt 13 2007] [21:09:32] !herd kde -[Sa Okt 13 2007] [21:09:35] Philantrop: (kde) caleb, carlo, centic, cryos, deathwing00, genstef, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, troll, vanquirius -[Sa Okt 13 2007] [21:09:45] Shall we move our meetings to the first Saturday each month? -[Sa Okt 13 2007] [21:09:48] first saturday is bug day, but fine with me ;) -[Sa Okt 13 2007] [21:10:42] cryos|laptop, genstef, keytoaster, masterdriverz, tgurr? First Saturday each month from November on? -[Sa Okt 13 2007] [21:10:51] yes -[Sa Okt 13 2007] [21:11:07] Yes. -[Sa Okt 13 2007] [21:11:17] fine to me -[Sa Okt 13 2007] [21:11:44] Anyone objects having a note on the project page about the "usual" meeting time? -[Sa Okt 13 2007] [21:12:01] In case any interested party wants to follow the meetings -[Sa Okt 13 2007] [21:12:12] If I didn't misread genstef he doesn't object to it either so that would be 5:0 in favour of moving it. :-) -[Sa Okt 13 2007] [21:12:54] keytoaster: Could you add a note about the 1st Sat every month as our meeting time? -[Sa Okt 13 2007] [21:13:28] yup -[Sa Okt 13 2007] [21:13:53] It's decided then: The next meeting will take place on November, 3rd, 2007 at 18:00 UTC here in #gentoo-kde. :-) -[Sa Okt 13 2007] [21:14:05] i'll do it as soon as i'm home -[Sa Okt 13 2007] [21:14:12] keytoaster: Sure, no worries. :-) -[Sa Okt 13 2007] [21:14:30] !herd kde -[Sa Okt 13 2007] [21:14:31] Philantrop: (kde) caleb, carlo, centic, cryos, deathwing00, genstef, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, troll, vanquirius -[Sa Okt 13 2007] [21:14:32] Anything else for tonight, guys? -[Sa Okt 13 2007] [21:15:16] Can't recall anything else -[Sa Okt 13 2007] [21:15:37] Ok, thanks to all of your for attending. It's great this works and I really appreciate your feedback and help! -[Sa Okt 13 2007] [21:15:46] s/your/you :-) -[Sa Okt 13 2007] [21:15:52] Philantrop: well, I wonder about a kde lead? I think we decided last time about it, but cannot find anything on the project page? -[Sa Okt 13 2007] [21:16:03] genstef: We didn't decide about it. :) -[Sa Okt 13 2007] [21:16:30] genstef: I think we decided to *not* decide ;) -[Sa Okt 13 2007] [21:16:41] We could decide about it, of course. -[Sa Okt 13 2007] [21:16:46] Philantrop: some note like "we do not have a lead: decisions can be made by everyone but it usually it is a good idea to ask philantrop because he is around and knowledgable" -[Sa Okt 13 2007] [21:17:46] I would like to propose we select a lead for kde and I want to suggest Philantrop -[Sa Okt 13 2007] [21:17:46] anyways, not that important .. -[Sa Okt 13 2007] [21:18:48] Does anyone want to open up the election process? -[Sa Okt 13 2007] [21:18:58] jmbsvicetto: totally against it -[Sa Okt 13 2007] [21:19:05] we already decided on the matter :) -[Sa Okt 13 2007] [21:19:13] it just needs to be reflected on the project page -[Sa Okt 13 2007] [21:19:14] Against the lead or the election? ;) -[Sa Okt 13 2007] [21:19:19] Ah, ok :) -[Sa Okt 13 2007] [21:19:38] you said what we decided -[Sa Okt 13 2007] [21:19:42] :) -[Sa Okt 13 2007] [21:19:51] genstef: We'll add the note as you suggested to the project page. :-) -[Sa Okt 13 2007] [21:19:56] keytoaster: Mind to add a note to the page? ;) -[Sa Okt 13 2007] [21:20:11] Philantrop: We should also send a mail to -core or -dev announcing it -[Sa Okt 13 2007] [21:20:20] give me a complete text :) -[Sa Okt 13 2007] [21:20:40] keytoaster: look a few lines a bove the long text. -[Sa Okt 13 2007] [21:21:00] keytoaster: "We do not have a formal lead: Decisions can be made by every herd member but it usually is a good idea to ask philantrop because he is around and knowledgable." -[Sa Okt 13 2007] [21:21:41] ah, k, thanks -[Sa Okt 13 2007] [21:22:17] Ok, final call: Anything else? :-) -[Sa Okt 13 2007] [21:22:18] possibly close to the members box -[Sa Okt 13 2007] [21:22:34] keytoaster: Directly above the box, I'd say. :-) -[Sa Okt 13 2007] [21:24:28] I'm off then, ok? -[Sa Okt 13 2007] [21:25:00] Ok, let's call this meeting closed! Thanks again! :-) diff --git a/meeting-logs/kde-herd-meeting-log-20080306.txt b/meeting-logs/kde-herd-meeting-log-20080306.txt deleted file mode 100644 index acda721..0000000 --- a/meeting-logs/kde-herd-meeting-log-20080306.txt +++ /dev/null @@ -1,518 +0,0 @@ -[Do Mär 6 2008] [20:30:29] !herd kde -[Do Mär 6 2008] [20:30:31] Philantrop: (kde) caleb, carlo, cryos, deathwing00, genstef, ingmar, jmbsvicetto, keytoaster, masterdriverz, mattepiu, philantrop, tgurr, zlin -[Do Mär 6 2008] [20:30:32] ping ^^^ -[Do Mär 6 2008] [20:30:37] evening :) -[Do Mär 6 2008] [20:30:38] pong -[Do Mär 6 2008] [20:30:50] :> -[Do Mär 6 2008] [20:31:14] ctennis == caleb -[Do Mär 6 2008] [20:31:19] meh -[Do Mär 6 2008] [20:31:24] ctennis: Yes, thanks, I know. :-) -[Do Mär 6 2008] [20:31:32] just making sure everyone else did :) -[Do Mär 6 2008] [20:32:05] bzzzzz -[Do Mär 6 2008] [20:32:09] * gentoofan23 guessed -[Do Mär 6 2008] [20:33:02] jmbsvicetto, masterdriverz, genstef around? :-) -[Do Mär 6 2008] [20:33:11] * cryos|laptop had no clue... -[Do Mär 6 2008] [20:33:22] Mode ChanServ gives channel operator privileges to deathwing00. -[Do Mär 6 2008] [20:33:28] Mode deathwing00 gives channel operator privileges to you. -[Do Mär 6 2008] [20:33:34] Mode deathwing00 gives masterdriverz the permission to talk. -[Do Mär 6 2008] [20:34:20] Ok, let's start guys! :-) First on the agenda is the bump to 3.5.9 which was somewhat, bumpy... ;) -[Do Mär 6 2008] [20:34:24] Mode deathwing00 gives ctennis the permission to talk. -[Do Mär 6 2008] [20:34:44] deathwing00: Thanks, but this will be open floor anyway. :-) -[Do Mär 6 2008] [20:34:50] ok -[Do Mär 6 2008] [20:35:29] We have one major issue open: Split and monotlithic ebuilds. Split ebuilds depend hard on split dependencies and won't accept monolithic ebuilds. -[Do Mär 6 2008] [20:35:45] Some of us want to change that, some others don't. Your opinions? -[Do Mär 6 2008] [20:36:33] Well, doesn't it depend on the program? Some could do a || dep on split/monolithic and some can't, right? -[Do Mär 6 2008] [20:37:25] gentoofan23: No, not really as basically any monolithic ebuild would install what its split packages would. -[Do Mär 6 2008] [20:37:43] But we're talking about kde-base/* only here. -[Do Mär 6 2008] [20:38:10] My opinion is that we should opt to drop monolithic ebuilds for the following reasons: 1) Applying security fixes and patches to a split ebuild implies less development and maintenance effort, which in turn 2) implies less compilation on users and 3?) if I remember correctly KDE 4 was going to drop monolithic components (how's that by the way?) -[Do Mär 6 2008] [20:38:46] ++ -[Do Mär 6 2008] [20:38:48] KDE 4 has had them dropped already -[Do Mär 6 2008] [20:38:53] !bug 211116 -[Do Mär 6 2008] [20:38:55] Philantrop: https://bugs.gentoo.org/211116 maj, P2, All, infoman1985@gmail.com->kde@gentoo.org, REOPENED, pending, kde-base/*-3.5.9 split packages can't be mixed with kde-base/*-3.5.9 monolithic packages. -[Do Mär 6 2008] [20:38:55] Philantrop: https://bugs.gentoo.org/211116 maj, P2, All, infoman1985@gmail.com->kde@gentoo.org, REOPENED, pending, kde-base/*-3.5.9 split packages can't be mixed with kde-base/*-3.5.9 monolithic packages. -[Do Mär 6 2008] [20:39:15] ^^^ That's the bug. -[Do Mär 6 2008] [20:39:29] but I disagree, dropping monolithic :3.5 ebuilds is a regression imho, besides, some slow arches only have those keyworded, and I see no reason to force a change upon them on a version of KDE that's getting EOL'ed soon -[Do Mär 6 2008] [20:40:12] mixing splits and monolithic was never supported by us anyways, was it? possible yes.. sadly :) -[Do Mär 6 2008] [20:40:15] I'm with Ingmar on this one -[Do Mär 6 2008] [20:40:31] I'd like to keep it the way it is as only a few users even complained and most jsut switched to split ebuilds. :-) -[Do Mär 6 2008] [20:40:49] * Philantrop scribbles two names into his little black book... ;-) -[Do Mär 6 2008] [20:40:55] well, other users apparently care enough to attach a partial patch -[Do Mär 6 2008] [20:41:03] we are not planning on offering monolithic ebuilds on KDE 4, are we? -[Do Mär 6 2008] [20:41:04] tgurr: it used to be possible through the eclasses. 3.5.9 uses EAPI=1 and thus doesn't use those eclass functions anymore... -[Do Mär 6 2008] [20:41:11] deathwing00: Nope. :-) -[Do Mär 6 2008] [20:41:17] pong -[Do Mär 6 2008] [20:41:20] sorry, just got home -[Do Mär 6 2008] [20:41:22] and it doesn't make sense for a user that kdebase + kdenetwork works, but kdebase + kopete doesn't -[Do Mär 6 2008] [20:41:30] jmbsvicetto: No problem. Thanks for being here. -[Do Mär 6 2008] [20:41:36] I object as some boxes I maintain use monolithic and it'd be a huge pain to switch to split. I imagine many others would feel pain to -[Do Mär 6 2008] [20:41:48] and that's a good point too -[Do Mär 6 2008] [20:41:49] If we are to not provide it on KDE 4, we can let it be for now, I guess -[Do Mär 6 2008] [20:41:55] converting = lots of useless work -[Do Mär 6 2008] [20:42:15] gentoofan23: the problem is mixing. not all splits or all monos. -[Do Mär 6 2008] [20:42:34] make all splits block all monos and vice-versa -[Do Mär 6 2008] [20:42:52] that's essentially what we have now -[Do Mär 6 2008] [20:42:58] "you want a full mono, you got -meta" -[Do Mär 6 2008] [20:43:06] I agree on that one -[Do Mär 6 2008] [20:43:35] zlin: is it correctly implemented or are we missing something? -[Do Mär 6 2008] [20:43:46] Ok, let's try a slightly different approach - is anyone here willing to change what we have now? :-) -[Do Mär 6 2008] [20:43:59] * Philantrop looks at Ingmar and zlin. *g* -[Do Mär 6 2008] [20:44:32] we can sort of vote if necessary -[Do Mär 6 2008] [20:44:36] Guess that means that I'll do it -[Do Mär 6 2008] [20:44:49] Sure you can vote, but unless you convince me *not* to do it, it's going to happen though :> -[Do Mär 6 2008] [20:45:18] Join mikb has joined this channel (n=mikb@c211-31-30-148.belrs4.nsw.optusnet.com.au). -[Do Mär 6 2008] [20:45:19] Ingmar: I missed something in here... what is gonna happen? -[Do Mär 6 2008] [20:45:20] deathwing00: Well, I've already recorded opinions. At the moment, we're stuck at 2:2 but if Ingmar volunteers, why not. :-) -[Do Mär 6 2008] [20:45:37] Philantrop: ok, got it -[Do Mär 6 2008] [20:45:43] Quit mikb has left this server (Client Quit). -[Do Mär 6 2008] [20:45:53] \o/ -[Do Mär 6 2008] [20:45:54] deathwing00: What Ingmar wants to do is allowing users to mix 3.5.9 splits and monos again. I'm not too strongly against it. :-) -[Do Mär 6 2008] [20:46:02] It's simply stupid to force monolithic users to switch -[Do Mär 6 2008] [20:46:38] Ingmar: Well, considering that they will have to switch for KDE4 anyway, it wouldn't be too bad, I think, but since you volunteered... :-) -[Do Mär 6 2008] [20:46:43] arfie's patch shows what's we want to change.. might not be complete but you get the idea... -[Do Mär 6 2008] [20:46:48] As I've told others before, I agree that the problems caused by mixing splits/monos is reason enough to have splits hard dep on split -[Do Mär 6 2008] [20:47:11] But if Ingmar wants to support it, let him -[Do Mär 6 2008] [20:47:27] jmbsvicetto: Well, a thing Ingmar brought up elsewhere, we might run into even more bug reports now. :) -[Do Mär 6 2008] [20:47:39] Ingmar: If anyone else is willing to help you, you might want ot use an overlay to do that work -[Do Mär 6 2008] [20:47:45] Philantrop: so who is 'yeah' and who is 'nay'? -[Do Mär 6 2008] [20:48:15] deathwing00: I'm a yeay/neah ;) -[Do Mär 6 2008] [20:48:20] hehe -[Do Mär 6 2008] [20:48:30] * gentoofan23 isn't sure if he can vote, so he abstains. :). That's rather paradoxical though -[Do Mär 6 2008] [20:48:36] deathwing00: I've recorded you as "nay" to mixing, me too, jmbsvicetto undecided. Ingmar and zlin "yay". :-) -[Do Mär 6 2008] [20:48:44] ok -[Do Mär 6 2008] [20:48:51] * cryos|laptop is nay... -[Do Mär 6 2008] [20:48:54] jmbsvicetto: decide already -[Do Mär 6 2008] [20:49:17] cryos|laptop: Just to be sure: "Nay" to mixing splits and monos in 3.5.9? -[Do Mär 6 2008] [20:49:23] Yep -[Do Mär 6 2008] [20:49:23] Ingmar: If you do that work on an overlay, I can try to help on "a few" ebuilds - no promises though -[Do Mär 6 2008] [20:49:45] cryos|laptop: Thanks, noted. Anything you could add to make Ingmar see the light? ;-) -[Do Mär 6 2008] [20:50:16] Philantrop: Just that it really does not seem worth the effort, we looked at this in the beginning when splits were introduced.. -[Do Mär 6 2008] [20:50:26] deathwing00: My view is that allowing that is a good thing, but I understand if we decide otherwise. In any case, I can't commit that to the tree. I can try to help on an overlay though -[Do Mär 6 2008] [20:50:48] carlo is clearly a "yay" too and it was supported till 3.5.8 -[Do Mär 6 2008] [20:50:52] If he wants to do it I think he should try it but I wouldn't spend my time trying to fix that personally. It seems tough to get it right and I wonder where the pay off is. -[Do Mär 6 2008] [20:51:27] * cryos|laptop has been largely AFK in recent months though - desktop in a US customs area in New York still :-( -[Do Mär 6 2008] [20:51:46] cryos|laptop: That's annyoing. :-( -[Do Mär 6 2008] [20:52:04] Ok, se can we settle this by saying Ingmar may fix it if he wants? :-) -[Do Mär 6 2008] [20:52:05] I have another argument that you could consider, if we add this for 3.5.9 and then it exists no longer to KDE 4, won't the users be forced into monolithic anyway? -[Do Mär 6 2008] [20:52:14] Yeah - delays, delays and more delays. Do have my Gentoo laptop working with KDE4 and 3.5.9 though. -[Do Mär 6 2008] [20:52:26] deathwing00: To split ebuilds, yes. -[Do Mär 6 2008] [20:52:37] cryos|laptop: At least something. :-) -[Do Mär 6 2008] [20:52:48] Philantrop: yeah, that's what I meant -[Do Mär 6 2008] [20:52:52] deathwing00: that's a different SLOT though so it doesn't matter all that much imo -[Do Mär 6 2008] [20:52:59] Philantrop: I agree with that -[Do Mär 6 2008] [20:53:15] Quit ZeRoX has left this server (Client Quit). -[Do Mär 6 2008] [20:53:19] IIRC, the move forward is another point on this discussion -[Do Mär 6 2008] [20:53:32] zlin: I understand, but it might be a needless effort, we could focus our efforts elsewhere, m¢ :) -[Do Mär 6 2008] [20:53:39] Ok, final call for violent objections against Ingmar changing it. :-) -[Do Mär 6 2008] [20:53:48] no veto here -[Do Mär 6 2008] [20:54:07] deathwing00: that just means it's low priority.. :) -[Do Mär 6 2008] [20:54:16] zlin: agreed -[Do Mär 6 2008] [20:54:22] Ok, any other points that should be brought up for the past 3.5.9 version bump? -[Do Mär 6 2008] [20:55:10] Ok, topic 2: KDE 3.5.8 is stable now and will be in the 2008.0 release. :-) -[Do Mär 6 2008] [20:55:10] I have a point(slightly related). Is there anything wrong with keeping the old stable around a little longer(3.5.7 specifically)? -[Do Mär 6 2008] [20:55:34] gentoofan23: Well, what's wrong with removing it after a newer one has gone stable? -[Do Mär 6 2008] [20:56:15] Join ZeRoX has joined this channel (n=zerox@nelug/developer/zer0x). -[Do Mär 6 2008] [20:56:16] Well, we don't intend to support 5 versions of KDE -[Do Mär 6 2008] [20:56:38] Philantrop: Stable users only had 19 days(iirc) to upgrade before 3.5.7 got booted. It bit me in that I needed to install a specific aspect of Kde and only 3.5.8 was available. So I had to upgrade all of kdelibs,base to get that new portion -[Do Mär 6 2008] [20:57:11] given that we have a newer version which we know is way better, fixes tons of bugs and noone neither upstream nor downstream want to support the old version... -[Do Mär 6 2008] [20:57:26] Ingmar: I'm not suggesting that, I'm suggesting keeping it around a bit longer. 19 days is a little short -[Do Mär 6 2008] [20:57:30] I honestly don't see why we'd keep old stable versions around when never, better stable ebuilds are available -[Do Mär 6 2008] [20:57:33] it isn't -[Do Mär 6 2008] [20:57:42] gentoofan23: Well, yes, I would have thought two weeks were enough to update. It was even for my old Alpha workstation with 233 MHz. :) -[Do Mär 6 2008] [20:58:16] eh, I was a little busy. but granted that, I concede my point I guess -[Do Mär 6 2008] [20:58:22] gentoofan23: What would have been long enough for you? -[Do Mär 6 2008] [20:58:35] (Under normal circumstances.) -[Do Mär 6 2008] [20:58:41] Philantrop: This falls down to the discussion between maintainers/ats about whether old working versions shold be kept around or not -[Do Mär 6 2008] [20:58:55] Philantrop: maybe 45 days? -[Do Mär 6 2008] [20:59:07] gentoofan23: How about 30? :-) -[Do Mär 6 2008] [20:59:15] * Philantrop emulates a bazaar. ;-) -[Do Mär 6 2008] [20:59:19] Philantrop: even that'd be ok I guess -[Do Mär 6 2008] [20:59:19] 30 sounds more reasonable to me -[Do Mär 6 2008] [20:59:25] Join NeddySeagoon has joined this channel (n=NeddySea@gentoo/developer/NeddySeagoon). -[Do Mär 6 2008] [20:59:25] Mode ChanServ gives NeddySeagoon the permission to talk. -[Do Mär 6 2008] [20:59:30] Philantrop: I agree that for maintainers it makes sense to kick old versions - in particular for a project with as many ebuilds as kde -[Do Mär 6 2008] [20:59:30] 19 is rather unreasonable to me. -[Do Mär 6 2008] [20:59:41] yay to 30 days by me then -[Do Mär 6 2008] [20:59:54] jmbsvicetto: That's why we did it, indeed. :-) -[Do Mär 6 2008] [21:00:08] hey, Kubuntu is still supporting a KDE from 3 years ago :-P -[Do Mär 6 2008] [21:00:08] And Ingmar stole all those commits from me! ;-) -[Do Mär 6 2008] [21:00:19] hehe -[Do Mär 6 2008] [21:00:38] gentoofan23: 30 days are ok then? :-) -[Do Mär 6 2008] [21:00:40] So next time Philantrop will be so pressed to get thsoe commits, it won't even be 19 days :> -[Do Mär 6 2008] [21:00:57] Philantrop: yeah, it should be. Of course, I don't use mips :p -[Do Mär 6 2008] [21:01:21] gentoofan23: It doesn't matter anymore. mips has gone the unstable road -[Do Mär 6 2008] [21:01:35] jmbsvicetto: Oh yes, that is true -[Do Mär 6 2008] [21:01:37] Ok, anything else on the bump or 3.5.8 in the upcoming release? -[Do Mär 6 2008] [21:01:49] gentoofan23: From now on, mips needs to keyword a version at least until everyone marks it stable -[Do Mär 6 2008] [21:02:00] they already did -[Do Mär 6 2008] [21:02:03] monolithic 3.5.9 -[Do Mär 6 2008] [21:02:10] Ingmar: ok -[Do Mär 6 2008] [21:02:11] * Philantrop sobs -[Do Mär 6 2008] [21:02:21] * Philantrop sees his ebuilds tainted. ;-) -[Do Mär 6 2008] [21:02:30] Philantrop: :) -[Do Mär 6 2008] [21:02:31] or he didn't, but he's going to, any time soon :) -[Do Mär 6 2008] [21:03:01] Ok, anything else on the bump or 3.5.8 in the upcoming release? (Final call) -[Do Mär 6 2008] [21:03:31] Great. gentoofan23 already brought up topic 3 - Removal of KDE < 3.5.8 from the tree. :-) -[Do Mär 6 2008] [21:04:02] Ingmar kindly killed 3.5.5 to 3.5.7. So we don't have to worry about those anymore. :-) -[Do Mär 6 2008] [21:04:05] uh, I swear I didn't see that on the agenda. -[Do Mär 6 2008] [21:04:08] * gentoofan23 hides -[Do Mär 6 2008] [21:04:09] so that's done. next! :> -[Do Mär 6 2008] [21:05:04] Well, I guess since zlin has a hot date with a rubber doll, we should move on to topic 4 - State of KDE4 in the tree. ;-) -[Do Mär 6 2008] [21:05:24] Oo -[Do Mär 6 2008] [21:05:34] Ingmar, zlin: Let's hear - what's in the tree, when's 4.0.2 going in? :-) -[Do Mär 6 2008] [21:05:54] well, as such the ebuilds in the tree are in a pretty good state. the deps need to be updated for compatibility with the newly introduced split qt-4.4 ebuilds and it needs to be bumped to 4.0.2 (only kdebase and games have been bumped thus far)... -[Do Mär 6 2008] [21:05:54] Ingmar, zlin: And: What's the state of KDE 4.0.2 by your findings? :-) -[Do Mär 6 2008] [21:06:07] Well, some time this weekend, so far we've been busy with the newer Qt -[Do Mär 6 2008] [21:06:40] And the two of you did a great job with Qt, I'd say. :) -[Do Mär 6 2008] [21:06:43] honestly I haven't had a lot of time to use 4.0.2 yet.. but it'll come in the following days. -[Do Mär 6 2008] [21:06:48] Ingmar / zlin: Can I start working on kdenetwork? -[Do Mär 6 2008] [21:06:55] jmbsvicetto: certainly -[Do Mär 6 2008] [21:06:58] jmbsvicetto: Yes, please :) -[Do Mär 6 2008] [21:07:01] ok -[Do Mär 6 2008] [21:07:07] Do you want me to look at anything else? -[Do Mär 6 2008] [21:07:14] any help with bumping it will be appreciated -[Do Mär 6 2008] [21:07:46] eh, I'd help but amd64 AT's need a stable system. :( -[Do Mär 6 2008] [21:07:46] Right, and that goes for bug reports too :) -[Do Mär 6 2008] [21:07:51] I've updated my amd64 and x86 to 4.0.2 during the night, so I can start working on kdenetwork after the meeting -[Do Mär 6 2008] [21:08:11] maybe I'll be able to do it, but don't expect much :) -[Do Mär 6 2008] [21:08:27] s/do/help/ -[Do Mär 6 2008] [21:08:31] As for zlin's plea for help: Anyone who wants to help should simply mail me his ssh public key. Interested users who can show they're able and willing to work on ebuilds are *explicitly* invited, too. :-) -[Do Mär 6 2008] [21:09:29] The bump to 4.0.2 is taking place in a git overlay again to allow for non-ebuild devs to participate, too, and it's a great way to become a full dev as Ingmar and zlin can verify. :-) -[Do Mär 6 2008] [21:09:48] :) -[Do Mär 6 2008] [21:09:56] and as we want berniyh to do too! :> -[Do Mär 6 2008] [21:10:17] poor ignorants... they don't know it yet... *g* -[Do Mär 6 2008] [21:10:22] well, I might be able to help in places. I -[Do Mär 6 2008] [21:10:29] I'll e-mail my key -[Do Mär 6 2008] [21:10:46] gentoofan23: Ok, thanks, we'll work out the details later. -[Do Mär 6 2008] [21:11:14] Ok, anything else about KDE4 for now? -[Do Mär 6 2008] [21:12:03] just a question, what's the policy for things from playground/ going into gentoo-x86? -[Do Mär 6 2008] [21:12:26] various plasmoids come to mind. -[Do Mär 6 2008] [21:12:27] we can discuss that later -[Do Mär 6 2008] [21:12:29] It'd be wrong -[Do Mär 6 2008] [21:12:39] playground is what upstream doesn't consider release worthy -[Do Mär 6 2008] [21:12:45] alright. -[Do Mär 6 2008] [21:13:12] gentoofan23: We could have it in the overlay, though. :-) -[Do Mär 6 2008] [21:13:14] Meaning that it may work, but they won't support it -[Do Mär 6 2008] [21:13:18] definitely -[Do Mär 6 2008] [21:13:26] we already have a lot of it in the overlay -[Do Mär 6 2008] [21:13:29] Ok. -[Do Mär 6 2008] [21:13:40] Ingmar: They don't really support the other stuff either - see KDE 4.0.0. ;-> -[Do Mär 6 2008] [21:13:56] do we ? which cpv ? -[Do Mär 6 2008] [21:14:02] They just release it. Like Pandora did. ;-) -[Do Mär 6 2008] [21:14:05] Pfft, stop being a pansy and use 4.0.2 damnit -[Do Mär 6 2008] [21:14:36] Ok, anything else about KDE4 for now? (Final call.) -[Do Mär 6 2008] [21:14:41] orzelf: 6-8 packages... -[Do Mär 6 2008] [21:15:01] orzelf: Please ask about that in #genkdesvn. The guys there will help you. -[Do Mär 6 2008] [21:15:05] Most of the extragear things is really few work to package it btw -[Do Mär 6 2008] [21:15:59] oh, I might be confusing extragear and playground. maybe it's only a couple of packages then. ;) -[Do Mär 6 2008] [21:16:44] Ok, topic 5 - Herd Testers: Current state and next steps. jmbsvicetto, you're the one in charge with respect to that. :-) -[Do Mär 6 2008] [21:17:17] Well, I haven't done much yet. With the elections and a few other things, I was distracted -[Do Mär 6 2008] [21:17:31] However, the only person that as contacted me about HT was gentoofan23 -[Do Mär 6 2008] [21:17:40] jmbsvicetto: Yes, I know. You corrupted Neddy and four others. ;-) -[Do Mär 6 2008] [21:17:47] Philantrop: Has anyone else talked with you about it? -[Do Mär 6 2008] [21:17:57] Did you get berniyh's mail? :p -[Do Mär 6 2008] [21:18:05] jmbsvicetto: No, not so far. What we should -[Do Mär 6 2008] [21:18:17] jmbsvicetto: yeah, I was accepted by Philantrop as well. Haven't been doing much though -[Do Mär 6 2008] [21:18:17] hehe -[Do Mär 6 2008] [21:18:23] berniyh: Did you sent me an email? -[Do Mär 6 2008] [21:18:27] Ingmar: mail? -[Do Mär 6 2008] [21:18:33] jmbsvicetto: not that i know of ;) -[Do Mär 6 2008] [21:18:35] * do is flesh things a bit out, I think so that people know what we'd like to see done. :-) -[Do Mär 6 2008] [21:18:38] *none -[Do Mär 6 2008] [21:18:52] berniyh: ufff! :) -[Do Mär 6 2008] [21:19:01] jmbsvicetto: Don't worry, berniyh is worse a slacker than you are. ;-) -[Do Mär 6 2008] [21:19:11] hehe -[Do Mär 6 2008] [21:19:20] jmbsvicetto: maybe he meant that viagra thing? *g* -[Do Mär 6 2008] [21:19:32] Philantrop, zlin : ok ,thx. -[Do Mär 6 2008] [21:19:55] Philantrop: Agreed. We might also want to announce again that we're open for HTs and that people can help that way -[Do Mär 6 2008] [21:20:10] I can announce that on GMN -[Do Mär 6 2008] [21:20:11] Philantrop: We might want to push something to gmn and gentoo-pr -[Do Mär 6 2008] [21:20:18] shall I take note? -[Do Mär 6 2008] [21:20:21] berniyh: :) -[Do Mär 6 2008] [21:20:26] jmbsvicetto: Yes, good idea. We'll come to that in topic 8 - misc. :-) -[Do Mär 6 2008] [21:20:32] deathwing00: Yes, please. -[Do Mär 6 2008] [21:20:42] I can also "abuse" the forums for that ;) -[Do Mär 6 2008] [21:20:44] maybe have dberkholz put something on the front page? (as in not gmn) -[Do Mär 6 2008] [21:20:47] Philantrop: noted :) -[Do Mär 6 2008] [21:20:53] deathwing00: yes, please -[Do Mär 6 2008] [21:21:04] deathwing00, jmbsvicetto: Can you come up with a good text together? -[Do Mär 6 2008] [21:21:04] gentoofan23: that's gentoo-pr ;) -[Do Mär 6 2008] [21:21:11] Philantrop: sure thing -[Do Mär 6 2008] [21:21:16] Philantrop: I'll work with deathwing00 -[Do Mär 6 2008] [21:21:18] jmbsvicetto: oh, k -[Do Mär 6 2008] [21:21:26] jmbsvicetto: right after the meeting would be a good timing for me -[Do Mär 6 2008] [21:21:46] jmbsvicetto, deathwing00: Thanks, great! Once you're done, please mail it to kde@ so that we all can review it. Agreed? -[Do Mär 6 2008] [21:21:57] Philantrop: agreed -[Do Mär 6 2008] [21:21:58] deathwing00: If you could give me 30 minutes to have dinner, my stoamach would thank you ;) -[Do Mär 6 2008] [21:22:07] jmbsvicetto: no problem -[Do Mär 6 2008] [21:22:07] Philantrop: sure -[Do Mär 6 2008] [21:22:23] Philantrop: next ? -[Do Mär 6 2008] [21:22:29] Thanks! Anything else on HTs? -[Do Mär 6 2008] [21:22:50] other than the fact that I have no idea what to do, no ;-) -[Do Mär 6 2008] [21:23:07] gentoofan23: jmbsvicetto and deathwing00 will get you up to speed. *g* -[Do Mär 6 2008] [21:23:11] Philantrop: I don't think so. Not at this moment, at least -[Do Mär 6 2008] [21:23:18] Philantrop: :) -[Do Mär 6 2008] [21:23:34] Ok, anything else on HTs? (Final call.) -[Do Mär 6 2008] [21:23:54] Ok, let's move on to topic 6: -[Do Mär 6 2008] [21:23:56] 6. Lead election: -[Do Mär 6 2008] [21:23:56] During recent recruitments, DevRel informed us that the KDE project should have -[Do Mär 6 2008] [21:23:56] a lead as per GLEP39. Some herd members and other devs contacted Philantrop -[Do Mär 6 2008] [21:23:56] about it, too, and requested an election. A simple vote on IRC should be held. -[Do Mär 6 2008] [21:24:01] jmbsvicetto: I have to do forums threads as well btw -[Do Mär 6 2008] [21:24:09] ok -[Do Mär 6 2008] [21:24:35] Philantrop: I think it's about time we elect some leads -[Do Mär 6 2008] [21:25:14] jmbsvicetto: Yes, people asked me about that. As most of you know or can imagine, I volunteer. :-) -[Do Mär 6 2008] [21:25:22] Philantrop: That can help, by letting other people know who to talk to -[Do Mär 6 2008] [21:25:37] Philantrop: O'rly? ;) -[Do Mär 6 2008] [21:25:42] haha -[Do Mär 6 2008] [21:25:51] I second your nomination -[Do Mär 6 2008] [21:26:02] I even vote for Philantrop :) -[Do Mär 6 2008] [21:26:12] Philantrop++ -[Do Mär 6 2008] [21:26:13] Philantrop: I sugest we have 2 leads -[Do Mär 6 2008] [21:26:14] Same ;) -[Do Mär 6 2008] [21:26:27] jmbsvicetto: political power corrupting you? ;-) -[Do Mär 6 2008] [21:26:49] Philantrop: Whether we want an operation and a strategic lead or just a lead and sub-lead, it can help having a failsafe contact -[Do Mär 6 2008] [21:26:50] jmbsvicetto: why? -[Do Mär 6 2008] [21:26:50] I think jmbsvicetto means lead + sublead, as in former times -[Do Mär 6 2008] [21:27:03] gentoofan23: :) -[Do Mär 6 2008] [21:27:25] zlin: For the failsafe -[Do Mär 6 2008] [21:27:27] Philantrop: I think we concluded that we didn't want to split dutties (op + start), right? -[Do Mär 6 2008] [21:27:40] I don't think we need more than one lead, tbh -[Do Mär 6 2008] [21:27:52] 'dutties (op + start)'? -[Do Mär 6 2008] [21:28:04] op + strat* -[Do Mär 6 2008] [21:28:10] Some of us are more than active enough on irc, that there's always someone quick enough to answer KDE questions etc -[Do Mär 6 2008] [21:28:14] actually it's operation and technical -[Do Mär 6 2008] [21:28:14] Ingmar: What? You just want a lead and an HT lead? :o ;) -[Do Mär 6 2008] [21:28:16] ahh, and duties. ;) -[Do Mär 6 2008] [21:28:34] zlin: my bad :) -[Do Mär 6 2008] [21:28:58] I propose to vote if we want to have a sublead first, then vote for candidates -[Do Mär 6 2008] [21:29:03] I'm with Ingmar on this - the students among us are around anyway. ;-) -[Do Mär 6 2008] [21:29:45] I'm with Ingmar on this too. -[Do Mär 6 2008] [21:29:46] zlin: The principle behind the strategic + operational lead, was to have someone concerned with the big picture and another person taking care of the day-to-day -[Do Mär 6 2008] [21:30:14] jmbsvicetto: We all take care of day-to-day stuff. :-) -[Do Mär 6 2008] [21:30:16] Yes, and my point is that day-to-day is more than taken care of -[Do Mär 6 2008] [21:30:23] ok -[Do Mär 6 2008] [21:30:35] If you're happy with just a lead, then I accept that -[Do Mär 6 2008] [21:30:39] Let's vote on the sub-lead, I'd say. Yay/Nay, please. -[Do Mär 6 2008] [21:30:45] not that we can't improve in that, but I don't see a problem, and I don't see your suggestion as a solution ;) -[Do Mär 6 2008] [21:30:48] Nay -[Do Mär 6 2008] [21:30:49] I've already seconded a nomination ;) -[Do Mär 6 2008] [21:30:49] Yay -[Do Mär 6 2008] [21:30:51] * Philantrop votes nay -[Do Mär 6 2008] [21:30:54] Nay -[Do Mär 6 2008] [21:31:02] Yay -[Do Mär 6 2008] [21:31:17] * cryos|laptop abstains -[Do Mär 6 2008] [21:31:17] 2 Yay - 3 Nay ? -[Do Mär 6 2008] [21:31:22] ctennis: ^^ -[Do Mär 6 2008] [21:31:30] masterdriverz: ^^ -[Do Mär 6 2008] [21:31:31] hehe -[Do Mär 6 2008] [21:31:34] * gentoofan23 isn't sure if he can vote... -[Do Mär 6 2008] [21:31:42] You can, if you say nay -[Do Mär 6 2008] [21:31:43] gentoofan23: go on -[Do Mär 6 2008] [21:31:47] Ingmar: lol -[Do Mär 6 2008] [21:31:54] nay then -[Do Mär 6 2008] [21:32:02] haha -[Do Mär 6 2008] [21:32:16] I guess, nay passes then -[Do Mär 6 2008] [21:32:21] honestly, that *was* my opinion :) -[Do Mär 6 2008] [21:32:43] :p -[Do Mär 6 2008] [21:33:02] so, do we want Philantrop as lead? Yay/Nay? -[Do Mär 6 2008] [21:33:04] Yay -[Do Mär 6 2008] [21:33:05] yay -[Do Mär 6 2008] [21:33:09] Yay -[Do Mär 6 2008] [21:33:10] yay above too -[Do Mär 6 2008] [21:33:12] yay -[Do Mär 6 2008] [21:33:13] yay -[Do Mär 6 2008] [21:33:15] yay -[Do Mär 6 2008] [21:33:24] Philantrop: To do it the right way, we should open a nomination period and then have a voting period -[Do Mär 6 2008] [21:33:39] why are we even voting if there is only one nominee? *g* -[Do Mär 6 2008] [21:33:53] ok, if anyone feels comfortable with that, Yay -[Do Mär 6 2008] [21:33:58] gentoofan23: well, if over 50% goes nay, then we have to elect someone else -[Do Mär 6 2008] [21:34:08] If there're any other nominees, I'd suggest them to stand up :) -[Do Mär 6 2008] [21:34:20] Else Idon't see the point of an election, waste of time :) -[Do Mär 6 2008] [21:34:29] oh, I guess I was likening it to a political election. -[Do Mär 6 2008] [21:34:29] Ingmar: tell devrel -[Do Mär 6 2008] [21:35:07] Philantrop: the sublead thing is 3y - 4n -[Do Mär 6 2008] [21:35:07] So, other candidates? -[Do Mär 6 2008] [21:35:11] this isn't a political election. we just need the whole team to be comfortable with the chosen lead -[Do Mär 6 2008] [21:35:31] zlin: right :) -[Do Mär 6 2008] [21:35:54] Philantrop: This is another good reason to get gmn and gentoo-pr -[Do Mär 6 2008] [21:36:05] ? -[Do Mär 6 2008] [21:36:17] Philantrop: Let people know about our new lead and remind them of kde HTs -[Do Mär 6 2008] [21:36:29] Philantrop: ^ -[Do Mär 6 2008] [21:36:35] bah, deathwing00 ^ -[Do Mär 6 2008] [21:36:35] jmbsvicetto: Yes, a sec. :-) -[Do Mär 6 2008] [21:36:37] Philantrop: u sure you don't want jmbsvicetto as your sublead? -[Do Mär 6 2008] [21:36:46] jmbsvicetto: noted -[Do Mär 6 2008] [21:36:51] deathwing00: Thanks, but I'm not interested -[Do Mär 6 2008] [21:37:03] deathwing00: If we were to have a sub-lead, I had another in mind -[Do Mär 6 2008] [21:37:25] deathwing00: Well, let's keep things simple - everyone here can still make decisions so you're all sub-leads, IMHO. :) -[Do Mär 6 2008] [21:37:35] hehe -[Do Mär 6 2008] [21:38:17] For verification: sublead vote: 3 "yays", 3 "nays", one abstention, right? -[Do Mär 6 2008] [21:38:19] Philantrop: can you give me the vote counts on sublead y/n/a and lead election y/n/a? -[Do Mär 6 2008] [21:38:23] wheeeeeeeee! I'm one of the 10+ gentoo-kde executive vps^D^D^Dsub-leads ;) -[Do Mär 6 2008] [21:38:24] dooooooork -[Do Mär 6 2008] [21:38:37] jeeves: :P -[Do Mär 6 2008] [21:38:53] lead election: 7 yays, no nays, no abstention. -[Do Mär 6 2008] [21:39:04] noted -[Do Mär 6 2008] [21:39:17] sublead is a deadlock then? -[Do Mär 6 2008] [21:39:44] let's make it a 3 yays and 4 nays then :) -[Do Mär 6 2008] [21:40:04] noted -[Do Mär 6 2008] [21:40:08] ok -[Do Mär 6 2008] [21:40:15] tgurr: I need your vote on Philantrop :) -[Do Mär 6 2008] [21:40:32] yay for this wulf thing ;) -[Do Mär 6 2008] [21:40:42] done with that -[Do Mär 6 2008] [21:41:02] Philantrop: you have been elected as KDE lead, my congratulations -[Do Mär 6 2008] [21:41:13] Philantrop: copy-paste your speech here -[Do Mär 6 2008] [21:41:14] Thanks, guys. :-) -[Do Mär 6 2008] [21:41:17] * deathwing00 grins -[Do Mär 6 2008] [21:41:44] I have no speech and I don't want to waste your time so just let me thank my grand-parents, my parents, my wife, my children, my pet... ;-) -[Do Mär 6 2008] [21:41:54] ;-)) -[Do Mär 6 2008] [21:41:58] next issue -[Do Mär 6 2008] [21:42:10] Topic 7 - Review of the project page. -[Do Mär 6 2008] [21:42:28] Apart from the lead thing - what do we need to update=? -[Do Mär 6 2008] [21:42:37] kde-pr could take care of it if you want -[Do Mär 6 2008] [21:42:40] lots of kde 3.5.7 stuff. -[Do Mär 6 2008] [21:42:47] stable version + testing version and status of kde4 -[Do Mär 6 2008] [21:42:52] I have a cvs checkout here, I could update things to a semi-sane state -[Do Mär 6 2008] [21:43:14] That'd be nice -[Do Mär 6 2008] [21:43:16] kde-pr? -[Do Mär 6 2008] [21:43:36] kde-pr: just invented subproject -[Do Mär 6 2008] [21:43:47] gentoofan23, deathwing00: How about the two of you do it together? -[Do Mär 6 2008] [21:43:49] who volunteered? :> -[Do Mär 6 2008] [21:44:12] yeah, I am already asuming these duties -[Do Mär 6 2008] [21:44:15] deathwing00: that means you are an indirect sublead :) -[Do Mär 6 2008] [21:44:24] gentoofan23: you mean a monkey -[Do Mär 6 2008] [21:44:40] hehe -[Do Mär 6 2008] [21:44:44] deathwing00: well, the two can be related :) -[Do Mär 6 2008] [21:44:55] * cryos|laptop has to go - duty calls -[Do Mär 6 2008] [21:45:00] Congrats Philantrop :D -[Do Mär 6 2008] [21:45:02] gentoofan23, deathwing00: Can I take that for a "yes"? -[Do Mär 6 2008] [21:45:07] cryos|laptop: laters :) -[Do Mär 6 2008] [21:45:12] cryos|laptop: Thanks and thanks for having been here! -[Do Mär 6 2008] [21:45:15] Philantrop: sure. ;) -[Do Mär 6 2008] [21:45:33] Philantrop: affirmative, I'll take care of everything that needs to be spread to the public opinion everyone likes, with the help of everyone who likes -[Do Mär 6 2008] [21:45:46] gentoofan23, deathwing00: Can you do it till the next meeting (next month)? -[Do Mär 6 2008] [21:45:51] cryos|laptop: thank you for sparing your time :) -[Do Mär 6 2008] [21:46:18] Philantrop: when is the next meeting? tomorrow? -[Do Mär 6 2008] [21:46:28] deathwing00: next month. :-) -[Do Mär 6 2008] [21:46:32] Philantrop: probably. -[Do Mär 6 2008] [21:46:38] I already am editing a few things. -[Do Mär 6 2008] [21:46:49] will do -[Do Mär 6 2008] [21:46:55] I'll send any patches to kde@ for review -[Do Mär 6 2008] [21:47:04] Philantrop: What are we missing? -[Do Mär 6 2008] [21:47:21] gentoofan23, deathwing00: Ok, thanks! :-) And, yes, please, mail it to kde@. -[Do Mär 6 2008] [21:47:25] Philantrop: I'm being poked to have dinner -[Do Mär 6 2008] [21:47:44] jmbsvicetto: Missing? And poked by whom? :-) -[Do Mär 6 2008] [21:47:46] jmbsvicetto: meet you here in 35 minutes -[Do Mär 6 2008] [21:48:04] Philantrop: What other points? I'm at my parents house -[Do Mär 6 2008] [21:48:14] gentoofan23: can we have talk about it after the meeting? -[Do Mär 6 2008] [21:48:18] jmbsvicetto: Misc and next meeting date. :-) -[Do Mär 6 2008] [21:48:29] deathwing00: uh, maybe. I might have to go after the meeting though -[Do Mär 6 2008] [21:48:32] jmbsvicetto: Nothing very special, I think. :-) -[Do Mär 6 2008] [21:48:37] ok -[Do Mär 6 2008] [21:48:42] Quit orzelf has left this server (Remote closed the connection). -[Do Mär 6 2008] [21:48:51] I'll try to poke in a few minutes -[Do Mär 6 2008] [21:49:25] deathwing00, gentoofan23: 3, 4, 8, 9 of kde.gentoo.org need to updated, I think. :-) -[Do Mär 6 2008] [21:49:43] Philantrop: noted -[Do Mär 6 2008] [21:49:46] what do you mean by all those numbers? -[Do Mär 6 2008] [21:49:54] gentoofan23: The headlines. :-) -[Do Mär 6 2008] [21:50:01] oh, noted -[Do Mär 6 2008] [21:50:16] Ok, anything else about the project page? -[Do Mär 6 2008] [21:50:31] and of course we are here if you need additional info to write it... :) -[Do Mär 6 2008] [21:51:00] just a reminder to someone with cvs access to update proj/en/desktop/ with Philantrop as the Lead of the KDE project -[Do Mär 6 2008] [21:51:12] should be a one-liner -[Do Mär 6 2008] [21:51:20] zlin: noted, thanks! -[Do Mär 6 2008] [21:51:42] Anything else about the project page? (Final call.) -[Do Mär 6 2008] [21:51:56] zlin: :) -[Do Mär 6 2008] [21:52:11] Topic 8 - Miscellaneous -[Do Mär 6 2008] [21:52:14] gentoofan23: write a paragraph, then it looks like it is important ;) -[Do Mär 6 2008] [21:52:33] Anyone with anything to bring up? -[Do Mär 6 2008] [21:53:18] Ok, I have one point - as he hinted at earlier, deathwing00 kindly volunteered to help with spreading the news about the Gentoo KDE project. I'd like to take up this offer. :-) -[Do Mär 6 2008] [21:53:25] oh -[Do Mär 6 2008] [21:53:25] oh, what about #5 in index.xml? what is the status on monthly meetings? -[Do Mär 6 2008] [21:53:28] let me interrupt -[Do Mär 6 2008] [21:54:01] Philantrop: gentoofan23 made me notice that we could create a new section about meetings, with dates, sumary and logs -[Do Mär 6 2008] [21:54:02] gentoofan23: We'll resume that. :-) -[Do Mär 6 2008] [21:54:33] kde herd meeting? -[Do Mär 6 2008] [21:54:33] summary* -[Do Mär 6 2008] [21:54:33] deathwing00: Yes, we should updated section 5. I'd like to have monthly meetings again. -[Do Mär 6 2008] [21:54:34] ;-) -[Do Mär 6 2008] [21:54:40] genstef: Welcome! :-) -[Do Mär 6 2008] [21:54:41] right. -[Do Mär 6 2008] [21:54:45] hi genstef -[Do Mär 6 2008] [21:55:04] Philantrop: noted :) -[Do Mär 6 2008] [21:55:15] Anything else for topic 8 - Miscellaneous? -[Do Mär 6 2008] [21:55:25] one thing to note is that the first saturday of every month is Bugday, not sure if that will make any conflicts. -[Do Mär 6 2008] [21:55:34] bugday is dead -[Do Mär 6 2008] [21:55:47] eroyf: don't blame me plz :) -[Do Mär 6 2008] [21:55:52] not your fault -[Do Mär 6 2008] [21:55:58] gentoofan23: Oh, right, most people turned out to have no time during the weekend. What's best for everyone here? -[Do Mär 6 2008] [21:55:59] more my fault -[Do Mär 6 2008] [21:56:13] Philantrop: why not like today? -[Do Mär 6 2008] [21:56:16] Is Thursday good for everyone? -[Do Mär 6 2008] [21:56:23] Well, it is probably best for me -[Do Mär 6 2008] [21:56:29] Sundays are not very good -[Do Mär 6 2008] [21:56:41] Thursday afternoons are good, usually -[Do Mär 6 2008] [21:57:14] I like Thursdays, too. :-) -[Do Mär 6 2008] [21:57:38] thursday is great -[Do Mär 6 2008] [21:57:49] Anyone *against* (!) choosing Thursday? -[Do Mär 6 2008] [21:57:53] I prefer thursday over friday at least -[Do Mär 6 2008] [21:58:13] * Philantrop hums "It's just another manic Thursday"... ;-) -[Do Mär 6 2008] [21:58:18] anyone for Mondays? *g* -[Do Mär 6 2008] [21:58:33] Thursday it is. :-) -[Do Mär 6 2008] [21:58:44] PR: noted -[Do Mär 6 2008] [21:58:52] Second one, I'd say. Objections? -[Do Mär 6 2008] [21:59:07] first thursday of every month -[Do Mär 6 2008] [21:59:31] Ok, first. Objections? -[Do Mär 6 2008] [21:59:42] Perfect. *g* Anything else for topic 8 - Miscellaneous? -[Do Mär 6 2008] [22:00:07] can we go now? there's so much to do... *g* -[Do Mär 6 2008] [22:00:12] btw, I am at Cebit tomorrow :-) -[Do Mär 6 2008] [22:00:17] Join zsz has joined this channel (n=zsz@sa-184-64.saturn.infonet.ee). -[Do Mär 6 2008] [22:00:18] Ok, guys, final topic - Date of the next meeting and closing. -[Do Mär 6 2008] [22:00:19] well, I'm out, later everyone -[Do Mär 6 2008] [22:00:19] eh on the weekend -[Do Mär 6 2008] [22:00:21] second thursday is council meetings. not sure if that's a pro or a con though. :> -[Do Mär 6 2008] [22:00:24] Congrats, Philantrop -[Do Mär 6 2008] [22:00:40] zlin: Oh, right. Then it's really first. :-) -[Do Mär 6 2008] [22:00:52] yes -[Do Mär 6 2008] [22:00:57] gentoofan23: goodbye :-) -[Do Mär 6 2008] [22:01:04] Last topic: Date of the next meeting and closing. -[Do Mär 6 2008] [22:01:11] Quit gentoofan23 has left this server (Client Quit). -[Do Mär 6 2008] [22:01:16] April, 3rd, 2008. -[Do Mär 6 2008] [22:01:30] * zlin acks -[Do Mär 6 2008] [22:01:33] noted -[Do Mär 6 2008] [22:01:43] :) -[Do Mär 6 2008] [22:01:44] Anything else, guys? :-) -[Do Mär 6 2008] [22:01:50] Topic Ingmar sets the channel topic to "KDE 4.0 guide: http://tinyurl.com/27tbt5 | KDE herd meeting (april 3rd, 2008, 19:30 UTC, here). Agenda: http://tinyurl.com/2hhsvc | Problems upgrading to stable KDE 3.5.8? http://tinyurl.com/yqk4le | http://dev.gentoo.org/~masterdriverz/kde-help.txt | KDE Bugs: http://tinyurl.com/3bpdlv | If we're too quiet try #kde | KDE4 live ebuilds? -> "kde" overlay and #genkdesvn. | KDE 4 doesn't work with qt-4.4 *yet*". -[Do Mär 6 2008] [22:01:51] yes. -[Do Mär 6 2008] [22:02:05] you missed to say that you all are doing a great job. -[Do Mär 6 2008] [22:02:26] Hats off to the qt4 beta1 folks -[Do Mär 6 2008] [22:02:38] No, that's closing and that's what I'm doing now: Thanks for all your great work, guys! It's a great pleasure to work with you! :-) -[Do Mär 6 2008] [22:03:00] ctennis: you mean "heads off" ;-) -[Do Mär 6 2008] [22:03:08] that too! -[Do Mär 6 2008] [22:03:33] Quit mark_alec has left this server ("Konversation terminated!"). -[Do Mär 6 2008] [22:03:35] ctennis: And it's nice to have one of the grumpy old men back on IRC. ;-) -[Do Mär 6 2008] [22:03:47] :) -[Do Mär 6 2008] [22:03:58] heh -[Do Mär 6 2008] [22:04:07] I wish I had more time to play -[Do Mär 6 2008] [22:04:28] but it seems like there's no problem in picking up my slack -[Do Mär 6 2008] [22:04:34] :) -[Do Mär 6 2008] [22:04:34] Ok, guys, this meeting is now officially closed! :-) -[Do Mär 6 2008] [22:04:46] * deathwing00 cheers at the new lead -[Do Mär 6 2008] [22:04:56] ctennis: with qt-4.4? -[Do Mär 6 2008] [22:04:57] ctennis: :) -[Do Mär 6 2008] [22:04:58] ctennis: Oh, you should have seen Ingmar and zlin swear about Qt's build system sometimes... ;-) -[Do Mär 6 2008] [22:05:11] * berniyh nods -[Do Mär 6 2008] [22:05:13] we're still swearing.. ;) -[Do Mär 6 2008] [22:05:23] I'll mail the log and summary to kde@. :-) -[Do Mär 6 2008] [22:05:46] Philantrop: I'll reuse it :) -[Do Mär 6 2008] [22:06:04] deathwing00: That was my dark intention. :-) -[Do Mär 6 2008] [22:06:21] :) -[Do Mär 6 2008] [22:07:04] okay, zlin forced me to say that I vote for philantrop and against a sub-lead -[Do Mär 6 2008] [22:07:37] LOL -[Do Mär 6 2008] [22:07:37] err -[Do Mär 6 2008] [22:07:44] s/.*I vote/I vote/ -[Do Mär 6 2008] [22:07:52] keytoaster: noted -[Do Mär 6 2008] [22:09:35] ehrm, when will the 4.0.2 ebuilds be in portage ? -[Do Mär 6 2008] [22:09:44] Philantrop: I'll post the most interesting things on our forums btw :) -[Do Mär 6 2008] [22:09:49] * brot ducks -[Do Mär 6 2008] [22:10:09] deathwing00: Thanks! :-) Please let me know the link. :-) diff --git a/meeting-logs/kde-herd-meeting-log-20081204.txt b/meeting-logs/kde-herd-meeting-log-20081204.txt deleted file mode 100644 index e4c2b60..0000000 --- a/meeting-logs/kde-herd-meeting-log-20081204.txt +++ /dev/null @@ -1,641 +0,0 @@ -2008 Dec 04 20:01:04 http://dev.gentoo.org/~scarabeus/kde_meeting0812.txt -2008 Dec 04 20:01:11 time is here -2008 Dec 04 20:01:13 so who is around? -2008 Dec 04 20:01:23 -*- tampakrap -2008 Dec 04 20:01:26 -*- bonsaikitten -2008 Dec 04 20:01:43 !herd kde -2008 Dec 04 20:01:44 (kde) caleb, carlo, cryos, deathwing00, genstef, jmbsvicetto, keytoaster, mattepiu, scarabeus, tgurr -2008 Dec 04 20:01:54 guys you should all show up :] -2008 Dec 04 20:01:54 -*- krytzz -2008 Dec 04 20:02:01 hi there! -2008 Dec 04 20:02:22 -*- jmbsvicetto -2008 Dec 04 20:02:40 krytzz, Sput: you two around? -2008 Dec 04 20:02:42 -*- cryos|work is here -2008 Dec 04 20:02:49 yes -2008 Dec 04 20:03:20 ok i think that is most we can get, any words from others, stating that they show up too? -2008 Dec 04 20:03:35 scarabeus: No idea -2008 Dec 04 20:03:49 I guess we should let their backlog do its work ;) -2008 Dec 04 20:04:02 scarabeus: About your agenda, we should start with a "simple" point - who is still working / willing to work with KDE 3.5 -2008 Dec 04 20:04:10 me -2008 Dec 04 20:04:15 bonsaikitten: That doesn't work with caleb and carlo ;) -2008 Dec 04 20:04:28 I am somewhat, but with limited time... -2008 Dec 04 20:04:31 as long as it is only ebuild maintenance and not C++ stabbing I'm willing to keep it alive -2008 Dec 04 20:04:41 but I have no interest in 3.5 anymore :) -2008 Dec 04 20:04:48 i said i still use kde3 in my main desktop and wanted to have various tests about that and check bugs of course -2008 Dec 04 20:04:54 but i was busy with the quiz -2008 Dec 04 20:04:55 -*- cryos|work has waning interest in it... -2008 Dec 04 20:05:18 our users want it, so those primitives have to be kept happy ;) -2008 Dec 04 20:05:41 yes i would say it is requirement to have kde3 around until kde4.3 -2008 Dec 04 20:05:42 --> MartyMcFly (n=martin@dslb-088-064-190-153.pools.arcor-ip.net) has joined #gentoo-kde -2008 Dec 04 20:06:00 maybe even longer. if 3.5 is stable enough maintenance should be cheap -2008 Dec 04 20:06:01 yes -2008 Dec 04 20:06:03 I'm not saying we should drop 3.5, I'm asking who is willing to keep it alive ;) -2008 Dec 04 20:06:05 Quite probably, but it is essentially dead upstream. -2008 Dec 04 20:06:07 jkt|: maybe you will be interested in this too -2008 Dec 04 20:06:20 -=- hwoarang is now known as hwo[a]rang -2008 Dec 04 20:06:25 I will do what I can to help. -2008 Dec 04 20:06:28 Also, who is willing to work on the issues caused by the mixing of 3.5 with 4 -2008 Dec 04 20:06:44 me :) -2008 Dec 04 20:06:44 I have noted many distros already dropping it in new releases. Just keeping unported apps around. -2008 Dec 04 20:07:08 cryos|work: people would hate us, kde4 is not yet ready, even i miss some features -2008 Dec 04 20:07:10 I guess all of us will be hybrid users as noone goes back to a 3.5 desktop anymore :) -2008 Dec 04 20:07:16 I will help when I can, I think I may have neglected to pick up all the pieces... -2008 Dec 04 20:07:34 --> reavertm (n=maciek@bcv18.neoplus.adsl.tpnet.pl) has joined #gentoo-kde -2008 Dec 04 20:07:34 cryos|work: life happened. don't beat yourself up for that :) -2008 Dec 04 20:07:48 scarabeus: I am not talking about dropping it, I am however pointing out the deadness of upstream in that sense and what other distros are tending to do. -2008 Dec 04 20:08:08 i understand. -2008 Dec 04 20:08:12 Thanks bonsaikitten ;-) -2008 Dec 04 20:08:13 (if I'm out again it means my hardware is failing again, don't bother) -2008 Dec 04 20:08:17 <-- duog (n=doug@78-86-178-196.zone2.bethere.co.uk) has quit (Remote closed the connection) -2008 Dec 04 20:08:22 We should keep an eye on what is happening elsewhere. -2008 Dec 04 20:08:22 -=- Mode #gentoo-kde [+v reavertm] by scarabeus -2008 Dec 04 20:08:35 so we'll keep it alive, but there's a good chance we won't give it high priority -2008 Dec 04 20:09:03 agreed, on low priority i think we can handle this, and we should be closing up enhancement request for kde3 -2008 Dec 04 20:09:10 since it would be just pointless work -2008 Dec 04 20:09:24 <-- hvengel (n=hvengel@astound-66-234-194-11.ca.astound.net) has quit (Read error: 110 (Connection timed out)) -2008 Dec 04 20:09:42 mostly agree -2008 Dec 04 20:09:53 kde page stated along with some kde4 release announcement: "Don't look back" :) -2008 Dec 04 20:09:55 after all kde4.2 is close and will be stable enough -2008 Dec 04 20:10:31 ok so lets mark kde3 as work for cryos and tampakrap, i think you two can talk out what is needed on that field -2008 Dec 04 20:10:38 anyone else willing to jump on kde3? -2008 Dec 04 20:10:57 i don't think we need more people -2008 Dec 04 20:11:05 let's focus on kde4 "the future" -2008 Dec 04 20:11:09 cryos|work: Yes, a dead upstream (3.5) and their lack of work to keep more than one version around are the most important cause of the open bugs - imho -2008 Dec 04 20:11:43 <-- St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has quit ("http://quassel-irc.org - Chat comfortably. Anywhere.") -2008 Dec 04 20:11:49 jmbsvicetto: Certainly, and so the distros are forced to move along with them unless they have considerable resources. -2008 Dec 04 20:11:55 --> St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has joined #gentoo-kde -2008 Dec 04 20:12:01 well, upstream simply has no manpower to maintaint both -2008 Dec 04 20:12:07 cryos|work: never underestimate gentoo users ;) -2008 Dec 04 20:12:07 There was some talk of a distro maintained patch set but I haven't seen mention of it recently. -2008 Dec 04 20:12:24 cryos|work: ask arch linux team -2008 Dec 04 20:12:25 cryos|work: For 3.5? -2008 Dec 04 20:12:31 they have probably best kde3 team around -2008 Dec 04 20:12:33 currently -2008 Dec 04 20:12:43 their kdemod is epic -2008 Dec 04 20:13:06 htmlhandbook provides whole help or only some additional files? -2008 Dec 04 20:13:20 St_MPA3b: whole help -2008 Dec 04 20:13:33 scarabeus: thanks -2008 Dec 04 20:13:55 scarabeus: talking about htmlhandbook, I ended up not moving it away from ebuilds and into the eclass :\ -2008 Dec 04 20:13:57 scarabeus: and there are currently no file collisions if htmlhandbook is turned off? -2008 Dec 04 20:15:11 in @kde-live -2008 Dec 04 20:15:30 jmbsvicetto: well that goes for next point of meeting -2008 Dec 04 20:15:33 kde4 eclasses -2008 Dec 04 20:15:40 i heavily rewrote them -2008 Dec 04 20:15:48 applied some suggestions from jmbsvicetto -2008 Dec 04 20:15:53 (again?) -2008 Dec 04 20:15:55 --> breiti (n=breiti@p5DD69917.dip0.t-ipconnect.de) has joined #gentoo-kde -2008 Dec 04 20:15:57 any moar points to them -2008 Dec 04 20:16:04 when there will be commit? -2008 Dec 04 20:16:13 reavertm: they are still the same, it was not yet accepted. -2008 Dec 04 20:16:52 So what are the main changes made? -2008 Dec 04 20:17:12 mostly we allow dynamic detection for kde4 -2008 Dec 04 20:17:23 so apps can work with kde4.1 and kde4.2 and live -2008 Dec 04 20:17:25 no matter what -2008 Dec 04 20:17:32 nice -2008 Dec 04 20:17:32 eclasses handles all deps correctly -2008 Dec 04 20:17:40 also i removed most of not required code -2008 Dec 04 20:17:41 Which one are they linking too/building against? -2008 Dec 04 20:17:45 This is a bad thing(tm) in design, but I don't have a better alternative -2008 Dec 04 20:18:21 cryos|work: well now you can specify which kde it needs as minimal and then specify search order for other kde versions -2008 Dec 04 20:18:26 basicly it preffers -kdeprefix -2008 Dec 04 20:18:34 (actually one guy had problems with updating from 4.1.2 to 4.1.3 with -kdeprefix using portage eclasses and kde-crazy ones didn't help -2008 Dec 04 20:18:45 If they build/link against the latest version installed, they may not link to an earlier version, if it builds against old that doesn't have new symbols it won't compile. -2008 Dec 04 20:18:46 it may still need some checks -2008 Dec 04 20:19:12 cryos|work: that all can be ebuld specified -2008 Dec 04 20:19:21 <-- mx-tvt (n=costa@175.230.54.77.rev.vodafone.pt) has quit (Remote closed the connection) -2008 Dec 04 20:19:23 That is why I have always erred on the side of saying this is possible but a support nightmare. -2008 Dec 04 20:19:37 reavertm: he had fucked up kdesvn eclasses i guess, since we used that slot loong ago -2008 Dec 04 20:19:41 If it seems to work that is great though. -2008 Dec 04 20:19:55 yeah it works for all overlay guys -2008 Dec 04 20:20:06 and also my eclass supports koffice -2008 Dec 04 20:20:07 I think in general they should build/link against oldest installed version that satisfies the deps. -2008 Dec 04 20:20:13 which i can maintain with bonsaikittens help -2008 Dec 04 20:20:17 if he is still interested -2008 Dec 04 20:20:19 If KDE devs did their job well it will link to the latest version. -2008 Dec 04 20:20:21 koffice2 -2008 Dec 04 20:20:41 i could help there too a little bit -2008 Dec 04 20:20:41 cryos|work: that is default behavior -2008 Dec 04 20:20:42 So if we are planning on supporting it that should be the default behaviour. -2008 Dec 04 20:20:52 That sounds good to me then. -2008 Dec 04 20:21:00 scarabeus: There are a few things about get_latest_kdedir. That function shouldn't have hardcoded version strings - they should instead be defined in a var like KDE_SLOTS -2008 Dec 04 20:21:02 but dev can specify other order in ebuild -2008 Dec 04 20:21:31 OK, but I would discourage them from doing that unless they have an amazing reason to do so. -2008 Dec 04 20:21:33 jmbsvicetto: well enjoy its updating :] i will be hapy to see help from others :], i have no idea how to use it best, so i did it this way -2008 Dec 04 20:21:50 cryos|work: all written in comments for those variables -2008 Dec 04 20:21:56 scarabeus: Yeah, I'll see what I can do about it -2008 Dec 04 20:22:52 Sounds fine, we just need to stick to some policies for in tree stuff at least. -2008 Dec 04 20:23:08 scarabeus / cryos|work: Most of the issues that we're having (besides the linking to a versioned dir) is that upstream is breaking ABI continuously for KDE4, right? -2008 Dec 04 20:23:09 i use it for in tree stuff just fine -2008 Dec 04 20:23:14 --> NSaibot (n=quassel@i3ED6C704.versanet.de) has joined #gentoo-kde -2008 Dec 04 20:23:18 jmbsvicetto: right -2008 Dec 04 20:23:33 <-- NSaibot (n=quassel@i3ED6C704.versanet.de) has quit (Remote closed the connection) -2008 Dec 04 20:23:46 cryos|work: i will run some test tomorow and fix all remaining compatibility problems -2008 Dec 04 20:24:10 jmbsvicetto: Yeah, but they promised not to after 4.1. I guess they are failing... -2008 Dec 04 20:24:23 --> non7top (n=non7top@77.66.156.160) has joined #gentoo-kde -2008 Dec 04 20:24:25 Oh, an important point about the eclasses - are we ready to block kde4 eclasses for EAPI-0 and EAPI-1? -2008 Dec 04 20:24:30 I am talking at Camp KDE 2009 too - KDE and Gentoo. -2008 Dec 04 20:24:43 cool ^^ -2008 Dec 04 20:24:47 i volte for only eapi2 -2008 Dec 04 20:24:54 --> NSaibot (n=quassel@i3ED6C704.versanet.de) has joined #gentoo-kde -2008 Dec 04 20:24:57 scarabeus: EAPI-2 or later ;) -2008 Dec 04 20:25:00 yes -2008 Dec 04 20:25:39 Can we block change the EAPI on an existing in tree e-class? Don't we need to maintain backwards compatibility on eclasses? -2008 Dec 04 20:26:08 That is a question as I can't remember what the policy is. -2008 Dec 04 20:26:09 cryos|work: well packages will be broken if they use eapi lower than 2 and our eclass even currently -2008 Dec 04 20:26:13 so we should block it -2008 Dec 04 20:26:24 That would allow us to drop the QT4_BUILT_WITH_USE_CHECK, KDE4_BUILT_WITH_USE_CHECK and friends -2008 Dec 04 20:26:33 <-- fedux (n=fedux@host157.190-137-19.telecom.net.ar) has quit ("Saliendo") -2008 Dec 04 20:26:57 cryos|work: I'll confirm it with zmedico, but iirc the eclasses are now saved to vdb -2008 Dec 04 20:27:13 I am just not certain we can do that, but I could be wrong. An eclass that used to work with a version of portage should at least work to uninstall said ebuild. -2008 Dec 04 20:27:14 and no eapi1 package currently uses our eclass -2008 Dec 04 20:27:38 If the policy has changed due to portage changes then fine, but last I checked it had not. -2008 Dec 04 20:27:47 cryos|work: I'll be sure to check it -2008 Dec 04 20:27:50 You could leave empty functions there, but they had to remain there. -2008 Dec 04 20:28:14 So that it is possible to uninstall the cached ebuild that didn't cache its eclass. -2008 Dec 04 20:28:16 -*- jmbsvicetto mumbles - versioned eclasses -2008 Dec 04 20:28:29 -*- cryos|work thinks versioning should be used. -2008 Dec 04 20:28:29 cryos|work: understood -2008 Dec 04 20:28:37 It would get rid of many of these concerns. -2008 Dec 04 20:29:00 ok this could be handled later, jmbsvicetto can i wrote you as man taking care of eapi2only? -2008 Dec 04 20:29:03 We have what we have and I didn't want changes to hose peoples systems. -2008 Dec 04 20:29:59 <-- kaffeedoktor (n=kaffeedo@rps3741.ovh.net) has quit (Remote closed the connection) -2008 Dec 04 20:30:24 --> kaffeedoktor (n=kaffeedo@rps3741.ovh.net) has joined #gentoo-kde -2008 Dec 04 20:30:35 ok for next issue i see is wrong SLOT for our kde4 packages in the tree -2008 Dec 04 20:30:41 scarabeus: sure -2008 Dec 04 20:30:41 how to deal that -2008 Dec 04 20:30:51 i did something that should work for ktorrent -2008 Dec 04 20:30:59 hm ill have a look -2008 Dec 04 20:31:01 but i hope there will be better solution for the others -2008 Dec 04 20:31:12 scarabeus: what "wrong" slot? -2008 Dec 04 20:31:16 they use 4.1 -2008 Dec 04 20:31:21 -*- cryos|work is confused too. -2008 Dec 04 20:31:25 what used to mark kde they work -2008 Dec 04 20:31:34 but with new eclasses they should be marked as app version -2008 Dec 04 20:31:36 not slot of kde -2008 Dec 04 20:31:53 What app version? -2008 Dec 04 20:32:00 for example -2008 Dec 04 20:32:04 ktorrent has version 3 -2008 Dec 04 20:32:07 and 2 -2008 Dec 04 20:32:10 in the tree -2008 Dec 04 20:32:15 so 2 is slot:0 -2008 Dec 04 20:32:19 and 3 is slot:3 -2008 Dec 04 20:32:25 but now it was slot:4.1 -2008 Dec 04 20:32:28 cryos|work: I know what he means -2008 Dec 04 20:32:34 2 is for kde3? -2008 Dec 04 20:32:39 reavertm: yes -2008 Dec 04 20:32:43 cryos|work: The code used to apply only for packages in kde-base, that restriction was removed -2008 Dec 04 20:32:54 Can the two actually be slotted? -2008 Dec 04 20:33:02 That is another issue -2008 Dec 04 20:33:05 isn't this an issue only for -kdeprefix? -2008 Dec 04 20:33:08 Is it wise to remove the restriction? -2008 Dec 04 20:33:21 Are they all going into kdeprefix now? -2008 Dec 04 20:33:22 cryos|work: yes it is working as charm :] -2008 Dec 04 20:33:34 cryos|work: probably not, but it was done to enforce the use of prefix in kde-misc -2008 Dec 04 20:33:34 cryos|work: yes all packages sets themself based on kdeprefix -2008 Dec 04 20:33:50 I mean, if kde3 apps are going to /usr/kde/3.5 soon, there should be no issue anymore -2008 Dec 04 20:34:20 reavertm: That means we'll get with the kde3 apps the same issue we currently have with kde4 apps - they stop working after you bump kde version -2008 Dec 04 20:34:23 What about with -kdeprefix? They are still good I assume? -2008 Dec 04 20:34:40 The slot is changed, but the install location is still /usr -2008 Dec 04 20:35:01 well, kde3 will be no longer revbumped I'm afraid -2008 Dec 04 20:35:02 So they do the funky blocker that allows simulataneous files that collide, -2008 Dec 04 20:35:15 cryos|work: yes - that needs to be fixed -2008 Dec 04 20:35:22 jmbsvicetto hm i thought every future version of ktorrent for example it stays in the 3 slot right? -2008 Dec 04 20:35:33 cryos|work: i will give you my list of thoughts for kde3 -2008 Dec 04 20:35:38 and with the other extragear apps too -2008 Dec 04 20:35:57 cryos|work: http://dev.gentoo.org/~scarabeus/kde3-misc_packages.txt -2008 Dec 04 20:36:06 with scarabeus update yes. It was going to be 4.X without it -2008 Dec 04 20:36:07 krytzz: yep -2008 Dec 04 20:36:12 If you are installing the app into the kdeprefix then it makes sense for it to share the slot of the prefix dir it goes into. -2008 Dec 04 20:36:28 <-- deathwing00 (n=deathwin@gentoo/developer/Deathwing00) has quit ("Leaving.") -2008 Dec 04 20:36:32 cryos|work: well it can go to -kdeprefix too -2008 Dec 04 20:36:35 cryos|work: That was my thought, but now I have my doubts -2008 Dec 04 20:36:51 and you cant make dynamic slot -2008 Dec 04 20:37:03 cryos|work: amarok stopped working here with 4.1.80 because it was installed with 4.1.3, even though I still have 4.1.3 around -2008 Dec 04 20:37:07 sice ktorrent-3.1 now can go intoo 4.1 4.2 and live dirs -2008 Dec 04 20:37:20 That is why I have always had my doubts about slotting apps not released with the main KDE modules, you have to make artificial bumps I guess to other packages? -2008 Dec 04 20:37:40 How does ktorrent decide which prefix to install to? -2008 Dec 04 20:37:40 cryos|work: at this point I really don't know what to do -2008 Dec 04 20:38:05 :( -2008 Dec 04 20:38:07 This scheme sounds really messy, but I haven't been using it and so don't know what to say. -2008 Dec 04 20:38:16 cryos|work: One idea that crossed my mind was to install these apps into /usr/kde/apps/${PN}/${PV} -2008 Dec 04 20:38:24 the easiest would be to allow only one KDE4 installed... -2008 Dec 04 20:38:41 -*- cryos|work kinda suggested that... -2008 Dec 04 20:38:48 but scarabeus tried doing that and couldn't get it working with symlinks -2008 Dec 04 20:38:58 yeah i failed there too much -2008 Dec 04 20:39:03 it was not working for me -2008 Dec 04 20:39:10 Having so many options can be extremely tough to support. -2008 Dec 04 20:39:13 feel free to do it again for yourself -2008 Dec 04 20:39:21 cryos|work: i know :( -2008 Dec 04 20:40:06 That is why many distros choose not to do this, and it has bitten us many times in the past. 3.5 is simpler now due to no more bumps. -2008 Dec 04 20:40:11 cryos|work: This is another case were the real solution would be for upstream to think about this and provide a solution for having multiple versions in the same prefix -2008 Dec 04 20:40:36 we should try to push versioning on upstream -2008 Dec 04 20:40:40 that is not bad idea -2008 Dec 04 20:40:41 I agree with you entirely -2008 Dec 04 20:40:55 has anyone asked for this already? -2008 Dec 04 20:41:07 cryos|work: You've talked before with upstream about this, haven't you? -2008 Dec 04 20:41:12 I do think having multiple minor versions available to people who do not really know what they are doing is possibly a recipe for failure... -2008 Dec 04 20:41:28 jmbsvicetto: Yes, and I will probably talk about it again at Camp KDE in January. -2008 Dec 04 20:41:48 Many other distro developers also very much wanted this, and to a degree it works. -2008 Dec 04 20:41:56 Didn't you have a presentation you did about this issue? -2008 Dec 04 20:41:57 Not to the degree Gentoo would like though. -2008 Dec 04 20:42:08 Yes - it is on my blog somewhere. -2008 Dec 04 20:42:22 That should be an interesting reading for people in the team -2008 Dec 04 20:42:49 <-- MartyMcFly (n=martin@dslb-088-064-190-153.pools.arcor-ip.net) has quit (Remote closed the connection) -2008 Dec 04 20:43:03 yeah i would like to see it :] -2008 Dec 04 20:43:23 hm but with -kdeprefix there is no problem then... if the ABI is stable -2008 Dec 04 20:43:38 http://blog.cryos.net/archives/146-Gentoo-KDE-Talk-at-aKademy.html -2008 Dec 04 20:44:58 ok next point is more nice and all developers are needed: we need some lead, so people can oficialy find one, /me is proposing jmbsvicetto O:P (meantime looking on presentation on second monitor) -2008 Dec 04 20:45:00 I will be preparing half of the talk for the KDE and distros talk in January - so let me know if there are things you would like to be raised. -2008 Dec 04 20:45:46 -*- cryos|work never really saw the need for the hierarchy in small herds, but whatever makes you happy. -2008 Dec 04 20:46:23 --> Scorcere1 (n=Scorek@77-87-120-128.rev.masterkom.pl) has joined #gentoo-kde -2008 Dec 04 20:46:28 The KDE herd didn't have a lead for years and flourished, then dwindled... It is all about building a friendly community (lead or no). -2008 Dec 04 20:46:58 I agree with cryos|work about having a friendly community -2008 Dec 04 20:47:00 i have nothing against it :p -2008 Dec 04 20:47:05 :D -2008 Dec 04 20:47:31 Oh and I'm not that eager to get the "lead" hat :P -2008 Dec 04 20:47:32 i dont mind how this will evolve so i leave this one definetly up to all -2008 Dec 04 20:47:44 jmbsvicetto: yeah i am pretty sure of this :D -2008 Dec 04 20:47:54 noone wants to be lead i would say -2008 Dec 04 20:47:56 i think we should have a leader just as the other herds do -2008 Dec 04 20:48:05 not because we need someone to decide -2008 Dec 04 20:48:16 A quick note - team and not herd :P -2008 Dec 04 20:48:27 We're talking about the people and not about the packages ;) -2008 Dec 04 20:48:41 i will be the queen ;) -2008 Dec 04 20:48:41 jmbsvicetto: herd is missused for this for so long... -2008 Dec 04 20:48:44 --> dagger (n=dagger@piasek.co.uk) has joined #gentoo-kde -2008 Dec 04 20:49:06 i think word herd needs redefinition but it is not on todays topic -2008 Dec 04 20:49:12 -*- cryos|work never got why people were so picky about the words used, is it really a herd of packages? :D -2008 Dec 04 20:49:34 a bunch of packages -2008 Dec 04 20:49:35 ok so no lead for now, when times change jmbsvicetto is first on the row :P -2008 Dec 04 20:49:41 gentoo kde-bunch-of-people -2008 Dec 04 20:49:56 It is work time for me over here, I could do with getting stuff done soon. So I may leave in 5-10 mins. -2008 Dec 04 20:49:59 moving on to other not so pleasant topic, I think we need to look at the team members again - afaik, we have people listed in the kde page that haven't done anything kde related for many, many months -2008 Dec 04 20:50:06 <-- comawhite (n=comawhit@unaffiliated/comawhite) has quit ("Leaving") -2008 Dec 04 20:50:26 --> tgurr (n=tgurr@gentoo/developer/tgurr) has joined #gentoo-kde -2008 Dec 04 20:50:26 -=- Mode #gentoo-kde [+o tgurr] by ChanServ -2008 Dec 04 20:50:36 Hi tgurr -2008 Dec 04 20:50:40 agreed, we should clean it up, ask everyone if they are willing to do something and so on (does not count for people that are mentioned away) -2008 Dec 04 20:50:46 jmbsvicetto: hi -2008 Dec 04 20:50:58 <-- erulabs (n=seandon@net-cf9a4013.noc.impulse.net) has quit ("Leaving.") -2008 Dec 04 20:51:05 <-- JaMa (n=JaMa@chaos.mk.cvut.cz) has quit (Remote closed the connection) -2008 Dec 04 20:51:32 Getting to the same old same, it would help if all the members would be willing to join irc, but I don't have any illusions about getting some people in here -2008 Dec 04 20:51:50 jmbsvicetto: are you willing to mail them -2008 Dec 04 20:52:06 About being team members, sure? -2008 Dec 04 20:52:11 ok -2008 Dec 04 20:52:16 i am writing up notes -2008 Dec 04 20:52:20 so we have them after end -2008 Dec 04 20:52:21 :] -2008 Dec 04 20:52:38 about members -2008 Dec 04 20:52:42 we have problem in qt herd -2008 Dec 04 20:52:46 it is just yngwin -2008 Dec 04 20:53:00 how to get some qt devepoer :] -2008 Dec 04 20:53:05 I can even do something better, send a mail to the kde alias and ask everyone for a little introspection and to let us know if they're still part of the team and or want to be part of the team ;) -2008 Dec 04 20:53:20 jmbsvicetto: that i leave up to you :] -2008 Dec 04 20:53:22 scarabeus: I thought carlo and caleb where still in the team -2008 Dec 04 20:53:39 they are but they are inactive and non-responsive -2008 Dec 04 20:53:40 did you hear/see some commits from them in last month/2 -2008 Dec 04 20:53:41 scarabeus: with the obvious reservations about the above point -2008 Dec 04 20:53:56 yngwin: ok, just wanted to confirm -2008 Dec 04 20:54:04 reavertm: maybe you might be interested -2008 Dec 04 20:54:11 well, no major qt release recently so they may just wait for 4.5 -2008 Dec 04 20:54:21 yngwin: I'll talk to you about qt -2008 Dec 04 20:54:22 in qt maintenance a bit? -2008 Dec 04 20:54:28 and that reminds me, yngwin should get commit acces to kde-crazy -2008 Dec 04 20:54:32 reavertm: yes -2008 Dec 04 20:54:57 yngwin: do you have access to kde-testing? If not, you should also have it -2008 Dec 04 20:54:58 does bonsaikitten have access? :p -2008 Dec 04 20:55:11 jmbsvicetto: i dont -2008 Dec 04 20:55:16 krytzz: silence there! ;D -2008 Dec 04 20:55:21 unless i do but dont know it -2008 Dec 04 20:55:33 hmm, well I can try by forget about Qt from Trolltech svn fro bow - they shit svn only as daily snapshots via rsync -2008 Dec 04 20:55:37 bonsaikitten: I forgot to tell you, but robbat2 replied to me earlier saying you should have access now -2008 Dec 04 20:55:46 jmbsvicetto: ok, let me try :) -2008 Dec 04 20:55:57 for now^^ -2008 Dec 04 20:55:58 also, phonecall, I kinda missed the last half hour or so -2008 Dec 04 20:56:01 ok, my purpose with the kde-* overlays was for everyone on the team to have access to them -2008 Dec 04 20:56:10 yeah agreed -2008 Dec 04 20:56:36 I initially asked jokey to grant access to everyone at the time in the team. I haven't followed it through, so I'll talk to robbat2 again asking for an update about the current status -2008 Dec 04 20:56:52 and i took the liberty and added yngwin to team list on kde page, since it is project page for qt and kde, not only kde, i think i forget to mention that before for that i am ashamed -2008 Dec 04 20:57:05 ok tnx -2008 Dec 04 20:57:18 maybe i should get op status here then as well -2008 Dec 04 20:57:18 scarabeus: Yes, you're right -2008 Dec 04 20:57:22 sure -2008 Dec 04 20:57:30 keytoaster: I think it has to be you doing it -2008 Dec 04 20:57:45 keytoaster: iirc, we transfered +F to you -2008 Dec 04 20:58:57 oooh. can has access :D -2008 Dec 04 20:59:01 yngwin: seems I was able to grant it to you -2008 Dec 04 20:59:06 DrEeevil: you fail. -2008 Dec 04 20:59:08 <-- NSaibot (n=quassel@i3ED6C704.versanet.de) has quit (Remote closed the connection) -2008 Dec 04 20:59:12 bonsaikitten: :) -2008 Dec 04 20:59:32 ok one more infra thing -2008 Dec 04 20:59:36 -=- Mode #gentoo-kde [+o yngwin] by jmbsvicetto -2008 Dec 04 20:59:44 tampakrap would need normal mentor if he wants to became full dev -2008 Dec 04 20:59:51 i am willing to help him with the quiz -2008 Dec 04 20:59:57 but someone must oversee -2008 Dec 04 20:59:59 who can do that -2008 Dec 04 21:00:11 I'm too young for that I think -2008 Dec 04 21:00:14 end-quiz we are speaking about -2008 Dec 04 21:00:15 I'm also willing to help, but I still don't have the 6 months, so I can't mentor -2008 Dec 04 21:00:16 --> genady12 (n=genady12@87.69.85.204) has joined #gentoo-kde -2008 Dec 04 21:00:17 first of all is everyone ok with that? -2008 Dec 04 21:00:19 my quantum status is confusing -2008 Dec 04 21:00:31 -*- bonsaikitten is 2 years on, 2 years off ... -2008 Dec 04 21:00:42 bonsaikitten: You're *chaotic* ;) -2008 Dec 04 21:00:44 bonsaikitten: ;] you are cheating :D -2008 Dec 04 21:00:47 i am -2008 Dec 04 21:00:55 so is that 2 years or 2 months now? :) -2008 Dec 04 21:00:57 --> oc2k1 (n=oc2k1@p5B104618.dip.t-dialin.net) has joined #gentoo-kde -2008 Dec 04 21:01:16 bonsaikitten: we need to ask Betelgeuse -2008 Dec 04 21:01:22 :) -2008 Dec 04 21:01:39 I think it is better if I stay out of it for a while -2008 Dec 04 21:01:39 perhaps jokey could do it? -2008 Dec 04 21:01:54 krytzz: jokey is away -2008 Dec 04 21:01:56 i thought jokey was caught up in real life -2008 Dec 04 21:01:57 jokay is away -2008 Dec 04 21:02:01 ok -2008 Dec 04 21:02:06 yngwin: you cant do it? -2008 Dec 04 21:02:19 i can -2008 Dec 04 21:02:29 although i dont feel guru enough -2008 Dec 04 21:02:53 :] -2008 Dec 04 21:03:07 yngwin: you are guru enough! -2008 Dec 04 21:03:14 dont worry, from mine humble PoV you are guru enought -2008 Dec 04 21:03:16 well, if you say so :) -2008 Dec 04 21:03:27 :) -2008 Dec 04 21:03:36 thanks :) -2008 Dec 04 21:03:52 is there a bug for tampakrap's recruitment? -2008 Dec 04 21:04:01 no -2008 Dec 04 21:04:02 keytoaster: yes you did -2008 Dec 04 21:04:06 err -2008 Dec 04 21:04:08 <-- Scorcerer (n=Scorek@77-87-120-128.rev.masterkom.pl) has quit (Connection timed out) -2008 Dec 04 21:04:08 -=- Scorcere1 is now known as Scorcerer -2008 Dec 04 21:04:08 jmbsvicetto: yes you did -2008 Dec 04 21:04:21 yngwin: nope i can create one, i made him HT yesterday -2008 Dec 04 21:04:27 okay -2008 Dec 04 21:04:42 I let it pass, but since scarabeus mentioned the project page, we both applied some changes to the page to integrate KDE4 as a regular release and to update the status of the overlays -2008 Dec 04 21:04:58 Don't know if everyone has checked it and whether there's any objection to it -2008 Dec 04 21:05:03 scarabeus: then i'll second on that, and then we can see what betelgeuse says -2008 Dec 04 21:05:09 <-- scratch[x] (n=scratch@83.239.148.148) has quit (No route to host) -2008 Dec 04 21:05:14 tampakrap: kaloriziko ;) -2008 Dec 04 21:05:23 wtf? -2008 Dec 04 21:05:25 we can do this stuff after meeting, great :] -2008 Dec 04 21:05:43 ok last two things per my list -2008 Dec 04 21:05:46 first is kde4.2 -2008 Dec 04 21:05:50 so what shape is it in -2008 Dec 04 21:05:56 it is just statusreport for it -2008 Dec 04 21:06:00 scarabeus: Good and BAD!!! -2008 Dec 04 21:06:01 so speak up kde-crazy people -2008 Dec 04 21:06:04 I'll take care of them snapshots -2008 Dec 04 21:06:09 well, it works :) -2008 Dec 04 21:06:15 i'll also give priority to snapshots -2008 Dec 04 21:06:21 plasma crashes often :p -2008 Dec 04 21:06:22 kde 4.2? its crap. it friggin' needs mysql -2008 Dec 04 21:06:28 scarabeus: my keyboard layout is still messed up - but nepomuk and plasma have a better look ;) -2008 Dec 04 21:06:36 it works quite well for me -2008 Dec 04 21:06:41 also for me nepomuk is strange -2008 Dec 04 21:06:46 had a few compile failures, but nothing unexpected -2008 Dec 04 21:06:54 I guess trunk is way better than snapshots, but... regressions are quite often recently -2008 Dec 04 21:07:01 but rest is ok -2008 Dec 04 21:07:02 ebuild-wise - it's pretty mature -2008 Dec 04 21:07:14 One important point about snapshots, they can't rely on live packages -2008 Dec 04 21:07:24 live is in a very good shape, snapshots have been a bit neglected -2008 Dec 04 21:07:25 but upstream will mess with buildsystem for sure -2008 Dec 04 21:07:31 -*- bonsaikitten is just digesting them -2008 Dec 04 21:07:35 So we need to bug other teams or add new versions/snapshots if required to the overlay/tree -2008 Dec 04 21:07:50 especially opensync :p -2008 Dec 04 21:07:55 opensync is problem -2008 Dec 04 21:07:57 currently -2008 Dec 04 21:08:20 and also networkmanager, i took liberty of speaking up with rbu on our behalf -2008 Dec 04 21:08:31 opensync and it;s plugins were problematic with kde3 already -2008 Dec 04 21:08:34 and today/tomorow nm-0.7 hit the tree -2008 Dec 04 21:08:38 scarabeus: one solution is to try to add an update to kde-crazy overlay until it gets in the tree -2008 Dec 04 21:08:52 ah nice -2008 Dec 04 21:08:55 kitchensync is just lame kde3 port -2008 Dec 04 21:08:59 scarabeus: rbu has shown interest in getting nm working -2008 Dec 04 21:09:03 yes -2008 Dec 04 21:09:08 scarabeus: he might need some help with it, though -2008 Dec 04 21:09:09 he already made it work -2008 Dec 04 21:09:17 jmbsvicetto: well i will ask -2008 Dec 04 21:09:48 The GNOME team was also interested in getting 0.7 in the tree, iirc -2008 Dec 04 21:10:19 yeah, everyone is crazy about those networkmanager desktop applets... -2008 Dec 04 21:10:42 can we prevent such cross-repo dependencies in the future? -2008 Dec 04 21:10:54 I would just love to get some applet that does the eap stuff for me ;) -2008 Dec 04 21:11:05 bonsaikitten: what deps? -2008 Dec 04 21:11:08 there will be rule for next time all must be on portage/overlay -2008 Dec 04 21:11:14 like nm -2008 Dec 04 21:11:23 like kde4 requiring nm from rbu overlay -2008 Dec 04 21:11:24 we should have a copy in our repo if that happens -2008 Dec 04 21:11:31 yeah, agreed -2008 Dec 04 21:11:36 hm but this sucks somehow -2008 Dec 04 21:11:44 if you have both overlays you have the ebuild 2 times -2008 Dec 04 21:11:50 at least until we can get Zac to support repo deps ;) -2008 Dec 04 21:11:50 and you dont know if the 2 differ or something -2008 Dec 04 21:12:05 repodeps ;] -2008 Dec 04 21:12:10 it sounds llike sam rep band -2008 Dec 04 21:12:11 also its additional maintenance work -2008 Dec 04 21:12:25 talking about overlays i'd like to remind everyone that versioned misc packages go to kde-testing :) -2008 Dec 04 21:12:35 krytzz: yes, we should only have them until it gets pushed into the tree -2008 Dec 04 21:12:36 yeah, i just see GLEP for it being discussed, then presented, then rejected or suspended :P -2008 Dec 04 21:12:39 ok tampakrap :p -2008 Dec 04 21:13:02 ok so what with opensync -2008 Dec 04 21:13:06 it is BbD -2008 Dec 04 21:13:08 tampakrap: versioned "not known to be broken" misc packages ;) -2008 Dec 04 21:13:13 broken by design -2008 Dec 04 21:13:13 i wouldnt mind with a central gentoo-deps overlay :p -2008 Dec 04 21:13:30 we call that "the main tree" -2008 Dec 04 21:13:38 scarabeus you mean opensync akonadi plugin or kitchensync? -2008 Dec 04 21:13:44 so, how fast are we going to get 4.2 there as ~arch? -2008 Dec 04 21:13:51 bonsaikitten then stab people to get things faster in there then :p -2008 Dec 04 21:13:54 and is kde 4.2 a stable candidate? -2008 Dec 04 21:14:06 bonsaikitten: I don't think we should get 4.2 in the tree until RC -2008 Dec 04 21:14:09 yeah crappy opensync -2008 Dec 04 21:14:16 krytzz: I'm just cleaning up. If that's not enough go screw yourself counterclockwise ;) -2008 Dec 04 21:14:24 bonsaikitten: I would also hard mask the RCs and lift the mask with 4.2 -2008 Dec 04 21:14:25 i think it is time to have a stable kde4 version -2008 Dec 04 21:14:31 jmbsvicetto: acceptable -2008 Dec 04 21:14:48 scarabeus yes, but be more specific, opensync from portage is crappy or kde opensync support? -2008 Dec 04 21:14:49 i think if the 4.2 progress continues like know it should be great by 4.2.1 -2008 Dec 04 21:14:58 opensync from portage -2008 Dec 04 21:14:59 now -2008 Dec 04 21:14:59 bonsaikitten: we might however start thinking on moving 4.2 into kde-testing -2008 Dec 04 21:15:02 opensync itself -2008 Dec 04 21:15:09 bonsaikitten: at least as soon as we take care of the eclasses -2008 Dec 04 21:15:17 eclasses first! :D -2008 Dec 04 21:15:17 jmbsvicetto: +1 -2008 Dec 04 21:15:34 and I do think 4.2 should be a stable candidate - let's just see how it works -2008 Dec 04 21:15:47 one thing we need to solve quickly is getting 3.5.10 marked stable -2008 Dec 04 21:16:05 that is already stated in the summary paper :] -2008 Dec 04 21:16:08 jmbsvicetto which 4.2? you mean snapshots and revbump as 4.2 and keep them updated along with snaphots from kde-crazy? -2008 Dec 04 21:16:10 jmbsvicetto: i'll start working on kde3 right after this meeting -2008 Dec 04 21:16:18 if yes, then you are crazy ;) -2008 Dec 04 21:16:33 why? -2008 Dec 04 21:16:35 nope to testing should go only snapshots marked as betaX -2008 Dec 04 21:16:36 reavertm: I mean that I think 4.2 snapshots should be moved to testing -2008 Dec 04 21:16:45 reavertm: after the eclasses are merged back again -2008 Dec 04 21:16:49 snapshot itself i disagree -2008 Dec 04 21:16:57 but snapshots for beta1 beta2 rcX -2008 Dec 04 21:16:58 yes -2008 Dec 04 21:17:04 scarabeus: yes, that's what I mean -2008 Dec 04 21:17:10 should have been clearer -2008 Dec 04 21:17:16 I wouldn't advise that atm - there may be many changes and syncing them between kde-crazy <-> kde-testing ... -2008 Dec 04 21:17:17 great then we agree :] -2008 Dec 04 21:17:34 reavertm: just delete it and copy from point A to point B -2008 Dec 04 21:17:39 reavertm: git cherry-pick ;) -2008 Dec 04 21:17:41 it wont harm kittens TM -2008 Dec 04 21:17:52 jmbsvicetto: cherry-pick cross repos? -2008 Dec 04 21:17:56 yes -2008 Dec 04 21:17:58 wow -2008 Dec 04 21:18:00 that i didnt know -2008 Dec 04 21:18:05 that is even more cooler -2008 Dec 04 21:18:11 scnaphots are keep sync from live now - and I would just wait until some rc is released, and patched in kde-crazy and then quick revbup and move -> testing -2008 Dec 04 21:18:28 scarabeus: hmm, now you're going to force me to test it to be sure I didn't came up with that -2008 Dec 04 21:18:36 well, if you volunteer to do it :) -2008 Dec 04 21:19:14 <-- genady12 (n=genady12@87.69.85.204) has quit (Read error: 145 (Connection timed out)) -2008 Dec 04 21:19:15 ok this can be suspended and handled later -2008 Dec 04 21:19:20 reavertm: The idea was to try to have RCs in the tree, so we should try to get something in testing before that -2008 Dec 04 21:19:21 now more pain in the ass TM issue -2008 Dec 04 21:19:25 mysql -2008 Dec 04 21:19:28 whole kde needs it -2008 Dec 04 21:19:33 aarghl! :) -2008 Dec 04 21:19:33 and amarok is chapter itself -2008 Dec 04 21:19:42 what to do with it -2008 Dec 04 21:19:43 scarabeus: There's only one option here: work with robbat2 -2008 Dec 04 21:19:50 yes... we cant do anything about that :( -2008 Dec 04 21:19:58 did you see the eclass -2008 Dec 04 21:19:58 yes, I agres 4.2 should be in tree asap but moving it to testing only for the sake of having it in kde-testing is bad idea imho -2008 Dec 04 21:20:01 does he maintain mysql? -2008 Dec 04 21:20:04 did? did? i dont like it -2008 Dec 04 21:20:09 krytzz: yes he does -2008 Dec 04 21:20:09 scarabeus: I've asked him yesterday and he's still waiting for mysql upstream to reply to his request for a dynamic lib for mysql/e -2008 Dec 04 21:20:17 I've already put my mysql rant in gentoo-dev :P -2008 Dec 04 21:20:17 ah ok -2008 Dec 04 21:20:31 scarabeus: what do you mean? -2008 Dec 04 21:21:03 jmbsvicetto: too chaotical too much patches too much crazy -2008 Dec 04 21:21:11 but i dunno how is upstream cooperating -2008 Dec 04 21:21:19 reavertm: The point of kde-testing is to be the bridge to the tree -2008 Dec 04 21:21:28 ok on other hand who is willing to cooperate with robbat2 on that? -2008 Dec 04 21:21:32 scarabeus: you mean mysql eclass? -2008 Dec 04 21:21:37 jmbsvicetto: ay sir -2008 Dec 04 21:21:46 scarabeus: mysql isn't that "simple" -2008 Dec 04 21:22:05 scarabeus: And robbat2 if surely one if not the "one" gentoo mysql yoda -2008 Dec 04 21:22:09 s/if/is/ -2008 Dec 04 21:22:12 I've seen this eclass and it's.. well.. a bit complex as eclass for one package -2008 Dec 04 21:22:34 reavertm: it adds a build system to a braindead package ;) -2008 Dec 04 21:22:39 scarabeus: I'm willing to work with robbat2 about mysql -2008 Dec 04 21:22:58 yeah, I heard.... -2008 Dec 04 21:23:09 --> genady12 (n=genady12@87.69.85.204) has joined #gentoo-kde -2008 Dec 04 21:23:12 great puting you to the txt :] -2008 Dec 04 21:23:27 ok issues from my side mentioned -2008 Dec 04 21:23:32 scarabeus: I'll have to check that text - it feels like I'm being "canned" ;) -2008 Dec 04 21:23:36 someone else has something that needs to be handled -2008 Dec 04 21:23:49 jmbsvicetto: dont worry i try to make it to be factical -2008 Dec 04 21:23:58 is there an open bug for 3.5.10 stabilization? -2008 Dec 04 21:24:01 yes -2008 Dec 04 21:24:08 if not let's create one to sum up the issues -2008 Dec 04 21:24:12 ok then -2008 Dec 04 21:24:15 yeah, about the kde-plasma category: could we do it? -2008 Dec 04 21:24:15 If ctrl+f3 worked here, I could get you the number quicker ;) -2008 Dec 04 21:24:17 i'll search -2008 Dec 04 21:24:24 bug kde-3.5.10 -2008 Dec 04 21:24:27 do you like it? -2008 Dec 04 21:24:44 krytzz: I don't think we should go down that route -2008 Dec 04 21:25:13 ok what are the alternatives -2008 Dec 04 21:25:14 krytzz: If we try to get kde-plasma, kde-plasmoids, ..., we're going to create resistance -2008 Dec 04 21:25:28 no, only kde-plasma jmbsvicetto for everything plasma-related -2008 Dec 04 21:25:31 kde-plasma only it is going to be -2008 Dec 04 21:25:32 we've lived with kde-base and kde-misc for a long, long time -2008 Dec 04 21:25:34 could we have plasmoids for more than one version? and in case of slotted kde's, could we install a plasmoid for every session? -2008 Dec 04 21:25:59 how many packages are we talking and what type of packages -2008 Dec 04 21:25:59 tampakrap: nope it is same as misc packages for more kde installs -2008 Dec 04 21:26:09 tampakrap they won't build that easy -2008 Dec 04 21:26:11 jmbsvicetto: plasma aplets and enginges -2008 Dec 04 21:26:15 hm ok thats just personal preference how filled the categories are, but i prefer fewer packages per category -2008 Dec 04 21:26:28 currently about 150 on kde-apps/look -2008 Dec 04 21:26:39 and we can bundle them all in the end -2008 Dec 04 21:26:54 scarabeus: if we're talking about kde-look, perhaps we're going down the wrong path -2008 Dec 04 21:26:58 categories are bad btw, some tag clouds should be introduced one day... -2008 Dec 04 21:27:10 scarabeus: I'm thinking if we couldn't try to do something similar to what the perl team did with cpan -2008 Dec 04 21:27:15 --> Eythan (n=Eythan@AMontpellier-152-1-30-159.w81-251.abo.wanadoo.fr) has joined #gentoo-kde -2008 Dec 04 21:27:16 reavertm one day... yes :p -2008 Dec 04 21:27:22 jmbsvicetto: what they did -2008 Dec 04 21:27:40 some perl magic i guess ;] -2008 Dec 04 21:27:45 yup ;) -2008 Dec 04 21:28:09 --> fedux (n=fedux@190.55.126.139) has joined #gentoo-kde -2008 Dec 04 21:28:11 app-portage/g-cpan g-cpan: generate and install CPAN modules using portage -2008 Dec 04 21:28:19 hm -2008 Dec 04 21:28:58 i assume this is like ruby gems? -2008 Dec 04 21:28:59 so dedicated tool only for some plasmoids? -2008 Dec 04 21:29:24 not worth it imho -2008 Dec 04 21:29:31 I haven't looked at their implementation, but if I'm not mistaken, they've created a tool to help install packages in cpan. So instead of having one ebuild for every kde-look package, we could try to have some tool that helps install packages from kde-look -2008 Dec 04 21:29:38 i thought that upstream was going to apply a tool for downloading and easy installing plasmoids -2008 Dec 04 21:29:53 yeah kde-look, but plasmoids still have to be compiled -2008 Dec 04 21:30:04 cpan stuff not -2008 Dec 04 21:30:07 and have various dependencies -2008 Dec 04 21:30:31 No way to get them working without ebuilds? -2008 Dec 04 21:30:34 tampakrap hm but only for script plasmoids? -2008 Dec 04 21:30:34 and apply to different kde versions -2008 Dec 04 21:30:44 i'm not sure -2008 Dec 04 21:30:48 well, actually I was thinking about some ebuild generator with automatic depencency discovering (originally for plasmoids from playground) -2008 Dec 04 21:31:11 jmbsvicetto: not bad idea -2008 Dec 04 21:31:13 I think we need to think more about this -2008 Dec 04 21:31:17 writing it down as long-term goal -2008 Dec 04 21:31:18 while ebuild generator (without deps) I got done already, eclass is not yet ready for fetch/unpack from playground -2008 Dec 04 21:31:56 Are plasmoids "heavy"? -2008 Dec 04 21:32:09 some of them -2008 Dec 04 21:32:12 very few -2008 Dec 04 21:32:13 some are pretty normal c++ apps, so i would say yes -2008 Dec 04 21:32:33 the script ones can be installed by plasma, we dont have to care about these -2008 Dec 04 21:33:38 Anything else? -2008 Dec 04 21:33:45 well, we could do as well some knewstuff2 interface for kde4 for plasmoids but we're not kde devs.. -2008 Dec 04 21:34:10 (it could reduce problem of plasmoids to installing them as icon themes) -2008 Dec 04 21:34:26 yeah debug useflag in eclass -2008 Dec 04 21:34:33 but ok this was already discussed -2008 Dec 04 21:34:41 it is on dev already -2008 Dec 04 21:34:45 was it? -2008 Dec 04 21:34:45 ah ok -2008 Dec 04 21:34:46 so lets see how that evolve -2008 Dec 04 21:34:53 aa, my proposition? -2008 Dec 04 21:34:59 reavertm: we might have to write it as glep -2008 Dec 04 21:35:00 it won't evolve... -2008 Dec 04 21:35:03 and push it trhought -2008 Dec 04 21:35:38 no way, just pass - it's against "ultimate freedom" and to package manager specific -2008 Dec 04 21:35:45 i dont care they are picky about it, i think they would not agree with anything that does not worship their ethernal glory (dont cite me that is just brief overview of those flames) -2008 Dec 04 21:35:46 as it uses FEATURES -2008 Dec 04 21:36:43 anyway, "our own" debug suport you mean? -2008 Dec 04 21:37:03 well, "additiomnal debug codepaths" are supported already -2008 Dec 04 21:38:01 hm so scarabeus whats the role model for kde-misc ebuilds now? -2008 Dec 04 21:38:22 krytzz: have no idea -2008 Dec 04 21:38:29 everything what is not in kde-base -2008 Dec 04 21:38:32 actually I see no role for kde-misc really - never seen -2008 Dec 04 21:38:32 from what i can see -2008 Dec 04 21:38:44 ok, kdevelop, kdesvn then? -2008 Dec 04 21:39:03 hm -2008 Dec 04 21:39:09 oh it is mess like hell -2008 Dec 04 21:39:14 kdevelop is in KDE even and it will be in kde-base soon I guess (released as part of KDE) -2008 Dec 04 21:39:21 it is messy a bit -2008 Dec 04 21:40:00 ok is this still part of meeting chat or we can dismisso ourselfs? -2008 Dec 04 21:40:11 i have nothing further -2008 Dec 04 21:40:12 oh typos it is going to kill me one day -2008 Dec 04 21:40:39 scarabeus bug wranglers - needed or not? -2008 Dec 04 21:40:47 not now, we have pretty big list -2008 Dec 04 21:40:59 i will write it onto longterm with you as person interested -2008 Dec 04 21:40:59 ok -2008 Dec 04 21:41:01 ? -2008 Dec 04 21:41:37 I think you're looking at it from the wrong pov - bug-wranglers -2008 Dec 04 21:41:40 well, I'm not going to push if it's seen not necessary -2008 Dec 04 21:42:13 ok, i'm putting in a staffing-needs/recruitment request for developers and/or herd testers for qt herd -2008 Dec 04 21:42:16 I would like to model it a bit like KDE team, at least have more of them than 1 -2008 Dec 04 21:42:25 We don't need bug wranglers to look at new bugs and check if they're kde bugs. We need people that work through kde bugs and help get them resolved - by providing patches, by doing tests, by interacting with users. -2008 Dec 04 21:42:31 ok when the eclasses are merged every kde-testing ebuild should have the KDE_MINIMUM thing scarabeus? -2008 Dec 04 21:42:42 nope -2008 Dec 04 21:42:56 krytzz: kde_minimal is only override variable -2008 Dec 04 21:43:00 it should work as they are now -2008 Dec 04 21:43:10 read up description in eclass -2008 Dec 04 21:43:13 ok -2008 Dec 04 21:43:14 ill do -2008 Dec 04 21:43:45 ok, one last request from me - if you work in the overlays, be sure to run repoman full from time to time. There's some extra cookies for those also running pcheck ;) -2008 Dec 04 21:44:04 http://dev.gentoo.org/~scarabeus/kde_meeting_state.txt -2008 Dec 04 21:44:12 and i am going to save the log from this -2008 Dec 04 21:44:13 got it ^^ -2008 Dec 04 21:44:21 should i put it onto kde space? -2008 Dec 04 21:44:37 and please try to forward my access to kde-testing, i want to do some kde3 work there -2008 Dec 04 21:45:58 scarabeus: sure diff --git a/meeting-logs/kde-herd-meeting-log-20090108.txt b/meeting-logs/kde-herd-meeting-log-20090108.txt deleted file mode 100644 index 264dc6a..0000000 --- a/meeting-logs/kde-herd-meeting-log-20090108.txt +++ /dev/null @@ -1,666 +0,0 @@ -[20:00:10] my dear friends it the time to start the meeting :] -[20:00:13] masking 4.1 shouldn't be needed -[20:00:21] MEATING -[20:00:22] it is. -[20:00:28] *ding ding ding* -[20:00:30] yes =) -[20:00:31] --> linex (n=quassel@60.54.93.166) has joined #gentoo-kde -[20:00:35] !herd kde -[20:00:36] PSYCHO___: (kde) caleb, carlo, cryos, deathwing00, genstef, jmbsvicetto, keytoaster, mattepiu, patrick, scarabeus, tgurr -[20:00:40] time for meating -[20:00:43] emerge -DuvaN world will pull in 4.1 packages unless all your world entries use :3.5 -[20:00:47] it's quite annoying actually -[20:00:49] /mode +m -[20:00:52] tehehehehehe -[20:00:53] *** Mode #gentoo-kde +v alexxy by scarabeus -[20:01:12] =) -[20:01:20] heh -[20:01:20] Thanks a lot! Have fun with the meeting. -[20:01:20] =) -[20:01:28] -*- Sput had to fix his dad's world file to avoid installing KDE4 -[20:01:28] *** Mode #gentoo-kde +v hwoarang by scarabeus -[20:02:02] --> cryos|work (n=mhanwell@gentoo/developer/cryos) has joined #gentoo-kde -[20:02:02] *** Mode #gentoo-kde +o cryos|work by ChanServ -[20:02:08] <-- mortalmatt (n=matthew@p54A6D9A6.dip.t-dialin.net) has quit ("Leaving") -[20:02:12] now we can start :) -[20:02:17] :D -[20:02:30] cant we have at least few devs anounce their presence -[20:02:37] -*- yngwin present -[20:02:44] Look in the nick list... -[20:02:52] jmbsvicetto? -[20:03:15] hello -[20:03:25] I'm using quassel -[20:03:26] cryos|work: well only you me and yngwin are online, rest is away :] -[20:03:40] bonsaikitten: ?? -[20:03:43] yes? -[20:03:44] are you there? -[20:03:46] he is :] -[20:03:50] Sucks - I nearly didn't make it. Compositing and Avogadro crashed my X server... -[20:03:54] I got the core running and I use my client to connect to it. -[20:03:56] bonsaikitten is away-faking as usual :) -[20:04:03] whut! -[20:04:16] Its just a bot! -[20:04:16] ok i guess we can wait few minutes if jmbsvicetto shows up :] -[20:04:28] or start without him? -[20:04:29] maybe reavertm too -[20:04:31] bonsaikitten: Are you turing complete? -[20:04:48] Why do I have do pane of the same channel topand below -[20:05:05] cryos|work: I doubt it, but I do have some strange loops -[20:05:13] <-- the_p (n=the_p@cust.static.62-152-211-38.swisscomdata.ch) has quit (Remote closed the connection) -[20:05:35] does anyone know when dev.gentooexperimental.org will be up again? -[20:05:47] victorlf__: it isn't? -[20:05:58] nope -[20:05:59] right -[20:06:45] --> MartyMcFly (n=martin@dslb-088-066-055-066.pools.arcor-ip.net) has joined #gentoo-kde -[20:07:27] linex: the top one is the chat monitor, it shows activity in all channels that you are in -[20:07:53] linex: you can move it -[20:08:05] linex: or hide it by rightclick -[20:08:16] why is d.ge.o so popular? -[20:08:22] in the top bar^ -[20:08:24] --> tbeadle_ (n=tbeadle@204.181.64.60) has joined #gentoo-kde -[20:08:26] because we have our files in there :] -[20:08:26] Ah ok. nice feature but I don't think I want it. Not right now. Its removable, right ? -[20:08:35] what files? -[20:09:00] -*- Sput failed getting a shell on d.ge.o yet :/ -[20:09:02] tampakrap: snapshots of phonon4exampe -[20:09:03] tampakrap: because it hots so much -[20:09:13] right. someone fscked php -[20:09:14] ah yes -[20:09:36] MrRat: I right clck. There Configure. Then what ? -[20:09:49] linex: yes rightclick in the bar above topic, where file,view,etc... is -[20:10:03] ok -[20:10:03] --> restle (n=restle@212.6.7.10) has joined #gentoo-kde -[20:10:23] see "show chat monitor" -[20:10:30] ok, its gone. Its called Chat Monitor, right ? -[20:10:44] there. -[20:11:24] Mr Rat : is it possible to have the traditional channel tabs instead of the tree-like on the left ? -[20:11:31] linex: #quassel for other quassel related help :p -[20:11:40] ok i guess we should start so we can end up reasonably and hope others show up in progress... objections? -[20:11:41] MrRat: ok fair enough -[20:12:36] <-- tbeadle_ (n=tbeadle@204.181.64.60) has quit (Read error: 54 (Connection reset by peer)) -[20:12:41] first on the nice list is just sumarising of previous meeting (read as what is not done from that list :]) -[20:12:43] no objections here -[20:12:43] --> tbeadle_ (n=tbeadle@204.181.64.60) has joined #gentoo-kde -[20:12:44] linex: however id prefer tabs myself too :p -[20:12:46] http://www.gentoo.org/proj/en/desktop/kde/meeting-logs/kde-herd-meeting-summary-20081204.txt -[20:13:04] MrRat: :) -[20:13:17] -*- cryos|work is listening... -[20:13:30] ok, what's the latest on 3.5.10 stabilizing? -[20:13:37] For the record PSYCHO___ = ? -[20:13:44] scarabeus -[20:13:44] scarabeus -[20:13:48] OK -[20:13:52] <-- tbeadle (n=tbeadle@204.181.64.60) has quit (Read error: 104 (Connection reset by peer)) -[20:14:05] <-> scarabeus is now known as frogeater -[20:14:13] <-> You are now known as scarabeus -[20:14:42] 3.5.10 is stable enough for the users but still there are many open bugs regarding it -[20:14:55] and of course there is still the issue with the misc apps -[20:15:18] is there any progress? or nobody is working on it seriously -[20:15:25] the eclass has to be updated to make them prefixed to /usr/kde/3.5 -[20:15:29] maybe we should write on dev we want some volunteers -[20:15:46] i'm ok with this -[20:15:53] as a side remark: 3.5.10 will definitely be upstream's last release -[20:15:55] --> agamn (n=agamn@ip-83-134-215-20.dsl.scarlet.be) has joined #gentoo-kde -[20:15:58] i also can work on it but was busy with quiz and other things lately -[20:15:59] ok -[20:16:00] shame -[20:16:28] some patches still go into svn, but no further releases are planned. -[20:16:36] -*- cryos|work has found it tough finding spare time to work on 3.5.10... -[20:16:44] we need it stable in order to make 4.X stable :] -[20:16:56] since only 3.5.10 has correct cryos magic :] -[20:17:11] ok but i think we should concentrate on kde-4.2 release first and then to 3.5 -[20:17:21] so let's do a call for volunteers to help squash bugs on 3.5.10 -[20:17:31] agreed -[20:17:31] ok who will sent the mail on dev? -[20:17:40] you :) -[20:17:48] I will as and when I can send the time, but currently my spare time is at a real premium :-( -[20:18:08] well i am getting my time pretty sqeezed too :] -[20:18:16] so we shall see :] -[20:19:12] ok next thing is kde4 eclasses are ready for commit to the main tree -[20:19:27] after this commits, all in tree ebuilds must be updated and revbump -[20:19:38] and seems most of kde4 misc apps already ready for this eclasses -[20:19:39] and users must use these versions in order for flawless update -[20:19:45] I still think the default for live outside of kde-base should be changed back to what it was - doesn't directly affect tree ebuilds though. -[20:20:07] cryos|work: ok that i missed, fix that in some commit please, so i dont forget again -[20:20:23] I will do it - I just didn't want to cause it to yo-yo... -[20:20:26] make it +kdeprefix for everything live by default -[20:20:38] cryos|work: i already agreed on it :P i only forget -[20:20:52] Yep - explicitly setting to - will continue to work. -[20:20:56] -*- cryos|work goes to do that... -[20:21:18] anything else to eclasses? -[20:21:21] but there still should be possible to install live kde misc apps with kde 4.1 or 4.2 -[20:21:31] alexxy: it is :} -[20:21:39] you just need to set kdeprefix correctly first -[20:21:41] It is - set -kdeprefix. -[20:21:46] and for that you need to know what are you doing -[20:22:19] because some misc apllets exists only as -9999 ones -[20:22:24] Anyone using live should know what they are doing... -[20:22:38] agreed with cryos on this -[20:22:47] me too =) -[20:23:05] ok i guess ecalsses were polished pretty fine :] -[20:23:10] <-- undetected (n=laika@27.138.45.66.cm.sunflower.com) has quit -[20:23:11] btw i saw kde 4.1.4 tagged in svn -[20:23:17] They are looking good to me. -[20:23:27] alexxy: yeah, that'll keep us busy next week :) -[20:23:29] ok since he mention it SOMEBODY willing to bump 4.1.4 -[20:23:39] do we want it or need it? -[20:23:41] Yes it was and I think tarballs are uploaded. -[20:23:42] and what about misc apps? -[20:23:42] It will be a nice bump to all KDE apps when the new eclass goes in. -[20:23:56] cryos|work: good idea -[20:23:57] :] -[20:24:00] should live misc apps stay in :live and not in stable systems? -[20:24:06] Kill two birds with one stone. -[20:24:07] ok so we do eclass -> misc apps ->4.1.4 -[20:24:37] ok who is going to do actual bump -[20:24:40] All live apps should be in the :live slot shouldn't they? -[20:24:52] my opinion to this: ^^ -[20:25:04] can be in :0 if dev thinks it is needed -[20:25:12] we shouldn't provide live ebuilds for stable systems, it gets maintainance a hell -[20:25:13] but default is live -[20:25:24] It seems like a bad move to me. -[20:25:33] May be snapshots if it is warranted... -[20:25:38] we can make snapshots for some mis apps -[20:25:43] if they realy needed -[20:25:51] *misc -[20:26:05] well we dont give users chance to use live in stable, and if they pull kde-crazy, they have to pick consequences themselves -[20:26:27] agreed with snapshots if it is needed app -[20:26:44] <-- tbeadle_ (n=tbeadle@204.181.64.60) has quit (Read error: 60 (Operation timed out)) -[20:26:46] and what about the opposite? should we provide versioned apps in :live? -[20:26:50] i would suggest only make snapshots for things that should go into official tree -[20:26:51] and some things about kde :4.2 -[20:26:57] it needs -[20:27:03] networkmanager 0.7 -[20:27:19] well i finished nm-0.7 with blessing from rbu :] -[20:27:24] so it also needs policykit -[20:27:59] policykit is suspended for now, i spoke with gnome and they have it too, i would do it with cooperation, so we will have actualy better chance not to screw up :] -[20:28:00] also if we want to bump some stuff like kde printer applet we should have system-config apps unmasked -[20:28:31] alexxy: one problem per while man, if you throw 15 problems we should pick up on what to answer? :D -[20:28:51] let's start with the overlay situation before we discuss versioning ... -[20:28:56] scarabeus: its still one global problem -[20:29:02] deps of kde-4.2 -[20:29:02] --> tbeadle_ (n=tbeadle@204.181.64.60) has joined #gentoo-kde -[20:29:03] ) -[20:29:09] i know :D -[20:29:26] important question about stable tree: -[20:29:35] should we allow usage of +kdeprefix for stable users? -[20:29:49] i vote for no :) -[20:29:53] we had this nice discussion and i think for stable tree this feature could be disabled -[20:30:02] I always voted no... -[20:30:19] I think jmbsvicetto may have more to say here though. -[20:30:26] this fature should be use.masked -[20:30:32] I am not sure this can be decided without others here. -[20:31:00] so if people realy realy want it they should unmask this feature -[20:31:10] yup ;] -[20:31:33] Sounds like a good idea - still a shame more devs are not present if they wanted to discuss this further. -[20:31:47] alexxy: you have meeting about becoming dev tomorow right? -[20:31:53] well, in case we provide this, we could not officially support it -[20:31:53] its will look like a situation with clustered lvm extensions =) they are masked by default -[20:32:00] scarabeus: yes -[20:32:01] cryos|work: well this time i announced it properly -[20:32:20] I didn't say you didn't - you did a great job coordinating the meeting. -[20:32:20] ok i think alexxy can do bump for 4.1.4 as act of new dev :] so he try it too :} -[20:32:42] +1 -[20:32:58] cryos|work: it was supposed to sound like i am sad they didnt come even with proper anouncement... -[20:33:27] that handles in tree moves for 4.2 preparation, which is great :] -[20:33:34] heh =) i'll try -[20:33:49] also one thing for kde-testing overlay, somebody should doublecheck for missing ebuilds, in last week we added 2 completely new ones -[20:33:52] Sounds good, although make sure people are around to help/mentor ;-) -[20:34:07] scarabeus: Real life happens... I am sure jmbsvicetto would have made it if he could. -[20:34:42] yes yes he was looking forward on this meeting, he has few issues, and i think he would like to present his mysql magic ;] -[20:35:07] so who is willing to look up on kde-testing, that is important think that should not be forgoten -[20:35:23] What do you mean look up on? -[20:35:43] also i think we should sanitize deps of kde:4.2 packages -[20:35:47] You mean bump to rcs etc when they are tagged? -[20:35:57] some of deps already provided by kdelibs -[20:35:59] nope, there are missing ebuilds from dirs -[20:36:08] for example some missing games -[20:36:12] and missing applications -[20:36:22] as example bomber and kwrited -[20:36:24] so i think this deps shoul be reoved from kde-base packages since they already depend on kdelibs -[20:36:30] bomber added today -[20:36:37] kwrited yesterday -[20:36:42] tampakrap: i know, and what else is missing, that is the point -[20:36:51] oh -[20:36:52] someone has to doublecheck, cmakelists/directories -[20:37:03] you wanna do it? -[20:37:17] ok but we want two for this :) -[20:37:37] scarabeus: ok i'll oko for missing 4.2 apps -[20:37:38] =) -[20:37:43] ok so you two :] -[20:37:58] -*- alexxy uses kde 4.2 as dayly desktop] -[20:38:01] :] -[20:38:35] policykit is suspended until gnome starts working on it too as i said -[20:38:44] and one last thing regarding 4.2 -[20:38:49] there is printing dialog again -[20:38:52] written in python -[20:39:01] using system-config-bla -[20:39:02] files -[20:39:53] and something else -[20:39:55] these packages are from dberkholz whom allowed us to mess with them, i think we should start playing with this in testing -[20:40:08] and add printing later and not with bump of 4.2 -[20:40:09] -*- dberkholz highlights -[20:40:12] we should bump every kde-misc app to eapi2 in kde-testing -[20:40:15] since it wont be correctly tested -[20:40:40] tampakrap: what for, only if they use kde4-base -[20:40:50] i mentioned to scarabeus previously but not to everyone. it's very important that you bump everything before testing, because current versions are very outdated. -[20:41:03] <-- bicyclerepairman (n=sam@host86-128-227-224.range86-128.btcentralplus.com) has quit (Read error: 110 (Connection timed out)) -[20:41:22] anyone specialy interested in making this work? -[20:41:41] :( -[20:41:55] reavertm could do this but he isn't here :( -[20:42:08] he said he wont have time today -[20:42:15] he is only one properly excused :D -[20:42:41] --> mikb (n=mikb@c122-106-202-225.belrs3.nsw.optusnet.com.au) has joined #gentoo-kde -[20:42:52] ok, leave this one open and if he won't handle it, we'll announce it on g-desktop -[20:43:04] sounds good -[20:43:04] anyone has something with regards for kde4.1/4,2 what i didnt speak of? -[20:43:28] --> looonger (n=quassel@host-89-231-128-7.rawamaz.mm.pl) has joined #gentoo-kde -[20:43:35] yes -[20:43:58] should we provide versioned kde4 apps in live? -[20:44:04] <-- BCMM (n=bcmm@unaffiliated/bcmm) has quit (Remote closed the connection) -[20:44:09] or only live ones? -[20:44:14] in crazy you mean? -[20:44:27] there should be everything we think that is not mature enought -[20:44:32] for example those koffice ebuilds -[20:44:35] i mean globally -[20:44:40] what about kde-plasmoids? -[20:44:52] alexxy: you want them, you review them -[20:44:56] :D -[20:45:01] should we provide install of amarok2 in live and add block for amarok-live? -[20:45:01] --> tgurr (n=tgurr@gentoo/developer/tgurr) has joined #gentoo-kde -[20:45:01] ohhh -[20:45:01] *** Mode #gentoo-kde +o tgurr by ChanServ -[20:45:08] and what about sets -[20:45:13] in off tree? -[20:45:27] in off tree we can use them as we want i think -[20:45:39] for tree we have to prepare metas, which will be done with 4.2 bump -[20:45:58] can we add sets to off tree? -[20:46:16] why not -[20:46:18] or this will be done only after stabilazing portage-2.2? -[20:46:37] btw i'll write the guide for 4.2 and live this time for real :) -[20:46:53] ok writing it up to summary :] -[20:46:54] --> undetected (n=laika@27.138.45.66.cm.sunflower.com) has joined #gentoo-kde -[20:47:16] we can't put any sets in the official tree, but you can provide sets for them in the overlay -[20:47:25] as said yngwin -[20:47:39] for now we have to live with metas and be happy with eapi2 -[20:47:41] guys, why don't you put the direct url for each kde application instead of the generic www.kde.org? i mean, let's take for example marble, it's homepage is set to www.kde.org, but i think it would be 100 times better to put its own homepage ( http://edu.kde.org/marble/ ). so one interested to marble don't go to the kde homepage, but to its own. what do you think? -[20:48:08] --> jbrouault (n=jbrouaul@ARennes-552-1-79-210.w92-135.abo.wanadoo.fr) has joined #gentoo-kde -[20:48:18] xdmx: open bug and give us ebuilds and correct urls, up to then kde.org will be used, we wont search web for them i guess :] -[20:48:41] or we could use edu.kde.org for example -[20:48:47] scarabeus: http://nopaste.com/p/aHK4XLra6 this is a first one (some are to recheck because unmantained, i don't know if it's better to set directly the usertech site for some..) :) -[20:49:32] wow :] is anyone willing to do this? i am pretty sure i wont have itme for it, so i can only mark it as long term :] -[20:49:54] bonsaikitten: you dont wana use your regexp skillz? -[20:50:44] scarabeus: meh. maybe. if noone else can be coerced :) -[20:51:02] i guess it looks you are only one left with nothing assigned -[20:51:13] scarabeus: you too :) -[20:51:31] nope i am with putting eclasses to the tree and fixing all ebuilds -[20:51:37] :) -[20:51:38] i think it is pretty annoymarble -> http://edu.kde.org/marble/ -[20:51:38] kbounce -> http://games.kde.org/game.php?game=kbounce -[20:51:38] kbreakout -> http://games.kde.org/game.php?game=kbreakout -[20:51:38] kdiamond -> http://games.kde.org/game.php?game=kdiamond -[20:51:38] kgoldrunner -> http://games.kde.org/game.php?game=kgoldrunner -[20:51:38] klines -> http://games.kde.org/game.php?game=klines -[20:51:38] kolf -> http://games.kde.org/game.php?game=kolf -[20:51:38] kollision -> http://games.kde.org/game.php?game=kollision -[20:51:38] ksame -> http://games.kde.org/game.php?game=ksame -[20:51:38] kspaceduel -> http://games.kde.org/game.php?game=kspaceduel -[20:51:38] kbattleship -> http://games.kde.org/game.php?game=kbattleship -[20:51:38] kmahjongg -> http://games.kde.org/game.php?game=kmahjongg -[20:51:38] kreversi -> http://games.kde.org/game.php?game=kreversi -[20:51:38] kshisen -> http://games.kde.org/game.php?game=kshisen -[20:51:38] kfourinline -> http://games.kde.org/game.php?game=kfourinline -[20:51:43] crap -[20:51:46] what did i push -[20:52:02] hm -[20:52:04] interesting -[20:52:12] lol -[20:52:28] please pastebin don't spam the channel -[20:52:31] grrr -[20:52:35] lmao -[20:52:51] second time today quassel pasted when i didnt push that damn button :D -[20:53:15] scarabeus: cause you text contains newlines -[20:53:36] alexxy: i didnt write it i marked it from buffer and put into my editor -[20:53:38] not here -[20:53:41] i think this is everything about 4.1/4.2 -[20:53:46] yes /me too -[20:53:53] anyone has something in regards for that -[20:54:06] guess not -[20:54:21] tgurr: your ebuild in genkdesvn for that pdf in scribus is broken, take look on fixed one in kde-crazy -[20:54:35] ok we get to qt4 yngwin, you have something interesting there? -[20:54:42] yes -[20:54:50] i have several recruits now -[20:55:00] so it's starting to look good :) -[20:55:21] :) -[20:55:22] hwoarang is doing good work on qt4-build.eclass -[20:55:23] <-- Psychey (n=me@1x-193-157-193-9.uio.no) has quit (Success) -[20:55:25] scarabeus: not my biggest problem atm ;) kernel is also broken on 2 machines here ... -[20:55:28] ah hold on -[20:55:37] yngwin and everybody -[20:55:50] qt4-build class needs to be ported on EAPI2 standards -[20:55:55] yngwin: great you should sent the other aprentices here too so we can meet them :] -[20:56:03] this means that qt-4.4.9999 live ebuilds -[20:56:06] need to change too -[20:56:07] yes, i think sping came by the other day -[20:56:10] hwoarang: i guess on that you should use reavertm, he has great insight :] -[20:56:27] he's one of the qt-creator devs -[20:56:44] ok scarabeus. will talk to him -[20:56:48] so, we have been squashing qt4 bugs -[20:56:56] but qt ebuilds should move to qt overlay when it is ready -[20:57:13] i dont feel comfortable to play on kde-crazy :D -[20:57:18] i agree with this -[20:57:29] yes, we should have the qt overlay up and running in a few days -[20:57:44] hwoarang: we dont bite ;D -[20:57:47] then we'll push stuff to kde-testing/crazy when they're ready -[20:57:56] scarabeus: we do :p -[20:58:02] :D -[20:58:13] yngwin: dont forget to upload kde-teams keys if you want us to help you ;] -[20:58:35] yes, i'll look into that once it's really up -[20:58:47] :] -[20:59:02] another thing, i want to stabilize qt 4.4.2 -[20:59:10] first split ebuilds version to go stable -[20:59:15] i volte yes :] -[20:59:24] <-- hvengel (n=hvengel@astound-66-234-194-11.ca.astound.net) has quit (Read error: 145 (Connection timed out)) -[20:59:38] note: new kde4 eclasses specialy depends on splited qt ebuilds, i dropped the old mono qt stuff -[20:59:55] i wrote a migration guide, because i've seen many problems, but according to jkt and zmedico it should go smooth now -[20:59:55] you need some help there from us or bug is filled and all is going fine? -[21:00:42] well, i need a stable system with qt-4.3 and PyQt4, then test if keywording 4.4 ebuilds and masking 4.3 really gives a smooth upgrade path -[21:01:18] hm, read as: ANYONE ON STABLE HERE? ;] -[21:01:26] whats that? :P -[21:01:26] -*- tampakrap -[21:01:36] so i was planning to test that in a chroot tonight otherwise -[21:02:01] -*- alexxy uses ~arch ( read as ~amd64 ~x86 ~mips and ~arm) -[21:02:03] ok you two can talk it out, it is up to you :] -[21:02:07] tampakrap: you have qt-4.3 on there? -[21:02:24] no but i can downgrade 4.4 isn't even needed in this one -[21:02:42] ok, we'll talk about that after the meeting then -[21:03:03] ook -[21:03:41] another item is qt-embedded has not been receiving any love -[21:03:58] but i probably should speak to embedded people about that -[21:04:32] there i guess we are not much able to help :] only if as embedded can be count some cluster ;] -[21:05:36] he he =) -[21:06:11] yngwin: btw i looked on hwoarangs eom today and give him notes, i guess when he incorporate the updates he will pass review from recruiters so you will get new coleague :] -[21:06:23] and i need to get a pythonista to mentor me a bit wrt ebuilds using python (mostly PyQt4 packages) -[21:06:34] qt-embedded = Qt Extended now? -[21:06:36] scarabeus: great -[21:06:44] or what is that supposed to be? -[21:07:03] seems qt extended -[21:07:06] yngwin: when you are on pyqt take creepy look on pykde on the route i think :] -[21:07:14] yngwin: I can try to help with python things -[21:07:15] since qt embedded was renamed to it -[21:07:20] Sput: yes, qt-extended / qtopia -[21:07:27] k -[21:07:46] -*- Sput would like to have a Gentoo way of installing the Qtopia SDK -[21:07:55] scarabeus: i'll do what i can -[21:08:00] :] -[21:08:03] bonsaikitten: great -[21:09:12] --> hvengel (n=hvengel@astound-66-234-194-11.ca.astound.net) has joined #gentoo-kde -[21:09:19] now i would like to know what is state of that mysql issue, but we are out since only guy working on it is jmbsvicetto so this note will be added to the summary additionaly, i would really like to have amarok2 on amd64 with kde4.2 bump -[21:09:45] <-- St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has quit (Read error: 54 (Connection reset by peer)) -[21:09:50] --> St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has joined #gentoo-kde -[21:09:53] -*- cryos|work would love to see amarok 2, but thinks the move to MySQL as the *only* backend wasn't good... -[21:10:07] indeed -[21:10:17] --> neyz (n=neyz@ram94-6-82-242-23-69.fbx.proxad.net) has joined #gentoo-kde -[21:10:22] they are going to import others too -[21:10:25] i wonder why they couldn't use qt-sql interface, which can use various DBs -[21:10:43] because *censored* *censored* *censored* -[21:11:56] I am going to need to pay less attention to this meeting and more to work now... -[21:11:57] no they are not going to import others -[21:12:01] it'll stay mysql only -[21:12:07] ok, so we need to wait for feedback from jmbsvicetto on this -[21:12:08] I heard they weren't either, but don't know. -[21:12:41] I really question the intelligence of using such a heavy weight dep for a music player as the only option though. -[21:12:58] -*- yngwin just uses mpd -[21:12:58] I am not about to go trolling, but think it is a step backwards. -[21:13:15] well most of packagers think that it is step back -[21:13:25] what for fully fledged mysql on desktop machine -[21:13:29] In Avogadro we very carefully consider even optional deps, required deps even more so. -[21:13:43] from my own experience I claim that being unable to use sqlite is a sign of bad design -[21:13:45] I don't want to have to install things like MySQL on my EeePC... -[21:13:52] they're censoring the chatroms! protest! -[21:13:53] mysql only pseudoproffesional db :( -[21:13:55] it can handle millions of items, why can't it handle 6k songs? -[21:14:05] scarabeus: be quiet please :D -[21:14:09] sqlite can's work remotely though -[21:14:12] *can't -[21:14:13] 6k should be enough for anybody -[21:14:22] amarok upstream is not willing to maintain more than one backend -[21:14:27] Sput: uhm ... yeah ... let me just stab you a bit -[21:14:30] bonsaikitten: well i am doing some things as db specialist, so i know what is good db, and mysql never was such thing :D -[21:14:32] -*- yngwin has 21k -[21:14:34] Why do I care if it can work remotely? -[21:14:43] and yes, they didn't properly design their db access :p -[21:14:52] thanks to embeded, they need to run on local machine which is also great -[21:14:53] :D -[21:14:53] scarabeus: I've worked with sqlite and currently have >50 MySQL servers to babysit -[21:14:59] cryos|work: many people share their db over several instances -[21:15:07] bonsaikitten: hope you enjoy it :] -[21:15:10] cryos|work: I have a central file server, and with amarok1 I used to have a central database -[21:15:11] Yeah, but everyone? -[21:15:18] I like Amarok 2.0. -[21:15:19] I certainly don't. -[21:15:23] scarabeus: I could tell you things, but then I'd have to shoot me -[21:15:30] :D -[21:15:31] <-- Aw0L (n=awol@mx1.spfldsparc.org) has quit (Read error: 104 (Connection reset by peer)) -[21:15:31] <-- St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has quit (Operation timed out) -[21:15:35] I loved amarok, love the look of amarok 2. -[21:15:37] is this a good time to mention that I'd like koffice snapshots in kde-testing? -[21:15:41] We are drifting off topic though. -[21:15:44] hey i found one non flame topic -[21:15:49] MONO bindings in kde4 -[21:15:50] ok, before this becomes a flamefest, anything else on meeting? -[21:15:54] do we ship them or not? -[21:15:59] MONO is inherntly bad. -[21:16:01] no -[21:16:06] i volte for no -[21:16:09] !herd mono -[21:16:14] but if they will do them... -[21:16:18] there is no mono herd? -[21:16:25] lol -[21:16:26] I would go with no unless someone really wants to do it themselves. -[21:16:27] do we have any apps that use them? -[21:16:44] !herd dotnet -[21:16:45] scarabeus: (dotnet) compnerd, jurek, loki_val -[21:16:58] ok i will ask them if they want to create them :] -[21:17:04] haha -[21:17:04] otherwise they wont be shipped then -[21:17:16] scarabeus: ? -[21:17:52] loki_val: if you want kde-mono bindings -[21:17:53] loki_val: we have mono bindings in kde4, and nobody here uses mono, are you interested in it? -[21:18:42] I use only kde3 -[21:18:58] so it's dead :) -[21:19:05] Sometime when kde4 works for me, perhaps. -[21:19:05] so its dead :] -[21:19:16] loki_val: ok i will write suspended for now :] -[21:19:28] --> Vash63 (n=quassel@ip68-2-28-213.ph.ph.cox.net) has joined #gentoo-kde -[21:19:31] did we discuss the overlay situation already? -[21:19:32] bonsaikitten: ? -[21:19:39] afaik no -[21:19:45] might be a good time now :) -[21:19:45] nope i leave it on last thing -[21:19:50] because ti will be flame again -[21:19:54] i have one last thing -[21:19:59] no but we can't without jmbsvicetto and reavertm -[21:20:15] you know how we handle linguas in kde ebuilds -[21:20:24] how about move this magic to cmake-utils eclass -[21:20:29] so every cmake ebuild can use it -[21:20:40] agree -[21:20:51] How come kde-base/kde-l10n isnt in @kdebase? -[21:20:54] actually, i think there should be a generic linguas eclass -[21:20:59] ni1s: it is in @kde -[21:21:10] yngwin: well i write most abstract cmake stuff -[21:21:22] if some autotools mage wants to step in and write the same for autotools -[21:21:24] ok, that could be a start -[21:21:39] scarabeus, yeah, but it feels very baseish -[21:21:59] ni1s: it is not base requirement for system, and some people dont want it at all -[21:22:35] <-- gyama (n=gyama@89.143.147.33) has left #gentoo-kde -[21:22:41] scarabeus, ah ok -[21:23:00] ok i suspend the move to cmake utils eclass for now -[21:23:05] lets see how time evolve then :] -[21:23:14] i will try to talk someone to try it on autotools :] -[21:23:33] ok now we get to highly awaited topic -[21:23:52] too many overlays someone says :] merge kde-testing to kde-crazy or keep them splitted -[21:23:53] overlays? -[21:24:00] i personaly want them splitted like they are -[21:24:04] merge -[21:24:08] --> ivanich (n=ivanich@ivanich.tenet.odessa.ua) has joined #gentoo-kde -[21:24:10] cryos|work said we should define a policy -[21:24:11] split -[21:24:20] there's too many changes that don't get applied to the other -[21:24:27] but it is hard to maintain and sync changes between reavertm and alexxy :) -[21:24:43] that is good point -[21:24:45] yes -[21:24:53] but what about users that want only test something that is almost ready -[21:24:59] split feels better assuming the eclasses are always in sync (or different per overlay) -[21:25:00] we should use package masks? -[21:25:00] so we should efine policy for commiting tio overlays -[21:25:18] yes it is easier to maintain this way -[21:25:23] since no one merge changes from one overlay to other if he commit something -[21:25:32] personally my main duties was the syncing -[21:25:37] *were -[21:25:42] we can have merging supervisor ;] -[21:25:47] tampakrap was great one :D -[21:25:55] but didn't want to :) -[21:25:57] merge -[21:26:18] depends how much syncing is needed -[21:26:26] to my mind its better to merge overlays again -[21:26:29] quite much -[21:26:41] well i like the split only from users view -[21:26:43] then i can imagine having 1 overlay would be better -[21:26:43] and keep live stuff masked + unkeyworded -[21:26:53] just keep live unkeyworded -[21:27:06] only hardmask stuff that is known not to work -[21:27:08] if we are able to make visible only mature stuff for users which first checkout -[21:27:10] i am for merge too -[21:27:21] two overlays is realyhard to maintain -[21:27:25] profile.mask is the solution -[21:27:32] no -[21:27:44] -*- cryos|work was getting coffee and doing work... -[21:27:59] kde-testing stuff can go ~arch, and crazy stuff unkeyworded -[21:28:00] scarabeus: we can mask all live stuff -[21:28:07] live stuff is already masked -[21:28:08] right -[21:28:14] ok that sounds reasonable -[21:28:16] no it isn't -[21:28:29] it isn't hardmasked i mean -[21:28:31] If it is unkeyworded it is enough. -[21:28:32] about masking -[21:28:39] oh -[21:28:42] my bad -[21:28:47] You have to specially keyword and checkout an overlay. -[21:28:50] its better to have live stuff p.masked also -[21:28:58] If it makes you happy. -[21:29:02] :D -[21:29:04] alexxy: why? unkeywording is enough -[21:29:14] unkeywording is indeed enought -[21:29:21] no it isn't -[21:29:21] i have to drink my cure, brb -[21:29:28] in case of phonon it isn't -[21:29:34] yngwin: its too easy for user to unmask live stuff by error -[21:29:36] It is already in an overlay, and has no keywords. You have to specifically keyword **/ -[21:29:46] <-- Vash63 (n=quassel@ip68-2-28-213.ph.ph.cox.net) has quit (Read error: 54 (Connection reset by peer)) -[21:29:46] It isn't too easy. -[21:29:47] people symlink everything and live phonon gets installed in snapshots' machines -[21:29:52] alexxy: they need to specifically add ** keyowrds -[21:29:57] If it makes you happy and you stop bickering you can mask it too. -[21:29:59] <-- hvengel (n=hvengel@astound-66-234-194-11.ca.astound.net) has quit (Connection timed out) -[21:30:07] --> hvengel (n=hvengel@astound-66-234-194-11.ca.astound.net) has joined #gentoo-kde -[21:30:10] I think it is overkill though. -[21:30:13] symlinking unmask is easy too -[21:30:19] yeah but they symlink the whole p.keywords folder even if i splitted it for every version -[21:30:29] that is users fault -[21:30:34] the solution is a clear guide then -[21:30:35] --> St_MPA3b (n=quassel@gregory51.dialup.corbina.ru) has joined #gentoo-kde -[21:30:39] yes -[21:30:41] not two overlays -[21:30:46] You cannot prevent stupid users from doing stupid things. -[21:30:57] Just provide a clear path and reasonable policies. -[21:31:02] indeed -[21:31:05] --> Vash63 (n=quassel@ip68-2-28-213.ph.ph.cox.net) has joined #gentoo-kde -[21:31:14] It is too easy for a user to type rm -rf / -[21:31:21] lol -[21:31:21] :D -[21:31:24] lol -[21:31:30] cryos|work: this wil not work =) -[21:31:34] cryos|work: so what is your merge/split statement :D -[21:31:42] i mean rm -rf / will not work -[21:31:48] =) -[21:31:53] [ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo "You live" -[21:31:53] I would merge, but don't mind too much. -[21:32:01] brb -[21:32:09] rm -rf /* then? -[21:32:11] ok so far the voltes are: -[21:32:18] yngwin: merge -[21:32:18] kitten: merge -[21:32:18] scarab: merge -[21:32:18] tampakrap: merge -[21:32:18] reavertm: merge -[21:32:18] alexxy: merge -[21:32:18] cryos: dont mind merge -[21:32:22] Still to easy... -[21:32:31] so i guess we will again have one overlay :D -[21:32:33] also sput merge -[21:32:34] I would go with, but won't cry if you don't ;-) -[21:32:46] Hi -[21:32:48] :D -[21:32:51] Hey - he's here! -[21:32:53] HELLOOOOO -[21:32:56] sorry guys, but I've been tied up at work :\ -[21:32:57] hi! -[21:32:57] it's alive!!!!! -[21:33:08] its moving, RUN :D -[21:33:11] ok meeting is over we have one overlay end of the story bye -[21:33:13] I'm very sorry, but I had expected to be free for the meeting -[21:33:15] I need to mostly disappear and get some work done... -[21:33:30] Sorry I missed you jmbsvicetto. -[21:33:43] -*- cryos|work out - will read ML summary if there is one... -[21:33:43] I'll have to grab dinner in around 15 minutes. Is there anything I can clear up / explain / detail ? -[21:33:50] cryos|work: Hi. I'm sorry too -[21:34:09] jmbsvicetto: Life happens. We tried not to steam roll stuff ;-) -[21:34:27] I do need to go though. -[21:34:30] jmbsvicetto: we were volting about merge/split overlays and all volted for merge or dont mind merge :D -[21:34:54] About the tasks I was expected to do from the last meeting: 1. mysql - I'm stuck at the patch in the bug - I wasn't able to do more yet. 2. contact people to check whether they want to be in the kde team - I'm sorry, but I didn't got this done. -[21:35:01] cryos|work: hehe -[21:35:03] cryos|work: later -[21:35:11] :D -[21:35:20] scarabeus: ok, so my vote would have lost -[21:35:27] --> tinytony_ (n=tinytony@77.53.34.198) has joined #gentoo-kde -[21:35:37] scarabeus: what was the 3rd task I had to do? -[21:35:37] jmbsvicetto: ok for the mails i guess you will do it in future so no biggie in that -[21:35:54] jmbsvicetto: the third one i did instead of you -[21:35:55] :D -[21:36:09] Yeah, I'll try to get it done this week. I can also tell you some of them are under undertakers notice -[21:36:16] scarabeus: what was it? -[21:36:20] scarabeus: eclasses? -[21:36:23] eapi2only eclasses -[21:36:25] which i handled -[21:36:37] scarabeus: Thanks and sorry for leaving it up to you -[21:36:52] no problem really, i had time so i did it :] -[21:36:58] at least i know the eclass pretty well :] -[21:37:04] hehe -[21:37:15] scarabeus: want to know mysql "intimately"? ;) -[21:37:18] are we ok with moving eclasses to the tree? -[21:37:28] back -[21:37:44] looks like i will do it on saturday i guess -[21:37:46] scarabeus: I noticed reavertm seemed to find a bug in the eclasses related to the blocks -[21:37:48] tampakrap: ^ -[21:38:00] Were you able to sort that out? -[21:38:02] jmbsvicetto: ok one bug, needs to be fixored -[21:38:10] jmbsvicetto: he didnt tell me a thing -[21:38:20] btw I even think that merging the overlays is less confusing for users than the current state, where they always need to ask around which overlay contains what -[21:38:21] I think he sent a mail to the desktop alias -[21:38:32] there should be only one official gentoo KDE overlay one can point people -[21:38:35] Sput: I also didn't do the blog entry :\ -[21:38:40] oh i see -[21:38:50] jmbsvicetto: which blog entry? -[21:38:57] btw alexxy has review tomorow in case you dont know -[21:39:03] The one I was going to explain it (the overlays) -[21:39:08] scarabeus: I didn't -[21:39:10] alexxy: Good luck :) -[21:39:18] jmbsvicetto: thanks -[21:39:19] =) -[21:39:35] and i guess we should pronounce the meeting over uness jmbsvicetto has something new he wants to adres -[21:39:42] alexxy: I'm going to be busy tonight, but if you want / need to ask something, poke me until I reply ;) -[21:39:42] oh missing letters, shame on me -[21:39:55] scarabeus: No, nothing to add -[21:40:14] unit DISMISS! \ No newline at end of file diff --git a/meeting-logs/kde-herd-meeting-log-20090305.txt b/meeting-logs/kde-herd-meeting-log-20090305.txt deleted file mode 100644 index a52c535..0000000 --- a/meeting-logs/kde-herd-meeting-log-20090305.txt +++ /dev/null @@ -1,769 +0,0 @@ -[21:08:49] LETS BEGIN :D -[21:09:07] so first nice question is -[21:09:10] WHO IS AROUND? -[21:09:16] o/ -[21:09:17] !herd kde -[21:09:21] yngwin: (kde) alexxy, caleb, carlo, cryos, deathwing00, genstef, jmbsvicetto, keytoaster, mattepiu, patrick, scarabeus, tampakrap, tgurr -[21:09:21] !herd qt -[21:09:22] (qt) caleb, carlo, hwoarang, yngwin -[21:09:24] -*- wired is here -[21:09:29] -*- yngwin is present -[21:09:37] -*- alexxy here -[21:09:50] xine-lib-9999 does not compile yngwin because of missing Makefile.in -[21:09:50] *** Mode #gentoo-kde +v reavertm by scarabeus -[21:10:22] where are the other slackers :P -[21:10:37] slacking -[21:10:38] :p -[21:10:54] bumbl: see forum thread. if there is a patch/solution, i will apply it (tonight or tomorrow) -[21:10:58] -*- cryos|work is kinda here, ill, stressed... -[21:11:19] cryos|work: hi :] -[21:11:59] <-- KotBehemot (n=dracul66@unaffiliated/kotbehemot) has quit (Remote closed the connection) -[21:12:03] ping -[21:12:20] Sorry for being late -[21:12:22] ok we are closing onto desired goal >50% around :] -[21:12:22] I think you need to ping an address, or is that a broadcast packet? -[21:12:24] here -[21:12:34] <-- genady12__ (n=genady12@80.178.17.222.adsl.012.net.il) has quit (Read error: 110 (Connection timed out)) -[21:12:54] where is our main slacker? bonsaikitten are you here? -[21:12:56] =) -[21:13:09] am I ? -[21:13:16] yes! -[21:13:29] cryos|work: broadcast ping ;) -[21:13:34] ok so i guess we can start, others would have to show up later... -[21:13:37] any objections? -[21:13:54] none -[21:13:57] who are we missing? -[21:13:59] =) -[21:14:02] tampa -[21:14:05] Carlo! ;-> -[21:14:05] tampakrap i guess and reaver -[21:14:14] Philantrop: :P -[21:14:17] Philantrop: you actualy get him on irc at some point? :] -[21:14:17] Hi Wulf -[21:14:30] scarabeus: No, he never was nor will he ever. -[21:14:34] Hi Phil :) -[21:14:34] jmbsvicetto: Hello! :-) -[21:14:39] hehe -[21:14:52] scarabeus: carlo is a "mail" guy -[21:14:52] --> KotBehemot (n=dracul66@unaffiliated/kotbehemot) has joined #gentoo-kde -[21:15:05] yea i got that :] -[21:15:14] jmbsvicetto: ... if he communicates at all. -[21:15:37] Philantrop: well, a reply to a 4 or 6 month mail is still a reply :P -[21:15:40] http://www.pastebin.cz:80/15872 -[21:15:44] jmbsvicetto: :-) True. -[21:15:48] i'm here -[21:15:50] here is a list what we will chat about today -[21:15:53] hello tampy -[21:15:59] tampy! -[21:16:03] lol -[21:16:32] -*- cryos|work only claims 42% presence --- man flu... -[21:16:44] ok so we can start with kde3.5.10 state -[21:16:50] cryos|work: get well soon -[21:16:51] cause on that we all probably will just listen :D -[21:16:52] i'd like to say a few things about KDE 3 first -[21:17:17] may I? -[21:17:20] Hi Theo -[21:17:21] yes proceed -[21:17:22] say -[21:17:32] ok -[21:17:39] cryos|work: yeah, my cold has been bugging me for the past week :\ -[21:17:50] in kde-testing i have a kde-3.5 branch with new eclasses -[21:18:13] those eclasses prefix misc kde apps in /usr/kde/3.5 and permit eapi2 ebuilds -[21:18:38] i have started writing all kde-base ebuilds in eapi 2 i have about 60 here -[21:19:02] jmbsvicetto told me today to try to get rid of arts and use a different backend -[21:19:18] i'm not sure if this can be done and to be honest i don't know if it worths it -[21:19:24] i'd like your opinion -[21:19:24] -*- jmbsvicetto looks innocently into the sky -[21:19:37] and of course some testing of you people -[21:19:53] tampakrap: if it's too much work, forget arts -[21:19:54] kill arts. -[21:20:05] in my opinion kde 3.5.10 works as is, and i wouldnt spend too much time on 'improving' the ebuilds -[21:20:07] especially the kde4 guys, as the pending big issue is the proper use of kde3 apps inside kde4 environment -[21:20:12] tampakrap: I was just interested to find out if we could kill it -[21:20:21] jmbsvicetto: You could. -[21:20:22] --> looonger (n=looonger@host-89-231-128-7.rawamaz.mm.pl) has joined #gentoo-kde -[21:20:43] tampakrap: have you done any changes to the eclasses since we lasted talked about them? -[21:20:46] i agree with killing -[21:20:53] Philantrop: we should, but meh :\ -[21:20:57] give peas a chance -[21:21:17] wired: yes but not pushed -[21:21:17] jmbsvicetto: I wouldn't do it anymore. It's not worth the effort anymore. -[21:21:24] yeah, I agree -[21:21:50] it was allways broken from my POV and it is not worth the problems with it i guess -[21:21:57] tampakrap: how can we help you getting it done? -[21:22:02] tampakrap: ok, just asking because last time i used them [by accident] kdebluetooth failed to install -[21:22:23] wired: most of the bugs i tried to fix -[21:22:24] kdebluetooth is problematic anyway -[21:22:30] should probab;ly be hardmasked -[21:22:30] jmbsvicetto: i'll ping you guys when i need help don't worry -[21:22:41] tampakrap: If you think the eclasses are "almost done", you should probably merge them to the master branch -[21:22:54] yngwin: it works fine for me (with bluez < 4) -[21:22:57] yes i'm about to do it -[21:23:03] ok :) -[21:23:14] ok -[21:23:31] --> scratch[x] (n=scratch@83.239.148.148) has joined #gentoo-kde -[21:23:46] but i agree with Philantrop it is not worth the effort, everyone is moving to kde4.2, just a quick cleanup of kde3 is enough -[21:23:53] yep -[21:23:59] on a related note, i want to mask ~qt-3.3.8 for removal, and leave only ~qt-3.3.8b in tree -[21:24:05] and i am more intrested in kde4 too -[21:24:30] kde 3.5.x is old =) -[21:24:31] yngwin: feel free -[21:24:31] <-- er0x (n=kvirc@client-87-247-122-156.inturbo.lt) has quit ("KVIrc Insomnia 4.0.0, revision: , sources date: 20090224, built on: 2009/03/04 18:54:25 UTC http://www.kvirc.net/") -[21:24:56] alexxy: maybe old, but it works ;) -[21:25:02] :] -[21:25:04] yngwin: Is anything holding qt-3.3.8 around? -[21:25:13] yngwin: looking at keywords I see they're the same -[21:25:15] i thought kdebluetooth -[21:25:30] ok about kdebluetooth -[21:25:31] ah, ok -[21:25:38] not 100% sure, will look tomorrow -[21:25:43] there might be some users who still want to use kde 3.5 until ~ kde 4.4 (which is when all the third party developers will have ported their apps (hopefully)) -[21:25:51] NOTE: (guys i found out that my loging is not working with this weechat version so i will write summary and somebody else will have to put the log on devspace) -[21:26:08] bumbl: hmm, besides k3b, which major apps are still missing? -[21:26:09] -*- wired keeps logs -[21:26:11] bumbl: it's no reason to wait for them to release, we can provide working snapshots -[21:26:17] jmbsvicetto: nothing! -[21:26:20] scarabeus: I have logs, don't worry -[21:26:23] ouk -[21:26:40] jmbsvicetto: k3b, konversation, that i know -[21:26:46] kile -[21:26:48] and others -[21:26:51] jmbsvicetto: kaffeine4 is still very basic (kaffeinegl seems dead) -[21:26:53] kde3 is still needed -[21:26:54] quanta!!!!!!!!!! -[21:26:56] kile works from :live -[21:27:07] <_genuser_> qt-core is almost done. -[21:27:08] k3b dont at this moment -[21:27:09] live is not good for normal users :] -[21:27:13] yngwin: I liked quanta :) -[21:27:13] ok about kdebluetooth i'll have a look at it and try to find the very best solution -[21:27:16] <_genuser_> then more hours for kdelibs. -[21:27:21] Konversation's KDE 4 port is shaping up nicely, so that will be gone from the list soon. -[21:27:27] jmbsvicetto: yeah quanta is badly missing -[21:27:35] we can make snapshots for kile -[21:27:36] =) -[21:27:43] jmbsvicetto: i was hoping for quanta with vimpart -[21:27:44] blah -[21:27:47] <_genuser_> I'm so excited that in 2 days I can finally run kde4.2. :) -[21:28:06] <_genuser_> that was sarcastic. -[21:28:09] shouldn't kdevelop4 replace quanta? -[21:28:09] <_genuser_> hopefully it runs soon. -[21:28:10] jmbsvicetto: Kile -[21:28:14] we can make snapshots for many packages and maybe we can start doing it -[21:28:15] tampakrap: do you need our help somewhere on kde3? -[21:28:30] using TexClipse and this just sucks :D -[21:28:36] scarabeus: not now maybe in a few days -[21:28:52] oh and obviously we still a "working" amarok ;) -[21:29:00] genady12_: ah that's why my sarcasm detector went wild -[21:29:16] scarabeus: next? getting 3.5.10 stabled? -[21:29:21] people please we have a meeting here... -[21:29:26] right -[21:29:29] hehe lets wait what tampakrap shows us -[21:29:43] for now lets fix the prefixing -[21:29:45] :] -[21:29:51] we still have ~2 months :D -[21:30:06] For getting 3.5.10 marked as stable? :\ -[21:30:08] why? there's no need to keep 3.5.10 from going stable -[21:30:12] scarabeus: remember my kepas thing *g* -[21:30:15] I was hoping to do it next month -[21:30:18] as i said the main issue is running kde3 apps inside kde4 env that's where i need help and testing -[21:30:22] THIS month -[21:30:32] yngwin: :) -[21:30:33] how can we do it this month with so many bugs open? -[21:30:36] jmbsvicetto: for 4.2 starting its consideration :D -[21:30:48] <-- ABCD (n=ABCD@wikipedia/ABCD) has quit (Client Quit) -[21:31:03] ok this leads to the virtualbox snapshots i talked about -[21:31:09] tampakrap: can you make a list of the important bugs that need fixing? so we can work on that, and ask users (bugday!) to help -[21:31:14] we should create some generic gentoo instalation with kde3 and kde4 for testing -[21:31:17] yes i can -[21:31:27] --> ABCD (n=ABCD@wikipedia/ABCD) has joined #gentoo-kde -[21:31:28] that would be helpful -[21:31:37] scarabeus: Im on that -[21:31:51] i should separate kde base bugs from the misc ones as a first step -[21:31:52] yngwin / tampakrap: I think the most imporant point to get 3.5.10 marked as stable is getting the eclasses in the tree -[21:31:56] wired: How is that coming? Do you need my help? -[21:32:26] brb -[21:32:31] * tampakrap has changed topic for #gentoo-kde to: "MEETING NOW | Official gentoo-kde project channel | KDE 4 guide: http://tinyurl.com/4n47v4 | Overlays: kde-testing, qting-edge | Want to help us? Ask channel staff for info | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | KDE 4.2.1 is available | Weird issues with nvidia-drivers-180.35? bug 260441 | Qt 4.5.0 committed" -[21:32:34] NoirSoldats: well with 4.2.1 and all it kinda fell behind, but its cool, i figured out how to compact the thing as well so its more a matter of time now -[21:32:49] i think we're done with kde3 -[21:32:57] if nobody has questions on ya -[21:33:08] wired: I'm here if ya need me or my processors. :) -[21:33:31] alright, we'll talk about it after the meeting -[21:33:32] oh the last i wanted to tell about kde3 -[21:33:34] --> panard (n=panard@2a01:e35:8a09:e130:2e0:61ff:fe11:7adb) has joined #gentoo-kde -[21:33:34] anyone ever noticed you can compile all of koffice-2 except Krita -[21:33:50] comawhite: i know, not now, later i will talk with you -[21:34:04] okay -[21:34:23] carlo is doing an excellent job with kde3 misc apps he closed many bugs but he is never on irc, has anyone contacted him ever? -[21:34:33] only by email -[21:34:52] i gave up after he didnt answer my emails last year -[21:35:00] ok i'll keep that in mind -[21:35:05] <-- Bluespear (n=speedy@dhcp-83-219-104-51.customers.tvtnet.ch) has quit ("Leave") -[21:35:06] tampakrap: You should use mail to talk to carlo -[21:35:07] tampakrap: only by mail, or best is creating bug with high priority assigned to him -[21:35:11] that is how i contacted :D -[21:35:22] ok -[21:35:49] ok next thingie is: -[21:35:55] we need somebody maintain the amarok -[21:36:10] not me -[21:36:18] not me =) -[21:36:23] hehe -[21:36:24] is anyone from us willing to be official maintainer? -[21:36:25] both kde3 and 4? -[21:36:29] yeah both -[21:36:32] scarabeus: I haven't looked at 5.1.72 yet (mysql), but I'll get back to it this week -[21:36:34] omg -[21:36:37] --> eyal_ (n=eyal@IGLD-80-230-109-116.inter.net.il) has joined #gentoo-kde -[21:36:51] scarabeus: I don't think amarok for kde3 should require much work -[21:36:55] jmbsvicetto: :P -[21:37:00] --> mschiff (n=mschiff@e176096142.adsl.alicedsl.de) has joined #gentoo-kde -[21:37:05] jmbsvicetto: well not much work but minor bugz are poping up -[21:37:06] jmbsvicetto: no it does :) -[21:37:10] so polishing it needs -[21:37:17] :\ -[21:37:25] it is a mess, pretty abandoned -[21:37:42] yes, flameeyes tried to drop it on me -[21:37:44] i guess we could sent mail on -dev -[21:37:48] amarok-1.4 ? -[21:37:54] indeed -[21:38:11] as i offered to help at the time when he had to go to hospital -[21:38:40] hehe -[21:38:54] he assigned all amarok bugs to me -[21:38:55] soo do we have suicider, erm i mean maintainer... -[21:38:59] btw amarok-2.2 released -[21:39:04] tampakrap: yeah i know -[21:39:20] tampakrap: what?! -[21:39:24] 2.0.2 -[21:39:28] he cant write -[21:39:29] :D -[21:39:32] look i'm a big fun of amarok but until the end of the month i'll be pretty busy with some things and i can't take it -[21:39:43] yes i know i am not saying you should -[21:39:45] we could just hardmask it and assign to maintainer-needed ;) -[21:39:58] ok i will sent the mail on the dev you lazy .... -[21:40:00] :D -[21:40:01] i wonder if amarok compiles with qt-4.5 now -[21:40:11] hwoarang: Mine did. -[21:40:19] hmm -[21:40:26] so does here but the upstream bug is still open -[21:40:27] hwoarang: With a little hacking. -[21:40:31] we can add amarok 2.0.2 to overlay -[21:40:36] and reproducable by many users -[21:40:36] to see if it works -[21:40:41] scarabeus: add me silently to the amarok bugs -[21:40:42] +1 to alexxy -[21:41:01] jmbsvicetto: ok adding as note if you are really sure :] -[21:41:09] yup -[21:41:16] scarabeus: I'll take a look at it -[21:41:23] will the kde-herd and sound-herd maintainers remain though? -[21:41:33] yes of course :] -[21:41:41] ok amarok is done i think :] -[21:41:56] i dont think anyone @sound is really interested -[21:42:16] now i have "homepage updates" it means that we have pretty much tons of outdates info on webspace, in doc and in informations -[21:42:23] i don't care for sound-herd after all :) -[21:42:28] so we need somebody that will actualy try to keep that up-to-date -[21:42:39] -*- tampakrap -[21:42:43] tampakrap: careful, i am in sound :p -[21:42:45] next subject :) -[21:42:54] :P -[21:43:08] tampakrap: you will really keep the web updated? are you sure it is lots of pages and lots of stuff :] -[21:43:23] specialy now main page and the guide needs heavy lifting -[21:43:29] so do you have time?... -[21:43:33] i can help -[21:43:36] look as i said until the end of a month i'll be pretty busy with some things, next i'll have too much free time -[21:43:49] i'll take care of the guide though -[21:44:14] ok you two, try to work it out somehow then :] -[21:44:30] bonsaikitten: ping -[21:44:33] now i need you :] -[21:44:36] what! -[21:44:39] wait a minute -[21:44:46] I'm just providing access to tarballs ;) -[21:45:02] bonsaikitten: nope, i need YOU to take look on pykde bugs, and actualy fix them -[21:45:10] yeah -[21:45:11] since you are most relevant for this -[21:45:14] one quick note about the guide, people when you are fixing major stuff please do the guide fixes too immediately or assign it to someone, but it is a must -[21:45:23] scarabeus: I claim incompetence ;) -[21:45:32] been quite busy with work, maybe I find some time during the weekend -[21:46:14] greatie -[21:46:21] bonsaikitten: feel free to even remove it from kdeprefix -[21:46:32] well, first gotta fix slotting -[21:46:37] yup -[21:46:39] then see why it randomly fails -[21:46:46] then learn enough C++ to fix it -[21:46:50] :D -[21:47:24] there is nothing how i could help, combo of python and cpp is overhead for me -[21:47:25] :] -[21:47:29] hehe -[21:47:37] I still have so many other bugs I want to take care of :( -[21:47:53] maybe mask pykde4 then -[21:47:59] it will allways be that way, but this is one of the biggest kde4 stable blockers now -[21:48:54] yngwin: even that might be the final solution if we wont make it work -[21:49:02] althrought it would disable lots of plasmoids -[21:49:10] no Final Solutions here -[21:49:20] now it just fails for too many ppl -[21:49:23] we are pacifists who give every ebuild a chance -[21:49:34] :D -[21:49:36] :) -[21:50:13] -*- bonsaikitten glares at Phil -[21:50:59] any of you have any ideas about the bluez and kbluetooth, somebody who uses it, i might make it work, but frankly i dont use it much so i might missed stuff, it needs testing and maybe even patching -[21:51:03] kbluetooth4 -[21:51:56] so let's ask users :) -[21:52:04] bluez is hardmasked -[21:52:06] just compiled pykde4-9999 successfully -[21:52:07] I have no bluetooth equipment -[21:52:12] so it needs really brave insaners to test -[21:52:25] -*- alexxy dont have bluetoth -[21:52:33] i have bluetooth but i stopped trying with kbluetooth4 some time ago because it broke my nerves -[21:52:36] i can test again -[21:52:45] --> himikof (n=himikof@129.167.249.ozerki.net) has joined #gentoo-kde -[21:52:51] --> Varox (n=Varox@p4FD441A6.dip.t-dialin.net) has joined #gentoo-kde -[21:53:04] wired: ok -[21:53:08] i will leave it up to you -[21:53:18] gnokii + bluez + kdebluetooth4 + /me = /me insane -[21:53:34] ok. i think i saw a patch for solid and bluez4 somewhere -[21:53:39] <-- Ghabit (n=quassel@91.149.157.195) has quit ("No Ping reply in 30 seconds.") -[21:53:41] ok as sidenote and selfegomasturbation, this week i fixed KOFFICE and it works fine -[21:53:53] so we are prepared to add it for the tree :] -[21:53:54] --> Ghabit (n=quassel@91.149.157.195) has joined #gentoo-kde -[21:53:58] i was about to ask it, what was the issue? -[21:54:00] yey -[21:54:16] i spent 6-7 hours on it -[21:54:21] -*- wired writes down todo notes ^_^ -[21:54:29] and developed nice cmake hate :D -[21:54:40] ok well done -[21:54:58] --> bschindler|away (n=quassel@zux221-218-241.adsl.green.ch) has joined #gentoo-kde -[21:55:17] haha -[21:55:25] build systems seem to be very good for hate -[21:55:30] indeed -[21:55:39] but still i like it more than scons and bam -[21:55:42] scarabeus: so you've finally learned to hate cmake? :P -[21:55:53] jmbsvicetto: sorry for my disbelieve -[21:55:53] scarabeus: Are you feeling the love for autotools again? ;) -[21:55:57] yes :D -[21:55:57] --> kostekjo (n=opera@chello084010120054.chello.pl) has joined #gentoo-kde -[21:56:03] cause autotools wont allow such messy code -[21:56:08] <-- Varox (n=Varox@p4FD441A6.dip.t-dialin.net) has quit (Remote closed the connection) -[21:56:08] or i didnt see it anywhere -[21:56:17] hehe -[21:56:28] reavertm: pingping -[21:56:29] scarabeus: take a look @gromacs -[21:56:30] =) -[21:56:30] scarabeus: you should check kde autotools - it's also great ;) -[21:56:39] :D -[21:56:39] to see autotools mess code -[21:56:47] ok ok dont make me ruin my ideals -[21:56:52] hehe -[21:56:59] let's rewrite kde to use maven -[21:57:09] that would be orgasmic -[21:57:14] bonsaikitten: let's use propper autotools :P -[21:57:25] jmbsvicetto: that would have been my second-best suggestion :) -[21:57:46] ok jmbsvicetto do you have some items that we need to squash for 4.2 stabling -[21:57:54] currently we get hit by only minor stuff -[21:58:04] so i am asking if you have something actualy major -[21:58:04] --> non7top (n=non7top@77.66.156.160) has joined #gentoo-kde -[21:58:11] we need to double check webkit, qt-phonon and java deps -[21:58:21] jmbsvicetto: i already did webkit optional -[21:58:23] some arches don't support any or some of these -[21:58:41] mips dont have java -[21:58:50] for that we have virtuoso i guess -[21:58:53] at least untill icedtea6 will hit tree -[21:58:54] isn't the java issue fixed for soprano and such? -[21:58:56] btw that package needs to be splitted -[21:58:58] which reminds me, can we make all deps in kde4-base.eclass optional? -[21:59:03] cause it is 150mb big as one -[21:59:11] yngwin: talk with me later about it -[21:59:15] ok -[21:59:16] i am open for suggestions -[21:59:56] <-- S-man (n=quassel@cc84863-b.zwoll1.ov.home.nl) has quit (Remote closed the connection) -[22:00:09] i'll repeat, isn't the java issue fixed? -[22:00:18] tampakrap: seems yes -[22:00:34] at least i have sane deps tree on mips -[22:00:38] tampakrap / alexxy: Have you talked to ali_bush about that? -[22:00:49] i talked with ali_bush -[22:00:51] He was reporting an issue with gen1 jvms -[22:01:05] he said he'll look into it tomorrow -[22:01:14] --> S-man (n=quassel@cc84863-b.zwoll1.ov.home.nl) has joined #gentoo-kde -[22:01:41] great :] -[22:01:43] virtuoso does need ~15mb (the parts kde actually uses) -[22:02:18] yes but the rest is 10x bigger that is why i said that we should split it -[22:02:27] (apparently) -[22:02:54] (qt-)phonon is not supported/keyworded on alpha, ia64, mips, sparc and x86-fbsd -[22:02:55] yep -[22:03:12] stil the idea of splitting proposed by trueg is rather silly? (virtuoso-data, virtuoso-backends? it's database server :P) -[22:03:17] yngwin: i'll keyword phonon on mips -[22:03:22] ok -[22:03:31] alexxy: please keyword qt-demo as well -[22:03:32] webkit seems to have problems at least in big endian arches -[22:03:39] hwoarang: later -[22:03:44] yes -[22:03:44] only after kde =) -[22:03:52] btw, there is probably no more separate phonon release -[22:04:03] jmbsvicetto: my mips is bigendian -[22:04:27] USE-flags if possible -[22:05:00] alexxy: at least for sparc and I think ppc64 webkit has alignment issues -[22:05:41] -*- alexxy thinks that we should have abi and endianes keywords for packages -[22:05:47] only sparc -[22:05:58] ppc64 does have qt-webkit keyworded -[22:06:29] alpha and ia64 dont -[22:07:33] on the soprano[sesame2] java issue, it seems sesame doesn't like sun-jre-bin -[22:08:15] ok lads -[22:08:16] isn't this fixed? -[22:08:31] i will take care of easying the deps in eclass and you take care about keywording and deps :] -[22:09:22] wired to build? of it doesn't like switching between sun-jdk and sun-jre-bin after it was succesfully built -[22:09:54] --> Zucca (i=zucca@a88-112-55-25.elisa-laajakaista.fi) has joined #gentoo-kde -[22:09:54] reavertm: when i was testing it it would skip sesame2 support if sun-jre-bin was set as system-vm -[22:10:05] build fail -[22:10:14] it need somebody from java to look and investigate -[22:10:22] there's also another issue with sesame -[22:10:34] <-- bschindler (n=quassel@zux221-218-241.adsl.green.ch) has quit (Read error: 110 (Connection timed out)) -[22:10:37] if you run emerge with sudo -[22:10:41] scarabeus: I've heard of cmake not finding java -[22:10:44] it skips sesame support -[22:10:56] i talked to ali_bush about it and he said he'll look into it -[22:10:56] jmbsvicetto: it find it -[22:11:00] but marks as not sufficient -[22:11:04] i did bit investigation -[22:11:13] you can't build it with sun-jre and no wonder - it needs jdk - that's first -[22:11:44] second is - cmake FindJNI doesn't support many jdk's (IBM to mention one) -[22:11:53] sounds reasonable, but no checks are done for it -[22:11:59] (I have even some patch for that module somewhere) -[22:12:08] then give it upstream -[22:13:52] ok now we are getting to the fancy stuff -[22:13:54] <-- kostekjo (n=opera@chello084010120054.chello.pl) has left #gentoo-kde -[22:14:01] reavertm: how is looking the cmake stuff you are working on -[22:14:11] now the eclass in the testing is working right, can we make it more gentooish -[22:14:17] or it is not worth efforts? -[22:14:32] gentooish? -[22:14:34] :D -[22:14:40] scarabeus: could you please expand? i have no idea what you are talking about -[22:14:57] it's done, testing (rebuilding with kde now) -[22:14:58] tampakrap: obeying our variables and so on -[22:15:05] i tested too -[22:15:08] this afternoon -[22:15:10] works fine -[22:15:16] it's about preserving gentoo C(XX)?_FLAGS and such -[22:15:32] --> Zuccace_ (i=zucca@a88-112-55-25.elisa-laajakaista.fi) has joined #gentoo-kde -[22:15:35] goodie -[22:15:43] reavertm: ok so lets say we have this as final agreed? -[22:15:50] no more major updates :] -[22:16:01] scarabeus you tested it with obsolete cmake-utils and I already fund some user of forum (or here) complainging at /usr/local and claimig that he sysnced overlay recently -[22:16:13] he is lying -[22:16:14] g -[22:16:16] it is working -[22:16:17] ups :p -[22:16:23] tested on tons of cmake-utils ebuilds -[22:16:29] i have some stuff in /usr/local too -[22:16:36] wired: then try the stuff recompile -[22:16:48] kk -[22:16:57] its just soprano, i'll do it now -[22:17:17] no, it's cmake issue, not soprano issue -[22:17:22] i mean -[22:17:25] its soprano files -[22:17:26] in there -[22:17:27] :) -[22:17:31] yes it is cmake-eclass isue -[22:17:34] so sync and try plz -[22:17:39] on it -[22:17:40] so we can have it from the first hand -[22:18:09] <-- yngwin (n=yngwin@gentoo/developer/yngwin) has quit (Read error: 104 (Connection reset by peer)) -[22:18:19] meanwhile we removed htmlhandbook useflag so we have to create new generation for the docs :] -[22:18:31] --> yngwin_ (n=yngwin@gentoo/developer/yngwin) has joined #gentoo-kde -[22:18:31] *** Mode #gentoo-kde +o yngwin_ by ChanServ -[22:18:40] it is not biggie but it would be nice to have some reasonable doc system instead of broken htmlhandbook for 4.2.2 -[22:18:53] any ideas on this? -[22:18:57] doc USE flag? -[22:19:19] reavertm: hehehe -[22:19:21] sry, lost network -[22:19:21] i like this -[22:19:27] it was wrong -[22:19:28] and what then - extracyting /doc when set? -[22:19:48] yup but wont be smart to have kde-docs package -[22:19:52] easier and convinient -[22:20:47] -*- NoirSoldats seconds the idea of a kde-docs package. -[22:21:08] <-> yngwin_ is now known as yngwin -[22:21:22] why kde-docs? -[22:21:25] so... gather docs from all kde-base modules? -[22:21:35] yup -[22:21:36] If I only install 3 or 4 apps, why should I have the docs for all of KDE? -[22:21:42] <-- looonger (n=looonger@host-89-231-128-7.rawamaz.mm.pl) has quit (Client Quit) -[22:21:43] --> ayevee (n=quassel@62.140.238.1) has joined #gentoo-kde -[22:21:53] -*- reavertm agrees with jmbsvicetto :P -[22:21:54] ok so useflag you say -[22:21:55] ok -[22:21:57] :( -[22:22:04] my nice idea squashed to the dust :D -[22:22:04] jmbsvicetto: How big would the docs really be though? In total? -[22:22:10] quite much -[22:22:17] I mean, it's easier to maintain it at package level -[22:22:28] <100MB? -[22:23:04] am I the only one for whom automo-9999 fails to build? -[22:23:46] scarabeus: synced, emerge -av1 soprano but the files still installed in /usr/local -[22:23:48] scarabeus: Hmm, I have a suggestion for how to handle the docs, that should solve both ends of the spectrum.. if I may. -[22:23:57] ayevee: not now. we are in the middle of a meeting -[22:24:08] hwoarang: sorry -[22:24:19] <-- ayevee (n=quassel@62.140.238.1) has quit (Client Quit) -[22:24:22] np -[22:24:34] scarabeus: why was htmlhandbook wrong? -[22:24:59] htmlhandbook is installing *unpacked* docs -[22:25:19] ah ok -[22:25:20] sth like difference between .chm and unpacked help contents -[22:25:36] (i have no problem with that but i see the point) -[22:27:06] are we still in point 3 ? :\ -[22:27:27] :D -[22:27:33] we have 3 issues left -[22:27:39] I see we'e jumped ab it -[22:27:39] i pick randomly :D -[22:27:42] a bit* -[22:27:48] <-- Zucca (i=zucca@a88-112-55-25.elisa-laajakaista.fi) has quit (Read error: 110 (Connection timed out)) -[22:27:54] 4, 5 and 6 ? -[22:27:59] ok reavertm we will probably work on this -[22:28:12] those are due to now -[22:28:19] scarabeus: ^^ soprano still installs in /usr/local -[22:28:22] now lets talk about the splitting then -[22:28:27] wired: ok i will owrk on that -[22:28:32] ok :) -[22:28:55] reavertm: do you know how is upstream going with its splitting for 4.3? -[22:29:22] --> mikkoc_ (n=mikko@151.59.215.164) has joined #gentoo-kde -[22:29:57] upstream is going to split modules or to support splited builds? -[22:29:58] <-- scratch[x] (n=scratch@83.239.148.148) has quit ("Ухожу") -[22:30:10] or something else? -[22:30:32] related to binary/lib versioning? well, they don't seem to be eager (see the need - talked with dfaure ) to change .so version to make it possible to install multiple installations aside -[22:30:51] I wonder who came up with the idea (maybe I don't have clear picture) -[22:31:05] jmbsvicetto: you are most relevant for this ideas -[22:31:24] ok -[22:32:19] Our talk at FOSDEM was that they would (could?) probably split all the bins, but there were some resistance to lbis -[22:32:22] libs* -[22:32:45] is that about keeping 4.x and 4.(x+1) aside? -[22:33:13] jkt|: yes and in same prefix -[22:33:49] anyway - providing more restictive .so versions would restict their ABI compatibility - they already increase soversion for newer libs -[22:34:02] scarabeus: that's the next step -[22:34:13] -*- Sput thinks it does not make much sense to split libs that are always needed anyway -[22:34:37] so we would need either dependencies on *every*library* level (and not tied to particular kde version) or just override their choice on our side -[22:34:43] The first step from them was splitting the tarballs. The second step is providing support to have multiple versions around -[22:34:53] Sput: I tend to agree -[22:35:17] reavertm: libtool!!! ;) -[22:35:26] <-- anselmolsm (n=anselmo@200.184.118.130) has quit (Read error: 113 (No route to host)) -[22:35:40] hh -[22:35:45] <-- Zuccace_ (i=zucca@a88-112-55-25.elisa-laajakaista.fi) has quit (Read error: 110 (Connection timed out)) -[22:35:58] I don't know libtool and I'm not eager to learn it (libtool is broken as well, besides :P) -[22:36:36] reavertm: I mean that this issue of lib versions and deps is what libtool does -[22:37:02] setting versions for kde libs is not a problem -[22:38:09] reavertm: I mean run-time deps -[22:38:32] reavertm: Having app A with a rdep on lib X-1.0.1 and not lib X-1.0.2 -[22:38:41] <-- Sho_ (n=EHS1@kde/hein) has quit (Read error: 104 (Connection reset by peer)) -[22:39:28] --> anselmolsm (n=anselmo@200.184.118.130) has joined #gentoo-kde -[22:39:30] So, who's interested in this subject? -[22:39:56] i am not enought l33t for this one -[22:40:00] --> kostekjo (n=opera@chello084010120054.chello.pl) has joined #gentoo-kde -[22:40:32] neither am I -[22:40:37] <-- kostekjo (n=opera@chello084010120054.chello.pl) has left #gentoo-kde -[22:41:09] I don't believe you :P -[22:42:06] --> root (n=root@hor-jdh171.hor.ucl.ac.uk) has joined #gentoo-kde -[22:42:14] ok, I guess we should talk about this later. Let's see if we can get anything in the ml -[22:42:15] <-> root is now known as lfranchi -[22:42:26] Are you guys still awake? ;) -[22:42:36] <-- lfranchi (n=root@hor-jdh171.hor.ucl.ac.uk) has quit (Client Quit) -[22:42:37] yep -[22:42:39] i am trying -[22:42:42] ook -[22:42:43] hehe -[22:42:48] yeah i just woke up at 19:00 utc -[22:42:48] next thing -[22:42:50] importand one -[22:42:51] --> rex_ (n=quassel@host135-243-dynamic.4-87-r.retail.telecomitalia.it) has joined #gentoo-kde -[22:42:54] snapshots -[22:42:57] what should we do -[22:43:04] upstream dont give a f**k -[22:43:07] stop providing them i guess -[22:43:23] scarabeus: I'll try to mail Dirk directly -[22:43:34] I don't feel like it's worth repacking -[22:43:39] Dirk is the packager? -[22:43:40] last time it took him a few months to get back, but I won't lose anything by sending the mail -[22:43:43] Philantrop: ping -[22:43:44] it is getting high priority cause pple liek the feature -[22:43:49] scarabeus: I can script fixed ones -[22:43:56] Dirk Mueller is "release-team" :P -[22:44:04] <-- Civil (n=Civilian@95-24-48-161.broadband.corbina.ru) has quit (Remote closed the connection) -[22:44:05] scarabeus: that way we'd use our own mirroring -[22:44:06] that's why we can't get any feedback :P -[22:44:22] jmbsvicetto: Hm? -[22:44:25] --> leo (n=leo@hor-jdh171.hor.ucl.ac.uk) has joined #gentoo-kde -[22:44:26] reavertm: he's on the packagers and release ml -[22:44:33] <-> leo is now known as lfranchi -[22:44:40] we can repack this tarbolls -[22:44:55] yes, but he's de facto only man reposnible for releases and tarballs -[22:44:56] Philantrop: Have you tried to get someone from KDE about the snapshots names? -[22:45:09] yo Sput -[22:45:11] Philantrop: By you, I mean you, Ingmar or someone else from exherbo -[22:45:22] Sput: i get to complain at you now :) -[22:45:33] jmbsvicetto: Nope, we decided we don't care enough. :) -[22:45:38] hehe -[22:45:42] that's the spirit -[22:45:42] Philantrop: slacker :P -[22:45:44] hehe -[22:45:49] that is the point we are getting now :D -[22:46:10] actually we have similar approach I guess :) -[22:46:12] jmbsvicetto: "[05. 03. 2009 21:29] slacker! :p" <-- to me. :-> -[22:46:24] lol -[22:46:25] hehe -[22:47:00] I'll provide some feedback to the ml when / if I get something -[22:47:03] <-- mikkoc (n=mikko@151.59.212.173) has quit (Read error: 110 (Connection timed out)) -[22:47:04] <-- pipipde (n=pip@e179244051.adsl.alicedsl.de) has quit (Read error: 110 (Connection timed out)) -[22:47:08] we still need tarbolls for snapshots -[22:47:12] what's the backup plan then? -[22:47:15] ok lets state we sent hte mail -[22:47:22] and bonsaikitten will repack for time being -[22:47:26] I'm going to send another mail today -[22:47:34] ok you sent the mail -[22:47:42] jmbsvicetto: maybe CC to many KDE people and mls -[22:47:59] tampakrap: I'm going to address the packagers, the release team and Dirk directly -[22:48:01] so i'm just getting started with kde-svn ebuilds on gentoo, and automoc failed to install (failed to even begin checking out from svn). can anyone in here help me? -[22:48:09] --> pipipde (n=pip@e179247082.adsl.alicedsl.de) has joined #gentoo-kde -[22:48:25] lfranchi: later1 we have meeting there -[22:48:31] oh, sorry -[22:48:36] -*- lfranchi hides -[22:48:59] lfranchi: I guess it will be fixed soon, but will, many people use live kde (didn't have time to look up the issue) -[22:49:12] bonsaikitten: so you can rly pack it with not big effort? -[22:49:42] scarabeus: we can repack them as tar.lzma -[22:49:43] =) -[22:49:47] sweeet -[22:49:50] via scripts -[22:49:54] -*- jmbsvicetto kills alexxy -[22:49:58] tar.bz2 :P -[22:50:08] jmbsvicetto: .lzma better =) -[22:50:12] well since they really want their svn in the filename, maybe we can convince them to use a 4.x.SVNREV.tar.bz2 scheme? -[22:50:26] wired: well the svnrev is not deterministic -[22:50:31] jmbsvicetto: if you mailed Dirk, you would be mentining placing .svnrevision file or sth in tarball? -[22:50:31] you have to go and check for that revnumber -[22:50:40] normaly you just add +1 -[22:50:56] as I guess it's at least the way we agreed with thiago -[22:50:56] i see -[22:51:08] reavertm: I can suggest that as an alternative -[22:51:15] well i don't see them changing their minds any time soon, alexxy's log was pretty clear -[22:51:38] jmbsvicetto: I mean, let him know we already discussed it with kde folks :P -[22:52:09] reavertm: I will also ask for different options if they don't want weekly snapshots to be used by packagers -[22:52:21] wired: well, you may read jmbsvicetto log as well (later that day) -[22:52:57] if they don't want us to use - I think we should not use :P we just need to follow trunk changes then :P -[22:53:31] It's sufficient to prepare next stable (4.3) release -[22:53:34] --> Linux (n=marcus@92-234-252-159.cable.ubr06.blac.blueyonder.co.uk) has joined #gentoo-kde -[22:53:41] Hey everyone. -[22:53:49] besides - people should use portage version :P -[22:53:58] hehe -[22:53:59] Is KDE 4.2.1 available yet? I synced yesterday. -[22:54:09] Linux: Yes. -[22:54:11] yes, sync again -[22:54:16] so not making snapshots available we probably have greater 4.2 userbase to test and possibly stabilize later -[22:54:19] OK. :) -[22:54:53] reavertm: the snapshots are useful, imo -[22:55:10] as unstable snaphosts are not really *releases* but just svn dump - they are usually as broken as live -[22:55:16] i agree with reavertm, live is enough, we already maintain too many kde releases -[22:55:22] -*- alexxy starts repacking kde 4.2.65 -[22:55:29] :D -[22:55:34] alexxy: talk with kitten -[22:55:42] ok, if no one is willing to work on them for now, let them rest -[22:55:49] ook -[22:55:50] agreed -[22:55:54] We have enough things to take are already -[22:56:18] scarabeus: bugs? bugz? BUGZ??? ;) -[22:56:19] last thing -[22:56:24] BUGZZZZZZZZZZZZZZZZZZZZZZZ -[22:56:30] :) -[22:56:30] we have tons of them -[22:56:31] zzzzzzzzzz -[22:56:31] many dupes -[22:56:34] many needs fix -[22:56:37] many are trivial -[22:56:40] yngwin: :) -[22:56:44] and there is sh*tload of them -[22:57:01] nice, i was eating -[22:57:14] don't read then ;) -[22:57:15] good now you will starve as me :D -[22:57:22] hahahahahah -[22:57:23] -*- Sput looks into automoc now -[22:57:37] except somebody fixed that already -[22:57:43] Sput it may be as well cmake-utils related -[22:58:01] scarabeus: tell us the last issue and go to watch some pr0n -[22:58:06] :D -[22:58:12] the issue is we need to work on bugz -[22:58:24] tampakrap: you didn't watch pr0n during the meeting like the rest of us? -[22:58:25] we need smebody actualy devolting lots of time on them -[22:58:44] we need a cleanup as a first step -[22:58:44] Should we set some goals about bugs? -[22:58:53] yep that might be good -[22:58:57] -*- reavertm still has some updates 4.2.1 and wonders whether anyone wants them, especially with 4.2.1 removed from overlay :P -[22:58:59] take care of trackers, duplicates and resolved -[22:59:01] and then fixed -[22:59:15] Do we want to reduce them to a certain number by X months? Do we want to set a goal of taking care of X bugs per week? -[22:59:15] reavertm: pastebin it :] -[22:59:18] i'm sure 100 of them are already fixed or duplicate -[22:59:33] yes -[22:59:36] or invalid -[22:59:36] jmbsvicetto: you are the leader, you should set the number -[22:59:51] --> cypr1nus (n=cypr1nus@plus.ds14.agh.edu.pl) has joined #gentoo-kde -[22:59:57] scarabeus: when I'm done rebuilding kde with them (along with cmake-utils and those pasted kde4 eclass thing - so far so good) -[23:00:12] actualy we can have policy like "you want to be in herd fix X bugz a month" -[23:00:14] :D -[23:00:19] or some other contribution to kde -[23:00:51] i'm ok will all these, just give us the deadlines -[23:00:51] heh =) -[23:01:07] OK. Let's have a vote: get bugs under X or fix X bugs per week? -[23:01:25] the second -[23:01:27] yes! -[23:01:38] the second is more reasonable :] -[23:01:38] define "fix" -[23:01:40] I think the later might be more productive and may help feeling work done -[23:01:43] -*- bonsaikitten self-removes from the herd preemptively -[23:01:44] +1 -[23:01:53] bonsaikitten: hehe -[23:01:56] hhahahahahha -[23:02:06] bonsaikitten: we can give you expection for the kittening :D -[23:02:08] marking as RESOLVED/FIXED only to decrease bug count is wrong approach - I'd agree with flameeyes here :P -[23:02:22] well it has to be fixed too -[23:02:30] I'm not going to create a rule "if you don't fix X bugs per week, you're out", but I think we should all try to solve at least X bugs per week -[23:02:34] haha -[23:02:37] well, for starters it would probably help to weed out the duplicates -[23:02:41] well, I'm fixing too many other things -[23:02:41] reavertm: sure -[23:03:10] jmbsvicetto: btw did you sent the mail about removing of members to nonactive kde members? -[23:03:15] So, a reasonable number would be between 2 and 10? -[23:03:35] 4-10 -[23:03:57] 5 per week? -[23:03:58] a week -[23:04:00] 5 -[23:04:17] but actualy we are fixing even more :P -[23:04:21] i have 5 for today :D -[23:04:27] more than 5 -[23:04:28] lol -[23:04:29] :D -[23:04:33] ;) -[23:04:35] 10? -[23:04:39] 7? -[23:04:41] tampakrap: that is hard to tell -[23:04:46] Ok, let's all try to fix at least 5 bugs per week -[23:04:48] bug a day might be good idea -[23:04:51] ook -[23:04:57] tampakrap: Let's not aim too high -[23:04:59] at least 5 bugs per week -[23:05:14] <-- Caster (i=Caster@gentoo/developer/caster) has quit ("Don't waste your time, or time will waste you.") -[23:05:15] fine -[23:05:19] tampakrap: You're feel to fix 50 in a week if you can ;) -[23:05:27] oh i am? -[23:05:34] yes :P -[23:05:41] ok now we are clear -[23:05:42] bah, You're free* -[23:05:44] a bug a day keeps the doctor away -[23:05:53] hahahhaaha -[23:06:05] bumbl: nice moto -[23:06:07] a bug per day keeps the ladys away -[23:06:12] rofl -[23:06:13] lawl -[23:06:17] hehe -[23:06:20] lol -[23:06:28] dagger: you wanna help with bugz? -[23:06:28] I suggest we had bumbl moto to our page ;) -[23:06:32] do you rly want that to happen? -[23:06:32] tampakrap: 10 bugs a day keep your life away :p -[23:06:35] scarabeus: sure -[23:06:37] jmbsvicetto: agreed -[23:06:56] So, anything else? -[23:07:01] we are done -[23:07:03] dismissed diff --git a/meeting-logs/kde-herd-meeting-summary-20071013.txt b/meeting-logs/kde-herd-meeting-summary-20071013.txt deleted file mode 100644 index 567b83c..0000000 --- a/meeting-logs/kde-herd-meeting-summary-20071013.txt +++ /dev/null @@ -1,72 +0,0 @@ -Summary of 13 October 2007 KDE herd meeting - -Active participants: cryos, genstef, jmbsvicetto*, keytoaster, philantrop, tgurr -In the channel: masterdriverz -Missing: caleb, centic, carlo, deathwing00, mattepiu, troll, vanquirius -* = invited guests - -- Project page: The update of the project page was approved by the participants. - -- Process improvement: This topic was postponed until the next meeting. - -- Misc: - -1. Bump to KDE 3.5.8: -The bump to KDE 3.5.8 is taking place in a git repository to allow for others -to take part, too, and avoid critisism like for the last bump. -This allows interested users to be "trained on the job" including the use of -our QA tools in a controlled environment outside the official tree. -Furthermore, the KDE 3.5.8 is not meant to be public until the release as per -upstream request. -Nevertheless, we will put the finished packages into the tree as package.masked -ASAP to allow arch teams and other devs to test. After that's done, a mail will -be sent to kde@g.o and the core mailinglist by Philantrop. - -2. KDE 3.5.8 in stable for 2007.1: -We will *try* to get KDE 3.5.8 into stable in time for 2007.1 but if we don't, -the world won't stop spinning. We will *not* inform the release guys about us -making it in time to not endanger their time frame needlessly if we don't make it. - -3. Changing to split ebuilds by default: -This suggestion was rejected by the participants for 3.5.x. We will make it the -default for KDE 4, though. - -4. State of KDE4 in the overlay(s): -KDE4 in the overlay is doing well. People are installing it, using it and are -reporting bugs. We currently have both monolithic and split ebuilds. -The participants decided 3:1 for keeping the monolithic ebuilds for KDE4. - -5. Miscellaneous -- A particpant asked for information on cmake ("crash course"). Any input is -appreciated. - -- cmake-utils.eclass. Several participants asked to get it into the tree. The final -remaining "showstopper" is the src_test function which is mostly a verbatim copy -of the one in ebuild.sh. We currently need it to determine if it's an in-source or -out-of-source build. Any input on this is appreciated. -Philantrop is going to re-submit the eclass to the dev mailinglist next week. - -- Arch Testers / Herd Testers. It was suggested to have Herd Testers for the KDE -herd as per GLEP 41. The suggestion was accepted by unanimous vote. -Philantrop will talk to hparker, the AT lead about it. -genstef and jmbsvicetto will prepare a draft for the project page and mail to -kde@g.o. - -- A participant suggested to move the scheduled meeting to the first Saturday of -each month. This was approved by unanimous vote. -keytoaster will update the project page accordingly. - -- Several participants asked about the Herd lead status as this is currently not -reflected on the project page. The participants asked keytoaster to add the -following to the project page directly above the "Members" box: -"We do not have a formal lead: Decisions can be made by every herd member but it usually is a good idea to ask Philantrop because he is around and knowledgable." - - -Tasks: -- Put the finished KDE 3.5.8 packages into the tree in p.mask by October, 14th 2007 -and inform kde@g.o and the core mailinglist about it. (Philantrop) -- cmake-utils.eclass should be re-submitted to the dev mailinglist by next week. (Philantrop) -- Contact the AT project on how to implement HTs for the KDE herd. (Philantrop) -- Prepare a draft for the project page about HTs. (genstef, jmbsvicetto) -- Update the project page with information about project lead and monthly meetings. (keytoaster) - diff --git a/meeting-logs/kde-herd-meeting-summary-20080306.txt b/meeting-logs/kde-herd-meeting-summary-20080306.txt deleted file mode 100644 index 3208285..0000000 --- a/meeting-logs/kde-herd-meeting-summary-20080306.txt +++ /dev/null @@ -1,80 +0,0 @@ -Summary for the Gentoo KDE herd meeting on Thursday, 6th of March 2008 - -Participants: -caleb, cryos, deathwing00, genstef, ingmar, jmbsvicetto, keytoaster, philantrop, tgurr, zlin - -1. Bump to KDE 3.5.9: - -Apart from a few minor issues, the bump to KDE 3.5.9 went well. - -https://bugs.gentoo.org/211116 (mixing split and monolithic ebuilds) was -discussed. 3 participants didn't want the current behaviour changed, 3 were in -favour of changing it. Thus, it was agreed that Ingmar, who volunteered to -change it, should feel free to do it. - -2. KDE 3.5.8 in stable for 2008.0. - -Philantrop stated that KDE 3.5.8 will be in the 2008.0 release. - -3. Removal of KDE < 3.5.8 from the tree. - -gentoofan23 brought up the issue of the removal of older (specifically 3.5.7) -stable KDE versions from the tree after about 19 days and asked for a longer -period for users to upgrade to the newest stable version. -30 days were suggested as a rule of thumb and agreed upon by the majority of -the participants. - -4. State of KDE4 in the tree. - -Ingmar and zlin gave a short information about KDE4 in the tree. The ebuilds in -the tree are in a pretty good state. Their dependencies need to be updated for -compatibility with the newly introduced split Qt-4.4 ebuilds. - -KDE 4.0.2 is currently planned to be included in the tree during the weekend. -(p.masked) - -Anyone who wants to help with the bump to 4.0.2 should simply mail Philantrop -his ssh public key. Interested users who can show they're able and willing to -work on ebuilds are *explicitly* invited, too. -The bump to 4.0.2 is taking place in a git overlay again to allow for non-ebuild -devs to participate, too, and it's a great way to become a dev as Ingmar and -zlin can verify. - -5. Herd Testers: Current state and next steps. - -The HT stuff was delayed because of the trustee elections, etc. -jmbsvicetto and deathwing00 agreed to flesh out the work of a KDE Herd Tester -and publish information about it on the usual Gentoo news channels (pr@g.o, -GMN, Forums). - -6. Lead election: - -Having a sub-lead was discussed to ensure not to have a single point of failure -in case the lead disappears. In a vote, 3 herd members expressed their wish for -a sub-lead, 5 voted against it and there was one abstention. Thus, the notion -was rejected. - -deathwing00 initiated a vote for the lead. Philantrop was nominated and accepted -the nomination. -Philantrop was voted for by 9 of the participants, no votes against him and no -abstentions. Thus, Philantrop was elected the lead of the Gentoo KDE project. - -deathwing00 is going to inform the GMN, pr@g.o and post it on the forums. - -7. Review of the project page - -gentoofan23 and deathwing00 volunteered to update the project page with respect -to KDE versions and other information in the sections 3, 4, 8 and 9 till the -next meeting. - -8. Miscellaneous - -It was decided to re-instate the monthly meetings on the first Thursday each -month. - -9. Date of the next meeting and closing. - -The next KDE herd meeting takes place on Thursday, 3rd of April 2008. - -Philantrop thanked all the Gentoo KDE people for their great work and their -trust in him. diff --git a/meeting-logs/kde-herd-meeting-summary-20081204.txt b/meeting-logs/kde-herd-meeting-summary-20081204.txt deleted file mode 100644 index 8f86331..0000000 --- a/meeting-logs/kde-herd-meeting-summary-20081204.txt +++ /dev/null @@ -1,31 +0,0 @@ -kde3: - cryos and tampakrap are willing to handle its dying. Their priority should be stabilising 3.5.10 and making it live along 4.X. -kde4-eclasses: - currently in reviewing - Jmbsvicetto and krytzz promised helping me up with testing get_latest_kdedir. - Moving htmlhandbook to eclass? jmbsvicetto/scarabeus - fix remaining tree ebuild so they use NEED_KDE="version" and not NEED_KDE="slot" scarabeus will do it. - only eapi2 and greater in eclass: jmbsvicetto will look on this one. -kde4: - try to push versioning in one prefix into upstream. It will be bliss for maintaining. cryos (on kde camp :P) -people-in-team: - write mail to all whom are mentioned on project page and not active to determine their current status. :( - jmbsvicetto willing to do this. -qt4: - yngwin is currently only qt dev, he should get some help, reavertm volunteer (see HT guys are useful :]) -tampakrap: - getting his ebuild-quiz done i scarabeus am willing to help. Yngwin as mentor. -kde-crazy: - snapshots: tampakrap, alexxy, patrick; state: somehow working - live: sput, krytzz, reavertm; state: well live ;] -networkmanager: - scarabeus will ask rbu if he need some help with this vital part of kde4.2 networking. -mysql: - cooperate with robbat2 since kde4.2 and amarok are dead without it. Jmbsvicetto volunteer to help robbat2 so lets se what will be outcome from this. - -:::LONG TERM::: -kde-look/apps: - maybe create some generator for those apps, take look onto app-portage/g-cpan how perl mages do it. -bugwranglers: - reavertm, proposal about letting normal users to wrangle our bugs, most of them are needinfo or already closed so let users help us. - Maybe some wrangler-quiz.txt will be needed. \ No newline at end of file diff --git a/meeting-logs/kde-herd-meeting-summary-20090108.txt b/meeting-logs/kde-herd-meeting-summary-20090108.txt deleted file mode 100644 index 5b61c01..0000000 --- a/meeting-logs/kde-herd-meeting-summary-20090108.txt +++ /dev/null @@ -1,27 +0,0 @@ -kde3: - sent mail asking for volunteers since we are short on staff on kde3. Sqashing bugs/etc. - cryos -eclasses: - done, commit to the tree, anounce on dev, make sure all ebuilds are updated to new structure and revbumped. - scarabeus -kde4: - 4.1.4 after eclasses and mics apps are done, not earlier! - alexxy as a new dev :] - disable +kdeprefix on stable (in the tree) - jmbsvicetto? - 4.2 doublecheck for missing ebuilds, generate metas - alexxy, tampakrap - policykit: suspended for now, when time comes we should cooperate with gnomies - printing: bump everything first in kde-testing, move to tree when we think it is ready, printing suspended until this is done. - !!! NOBODY !!! (leave it on gentoo-desktop?) - write nice guide - tampakrap - fix homepages for kdebase ebuild on correct ones in kde structure - patrick - mono - suspended until someone care, we dont want them - scarabeus -qt4 - status: yngwin states he has some qt apprentices, which is great :] - overlay: there will be new overlay for qt stuff which is yngwin creating - pyqt/pykde messie - patrick, yngwin if they get to it :] - -SPLIT/MERGE overlays VOLTES: -yngwin: merge -kitten: merge -scarab: merge -tampakrap: merge -reavertm: merge -alexxy: merge -cryos: dont mind merge -sput: merge \ No newline at end of file diff --git a/meeting-logs/kde-herd-meeting-summary-20090305.txt b/meeting-logs/kde-herd-meeting-summary-20090305.txt deleted file mode 100644 index 09f2d37..0000000 --- a/meeting-logs/kde-herd-meeting-summary-20090305.txt +++ /dev/null @@ -1,40 +0,0 @@ -AROUND: -yngwin, wired, scarabeus, alexxy, cryos, jmbsvicetto, hwoarang, bonsaikitten, tampakrap, reavertm - -kde3 state/others: -- merging to master branch in kde-testing soon, for more info/help offers talk with tampakrap -- so correct prefixing for kde3 and no more blocks are coming near to you. -- create important bug list and ask bugday people and others for help -> tampakrap - -amarok maintainer: -- send mail to -dev to get one -> scarabeus - -homepage updates: -- we need to keep our webspace up-to-date and guides actualy working -> yngwin, tampakrap - -pykde: -squash the bugs/issues, unslot, unkdeprefix... -> bonsaikitten - -kbluetooth4: -may be even working, needs testing/patching -> wired - -kde4 stabling/keywording: -we need to check deps so they are working on target arches -also we should make less strict deps on kde4 eclass -> scarabeus on this - -cmake-utils: -hopefully done, now only bugfixing -> reavertm, scarabeus - -removal of htmlhandbook: -introduce working doc flag -> probably scarabeus (needs to be done before 4.2.2) - -tarballs splitting and libs/apps versioning: -- discussion to start on the desktop ml -> jmbsvicetto - -snapshots: -send mail to dirk -> jmbsvicetto -repack tarballs -> bonsaikitten -set on rest for now by majority vote, come and volunteer if you want it changed - -bugsquash: -let's aim at having each kde team member fixing 5 bugs per week diff --git a/meeting-logs/kde-project-meeting-log-20090212.txt b/meeting-logs/kde-project-meeting-log-20090212.txt deleted file mode 100644 index f8d29e5..0000000 --- a/meeting-logs/kde-project-meeting-log-20090212.txt +++ /dev/null @@ -1,761 +0,0 @@ -21:00 <@scarabeus> ok sunshines, meeting time :P -21:00 <@hwoarang> is it time? -21:00 <@scarabeus> !herd kde -21:00 * yngwin kicks Willikins -21:00 <@scarabeus> i am going to hurt willikins... -21:00 <+wired> lmao -21:00 <@hwoarang> fail? -21:00 <+MrRat> wired: do you know the amarok qt-4.5 bug at all? -21:00 <@hwoarang> errr meeting time -21:00 <+wired> yeah i read a bug you posted earlier about a missing line -21:01 <@yngwin> i'll use this clone here -21:01 <@scarabeus> :] -21:01 <@hwoarang> ok who broke Willikins -21:01 <@scarabeus> but i want that herd -21:01 <@scarabeus> !herd kde -21:01 < arachnist> hwoarang: i did -21:01 < arachnist> ;) -21:01 <+MrRat> wired: http://rafb.net/p/g1msai72.html -21:01 <@scarabeus> !herd qt -21:01 <@hwoarang> :D -21:01 <+wired> !herd kde -21:01 <@scarabeus> ok the other route -21:01 <+wired> ^_^ -21:01 <+MrRat> wired, thats it, just one line -21:02 <+wired> alright - does that work with 4.4.2 as well? -21:02 <+MrRat> wired: but the file is not generated until about 10% of the build when qtscriptgenerator runs -21:02 <@scarabeus> alexxy, bonsaikitten, cryos, hwoarang, jmbsvicetto, keytoaster, tampakrap, yngwin, dagger_, krytzz, MrRat, reavertm, Sput, wired -21:02 <@scarabeus> meeting -21:02 <@scarabeus> who is around -21:02 * alexxy here -21:02 * tampakrap -21:02 * wired ^_^ -21:02 <+Sput> see above -21:02 * hwoarang * -21:02 * yngwin is a square -21:03 <+MrRat> wired: so when the file is generated, i can edit it and back out of the directory and build is success -21:03 <+krytzz> that joke is OLD :p -21:03 * reavertm reporting -21:03 <@jmbsvicetto> Sput: You're missing people :P -21:03 * jmbsvicet waves hand -21:03 <@yngwin> krytzz: so am i ;) -21:03 <+wired> MrRat: i see -21:03 <+Sput> I'm what? -21:03 <+Sput> mostly I'm missing alcohol and inspiration right now -21:03 <@jmbsvicetto> Sput: Not in FOSDEM? ;) -21:03 <+wired> MrRat: i'll check it out after the meeting -21:04 * yngwin notes that caleb and carlo are missing as usual -21:04 <@scarabeus> ok so are we waiting on somebody else -21:04 <@scarabeus> i wrote carlo a mail -21:04 <@scarabeus> asking him to drop at least for volte :( -21:04 <@tampakrap> cryos also said he will probably be away -21:04 <+wired> we'll give him the logs ^_^ -21:05 <@scarabeus> i know about those missing i am asking if we are waiting on somebody more? -21:05 <@yngwin> bonsaikitten? -21:05 <@scarabeus> yup right -21:05 <@scarabeus> this one i would like to see :P -21:05 <@scarabeus> !lastspoke bonsaikitten -21:06 <@scarabeus> ok that bot actualy dont work now -21:06 <@hwoarang> stupid bots -21:06 -- rangerpb- is now known as rangerhomezzz -21:06 <@scarabeus> ok i give him 4 minutes (agreed?) -21:06 <@tampakrap> ok -21:06 <@hwoarang> k -21:06 <@tampakrap> should i call him? :) -21:06 <@scarabeus> so he has 10 minutes after meeting start to show up :] -21:06 <@scarabeus> :D -21:07 <@alexxy> ok -21:07 <@alexxy> bonsaikitten: !~!!! -21:07 <+krytzz> we count to ten, then shout as loud as we can -21:07 < kev009> what does use=raster for qt-gui? -21:07 <+wired> speeds things up -21:07 <+MrRat> kev009: speed! -21:07 <@scarabeus> krytzz: i would wake teh kids -21:07 <+krytzz> kev009 but breaks compositing :p -21:08 * hwoarang walks around -21:08 * scarabeus prepares editor and stuff for volting and so on :] -21:09 <@hwoarang> time is up -21:09 * wired is building live qt and kde ^_^ -21:10 <@scarabeus> actualy 50 secs -21:10 <@scarabeus> now up -21:10 <@scarabeus> ok -21:10 < kev009> krytzz: is there a document that expalins how compositing breaks? -21:10 <+reavertm> kev009 later please -21:10 <@scarabeus> i officialy start february gentoo kde meeting in year 2009 -21:10 <@scarabeus> :} -21:10 <@scarabeus> so first subject is review of old one -21:11 <@scarabeus> i think we did great job with 4.2 and we deserve some cookies :] -21:11 <@scarabeus> only thing that is missing from last month summary is pyqt/pykde and printing -21:11 <+krytzz> yeah, it was great -21:11 <@scarabeus> so how is the printing status reavertm -21:11 <@scarabeus> only testing needed or some more coding? -21:11 <+reavertm> printing status - it's reportedly working fine -21:12 <@tampakrap> so can we add it to the tree? -21:12 <+reavertm> we need maintainer -21:12 <@scarabeus> ok process will be 1 week in overlay, and then the main tree -21:12 <@scarabeus> reavertm: that is no problem -21:12 <@scarabeus> we are kde herd -21:12 <@scarabeus> we became maintainer -21:12 <@tampakrap> right -21:12 <+reavertm> system-config-printer and pycups are part of leftwovers after Donnie -21:12 <@scarabeus> i know -21:13 <+reavertm> they are straight dependecies for out printing kde stuff -21:13 <@scarabeus> but if it is fixed and working for us we canmaintain -21:13 <@scarabeus> ok there are no issues, so feel free to remove the mask from it in overlay :] -21:13 <@alexxy> scarabeus: also we should unmask networkmanager/policykit -21:13 <+reavertm> and there is one new ebuild that possibly needs to be perfected with some python deps as well - hal-cups-info (in overlay) -21:13 <@scarabeus> alexxy: that is negative my friend -21:13 <@scarabeus> we get to that -21:13 <@tampakrap> we can also start maintaining them and ask in -dev if there are any others intrested in maintaining -21:13 <+reavertm> (it's printer-applet dep) -21:13 <@jmbsvicetto> We could ask the printing herd if they want to co-maintain it -21:13 <@scarabeus> jmbsvicetto: there is no printing herd -21:14 <@scarabeus> really i looked -21:14 <@scarabeus> they are mostly dead -21:14 <@jmbsvicetto> ok -21:14 <@jmbsvicetto> Where's tgur? -21:14 <@yngwin> paper is so last century :p -21:14 <@scarabeus> i have no clue -21:14 <@tampakrap> !seen tgurr -21:14 < Willikins> tampakrap: tgurr was last seen 6 days, 16 hours, 49 minutes and 14 seconds ago, quitting IRC (Remote closed the connection) -21:14 < Philantrop> jmbsvicetto: Health troubles. -21:14 <@jmbsvicetto> Philantrop: ok, thanks for the info -21:14 <@tampakrap> Philantrop: thanks -21:14 <@jmbsvicetto> Philantrop: Do you know if he's still interested in printing packages? -21:15 < Philantrop> jmbsvicetto: Mostly in cups and friends, yes. -21:16 <@scarabeus> ok in that case reavertm should speak to him :] -21:16 <@scarabeus> ok we can wait with printing on him :] -21:16 <@scarabeus> hope his sickness is not serious and he will get well soon :] -21:18 <@scarabeus> ok one more question for the last meeting -21:18 <@scarabeus> did somebody sent that mail about kde3? -21:18 <@yngwin> i havent seen any -21:18 <@scarabeus> that we actualy ask for help on them -21:18 <@scarabeus> tampakrap: so it will be your responsibility i guess -21:18 <@tampakrap> ok -21:19 <@tampakrap> i'll also talk with carlo about this -21:19 <@jmbsvicetto> oh, there was a user that had a comment in my blog entry pleading for us not to drop kde3 -21:19 <@scarabeus> we are not droping it :] -21:19 <@scarabeus> at least for now :] -21:19 <+reavertm> we're droping 4.1 :) -21:19 <+reavertm> (are we?) -21:19 <@scarabeus> and next year i guess -21:19 <@scarabeus> yup we are -21:19 <@scarabeus> as said reaver -21:19 <@scarabeus> anyone is against it? -21:20 <@scarabeus> i wolte for drop :] -21:20 <@hwoarang> +1 -21:20 <@tampakrap> drop -21:20 <+reavertm> kill it -21:20 <+wired> farewell -21:20 <@yngwin> 4.1? yes -21:20 <+Sput> +1 -21:20 <@scarabeus> 4.1 drop are we speaking about :] not the 3.5 :] -21:20 <@scarabeus> yngwin: ^ -21:20 <@yngwin> :) -21:20 <+wired> nobody will miss it anyway ^_^ -21:20 <@jmbsvicetto> bye bye 4.1 -21:20 < termite47384> hwoarang, MrRat: amarok fix0red? -21:20 <@scarabeus> ok super -21:21 <@hwoarang> termite47384 will get to it -21:21 <+Sput> absolutely no need to keep that one around -21:21 <@scarabeus> soo what is on schedule? ah jmbsvicetto you are :] -21:21 < termite47384> sorry, I was away and wasn't sure if you had already -21:21 <@hwoarang> \o/ -21:21 <@jmbsvicetto> scarabeus: :P -21:21 <@scarabeus> btw who will do the drop -21:21 <@scarabeus> alexxy: ? -21:21 <@jmbsvicetto> 4.1? -21:21 <@scarabeus> yup -21:21 <@scarabeus> the drop -21:21 <@tampakrap> may I? -21:21 <@jmbsvicetto> sure -21:21 <@scarabeus> tampakrap: if you want :] -21:21 <+reavertm> still we need to sort packages that may explicitly depend on it -21:22 <+reavertm> so called kde-misc -21:22 <@scarabeus> there are none in the tree :] -21:22 <@tampakrap> of course -21:22 <@scarabeus> tested/fixed -21:22 <+wired> there are -21:22 <+wired> i.e. lancelot-menu -21:22 <@tampakrap> let's double check to be sure -21:22 <@scarabeus> only the powerdevil and lancelot -21:22 <@scarabeus> :] -21:22 <@scarabeus> ok -21:22 <@scarabeus> lets go and volte the leader as we promised -21:22 <@scarabeus> jmbsvicetto: looks like you are the only aplicant -21:22 < Philantrop> *VOTE*. It's *vote*. -21:23 <@tampakrap> i'll drop it in weekend as i'll be away tomorrow (exams) -21:23 <@scarabeus> typo is still the typo -21:23 <+MrRat> The volte is a very small circle that is used in the training of a horse -21:23 <+MrRat> :) -21:23 <+reavertm> could anyone nlighten me, what exactly is this voting for? -21:23 <+wired> o_o MrRat -21:23 <@scarabeus> reavertm: kde team leader -21:23 <@scarabeus> gentoo kde team leader -21:24 <+reavertm> ah, I got confused with Donnie stepping out from desktop lead -21:24 <@scarabeus> so jmbsvicetto why we should volte for you, some promotial i guess :] -21:24 <+reavertm> *down -21:24 <@scarabeus> again -21:24 <@scarabeus> why the crap i write volte -21:24 <@scarabeus> i know it is vote :P -21:24 < dberkholz> well. i can't really step out till someone else steps in -21:24 < dberkholz> till then, i make a great figurehead -21:24 <@yngwin> :) -21:25 <@scarabeus> :D -21:25 <@jmbsvicetto> scarabeus: hmm, because you were impressed with me in FOSDEM? ;) -21:25 <@scarabeus> :] -21:25 <+reavertm> ok, +1 on Jorge -21:25 <@yngwin> +1 -21:26 <@alexxy> scarabeus: yep =) i can drop 4.1.x -21:26 <+krytzz> i dont know if i have the right to vote but, +1 -21:26 <+Sput> _1 -21:26 <@scarabeus> alexxy: too late :] -21:26 <+Sput> eh -21:26 <+Sput> +1 -21:26 <@hwoarang> +1 -21:26 <+wired> +1 -21:26 <@alexxy> and i vote for jmbsvicetto to be kde lead -21:26 <@scarabeus> actualy it counts only from devs :} -21:26 < rane> gratz jmbsvicetto -21:26 <@scarabeus> but i suggest the other way -21:26 <@jmbsvicetto> dberkholz: You make much more than a figurehead, but we're very happy with your figurehead ;) -21:26 <@scarabeus> who is against -21:26 <+Sput> meh, I can still give my moral support :) -21:26 <@jmbsvicetto> rane: :) -21:27 <@jmbsvicetto> scarabeus: you might want to count the positive votes ;) -21:27 <@scarabeus> and ftr i volte for him too -21:27 <@jmbsvicetto> scarabeus: hehe (volte) ;) -21:27 <@tampakrap> jmbsvicetto++ -21:27 * Sput applies 240 volts to scarabeus -21:27 <@scarabeus> sdamn -21:27 <+wired> lmao -21:27 <+MrRat> haha -21:27 <@scarabeus> ok you have 5 votes now -21:27 <+wired> beat a typo with a typo, thats something ^_^ -21:28 <@jmbsvicetto> scarabeus: Don't know if you want to count deathwing00's vote -21:28 <@scarabeus> oh right 6 -21:28 <+MrRat> +1 -21:28 <+MrRat> count me -21:28 <@scarabeus> hwoarang: ping dude -21:28 <@hwoarang> i did say +1 -21:29 <@hwoarang> :) -21:29 <@scarabeus> ok 7 -21:29 <@jmbsvicetto> scarabeus: who's missing? bonsaikitten, cryo? -21:29 <@scarabeus> yup -21:29 <@jmbsvicetto> c/cryo/cryos/ -21:29 <@scarabeus> we can count kittens volte on fosdem? -21:29 <@tampakrap> keytoaster and tgurr -21:29 <@tampakrap> and carlo -21:30 <@yngwin> and caleb -21:30 <+reavertm> ok, lets' go further - 7 is enough already :) -21:30 <@jmbsvicetto> and corsair and genstef if we look at the kde page -21:30 <@scarabeus> those are kde devs? -21:30 <@jmbsvicetto> according to the page -21:30 <@hwoarang> are they active or smtg? -21:30 <@jmbsvicetto> Not in a long time, afaik -21:30 <@scarabeus> actualy i remember somebody promised that he will clean that up :] -21:31 <@jmbsvicetto> So, do I get to wear the KDE royal crown or what? ;) -21:31 <@scarabeus> jmbsvicetto: ok you are the leader -21:31 <@hwoarang> \o/ -21:31 <@scarabeus> nobody volted against actualy :] -21:31 <@yngwin> hail jmbsvicetto -21:31 <@jmbsvicetto> :) -21:31 * scarabeus bows in front of our new leader -21:31 <@tampakrap> congratulations!! -21:31 <@hwoarang> and as a leader you should provide us some free beers -21:31 <@scarabeus> jmbsvicetto: btw you have to update the page yourself, i hate cvs :] -21:31 <@jmbsvicetto> Thanks for the confidence guys -21:31 <+krytzz> right -21:31 <@alexxy> he he =) -21:31 <@jmbsvicetto> :) -21:32 <@alexxy> congratulations jmbsvicetto -21:32 <@tampakrap> POP *champagne* -21:32 <@yngwin> i can update the webpage -21:32 <@yngwin> need to edit it anyway -21:32 <@jmbsvicet> yngwin: thanks -21:32 <@yngwin> np -21:33 <@scarabeus> ok this was actualy funniest part of the meeting -21:33 <@scarabeus> things that will came are not that nice -21:33 <@alexxy> yep -21:33 <@yngwin> so grab another beer -21:34 <@jmbsvicetto> scarabeus: so I guess I can just leave now ;) -21:34 <@scarabeus> grm -21:34 <@scarabeus> actualy you should be leading the discussion now ;P -21:34 <@jmbsvicetto> hehed -21:34 <@scarabeus> ok lets start with upstream and prefixing thingie -21:34 <@scarabeus> i think that is something you have something to say about :] -21:35 <+reavertm> hmm? please introduce topic -21:35 <+reavertm> ah, kdeprefixing -21:35 <+reavertm> but what part of exactly? -21:35 <@tampakrap> i'll change topic -21:36 <+reavertm> no noe -21:36 <@scarabeus> not kdeprefixing -21:36 tampakrap changed the topic of #gentoo-kde to: Official gentoo-kde project channel | KDE 4 guide: http://tinyurl.com/4n47v4 | Next meeting 12/02/2009@20:00 UTC |Overlays: kde-testing, qting-edge | Want to help us? Ask channel staff for info | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | jmbsvicetto is the new leader!! -21:36 <@scarabeus> instaling multiple kde versions in one prefix -21:36 <+reavertm> hmm, how? -21:36 <+reavertm> elaborate please :) -21:36 <@scarabeus> that what jorge has to do -21:36 <@scarabeus> i have not much clue -21:36 jmbsvicetto changed the topic of #gentoo-kde to: Official gentoo-kde project channel | KDE 4 guide: http://tinyurl.com/4n47v4 | meeting: now - multiple installs under 1 prefix |Overlays: kde-testing, qting-edge | Want to help us? Ask channel staff for info | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | jmbsvicetto is the new leader!! -21:37 <+reavertm> I would like to hear what's all about first -21:37 <@jmbsvicetto> ok -21:37 <@jmbsvicetto> We were talking in FOSDEM that the real solution to our kdeprefix issues is to get KDE support for multiple versions in the same prefix -21:38 <+reavertm> eselect? -21:38 <@jmbsvicetto> To get that, we'll need versioned libs and we could use versioned apps (possibly with some symlinks to choose the default versions to use) -21:38 <@alexxy> hmm -21:38 * reavertm shuts up -21:38 <@alexxy> that will be good -21:38 <@jmbsvicetto> reavertm: that was one option presented -21:38 <@scarabeus> which sounds most reasonable -21:38 <@jmbsvicetto> reavertm: I thought it wasn't the best option - at least according to users. But if we get the versioned libs+apps, than it could be a good solution -21:38 <@alexxy> jmbsvicetto: what was another option? -21:39 <@jmbsvicetto> reavertm: the eselect would only select the "default" version -21:39 <+reavertm> what do you mean - versioned libs/apps -21:39 --rangerhom- is now known as rangerpb -21:39 <@scarabeus> sonames pn-version and so on -21:39 <@alexxy> jmbsvicetto: you mean that konsoel would be konsole-4.2.0 ? -21:39 <@jmbsvicetto> reavertm: having kwrite-4.1 or libkdeinit4_kinfocenter.so.4.2.0 -21:40 <@scarabeus> alexxy: only 4.2 -21:40 * Sput wouldn't add support for point releases -21:40 <@jmbsvicetto> alexxy: probably 4.2 -21:40 <@scarabeus> :} -21:40 <@alexxy> hmm -21:40 <+wired> upstream is willing to do something like that? -21:40 <+Sput> though this will of course screw up tab completion :( -21:40 <@scarabeus> upstream is willing to accept our patches for that -21:40 <+Sput> no more automatic space! -21:40 <+Sput> ooh, upstream should do that, rather than us? -21:40 <@jmbsvicetto> alexxy: the idea of the symlinks would be to have a konsole that would point to the version the user wants. Anyone using 4.2 as their default version, could still run 4.1 with konsole-4.1 or live with konsole-live -21:41 <@alexxy> ok -21:41 <+wired> this sounds so much cleaner than kdeprefix -21:41 <@alexxy> what will be with .desktop files? -21:41 <@jmbsvicetto> Sput: That would be the best option, but it doesn't seem likely they'll want to do it by themselves -21:41 <+reavertm> and messy -21:41 <+reavertm> what about shared data? -21:41 <+Sput> also this would allow other distros (with no concept of slotted installs) to support multiple versions easily -21:41 <@jmbsvicetto> Sput: They were however somewhat open to accept our patches to get it done -21:42 <@tampakrap> alexxy and reavertm made some good points -21:42 <+reavertm> like kbuildsysoca area of interest? -21:42 <@scarabeus> reavertm: actualy it is easy to suffix any filename with cmake so it can be all sufixed correctly -21:42 <@jmbsvicetto> reavertm: We could have /usr/share/kde//* or /usr/share/kde/- -21:43 <+reavertm> for me it's just a rehash of kdeprefix but with messed up files and separate - swtitched shared data areas -21:43 <@jmbsvicetto> reavertm: kdeprefix was never the best option. It was just the easy way to get around the fact that kde doesn't version libs/apps -21:43 <+reavertm> it would be easier to just eselect using kdeprefix -21:43 <@scarabeus> actualy this one would mean pretty nice elimination of kdeprefix really -21:43 <@jmbsvicetto> yes -21:44 <+reavertm> and actualy selected version of KDE would be target destination of actually built kde-misc package -21:44 <@scarabeus> reavertm: dependency nightmare -21:44 <@scarabeus> really -21:44 <@jmbsvicetto> reavertm: that seems worse, imho -21:45 <+reavertm> scarabeus we have deps already set per ebuild -21:45 <@jmbsvicetto> reavertm: Instead, with this proposal, kde-misc packages could link directly the unversioned deps -21:45 <@alexxy> ohh -21:45 <@alexxy> deps hell -21:45 <@scarabeus> reavertm: as said jmbsvicetto ^^ -21:45 <@jmbsvicetto> reavertm: The issue it raises is that KDE keeps breaking ABI which would break the packages -21:45 <@scarabeus> you could with this enable easy linking and it would be correct -21:45 <+Sput> well, easiest would just be going back to good old slots. :> -21:45 <@scarabeus> Sput: grm -21:45 <@alexxy> jmbsvicetto: what will be with misc apps that only works with for example kde>=4.3 -21:45 <@jmbsvicetto> Sput: we have slots :P -21:46 <@scarabeus> they link to the kdelibs.so-4.3.0 -21:46 <@jmbsvicetto> alexxy: well, you're not going to like my answer, but *pkgconfig* -21:46 <@scarabeus> for example -21:46 <+Sput> jmbsvicetto: KDE is no longer supposed to break ABI -21:46 <@jmbsvicetto> scarabeus: kdelibs-4.3 I would say -21:46 <@scarabeus> or pkgconfig is even better :] -21:46 <@scarabeus> Sput: they did it. -21:46 <@scarabeus> so we can expect more -21:47 <@jmbsvicetto> What we can do in the future, is to be very active in the kde-packagers / kde-build mls and don't let them get away with ABI breakage -21:48 <@alexxy> hmm -21:48 <@jmbsvicetto> Now, who would like to work on this and does anyone have any ideas on how to get it started? -21:48 <@alexxy> so kde upstream will accept splitting of kde apps? -21:49 <+reavertm> where are kde-misc packages installed and are they subject to versioning as well? -21:49 <@jmbsvicetto> alexxy: They will start doing it for 4.3 -21:49 <@jmbsvicetto> reavertm: I would say /usr and yes -21:50 <@jmbsvicetto> reavertm: Perhaps only between major versions -21:50 <@alexxy> hmm -21:50 <@alexxy> thats will be good -21:50 <+reavertm> so the only thing that's to be done is switching XDG_DATA_DIRS? -21:50 <@alexxy> they idea to add svn rev to snapshots was bad -21:50 <@scarabeus> probably in basic -21:50 <@scarabeus> but also adding sonames and so on -21:50 <@scarabeus> alexxy: that is other point -21:50 <@jmbsvicetto> alexxy: scarabeus mailed them about it -21:50 <@scarabeus> i already sent the mail -21:50 <@scarabeus> but get no response -21:51 <@scarabeus> for 4 days now -21:51 <@scarabeus> so i think we need to push it more -21:51 <@scarabeus> where is the best place? -21:51 <+reavertm> ok, I have a question - how is versioning binaries going to be implemented? -21:51 <+reavertm> via symlinks or shell scripts that set proper env for them? -21:51 <+reavertm> (scripts means overhead) -21:52 <@jmbsvicetto> reavertm: I think we should add the version when we install -21:52 <@jmbsvicetto> reavertm: We also need to write an eselect backend that can help manage the symlinks -21:54 <+reavertm> with eselect env may be switched right away - just like in java-config -21:54 <@scarabeus> btw you are planning way ahead i think, now we should think about who is willing to work on it :] -21:54 <+wired> jmbsvicetto: you said upstream will accept patches for versioning, wouldn't that eliminate the need for env switching? -21:54 <+reavertm> so only symlinks would be sufficient -21:54 * jmbsvicet puts the crown and starts delegating -21:54 <@jmbsvicetto> ;) -21:55 <@scarabeus> jmbsvicetto: dont look at me -21:55 <@jmbsvicetto> wired: If we want to have both around, we'll need the 2 -21:55 <+reavertm> wired env switchig is XDG_DATA_DIRS at least -21:55 <@scarabeus> i will be busy with the other distro patches sharing -21:55 <@jmbsvicetto> wired: unless users are willing to run kwrite-4.1 and amarok-2, instead of kwrite and amarok -21:55 * bonsaikit fell asleep ... -21:55 <+wired> if kde shipped kwrite-4.2 binary -21:55 <@jmbsvicetto> bonsaikitten: Got that bored? :P -21:55 <+wired> we would only need a symlink to make it run -21:56 <@scarabeus> bonsaikitten: tell me your volte ;P -21:56 <@jmbsvicetto> lol -21:56 <@scarabeus> :] -21:56 <@scarabeus> i am just curious -21:56 <@scarabeus> he wont be included :D -21:56 <@jmbsvicetto> wired: yes, but that's what we need eselect for -21:56 <@bonsaikitten> I vote for freedom -21:56 <@jmbsvicetto> scarabeus: lol -> "volte" ;) -21:56 <@scarabeus> ah -21:56 <@scarabeus> sdflhsdlfgksdhs -21:56 * bonsaikit still isn't coherent -21:56 <+wired> jmbsvicetto: i agree, i was refering to env switching, not symlink management -21:57 <@jmbsvicetto> wired: ok -21:57 <+Sput> bonsaikitten: nobody was talking about voting, you are supposed to do a little volte... -21:57 <+reavertm> I like the idea in general -21:57 <@jmbsvicetto> reavertm: what can we do to start the work? -21:57 <@jmbsvicetto> (since you are our cmake expert) -21:58 <@alexxy> write module for eselect -21:58 <@scarabeus> alexxy: that might be actualy last point -21:58 <@bonsaikitten> Sput: re-volt-ing? -21:58 <+reavertm> yeah, that's the magic part -21:58 <+wired> eselect is probably the last of our issues -21:58 <+reavertm> me expert? no.. -21:59 <@scarabeus> reavertm: yes you are our expert :] -21:59 <+reavertm> besides I can't answer about this off the top of my head right away -21:59 <@scarabeus> ok who is willing to work on this: -21:59 <@scarabeus> it is more upstream than gentoo -21:59 <@scarabeus> ? -21:59 <@jmbsvicetto> I'll have to look at it -22:00 <@jmbsvicetto> reavertm: can I nag you about cmake for this? -22:00 <+reavertm> I'll look into it -22:01 <@scarabeus> anyone else? -22:01 <@scarabeus> *doggyeyes* -22:01 <@scarabeus> or actualy *puppyeyes* -22:01 <@jmbsvicetto> scarabeus: Thanks for your offer -22:01 <@scarabeus> that sad look :] -22:01 <@scarabeus> jmbsvicetto: i will be quite fine with patch cooperation -22:01 <@scarabeus> :P -22:01 * jmbsvicet just made his first lead decision -22:01 <@jmbsvicetto> :P -22:01 <@scarabeus> :D -22:01 <@alexxy> heh =) -22:01 <@alexxy> btw -22:01 <@scarabeus> jmbsvicetto: ok and mine lead decision is delegat -22:02 <@scarabeus> e -22:02 <@scarabeus> so HTs what are you doing? :P -22:02 <@alexxy> whet will be with kde 3.5? -22:02 <@scarabeus> alexxy: that is on tampakrap, dont worry :] -22:02 <@tampakrap> mostly on carlo i'd say -22:02 <@jmbsvicetto> bonsaikitten: Anyway we can use your tinderbox for helping with the testing? -22:02 <@alexxy> there still parts of 3.5.7 3.58 3.5.9 and 3.510 -22:03 <@yngwin> i'd say drop 3.5.{7,8} -22:03 <@yngwin> and stabilize .10 asap -22:03 <@scarabeus> ok that is good idea -22:03 <@scarabeus> get rid of 7.8 -22:03 <@jmbsvicetto> yeah, but we need to check arches keywords -22:03 <@scarabeus> the arch teams has plenty time up to now to stable 3.5.9 on all needed arch -22:03 <+reavertm> stabilize 3.5.10 with revbumping kde-misc to be installed in /usr/kde/3.5? -22:03 <@scarabeus> yep -22:04 <@alexxy> yep -22:04 <@alexxy> but 3.5.8 is monolitic -22:04 <@alexxy> last monolitic release -22:04 <@scarabeus> that is no problem -22:04 <@jmbsvicetto> alexxy: 3.5.9 -22:04 <@scarabeus> and 3.5.9 is mono to -22:04 <@alexxy> so we can drop it =) -22:04 <@jmbsvicetto> 3.5.10 was teh first release without monos -22:05 <@jmbsvicetto> we need to check arch keywords as at least mips will probably lose all keywords -22:05 <@scarabeus> jmbsvicetto: well since mips is only ~ and they had actualy pretty long time to do it up to now... -22:06 <@scarabeus> but ok, lets poke them -22:06 <@jmbsvicetto> scarabeus: let's talk to them -22:06 <@alexxy> heh -22:06 <@alexxy> i can test kde on ~mips -22:06 * reavertm has his own 3 agenda points on the list -22:06 <@alexxy> =) -22:06 <@scarabeus> jmbsvicetto: actualy alexxy can do it :] -22:06 <@scarabeus> late -22:06 <@scarabeus> :D -22:07 <@jmbsvicetto> alexxy: are you in the mips arch team? -22:07 <@alexxy> seems they add me -22:07 <@alexxy> =) -22:07 <@alexxy> i have mips machine @work -22:07 <@alexxy> running gentoo -22:07 <@jmbsvicetto> Good :) -22:07 <@alexxy> also i have premison to add arm keywords -22:07 <@alexxy> =) -22:08 <+wired> so our kde4 upstream patches goal is to patch cmake to build/install everything version-prefixed with version-suffixed binaries? -22:08 <@scarabeus> alexxy: ok i delegate this point to you :] -22:08 <@scarabeus> ok one last thing from me -22:08 <@scarabeus> cooperating with reasonable distributions in patches sharing -22:09 <@alexxy> jmbsvicetto: i'll test kde:4.2 on mips -22:09 <@scarabeus> reasonable as debian for example -22:09 <@scarabeus> not as suse -22:09 <@hwoarang> scarabeus: like? -22:09 <@jmbsvicetto> alexxy: ok, thanks -22:09 <@scarabeus> hwoarang: like they have upstream and downstream patches we would like so we use them -22:09 <+Sput> you mean: distros backporting features from 4.3 trunk to 4.1 stable are not reasonable? :) -22:09 <@scarabeus> and in return we share our patches -22:09 <@jmbsvicetto> scarabeus: We can work with any distro - it all depends on their work ;) -22:09 <@scarabeus> for that i wrote this -22:09 <@scarabeus> http://dev.gentoo.org/~scarabeus/patches-glep.html -22:09 <@scarabeus> jmbsvicetto: i know -22:10 <@scarabeus> but i think we should make our patches nicely accessable like debian do -22:10 <+dagger_> I just came back home ;( -22:10 <@scarabeus> dagger_: bad for ya :] -22:10 <+reavertm> we use sed :P -22:10 <+Sput> System Message: ERROR/3 (patches-glep.txt, line 65) -22:10 <+Sput> Unexpected indentation. -22:10 <+Sput> coool : -22:10 <@scarabeus> i know -22:10 <+Sput> :) -22:10 <@scarabeus> it is not finished -22:11 <@scarabeus> christ why i showed it to you -22:11 <@scarabeus> i thought that somebody start complaining -22:11 <+Sput> :D -22:11 <@scarabeus> notes for this one will be accepted on my mail for now -22:11 <@scarabeus> until i get it into some reasonable shape for anouncing -22:12 <@hwoarang> your abstract idea is quite resonable -22:12 <@hwoarang> have you talked about this with other distro dudes? -22:12 <@tampakrap> we had a small chat with a debian-kde guy at fosdem -22:12 <@scarabeus> yep i talked with kde -22:12 <@scarabeus> debina -22:12 <@scarabeus> craaap -22:13 <@jmbsvicetto> scarabeus: You'll want to talk to infra and security teams about your proposal -22:13 <@scarabeus> yes i will do it -22:13 <@scarabeus> when i finish it -22:13 <@scarabeus> :P -22:13 <@jmbsvicetto> hehe -22:13 <@scarabeus> i dont want to come there with my hands empty -22:13 <@scarabeus> i would feel lame -22:14 <@scarabeus> so you know that i am on this one -22:14 <@scarabeus> that is everything from my side -22:14 <@scarabeus> anyone what do you have to discuss -22:14 <@jmbsvicetto> scarabeus: Did we cover all business in the agenda? -22:15 <@scarabeus> the things i pointed out -22:15 <@scarabeus> but this month i didnt get notes from others -22:15 <@scarabeus> (short time) -22:15 <+reavertm> ok... pykde4? -22:15 <@scarabeus> that is why i ask now -22:15 <@scarabeus> that bonsaikitten said that he will look on it -22:15 <@scarabeus> last meeting -22:15 <@scarabeus> :D -22:15 <+reavertm> that's the problem :) -22:16 <+reavertm> ok, another one -22:16 <+reavertm> what about non-SLOTted sets? -22:16 <@alexxy> btw -22:16 <@alexxy> when sets will be added to tree? -22:16 <+reavertm> I'd propose to remove them or made symlinks -> @kdebase -> @kdebase-4.2 and so on -22:17 <@tampakrap> are the symlinks valid? -22:17 <+reavertm> because unSLOTtted sets pulll all versions from every SLOT -22:17 <+reavertm> (in overlay) -22:17 <+reavertm> alexxy no -22:17 <+reavertm> never :) -22:17 <+reavertm> tampakrap why they coudn't be? -22:17 <@scarabeus> reavertm: good idea -22:18 <@jmbsvicetto> alexxy: That needs more time -22:18 <@jmbsvicetto> alexxy: we need to get an agreement about it -22:18 <@alexxy> ohh -22:18 <@alexxy> =( -22:18 <@tampakrap> reavertm: i don't know, i'm just asking :) -22:18 <@scarabeus> tampakrap: it works -22:18 <@yngwin> i guess that means at least waiting till portage 2.2.0 final release -22:18 <@jmbsvicetto> reavertm: the unversioned set should match the last version -22:19 <@tampakrap> last version of portage kde or of snapshots? -22:19 <+reavertm> yes -22:19 <@jmbsvicetto> reavertm: wait, you want them to have slotted deps? They can't -22:19 <+reavertm> those would be symlinks to latest set (but versioned one) -22:19 <+reavertm> jmbsvicetto it simplyfies upgrade -22:19 <@alexxy> yep -22:20 <+reavertm> I want unslotted sets to be removed or changed to symlinks to corresponding slotted sets -22:20 <@jmbsvicetto> reavertm: The unversioned deps should match the last version with sed s/:.*$// -22:20 <@alexxy> but unversioned sets should point to latest in tree slot -22:21 <@jmbsvicetto> reavertm: We need/want users to run the unversioned sets for installing - thus it can't have slotted deps -22:21 <+reavertm> jmbsvicetto wait wait -22:21 <+reavertm> there would be @kdebase set - the only difference would be, it would be symlink to @kdebase-4.2 -22:22 <@jmbsvicetto> reavertm: but that would mean it would have a kdebase-startkde:4.2 dep -22:22 <@tampakrap> aka latest portage version -22:22 <+reavertm> how are deps related? -22:22 <@jmbsvicetto> reavertm: I'm thinking :P -22:22 <+reavertm> they would be symlinks to latest portage version -22:23 <@jmbsvicetto> reavertm: I understand what you're trying to do. It might be the easiest option and it might even work -22:23 <+reavertm> (just like they are now) - but with SLOT definition so that we actually pull only that slot -22:23 < Enrico[ITA]> hi guys! if here there is some dev of kde-testing overlay there are some missing deps in kde-3.5.keywords file: kde-base/kde-i18n:3.5 ~kde-base/dcoppython-3.5.10 (and app-pda/libopensync but this is not part of kde ^^) -22:23 <@jmbsvicetto> Enrico[ITA]: we're in the middle of a meeting. Stick around and we can talk about it later -22:24 <@jmbsvicetto> reavertm: ok, I think I can live with it -22:24 <@tampakrap> i agree with that too -22:24 <+reavertm> jmbsvicetto well, it doesn't change anything from user perspective -22:24 <@jmbsvicetto> reavertm: my concern was that we might be restricting users to a specific slot -22:24 < Enrico[ITA]> jmbsvicetto: oh don't warry it is not a huge issue ^^. but ok i can wait no problem ^^ -22:24 <@scarabeus> yeah it should work -22:24 <@scarabeus> jmbsvicetto: that should be working correctly -22:25 <@scarabeus> the update with this -22:25 <@scarabeus> iirc the behavior portage does -22:25 <+reavertm> well, we would be responsible for managing those symlinks in overlay -22:25 <@jmbsvicetto> reavertm / scarabeus: yes, I see it should work -22:25 <@jmbsvicetto> reavertm: hmm, I do hope to get those sets in the tree - one day, one day -22:26 <@jmbsvicetto> reavertm: actually, if/when zmedico gets to re-work the sets, we might just have unversioned sets -22:26 <+reavertm> yeah -22:26 < Enrico[ITA]> well since you are in the middle of a meeting think about mark kde 3.5.10 as stable (and maybe even kde4.2!!!!) well i'm just kidding don't ban me ihihihi :P -22:26 <@jmbsvicetto> reavertm: or we would, if upstream stopped playing with moving apps between tarballs and renaming apps -22:26 < Enrico[ITA]> i don't speak no more promise ^^ -22:27 <+reavertm> well, it's up to us how we split packagees jmbsvicetto :) -22:27 * reavertm likes good refactoring -22:27 <@jmbsvicetto> reavertm: we'll have to follow the work being done for 4.3 -22:27 <@jmbsvicetto> :) -22:28 <@tampakrap> that's why snapshots and :live are :) -22:28 <@tampakrap> we were following 4.2 pretty well if you recall -22:28 <@jmbsvicetto> yes, but they're talking about splitting packages for 4.3 -22:29 <@jmbsvicetto> They seem willing to break apps, but not libs -22:29 <@jmbsvicetto> I think we should probably rethink the way we split libs and kdebase-runtime/kdebase-workspace -22:29 <@alexxy> why? -22:29 <@tampakrap> so what? i rebuild live every two days i follow changes -22:30 <@jmbsvicetto> alexxy: we probably don't need to split it up so much -22:30 <+reavertm> probably -22:30 <@alexxy> well i think current split are pretty well =) -22:30 <+reavertm> I'd vote for debian-like splitting scheme -22:31 <+reavertm> they split kdepim completely (like we do) but kdebase-workspace /runtime not that much -22:31 <@alexxy> reavertm: what it looks like? -22:31 <@tampakrap> ok i'll have a look at this -22:31 <+reavertm> (as those apps need to be installed for kde to work anyway) -22:31 <+reavertm> (they split plasma from kdelibs - for now reason whatsoever) -22:32 <@alexxy> hmmm -22:33 <+reavertm> ok, and I have another idea - drop kdepimlibs from DEPEND in eclass -22:33 <@alexxy> last time i take a look at debian it was using kde 2.x or 1.x dont remember -22:33 <+reavertm> I made alittle research and there are just some components that actually need it -22:34 <+reavertm> and plenty of people crying aabout mysql deps (akonadi server is pulled by kdepimlibs) -22:34 <+reavertm> alexxy well... you can look at Kubuntu... -22:34 <@jmbsvicetto> reavertm: seems like aseigo was willing to split plasma from kdelibs too -22:34 <+reavertm> it's debian afterall -22:34 <@tampakrap> upstream is going to import other dbs as well -22:34 <+reavertm> tampakrap any evidence? -22:34 <@jmbsvicetto> reavertm: if we can drop it, we should -22:34 <@tampakrap> fosdem talks :) -22:34 <@jmbsvicetto> (kdepimlibs) -22:34 <+reavertm> apart tahat techbase article saying that itis possible to implement but not planned? -22:35 <@jmbsvicetto> tampakrap: s/import/support/ ? -22:35 <+reavertm> jmbsvicetto yeah, we can -22:35 <+reavertm> I've made a list for kde-base stuff that needs it (I was grepping KdepimLibs in cmakelistx.txt in tarballs -22:36 <@jmbsvicetto> reavertm: ok, I'll look at it -22:36 <+reavertm> jmbsvicetto no, you "encourage" kitten to take care of pykde4 :) -22:36 <@jmbsvicetto> hehe -22:37 * jmbsvicet picks up the whip and calls for bonsaikitten -22:37 <@jmbsvicetto> kitten, kitten -22:38 <@scarabeus> :D -22:38 <@scarabeus> ouka i am back -22:38 <@scarabeus> what i sleft -22:38 <@scarabeus> (sorry i feel really dizzy today) -22:39 <+MrRat> reavertm: yes more db support is coming for akonadi -22:39 <+MrRat> http://techbase.kde.org/Projects/PIM/Akonadi#Akonadi_FAQ -22:40 <@jmbsvicetto> What are we still missing for today? -22:40 <+MrRat> a crazy hack at fixing amarok2 for qt-4.5 -22:40 <@tampakrap> yes, me and scarabeus saw it at fosdem talk of the debian kde packager -22:41 <@scarabeus> jmbsvicetto: i dont know -22:41 <@scarabeus> i dont have anything for adding -22:41 <@scarabeus> anyone else something? -22:41 <@ hwoarang> yngwin do we have something to add? -22:42 <@scarabeus> hwoarang, yngwin: actualy you two could you test qt-4.5 on kde-4.2 and spread patches? :] -22:42 <@ yngwin|2> kde4 doesnt work here -22:42 <@tampakrap> y? -22:42 <@hwoarang> works here though -22:43 <@hwoarang> scarabeus who this thing gonna work? -22:43 <@alexxy> http://dpaste.com/119912/ -22:43 <@hwoarang> gentoo qt <-> gentoo kde <-> kde upstream -22:43 <@alexxy> list of kde-3.5.[45678] ebuilds -22:43 <+wired> i can help on qt4.5/kde4.2 testing :) -22:43 <@hwoarang> we need to CC kde@gentoo.org on every kde4+qt4-5 related issue -22:43 <@ alexxy> yngwin: hwoarang: plasma segfaults with qt 4.5 if you dont recompile it -22:44 <@alexxy> same for knotify -22:44 <@hwoarang> there is a topic on kde forums -22:44 <@hwoarang> kde-4.2+qt-4.5 -22:44 <@tampakrap> recompile qt or knotify? -22:44 <@alexxy> so you two should add it to ewarn -22:44 <@hwoarang> maybe it will be good to monitor it -22:44 <@alexxy> recompile knotify and plasma-workspace -22:45 <@hwoarang> alexxy: we need to narrow down what should be rebuild -22:45 <@hwoarang> if something fails -22:45 <+reavertm> I guess I'm out of ideas for today as well -22:45 <@hwoarang> and i think that our ewarn message is quite clean -22:45 <@hwoarang> "if something fails, rebuild it" -22:45 <@alexxy> yep -22:45 <@jmbsvicetto> alexxy: the kde packages segfault after qt upgrade is an old issue -22:45 <@tampakrap> are these talks still on the meeting? -22:45 <@alexxy> but you only mention kdelibs -22:45 <@hwoarang> this is what every qt package states on pkg_postinst -22:45 <@alexxy> =) -22:46 <@alexxy> jmbsvicetto: i know -22:46 <@hwoarang> if this solution is valid i ll add it -22:46 <@alexxy> but for 3.5 only kdelibs was needed to be recompiled -22:46 <@hwoarang> but there is a report on forums that libplasma+ plasma-workspace didn solve it -22:46 <@alexxy> for 4.2 its at least kdelibs and plasma-workspace -22:47 <+MrRat> if sets were in portage an @kde-4.2 would solve it -22:47 <+MrRat> :P -22:47 <@alexxy> he he -22:47 <@hwoarang> so , from my part i ll CC kde@g.o alias on every mixed kde4+qt4.5 bug -22:47 <@hwoarang> to work it together -22:47 <@scarabeus> http://pastebin.ca/1335397 -22:48 <@scarabeus> reformat add on cvs -22:48 <@hwoarang> i wish i could do it on bugs.kde.org too -22:48 <@scarabeus> i am sick and going to sleep -22:48 <@scarabeus> i hope i wont be needed today anymore -22:48 <@tampakrap> i guess meeting is over -22:49 <@jmbsvicetto> scarabeus: You should end the meeting then ;) -22:49 <@jmbsvicetto> hwoarang: what are you missing in bgo ? -22:49 <@tampakrap> you are the leader -22:49 <@hwoarang> mmm -22:49 <@jmbsvicetto> ah, bko -22:50 <@hwoarang> every time i try to add a gentoo alias -22:50 <@hwoarang> it slaps me -22:50 <@hwoarang> ah -22:50 * jmbsvicet puts the hat and officialy ends the meeting -22:50 <@hwoarang> no on bgo -22:50 <@hwoarang> on bugs.kde.org -22:50 <@jmbsvicetto> yeah, I noticed it after I asked -22:50 <@jmbsvicetto> scarabeus: just one issue before you go, if you have 2 minutes -22:52 <@scarabeus> ook -22:53 <@scarabeus> listening -22:53 < arachnist> so, since the meeting has ended -22:53 < arachnist> is there a nice, working networkmanager plasmoid for kde-4.2? :> -22:53 < arachnist> preferably with an ebuild -22:54 <@jmbsvicetto> scarabeus: About the meetings, do you want me to start doing the preparation work or would you be willing to keep doing it? -22:54 <@scarabeus> i am willing to keep doing it if you want :] -22:54 <@jmbsvicetto> scarabeus: You've been doing a great job and I don't want to take away that pleasure from you ;) -22:54 <@jmbsvicetto> scarabeus: thanks -22:54 <@scarabeus> it is not pleasure ;D -22:54 <@scarabeus> but i will do it -22:54 <@jmbsvicetto> Hehe -22:54 <@scarabeus> since nobody else wants to do it :] -22:55 <@jmbsvicetto> ok, meeting in 1 month? -22:55 <@scarabeus> arachnist: there is networkmanager-applet-9999 in kde-testing -22:55 <@jmbsvicetto> I think we should review the date as I missed the council meeting today :\ -22:55 <+MrRat> arachnist: networkmanager-applet ebuild is in kde-testing, but in short, networkmanager nor the applet work well. -22:56 <+MrRat> arachnist: use wicd -22:56 < arachnist> wicd? -22:56 <+MrRat> yes -22:56 < arachnist> it needs gtk -22:56 <@scarabeus> yup 1 per month -22:56 <@scarabeus> feel free to change the date -22:56 < arachnist> there;s a reason i have gtk+ in package mask -22:56 < Pesa> may i ask if you could remove the new hard dep on qt-phonon for Qt 4.5, making it optional? -22:56 <@scarabeus> i just randomly picked -22:56 < arachnist> there's* -22:56 <+MrRat> wicd works great and you can start wicd-client in kde4's ststem settings autostart and it works great -22:57 <@jmbsvicetto> scarabeus: ok -22:57 < arachnist> not a very valid one, but there is ;> -22:57 <@jmbsvicetto> scarabeus: I think we might opt for the 1st Thursday of the month -22:57 <@jmbsvicetto> I'll ask in the alias/ml -22:57 <@scarabeus> that is already in there or not? -22:57 <@scarabeus> :D -22:57 <@jmbsvicetto> ok, I'm going to eat something -22:58 <@yngwin> Pesa: there is no hard dep on qt-phonon -22:58 <@scarabeus> on the first Wednesday/Thursday of every month at 19:00 UTC -22:58 <@scarabeus> indeed i wrote this ;} diff --git a/meeting-logs/kde-project-meeting-log-20090401.txt b/meeting-logs/kde-project-meeting-log-20090401.txt deleted file mode 100644 index 0c83346..0000000 --- a/meeting-logs/kde-project-meeting-log-20090401.txt +++ /dev/null @@ -1,601 +0,0 @@ -21:01 <@scarabeus> hey -21:01 <@scarabeus> now we can start -21:01 <@jmbsvicetto> I'm out of here. See you later :P -21:02 <@alexxy> jmbsvicetto: stay here =) -21:02 <@scarabeus> hehe -21:02 <@scarabeus> !herd kde -21:02 < Willikins> (kde) alexxy, caleb, carlo, cryos, deathwing00, genstef, jmbsvicetto, keytoaster, mattepiu, patrick, scarabeus, tampakrap, tgurr -21:02 <@scarabeus> krytzz: reavertm Sput wired -21:02 <@scarabeus> ausing again -21:02 <@scarabeus> meeting time -21:03 <+krytzz> aye -21:03 * tampakrap is here -21:03 <@cryos|work> That was an hour ago wasn't it? I thought we were done :P -21:03 * jmbsvicetto agrees -21:03 <@scarabeus> :D -21:03 * alexxy here or there like a psi^2 -21:04 <@scarabeus> bonsaikitten: dont hide, i saw ya -21:04 -!- jmbsvicetto changed the topic of #gentoo-kde to: Official Gentoo KDE Project channel | Next Meeting^Wamarok party: Wednesday April 1st 19:00 UTC | KDE 4 guide: http://tinyurl.com/4n47v4 | Overlays: kde-testing, qting-edge | Want to help us? Ask channel staff for info | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 -21:04 <@scarabeus> !herd qt -21:04 < Willikins> scarabeus: (qt) caleb, carlo, hwoarang, yngwin -21:04 * jmbsvicetto starts jumping around -21:04 <@jmbsvicetto> scarabeus: ok, ok. I'll behave ;) -21:04 <@hwoarang> im here -21:04 * hwoarang GOGO GREEEEEEEEEEEEEECE -21:04 <@scarabeus> jmbsvicetto: well you are the lead, you do the example for us :D -21:05 <@scarabeus> remember we store meeting logs tho :D -21:05 <@tampakrap> i think we shouldn't this time -21:05 <@scarabeus> hehe -21:05 <+reavertm> ok... -21:05 <@scarabeus> reavertm: you are first on list -21:05 <@scarabeus> so speak up -21:06 <@scarabeus> :D -21:06 <+reavertm> so, kdeprefix -21:06 <@scarabeus> http://www.pastebin.cz:80/16911 -21:06 <+reavertm> the idea is ... to drop it :) -21:06 <@scarabeus> (list for others) -21:06 * wired back -21:06 <@alexxy> or mask kdeprefix useflag -21:06 <@alexxy> =) -21:06 <+reavertm> (from non kde-base) -21:06 <@tampakrap> i agree -21:07 <+reavertm> I already started to play in dropped-kdeprefix-on-non-kde-base branch if anyone is interested -21:07 <@alexxy> may be better to mask it for all packages -21:07 <+reavertm> in the process I rewritten kde4 eclass -21:07 <@alexxy> so people who realy want could unmask it -21:07 -!- spitfire_ [n=quassel@ackz136.neoplus.adsl.tpnet.pl] has joined #gentoo-kde -21:07 <+reavertm> important changes are: -21:07 <@scarabeus> alexxy: nah i prefer nonkdeprefix, it is better -21:08 <@scarabeus> alexxy: less thins to worry about -21:08 <+reavertm> NEED_KDE deprecated in favor of KDE_REQUIRED and KDE_MINIMAL (the latter already there) -21:08 <+wired> scarabeus++ -21:08 <@alexxy> scarabeus: i use -kdeprefix too -21:08 <@alexxy> so we can mask kdeprefix use flag for tree packages -21:08 <@tampakrap> if we mask it, we somehow still provide support for it, something that i don't want -21:08 <@cryos|work> I use -kdeprefix too, but I think it would be nice to keep it as an option that can be unmasked. It has its uses, I just don't think it is for general consumption... -21:08 <@alexxy> so people who want install 4.2 4.3 and live together can unmask it -21:09 <+reavertm> my eclass drops kdeprefix from non-kde-base -21:09 <@scarabeus> alexxy: the part for non-kde-base -21:09 <@scarabeus> not for base kde -21:09 <@scarabeus> :D -21:09 <+reavertm> do you even read me? -21:09 <@scarabeus> we are not removing the flags from kdebase/* -21:09 <@scarabeus> :D -21:09 <@cryos|work> Is there a way to hack it back in for non-kde-base if you don't care about support? -21:09 <@tampakrap> everybody stop typing until reavertm finishes his words please -21:09 <@scarabeus> cryos|work: narp -21:10 <@scarabeus> for the eclass i already read it and i think it is much cleaner, specialy no "get_latest_kdedir" -21:10 <@cryos|work> I work on several packages where I would like trunk and release. I could locally hack it, but the current situation is useful even if not supporte.d -21:10 <+reavertm> RPATH solves possible linking issues -21:10 <@scarabeus> well we droped mostly live slot for packages -21:10 <@scarabeus> cryos|work: buty you can allways override prefix so it shoudl be no prob -21:11 <+reavertm> now packages are built not agains newest available KDE (if more installed) but with the oldest - yet respecting KDE_MINIMIAL -21:11 <@cryos|work> Seems a shame, but I can maintain custom ebuilds for the few I work on. -21:11 <+reavertm> scarabeus: all live slots dropped -21:12 <@jmbsvicetto> hmm, scarabeus / reavertm drop kdeprefix for non-live, right? -21:12 <@scarabeus> for everything -21:12 <@jmbsvicetto> scarabeus / reavertm: !kde-base live apps should install under /usr/kde/live -21:13 * cryos|work thought that too... -21:13 <+reavertm> /usr/kde/live is KDE release dir and should not contain any 3rd party apps imho -21:13 <@scarabeus> that wont run for pple that install live misc apps for 4.2 in example -21:13 <@alexxy> jmbsvicetto: no =) -21:13 <@jmbsvicetto> We've been talking about this for a long time. all live ebuilds should go under /usr/kde/live -21:13 <@scarabeus> i use lots of live apps -21:13 <+reavertm> how aboyut accessing those live packages from kde 4.2 ? -21:13 * alexxy also use kile amarok and k3b -21:13 <@alexxy> with 4.2 and 4.3 snapshots -21:14 <@alexxy> so i dont like idea of dropping kdeprefix for misk apps -21:14 <@jmbsvicetto> If we use the KDE_MINIMAL it should work, no? -21:14 <@cryos|work> So you are dropping any support for installing/building live apps against live KDE builds? -21:14 <@alexxy> in way as jmbsvicetto said -21:14 -!- [DWSR] is now known as DWSR -21:14 <+reavertm> how is dropping kdeprefix from live packages related to not being able to use them with 4.2 ? -21:14 <@scarabeus> cryos|work: so you think live should be special case... -21:15 <@scarabeus> reavertm: well it can be done so live is special enviroment -21:15 <@alexxy> i think better to mask kdeprefix use flag for all kde in tree -21:15 <@scarabeus> and we can just not bother for it -21:15 <@jmbsvicetto> scarabeus: That's why live doesn't fit in SLOTS ;) -21:15 <@cryos|work> scarabeus: I always have, but I tend to work with live and do development, but want a stable desktop for work... -21:15 <@alexxy> so people who want eg 4.2 and live togther can deal with it -21:16 <@scarabeus> alexxy: current approach is broken -21:16 <+reavertm> I use 4.2 and live non-kde-base stuff -21:16 <@scarabeus> i srsly fear next major release -21:16 <@jmbsvicetto> ok, let's try something different -21:16 <@jmbsvicetto> The point of having kdeprefix was to allow running more than 1 version at the same time -21:16 <@cryos|work> I guess for people with live KDE, and live misc apps built against 4.2 things would likely still work though. -21:16 <@scarabeus> eys that is maintained -21:16 <+reavertm> jmbsvicetto: be more precise -21:16 <+reavertm> more than one version of what? -21:17 <+reavertm> KDE release or any package? -21:17 <@jmbsvicetto> With the exception of live (imo) which should be under /usr/kde/live - the real solution for that is to change the kde build system and have all versions under /usr -21:17 <@cryos|work> KDE, but are you really trying to separate packages that build against it? -21:17 <@scarabeus> well it is like kde3 -21:17 <@scarabeus> cryos|work: -21:17 <@jmbsvicetto> reavertm: more than one KDE release -21:17 -!- non7top [n=non7top@94.77.134.21] has joined #gentoo-kde -21:17 <+reavertm> and you'll still have it :P -21:18 <@cryos|work> OK - I will stay quiet. I am really busy today anyway and have not been on IRC for weeks.... -21:18 < spitfire_> cryos|work: no it doesn't always work. I had quassel built against 4.2 and it didn;t run in live complaining about missing symbols in oxygen.so. -21:18 <@jmbsvicetto> The point is whether anyone is willing to start the work -21:18 <@jmbsvicetto> I haven't looked at that yet -21:18 <+reavertm> spitfire_: -21:18 <+reavertm> nop -21:18 <@jmbsvicetto> cryos|work: I would like to get your opinion about this issue -21:18 <+reavertm> you had quassel built againd live that didn;'t work with 4.2 -21:19 <+reavertm> because so far it was like this - having 4.2 and -9999 - apps were bult againt *the newest* kde -21:19 <@cryos|work> At least now KDE will work if built against an old KDE and linked to a newer one. -21:19 <@scarabeus> yes -21:19 <@jmbsvicetto> cryos|work: We've talked a lot about this and tried to reach a compromise that would satisfy everyone, so I would like that any change gets our support -21:19 <@cryos|work> So building against 4.2 and linking to live should work, assuming no one screwed up and I do that a lot. -21:19 <@scarabeus> yes it have to wor -21:19 <@scarabeus> the cant break abi -21:19 < spitfire_> reavertm: sry to interrupt but for example quassel never finds kde-live, always builds against 4.2 -21:19 <+reavertm> actually there's RPATH -21:20 <+reavertm> if we drop RPATH then we may start worrying about linkage problems -21:20 <@cryos|work> It doesn't have to - people screw up... And there is RPATH which can force linking to a particular path. -21:20 <@jmbsvicetto> scarabeus: that's the "theory", but that's not their practice -21:20 <@alexxy> spitfire_: later -21:20 <@scarabeus> indeed -21:20 <@cryos|work> jmbsvicetto: They do pretty well on the whole, but RPATH alleviates issues with screw ups too... -21:20 <+reavertm> (and I'm going to drop rpath for -kdeprefix) -21:20 <+reavertm> (btw) -21:20 <@jmbsvicetto> cryos|work: all the mess with libplasma, phonon, kdeartwork-kscreensaver, ... -21:21 <+reavertm> phonon is kdeprefix problem -21:21 <@cryos|work> Like I said, they do pretty well... ABI is really tough to keep stable... -21:21 <+reavertm> it install kde4 plugins -21:22 <+reavertm> adding QT_PLUGIN_PATH to /usr/lib64/kde4/plugins could possibly solve it -21:22 <@jmbsvicetto> cryos|work: The problem is that 4.0 was nowhere where they wanted it to be, so they've realized many things required changes -21:22 <@cryos|work> Yeah, I know... Mixing versions is always really tough to get right too. -21:22 <+reavertm> 4.3 is meant to be ABI compliany with 4.2 -21:23 <@scarabeus> ok how about removing prefix totaly -21:23 <@scarabeus> and have live/stable -21:23 * jmbsvicetto looks at bonsaikitten -21:23 <@scarabeus> so live apps are their own env -21:23 <@scarabeus> and the stable is /usr -21:23 * reavertm doesn't get it -21:23 <+reavertm> where does live go? -21:23 <@scarabeus> on the live note we can generate snapshots (weekly) -21:23 <@scarabeus> /usr/kde/live/ -21:24 <@scarabeus> everything live -21:24 <@bonsaikitten> jmbsvicetto: what! -21:24 <+reavertm> how is this different from current situation? -21:24 <@scarabeus> i still prefer your solution -21:24 <@jmbsvicetto> scarabeus: To be honest, I'm losing the "motivation" to keep hammering about kdeprefix, but that was the major issue I had to deal with when we started working back in KDE -21:24 <@scarabeus> reavertm: that there wont be kdeprefix anywhrere else than in live -21:24 <@jmbsvicetto> scarabeus: That's why I've resisted so long to dropping it -21:24 -!- ali_bush [n=alistair@gentoo/developer/alibush] has quit [Remote closed the connection] -21:24 <@scarabeus> jmbsvicetto: well reavers approach is working with +kdeprefix and keeping good usability -21:24 <@jmbsvicetto> bonsaikitten: Do you still care about kdeprefix or not? -21:25 <@scarabeus> trust me it is 500% better than current solution of mine -21:25 * cryos|work has also grown tired of the back and forth... Just want a reasonably stable env for users, and a solution for developers.... -21:25 <@alexxy> kdeprefix can be masked -21:25 <@jmbsvicetto> bonsaikitten: As I recall, you also felt it was important to have it and to allow users to mix versions -21:25 <+reavertm> well, it's not working yet :P -21:25 <@bonsaikitten> jmbsvicetto: my opinion hasn't changed since it was introduced -21:25 <@alexxy> so users who sant it will unmask it -21:25 <+reavertm> (plugins are not loaded properly - amarok issue) -21:25 <@alexxy> but its good fature to have more then one kde release installed -21:26 <@scarabeus> i would say lets see how it work and we can roll it out with 4.2.3 -21:26 <+reavertm> what's all with this masking kdeprefix? -21:26 <+reavertm> you can use.force it if you like :P -21:26 <@jmbsvicetto> cryos|work / bonsaikitten: So, what do you say about this? -21:26 <@scarabeus> i am for reavers solution -21:27 <@cryos|work> Honestly, I am no longer certain what is being proposed. I feel like we really need to pick a solution and try to stick with it. The Apache team went back and forth over a few years and drove many users away... -21:27 <@alexxy> reavertm's solutions better for misk packages -21:27 <+reavertm> my idea (if it works) is to be possible to have kdeprefixed releases and the rest in /usr (accessible from any kde installed) -21:27 <@jmbsvicetto> I guess I'll swallow kdeprefix at this time and will try to force me to look at the build system to allow the multiple versions / better split of packages -21:27 <@bonsaikitten> jmbsvicetto: I haven't followed the discussion enough to have useful input -21:28 <@jmbsvicetto> cryos|work / bonsaikitten: Then if you don't oppose, I say we try reavertm's approach -21:28 <@scarabeus> bonsaikitten: kdeprefix for kde-base, misc apps into /usr including live misc apps -21:28 <@bonsaikitten> sounds acceptable -21:28 <@bonsaikitten> as I haven't contributed anything relevant in a while I don't see why I should be the decider -21:28 <@scarabeus> ok majority already agreed -21:28 <+reavertm> well, there's nothing spectaculat to try now, if it works then we'll see - i need to handle this plugins paths 1st -21:29 <@cryos|work> I can live with it, I would rather be able to put misc live apps in /usr/kde/live too, but can likely hack the ebuilds I care about... -21:29 <@jmbsvicetto> cryos|work / bonsaikitten: If in the end we realize we lost some flexibility, that will only serve to foster the need to look for the real solution (imho) - fixing the build system -21:29 <@bonsaikitten> jmbsvicetto: acceptable :) -21:29 <@scarabeus> bonsaikitten: could you fix at least 258027 -21:29 <+reavertm> actually there's not a problem with restoring kdeprefix for misc apps, but -21:29 <@cryos|work> So you are going to try and mix multiple versions in /usr? -21:29 <+reavertm> live kde-misc would nee to have separate prefix :P -21:30 <@jmbsvicetto> cryos|work: I think that's the "final" solution -21:30 <@jmbsvicetto> cryos|work: I don't have any particular skill or knowledge to get it done, though -21:30 <@cryos|work> That sounds amazingly tough to pull off. -21:30 <@cryos|work> Not this solution though? -21:30 <+reavertm> ok, cryos|work what's your proposition? -21:30 <@bonsaikitten> scarabeus: oh ... let's see -21:31 <+krytzz> hm... would that allow to mix 4.2 kdelibs and live kde-misc stuff for example? -21:31 <+reavertm> maybe it apperas easier to handle than kde-misc in /usr -21:31 <@cryos|work> I don't have one, more trying to understand what this proposal is planning on changing. -21:31 <@jmbsvicetto> cryos|work: That solution isn't "compromised" for the current proposal -21:31 <@scarabeus> the current pospal is easing major bumps, lets stick with it for 4.3 and then we can think about updating the build system -21:31 * cryos|work was just trying to figure out if he understood what *this proposal* encompassed. -21:32 <+reavertm> ok, let me summarize -21:32 <+reavertm> the problem with kdeprefix for kde-misc apps is as follows : -21:33 <+reavertm> let's say we have taglib-extras -21:33 <+reavertm> it has optional kde integration -21:34 <@cryos|work> So you are concerned with corner cases? -21:34 <+reavertm> still it's just typical lib and should be accessed globally - it would be nice for it to not be kde-prefixed -21:34 <+reavertm> or any other app - like amarok - I want it installed and used from any KDE4 i have (and I have 4.2, 4.3, live) -21:34 <@cryos|work> I totally agree. I was the one who wanted to throw everything in /usr apart from development builds where people got to pick up the pieces themselves... -21:35 <@cryos|work> If I develop on amarok I can write a custom ebuild if I want it in my /usr/kde/live as any dev can, so the impact is not terrible. -21:35 <@cryos|work> I was more trying to confirm the scope of the changes proposed. -21:36 <@jmbsvicetto> reavertm: The only issue I see and the reason for the kdeprefix is if you have k3b-1.* working and want to follow k3b-2.* (which I think is still broken), you're not willing to have to choose between one or the other -21:36 <@jmbsvicetto> reavertm: But as stated, I'm going to drop my "resistance" -21:36 <+reavertm> k3b-1 will be installed in kde3 prefix so i am told -21:36 <+reavertm> (tampakrap?) -21:36 <@cryos|work> That was my concern, but those users could be out of luck... -21:36 <@cryos|work> At some stage having too much choice can spread us too thin. -21:37 <@cryos|work> Many distros are just dropping KDE 3 entirely already. -21:37 <@jmbsvicetto> cryos|work: yeah. The problem is that some users have been mailing us asking us not to do it -21:37 <@scarabeus> ok put it straight: lets just comfor for now on that we are going to support unprefixing misc apps -21:37 <@jmbsvicetto> cryos|work: And I think we haven't convinced everyone in the kde team that kde-4 is better -21:37 * jmbsvicetto looks at yngwin -21:37 <@cryos|work> I am not proposing we do - I am just pointing out what is happening. -21:38 <@jmbsvicetto> cryos|work: I agree -21:38 <@cryos|work> I think many distros dropped KDE 3 too soon. -21:38 <+reavertm> kdeprefix as great idea and flexibility it adds, it's pain in ass to mantain :P -21:39 <@cryos|work> I was more making the point that Gentoo has such an extreme amount of choice compared to other distros we could end up chasing bugs no-one else cares about that only crop up in slotted envs. -21:39 <+reavertm> (btw, eselect for kde is not required) -21:39 <@cryos|work> Reducing overall quality which is bad. Not claiming I have the answer either... ;-) -21:40 <@scarabeus> :] -21:40 <@jmbsvicetto> we're all brainstorming ;) -21:40 <@jmbsvicetto> tampakrap: How's your work on the kde3 eclasses going? -21:41 <@cryos|work> I am very attached to Gentoo and KDE. I don't want to see it go to crap, don't have as much time as I would like these days. -21:41 <@tampakrap> eclasses are ready -21:41 <@tampakrap> i'm still on the ebuilds -21:41 <@scarabeus> and the packages are compilling fine? -21:41 <@jmbsvicetto> tampakrap: kdeprefix isses on kde4 are hurting us, but colisions with kde3 apps are doing us more harm (imho) -21:41 <@cryos|work> Bumped avogadro for the super nerdy people who want to play though ;-) -21:41 <@tampakrap> i'll tell you what i need -21:41 <@tampakrap> if there are two people willing to test kde3 misc apps that would be greate -21:42 <@tampakrap> great -21:42 <@scarabeus> herd testers i bet -21:42 * wired raises hand -21:42 <@yngwin> evening -21:42 <@scarabeus> also write mail to desktop and dev -21:42 <+wired> yngwin: =] -21:42 <@jmbsvicetto> tampakrap: with kde4 env? -21:42 <@alexxy> cryos|work: i'll test it with students (avogadro) -21:42 <+reavertm> btw, masking kdeprefix is good idea for typical users -21:42 * yngwin completely forgot about the meeting, sry -21:42 <@tampakrap> i'll prepare a list with the packages and eapi2 as well them -21:42 <@jmbsvicetto> tampakrap: if so, I can do some tests -21:42 <@cryos|work> alexxy: Great - I fixed the desktop file among many other things... -21:42 <@tampakrap> i'm on kde-base only still -21:42 <@alexxy> reavertm: yep -21:43 <+reavertm> I guess it should be done when 4.2.2 is introduced -21:43 <@cryos|work> reavertm: That was always my point - typical users don't want/understand kdeprefix. If they do they will unmask and use. -21:43 <@alexxy> i think kdeprefix is not for users -21:43 <@alexxy> =) -21:43 <@cryos|work> It is awesome for devs/power users though. -21:43 <+wired> many users activate it without knowing though, mask++ -21:43 <+krytzz> hm... i thought gentoo is for powerusers? -21:43 <@jmbsvicetto> cryos|work: iirc, kdeprefix is no longer an IUSE default -21:44 <+reavertm> I want 4.2.2 stable in portage, so let make it easier for users to use -21:44 * yngwin is with krytzz -21:44 <@scarabeus> krytzz: you. sent. ssh key. me. now -21:44 <@cryos|work> jmbsvicetto: I didn't know it ever was. -21:44 <+reavertm> jmbsvicetto: yeah, but still users see USe flag and enable it out of curiosity :P -21:44 <+wired> krytzz: the definition of a poweruser is amazingly flexible these days.... -21:44 <+krytzz> scarabeus: ok, few minutes -21:44 <+krytzz> wired: ok well -21:44 <@scarabeus> cryos|work: YOU CHANGED IT TO ENABLED BY DEFAULT FIRST :D -21:44 <@scarabeus> heh caps -21:45 <@cryos|work> Many Gentoo users are not what I would call power users, but I guess by definition we have more advanced users than *buntu for example.. -21:45 <@cryos|work> scarabeus: For :live only! -21:45 <+wired> we also have a lot of users who'd want to be powerusers -21:45 <@alexxy> he he =) -21:45 <+wired> =] -21:45 <@yngwin> i'd say gentoo targets powerusers -21:46 <@yngwin> doesnt mean all our users are tho -21:46 <@jmbsvicetto> reavertm: well, that's the same thing as CFLAGS. Gentoo's policy has never been to hide it from the user - even if that leads to user bitting himself in the rear ;) -21:46 <+krytzz> wired: lol -21:46 <+reavertm> btw, our existing problems with kdeprefix *only* phonon and pykde -21:47 <@jmbsvicetto> reavertm: +affect? -21:47 <@scarabeus> ok back on topic tampakrap are you able to get needed stuff around here or you need our direct intervention (ak more devs searching for testing monkeys?) -21:47 <+reavertm> jmbsvicetto: hmm? -21:47 <@tampakrap> no just some testing mostly -21:48 <@tampakrap> i don't think we should waste more manpower on kde3 -21:48 * wired now that we're all here, can someone pretty please cp the latest .2 tbz2s to d.ge.o? -21:48 <@jmbsvicetto> reavertm: never mind -21:48 <+reavertm> ah, right - phonon and pykde4 - the only really kdeprefix *issue* -21:48 <+reavertm> the rest is just inconvenience -21:49 <@jmbsvicetto> reavertm: The phonon issue is mostly upstream "hard-coding" the plugins location, right? -21:49 <@scarabeus> ok so kde3 is moving forward, i would say that we need to have it done by end of april some time on may... so we can actualy stable the kde4 -21:49 <+reavertm> I can easily not drop kdeprefix and install 3rd party apps with kde they were built against (still changing need_kde behaviour) -21:50 -!- smith_ [n=smith_@adsl-62-167-36-86.adslplus.ch] has joined #gentoo-kde -21:50 <+reavertm> phonon issue is bunding KDE plugins with phonon -21:50 <@jmbsvicetto> scarabeus: we need to go for 3.5.10 stable *soon* -21:50 <@scarabeus> jmbsvicetto: btw i would like to mask the kde -21:50 <@scarabeus> jmbsvicetto: old nonsplit stuff i mean -21:50 <+reavertm> hence, phonon should be in location visihble by all KDE releases -21:50 <@jmbsvicetto> 3.5.9? -21:50 <+reavertm> or kdeprefixed -21:51 <@scarabeus> jmbsvicetto: yes -21:51 <@jmbsvicetto> scarabeus: Not without 3.5.10 stable! -21:51 -!- mikkoc [n=mikko@host254-81-dynamic.7-79-r.retail.telecomitalia.it] has quit [Read error: 60 (Operation timed out)] -21:51 <@jmbsvicetto> scarabeus: unless you're the one doing it and I can redirect all bugs, mails, threats, ... to you :P -21:51 <@yngwin> well, we can leave split 3.5.9 unmasked, and just mask the monolithic pkgs -21:52 <@jmbsvicetto> yngwin: we could, but we have quite vocal users already complaining about the drop of the monos for 3.5.10 -21:52 <+reavertm> or just put proper blocks -21:52 <@yngwin> then when 3.5.10 is stable, we can mask the rest -21:52 <@yngwin> jmbsvicetto: well, too bad, i'd say -21:52 -!- mikkoc [n=mikko@host182-164-dynamic.56-82-r.retail.telecomitalia.it] has joined #gentoo-kde -21:52 <@jmbsvicetto> ok -21:52 <@yngwin> or someone must stand up to become monolithic maintainer -21:53 <+reavertm> jmbsvicetto: who are those vocal users? -21:53 -!- anselmolsm_ [n=anselmo@200.184.118.130] has joined #gentoo-kde -21:53 <+reavertm> devs by occasion? -21:53 <@jmbsvicetto> reavertm: no -21:53 <+reavertm> idf so, let them step up to maintain :P -21:53 -!- anselmolsm [n=anselmo@200.184.118.130] has quit [Read error: 113 (No route to host)] -21:54 <@jmbsvicetto> reavertm: hehe, wait until you become a dev and you'll see how "demanding" some users can be ;) -21:54 <+reavertm> and what was basis for their objections? -21:54 -!- anselmolsm_ is now known as anselmolsm -21:55 <+reavertm> write migrating guide (if there's no already) and that's all. period -21:55 <@yngwin> we've had that for years -21:55 <@scarabeus> yeah i was speaking about the monos -21:55 <@jmbsvicetto> Some people just want monos. I haven't seen many and in particular good motives. But they want them, nonetheless -21:55 <+reavertm> Qt4 split was much more difficult yet it was done -21:55 <+reavertm> jmbsvicetto: I want reiser4 in gentoo-sources and? -21:55 <@jmbsvicetto> ok, ok -21:56 <+reavertm> some people want some things and they won't have it nevertheless :P -21:56 <@yngwin> use hitchhiker-sources then -21:56 <@jmbsvicetto> When they knock at my door I'll be sure to point them somewhere else ;) -21:56 * cryos|work has a meeting... Bye! -21:56 <+krytzz> bye -21:56 <@jmbsvicetto> bye cryos|work -21:56 <+reavertm> jmbsvicetto: let me brainwash them then -21:56 <+reavertm> bye cryos|work -21:56 <+wired> bye cryos|work -21:56 * cryos|work will try to contribute more this month! -21:56 <@jmbsvicetto> scarabeus: sorry for the disturbance. -21:57 <@jmbsvicetto> So, about kdeprefix we're done, right? -21:57 <@scarabeus> bb -21:57 <@scarabeus> yes -21:57 <@scarabeus> kde3 and kdeprefix is done -21:57 <@jmbsvicetto> about 3.5 tampakrap will do more tests and is searching for people to help with kde-misc apps -21:57 -!- mx-tvt [n=quassel@bl9-29-140.dsl.telepac.pt] has quit [Read error: 110 (Connection timed out)] -21:57 <+reavertm> I'll see what i can do - anyway i propose some my changes in eclass anyway as it's much shorter and easier to read now -21:57 <@jmbsvicetto> scarabeus: What's next? -21:58 <+reavertm> plasmoids to tree -21:58 <+reavertm> pros/cons :) -21:58 <@scarabeus> yeah i think we can start adding them -21:58 <@scarabeus> we cook them since pre 4.1 and still in the overaly -21:58 <@scarabeus> so lets make users happy -21:58 <+reavertm> I haven't tested all of them yet -21:58 <@jmbsvicetto> They're in kde-misc now, right? -21:59 <@scarabeus> i will add only those i personaly tested -21:59 <@yngwin> reavertm: that's what ~arch is for -21:59 <@yngwin> :p -21:59 <@scarabeus> jmbsvicetto: yes i did the move, actualy forced wire to move it -21:59 <+wired> i've tried them all at least once -21:59 <@jmbsvicetto> scarabeus: In that case I have nothing to say ;) -21:59 <+reavertm> anyway i already found one problem - systemmontor or sth has been moved to kdeplasma-addons and conflicts with kdeplasma-addons:live -21:59 <@scarabeus> ok i just want to hear OK :D -21:59 <+reavertm> about plasmoids -21:59 <+wired> most of them get regular updates btw and there are a lot more available in kde-look -21:59 <+reavertm> let me check them 1st -21:59 <@jmbsvicetto> reavertm: we can add a block on a slot package -22:00 <+reavertm> I fixed most deps in kde-misc but still something may be wrond there -22:00 <+wired> i think most plasmoids are simple enough to be safely added to ~ -22:00 <+reavertm> wired applied blocks already -22:00 <@scarabeus> ok this one was quick -22:00 <@scarabeus> so we just test them and start moving -22:00 <@scarabeus> :] -22:01 <@scarabeus> next is printing -22:01 <@scarabeus> reavertm: how is it looking -22:01 <+reavertm> printing.. -22:01 <@jmbsvicetto> scarabeus: what are we missing? The deps? -22:01 <@scarabeus> jmbsvicetto: we have everything -22:01 <@scarabeus> jmbsvicetto: the problem is it pulls half of gnome -22:01 <+reavertm> if I leave it as it is now - system-config-printer-kde is done, printer-applet not yet -22:01 <+reavertm> scarabeus: no longer -22:01 <@scarabeus> the better then -22:02 <@scarabeus> ok so i will coordinate it with you after 4.2.2 is released (weekend probably) -22:02 <@scarabeus> reavertm: agreed -22:02 <@scarabeus> ? -22:02 <+reavertm> just let me finish printer-applet the way I did system-config-printer-kde (taking some files from system-config-printer) and they can go -22:02 <+reavertm> scarabeus: yeah -22:03 <@scarabeus> ok cool then -22:03 <@scarabeus> jmbsvicetto: do we have any response on the snapshot thingie? -22:03 <+reavertm> I made system-config-printer-kde is totally independent from system-config-printer -22:03 <@jmbsvicetto> Not that I have seen -22:03 <@jmbsvicetto> scarabeus: I sent the mail 2 days ago, though. -22:03 <@alexxy> so they simply ignoring us -22:03 <@scarabeus> jmbsvicetto: ok so alexxy will have to do it himself for all the time -22:04 <@jmbsvicetto> scarabeus: I think as cryos|work was suggesting, we ignore them for now and keep doing the work alexxy is doing -22:04 <@scarabeus> alexxy: btw i heared some noise about l10n not working -22:04 <@alexxy> scarabeus: its working for -kdeprefix -22:04 <+reavertm> Dirk was in kde-devel for a minute -22:04 <@alexxy> didnt test it with +kdeprefix -22:04 <@alexxy> =) -22:04 -!- mkyral [n=maros@nezmar.jabbim.cz] has left #gentoo-kde [] -22:04 <@scarabeus> ok then it is their issue they can fix it -22:05 -!- sIbOk [i=sNOUbOR@56.Red-80-36-227.staticIP.rima-tde.net] has joined #gentoo-kde -22:05 <@scarabeus> jmbsvicetto: again one more on you -22:05 <@scarabeus> jmbsvicetto: how is dead member removing -22:05 <@scarabeus> going on -22:05 <@jmbsvicetto> I'm going to go over the retirement bugs (I think a few of them have already retired) and will then send mails to the folks that haven't been around for a long time -22:06 <@jmbsvicetto> I'll have the page cleaned by next meeting -22:06 <@scarabeus> ok -22:07 <@scarabeus> pykde -22:07 <@scarabeus> bonsaikitten: -22:07 <@scarabeus> so you say it works -22:07 <@scarabeus> despite the bugs in bugzilla -22:07 <@bonsaikitten> I haven't been able to reproduce -22:07 <+reavertm> problem with pykde4 is kdeprefix -22:07 <@bonsaikitten> I guess I'll need to change my testing strategy :) -22:07 <+reavertm> all kde installs pykde4 in site-packages -22:07 <@jmbsvicetto> reavertm: build or runtime error? -22:07 <@alexxy> so lets mask kdeprefix use flag -22:07 <@alexxy> =) -22:07 <+reavertm> install -22:07 <@alexxy> like it was for networkmanager -22:07 <+reavertm> so - two choices -22:07 <@scarabeus> there was sip buildtime errors -22:08 <+reavertm> make eselect module or slot them properly -22:08 <@jmbsvicetto> reavertm: I have pykde-4.2.1 installed with +kdeprefix here -22:08 -!- kamik [n=quassel@dslb-088-065-079-200.pools.arcor-ip.net] has joined #gentoo-kde -22:08 <+reavertm> so that pykde4 live will go to /usr/kde/live and so on -22:08 <+reavertm> jmbsvicetto: install pykde4-9999 as well -22:08 <+reavertm> you need package.provided entry now to do it -22:09 <@jmbsvicetto> reavertm: I'm not running live ebuilds here -22:09 <+reavertm> well, some people are :) -22:09 <@jmbsvicetto> sure, I'm just conveying my experience here -22:09 <@scarabeus> one +kdeprefix is ok -22:09 <@scarabeus> more than one kdeprefix is fail -22:09 <@scarabeus> for pykde -22:09 <@jmbsvicetto> ah, ok -22:10 <+reavertm> hell, it even install files in /usr/share/sip -22:10 <+reavertm> (apart from site-packages) -22:11 <+reavertm> bonsaikitten: some QA notice says that precompiled modules need to go to site-packages -22:11 <@bonsaikitten> :( -22:11 <+reavertm> is it possible to create external site packages in kde slot? (/usr/kde/4.2 etc) -22:12 <+reavertm> and set some PYTHON_PATH or whatever in startkde? -22:12 <@jmbsvicetto> This is why having multiple versions around in /usr is going to be "messy" :\ -22:13 <+reavertm> bonsaikitten: what useful python env variables do you know that would help here? :) -22:13 <@jmbsvicetto> reavertm: perhaps the correct solution here would be to remove the python files and have a single package that is used by all versions? -22:13 <+reavertm> that is also possible but... -22:14 <+reavertm> pykde4 happeds to install /usr/kde/live/lib64/kde4/kpythonpluginfactory.so -22:14 <+reavertm> which is in kdeprefixed location -22:14 <@jmbsvicetto> if they didn't break abi compatibility, it should be possible to use the latest pykde version with earlier 4.X releases -22:14 <+reavertm> installing it in /usr prefix is the same thing like installing kde-misc in /usr -22:15 <+reavertm> (may not work - like this plugin thing I'm struggling with) -22:16 <+reavertm> yes, I'm not worrying about linking, it should work - still ebuild would need some tweaks to make it build not agains kde release it is from but minimal installed -22:16 <@jmbsvicetto> reavertm: pkgconfig!! -22:16 <@scarabeus> he he he -22:16 <@scarabeus> again prefix you -22:16 <@scarabeus> SILENCE -22:16 <@scarabeus> :D -22:17 <+reavertm> what is pkgconfig going to solve? -22:17 <@alexxy> lets mask kdeprefix =) -22:17 <+reavertm> buildig is no longer an issue :P -22:17 <+reavertm> running is :) -22:17 <@jmbsvicetto> If they were using autotools they could use pkgconfig to chose the minimum so version needed -22:18 <+reavertm> jmbsvicetto: ah, eclass does it already -22:18 <+reavertm> (picks lowest kdelibs, yet >=KDE_MINIMAL) -22:18 <@scarabeus> ok i gues we are done with the pykde :P -22:18 <+reavertm> are we? -22:18 <@yngwin> hardmask? -22:18 <+reavertm> what's the solution then :P -22:18 <@scarabeus> yeah lets kitten handle it -22:19 <@scarabeus> also write whiny mail on dev -22:19 <+reavertm> I'd slot the f*er -22:19 <@jmbsvicetto> scarabeus: hehe - solution? hand it over to Patrick ;) -22:20 <+reavertm> along with phonon -22:20 <@scarabeus> jmbsvicetto: yup -22:20 -!- cypr1nus [n=cypr1nus@plus.ds14.agh.edu.pl] has quit [Read error: 104 (Connection reset by peer)] -22:20 <@scarabeus> (i am practising my "solid-rock" face) -22:20 <+reavertm> or ,If I get plugins in /usr to work, it will be solved -22:20 <@scarabeus> :] -22:21 <@scarabeus> so, um, what was next, ah, koffice2 -22:21 <@jmbsvicetto> reavertm: I haven't looked at that in a long time, but can't you specify more than 1 RPATH? -22:21 <@jmbsvicetto> reavertm: more than 1 dir in RPATH -22:21 <+reavertm> RPATH is not problem, they are all linked well, just app can't find those plugins -22:21 <@jmbsvicetto> isn't it supposed to look in the compiled RPATH? -22:22 <+reavertm> I am yet to check some things -22:22 <+reavertm> for plugins? no -22:22 <+reavertm> RPATh is just for linker -22:22 -!- neuron [n=neuron@85.252.65.217] has joined #gentoo-kde -22:23 -!- Civil [n=Civilian@95-24-156-60.broadband.corbina.ru] has quit [Remote closed the connection] -22:23 <+reavertm> if plugins are in /usr/kde/XXX/lib64/kde/ and /usr/kde/XXX/lib64/kde/plugins - app needs to know where to find them -22:24 <+reavertm> (usually just works if app was comopiled against kde XXX and istalled in /usr/kde/XXX -22:24 <+reavertm> otherwise it fails to find them even when KDEDIRS and QT_PLUGIN_PATh is pointed there -22:25 <+reavertm> yet I'm to test some things so we'll see - it should work somehow -22:25 -!- cypr1nus [n=cypr1nus@plus.ds14.agh.edu.pl] has joined #gentoo-kde -22:25 -!- looonger [n=looonger@host-89-231-128-7.rawamaz.mm.pl] has quit [Client Quit] -22:25 <+reavertm> I have manually compiled kdevelop in ~/kde4 and my KDEDIRS just points there and it workds -22:26 <+reavertm> so maybe it's something with building it gentoo way -22:26 <+reavertm> (I guess I'll try kdeprefix-less kdevelop...) -22:27 -!- _Phlogi [n=quassel@138-135.1-85.cust.bluewin.ch] has joined #gentoo-kde -22:27 <+reavertm> ok, what's next? -22:27 -!- non7top [n=non7top@94.77.134.21] has quit [Remote closed the connection] -22:27 <@scarabeus> koffice -22:28 <+reavertm> I built kword and it works -22:28 <@scarabeus> the state is i fixed the crap -22:28 <@scarabeus> it works -22:28 <@scarabeus> problem is that it is not much usable -22:28 <@scarabeus> they are going to release it at the end of this month -22:28 <@scarabeus> so i will add it to the tree -22:28 <+reavertm> 2.0? oh crap -22:28 <@scarabeus> but i am not sure if it should go masked or not -22:28 <@scarabeus> 2.0 indeed -22:29 <+krytzz> released? oh zomg :p -22:29 <@jmbsvicetto> scarabeus: maybe we should get an rc in the tree first, no? -22:29 <@scarabeus> jmbsvicetto: ideas? -22:29 <@scarabeus> well i have the tarball and it is just matter of renaming -22:29 <@scarabeus> anyone can do it -22:29 <@jmbsvicetto> scarabeus: the rc could be masked and pending bug reports, 2.0 would be unmasked or not -22:30 <@jmbsvicetto> The 2.0 tarball? -22:30 <+reavertm> btw, let someone just in any case look at those ebuilds and see whether deps are correct (rdepend, depend, commondepend handled carefully) -22:30 <@scarabeus> yeah i am worried about it and in doubts -22:30 <@scarabeus> it definetly is stable -22:31 <@scarabeus> but it lacks some features and it looks just ugly -22:31 <@tampakrap> i like the :live one though -22:31 <@tampakrap> haven't tested the releases -22:31 <@tampakrap> maybe we can create snapshots -22:32 <@scarabeus> what for -22:32 <@scarabeus> i have todays taged rc1 -22:32 <@scarabeus> :D -22:32 <@tampakrap> ok then -22:32 <+reavertm> KOffice 1.9.99.0 RC1 uploaded -22:32 <@scarabeus> not yet, it is on ktown :] -22:32 <+reavertm> just pasted announcement -22:32 <@scarabeus> jmbsvicetto: so what do you thing the stable at the end of the month as pure testing or hardmasked? -22:33 <@jmbsvicetto> I haven't used koffice myself, so I'm not sure -22:34 <@jmbsvicetto> But if you're in doubt, try pusing something masked into the tree and check for bug reports -22:34 <@scarabeus> ok -22:34 <@scarabeus> good idea -22:35 -!- Varox [n=Varox@p4FD44E52.dip.t-dialin.net] has joined #gentoo-kde -22:35 <@scarabeus> last thing on the list: -22:35 <@scarabeus> moving the meeting date -22:35 <@scarabeus> i would like to see meeting 14 days before upstream release for public -22:35 <@jmbsvicetto> pushing* -22:35 <@jmbsvicetto> scarabeus: releases what? ;) -22:36 <@tampakrap> we don't have much to talk before release i think -22:36 <@scarabeus> kde -22:36 <@scarabeus> we are kde team -22:36 <@tampakrap> after release is everything that comes in surface -22:36 -!- sIbOk [i=sNOUbOR@56.Red-80-36-227.staticIP.rima-tde.net] has quit ["kUALKIER hiJO dE pUTA sAbE lO q dARTE sI tIENE q dOLERTE pERO No kUALKIER hiJO dE pUTA sABE lO q dARTE sI tIENE q gUSTARTE, y] -22:37 -!- helch [n=helch@212-41-103-166.adsl.solnet.ch] has quit [Remote closed the connection] -22:38 <@scarabeus> hmm -22:38 <@scarabeus> what does other think? -22:39 <+krytzz> hm -22:39 -!- Phlogi [n=quassel@138-135.1-85.cust.bluewin.ch] has quit [Read error: 110 (Connection timed out)] -22:40 <+wired> maybe a week is enough? -22:40 <+krytzz> i would agree with tampakrap i think, but i have nothing against short-dated meetings -22:40 <@jmbsvicetto> scarabeus: floating schedule or point to 3rd Thursday of the month? -22:40 <@scarabeus> 3rd thursday i had on my mind -22:40 <+krytzz> when $PANIC_LEVEL reaches 10 would be good :p -22:41 <@scarabeus> well or 4th week -22:41 <@jmbsvicetto> krytzz: Isn't it too late by then? ;) -22:41 <@scarabeus> the problem is that release is today -22:41 <+krytzz> k... 9? :p -22:41 <@jmbsvicetto> scarabeus: 4th will hit council meetings -22:41 <@scarabeus> ok i will write to summary what ever you decide :] -22:42 <@jmbsvicetto> I think 3rd would be better, but am open to other dates -22:42 <@yngwin> 3rd sounds good -22:43 -!- MaNI [n=malcolm@dsl-247-169-66.telkomadsl.co.za] has joined #gentoo-kde -22:45 <@scarabeus> ok i go for 3rd too then -22:45 <@jmbsvicetto> So, what are we missing? -22:45 <@tampakrap> one last joke -22:45 <@tampakrap> hwoarang wants me to change my cloak to gentoo/slacker/tampakrap -22:46 <@scarabeus> hm and you could not write this yesterda -22:46 <+krytzz> hehe -22:47 <@alexxy> he he =) -22:47 -!- g1lt [n=quassel@203-79-94-158.cable.telstraclear.net] has joined #gentoo-kde -22:48 <@scarabeus> jmbsvicetto: http://dpaste.com/22343/ -22:48 <@scarabeus> jmbsvicetto: again no log, i didnt reboot my client yet :D -22:48 <@scarabeus> uptime 48 days cant be ruined :D -22:50 <@jmbsvicetto> hehe -22:50 <@jmbsvicetto> tampakrap: You have a long road to go before you qualify for that :P -22:50 <@jmbsvicetto> tampakrap: We have real "slacker" experts around here ;) -22:50 <@tampakrap> i don't think so, take a look at my cia.vc page -22:51 <@jmbsvicetto> So are we done? -22:51 <@tampakrap> yes, where is the summary? -22:51 * reavertm unpauses music -22:52 <@jmbsvicetto> In that case, let me remind people that we still have a *few* open bugs and that we should all try to help get that number down -22:52 <@scarabeus> tampakrap: http://dpaste.com/22343/ -22:52 <@scarabeus> yeah and ehm officaly meeting is over ;] diff --git a/meeting-logs/kde-project-meeting-log-20090521.txt b/meeting-logs/kde-project-meeting-log-20090521.txt deleted file mode 100644 index c66ea36..0000000 --- a/meeting-logs/kde-project-meeting-log-20090521.txt +++ /dev/null @@ -1,1769 +0,0 @@ -22:00 (@alexxy) !time -22:00 (Willikins) alexxy: Europe - Moscow - Thu May 21 23:00 MSD -22:00 (@alexxy) heh -22:00 (@scarabeus) roll-call slackers -22:00 (+wired) w000t -22:00 (@alexxy) time to start -22:00 (@scarabeus) !herd kde -22:00 (@alexxy) =) -22:00 (Willikins) (kde) alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, patrick, scarabeus, tampakrap, tgurr -22:00 (+wired) meh -22:00 (+wired) hopefully last meeting im not in that list -22:00 (dagger) huh -22:00 (+wired) :D -22:00 (@alexxy) time to start meeting -22:00 (nirbheek) hurr hurr -22:00 (@scarabeus) Time to start meting :D -22:00 (@alexxy) who is here? -22:00 -> tampakrap -22:00 (@hwoarang) wait! -22:00 (nirbheek) Time to start mating! -22:00 -!- Pesa [n=Pesa@bluemchen.kde.org] joins -> #gentoo-kde -22:00 (@hwoarang) !herd qt -22:00 (dagger) alexxy: I'm not here :) -22:00 (@hwoarang) ladies? -22:01 (dagger) hwoarang: lol -22:01 (Willikins) (qt) carlo, hwoarang, tampakrap, yngwin -22:01 (Gentle) is the libusb blocker ( http://dpaste.com/46414/ ) known? How to best avoid it? -22:01 (nirbheek) !herd gnome -22:01 (Willikins) (gnome) dang, eva, ford_prefect, leio, nirbheek, remi -22:01 (+wired) that list as well -22:01 (nirbheek) Low attendance, hmmm. -22:01 (@hwoarang) Pesa: dont hide , come over here -22:01 (+wired) nirbheek: lolz -22:01 (Pesa) i'm here, just in time :D -22:01 (@scarabeus) bonsaikitten: you too, are you around? -22:01 (@bonsaikitten) no, I'm a square -22:01 -!- mode/#gentoo-kde [+vvvv papillon81 Phlogi _Phlogi Civil] by scarabeus -22:01 (@alexxy) bonsaikitten: or you square today? -22:01 (@bonsaikitten) :) -22:01 (nirbheek) bonsaikitten, lrn2read vowels -22:02 (@scarabeus) :D -22:02 (nirbheek) So, wait, this is it? This is the meeting? -22:02 (@scarabeus) so we are missing few devs, and importantly our lead -22:02 (nirbheek) rollcall followed by silence? -22:02 (+krytzz) im a triforce -22:03 (cvandonderen) I want to join too! :-D:-P -22:03 (@alexxy) jmbsvicetto: !!!!! -22:03 (dagger) should I *stab* him? -22:03 (+wired) nirbheek: our meetings happen in brainwave levels :P -22:03 (@hwoarang) yngwin_: !! -22:03 (+wired) the leads are away -22:03 (@alexxy) Civil: ! -22:03 (@hwoarang) slacking leaders :D -22:03 (+wired) maybe they went out for beers -22:03 (+wired) :D -22:03 (@alexxy) mine beer is near me -22:03 (@alexxy) =) -22:04 (@hwoarang) +1 -22:04 (@scarabeus) mine too :] -22:04 (@scarabeus) ok -22:04 (+Civil) alexxy, ? -22:04 (@hwoarang) o_0 -22:04 (+wired) i see -22:04 (dagger) I've got tonic with me (no without gin) -22:04 (@yngwin_) present -22:04 (@hwoarang) !! YEY!! -22:04 (+wired) beer meeting this will be -22:04 -!- yngwin_ is now known as yngwin -22:04 (+wired) yngwin: :D -22:04 (spatz) for me? you shouldn't have :p -22:04 -> papillon81 is here -22:04 -> Civil is here -22:04 -!- hwoarang topic of #gentoo-kde ->> Gentoo KDE | meeting 21.5. 19:00 UTC | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU | Beer meeting in -22:04 (@hwoarang) stupid topic -22:04 -!- joost_op [n=joost@86.92.194.222] joins -> #gentoo-kde -22:04 (+wired) hwoarang: you fail it -22:05 -> nirbheek is here -22:05 (joost_op) evening -22:05 (@scarabeus) nirbheek: you want really to be listed on the roll-call? -22:05 -!- mode/#gentoo-kde [+v spatz] by yngwin -22:05 -> nirbheek does not know why he is here except maybe for espionage and sabotage -22:05 (@scarabeus) nirbheek: dont you fear other gnomies would burn you as witch -22:05 -> reavertm around -22:05 -!- mode/#gentoo-kde [+v Pesa] by yngwin -22:05 (nirbheek) scarabeus, they're too busy slacking :p -22:05 (@scarabeus) ok -22:05 (@scarabeus) i think better it wont get -22:05 (@scarabeus) most of us is here -22:05 (@hwoarang) :D -22:06 (+wired) yodabeus -22:06 (@scarabeus) :D -22:06 (@scarabeus) ok somebody must do the log -22:06 (+reavertm) nirbheek: we'll talk about some desktop file related stuff that touches gnome as well, so stay here :) -22:06 (@scarabeus) i still didnt find how todo it on quassel -22:06 (+wired) i'm logging -22:06 (@scarabeus) great -22:06 (@hwoarang) nice -22:06 (nirbheek) reavertm, kewl -22:06 (@scarabeus) so anyone has something to the topic list we have on the mail, or we should start right away with it? -22:07 (cvandonderen) scarabeus: you can just copy-paste it from the backlog -22:07 (@tampakrap) why not wait 10 minutes for others? -22:07 (@scarabeus) cvandonderen: not convinient -22:07 -> papillon81 has got no mail -22:07 (cvandonderen) scarabeus: we did it last time for a kde.org meeting ;-) -22:07 (@scarabeus) tampakrap: what others, only boss and cryos is missing -22:07 -!- Red_Devil [n=red@lounge.datux.nl] <- quit [Read error: 110 (Connection timed out)] -22:07 (@tampakrap) boss then -22:07 -> jokey enters spectator mode -22:08 (nirbheek) jokey, YESH -22:08 (nirbheek) I finally catch you -22:08 -!- _Phlogi [n=quassel@38-77.76-83.cust.bluewin.ch] <- quit [Read error: 110 (Connection timed out)] -22:08 (+reavertm) http://dpaste.com/46416/ - meeting agenda -22:08 (+papillon81) reavertm: thanks -22:08 (@scarabeus) http://archives.gentoo.org/gentoo-dev/msg_c5211b31c0fbff058bc767e3ac8ef077.xml -22:08 (@scarabeus) for those whom dont like pastebins -22:09 (@yngwin) scarabeus: carlo is missing too -22:09 -> lxnay sniffs packets from now -22:09 (@scarabeus) yngwin: he will be allways missing -22:09 (@yngwin) i know, but i consider this an offence -22:09 (@scarabeus) well he does not reply to mine mails either -22:10 (@scarabeus) ok i will write it to summary and let it to jorge to sort out :P -22:10 (@yngwin) yes please -22:10 (@hwoarang) no -22:10 (+reavertm) a'ka "removing dead members" ? -22:10 (@hwoarang) i ve talked to jorge before 2-3 days -22:10 (cvandonderen) I could do the kde4 guide.... -22:10 (@hwoarang) he said it is up to qt herd to deal with him -22:10 (@hwoarang) :) -22:10 (@yngwin) ok -22:10 (cvandonderen) I'm new to Gentoo, so I can do it based on experiences encontered -22:10 (@yngwin) i'll take care of it then -22:11 (@hwoarang) ok -22:11 -> cryos|work wife is having a baby in a few weeks - he may not be present for the next few meetings. Sorry! -22:11 -!- kdeR [n=wired@musici.static.otenet.gr] joins -> #gentoo-kde -22:11 (@hwoarang) o_0 -22:11 (@hwoarang) new developer :D -22:11 (@tampakrap) congratulations! -22:11 (@yngwin) good luck with that -22:11 (+krytzz) haha -22:11 (@scarabeus) cryos|work: wow, cool, enjoy the little slacker, be sure you wont be sleeping either :] -22:11 (@yngwin) :) -22:12 (+krytzz) yeah congratulations -22:12 (dagger) cryos|work: grats to you and your mrs dude :) -22:12 (@hwoarang) \o/ congrats cryos|work :) -22:12 (@cryos|work) Thanks - expecting lots of ups and downs over the next few months. Today has been hectic... -22:12 (@cryos|work) US time zone doesn't help me get here either... -22:12 (+wired) cryos|work: congrats =] -22:12 (@alexxy) he he =) congratulations cryos|work =) -22:13 (@jmbsvicetto) Hello -22:13 (jokey) new dev training++ -22:13 (dagger) yaay jmbsvicetto! -22:13 (+krytzz) yay chef -22:13 (+wired) jmbsvicetto: leader! -22:13 (@hwoarang) :) -22:13 (+wired) w00t -22:13 (@jmbsvicetto) Sorry guys, but I just sat down at work. I've been working up until now -22:13 (@hwoarang) no worries -22:13 (@hwoarang) i bet we are about to break a record today -22:13 (@scarabeus) jmbsvicetto: the network magic? :] -22:14 (lxnay) jmbsvicetto: helloes -22:14 (@scarabeus) ok i know we all can say hello for next 20 minutes, but lets get started :] -22:14 (@scarabeus) topic 1; doc handling -22:14 (@scarabeus) reavertm: anything changed on that subject? -22:14 (nirbheek) #gentoo-kde -22:15 (@scarabeus) and for specified packages with api-doc we will create new useflag -22:15 (nirbheek) mumble, mumble, what about packages that just rebuild the docs? -22:15 (nirbheek) And unconditionally install docs? -22:15 (@jmbsvicetto) cryos|work: congrats -22:15 (@scarabeus) nirbheek: we dont have such :] -22:16 (+reavertm) I support idea of leaving 'doc' for handbooks and introduce some other useflag when there's apidocs along with use documentation -22:16 (@cryos|work) Thanks jmbsvicetto :P -22:16 (@jmbsvicetto) scarabeus: getting ready for that -22:16 (@scarabeus) reavertm: so we agree on that :] -22:16 (nirbheek) scarabeus, but hypothetically, if you guys did, what would you do :p -22:16 (+krytzz) nirbheek slap upstream -22:16 (@jmbsvicetto) Hi everyone -22:16 (nirbheek) krytzz, difficult to slap entire gnome :p -22:16 (joost_op) right now compile kdelibs +doc results in a 268MB vs 48MB package -22:16 (nirbheek) jmbsvicetto, HELLO. -22:16 (@scarabeus) so what would be the apidoc useflag -22:17 (+reavertm) same for kdepimlibs -22:17 (@scarabeus) api-doc apidoc -22:17 (@scarabeus) anything else? -22:17 (@jmbsvicetto) reavertm: By default on Gentoo, user docs should be installed -22:17 (@scarabeus) suggestions ... -22:17 (cvandonderen) and will the apidoc useflag only be for kde, or Gentoo-wide? -22:17 (@scarabeus) jmbsvicetto: they are large -22:17 (@jmbsvicetto) reavertm: Only api / dev docs / examples should be conditional on use flags -22:17 (+reavertm) jmbsvicetto: hmm -22:17 (+wired) we could keep useflag for user docs but + it -22:17 (+reavertm) well, that's the way as well -22:18 (@scarabeus) sounds reasonable -22:18 (@scarabeus) +doc on kde-base -22:18 (@jmbsvicetto) scarabeus / reavertm: If they are large, they fit with the other docs - thus should depend on a use flag -22:18 (+reavertm) nirbheek: how do you have it on gnome? -22:18 (@jmbsvicetto) Gentoo does allow for exceptions ;) -22:18 (nirbheek) reavertm, we ignore the problem entirely =p -22:18 (+wired) lolz -22:18 (@scarabeus) jmbsvicetto: well then lets invent apidoc -22:18 (@jmbsvicetto) nirbheek: hehe -22:18 (@scarabeus) jmbsvicetto: docs are handled fine -22:18 (cvandonderen) and then make it kde-docs or something, because Java installs apidoc with doc too -22:18 (@scarabeus) but as joost said -22:18 (@scarabeus) 268 mb vs 48 mb -22:18 (@jmbsvicetto) scarabeus: what fills those 268MB ? -22:19 (nirbheek) docsdammitwhatelse -22:19 (@yngwin) maybe a discussion on dev ml is warranted, about global apidoc useflag -22:19 (@scarabeus) jmbsvicetto: api documentation -22:19 (@scarabeus) yngwin: i hate writing on -dev -22:19 (@scarabeus) yngwin: everything that is not anouncement turns to flame -22:19 (joost_op) for users having +doc in their make.conf, its not what they wanted -22:19 (lxnay) scarabeus: ;) true -22:19 (@yngwin) well, thats the official channel... -22:19 (+reavertm) if gentoo policy is to install docs by default, maybe we should drop 'doc' useflag for handbooks then -22:20 (+wired) scarabeus: it works if you just ignore flame[baits] -22:20 (nirbheek) scarabeus, ignore all replies is the solution -22:20 (@scarabeus) reavertm: now when it finaly works? ;] -22:20 -!- Devrethman [i=mpd@D-128-208-118-158.dhcp4.washington.edu] <- quit [Read error: 110 (Connection timed out)] -22:20 (@scarabeus) reavertm: i would go with +doc -22:20 (+wired) nah it should be optional, its gentoo -22:20 (+krytzz) me too scarabeus -22:20 (+spatz) if doc should be enabled by default then it should be done in the profile -22:20 (+wired) +doc sounds best -22:20 (@yngwin) no! -22:20 (+krytzz) why not -22:20 (@hwoarang) i dont like +doc -22:20 (+reavertm) not in profile -22:20 (@alexxy) heh ; to me seems better to use doc for user docs -22:20 (dagger) +doc sounds the best. If you want, you can disable it -22:20 (nirbheek) spatz, that results in too many circular deps -22:20 (@scarabeus) in kde-base packages -22:20 (@yngwin) not in profile -22:20 (+reavertm) better +doc per ebuild -22:20 (@scarabeus) yes per ebuild -22:21 (nirbheek) spatz, it's officially unsupported by Gentoo for global enabling -22:21 (@scarabeus) and the apidoc i will sum up some mail then -22:21 (@jmbsvicetto) scarabeus: But is it only api documentation or the handbook as well? -22:21 (+reavertm) jmbsvicetto: we need to distinguish them where they are both -22:21 (+reavertm) (like in kdelibs) -22:21 (@scarabeus) jmbsvicetto: +doc for documetnation only -22:21 (+reavertm) +doc whould be just for handbooks -22:21 (@scarabeus) jmbsvicetto: apidoc or sth for api doc -22:21 -> yngwin goes off to set -doc in make.conf -22:21 (@scarabeus) jmbsvicetto: where we ask on -dev for suggestions -22:22 (@scarabeus) yngwin: :D -22:22 (@yngwin) i can use internet thankyouverymuch -22:22 (dagger) yngwin: how about kde-base/* -doc :) -22:22 (@jmbsvicetto) ok, let me ask again. I'm not talking about use flags yet. I'm just trying to undestand what type of docs we have and an approximate size -22:22 -!- Enrico|ITA| [n=quassel@host86-47-dynamic.7-87-r.retail.telecomitalia.it] joins -> #gentoo-kde -22:22 (@yngwin) dagger: if only portage would support that -22:22 (@scarabeus) jmbsvicetto: the doc is 5-10megs -22:22 (@scarabeus) per package -22:22 (dagger) yngwin: ouch. I though it does -22:22 (@scarabeus) jmbsvicetto: apidoc is big crap -22:22 (@jmbsvicetto) yngwin: It does, if you change the order for inheritance ;) -22:23 (@yngwin) huh? -22:23 (joost_op) jmbsvicetto, it looks like right now on kdelibs with +doc it generates an insane size on the disc.. for no clear reason.. -22:23 (@jmbsvicetto) scarabeus: So 5-10MB for handbook and possible >100MB for the rest? -22:23 (@scarabeus) y -22:23 (@scarabeus) so growth in total about +500meg now -22:23 (@alexxy) ohh -22:23 (@alexxy) realy big -22:23 (dagger) that's quite extensive -22:23 -> scarabeus already has -doc in use -22:23 (@jmbsvicetto) yngwin: It's possible to affect the way portage treats the use flags - but I'll leave that for another time -22:24 (@yngwin) jmbsvicetto: we were talking about wildcard support -22:24 (@jmbsvicetto) Ah, sorry. I -meant you were talking about -* default use flags -22:24 (+reavertm) or rather per-category USE flags -22:24 (@jmbsvicetto) s/-meant/thought/ -22:25 (+reavertm) anyway, we're deviating a bit from the topic -22:25 (@scarabeus) bit -22:25 (@jmbsvicetto) scarabeus: In that case, let's talk about it in the dev ml -22:25 (@scarabeus) ok -22:25 (@scarabeus) i will sent that mail -22:25 (+reavertm) so we leave kdelibs alone for now or invent use flag for apidocs? -22:25 (@scarabeus) reavertm: first -dev -22:25 (@scarabeus) reavertm: then we will do whole thing -22:25 (@scarabeus) for now waiting on the mail -22:26 (+reavertm) it will take forever -22:26 (@jmbsvicetto) scarabeus: Personally I would suggest we install handbook by default (handbook use flag) and leave the doc use flag for the rest (disabled by default) -22:26 (@scarabeus) reavertm: i give them 7 days -22:26 (+reavertm) we can rename USE flag anytime -22:26 (+reavertm) (and play with it in overlay) -22:26 (@scarabeus) pple would tear us apart :D -22:26 (@scarabeus) if we move back to handbook D: -22:26 (+wired) lol -22:26 (+reavertm) pple can kill our asses - who does the work - decides -22:26 (@alexxy) he he =) -22:26 (@jmbsvicetto) scarabeus: +handbook for user docs ;) -22:26 (@alexxy) someone would forced to rebuild whole kde -22:26 (nirbheek) ouch -22:26 (joost_op) yeah it makes more sense.. -22:26 (+reavertm) jmbsvicetto: +handbook or +doc? -22:27 (joost_op) (o; -22:27 (@jmbsvicetto) My proposal would be +handbook for handbook and doc for the rest -22:27 (+wired) alexxy: doesn't portage profile/updates cover user flag changes? -22:27 (@scarabeus) --newuse -22:27 (+reavertm) (I'd like to rename +100 ebuilds and eclass) -22:27 (@jmbsvicetto) reavertm: meaning eapi docs -22:27 (@scarabeus) pple would hate us -22:27 (joost_op) since +doc right now generates the handbook -22:27 (+wired) use* -22:27 (@jmbsvicetto) s/eapi/api/ -22:27 (joost_op) keeping kdelibs out of it -22:27 (@alexxy) wired: no =) -22:27 (+reavertm) (i mena I woundn't lke to rename so many use flags...) -22:28 (@jmbsvicetto) We can do any changes in the use flags for 4.3 -22:28 (Kuja^) wired: it only handles package renames afaik -22:28 (+wired) meh -22:28 -!- BarbieGentoo-er is now known as Tina- -22:28 (@scarabeus) i agree with reaver, we need some test suicider who will do it, with apidoc we have 2 packages to change -22:28 -!- jmbsvicetto topic of #gentoo-kde ->> Gentoo KDE | meeting: Now | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU -22:29 (@scarabeus) with handbook we have to touch all -22:29 (@jmbsvicetto) scarabeus: The handbook should be dealt with in the eclasses, imo -22:29 (@scarabeus) jmbsvicetto: ok but it will be todo for 4.3 -22:29 (+reavertm) it's already dealt there, but ebuilds need to fixed as well -22:29 (@jmbsvicetto) scarabeus: that's my opinion -22:29 (@scarabeus) or 4.4 -22:29 (@scarabeus) :D -22:30 (@jmbsvicetto) scarabeus: But you don't have to agree with me ;) -22:30 (joost_op) i'd address it to 4.4 -22:30 (joost_op) but thats just my ho -22:30 (@scarabeus) well i am just lazy, cause it is annoying work -22:30 -!- ehustad [n=espen@ti511220a080-1003.bb.online.no] joins -> #gentoo-kde -22:30 (@scarabeus) go throught all ebuilds and manualy check them -22:30 (@scarabeus) there is 250 of them -22:30 (@scarabeus) and pple still commit to them -22:30 (@scarabeus) so merge failitures -22:30 (@scarabeus) AAGHR -22:30 (dagger) scarabeus: make it 40 each :) -22:31 -!- UT2K3 [n=UT2K3@one.lanrena.ilk.de] joins -> #gentoo-kde -22:31 -> lxnay can do annoying work -22:31 (@scarabeus) lxnay: you are realy willing to do it? -22:32 -> lxnay hides -22:32 (lxnay) ;) -22:32 (lxnay) well we can talk about it -22:32 (@scarabeus) as you wish -22:32 (joost_op) lxnay, hahaha leave it to scarabeus -22:32 (lxnay) but sure -22:32 (joost_op) we have enough todo -22:32 (lxnay) i can help out -22:32 -> joost_op grins -22:32 (@scarabeus) :] -22:32 (@scarabeus) :D -22:32 (+reavertm) I'd like to see how it's handled elsewhere 1st -22:32 (@scarabeus) reavertm: by elsewhere you mean? -22:33 (UT2K3) hi guys i upgraded to kde-4.3 and now the most icons are missing -22:33 (@jmbsvicetto) ok, so we'll use the dev ml to discuss the split between the documentation and the use flags for it. Anyone objects? -22:33 (@jmbsvicetto) UT2K3: We're in the middle of a meeting, please leave it for after the meeting -22:33 (UT2K3) ok -22:33 (lxnay) anything that falls into split attracts me, split and reign -22:34 (+reavertm) elsewhere, gnome (nirbheek by ignoring problem you mean installing everything provided by autoconf not caring whether docs are there or not?), openoffice, whatever -22:34 (nirbheek) reavertm, yeah, pretty much -22:34 (@scarabeus) reavertm: mostly they dont care -22:34 (nirbheek) the doc use-flag on gnome packages rebuilds the docs -22:34 (nirbheek) But even that's inconsistent for a few packages -22:35 (nirbheek) (some packages don't use gtk-doc) -22:35 (nirbheek) Oh, and these are api docs :p -22:35 (nirbheek) ls /usr/share/gtk-doc/html -22:35 (@jmbsvicetto) hmm, so do we want to move that discussion to the dev ml? -22:36 -> jmbsvicetto looks at the clock -22:36 (@scarabeus) jmbsvicetto: jup -22:36 (+reavertm) anyway if 'doc' is for developer documentation, we need new USE flag for handbooks -22:36 (@scarabeus) end of this topic :] -22:36 (@jmbsvicetto) ;) -22:36 (@jmbsvicetto) KDE3? -22:36 (@scarabeus) that was FUBAR -22:36 (@scarabeus) total one -22:36 (@scarabeus) when we moved it to the tree -22:36 (@scarabeus) many things broke -22:36 -!- jmbsvicetto topic of #gentoo-kde ->> Gentoo KDE | meeting: Now - KDE3 | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU -22:37 (@scarabeus) even now it is not finished -22:37 (@tampakrap) not exactly -22:37 (+Pesa) please try to avoid the gtk-doc mess ;) -22:37 (@tampakrap) we knew from the beginning that were was going to be a mess with kde3 misc apps -22:37 (@jmbsvicetto) Well, we also have gcc-4.4 and glibc-2.10 joining the *fun* -22:37 (Mirrakor) :) -22:37 (+reavertm) kde3, well, the state is kdelibs is hacked to replace some entries of .desktop files on the fly to make kde4 apps (even those from kdeprefix) distinguished (and runnable) -22:37 (+wired) btw kdelibs3 -r6 just failed on me -22:37 (+reavertm) but... -22:38 (+wired) probably due to glibc or gcc =] -22:38 -!- cvandonderen [n=casper@212-182-159-91.ip.telfort.nl] <- quit ["leaving"] -22:38 (+wired) kde3 session lists all -kdeprefix kde4 apps in menu now properly -22:38 (@jmbsvicetto) Just a quick point, I think we should open a tracker bug about gcc-4.4 and another about glibc-2.10 breakages with KDE apps -22:38 (@alexxy) yep =) i use gcc 4.4 and new glibc -22:38 (+reavertm) the problem is - not all kde4 executables want to work within kde3 (or any non kde4) session -22:39 (@scarabeus) reavertm: i think that pple will have to live with it -22:39 (+wired) reavertm: actually all kde4 apps i tested worked in kde3 session -22:39 (+wired) reavertm: always -kdeprefix -22:39 (@scarabeus) with +kdeprefix i know it is evil -22:39 (+reavertm) wired: install 4.2 in kdeprefix and live in kdeprefix as well (so you have two kde4 releases in kdepredfx) and install kde3 -22:39 (@scarabeus) but it wont work correctly so i think kde3 should not see it at all -22:39 (+wired) kdeprefix isn't supported atm -22:39 (+reavertm) troubles start there -22:40 (+wired) the patch doesn't even care -22:40 (@scarabeus) and we should focus on making the kde3 misc apps revbumped and stabled -22:40 (+reavertm) wired: looked at my patch? -22:40 (+reavertm) my patch does care :) -22:40 (@scarabeus) reavertm: i know you patched it, simple, just revert it -22:40 (+wired) haven't seen your patch -22:40 (+krytzz) i think who uses kde3 and kdeprefix doesnt deserve better :p -22:40 (+reavertm) well, it works with -kdeprefix as well -22:40 (@scarabeus) one +kdeprefix version never saw other +kdeprefix one -22:40 (@scarabeus) so... -22:40 -!- UT2K3 [n=UT2K3@one.lanrena.ilk.de] <- quit ["Bambus> frei nach dem motto: was ist besser als 14? 2 x 7 :o"] -22:40 (+wired) reavertm: does it work or not then? -22:40 (+reavertm) the point is - there's other approach -22:41 -!- ehustad_ [n=espen@ti511220a080-1003.bb.online.no] <- quit [Read error: 110 (Connection timed out)] -22:41 (+reavertm) wired: patch works, but just replacing those is not sufficient to run kde4 apps (kde 4.2 apps) within kde3 -22:41 (+wired) well no -22:41 (+reavertm) they try to load oxygen theme from live kde -22:41 (+wired) kde4 kdeprefix apps will need a wrapper script -22:41 (+reavertm) that's issue that needs to be resolved -22:41 (+wired) just as kde3 apps need kde3 wrapper script in kde4 -22:41 (+reavertm) that's stupid anyway -22:42 (+reavertm) let me check wrapper -22:42 (+papillon81) what is the main issue behind the kde3 topic that needs to be discussed here? -22:43 (+wired) having all stuff available in all menus -22:43 (+papillon81) k -22:43 (@tampakrap) ok apart from that -22:43 (+reavertm) wrapper doesn't fix this -22:43 (+reavertm) so anyway -22:43 (+reavertm) new idea is to modify .desktop files directly -22:43 (@tampakrap) i started opening stabilization bugs for various kde3 apps -22:44 (+reavertm) substitute paths with absolute ones, add suffixes to names to make it distinguished etc -22:44 (@tampakrap) i think monolithics can be masked and 3.5.10 can go to stabilization since 3.5.9 is dead -22:44 (@yngwin) ah that reminds me, are we deprecating arts as per bug 270575 ? -22:44 (Willikins) yngwin: https://bugs.gentoo.org/270575 "Dropping USE="arts" and USE="esd""; Gentoo Linux, Applications; NEW; ssuominen@g.o:qa@g.o -22:44 (+reavertm) i alrady started working on desktop-file-edit util (in desktop-file-utils, maybe it will be added there sometime) -22:44 (@scarabeus) we should -22:45 (@hwoarang) at last :) -22:45 (@yngwin) i think we can just remove arts support in 3.5.10 -22:45 (@scarabeus) yup that would be smart -22:45 (@tampakrap) can arts be safely disabled? it needs testing -22:45 (@scarabeus) remove arts support in 3.5.10 -22:45 (@yngwin) but we should check stable tree for packages requiring arts, if any -22:45 (@scarabeus) tampakrap: actualy more breakages is arts enabled -22:45 (+reavertm) nirbheek: you're not going to hack .desktop files loader in gnome to make kde4 apps (from multiple prefixes) not seen as duplicates? -22:45 (@scarabeus) tampakrap: it is more question, can we affort supporting arts -22:45 (+papillon81) lol -22:46 (@bonsaikitten) kill it with fire -22:46 (@bonsaikitten) then kill it again until it is dead -22:46 -!- gengor|lunch is now known as gengor -22:46 (+wired) lol -22:46 -> papillon81 has arts disabled since ages -22:46 (nirbheek) reavertm, why should they not be shown as duplicates? -22:47 (nirbheek) (I'm unfamliar with exactly how kde4 prefixes work) -22:47 (+reavertm) if you have kde4.2 in /usr/kde/4.2 and /usr/kde/live - you'll get two identical "Text editor" icons lanching same app -22:47 (+reavertm) (the one that is 1rst in PATH -22:48 (@yngwin) kde4 installs vim? -22:48 (@hwoarang) lol :P -22:48 (@yngwin) "text editor" ... -22:48 (+reavertm) kwrite -22:48 (nirbheek) reavertm, I'm confused, how can two paths in PATH cause duplicate .desktops? -22:48 (Enrico|ITA|) yngwin: kde4 rocks, vim rocks so they pull in each other :D -22:48 -!- jkt| [n=jkt@gentoo/developer/jkt] <- quit [Read error: 60 (Operation timed out)] -22:49 (@scarabeus) reavertm: i still think it is just wasting time -22:49 (@scarabeus) reavertm: just forget about some +kdeprefix -22:49 (@scarabeus) and problem is solved -22:49 (@scarabeus) really -22:49 (@scarabeus) we need it stable -22:49 (@scarabeus) for stabling kde4 -22:49 (@yngwin) yeah, dont make it more complicated than necessary -22:49 (@scarabeus) then it will be done in 7 months -22:49 (@scarabeus) s/done/gone -22:49 (+reavertm) then there's no point in exporting XDG_DATA_DIRS for kdeprefixed installs -22:49 (nirbheek) Oh, I see -22:49 (nirbheek) _that_ way -22:49 (@alexxy) scarabeus: thats why i suggest to mask kdeprefix from regular users -22:50 (@yngwin) i think once kde4 is in stable, there will be few kde3 users -22:50 (nirbheek) reavertm, yes, plz2don't export prefixed installs (except for default prefix?) -22:50 (+papillon81) also think about the issue with networkmanager-applet concerning different paths -22:50 (@scarabeus) papillon81: later later -22:50 (@scarabeus) now we are on kde3 -22:50 (@scarabeus) :] -22:50 (+reavertm) but it can be done :P -22:50 (@scarabeus) reavertm: can and must are 2 things -22:50 (@scarabeus) reavertm: and we have other things we need to have done -22:50 (@scarabeus) which are actualy more important than this -22:51 (+wired) if user has kdeprefix -22:51 (nirbheek) You guys have too much time and manpower :p -22:51 (+wired) we should just export -22:51 (@scarabeus) if user has kdeprefix, we dont bother with kde3 -22:51 (+wired) the ... higehr version one maybe? -22:51 -!- Sho_ [n=EHS1@kde/hein] <- quit [Read error: 104 (Connection reset by peer)] -22:51 (+wired) in XDG_DATA_DIRS -22:51 (+reavertm) there is a bug already - "kde4 apps not shown in gnome" or whatever -22:51 -!- Sho_ [n=EHS1@kde/hein] joins -> #gentoo-kde -22:51 (@scarabeus) reavertm: yep that is other thing, and that can be handled by, newest ap win -22:51 (+reavertm) (or the other way around?) -22:52 (@scarabeus) kde4 apps in gnome -22:52 (+wired) if user has -kdeprefix installed, only that one shows in other DEs, if he has only +kdeprefix then grab newer version (or stabler, whatever) -22:52 (@scarabeus) yep -22:52 (@scarabeus) but dont bother with it on kde3 -22:52 (@jmbsvicetto) tampakrap: we can't mask 3.5.9 monos until we get 3.5.10 marked stable -22:52 (@hwoarang) afaik there was another situation that kde3 apps didnt show on kde4 session -22:52 (+reavertm) what you have just written - how exactly are you going to implement? -22:53 (+reavertm) espeically "if he has only +kdeprefix then grab newer version (or stabler, whatever)" part -22:53 (@jmbsvicetto) tampakrap: That would cause issues for stable users -22:54 (+wired) reavertm: check in /etc/env.d/... ? -22:55 (@scarabeus) ok for kde3 i have two things -22:55 (@scarabeus) - kill arts, all misc apps needs it removed and be stabled before 3.5.10 stabling -22:55 (@scarabeus) - stable 3.5.10, all kde related misc apps needs to be revbumped/verbumped and stabled before it -22:55 (@scarabeus) anything to this -22:55 (@alexxy) jmbsvicetto: thats why i think its better to mask kdeprefix use flag to not confuse stable users at all -22:55 -!- jkt| [n=jkt@basa.flaska.net] joins -> #gentoo-kde -22:55 (@tampakrap) kde3 misc apps is up to me -22:55 (+reavertm) making kdeprefix is differnt topic :) -22:55 (@yngwin) i'd agree with masking kdeprefix useflag -22:55 (+wired) actually i agree with alexxy it should be masked -22:56 (+krytzz) me too ^^ -22:56 (@jmbsvicetto) alexxy: Unmasking a use flag is not something we should ask our users to do -22:56 (@scarabeus) reavertm: i think we will talk about it on the bug -22:56 (@tampakrap) i want someone to stable 3.5.10, i don't know the procedure for a list of packages -22:56 (@jmbsvicetto) alexxy: We already have it disabled by default -22:56 (+wired) too many users use +kdeprefix without knowing wth it is -22:56 (+wired) ohhh look shiny use flag -22:56 (@alexxy) jmbsvicetto: kdeprefix is topper to make kde 4.2 stabel -22:56 (@hwoarang) wired is right actually :) -22:56 (@scarabeus) jmbsvicetto: i dont mind having unmasked kdeprefix, when the kdeprefix issues are fixed -22:56 (@alexxy) jmbsvicetto: users can think that they want to have kde in /usr/kde/ and use kdeprefix -22:56 (@scarabeus) and users install it "by accident" -22:57 (@jmbsvicetto) wired: Gentoo is not a distro for "not smart" users -22:57 (+wired) jmbsvicetto: im with you 100% -22:57 (+wired) the users aint -22:57 (@jmbsvicetto) wired: We don't want to become Ubuntu ;) -22:57 (@alexxy) but it will cause troubles if they hav kde3 for example -22:57 (nirbheek) jmbsvicetto, Hey, you just Godwinned the conversation :p -22:57 (@yngwin) ok, maybe add an ewarn then -22:57 (+wired) there seems to be some general confusion regarding it -22:57 (+wired) maybe it needs to be documented better -22:57 -!- _Phlogi [n=quassel@168-18.77-83.cust.bluewin.ch] joins -> #gentoo-kde -22:57 (+reavertm) great, then I need volunteer to fix one bug - the one with picking live oxygen by kde 4.2 apps (both installed in kdeprefix) -22:58 (+reavertm) after that - I can call kdeprefix supported -22:58 (+reavertm) volunteers? -22:58 (+reavertm) if no - mask kdeprefix :P -22:58 (joost_op) we will have -kdeprefix in our next branch for sure -22:58 -!- bschindler [n=quassel@77-56-156-71.dclient.hispeed.ch] joins -> #gentoo-kde -22:58 (@jmbsvicetto) Let's improve our docs and make it *very* clear that users shouldn't enable kdeprefix unless they're ready to assume the support for their install -22:58 (joost_op) if it helps -22:58 (@scarabeus) jmbsvicetto: also evarn is not bad idea -22:58 (@scarabeus) ewarn -22:58 (@jmbsvicetto) No problem with that -22:58 (+wired) jmbsvicetto++ -22:58 (@scarabeus) something like I_KNOW_WHAT_I_AM_DOING variable -22:59 (+wired) and ewarn should be there as well -22:59 -!- Eythan [n=Eythan@AMontpellier-552-1-118-57.w86-197.abo.wanadoo.fr] <- quit ["Leaving"] -22:59 (+krytzz) yeah this one is great -22:59 (nirbheek) Why not just globally use.mask it? -22:59 (@jmbsvicetto) Although you all know just how much ewarns users tend to pay attention to -22:59 (nirbheek) People who want to use it can enable it -22:59 (@jmbsvicetto) scarabeus: no -22:59 (@yngwin) not another variable, then it'd be better just to mask the useflag -22:59 (+wired) also many users think kdeprefix is needed for kde3/kde4, we need to tell them thats no longer the case -22:59 (+reavertm) what's wrong with masking it until kdeprefix issues are fixed? -22:59 (dagger) nirbheek: global use.mask should be for stuff which is know to be broken. -23:00 (+reavertm) actually kdeprefix IS KNOWN to be broken :P -23:00 (@scarabeus) jmbsvicetto: i mean like live warning is handled -23:00 (@yngwin) well, it *is* known to break things -23:00 (nirbheek) dagger, isn't this known to be broken? :p -23:00 (@jmbsvicetto) reavertm: I use it here :P -23:00 (@scarabeus) jmbsvicetto: i just expresed myself poorly -23:00 (@scarabeus) jmbsvicetto: broken ktorrent.. -23:00 (+reavertm) it is broken when used with non-kde4 sessions . period -23:00 (dagger) is it broken for all installs? If you just use one kde (4.2) and no other version? -23:00 (@jmbsvicetto) scarabeus: I don't think we should require users to set a new use flag or to have to digg how to unmask use flags -23:00 (@scarabeus) jmbsvicetto: broken misc plasmoids... -23:00 (@scarabeus) jmbsvicetto: no useflag -23:00 (@alexxy) reavertm: if its known to be broken then it should be masked by default -23:00 (@alexxy) from regular users -23:01 (@scarabeus) jmbsvicetto: like the warning it is doing in live -23:01 (@jmbsvicetto) reavertm: You're talking about mixing kde versions or using other DEs -23:01 (nirbheek) dagger, then it's of no use, right? (if you only have one) -23:01 (@alexxy) people who want to play with it smart enough to unmask it -23:01 (+reavertm) both -23:01 (+reavertm) using other DEs with multiple KDE4's installed -23:01 (dagger) nirbheek: but I might like to have it in /usr/kde/4.2 location -23:02 (+reavertm) jmbsvicetto: ^ -23:02 -!- mode/#gentoo-kde [+v Kuja^] by scarabeus -23:02 (nirbheek) dagger, then why not make it default? :p -23:02 (dagger) use.mask unmasking is not documented and should not be used really -23:02 (nirbheek) kdeprefix is not documented, and should noe be used really (unless you know what you're doing) -23:02 (@tampakrap) kdeprefix is documented -23:02 (+reavertm) what else. use.force? -23:03 (+reavertm) (and it be overriden in /etc somewhere?) -23:03 -!- ELITE_x [n=quassel@quassel/user/elite] <- quit [Remote closed the connection] -23:03 (nirbheek) tampakrap, yeah, and my code is documented ;p -23:03 (@scarabeus) ok you guys are way of topic :} -23:03 (@scarabeus) we are suposed to talk about kde3 -23:04 (@scarabeus) so for now we have revbumping all misc packages and removing arts -23:04 (@jmbsvicetto) So let's focus again on KDE3 -23:04 (@scarabeus) anything else onto that topic? -23:04 (@tampakrap) yes -23:04 (@tampakrap) let me talk for a minute -23:04 (@yngwin) well, this kdeprefix mess should be decided before stabling 3.5.10 -23:04 (@jmbsvicetto) scarabeus: I don't think it's worthy to worry about arts, but if those working on KDE3 want to drop it now, I don't have a problem with it -23:04 (@scarabeus) jmbsvicetto: it is not working, again ton of bugs open -23:04 (@tampakrap) the original idea behind hacking kde3 eclasses was to have mostly a kde4 session with kde3 apps working -23:04 (@scarabeus) jmbsvicetto: so if we kill it we smash bugs -23:05 (@jmbsvicetto) scarabeus: well, it isn't a regression ;) -23:05 (@tampakrap) especially those that aren't still ready for kde4 -23:05 (@alexxy) kde3 works perfectly without arts -23:05 (@alexxy) =) -23:05 (@tampakrap) this issue is fixed, if wired and reavertm want to play more it is their issue, the stabilizattion can be proceeded normally -23:05 (@tampakrap) and i'm going to document it -23:05 (@tampakrap) objections? -23:05 (+reavertm) nope -23:06 (+reavertm) we can add some blocker anytime -23:06 (+reavertm) (if needed) -23:06 (@tampakrap) also -23:06 (@jmbsvicetto) tampakrap: I agree with that -23:06 (@yngwin) as long as kdeprefix is properly documented -23:06 (@tampakrap) the mess created in kde misc apps was expected, so nothing is fucked -23:06 (wilder_) hiall, qt-4.5.1 in portage does not contain http://websvn.kde.org/trunk/qt-copy/patches/0279-svg-rendering-regression.diff -23:06 (@tampakrap) we new from the beginning that most of them should be rebuilt to work and i am trying to revbump and stabilize the most popular ones -23:07 (@tampakrap) and close random bugs -23:07 (wilder_) ? -23:07 (@jmbsvicetto) tampakrap: At this point, I think we should have 2 goals with KDE3: working environment to those still resisting KDE4 and working KDE3 apps inside a KDE4 session -23:07 (@hwoarang) wilder_: it does. but we have a meeting now -23:07 (+krytzz) wilder_ please later, we are in a meeting currently -23:07 (@tampakrap) jmbsvicetto: both those work -23:07 (@scarabeus) so we can stable -23:07 (@scarabeus) goodie -23:07 (wilder_) sry -23:07 (+krytzz) np -23:07 (@jmbsvicetto) tampakrap: right, but we should be explicit that is what we'll support for KDE3 -23:08 (@jmbsvicetto) tampakrap: So people know what we're doing and what we're willing to support -23:08 (@tampakrap) i can document that -23:08 (+reavertm) if we disable XDG_DATA_DIRS for kdeprefixed kde4's - current kdelibs patch is sufficient -23:08 (+reavertm) (for kde3) -23:08 (@tampakrap) and also propose things to users so as to have a fully working kde4 env -23:09 (+reavertm) so only remaining issue is to fix kde4 session (kdelibs .desktop files loader) the same way as kdelibs3 one -23:09 (+reavertm) (I can do it) -23:09 (@tampakrap) not a major one but feel free -23:09 (@jmbsvicetto) I also propose we make it clear that upstream stopped working on KDE almost 1 year ago and doesn't show much concern about it anymore -23:09 (+reavertm) (a'ka fixing kde3 apps in kde4) -23:09 (@tampakrap) the major issue is to have them working, i don't care much if they aren't listed in kmenu :) -23:09 (@jmbsvicetto) So people worried about security should start thinking about upgrading -23:10 (+wired) actually them showing up is important -23:10 (@tampakrap) ok i'll prepare a new document about kde3 and kde3/4 -23:10 (@jmbsvicetto) That's another reason we need to press for KDE4 going stable -23:10 (+wired) so that patch reavertm is talking about is needed -23:10 (+reavertm) tampakrap: it will make them work - they need no special care apart from appending fullpath to executable -23:10 -!- pgega [n=pgega@tonbridgesecpay.force9.co.uk] <- quit [Remote closed the connection] -23:10 -!- Phlogi [n=quassel@24-167.77-83.cust.bluewin.ch] <- quit [Read error: 110 (Connection timed out)] -23:10 (@tampakrap) reavertm: feel free to do it no problem by me -23:11 (@scarabeus) ok i would say important things about kde3 are done -23:11 (@scarabeus) what is next... -23:11 (@scarabeus) KDE 4.3 -23:11 (@jmbsvicetto) tampakrap: So, should we try to define a timeline for 3.5.10? -23:11 (@scarabeus) oh -23:11 (@jmbsvicetto) scarabeus: just one sec -23:11 (@scarabeus) deadline? -23:11 (@tampakrap) what deadline? i can open the bug even now, the things i wanted to work are ready -23:12 (@tampakrap) i don't know from the open bugs view if this is possible -23:12 (@jmbsvicetto) ok -23:12 (@scarabeus) ok so lets say 15.6 is last day when we cc archies? -23:12 (@tampakrap) ok we have the kde3 thing settled -23:12 (@jmbsvicetto) So we'll open a stabilization bug for 3.5.10 asap? -23:13 (@tampakrap) yes ok -23:13 (@jmbsvicetto) Good :) -23:13 (@tampakrap) scarabeus: paste the summary so everyone can see it -23:13 -!- jmbsvicetto topic of #gentoo-kde ->> Gentoo KDE | meeting: Now - KDE4.3 | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU -23:13 (@hwoarang) http://archives.gentoo.org/gentoo-dev/msg_c5211b31c0fbff058bc767e3ac8ef077.xml -23:13 (@scarabeus) tampakrap: it is mess -23:13 (@scarabeus) tampakrap: i need to polish it later -23:13 (@scarabeus) dont worry summary will be -23:13 (@tampakrap) ok -23:13 (@tampakrap) next topic -23:13 (@scarabeus) libknotification is done -23:13 (+krytzz) ok for 4.3, i dont know for sure but i think the libnotification stuff is being merged into kdelibs later -23:13 (@scarabeus) it is pdepend in kdelibs -23:14 (@scarabeus) it will be merged in 4.4 -23:14 (+krytzz) ah ok -23:14 (@scarabeus) so for now it is best solution -23:14 (@scarabeus) also i dont get upstream -23:14 (@scarabeus) seriously -23:14 (@scarabeus) the lib is needed in half core packages -23:14 (@scarabeus) and they didnt add it -23:14 (@scarabeus) insane -23:14 (+wired) yes well -23:14 (@alexxy) yep -23:14 -> jmbsvicetto whistles -23:14 (+wired) at first they had it in extra gear -23:14 (+reavertm) abi/api changes probably -23:14 (+wired) LOLZ -23:14 (+wired) :p -23:14 (+reavertm) they wanted to workaround feature freeze :P -23:14 (+reavertm) simly -23:15 (+reavertm) so they invented "experimental" thing -23:15 (@alexxy) ohh -23:15 (@scarabeus) ok -23:15 (@scarabeus) what else we have for kde4.3 -23:15 (@alexxy) some additional deps -23:15 (@alexxy) like wicd -23:15 (@tampakrap) kopete will have facebook support :) -23:15 (+reavertm) and phonon -23:15 (@hwoarang) LOOOOLZ -23:15 (@alexxy) yep -23:16 (@alexxy) also non released phonon as dep -23:16 (+krytzz) well virtuoso isnt stable as trueg wrote -23:16 (@scarabeus) krytzz: it is not mandatory for 4.3 -23:16 (@scarabeus) :} -23:16 (+reavertm) or maybe we pull mplayer with mplayerthumbs? -23:16 (+reavertm) (it's pretty heavy dep) -23:16 (dagger) what's the status of policykit with 4.3? Do we need some extra docs? -23:16 (+krytzz) yes -23:16 (@scarabeus) ah -23:16 (@scarabeus) docs -23:16 (+krytzz) reavertm how do other package handle such deps? -23:16 (@scarabeus) definetly -23:16 (@alexxy) well -23:16 (+reavertm) (that's why I opted for making phonon snapshot evem if I use mplayer myself) -23:17 (@alexxy) policy kit used to control some privilegies like suspend/resume -23:17 (+reavertm) krytzz: you mean other distros? -23:17 (@yngwin) when is kde going to use qt's phonon? -23:17 (+reavertm) or whether it's compatible? -23:17 (+krytzz) reavertm no, i mean other packages who just call another binary -23:17 (@scarabeus) yngwin: hopefully with 4.6 -23:17 (+reavertm) yngwin: for us? never -23:17 (@scarabeus) yngwin: but we can just hope -23:17 (@yngwin) ok -23:17 (+reavertm) unless we package xine backend separately -23:18 -!- Pesa [n=Pesa@bluemchen.kde.org] <- leaves #gentoo-kde [] -23:18 (+reavertm) (btw, policykit panel crashes in kde trunk, anyone can confirm?) -23:18 (@scarabeus) reavertm: ok we will ship phonon snapshot -23:18 (@hwoarang) is this possible? does it worth the pain? -23:19 (@scarabeus) hwoarang: worth it is -23:19 (@scarabeus) because we wont have the blocker bugs -23:19 (+reavertm) pain it is not -23:19 (@hwoarang) ok then this sounds great ! -23:19 -!- Pesa [n=Pesa@bluemchen.kde.org] joins -> #gentoo-kde -23:19 (@alexxy) reavertm: in 4.2.87 it works -23:19 (@scarabeus) ok what state is the policykit anyway -23:19 (@scarabeus) is it usable -23:19 (@scarabeus) does it work? -23:19 (@scarabeus) is there something neede -23:19 (@scarabeus) d -23:19 (@scarabeus) (i am quite scared about it) -23:20 (@alexxy) scarabeus: polkit works -23:20 (+reavertm) krytzz: I haven't understood, sorry -23:20 (@alexxy) and its needed for some actions like suspend resume -23:20 (dagger) alexxy: isn't it controled by hal's policykit settings? -23:20 (@scarabeus) if it works then ok -23:20 (@alexxy) dagger: not sure -23:20 (+krytzz) reavertm hm forget it :p i think i missed something -23:21 (+reavertm) (in kubuntu thet did it well btw) -23:21 (@jmbsvicetto) scarabeus: about the blocks, I think we should add a kde use flag for qtscriptgenerator/qt-qt3support so that we can solve the phonon blocks. I talked about that in the bug -23:21 (@tampakrap) kde4 use flag -23:21 (@yngwin) we'll come to that -23:21 (dagger) jmbsvicetto: good point -23:21 (+reavertm) what about adding virtual for phonon? -23:21 (@scarabeus) ok so we will ship phonon snapshot in main tree -23:21 (@alexxy) ahh yes use flags -23:21 (@scarabeus) any objections -23:21 (@alexxy) =) -23:22 (@scarabeus) and i think virtual is better than useflag -23:22 (@hwoarang) +1 ^^ -23:22 (@yngwin) why? -23:22 (@scarabeus) it should work -23:22 (+reavertm) phonon in qt 4.5.1 is the same version as media-sound/phonon in tree -23:22 (@scarabeus) and we dont have to polute the qt ebuilds -23:22 (@jmbsvicetto) bug 270188 -23:22 (+reavertm) (just with no-go backend - gstreamer) -23:22 (Willikins) jmbsvicetto: https://bugs.gentoo.org/270188 "qt-phonon / phonon + phonon-kde block"; Gentoo Linux, Applications; REOP; jannisf@gmail.com:kde@g.o -23:23 (+reavertm) those blocks are mostly portage bugs btw -23:23 (@yngwin) yes -23:23 (@yngwin) well, if kde wants a virtual, i suppose that would work -23:23 (@scarabeus) yngwin: well i thinked about you -23:23 (@jmbsvicetto) hmm, how will the virtual solve the isue? -23:23 (@scarabeus) i dont mind poluting qt ebuilds -23:23 (@jmbsvicetto) issue* -23:23 (@scarabeus) but isnt virtual better for maintaining? -23:24 (+reavertm) || deps will be removed from ebuilds -23:24 (@jmbsvicetto) The virtual will have to prefer one implementation over the other - which one will we prefer? -23:24 -!- marco_ [n=marco@95.222.93.133] <- quit [Remote closed the connection] -23:24 (@scarabeus) media one -23:24 (+reavertm) || ( qt-phonon phonon ) deps -23:24 (@scarabeus) cause it is phonon + xine -23:24 (@jmbsvicetto) scarabeus: I don't think qt will want that -23:24 (+wired) i agree with jmbsvicetto, kde use sounds better -23:24 (@scarabeus) ok then we have to separate the xine -23:24 (@scarabeus) srsly i dont mind -23:24 (@scarabeus) so make it work :] -23:24 (@yngwin) we wont use the virtual if qt-phonon is 2nd choice -23:24 (@jmbsvicetto) scarabeus: Otherwise, we could just revert the deps on the qt ebuilds -23:25 -> hwoarang lost contact -23:25 (+reavertm) separating xine needs to be done anyway iho -23:25 (@hwoarang) qt-phonon+xine sounds better -23:25 (@hwoarang) n? -23:25 (@hwoarang) *no? -23:25 (@yngwin) that sounds like a better solution -23:25 (+reavertm) make it possible -23:25 (@jmbsvicetto) reavertm: What we really need to do is to force xine to qt upstream ;) -23:25 (@hwoarang) you cant -23:25 (+reavertm) xine is evil GPL -23:25 (+reavertm) no can do -23:26 (@jmbsvicetto) right, *evil* -23:26 (@yngwin) lol -23:26 (@scarabeus) ok so snapshot and spliting -23:26 (@hwoarang) the thing is, is it possible to ship xine separately? -23:26 (@scarabeus) the useflag i guess is ok -23:26 (@hwoarang) good -23:26 (+reavertm) hwoarang: shoud be possible -23:26 (@scarabeus) so lets use it for now -23:26 (@scarabeus) and later we just drop media-sound/phonon -23:26 (@scarabeus) problem solved -23:27 (@yngwin) hwoarang: you ok with USE=kde in qt ebuilds to prefer media-sound/phonon over qt-phonon? -23:27 (+reavertm) (what about -9999? live phonon frm qt is not really live phonon - media-sound/phonon-9999 will need to stay - virtual can come into play) -23:27 (@hwoarang) i dont mind -23:28 (+reavertm) hwoarang: and you need to strip gstreamer from qt-phonon as well -23:28 (@yngwin) ok -23:28 (@hwoarang) in case we have kde? -23:28 -!- d00p [n=d00p@srv3.nutime.de] joins -> #gentoo-kde -23:28 (@hwoarang) kde? -> media-sound/phonon and strip gstreamer? -23:28 -> hwoarang lost contact again :S -23:28 (+reavertm) xine and gstreamer backends could be split from media-sound/phonon -23:28 (@hwoarang) ok -23:29 (@jmbsvicetto) yngwin: can we have "kde? ( || ( media-sound/phonon x11-libs/qt-phonon )) !kde? ( || ( x11-libs/qt-phono media-sound/phonon ))" ? -23:29 (@yngwin) we can work out the details later -23:29 (@hwoarang) reavertm: so we ll use the split packages and strip the gstreamer from qt-phonon -23:29 (+reavertm) imho - qt-phonon should provide just phonon library - no platorm sound library -23:29 (@scarabeus) details later plz -23:29 (@hwoarang) ok -23:29 (+reavertm) ok -23:29 (@scarabeus) anything else for kde4.3 -23:29 (@scarabeus) this release seems fine -23:29 (@jmbsvicetto) That way we can add a dep on kde4 eclasses for x11-libs/qt-qt3support[kde] -23:29 (@scarabeus) if we have nothing else -23:29 (+reavertm) yeah, it's b0rked! -23:29 (@scarabeus) borked by upstream -23:30 (@scarabeus) but if there is something from our side -23:30 -!- helch [n=helch@212-41-73-167.adsl.solnet.ch] joins -> #gentoo-kde -23:30 (+reavertm) (bth, it's misusing kde USE flag - better something related to phonon, not kde) -23:30 (@tampakrap) phonon use flag? -23:30 (@hwoarang) we can work on that -23:31 (@hwoarang) kde4 sounds better to me . or kde -23:31 (@yngwin) kde it is -23:31 (@hwoarang) ok move on -23:31 (@jmbsvicetto) hwoarang: As we're talking about kde-4.3, let's spend a few minutes talking about the use flags -23:31 (+reavertm) kde, kde4? -23:31 (@hwoarang) as you wish :) -23:32 (@jmbsvicetto) hwoarang: We should drop the KDE4 use flag now and instead use KDE and KDE3 use flags -23:32 (@tampakrap) kde->kde3 and kde4->kde4 and we can document that too -23:32 (+reavertm) I expreessed my opition on -desktop ml -23:32 (@hwoarang) that discussion took place ages ago -23:32 (@tampakrap) why change the kde use flag? it is already used by kde3 -23:32 (@hwoarang) :/ i m not sure if we reached on some solution -23:32 (@jmbsvicetto) The KDE use flag should give users the best working version at each point in time - that means it should give users KDE4 now -23:32 (@scarabeus) kde = latest kde, for now kde4 -23:32 (@scarabeus) kde3 = kde 3.5 -23:32 (@yngwin) kde useflag means highest available version that is relevant to the package -23:33 (@jmbsvicetto) not exactly the latest. As long as a version is experimental, it makes sense to have one use flag for it -23:33 (@scarabeus) what i write -23:33 (+reavertm) I don't like idea of self-'migrating' USE flag -23:33 (@tampakrap) and what about kgtk for example that supports both? -23:33 (@scarabeus) reavertm: gtk2 gtk1 was pain -23:33 (+reavertm) "now we consider kde as KDE4, later it will be KDE5) -23:33 (@scarabeus) trust me self migrating is better -23:33 (dagger) jmbsvicetto: wouldn't it be less ambiguous to keep kde3 and kde4, so people will _always_ know what potential deps it might have/ -23:33 (@jmbsvicetto) reavertm: that's how it should be, imo -23:33 (+reavertm) dagger: my point -23:34 (@scarabeus) their issue -23:34 (@jmbsvicetto) dagger / reavertm: One can check the local use flags -23:34 (@scarabeus) they can track our anouncement -23:34 (@scarabeus) we have news -23:34 (@scarabeus) so we can sent it to their machine quite obviously -23:34 (@jmbsvicetto) That's why we can now have local descriptions to make clear what each flag does -23:34 (+reavertm) ok, what about compiz? -23:34 (dagger) jmbsvicetto: what if we suddenly change kde flag to old kde4. That will cause problems for users -23:35 (+reavertm) kde3 and kde USE flags? -23:35 (@jmbsvicetto) reavertm: I'll fix that one -23:35 (+reavertm) what about 'kde' meaning "general KDE support" -23:35 (@jmbsvicetto) reavertm: I haven't spend as much time with it as I would like -23:35 (+reavertm) what the heck is that? -23:35 (@scarabeus) dagger: nothing -23:35 (dagger) I really believe we shoudn't have kde and kde3, just kde4 and kde3. That way it's simple for people -23:35 (@scarabeus) they just read anoucnement -23:36 -!- Weaselweb [n=quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409] <- quit [Read error: 104 (Connection reset by peer)] -23:36 (dagger) scarabeus: do you read announcements? Most people don't -23:36 (@scarabeus) their problem -23:36 (@scarabeus) really -23:36 (@scarabeus) i read them -23:36 (@yngwin) indeed -23:36 (+reavertm) jmbsvicetto: I mean, there's choice to build against kdelibs:3.5 and kdelibs4 - it needs to be distinguished -23:36 (@hwoarang) wtf -23:36 (@jmbsvicetto) dagger: That way everyone will have to update their use flags to migrate between versions - I don't think that makes any sense -23:36 (@hwoarang) stop carying about lazy users -23:36 (+papillon81) scarabeus is right. kde should always refer to the latest version -23:36 (@jmbsvicetto) reavertm: yes, I know. I'll keep the 2 use flags, but they're going to become kde3 and kde -23:36 -!- pip_ [n=pip@e179240053.adsl.alicedsl.de] <- quit [Read error: 110 (Connection timed out)] -23:36 (dagger) jmbsvicetto: they will have to modify use flags anyway migrating from 3 to 4, as most use flags are different anyway -23:37 (@yngwin) most users will want/assume support for latest version -23:37 (+reavertm) "general KDE support" means compiling against some kdelibs -23:37 (@jmbsvicetto) dagger: that's a different thing, but kde will mean adding support for KDE -23:37 (+reavertm) there's no "general" kdelibs - it's particular kdelibs that will be pulled -23:37 (dagger) I don't want to wonder - what version might it be today ... and what will it be tommorow - and I'm pretty sure users don't want it as well -23:38 (@yngwin) it's pretty straightforward -23:38 (+reavertm) that being said = "support for KDE" is not clear enough -23:38 -!- LXj [n=lx@ip211-94.telenet.dn.ua] <- quit [Read error: 110 (Connection timed out)] -23:38 -!- wohnout [n=wohnout@kolej-mk-60.zcu.cz] joins -> #gentoo-kde -23:38 (+reavertm) stable users have kde 3.5 and support for kde means support for THEIR kde -23:38 (dagger) no it's not streaightforward. Some will assume - most recent, some will assume stable, some other wont have idea -23:38 (+wired) well one valid alternative would be to just ditch kde and keep kde3 and kde4 -23:38 (+reavertm) for me kde treacking latest kde in portage is no go -23:38 (+reavertm) never -23:39 (dagger) if we change kde to kde3 - we screw stable users and emerge -DN -23:39 (@yngwin) it's been that way for a long time, and for good reasons -23:39 -!- The_Ball [n=The_Ball@d58-106-136-240.sbr4.nsw.optusnet.com.au] joins -> #gentoo-kde -23:39 (dagger) unless you want to do the change when kde4 goes stable -23:39 (+reavertm) yes, my recommendation is to drop 'kde' and keep only 'kde3', 'kde4' and so on -23:39 (@yngwin) dagger: we dont need to change -23:40 (dagger) yngwin: I'm lost than. I thought kde will suppose to be for kde 4 -23:40 (@jmbsvicetto) dagger: I think you're missing an important point - the kde use flag is relevant for misc apps, not for base kde -23:40 (+spatz) will be symmetric with 'qt3', 'qt4', which makes sense to many people -23:40 (@tampakrap) can we vote? options: kde3-kde4 and kde-kde3 -23:40 (@scarabeus) ok -23:40 (@scarabeus) lets have vote -23:40 -!- thansen [n=thansen@c-76-27-110-194.hsd1.ut.comcast.net] joins -> #gentoo-kde -23:40 (@alexxy) reavertm: +1 -23:40 (+Civil) kde3-kde4 -23:40 (@tampakrap) i vote kde3-kde4 -23:40 (dagger) kde3-kde4 -23:40 (@yngwin) kde means kde support -23:40 (+krytzz) kde3-kde4 -23:40 (+wired) do we vote or dev-only? =] -23:40 (@scarabeus) on this only devs please -23:40 (@scarabeus) and use 1 2 -23:40 (+krytzz) oh :p sorry ignore mine -23:41 (@scarabeus) 1 for kde3-kde4 -23:41 (@scarabeus) 2 for kde3-kde -23:41 (@hwoarang) 2 -23:41 (@tampakrap) 1 -23:41 (@yngwin) 2 -23:41 (@alexxy) 1 -23:41 (@scarabeus) 1 -23:41 (@jmbsvicetto) 2 -23:41 (dagger) 1 -23:41 (@scarabeus) erm 2 -23:41 (@jmbsvicetto) scarabeus: I think you messe your vote ;) -23:41 (@scarabeus) i mean 2 -23:41 (@scarabeus) :D -23:41 (@scarabeus) idiot -23:41 (@jmbsvicetto) messed* -23:41 (@scarabeus) yup -23:41 (@yngwin) you pulled a ssuominen -23:41 (@scarabeus) 2222222 -23:41 (@scarabeus) i wont change it -23:42 (@alexxy) no!!!!!! -23:42 (@hwoarang) 2 it is :P -23:42 (@scarabeus) i just wanted to mark kde3-kde as one ; then i read it above -23:42 (dagger) scarabeus: lies! -23:42 (Viedzmin) ave \m/ -23:42 (dagger) scarabeus: ;) -23:42 (@scarabeus) ;[ -23:42 (@scarabeus) ;] -23:42 (@yngwin) so we stay with current practice -23:42 (@jmbsvicetto) ok, so let's move forward -23:42 (@scarabeus) yep -23:42 (@scarabeus) CODE -23:42 (@tampakrap) wait -23:42 -!- doobry [n=quassel@host86-169-175-149.range86-169.btcentralplus.com] <- quit [Read error: 104 (Connection reset by peer)] -23:42 (@yngwin) yes -23:43 (@tampakrap) who will do the change? -23:43 (@tampakrap) :) -23:43 (@yngwin) what change? -23:43 (@hwoarang) you -23:43 (@scarabeus) when you smile so much -23:43 (@scarabeus) guess twice -23:43 (+reavertm) thos who voted that is -23:43 (dagger) scarabeus: can you please explain magic CODE -23:43 (@scarabeus) dagger: you dont get something in it? -23:43 (@scarabeus) then ask -23:43 (@scarabeus) ok what code is -23:43 (@tampakrap) people wait the last topic isn't finished -23:43 (@scarabeus) it is list of things all kde team packages should comply -23:43 (dagger) scarabeus: I have no idea what " - enforcing CODE requirements everywhere" is about -23:43 (+reavertm) look at CODE file in Documentation -23:43 (@tampakrap) we need to grep the tree and change the flags who will do it??????????? -23:44 (@yngwin) tampakrap: NO NEED -23:44 (+reavertm) it's work in progress -23:44 -!- The_Ball1 [n=The_Ball@d58-106-26-133.sbr2.nsw.optusnet.com.au] joins -> #gentoo-kde -23:44 (@scarabeus) http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/CODE -23:44 (@yngwin) only when there is a choice between kde 3 and 4 support do you need to specify USE=kde3 -23:44 (dagger) scarabeus: ok, now I get you -23:44 (@jmbsvicetto) tampakrap: That needs only to be done for latest versions of misc packages that work with KDE4 -23:45 -!- termite47384 [n=me@cpe-066-057-082-106.nc.res.rr.com] <- quit [Read error: 60 (Operation timed out)] -23:45 -!- LXj [n=lx@ip211-94.telenet.dn.ua] joins -> #gentoo-kde -23:45 (+reavertm) ok, so CODE is set of commit policies/guides in overlay basically -23:46 (@scarabeus) in overlay and in tree too -23:46 (+reavertm) maybe some ebuild workflow will be recommended there as well -23:46 (@scarabeus) yup i want everyone to look on it and write some suggestions there and we will merge it -23:46 (+krytzz) repoman plugin for the CODE :p -23:46 (@scarabeus) krytzz: :D -23:46 (@hwoarang) lazy ppl -23:47 (@hwoarang) you can write a quick draft for kde ebuilds, just like i did for qt4 based ebuilds -23:47 (+reavertm) will be there -23:47 (+reavertm) as well as templates for blocks, etc -23:47 (+reavertm) anyway - one rule -23:47 (@yngwin) btw, i want $PN in commit messages for qting-edge as well -23:48 (@hwoarang) hm? -23:48 (+reavertm) everyone should respect them :) -23:48 (@jmbsvicetto) scarabeus: If we have a CODE file, I might add a few suggestions about ebuilds (the ones reavertm noted some time ago) -23:48 (@scarabeus) yep this one is draft -23:49 (@scarabeus) althrought i enforce it as-is -23:49 (@scarabeus) so please improve it -23:49 (@hwoarang) yngwin: what? you want a template for qting-edge commits? -23:49 (@scarabeus) and in next meeting it will be enabled as hard-forced -23:49 (@scarabeus) and we should punish not folowing it -23:49 -!- Red_Devil [n=red@lounge.datux.nl] joins -> #gentoo-kde -23:49 (@scarabeus) i know annoying, but reduces time needed for maintaining -23:49 (@hwoarang) indeed -23:49 (@yngwin) hwoarang: yes please start commit msg with $PN -23:50 -!- Red_Devil is now known as Guest36992 -23:50 (@hwoarang) thats sad. I really enjoyed funny commit messages -23:50 (@hwoarang) :D -23:50 (@yngwin) i dont mind funny :) -23:50 (@hwoarang) ok hold on -23:50 (+reavertm) ok, anything else? next? -23:50 (@yngwin) but i do want to see what pkg is affected -23:50 (@hwoarang) !herd qt && Pesa && spatz -23:50 (+wired) lol-cat/pn -23:50 (@hwoarang) ^^ -23:50 (@hwoarang) && wired -23:51 (Pesa) hwoarang: i'm here -23:51 -!- mode/#gentoo-kde [+vv Pesa spatz] by scarabeus -23:51 (+wired) hwoarang: seriously, we read it already -23:51 (+wired) :D -23:51 (@hwoarang) did you see what we said about commit messages? -23:51 -!- The_Ball_ [n=The_Ball@d58-106-141-118.sbr4.nsw.optusnet.com.au] <- quit [Read error: 110 (Connection timed out)] -23:51 (+spatz) yep -23:51 (@hwoarang) you did -23:51 (@hwoarang) ok -23:51 (+Pesa) yes -23:52 (@hwoarang) anything else about CODE kde ppl? -23:52 (@scarabeus) ok -23:52 (@scarabeus) code done -23:52 (@scarabeus) if noone has anything else -23:52 (Willikins) hwoarang: incorrect usage, ask for help using 'Willikins: help herd' -23:52 (+wired) lolz -23:52 (@hwoarang) yes baby whatever -23:52 (@scarabeus) next new pple in team etc/etc... -23:52 (@scarabeus) so if you move your eyes to voiced pple -23:53 (@hwoarang) we have plenty of them :P -23:53 (@scarabeus) those are our not-yet deved/herdtested resources -23:53 (@jmbsvicetto) hmmm, we're at around half of the agenda and we're hitting the 2 hour mark -23:53 (+wired) who did you call a resource!!! :D -23:53 (@yngwin) wired has finished quizzes, now it's up to recruiters -23:53 (@hwoarang) this meeting will last forever! -23:53 (@scarabeus) jmbsvicetto: too much spam about kde3 -23:53 (+krytzz) 1/4 if you add the qt stuff jmbsvicetto :p -23:53 (@hwoarang) \o/ -23:53 (@scarabeus) most is done -23:53 (+reavertm) jmbsvicetto: you know - it's merithorical meeting, not just fluff talk! :) -23:53 (@scarabeus) jmbsvicetto: kdeprefix is done -23:53 (@scarabeus) and so on -23:54 (@yngwin) i'm interjecting qt recruits now -23:54 (@scarabeus) ok so if you pple want to mentor someone -23:54 (+reavertm) scarabeus: I'd have some idea -23:54 (@scarabeus) or vice versa, if someone has urge became dev fast :D -23:54 (@scarabeus) reavertm: you dont count, you have resistance to becaming dev, althrought i dunno why ;D -23:54 (+reavertm) even if we have quite many HT's and contributors, I still feel we're understaffed in terms of tracking uptream patches -23:54 (@yngwin) Pesa has been very active with Qt already, and spatz is our newest recruit -23:55 (@hwoarang) \o/ -23:55 (+wired) woot -23:55 (@yngwin) they both are on their way to devhood -23:55 (+spatz) :D -23:55 (+Pesa) ;) -23:55 (@yngwin) there is another one, sping, not here now, he will join us after finishing GSoC -23:55 (@tampakrap) and me :D -23:55 (@hwoarang) we are growing fast -23:55 (@hwoarang) be carefeull -23:55 (@scarabeus) for kde team i would like krytzz and papillon81 to work on their ebuild quiz, cause you two are progressing :] -23:55 (+papillon81) scarabeus: i have the quiz ready :-) -23:55 (@scarabeus) great -23:56 (@scarabeus) papillon81: sent it by mail, and we will discuss the meeting about it -23:56 (+wired) yngwin: btw when should I expect a response? :) -23:56 (@scarabeus) later :} -23:56 (@hwoarang) soon wired -23:56 (+krytzz) i cant devote enough time currently to do serious stuff -23:56 (@yngwin) tampakrap: you may hear from sping (sebastian) as he is interested in qt3/kde3 maintenance -23:56 (@yngwin) wired: usually within a few days -23:56 (+reavertm) btw, what about 'assigning' some herd packages to particulat people? -23:57 (+reavertm) for example one would take kdepim, someone else kdebindings -23:57 (@tampakrap) not kde-base/* only extra packages -23:57 (@scarabeus) reavertm: it needs interest -23:57 (+reavertm) this way work is somewhat split -23:57 -!- mikkoc [n=mikko@host116-78-dynamic.17-79-r.retail.telecomitalia.it] <- quit [Remote closed the connection] -23:57 (+papillon81) scarabeus: it's mostly ready but already lying around for a year or so. will have to look over it -23:57 (+wired) yngwin: thnx -23:57 (@scarabeus) papillon81: no prob :} -23:57 (+reavertm) scarabeus: of course... unfortunately -23:58 (@scarabeus) ok i think that is all i wanted about recruits -23:58 (@jmbsvicetto) reavertm: That's against the spirit of herds -23:58 (@scarabeus) i wanted you to see them -23:58 (@scarabeus) and also whom is progressing i contacted -23:58 (@jmbsvicetto) reavertm: But nothing prevents one from adding himself to a package belonging to one of the herds -23:58 -!- dagger [n=dagger@gentoo/developer/dagger] <- leaves #gentoo-kde ["http://quassel-irc.org - Chat comfortably. Anywhere."] -23:58 -!- dagger [n=dagger@gentoo/developer/dagger] joins -> #gentoo-kde -23:58 -!- mode/#gentoo-kde [+o dagger] by ChanServ -23:58 (@scarabeus) anything else upon recruits? -23:58 (@scarabeus) anyone? -23:59 -!- The_Ball [n=The_Ball@d58-106-136-240.sbr4.nsw.optusnet.com.au] <- quit [Read error: 110 (Connection timed out)] -23:59 (@scarabeus) jokey: are you here? -23:59 (+reavertm) jmbsvicetto: I'm not talking about beaurocracy (adding to metadata) but real maintenance (periodically looking for some bugs in kde.org) -23:59 (+reavertm) or we can just rely on b.g.o -23:59 (@scarabeus) we are good at handling new bugs -23:59 (@scarabeus) really -23:59 (@jmbsvicetto) reavertm: Well, people can focus on particular areas ---- Day changed Fri May 22 2009 -00:00 (jokey) scarabeus: yep -00:00 (@jmbsvicetto) About bugs, we need to start paying extra attention to security bugs -00:00 (@scarabeus) jokey: so, what i need to do to be able to add pple to our git overlay -00:00 (@scarabeus) jokey: i can do for sunrise, so what is needed to be done for kde team ones -00:00 (@jmbsvicetto) you need to poke him :P -00:00 (@scarabeus) i know -00:00 (@jmbsvicetto) or rbu or robbat2 -00:00 (@scarabeus) directly i mean -00:00 (jokey) need to mess with robin, I'll poke you back -00:00 (@scarabeus) rbu cant touch git -00:00 (@jmbsvicetto) scarabeus: he can -00:01 (@dagger) scarabeus: he can -00:01 (@scarabeus) jokey: this workflow is unflexible :] -00:01 (@scarabeus) dagger: good update :] -00:01 (@scarabeus) okey i will handle this with jokey internaly then :] -00:01 (@scarabeus) the next topic is our guide -00:01 (@scarabeus) kde4 one -00:01 (@scarabeus) it neeeds update/cleanup -00:01 (@scarabeus) who will do it -00:01 (+reavertm) "handling cmake relwithdebuginfo compilation to please upstream..." ? -00:01 (jokey) internally? oO teh sekrit -00:02 (joost_op) guys can the sabayon point on the agenda be discussed at later time -00:02 (@jmbsvicetto) joost_op: hehe -00:02 (@scarabeus) reavertm: deffered -00:02 (@scarabeus) reavertm: thought about it -00:02 (@scarabeus) reavertm: not worth -00:02 (+krytzz) what?? -00:02 (+reavertm) yeah, agreed -00:02 (+papillon81) goooood -00:02 (@scarabeus) jokey: definetly -00:02 (@scarabeus) ;] -00:03 (joost_op) jmbsvicetto, i think it can be talked about off the record anyway -00:03 (@scarabeus) so the guide -00:03 (+krytzz) ok then lets discuss this later scarabeus -00:03 (@scarabeus) who -00:03 (@tampakrap) wait -00:03 (@tampakrap) about the guide -00:03 (@tampakrap) would you like a kde3/4 monolithic one? -00:03 (@jmbsvicetto) joost_op: sorry, that was meant for jokey -00:03 -!- pgega [n=pgega@77-99-66-168.cable.ubr01.tonb.blueyonder.co.uk] joins -> #gentoo-kde -00:04 (joost_op) oh -00:04 (@yngwin) tampakrap: i think it makes sense, with kde4 going to go stable -00:04 (@tampakrap) stating how to install kde4, how to install live/snapshots and how to install 3.5, and how we can mix them -00:04 (@tampakrap) i'll do the guide -00:04 (@tampakrap) agreed with the mixed guide? -00:05 (joost_op) scarabeus, let me know the outcome of the dicussion -00:05 (@tampakrap) boss? devs? hts? -00:05 (joost_op) if any -00:05 (@scarabeus) tampakrap: agreed -00:05 (@scarabeus) so quiet... -00:05 (@jmbsvicetto) tampakrap: Perhaps we could have a new doc that points to specific guides about KDE4 and KDE3 -00:05 (@scarabeus) what happend -00:05 -!- AntiXpucT [n=Skim@77.106.108.232] <- quit [] -00:06 (@jmbsvicetto) tampakrap: That doc would just focus on the integratio of 3 and 4 -00:06 (@yngwin) scarabeus: more beer, less talk ;) -00:06 (@hwoarang) lolz -00:06 (@jmbsvicetto) yngwin: I need to have some fun with work network yet, so no beer for me ;) -00:06 (@yngwin) heh -00:06 (+reavertm) if we focus guys - we'll finish earlier :P -00:07 (@hwoarang) ok with the guide? -00:07 (joost_op) +1 -00:07 (@hwoarang) shall we proceed? -00:07 (@hwoarang) tampakrap: ? -00:07 (@tampakrap) jmbsvicetto: the procedure to install kde3 and to install kde3/4 isn't different so i wouldn't agree :) -00:07 (@tampakrap) same sets, same keyword files... -00:07 (@jmbsvicetto) tampakrap: ok, feel free to work on it -00:07 (@yngwin) i say whoever writes the guide(s), gets to make the decision -00:07 (@tampakrap) ok move on then -00:08 (@scarabeus) ok yngwin you take over -00:08 (@hwoarang) what about kdebindings? -00:08 (@hwoarang) is this off as well? -00:08 (@scarabeus) eh -00:08 (+reavertm) lacks some ebuilds -00:08 (@scarabeus) right -00:08 (@scarabeus) bindigns -00:08 (@dagger) "kdebindings, lots of stuff missing there" -00:08 (@scarabeus) we lacks tons of stuff -00:08 (+reavertm) usually ruby and c# -00:08 -!- jmbsvicetto topic of #gentoo-kde ->> Gentoo KDE | meeting: Now - kdebindings | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU -00:09 (+wired) lol -00:09 (@yngwin) ok, whats the story with ruby for kde? does that depend on (currently broken) qt4-qtruby at all? -00:09 (+reavertm) nobody knows :) -00:09 (@scarabeus) ruby java c# php -00:09 (@scarabeus) so whom wants it -00:09 (+reavertm) - we need to try add those ebuilds -00:09 -!- ABCD [n=ABCD@wikipedia/ABCD] joins -> #gentoo-kde -00:10 (+reavertm) - maybe some ebuild name refactor for 4.3 -00:10 (+reavertm) anything else regarding kdebindings? -00:10 (@scarabeus) ok reavertm we will talk about it later -00:10 (@jmbsvicetto) scarabeus: no PERL? -00:10 (@scarabeus) reavertm: and delegate to other HTs -00:10 (@scarabeus) jmbsvicetto: no perl -00:10 (@jmbsvicetto) I suggest we hand JAVA to bonsaikitten :P -00:10 (@scarabeus) bindigns done -00:11 (@scarabeus) joost_op: do you want to talk about sabayon then? -00:11 (@jmbsvicetto) He's becoming too sane -00:11 (@scarabeus) D -00:11 (@bonsaikitten) jmbsvicetto: thank you :) -00:11 (@jmbsvicetto) bonsaikitten: we aim to please ;) -00:11 (@bonsaikitten) I aim to kill -00:11 (+papillon81) :D -00:11 (joost_op) well scarabeus i'm here -00:12 (+reavertm) go :) -00:12 (@scarabeus) shoot -00:12 (@scarabeus) :] -00:12 (@dagger) RUN! -00:12 (joost_op) from the sabayon side we want to shoulder the kde herd as much as possible -00:12 -!- Guest36992 [n=red@lounge.datux.nl] <- quit [Read error: 60 (Operation timed out)] -00:12 (joost_op) what we can offer would be something in the form off a repository that has experimental kde stuffs, built of the testing tree -00:12 (+reavertm) you already did with some automagic deps and doc verification -00:13 (joost_op) since i would maintain that tree, i could feedback about my findings -00:13 (+reavertm) binary packages you mean? i don't follow -00:13 (joost_op) nah -00:14 (joost_op) i built against a tree thats near full portage -00:14 -!- UT2K3 [n=UT2K3@212.86.209.81] joins -> #gentoo-kde -00:14 (joost_op) sabayon is near full portage -00:14 (+reavertm) yes, I know, what would be that experimental kde stuff? -00:14 -!- FlyingFoX [n=FlyingFo@137.226.140.67] joins -> #gentoo-kde -00:14 (joost_op) well, e.g. you are working on kde 4.3 -00:15 (joost_op) i could add this in a kde repository -00:15 (joost_op) and start working on this and feedback my findings -00:15 (UT2K3) hello guys, i'm using fglrx with dualscreen. When run kde its only on the notebook lcd and the right screen have no wm. Its possible to make it work? -00:15 (@hwoarang) why not use the ebuilds from kde-testing? whu starting a new repository -00:15 (joost_op) if you think it would help collect info -00:15 (@hwoarang) UT2K3: meeting now . laterz : -00:15 (@hwoarang) :) -00:16 (joost_op) hwoarang, we don't want that in our mainline repositories .. -00:16 (+krytzz) joost_op hm well duplicated work/ebuilds is always bad :p -00:16 (UT2K3) oh its still meeting ok -00:16 (@hwoarang) as krytzz said, duplicating ebuilds will lead to more compilcated results -00:17 (@dagger) UT2K3: yeah, but it shouldn't take long now -00:17 (joost_op) do you guys to start with see a benefit in me, or sabayon, help testing -00:17 (tdr) duplicated ebuild confuse people -00:17 (+reavertm) joost_op: you're free to do anything with ebuilds - and patches (those upstream I guess) are always welcome -00:17 (UT2K3) okay (= ty -00:17 (@jmbsvicetto) joost_op: If you want to cooperate, using something we provide would seem to be better for both projects than duplicating work -00:17 (joost_op) nono -00:17 (joost_op) your ebuilds -00:17 -!- panard [n=panard@2a01:e35:8a09:e130:2e0:61ff:fe11:7adb] <- quit [Read error: 104 (Connection reset by peer)] -00:18 (+reavertm) joost_op: you just need to find someone to take care of this - it's quite a bit of work -00:18 (joost_op) lol -00:18 (@jmbsvicetto) So you mean you could test ~arch ebuilds? -00:18 (joost_op) x86 and amd64 -00:18 (+krytzz) joost_op we had this already with kde-crazy and kde-testing, was a mess :p -00:18 (@jmbsvicetto) Then go for it, we'll be glad to get bug reports -00:18 (joost_op) i have a power machine to built -00:18 (@scarabeus) ok i will put it this way -00:19 (joost_op) i have testers AND users that report -00:19 (@scarabeus) bugs from ppl with @sabayonlinux.org will be handled legitimely as our bugs -00:19 (@scarabeus) and we can reflect them as HTs -00:19 (@jmbsvicetto) joost_op: although most of us run ~arch or stuff in kde-testing -00:19 (joost_op) i can filter whats important -00:19 (@scarabeus) just for internal herd needs -00:19 -!- Sho_ [n=EHS1@kde/hein] <- quit [Read error: 104 (Connection reset by peer)] -00:19 (@scarabeus) so we can rely for some info from them -00:19 (+reavertm) especially those automagic deps are welcome -00:19 (@scarabeus) yep -00:19 (+reavertm) :) -00:20 (@scarabeus) those made mine day great :] -00:20 -!- Sho_ [n=EHS1@kde/hein] joins -> #gentoo-kde -00:20 (joost_op) yeah in our staff meeting we talked about how to report anything back to gentoo -00:20 (@jmbsvicetto) ok, I'll have to leave in approximately 10 minutes -00:20 (@dagger) Qt stuff now? -00:21 (@scarabeus) jmbsvicetto: did you read what i wrote? -00:21 (@scarabeus) any objections to that? -00:21 (joost_op) anybody from our team uses @sabayonlinux.org -00:21 (@jmbsvicetto) joost_op: we discuss details later with you. We can even schedule some time -00:21 (joost_op) and each report has been dicussed in our team first -00:21 -!- panard [n=panard@banquise.backzone.net] joins -> #gentoo-kde -00:21 (joost_op) to not overload anybody -00:21 (joost_op) and to certainly not duplicate work -00:21 (@jmbsvicetto) scarabeus: no objection -00:22 (joost_op) allright -00:22 -!- helch [n=helch@212-41-73-167.adsl.solnet.ch] <- quit [Remote closed the connection] -00:22 (@jmbsvicetto) In some cases we might require some testing to duplicate the bug, but we'll address the bugs -00:22 (joost_op) i'm saying you can abuse me to get things in our yet to make repository -00:22 (joost_op) where we can heve people to test it -00:23 (joost_op) *have -00:23 (@jmbsvicetto) ok, thanks -00:23 -!- mpagano [n=mpagano@gentoo/developer/mpagano] <- quit ["cya"] -00:23 (@scarabeus) ok we will address this issue more at more comfy time :] -00:23 (@scarabeus) now lets get to the qt -00:23 (@hwoarang) \o/ -00:23 (@hwoarang) ************************** qt meeting ***************************** -00:23 (joost_op) allright, thx -00:23 (@hwoarang) wake up ppl -00:23 (+Pesa) :) -00:23 (@hwoarang) !herd qt -00:24 (+wired) hwoarang: seriously, we're all here -00:24 (Willikins) (qt) carlo, hwoarang, tampakrap, yngwin -00:24 (+wired) :D -00:24 (@dagger) bear time :) -00:24 (@hwoarang) spatz: ping -00:24 (+spatz) pong -00:24 (@dagger) (not ever beer :p) -00:24 (@jmbsvicetto) hwoarang: technically it's still the KDE *team* meeting ;) -00:24 (@hwoarang) well yes :P -00:24 (@yngwin) ok, first decision: next time separate qt meeting -00:24 (@hwoarang) i just wanted to wake them up -00:24 (@hwoarang) :D -00:24 (@yngwin) this is getting too long for some ppl -00:24 (+reavertm) I agree -00:24 -!- Sho_ [n=EHS1@kde/hein] <- quit [Read error: 104 (Connection reset by peer)] -00:24 (@tampakrap) for all -00:24 (@hwoarang) i think this is the first time the kde one took that long -00:25 (@scarabeus) yngwin: well the issue is due to we didnt have meeting in 2 months window -00:25 (+reavertm) we're technical, soory ;) -00:25 (@yngwin) i know -00:25 (@jmbsvicetto) yngwin: Do you think it's best to have split meetings or should we have more frequent/shorter meetings? -00:25 (@scarabeus) good Q -00:25 (@yngwin) more frequent + shorter -00:25 (+reavertm) split meeting is good anyway -00:25 (+papillon81) first of all we should go on with the topics -00:25 (@hwoarang) +1 yngwin -00:25 (+reavertm) no need to qt folks to attend to kde meeting anyway unless they're interested -00:26 (@jmbsvicetto) yngwin: I can live with both and if we keep having the same meeting, qt issues don't (shouldn't) be left for the end -00:26 (@hwoarang) meeting is supposed to be 'project' wise -00:26 (@hwoarang) not herd wise -00:26 (@scarabeus) jmbsvicetto: it is for this time -00:26 (@scarabeus) jmbsvicetto: next time i can shuffle the topics -00:26 (@jmbsvicetto) yeah, I'm just opening up other solutions in case people prefer them -00:26 (@scarabeus) and we can have the meetings often i dont mind :] -00:26 (@yngwin) alright, lets get on it -00:26 -!- Civil [n=Civilian@95-24-2-240.broadband.corbina.ru] <- quit [Remote closed the connection] -00:27 (@yngwin) we can discuss needs for next meeting tomorrow ;) -00:27 (@hwoarang) i think we can pass the recruit stuff -00:27 (@scarabeus) okey -00:27 (@yngwin) recruits i already mentioned -00:27 (@yngwin) qt status in tree -00:27 (@yngwin) 4.5.1 is goibng stable, but arches are slow -00:27 (@hwoarang) indeed :/ -00:27 -!- Displacer [n=tool@tool.gtn.ru] <- quit ["Leaving"] -00:27 (+wired) !earch qt-core -00:27 (Willikins) wired: x11-libs/qt-core 4.4.2[4]: 4.4.2-r2[4]: amd64 hppa ia64 ppc64 sparc x86 4.5.1[4]: alpha ~amd64 ~arm ~hppa ~ia64 ~mips ppc ~ppc64 ~sparc ~x86 ~x86-fbsd -00:28 (@hwoarang) there is a bug about the -platform . The addition on qt4-build-edge eclass seems to fix it -00:28 -> hwoarang searches the bug -00:28 (+wired) bug 266201 -00:28 (Willikins) wired: https://bugs.gentoo.org/266201 "Please mark x11-libs/qt-*-4.5.1 stable [also regression tracker]"; Gentoo Linux, Ebuilds; NEW; yngwin@g.o:qt@g.o -00:28 (@hwoarang) bug 270475 -00:28 (Willikins) hwoarang: https://bugs.gentoo.org/270475 "x11-libs/qt-4.5 configure guesses arch based on uname"; Gentoo Linux, Ebuilds; NEW; jokey@g.o:qt@g.o -00:29 -!- emera|d [n=smaragd@p579DE9E7.dip.t-dialin.net] <- quit [] -00:29 (@hwoarang) this bug ( and the proposed solution ) seems to fix the massive errors we had with ppc, chroots, distcc etc -00:30 (@yngwin) ok, i propose we add arches on that one, and ask their opinion -00:30 (@jmbsvicetto) It would great if you could get upstream to fix qt-webkit on sparc -00:30 (+papillon81) there is another patch for qt-gui (already in the qting-edge overlay), that fixes PPC graphics issues and should go to the treee ASAP -00:30 (@hwoarang) qt-gui is stable on ppc -00:30 (@jmbsvicetto) We won't be able to get KDE in sparc until qt-webkit is fixed or we can make KDE upstream make it optional -00:30 (@yngwin) bug number? -00:30 (+wired) yngwin: ^^ thats the one i've talked to you about -00:31 (@hwoarang) jmbsvicetto: dont expect this to happen soon -00:31 (@yngwin) i know, i still havent heard if its so important and why -00:31 (@hwoarang) upstream is really really slow -00:31 (+papillon81) yngwin: no bug # -00:31 (@hwoarang) i really dont think we should do a revbump just for a ppc patch -00:31 (@hwoarang) cause all other arches will upgrade for nothing -00:31 (@hwoarang) maybe we can put is 'silently' on stable qt-gui-4.5.1 -00:31 (@hwoarang) *s/is/it -00:31 (+papillon81) hwoarang: just add it silently :-) -00:32 (@yngwin) we need a proper bug report -00:32 -> papillon81 will do it -00:32 (@tampakrap) well, revbump and tell ppc to stabilize again -00:32 (@yngwin) because i still dont know what we're talkingf about -00:32 (@tampakrap) it won't break stable users anywayz -00:32 (@hwoarang) tampakrap: revbump is wrong -00:32 (@hwoarang) the rest of arches dont need to emerge qt-gui again -00:32 (@jmbsvicetto) yngwin / wired: are you asking the bug number for qt-webkit and sparc? -00:33 (@hwoarang) it is just a ppc patch that can go on the current qt-gui -00:33 (@tampakrap) i know but there is no other way -00:33 (@yngwin) ok, we can discuss that on the bug -00:33 (+wired) jmbsvicetto: no the patch for qt-gui and ppc -00:33 (@hwoarang) good -00:33 (@yngwin) jmbsvicetto: no, the ppc issue -00:33 (@jmbsvicetto) ok -00:33 (+wired) jmbsvicetto: it doesn't have a bug -00:34 (@tampakrap) two options, silent update or revbump and restabilize, choose one, i choose the second -00:34 (@yngwin) ok, other in tree issues? -00:34 (@hwoarang) scarc issue should go upstream but i am pretty sure it ll take forever even to accept it as valid -00:34 -!- ali_bush_work [i=cab44391@gateway/web/ajax/mibbit.com/x-e12143e624250926] joins -> #gentoo-kde -00:34 (@yngwin) yes, but we can do our duty and report -00:34 (@hwoarang) yes -00:34 (@hwoarang) of course -00:34 (@tampakrap) wait -00:34 (@tampakrap) the sparc issue is reported by me in gentoo bugzilla long time ago -00:34 (@tampakrap) i've made some research about it -00:35 (@hwoarang) yes but did you take it upstream? -00:35 (@tampakrap) there was actually a patch -00:35 (@hwoarang) can you ? -00:35 (@hwoarang) mmm -00:35 (@yngwin) bug # ? -00:35 (@tampakrap) but it broke ppc64 i think or something -00:35 (@jmbsvicetto) tampakrap: The patch wasn't accepted upstream -00:35 (@tampakrap) of course since it broke ppc64 -00:35 (@jmbsvicetto) tampakrap: And iirc, that bug may also affect alpha (or at least also interests them) -00:35 (@yngwin) we could apply the patch only on sparc -00:36 (@tampakrap) yes -00:36 (@tampakrap) exactly -00:36 (@hwoarang) sound like an easy work around -00:36 (@tampakrap) i own a sparc but it will take some time to update it to qt-4.5 -00:36 (@tampakrap) i'll contact sparc herd as well -00:36 (@hwoarang) ok -00:36 (@jmbsvicetto) tampakrap: tcunha and jmorgan might be willing to help out with it -00:37 (@tampakrap) bug 235685 -00:37 (Willikins) https://bugs.gentoo.org/235685 "x11-libs/qt-webkit-4.4.x sigbus on ~sparc"; Gentoo Linux, KDE; NEW; tampakrap@g.o:sparc@g.o -00:38 (@hwoarang) ok -00:38 (@yngwin) ok, if you can follow-up on that with sparc arch team -00:38 (@tampakrap) comment 7 says that it should not be restricted to sparc only -00:38 -!- B-Man1 [n=B-Man@cpe-098-024-241-139.ec.res.rr.com] joins -> #gentoo-kde -00:38 (@tampakrap) i don't know why -00:38 (+papillon81) bug 270769 -00:38 (Willikins) papillon81: https://bugs.gentoo.org/270769 "x11-libs/qt-gui-4.5.1 PPC endian fix"; Gentoo Linux, Ebuilds; NEW; chrschmitt@gmail.com:bug-wranglers@g.o -00:38 (@yngwin) tampakrap: could be interesing for other arches too, like alpha -00:39 (@yngwin) papillon81: tnx -00:40 (@hwoarang) are we done with bugs? -00:40 (@yngwin) no -00:40 (@yngwin) i'd like someone to look at bug 209626 -00:40 (Willikins) yngwin: https://bugs.gentoo.org/209626 "Patches for qt4.eclass and qt4-build.eclass to make them ready for eclass-manpages"; Gentoo Linux, Eclasses and Profiles; NEW; bugs@rennings.net:qt@g.o -00:41 (@hwoarang) I will take care of it -00:41 (@yngwin) thanks -00:41 (@hwoarang) anything else? -00:42 -!- andreax [n=andreaz@p57B94087.dip.t-dialin.net] joins -> #gentoo-kde -00:42 (@yngwin) and is there anyone interested in bug 224951 ? -00:42 (Willikins) yngwin: https://bugs.gentoo.org/224951 "[Tracker] dev-ruby/qt4-qtruby issues"; Gentoo Linux, Applications; NEW; unnamedrambler@gmail.com:ruby@g.o -00:42 -!- Friesia [n=speckius@212.113.107.78] <- quit [Remote closed the connection] -00:42 (@yngwin) it has been hardmasked (all versions) in tree for a while now -00:42 (@hwoarang) brrrrrrrrrrrrr ruby -00:43 (@yngwin) well, i think we should fix it or schedule for removal -00:43 (@hwoarang) we can ping ruby herd again -00:43 (@hwoarang) as reach a common decision -00:43 (@hwoarang) *and -00:44 (@yngwin) i started doing some testing on 2.x version, but didnt get far -00:44 (+wired) i could give it a try as well -00:44 (@hwoarang) we can add it on overlay and start playing -00:44 (@yngwin) i needs work (which means time) -00:44 (@yngwin) ok, i'll add what i have to overlay -00:44 (@hwoarang) ok -00:44 (+wired) =] -00:44 (@hwoarang) bug 236341 needs some love as well -00:44 (Willikins) hwoarang: https://bugs.gentoo.org/236341 "PyQt4 has automagic dependencies"; Gentoo Linux, Ebuilds; REOP; alessandro.guido@gmail.com:qt@g.o -00:45 (@hwoarang) i think me and Pesa will get this done soon -00:45 (+Pesa) i'm working on that one -00:45 (@yngwin) nice -00:45 (@hwoarang) sweet -00:45 (@hwoarang) i cant see anything else -00:45 (+Pesa) btw, bug 251997 was fixed some time ago -00:45 (Willikins) Pesa: https://bugs.gentoo.org/251997 "net-im/psi: pre-stripped files found"; Gentoo Linux, Ebuilds; NEW; flameeyes@g.o:welp@g.o -00:45 -!- andreax1 [n=andreaz@p57B9556B.dip.t-dialin.net] <- quit [Operation timed out] -00:45 (+Pesa) please mark as such :) -00:45 (@yngwin) ok, we can close that? -00:45 (@hwoarang) yes indeed -00:45 (+Pesa) yep -00:46 (+Pesa) fixed by a change in eqmake4 -00:46 (@yngwin) done -00:46 (@hwoarang) \o/ -00:46 (+Pesa) thanks -00:46 (@hwoarang) any other bugs? -00:46 (@yngwin) what about the embedded stuff -00:47 (@hwoarang) tricky -00:47 (@hwoarang) qt-embedded? -00:47 (@yngwin) esp https://bugs.gentoo.org/show_bug.cgi?id=43827#c9 -00:48 (@hwoarang) we can contact him -00:48 (@yngwin) maybe we should contact him and see if he still wants to maintain it -00:48 (@hwoarang) and ask him to be proxy mantainer -00:48 (@yngwin) then add it to overlay or tree -00:48 (@yngwin) indeed -00:48 -> hwoarang noted -00:48 (@hwoarang) I will contact him -00:48 (@yngwin) ok, on to overlay then? -00:49 -!- panard [n=panard@banquise.backzone.net] <- quit [Read error: 54 (Connection reset by peer)] -00:49 (@hwoarang) sorry? -00:49 (@tampakrap) yes -00:49 (@yngwin) next point on agenda -00:49 (@hwoarang) we are moving on? -00:49 (@hwoarang) ok -00:49 (@hwoarang) Pesa: spatz -00:49 (@hwoarang) are you guys using qt live ebuilds? -00:49 (+Pesa) no -00:49 (+spatz) nope -00:49 -!- Guest36992 [n=red@lounge.datux.nl] joins -> #gentoo-kde -00:49 (@tampakrap) i am -00:50 (@hwoarang) ok -00:50 (+papillon81) me -00:50 (+reavertm) i use qt-copy in chroot -00:50 (@hwoarang) so we need to see who maintains what -00:50 (@hwoarang) i do maintain 4.5.9999 (both qt-copy and nokias ) -00:50 (@yngwin) i use latest release -00:50 (+reavertm) but I'm no longer maintaing those... -00:50 (@hwoarang) that is 4.9999? -00:50 (@hwoarang) wired: is on 4.9999 -00:50 (+wired) i test 4.999 and 4.5.9999[-qt-copy -00:50 (@yngwin) 4.9999 is nokia qt git trunk -00:50 (+wired) i test 4.999 and 4.5.9999[-qt-copy] -00:51 -!- panard [n=panard@2a01:e35:8a09:e130:2e0:61ff:fe11:7adb] joins -> #gentoo-kde -00:51 (@hwoarang) so we are ok on that -00:51 -!- Polynomial-C [n=Poly-C@gentoo/developer/Polynomial-C] <- quit [Remote closed the connection] -00:51 (+wired) nokia -00:51 (+wired) 4.6 trunk and 4.5 trunk ^^ :) -00:51 -!- Hello_World [n=koukos@ip-83-212-218-40.adsl.aueb.gr] joins -> #gentoo-kde -00:51 (@hwoarang) ok so we re ok on qt libe ebuilds -00:52 (@hwoarang) *live -00:52 (+wired) we should discuss what will happen to the RDEPEND in qt4-edge-build -00:52 (@hwoarang) yes -00:52 (+wired) are we moving that in tree? -00:52 (@yngwin) is it tested enough? -00:52 (+wired) today tampakrap had yet another issue -00:52 -!- UT2K3 [n=UT2K3@212.86.209.81] <- quit [Remote closed the connection] -00:53 (@hwoarang) what about the paludis support -00:53 (+wired) yngwin: so far it seems safe on my tests -00:53 (+wired) paludis doesn't like it but thats only because ciaran doesn't want to implement blocks the same way portage does -00:53 (@yngwin) paludis seems to be broken at this point -00:53 -!- Polynomial-C [n=Poly-C@gentoo/developer/Polynomial-C] joins -> #gentoo-kde -00:53 (@bonsaikitten) hwoarang: why do we care? -00:53 (@hwoarang) cause i cant stand the trolls tomorrow -00:54 -!- bschindl [n=quassel@77-56-156-71.dclient.hispeed.ch] <- quit [Read error: 104 (Connection reset by peer)] -00:54 (+wired) no trolls -00:54 (@hwoarang) if you know what i mean -00:54 (+wired) actually -00:54 (@bonsaikitten) so ignore them -00:54 (@bonsaikitten) "WORKSFORME" is a great defense ;) -00:54 (+wired) this is one of the few cases where he didn't complain -00:54 (@hwoarang) in this case we can proceed -00:54 (+wired) i think the way this works is valid and paludis should adapt if it wants to work -00:54 (@hwoarang) the solution is pretty clean and easily revertable -00:55 (@hwoarang) yngwin: what do you think -00:55 (@yngwin) i dont think there is a better solution -00:55 -!- termite47384 [n=me@cpe-066-057-082-106.nc.res.rr.com] joins -> #gentoo-kde -00:55 -!- mode/#gentoo-kde [+v termite47384] by ChanServ -00:55 (@hwoarang) ok then we can proceed -00:55 (@yngwin) if we talk about eclass functionality anyway -00:55 (+wired) ok then it should go to qt4-build along with anything else we decide to migrate -00:55 (@yngwin) what about other stuff we want to move to tree -00:56 (@hwoarang) well -00:56 (@hwoarang) qt4-build can use -platform as discussed before -00:56 (@hwoarang) but that should take a while -00:56 (@yngwin) yes -00:56 (@hwoarang) we need to invite arches on that bug -00:56 (@hwoarang) i have nothing else to propose for qt4-build -00:57 (@hwoarang) i think this eclass has been reviewed recently -00:57 (@hwoarang) just before pushing qt-4.5.0_rc1 -00:57 (@yngwin) we need to remove custom-cxxflags when 4.5.2 goes in -00:57 (@hwoarang) yes -00:58 (@hwoarang) this use flag has been dropped on overlay. Works ok . -00:58 (@hwoarang) we are safe to drop it when 4.5.2 arrives -00:58 (@yngwin) good, let's not forget -00:58 -> hwoarang noted -00:58 (@yngwin) what about qt4.eclass -00:58 (@hwoarang) Pesa: here we are -00:58 (@hwoarang) :D -00:59 (+Pesa) heh -00:59 (@yngwin) we wanted qt4-edge -> qt4-ng or something? -00:59 (@hwoarang) i think that you pushed a default src_configure and src_install in the past -00:59 (@hwoarang) but you revert it -00:59 (@hwoarang) why? -00:59 (@yngwin) we had to -00:59 (@hwoarang) brakeages? -00:59 (@yngwin) it broke stuff all over the place -00:59 (@hwoarang) right -01:00 (@hwoarang) i cant understand how -01:00 (@hwoarang) since src_install is always overriden -01:00 (@yngwin) so i do want that back in, but we need it in a separate eclass, so existing ebuilds can be migrated slowly -01:00 (@hwoarang) but lets play it safe -01:00 (@hwoarang) ok -01:00 (+Pesa) isn't it possible to have a drop-in replacement? -01:00 (@hwoarang) meaning? -01:01 -!- smorg [n=quassel@75-168-239-242.mpls.qwest.net] <- quit ["http://quassel-irc.org - Chat comfortably. Anywhere."] -01:01 (+Pesa) a revised qt4.eclass, but maintaining backward compatibility -01:01 (@yngwin) no, because we require eapi-2 and have new default functionality such as src_configure in there -01:01 (@hwoarang) we cant -01:01 -!- smorg [n=quassel@75-168-239-242.mpls.qwest.net] joins -> #gentoo-kde -01:01 (@hwoarang) how about maintain eqmake4 on qt4.eclass and inherit that eclass on the new one? -01:02 (@hwoarang) just to avoid mantaining 2 eqmake4 -01:02 (@yngwin) hmm, i dont like the added level of complexity -01:02 (+Pesa) i agree with yngwin -01:03 -> hwoarang is thinking -01:03 (+spatz) is qt4-edge to be merged as-is? at least the translations stuff seems broken on many packages and fixing after merge can be problematic -01:03 (+Pesa) it'd be better to have a eqmake4.eclass inherited by both the new and the old qt4 eclasses -01:03 (@hwoarang) the translations part is experimental -01:04 (+Pesa) spatz: i don't think so -01:04 (@hwoarang) yngwin: cant we open a tracker -01:04 (@hwoarang) about the brakeages? -01:04 (+spatz) Pesa: which part? -01:04 (@yngwin) what breakages? -01:04 (@hwoarang) which are caused by the new eclass? -01:05 (@hwoarang) in case we push it as qt4.eclass -01:05 (+Pesa) spatz: well, src_configure() needs improvements imho -01:05 (@yngwin) only if we dont touch the original eclass, we can't break stable stuff -01:06 (@hwoarang) introducing the default src_configure and src_install will brake some packages -01:06 (@hwoarang) we can track them on bugzilla -01:06 (@hwoarang) on a special tracker -01:06 (@yngwin) what i propose is to add the new eclass, and mark the old one as deprecated and make a tracker for migration to new eclass -01:06 (+Pesa) yeah -01:06 (@tampakrap) ^^nice -01:06 (+wired) yngwin++ -01:07 (+wired) qt4-v2.eclass? -01:07 (@hwoarang) nah -01:07 (@hwoarang) we need a pretty cool name -01:07 (@hwoarang) :P -01:07 (@yngwin) we had qt4-ng in mind -01:07 (@hwoarang) -ng sounds ok -01:07 (+wired) keep in mind one day we might have another big-bad-ass revision -01:07 (+wired) lets stick a number in there -01:07 (@yngwin) yeah, so i'm open for suggestions -01:07 (@tampakrap) qt4-r1.eclass? -01:07 (+wired) -r1 isn't bad either -01:08 (@yngwin) inherit qt4-r1 -01:08 (@hwoarang) nah -01:08 (@hwoarang) ugly -01:08 (@hwoarang) :P -01:08 (@yngwin) i'm not sure i like that -01:08 (+wired) i prefer qt4-v2 -01:08 (+wired) inherit qt4-v2 -01:08 (kage-ookami) qt4-2nd -01:08 (@yngwin) qt4-edition2009 -01:08 (@hwoarang) .. -01:08 (@yngwin) just brainstorming -01:08 (+spatz) qt4-home_premium -01:08 (@tampakrap) qt4_pre20090521 -01:08 (+wired) lol -01:08 (@yngwin) well, that's bikeshedding, can be done tomorrow -01:09 (+wired) qt4-try2 -01:09 (+wired) :D -01:09 (@hwoarang) ok -01:09 (@tampakrap) qt4_thepreviousonewasFAIL -01:09 (@yngwin) but we agree on principle? -01:09 (@tampakrap) yes -01:09 (+wired) i think its the best approach yeah -01:09 (@hwoarang) ok -01:09 -!- joost_op [n=joost@86.92.194.222] <- quit ["Leaving"] -01:09 (+Pesa) i do, if my opinion counts -01:09 (@yngwin) it does :) -01:09 (@hwoarang) also Pesa and me are working on eqmake4 patch, to automatically guesses the project name so we can have a more generic src_configure -01:09 (@yngwin) translation stuff still needs work? -01:10 (@hwoarang) yes -01:10 (+Pesa) can be made more generic i think -01:10 (@hwoarang) i have two ebuilds that I still want to migrate on that -01:10 (@yngwin) ok, so lets work on it in overlay, and see in a few weeks time or so -01:10 (@hwoarang) Pesa: i ll add the second patch, then feel free to play :) -01:11 (@yngwin) anything about other packages in overlay? -01:11 (@hwoarang) the current status seems ok -01:11 (+Pesa) hwoarang: with '.' instead of ${S} though! -01:11 (@tampakrap) i can take care of live ones -01:11 (@hwoarang) yes :) -01:11 (@hwoarang) i ve moved many packages on tree -01:11 (@hwoarang) and kept the live ones -01:11 (+Pesa) fine then -01:12 (@yngwin) what about qtjambi -01:12 (@yngwin) shouldnt that go to tree as well? -01:12 (@yngwin) 4.5.0 that is -01:12 (+Pesa) i added 4.5.0_p1 to the overlay -01:12 (@hwoarang) does it work? -01:12 (@hwoarang) or it needs further testing -01:12 (+Pesa) worksforme :D -01:12 (@yngwin) it's java, how would i know if it works? -01:12 (+wired) lol -01:12 (@yngwin) :p -01:13 (+wired) yngwin: actually the correct answer would be -01:13 (@hwoarang) so what can we do with it -01:13 (+wired) its java, ofcourse not -01:13 (+Pesa) seriously, it has huge improvements over portage version -01:13 (+wired) :D -01:13 (@yngwin) who maintains it in portage again -01:13 -!- bschindler [n=quassel@77-56-156-71.dclient.hispeed.ch] <- quit [Read error: 110 (Connection timed out)] -01:14 (@hwoarang) !meta -v qtjambi -01:14 (Willikins) hwoarang: Package: dev-java/qtjambi Herd: qt, java Maintainer: qt, java -01:14 (@hwoarang) we do -01:14 (@hwoarang) :P -01:14 (+wired) lolz -01:14 (@dagger) lol ;) -01:14 (@yngwin) ali_bush it seems from changelog -01:15 (@yngwin) ok, maybe confer with him -01:15 -> hwoarang noted -01:15 (@yngwin) then we can bump -01:15 (@hwoarang) i ll poke him as long as he is available -01:15 (@hwoarang) *as soon as -01:15 (@hwoarang) stupid beer -01:16 (@yngwin) heh -01:16 (@jmbsvicetto) ok, I really need to leave now. See you later -01:16 -!- Guest36992 [n=red@lounge.datux.nl] <- quit [Read error: 60 (Operation timed out)] -01:16 (@hwoarang) bye bye jmbsvicetto -01:16 (@yngwin) ok, see you jmbsvicetto -01:16 -!- sean345 [n=quassel@c-76-105-5-254.hsd1.ca.comcast.net] joins -> #gentoo-kde -01:16 (+wired) bye jmbsvicetto -01:16 (@hwoarang) ok i think we are done with the overlay -01:16 (@yngwin) on to last point? -01:16 (+Pesa) bye jmbsvicetto -01:16 (ali_bush_work) you talking to me :) -01:16 (+spatz) have fun :) -01:16 (@hwoarang) ah -01:16 (@hwoarang) there he is -01:16 (@yngwin) ali_bush_work: yes, we have qtjambi-4.5.0_p1 in overlay -01:17 (ali_bush_work) cool. does it work -01:17 -!- Guest36992 [n=red@lounge.datux.nl] joins -> #gentoo-kde -01:17 (@hwoarang) lol :) -01:17 (@yngwin) [00:12:52] it's java, how would i know if it works? -01:17 (@yngwin) ;) -01:17 (@yngwin) but Pesa says it does -01:18 (ali_bush_work) i'll put it on my todo list :) -01:18 -!- anselmolsm [n=anselmo@200.184.118.130] <- quit [Remote closed the connection] -01:18 (@yngwin) alright -01:18 (ali_bush_work) ETC next century -01:18 (@hwoarang) goodie -01:18 (@hwoarang) no rush :P -01:18 (+Pesa) ali_bush_work: yes, demos and examples work, and also qtdesigner integration -01:18 (@yngwin) we can bump, and let you deal with the bugs :p -01:19 (@yngwin) but if Pesa says it works, i trust him -01:19 (+Pesa) ali_bush_work: and there are tons of other improvements -01:19 (ali_bush_work) ok cool. I will qa the ebuild just too make sure if follows our standards -01:20 (@hwoarang) sweet -01:20 (+Pesa) thanks -01:20 -!- geo27 [n=quassel@lns-bzn-56-82-255-250-237.adsl.proxad.net] <- quit [No route to host] -01:20 (@hwoarang) ok last topic -01:20 (@hwoarang) leader? :/ -01:20 (@yngwin) do we need an elected lead? -01:20 (@hwoarang) what for -01:20 (@yngwin) now that we're a fast growing team -01:21 (@tampakrap) jmbsvicetto is the project leader, scarabeus is KDE HT Lead and yngwin is Qt HT lead -01:21 (@yngwin) well, i thought i would put it before you -01:21 (@tampakrap) i think that is enough -01:21 (@hwoarang) i cant see the reason :) -01:21 (@yngwin) because i just assumed the position, when no-one was looking -01:21 (@hwoarang) i am pretty happy with the current situation -01:22 (@hwoarang) maybe we should discuss it again in July -01:22 (@yngwin) but if you guys are happy with it -01:22 (@hwoarang) before we leave -01:22 (kage-ookami) yngwin: sometimes it takes a person to just assume the position -01:22 (@yngwin) i know -01:23 (@hwoarang) so the answer is NO -01:23 (+spatz) if it works don't fix it -01:23 (@hwoarang) you ll stay the leader either you like it or not -01:23 (@yngwin) ok -01:23 (@hwoarang) -01:23 (+wired) yngwin QT leader woot =] -01:23 (@scarabeus) :D -01:23 (@yngwin) -01:23 (@scarabeus) okey -01:23 (@scarabeus) :D -01:23 (@hwoarang) ------------------- -01:23 (+Pesa) :D -01:23 (@hwoarang) omg -01:24 (@hwoarang) 3:30 hours -01:24 (@hwoarang) jesus! -01:24 (@yngwin) holy mother -01:24 (+wired) closer to 3 hours actually -01:24 (+spatz) back to homework :/ -01:24 (+wired) but still! -01:24 -> yngwin hands out more cookies -01:24 (+wired) scarabeus: you want log? -01:24 (@yngwin) wired: CC me as well please -01:24 (@tampakrap) does it need rendering? -01:25 (@yngwin) i'll do summary for Qt part -01:25 (@hwoarang) ohhhhhhhhhhhhhh -01:25 (@hwoarang) btw -01:25 (@hwoarang) for those who havent noticed -01:25 -!- tampakrap topic of #gentoo-kde ->> Gentoo KDE | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 | KDE 4.2.87in kde-testing! | SitRep: SNAFU -01:25 (@hwoarang) i ve wrote this guide http://www.gentoo.org/proj/en/desktop/kde/qt4-based-ebuild-howto.xml -01:25 (@hwoarang) so any additions etc are welcomed diff --git a/meeting-logs/kde-project-meeting-log-20090618.txt b/meeting-logs/kde-project-meeting-log-20090618.txt deleted file mode 100644 index 96f0650..0000000 --- a/meeting-logs/kde-project-meeting-log-20090618.txt +++ /dev/null @@ -1,1064 +0,0 @@ -Note: times are UTC+2 - -[20:59.03] *** Topic is 'Gentoo KDE | 18.6. @ 19:00 UTC = Meeting [http://dev.gentoo.org/~scarabeus/0906meeting_topics.txt] | KDE 4 guide: http://tinyurl.com/4n47v4 | p.keywords: http://xrl.us/kdekeyw | Overlays: kde-testing, qting-edge | Want to help? http://tinyurl.com/gktodo | Bugs: http://tinyurl.com/kdebugs1 http://xrl.us/qtbugs | Useful links: http://userbase.kde.org/ http://ktown.kde.org/~dirk/dashboard | Want to test KDE4 on a kvm? http://tinyurl.com/by7tv3 ' -[20:59.03] *** Set by scarabeus on Thu Jun 18 20:40:41 -[20:59.04] but if you listen, we'll have to kill you -[20:59.07] it's custom the ops get to kick everyone except club members out when the meeting starts -[20:59.08] :P -[20:59.11] be ready.. -[20:59.33] the meeting starts with a customery kick-banning -[20:59.54] *** BCMM (n=bcmm@unaffiliated/bcmm) has joined #gentoo-kde -[21:00.01] and when the channel's empty, the discussion can begin -[21:00.35] meeting starts ;] -[21:00.39] !herd kde -[21:00.41] (kde) alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, patrick, scarabeus, tampakrap, tgurr -[21:00.42] !herd qt -[21:00.42] scarabeus: (qt) carlo, hwoarang, tampakrap, yngwin -[21:00.44] rollcall plz -[21:00.48] present -[21:01.16] tampakrap will be one hour late so his topic is last on the list (FTR) -[21:01.32] he might not make it -[21:01.35] carlo is absent as usual -[21:01.36] called me 3 hours ago -[21:01.41] hi btw -[21:02.06] and hi from here :) -[21:02.13] haavardw: ping -[21:02.17] hi hwoarang, yngwin, ayoy -[21:02.20] *** scarabeus sets mode: +v ABCD -[21:02.22] hwoarang: pong, I'm here -) -[21:02.25] goodie -[21:02.33] your recruits? ;] -[21:02.34] yngwin: ps, remember to set him up on qting-edge -[21:02.34] and hi haavardw -[21:02.41] hi all -[21:02.46] i wander one thing -[21:02.50] where the ... is the rest -[21:02.58] howdy -[21:03.01] aparently only qt is present -[21:03.08] heh -[21:03.21] ok, mask kde for removal; done -[21:03.26] :D -[21:03.27] *** BCMM (n=bcmm@unaffiliated/bcmm) Quit (Remote closed the connection) -[21:03.29] you failed -[21:03.29] LOL -[21:03.31] :p -[21:03.37] we'll rule the world -[21:03.43] meeting's over -[21:03.43] bonsaikitten: still arround i assume ;] -[21:03.51] actually i'm on kde 4.2.4 presently -[21:03.57] woooooooooow -[21:04.03] big step -[21:04.05] sabayon -[21:04.07] * alexxy here -[21:04.08] *** scarabeus sets mode: +v Sput -[21:04.22] *** hwoarang sets mode: +v ayoy -[21:04.24] *** scarabeus sets mode: +v lxnay|two -[21:04.29] *** hwoarang sets mode: +v haavardw -[21:04.42] *** hwoarang sets mode: +v Pesa -[21:04.43] *** yngwin sets mode: +v hwoarang -[21:04.51] ;) -[21:05.04] * scarabeus gives them 5 minutes, then he will be seriously unhappy -[21:05.11] lol -[21:05.41] who do we miss? -[21:05.43] jorge? -[21:05.46] tampakrap_: is off -[21:05.51] bonsaikitten: slacking -[21:05.54] !herd kde -[21:05.56] yngwin: (kde) alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, patrick, scarabeus, tampakrap, tgurr -[21:05.57] so pretty much everybody is here -[21:05.58] I almost forgot -[21:06.03] dagger -[21:06.05] reavertm: hello -[21:06.11] hi scarabeus -[21:07.03] hwoarang: well specialy when we vote on first topic it would be damn nice to have majority of kde devs here -[21:07.17] where is the agenda -[21:07.21] topic -[21:07.27] so for those who hadnt noticed yet, we have two new qt recruits present: ayoy and haavardw -[21:07.36] *** Skim[ihz] (n=skim@skim.static.corbina.ru) has joined #gentoo-kde -[21:07.40] yngwin: voice them -[21:07.50] hwoarang already did -[21:07.51] they are voiced -[21:07.56] ah -[21:07.57] :] -[21:07.58] of course -[21:07.59] didnt look :] -[21:08.00] * haavardw can talk -[21:08.04] bla bla -[21:08.10] ayoy, haavardw: then welcome guys :] -[21:08.17] thank you! -[21:08.20] :) -[21:08.24] thanks -) -[21:08.33] http://archives.gentoo.org/gentoo-desktop/msg_1ef792a71171a444d60ecb870a27e9f3.xml <- agenda -[21:08.41] http://dev.gentoo.org/~scarabeus/0906meeting_topics.txt -[21:08.45] just for the record -[21:09.02] yes -[21:09.09] scarabeus: we can change the topics order -[21:09.21] hwoarang: yes we can -[21:09.23] until kde devs are here -[21:09.34] but kde3 is last or at least until tampakrap show up -[21:09.35] we can start with qt topics if you like -[21:09.49] ok scarabeus . but as I said he mgiht not make it -[21:09.49] :/ -[21:10.04] then wired will be his replacement -[21:10.08] sweet -[21:10.11] where is he -[21:10.11] he hopefully tracked him -[21:10.17] wired: stupid boy -[21:10.29] ping pong -[21:10.31] i foresee that they blame the late announcement :p -[21:10.37] im here -[21:10.39] excuses -[21:10.41] for some weird reason -[21:10.43] :p -[21:10.53] ok shall we start with qt stuff then? -[21:11.11] ok lets start with the qt3 apps first -[21:11.14] I'm fine with this -[21:11.18] and ftr i am really not happy -[21:11.34] slackers -[21:11.38] ok what about the qt3 apps? -[21:11.49] btw, who's going to vote on kdeprefix? -[21:11.55] kde project devs -[21:11.58] i guess -[21:11.59] reavertm: devs, including you -[21:12.09] * alexxy -[21:12.13] reavertm: because you are one of few who can work on it -[21:12.30] * alexxy gonna vote for masking it -[21:12.33] well, last time it was not the case :P -[21:12.36] hwoarang: so lets start with second topic now -[21:12.42] ok -[21:12.53] yngwin: ping pong -[21:13.09] kde3 is scheduled to be removed early next year, right? -[21:13.15] yes -[21:13.20] to some special overaly -[21:13.25] so lets create one common overlay -[21:13.26] and kde3 is the biggest consumer of qt3 -[21:13.29] kde3 and qt3 crap -[21:13.36] instead of just ripping it off -[21:13.40] i agree -[21:13.44] and users can maintain themselves if they want -[21:13.44] fine by me -[21:13.48] otherwise we can throw it -[21:13.59] I wouldn't mind creating special overlay for qt4 and kde4 crap :P - to keep them away from main tree "{ -[21:14.11] oooh flamebite -[21:14.13] what about kde3/qt3 apps not yet ported to kde4/qt4? -[21:14.14] ok whom would update the kde team page reffering to the policy -[21:14.24] spatz: problematic, but hell for maintaining -[21:14.25] spatz: we dont care :) -[21:14.34] yngwin: hwoarang ^ -[21:14.38] the update... :] -[21:14.40] but some are widely used, like k3b -[21:14.42] scarabeus: do we need to update it? -[21:14.47] for what -[21:14.58] by users -[21:15.06] ping :) -[21:15.08] some of them fail to build with libpcre[-static-libs] -[21:15.09] i would like to propose that we officially discourage further usage of qt3: dont introduce new qt3 based apps, prefer qt4 over qt3 -[21:15.11] i hope k3b will see a stable release before the end of this year -[21:15.12] hwoarang: just that other knows -[21:15.17] spatz: k3b has already a kde4 version -[21:15.19] _alpha -[21:15.28] yngwin: good idea -[21:15.32] yngwin: +1 -[21:15.37] spatz: in 6 months ;] -[21:15.49] tanderson: ? -[21:15.57] i think qt3 useflag is enabled by desktop profile? that should be removed -[21:16.18] also good idea, but since when -[21:16.21] Any objections to me patching a kde 3 ebuild with fixes for the .desktop file ? -[21:16.27] tanderson: enjoy -[21:16.28] or JustDoIt ? :) -[21:16.37] tanderson: open kde.gentoo.org -[21:16.42] tanderson: search for CODE file -[21:16.45] tanderson: read it -[21:16.48] tanderson: answer is there -[21:16.59] * bonsaikitten present -[21:17.03] yngwin: aka when we switch the discouraging of qt3 useflag -[21:17.17] it can be even now but apps will be gone in the feb of 2010 -[21:17.21] i'd say immediately -[21:17.33] still we need to make the transission smooth -[21:17.38] scarabeus: aah ok -[21:17.40] i failed on spelling -[21:17.41] hmmm -[21:17.51] scarabeus: oh, did I interrupt your meeting? -[21:17.52] so as yngwin said , immediately -[21:17.57] tanderson: smart boy -[21:18.03] *** dipogon (n=dipogon@84.249.84.164) Quit (Remote closed the connection) -[21:18.09] tanderson: ;] -[21:18.12] qt3 is enabled in /usr/portage/profiles/targets/desktop/make.defaults -[21:18.13] scarabeus: I'm sorry, I'd have taken it to a query if I had known -[21:18.22] tanderson: no prob :] -[21:18.56] hwoarang: ok since you two agree just do it, i wrote it in summary :] -[21:19.02] ok -[21:19.09] afaik profile changes need announcement/discussion on dev ml, so i'll draft up something -[21:19.18] thanks yngwin -[21:19.34] it is strange, but I can't add my own language in system settings... l10n is installed, kde installed without "kdeprefix", some software is translated, but I still can't add my own language.... ;( -[21:19.40] Skim[ihz]: meeting time -[21:19.58] * scarabeus consider +m ;] -[21:20.03] -_- -[21:20.07] we can voice pple if they query us -[21:20.09] sorry -[21:20.10] stop considering -[21:20.17] just do it already -[21:20.18] *** scarabeus sets mode: +m -[21:20.20] :D -[21:20.22] should be done -[21:20.25] ok -[21:20.33] end of story -[21:20.44] scarabeus: moving forward? -[21:20.48] okey -[21:20.51] kde4 stabilization? -[21:21.01] bonsaikitten: patrick since you are here, can we talk about the pykde? -[21:21.10] we can -[21:21.21] *** gengor (n=gengor@gentoo/developer/gengor) has left -[21:21.41] you agreed to deprecate qt3 as of now, so i assume discussion on moving current packages to an overlay will be postponed? -[21:21.42] it is 5th topic for those whom wonder -[21:21.50] scarabeus: voice tanderson -[21:21.52] spatz: yes -[21:21.54] *** scarabeus sets mode: +v tanderson -[21:22.32] bonsaikitten: ok did you find any solution about the collisions in site-packages? -[21:22.42] not yet, but I haven't spent much time on it -[21:22.54] unprefixing of pykde is fine with us, but the issue is also in plasma-workspace now -[21:22.58] or plasma-addons not sure now -[21:23.11] either we allow to use a newer pykde with an older slotted kde (does that work?) -[21:23.20] (with python USE flag only) -[21:23.24] or we try to move the pykde package to versioned directories -[21:23.36] it's all depending on kdeprefix status -[21:23.37] but then packages trying to use it will most likely need some patching -[21:23.59] bonsaikitten: cant we somehow eselect correct site modules for what kde we start -[21:24.01] (no kdeprefix - no pytkde issue) -[21:24.20] *** pgega (n=pgega@77-99-66-168.cable.ubr01.tonb.blueyonder.co.uk) Quit (Client Quit) -[21:24.22] scarabeus: potentially yes, but might be very fragile -[21:24.34] eselect is not the answer here -[21:24.43] and as reaver say, if we agree we can just mask kdeprefix flag, which will be voted -[21:24.50] because without this the kde cant be stabled -[21:24.55] the collision would piss users -[21:24.56] anyway - either unslot or eselect - pykde4-9999 is likely to not work very well with kdelibs-4.2 -[21:24.57] someone still might want to run amarok1 in kde4 for example -[21:25.22] *** haavardw (n=haavardw@cm-84.208.110.202.getinternet.no) Quit (Read error: 104 (Connection reset by peer)) -[21:25.23] right, so we need versioned dirs in site-packages -[21:25.31] how many packages depend on pykde ? -[21:25.40] everything in kde with use python -[21:25.49] yngwin: I don't see it relevant (amarok1) -[21:25.58] (as it uses kdelibs3) -[21:26.06] and pykde3 -[21:26.07] I'm aware of marble plasma-workspace -[21:26.10] any others? -[21:26.10] *** haavardw (n=haavardw@cm-84.208.110.202.getinternet.no) has joined #gentoo-kde -[21:26.26] printing stuff -[21:26.30] (upcoming in 4.3) -[21:26.50] + guidance-power-manager (extragear) -[21:27.01] ok, tolerable amount to patch -[21:27.19] *** pgega (n=pgega@77-99-66-168.cable.ubr01.tonb.blueyonder.co.uk) has joined #gentoo-kde -[21:27.29] I don't worry about API differences here, rather ABI issues -[21:27.34] *** scarabeus sets mode: +v haavardw -[21:28.08] reavertm: the only thing that will suffer is the detection by other packages afaict, so we will have to frickel them to accept the changes -[21:28.22] besides nobody really tried yet mixing new pykde4 with 'old' apps (and we're preventing it so far) -[21:28.22] so if we have to tweak 5 packages that's an acceptable amount of work -[21:28.30] *** Phlogi_ (n=quassel@236-60.77-83.cust.bluewin.ch) Quit (Read error: 60 (Operation timed out)) -[21:29.12] (I guess we don't plan to support older pykde4 with newer apps - so just SLOT deps would be dropped if any) -[21:29.18] *** bertodsera (n=quasseul@95.133.248.44) has joined #gentoo-kde -[21:29.45] anyone willing to help? -[21:29.50] maybe you should test backwards compatibility of newer pykde4 then, as that would prevent the need for patching -[21:29.56] I did it partially in local branch -[21:30.43] Hi -[21:30.47] hey boss -[21:30.49] I'm sorry for being late -[21:31.16] yngwin: right, that will be annoying to test :) -[21:31.27] bonsaikitten: so you and reaver will do it -[21:31.43] *** Phlogi (n=quassel@10-175.0-85.cust.bluewin.ch) has joined #gentoo-kde -[21:31.49] ? -[21:31.52] *** scarabeus sets mode: +v Phlogi -[21:31.59] *sigh* :) -[21:32.06] I'll try to have a look on the weekend -[21:32.07] i take it as yes :] -[21:32.44] ok -[21:32.55] anything else to this topic? -[21:33.07] jmbsvicetto: o hi, i missed ya ;] -[21:34.09] ok, since there wont be more devs here around and since alexxy has pretty late hour i would like to go with his kdeprefix stuff -[21:34.12] alexxy: please -[21:34.22] the topic Solving the final question about kdeprefix. -[21:34.45] well -[21:35.34] One thing: I as a amd64 person won't let kde4 go stable on my architecture with kdeprefix available to my users -[21:35.49] :) -[21:36.01] he he =) -[21:36.03] It causes far too many problems -[21:36.08] tanderson: don't make us go behind your back ;) -[21:36.18] you even don't know about one problem I know of :P -[21:36.20] so kdeprefix will cause many headache to users -[21:36.27] it does already -[21:36.28] bonsaikitten: to whom? -[21:36.29] so lets mask it! -[21:36.29] (qt4 bug related to plugin loader) -[21:36.29] =) -[21:36.35] also the python issue -[21:36.42] plugin loader i personaly HATE -[21:36.49] tanderson: well, let me put it this way - you're not the only one on amd64 with a commit access ;) -[21:37.01] bonsaikitten: if we will mask it -[21:37.12] user can still unmask it -[21:37.17] people who want to use still can do it after unmasking -[21:37.19] and we already state it deemed evil -[21:37.20] bonsaikitten: I think I represent the others on my team -[21:38.01] :] -[21:38.03] scarabeus: I noticed in the back log ;) -[21:38.13] ok i think we should vote on it -[21:38.19] and if the vote will be keep unmasked -[21:38.30] the voting devs must promise to work on the issues with +kdeprefix -[21:38.34] aka they will focus on them -[21:38.42] not that I with -kdeprefix would fix them -[21:38.51] objections? -[21:39.06] tanderson: You're forgetting that you can even mask a use flag in a profile ;) -[21:39.20] tanderson: so you could always stable kde4 *without* kdeprefix -[21:39.34] jmbsvicetto: I am aware of that -[21:39.37] tanderson: and we're not voting on removing kdeprefix - but masking in profiles -[21:39.51] (as most of devs will unmask it anyway) -[21:39.51] why not just remove it? -[21:40.01] I never mentioned removing kdeprefix! I mentioned "being available to my users" -[21:40.04] because we use live and stable right now -[21:40.04] :) -[21:40.10] yngwin: aside -[21:40.11] scarabeus / reavertm: what issues do you want to fix by masking it? -[21:40.15] with help of +kdeprefix -[21:40.27] The pykde conflict and? -[21:40.28] jmbsvicetto: update strategy, collisions, broken plugins, user confusion -[21:40.39] jmbsvicetto: just decrease ^^^ impact on average users -[21:41.08] ok, I've became tired of fighting this war -[21:41.23] I'll let anyone else take this one if they want -[21:41.39] i would more of like to convince you rather than tire you :] -[21:41.44] But, just for the record, my +kdeprefix laptop is working fine :P -[21:42.06] jmbsvicetto: yeah because me and reaver spent quite stuff on prefix stuff, and it is still not 100% -[21:42.07] :] -[21:42.16] scarabeus: As I've said before, the real solution is to fix upstream build system to allow co-existence of different versions side by side -[21:42.18] fist stuff was to be time -[21:42.23] jmbsvicetto: you're free to go with +kdeprefix if you fix qt plugin loader to not pick oxygen.so from current kde session (and plugin cache stored in .config/Trolltech.conf) instead of using kde4-config --qtplugins -[21:42.25] yes on that i agree -[21:42.41] jmbsvicetto: well we wont remove it -[21:42.42] jmbsvicetto: that's no longer build system issue -[21:42.44] just mask in profile -[21:42.47] anyone can enable it -[21:42.50] scarabeus: this way someone might feel "pressured" to start that work ;) -[21:42.58] they can coexist -[21:43.09] there's problem with plugin loader -[21:43.14] jmbsvicetto: yeah it might motivate pple to work on it so it will get unmasked -[21:43.14] reavertm: I mean having them on the same dir, not on separate prefixes -[21:43.17] and of course with .desktop files -[21:43.33] ok guys we are far away from the subject -[21:43.35] (they all have relative paths in Exec=) -[21:43.36] it is mask/not mask -[21:43.46] * jmbsvicetto abstains -[21:44.01] in current state kdeprefix is NO GO -[21:44.21] one can not like it, but this is the fact -[21:44.25] jmbsvicetto: you cant you are lead :D -[21:44.31] ok please -[21:44.34] !herd kde vote -[21:44.39] !herd kde -[21:44.40] bonsaikitten: what about you? -[21:44.48] i hate that bot -[21:44.50] seriously -[21:44.51] scarabeus: Willikins doesn't have +v -[21:44.53] scarabeus: give me a minute -[21:44.55] rotfl -[21:44.57] *** scarabeus sets mode: +v Willikins -[21:44.57] *** jmbsvicetto sets mode: +v wired -[21:44.57] I've spent already too many hours working on it - if anyone doesn't like it, I'll be happy to pass the work to him -[21:44.59] !herd kde -[21:44.59] (kde) alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, patrick, scarabeus, tampakrap, tgurr -[21:45.04] O;] -[21:45.13] scarabeus: Yeah, blame the bot ;) -[21:45.15] jmbsvicetto: I prefer kdeprefix, but I don't care enough to fight for it -[21:45.20] ok -[21:45.26] i vote the mask -[21:45.39] scarabeus: How do you plan to mask it? -[21:45.40] i vote for mask this crap! -[21:45.45] * wired votes on his dev bug -[21:45.48] :D -[21:45.50] jmbsvicetto: via use.mask -[21:45.55] globaly in profile in use.mask -[21:46.00] base/use.mask ? -[21:46.02] I vote to mask it (for now) -[21:46.03] yes -[21:46.14] Can users unmask it in /etc/portage ? -[21:46.18] yes -[21:46.19] yes -[21:46.21] as it should have been done at the same begin -[21:46.24] iirc, last time one would have to do it in profiles/ -[21:46.28] ok -[21:46.34] so it would still be available for those who really want it -[21:46.40] I can live with the mask then -[21:46.56] jmbsvicetto: to unmask, put "-kdeprefix" in /etc/portage/profiles/use.mask -[21:47.15] ABCD: ok, thanks -[21:47.15] ok somebody around whom didnt vote? -[21:47.22] ABCD: ssshh, users will hear it :P -[21:47.24] * jmbsvicetto notices Patrick didn't -[21:47.25] just make sure the whole thing is properly documented -[21:47.46] well the guide will be updated, at least tampakrap_ promised he will do it -[21:48.00] ABCD: it's profile, not profiles, IIRC -[21:48.07] ...right -[21:48.17] I blame my IRC client -[21:48.17] bonsaikitten: so say mask/notmask plz -[21:48.25] ;) -[21:48.50] directory name is profiles, but calling it 'profile' is common :P -[21:48.57] scarabeus: abstain -[21:49.04] *** himikof_ (n=himikof@129.167.249.ozerki.net) Quit (Read error: 104 (Connection reset by peer)) -[21:49.04] :DDDD -[21:49.06] reavertm: directory name is profie - I just checked -[21:49.06] ok -[21:49.14] profile* -[21:49.18] *** himikof_ (n=himikof@129.167.249.ozerki.net) has joined #gentoo-kde -[21:49.23] (ah, you mean the one in /etc/portage) -[21:49.28] yes -[21:49.34] it's profile -[21:49.37] ok then it will be masked in profiles -[21:49.38] nm, so results? -[21:49.40] per vote -[21:49.42] great :P -[21:49.58] alexxy: please do the change and according documentation update in the guide -[21:50.19] sweet -[21:50.31] Now I can stable kde with a clear conscience -[21:50.32] he he =) -[21:50.41] there should be information. about being unable to load oxygen.so and the need of wiping ~/.config/Trolltech.conf -[21:50.57] so tommorow i'll mask it via profile -[21:51.03] alexxy: okey -[21:51.05] and update guide -[21:51.06] =) -[21:51.10] so this topic is done :] -[21:51.17] * alexxy realy tired and gonna sleep -[21:51.24] next one because we ocupied 2 in the row is for qt herd -[21:51.29] topic: Handle the PyQt3 qscintilla dependencies -[21:51.31] (maybe remove all traces of kdeprefix from guide :) -[21:51.33] alexxy: gn -[21:51.44] yngwin: hwoarang ^ -[21:51.49] what about it? -[21:51.56] it is your topic -[21:51.58] messy -[21:51.59] no -[21:51.59] gn =) -[21:52.09] i guess the problem is sip and PyQt-3? -[21:52.11] nn alexxy -[21:52.16] nn alexxy -[21:52.18] Pesa: no -[21:52.27] pyqt3 requires qscintilla-python[-qt4] -[21:52.30] so what is the problem? -[21:52.36] whilst Pyqt4 requires qscintilla-python[qt4] -[21:52.41] no it doesnt -[21:52.47] sorry? -[21:52.48] :) -[21:53.05] PyQt4 does not hard depend on qscintilla -[21:53.15] indeed -[21:53.16] the other way around -[21:53.30] if any.. -[21:53.53] if some app needs qscintilla-python[qt4], yes then there will be a blocker -[21:54.07] *** SaCu (n=quassel@213-172-122-045.dsl.aktivanet.de) has joined #Gentoo-KDE -[21:54.08] this blocker does not exist right now -[21:54.47] sort of, as you can only have qt4 or -qt4 set on qscintilla-python -[21:54.55] so the problem is that you can't have both qt3 and qt4 qscintilla installed? -[21:55.00] ye -[21:55.01] indeed -[21:55.31] adding qscintilla-python[-qt4] on PyQt -[21:55.37] creates a kind of mess -[21:55.44] meaning you can only have PyQt and PyQt4 side by side as long as nothing needs qscintilla-python[qt4] -[21:55.47] well , a mess that users dont get it -[21:55.51] yes yngwin -[21:56.17] *** wilder (n=quassel@host126-104-dynamic.21-87-r.retail.telecomitalia.it) has joined #gentoo-kde -[21:56.22] now that qt3 is removed this should happen less frequently -[21:56.36] it's not removed -[21:56.46] spatz: this wont happen until 2010 -[21:56.49] it will be soon, i mean -[21:56.59] we will remove qt3 use flag from desktop profile and that is all -[21:57.05] removed from desktop profile -[21:57.17] ok -[21:57.28] but still , the blocker is there -[21:57.34] users can have qt3 on make.conf -[21:58.24] what's the problem here? python bindings collision? -[21:58.41] qt3 itself resides in separate prefix than qt4 -[21:58.52] no -[21:58.54] qscintilla-python is fine -[21:58.55] you can build qscintilla-python only for qt3 OR qt4 -[21:59.01] the problem is qscintilla iirc -[21:59.11] it's buildsystem doesn't allow that or what? -[21:59.28] file collisions -[21:59.48] the buildsystem is simply not designed to do that -[22:00.03] adjust the build system -[22:00.04] simple -[22:00.04] it may indeed by qscintilla itself, not the python bindings -[22:00.17] scarabeus: patches welcome -[22:00.33] guys it is your bug :D -[22:00.39] (a'ka gfy :) -[22:00.43] then i say: mask for removal :p -[22:01.15] it's qt3, it's deprecated, i dont want to waste time on it -[22:01.28] yngwin: well you are the boss -[22:01.34] yngwin: and if hwoarang agree... :] -[22:02.07] a real day issue is having amarok-1.4 and eric4 -[22:02.20] this sounds to me like the most common blocker -[22:02.25] there are just a few apps that use PyQt-3, most importantly amarok:3.5[python] -[22:02.28] *** jefferai (n=quassel@amarok/developer/mitchell) has joined #gentoo-kde -[22:02.30] yes -[22:02.38] amarok is the big pain atm -[22:02.48] and many many ppl are using it -[22:03.02] and what for are the python bindings -[22:03.10] scripts i suppose -[22:03.12] *** scarabeus sets mode: +v jefferai -[22:03.12] scripts afaik -[22:03.28] jefferai: by any chance you know how important are python bindings in amarok 1? -[22:03.32] hwoarang: amarok-1.4 can be deprecated after we get amarok-2 marked stable -[22:03.43] that will take a while -[22:03.48] indeed -[22:03.51] scarabeus: there are python bindings in amarok 1? -[22:03.59] :D -[22:04.20] guys this is statement from upstream dev -[22:04.21] :D -[22:04.28] so maybe we can mask python useflag in amarok-1* ? -[22:04.30] so i think when they dont care why should we :P -[22:04.37] well, I'd have to ask -[22:04.42] yngwin: yep that i was thinking about -[22:04.43] the fact that I'm not aware of them doesn't mean... -[22:05.03] jefferai: too late :P -[22:05.08] heh -[22:05.10] python masking sounds good to me -[22:05.12] that'll get more users annoyed than having problems with qscintilla, imo -[22:05.16] *** etix (n=etix@videolan/developer/etix) Quit (Remote closed the connection) -[22:05.18] *** etix (n=etix@nala.l0cal.com) has joined #gentoo-kde -[22:05.27] jefferai: too late, python use flag has already been taken to the alley and beaten up^Dmasked ;) -[22:05.30] or have the useflag renamed and disabled by default -[22:05.46] as globally python is enabled by profile -[22:05.48] what's this for? -[22:06.14] jefferai: some bindings probably :] -[22:06.19] hopefully just bindings -[22:06.30] oh -[22:06.31] jefferai: we have a conflict between dependencies of PyQt3 and PyQt4, and amarok-1 is the biggest consumer of PyQt3 it seems -[22:06.33] webcontrol -[22:06.42] bah -[22:06.46] I don't know of anyone using it -[22:06.50] at least, that I've ever heard -[22:07.02] it's some random script that allows web control of Amarok -- I guess -[22:07.17] *** genewbie (n=genewbie@cpe-76-172-51-77.socal.res.rr.com) has joined #gentoo-kde -[22:07.17] take a look in the ebuild -- just make sure you keep that rm for the webcontrol script in there -[22:07.24] so that people don't file bugs asking why it doesn't work/run -[22:08.08] we are still on the qscintilla topic? ;P -[22:08.23] yes -[22:08.35] :] -[22:08.36] okey -[22:08.51] *** pgega (n=pgega@77-99-66-168.cable.ubr01.tonb.blueyonder.co.uk) Quit (Client Quit) -[22:09.04] *** pgega (n=pgega@77-99-66-168.cable.ubr01.tonb.blueyonder.co.uk) has joined #gentoo-kde -[22:09.14] so i propose useflag s/python/webcontrol/ in amarok-1* ebuilds -[22:09.43] jmbsvicetto: ^ -[22:09.53] yngwin: I'd suggest dropping the python flag and removing the scrpit -[22:09.55] script* -[22:10.07] either way -[22:10.24] yngwin: I think we should start hinting that users should start moving to amarok-2 -[22:10.45] yeah 2.1 is already usable on same level i think -[22:10.55] as long as it's not stable... -[22:11.28] it will be next topic -[22:11.28] :D -[22:11.36] just finish with this one -[22:11.40] anyway, that will make things easier -[22:12.18] with that one done, what do we think of mutual blocking of PyQt and PyQt4 to prevent portage tripping over the deeper deps issue? -[22:12.28] *** gengor (n=gengor@gentoo/developer/gengor) has joined #gentoo-kde -[22:12.37] yep that is good idea -[22:12.40] yngwin: what apps will that mask? -[22:12.42] the block between them -[22:12.54] sorry guys, my connection is lagging a lot -[22:12.57] s/mask/cause slot blocks/ -[22:13.00] it won't mask anything, just force users to choose -[22:13.15] yeah, I meant what apps will be affected by that -[22:13.28] !rdep PyQt -[22:13.29] jmbsvicetto: Too many packages have reverse RDEPEND on dev-python/PyQt, go to http://tinderbox.dev.gentoo.org/misc/rindex/dev-python/PyQt instead. -[22:13.30] !rdep PyQt -[22:13.30] !rdep PyQt4 -[22:13.31] jmbsvicetto: Too many packages have reverse RDEPEND on dev-python/PyQt4, go to http://tinderbox.dev.gentoo.org/misc/rindex/dev-python/PyQt4 instead. -[22:13.31] yngwin: Too many packages have reverse RDEPEND on dev-python/PyQt, go to http://tinderbox.dev.gentoo.org/misc/rindex/dev-python/PyQt instead. -[22:13.37] :) -[22:13.44] *** tbeadle (n=quassel@division.aa.arbor.net) Quit (Client Quit) -[22:13.55] yngwin: sorry, feeling lazy today ;) -[22:14.06] kelogviewer, releaseforge, kanyremote -[22:14.07] no important crap expect amarok i think -[22:14.25] hmm, hplip :\ -[22:14.36] hplip also has qt4 option -[22:14.49] hplip has qt4 option (and I have it installed, so I know it works) -[22:14.58] yeah, sorry just noticed it -[22:15.02] i think there's a bug about the new hplip version not really having qt3 support -[22:15.23] he he -[22:15.24] :D -[22:15.50] *** wired|quassel (n=quassel@athedsl-290085.home.otenet.gr) has joined #gentoo-kde -[22:16.01] *** wired|quassel (n=quassel@athedsl-290085.home.otenet.gr) Quit (Client Quit) -[22:16.17] *** wired|quassel (n=quassel@athedsl-290085.home.otenet.gr) has joined #gentoo-kde -[22:16.40] jmbsvicetto: in case you didnt look yet: http://bugs.gentoo.org/chart.cgi?category=-All-&subcategory=-All-&name=320&label0=Kde-Charting&line0=591&datefrom=&dateto=&action-wrap=Chart+This+List -[22:16.41] so does anyone have anything against the blocker? -[22:16.48] no prob here -[22:16.51] *** Skim[ihz] (n=skim@skim.static.corbina.ru) Quit (Client Quit) -[22:16.56] it looks fine when i compared -[22:17.06] i am on board -[22:17.34] ok, let's do it then -[22:17.52] next topic :) -[22:18.02] okey qt team can touch the amarok for this one i assume ;] -[22:18.12] KDE 4 Stabilisation. -[22:18.15] quite big -[22:18.41] but the bugs are ok, and now we agreed masking the prefix useflag only thing that remains is the kde4 apps out of the kde4 session -[22:18.53] reavertm: how we are standing on that bug, i was not paying much attention to it lately -[22:19.02] scarabeus: hmm, should I get a chart? -[22:19.14] jmbsvicetto: yes for me it draws nice chart -[22:19.19] jmbsvicetto: open in anything else than FF -[22:19.28] and second thing is what version we will stable -[22:19.29] so it only fails on FF? -[22:19.30] 4.2 or 4.3 -[22:19.30] wow that is fail -[22:19.31] *** etix (n=etix@videolan/developer/etix) Quit (Client Quit) -[22:19.41] jmbsvicetto: yes -[22:19.42] I'd say it depends when we get it done -[22:19.53] For the next 2 months I would bet on 4.2.4 and or 4.2.5 -[22:19.59] jmbsvicetto: well i am testing the 4.2.91 and i am damn impressed -[22:20.02] they would work with kdeprefix if qt plugin loader wasn't affected - with -kdeprefix (and ~.config/Trolltech.conf wiped out) they are fine -[22:20.23] another issue is with kde3 .desktop icons in kde4 session -[22:20.38] scarabeus: Yeah, but it's too early for it -[22:20.42] the guys are really working their asses to make it nice -[22:20.43] currently nothing is shown (because nothing would work) -[22:20.49] well it will be in 1 month around -[22:20.58] scarabeus: I guess users that have been waiting for 2 years, can wait another month or two for 4.3 ;) -[22:20.59] and you'll have to wait a month to stabilize it -[22:21.00] also the printing dialog is tempting -[22:21.14] jmbsvicetto: ok should we vote on the thing or we agree -[22:21.19] reavertm: what do you think :] -[22:21.40] scarabeus: does that printing dialog work for you? -[22:21.46] reavertm: nope ;D -[22:21.47] I guess I'll make an "executive decision" on this one :P -[22:21.48] (crashes in my cheoot) -[22:21.54] it says that it hate me -[22:21.58] it cant chat with cups -[22:22.02] scarabeus: printing is deferred until fixed :P -[22:22.04] even tho i am able to print -[22:22.18] jmbsvicetto: okey so decide -[22:22.29] (so no go for system-config-printer-kde and printer-applet) -[22:22.30] jmbsvicetto: fine with me you are elected lead, so you choose global policy:] -[22:22.41] 4.2.[4|5] for the next 2 months - after that we can talk about 4.3 -[22:22.42] reavertm: they are already in the tree by accident ;DDD -[22:22.53] well, masked they can be -[22:22.58] reavertm: some looser already opened bug about it has missing deps ;D -[22:23.08] because movetocvs just grab everything with nice version :D -[22:23.08] good -[22:23.21] scarabeus: we should also open the bug asap -[22:23.26] jmbsvicetto: ok whom will handle stabling of 4.2 then -[22:23.57] *** ebola_ (i=ebola@S0106066606660666.su.shawcable.net) has joined #gentoo-kde -[22:24.01] what is blocking it? -[22:24.10] most of kde4 issues -[22:24.10] the above thng only -[22:24.11] *** Skim[ihz] (n=skim@skim.static.corbina.ru) has joined #gentoo-kde -[22:24.12] :P -[22:24.23] running the kde4 apps out of the kde4 session -[22:24.25] kde-print? -[22:24.28] ah -[22:24.29] but it should be addressed already -[22:24.30] also kdm crashes -[22:24.40] yeah kdm is weird crap with -O3 -[22:24.53] scarabeus: KDE has had issues with -O3 since ever -[22:25.01] without -O3 as well (but works with new user) -[22:25.02] scarabeus: If you look in bugzilla there were a few reports about that -[22:25.13] *** ebola_ (i=ebola@S0106066606660666.su.shawcable.net) has left -[22:25.16] reavertm: are you sure it's not a graphics driver issue? -[22:25.19] *** InvaderNOP (i=ebola@S0106066606660666.su.shawcable.net) has joined #gentoo-kde -[22:25.28] if it works with new user... -[22:25.41] yeah, hmm config option? -[22:25.46] like? -[22:25.55] *** Civil (n=Civilian@95-24-130-90.broadband.corbina.ru) Quit (Remote closed the connection) -[22:26.02] anyway, stabilization bug could be opened to track issues -[22:26.09] tracker bug -[22:26.13] let's open the tracker then -[22:26.15] 1 for tracking 2 for stabling -[22:26.17] personally I wouldn't hurry with stabilization -[22:26.23] but whom will wrangle the stuff -[22:26.31] i guess tampy wont do second round -[22:26.33] everyone :P -[22:26.33] :] -[22:26.55] I suppose you want someone with -kdeprefix O:-) -[22:27.02] *** andreax (n=andreaz@p57B951A2.dip.t-dialin.net) has joined #gentoo-kde -[22:27.24] GRM -[22:27.37] btw i noticed sabayon is on +kdeprefix -[22:27.38] i am definetly sure that i will still target on closing bug than on wrangling them -[22:27.41] I'd take commit count :D -[22:27.47] i am allways depressed about wrangling -[22:28.06] yngwin: 5.0 branch is -kdeprefix -[22:28.09] scarabeus: oh, looking at bugs? we can all do it -[22:28.16] remember that we cooperate at sabayon -[22:28.18] ok good -[22:28.26] s/at/with/ -[22:28.34] yes, thats why i mentioned it -[22:28.37] !seen joost-op -[22:28.39] scarabeus: nope! -[22:28.53] !seen joost_op -[22:28.54] scarabeus: joost_op was last seen 4 days, 45 minutes and 54 seconds ago, quitting IRC (Remote closed the connection) -[22:29.28] i already discussed with him about it :] -[22:29.31] so problem solved :] -[22:30.03] ok i think we have stuff that is needed to be done -[22:30.15] and i guess each of us can wrangle some itching bug -[22:30.25] i think everything above normal must be assinged there -[22:30.25] *** haavardw (n=haavardw@cm-84.208.110.202.getinternet.no) Quit (Remote closed the connection) -[22:30.33] and rest is up to our decision -[22:31.26] anything else to this topic? -[22:31.28] *** ABCD (n=ABCD@wikipedia/ABCD) Quit (Client Quit) -[22:31.32] *** ABCD (n=ABCD@wikipedia/ABCD) has joined #gentoo-kde -[22:31.37] hmm,m what about phonon? -[22:31.38] *** scarabeus sets mode: +v ABCD -[22:31.44] already stable -[22:31.46] it will be blocker for 4.3 I guess -[22:31.57] ah this -[22:32.07] it is not issue for 4.2 stable bug for now -[22:32.17] even if we might transcendent to 4.3 it can be address later -[22:33.34] ok since everyone is silent lets go with next topic -[22:33.37] topic: Review the useflags we enable by default in qt herd -[22:33.44] yngwin, hwoarang: ^ -[22:33.51] (and in kde as well :P) -[22:33.59] i think the +gtkdialog is FKHE#(*%$YU#HR$(*%W#URJTN stupid -[22:34.03] it pulls gtk -[22:34.07] and that pulls X -[22:34.10] on -X install -[22:34.15] gtktheme you mean? -[22:34.16] so instead of 17 deps you have 55 -[22:34.20] oh theme right -[22:34.38] gtkstyle -[22:34.45] ah -[22:34.54] what ever ;] -[22:35.14] but that's in qt-gui which needs X anyway -[22:35.25] :) -[22:35.49] *** bbroeksema (n=bbroekse@cust-02-5286b4cb.adsl.scarlet.nl) Quit (Remote closed the connection) -[22:35.57] there's another topic in the agenda about this btw -[22:36.01] we could rename that to gtk, so it only get enabled by default in desktop profile -[22:36.17] was just about to say that -[22:36.22] Pesa: which one -[22:36.31] review the useflags we enable by default in qt herd -[22:36.33] rename to gtk and not have it on by default -[22:36.38] *** B-Man1 (n=B-Man@cpe-098-024-241-139.ec.res.rr.com) Quit (Client Quit) -[22:36.45] Pesa: thats what we're discussing now -[22:36.52] *** B-Man (n=B-Man@cpe-098-024-241-139.ec.res.rr.com) has joined #gentoo-kde -[22:37.05] ha -[22:37.09] i failed -[22:37.09] :P -[22:37.17] i'm getting angry with my ISP -[22:37.33] do we really need to enable something by default? -[22:37.37] but gtk isn't the only issue, also dbus, glib, qt3support and others -[22:37.44] they're all enabled by default -[22:37.54] dbus is already on profile -[22:37.56] qt3support disable guys i think -[22:38.01] glib can be disabled too -[22:38.06] i live without the later -[22:38.15] i cant recall why glib is on -[22:38.16] and the former we demand on kde but otherwise it is not needed right? -[22:38.29] i think -[22:39.08] the default should be off by default unless there's a good reason, not the way it is right that almost everything is on by default, IMHO -[22:39.20] i'm talking about all qt-* useflags -[22:39.36] yes -[22:39.39] the reasoning why i enabled most of those is to have the default qt4 install have all the functionality that most users would want -[22:40.04] define: all the functionality -[22:40.05] most users of qt will have a desktop profile and/or have all the useflags they want enabled -[22:40.05] :P -[22:40.26] desktop profile enables most of them anyway -[22:40.42] i would suggest remove all + and see what it does -[22:40.48] and introduce only where really needed -[22:40.49] yes, so we can drop those that the desktop profile enables -[22:40.54] re-introduce -[22:40.57] the current behavious is useless to the average user and annoying to those actually having a benefit from split ebuilds -[22:40.59] qt3support is enabled by desktop -[22:41.10] useless?? -[22:41.10] scarabeus: I don't quite agree -[22:41.24] yes, because he has those useflags enabled anyway -[22:41.30] jmbsvicetto: see above -[22:41.32] scarabeus: default use flags allow us to drop most use flags from profiles -[22:41.33] it doesn't affect him at all -[22:41.34] jmbsvicetto: the flag is in profile -[22:41.41] more superfluous than useless -[22:41.47] i was damn angry having +qt3support on sever -[22:41.51] yes -[22:41.53] so i had to edit useflag list -[22:41.56] bad choice of words -[22:42.06] spatz: nothing prevents you from adding - to your /etc/portage/package.use[/*] config file(s) -[22:42.34] mm -[22:42.46] of course, but useflags should be opt-in, not opt-out in the general case -[22:42.48] scarabeus: yes, but instead of removing default use flags because they're enabled on profiles, we should be dropping use flags from profiles and moving them to default use flags -[22:43.03] so let's drop the + on the useflags that are already in profiles -[22:43.11] +1 -[22:43.12] that would be a good start -[22:43.13] jmbsvicetto: really? why? -[22:43.15] and rename gtkstyle to gtk -[22:43.24] *** Kame2 (n=manuel@port-92-196-126-246.dynamic.qsc.de) Quit (Remote closed the connection) -[22:43.36] because that would prevent users from getting all the crap they get from profiles with ton of use flags like qt, kde, gtk or gnome -[22:43.45] tons* -[22:43.46] jmbsvicetto: i really like that i have different useflags on case like server/desktop based on profile -[22:44.01] and for the qt it really made me sad -[22:44.02] yeah, but desktop profiles currently have too many use flags -[22:44.25] maybe the desktop profile needs to be split, but that's out of scope -[22:44.28] scarabeus: the first thing I add to my servers is USE="-X -gtk -gnome -kde -qt" ;) -[22:44.39] yeah yeah but i need qt on mine server -[22:44.40] maybe desktop profile should be divided into subprofiles -[22:44.43] quassel ;\ -[22:44.45] ;] -[22:45.10] so? -[22:45.10] No, I don't think it's out of scope. Instead of spliting profiles or moving flags from packages to profiles, I think we should be going the other way around and dropping use flags from profiles back to packages -[22:45.16] and you shouldn't use the desktop profile on your server :) -[22:45.19] you can still have quassel with -qt -[22:45.42] jmbsvicetto: mail the idea to the -dev :] -[22:45.42] per profile is more appropriate than per package -[22:45.45] spatz: I don't use the desktop profile on my workstations ;) -[22:45.45] jmbsvicetto: well, that's stuff for a wider policy discussion -[22:45.51] that was also agreed last week on -dev, iirc -[22:45.56] yngwin: indeed -[22:46.08] that's what i meant by "out of scope" -[22:46.16] *** scarabeus sets mode: +v wired|quassel -[22:47.07] Anyway, I think kde should retain default use flags for most optional support features that upstream enables by default -[22:47.26] well, i dont have a string preference here, but it looks like my qt brothers do -[22:47.32] strong* -[22:48.10] http://archives.gentoo.org/gentoo-dev/msg_d676d199747afac881bbf444dac478ea.xml -[22:48.48] ok lets continue this topic there -[22:48.56] rather on the meeting :] -[22:49.16] wired: are you around? -[22:49.25] yes -[22:49.33] * bonsaikitten gone -[22:49.34] *** geo27 (n=quassel@lns-bzn-30-82-253-130-209.adsl.proxad.net) Quit (Remote closed the connection) -[22:49.36] jmbsvicetto: upstream enabled by default everything that's autodetected -[22:49.39] wired: did you tracked the tampakrap what he is doing with kde3? -[22:49.48] hence, it's bad approach imho -[22:49.50] only the eclass part -[22:49.53] ah -[22:49.59] scarabeus: btw i talked to him a few minutes ago -[22:50.04] *** geo27 (n=quassel@lns-bzn-30-82-253-130-209.adsl.proxad.net) has joined #gentoo-kde -[22:50.05] where is he -[22:50.10] he missed the meeting because he was traveling to athens -[22:50.19] and can he get online now? -[22:50.24] only to give us status info? -[22:50.32] /report -[22:50.33] hmm -[22:50.39] let me call him and ask -[22:50.42] 1min -[22:50.51] yngwin: so let's do what you decided and check back in while -[22:51.27] reavertm: They don't autoenable everything -[22:51.31] jmbsvicetto: they do -[22:51.36] gtkstyle->gtk, remove default on all flags enabled in desktop profile -[22:51.37] scarabeus: he'll be in here in 15m -[22:51.38] jmbsvicetto: if they detect package, they enable it -[22:51.44] reavertm: For instance kopete doesn't enable by default all protocols and plugins -[22:51.47] do we change them now or on next release? -[22:51.56] there are some exceptions, yes -[22:51.59] *** mrpouet (n=mrpouet@gentoo/developer/mrpouet) Quit (Client Quit) -[22:52.00] ok guys how much you want to read last topic -[22:52.19] scarabeus: ok? =] -[22:52.33] wired: well it depends on others -[22:52.41] i cant hold them here for another 20 minutes ;] -[22:52.45] yngwin: would that require re-stabilizing? -[22:52.46] the meeting already lasts 2 hours -[22:53.02] hmm, good question -[22:53.03] spatz: nope, archies are supposed to test various use flags -[22:53.13] wired: he can login when he can and put a short status message here -[22:53.21] so i guess not :) -[22:53.29] if not than we should do it now, imo -[22:53.36] otherwise we'll forget :) -[22:53.37] *** hkBst (n=hkBst@gentoo/developer/hkbst) Quit (Read error: 104 (Connection reset by peer)) -[22:53.40] *** himikof_ (n=himikof@129.167.249.ozerki.net) Quit (Remote closed the connection) -[22:53.55] 4.5.2 shouldn't be too far -[22:53.58] *** NSaibot (n=quassel@dslb-094-217-110-040.pools.arcor-ip.net) has joined #gentoo-kde -[22:53.58] in that case we can also drop custom-cxxflags useflag as we decided before -[22:54.02] yngwin: it can change the installed package, so it should go through the revbump process -[22:54.20] ok -[22:54.23] then wait for 4.5.2 -[22:54.31] i agree -[22:54.37] for everything or just custom-cxxflags? -[22:54.42] everything -[22:54.42] everything -[22:54.55] ok -[22:55.27] of course we can already do it in the overlay, where applicable -[22:55.29] next topic? -[22:55.43] *** bearsh (n=quassel@80-219-1-239.dclient.hispeed.ch) Quit (Remote closed the connection) -[22:55.45] btw, what about libX11 dep in qt-core? -[22:56.02] that's good to go into the tree -[22:56.20] should we do the same for qt-dbus? -[22:56.21] those deps should be added to qt-gui and friends, no? -[22:56.35] ah good call -[22:56.35] Pesa: it works for me -[22:56.48] can you commit to overlay? -[22:56.53] those that do depend on libX11 and libXext should get it -[22:57.16] make sure all modules are ok and checked for those -[22:57.34] *** himikof_ (n=himikof@129.167.249.ozerki.net) has joined #gentoo-kde -[22:57.35] *** DeSoVoDaMu (n=deso@77-21-66-33-dynip.superkabel.de) Quit (Read error: 113 (No route to host)) -[22:58.03] i might not have time to do it in the overlay because of my exams :/ -[22:58.10] so we need to revbump those packages anyway -[22:58.54] then we might as well do the useflag change, unless 4.5.2 is released very soon -[22:59.04] right -[22:59.18] ok, great -[22:59.55] *** papillon81 (n=papillon@f053145102.adsl.alicedsl.de) has joined #gentoo-kde -[23:00.05] scarabeus: shall we close the meeting then? -[23:00.06] *** scarabeus sets mode: +v papillon81 -[23:00.18] well we can wait 8 minutes and tampy will be here -[23:00.23] it is up to you -[23:00.31] you forget he's greek -[23:00.42] for what topic? (i forgot) -[23:00.43] what does it mean -[23:00.51] Progress of kde3 mess and way how anyone can help (here we call even for non-kdeteam devs) -[23:00.52] 8 minutes could mean anything -[23:01.23] *** scarabeus sets mode: +v wohnout -[23:01.33] *** Gabrys (n=Gabrys@77-254-190-150.adsl.inetia.pl) has joined #gentoo-kde -[23:02.02] wired: ok tell him not to rush, and he will have to sent us the mail onto the kde@ and qt@ alliases or onto -desktop -[23:02.24] ok i hereby close the meeting -[23:02.30] and btw someone create log -[23:02.30] well he should be here shortly, but ok :) -[23:02.36] *** scarabeus sets mode: -m -[23:02.55] i'm here -[23:02.57] aghr -[23:02.59] *** tampakrap_ is now known as tampakrap -[23:03.02] you are joking :D -[23:03.04] lol -[23:03.05] *** scarabeus sets mode: +m -[23:03.06] no i am here -[23:03.15] welcome :) -[23:03.15] yeah i see :] -[23:03.16] ok -[23:03.33] welcome indeed -[23:03.34] what's the deal -[23:03.36] ? -[23:03.41] lol -[23:03.48] kde3 -[23:03.54] we want to know -[23:03.59] Progress of kde3 mess and way how anyone can help (here we call even for non-kdeteam devs) -[23:04.00] state/progress what is to be done -[23:04.02] what is done -[23:04.16] ok -[23:04.31] kde3 misc apps need slotmove and stabilization this will take some time -[23:04.34] as i have no help -[23:04.35] yngwin: hehe -[23:04.39] Heya Theo -[23:04.44] koffice is my playground, i'll fix eclass -[23:04.47] tampakrap: hey i did about 5-10 apps -[23:04.51] *hello hello* -[23:05.00] not the stabilization part though -[23:05.07] so i still have to take care of the list -[23:05.13] and kde-base/*3.5.10* -[23:05.20] has many *stupid* bugs -[23:05.22] tampakrap: i would suggest to switch all misc apps -[23:05.25] that i have no motivation to fix -[23:05.26] and then open 1 stable bug -[23:05.33] this can't be done -[23:05.40] they don't have the same keywords -[23:05.40] why not -[23:05.44] no problem -[23:05.45] and it is against the rules :) -[23:05.48] just make list for each arch -[23:06.02] we do it in X when we stable all the stuff -[23:06.09] this isn't easier for me -[23:06.13] okey -[23:06.16] as pleases you -[23:06.19] since you do the work -[23:06.20] i slotmove package, check bugs and open bug -[23:06.34] anything else? -[23:06.41] what did you say about the stabilization? -[23:06.44] of kde4 -[23:06.55] KDE 4 Stabilisation. -[23:06.55] - Jorge decided to start with 4.2 stabilisation. -[23:06.55] - stabilisation bug will have to be opened -[23:06.55] - tracking bug will have to be opened and bugs wrangled (volunteers??) -[23:06.59] this is summary -[23:07.08] ok -[23:07.11] we need tracker again -[23:07.18] ah how about asking for help with kde3 misc stuff on -dev -[23:07.25] *** Skim[ihz] (n=skim@skim.static.corbina.ru) Quit (Client Quit) -[23:07.26] i volunteer with bug wrangling -[23:07.37] ssuominen did probably great job with removing arts usefla -[23:07.38] g -[23:07.44] how is its progress -[23:07.49] *** scarabeus sets mode: +v ssuominen -[23:07.59] well we can say that kde3 is *open* for anyone -[23:08.09] media-sound cat. is clear of all arts deps -[23:08.10] !rdep arts -[23:08.10] scarabeus: Too many packages have reverse RDEPEND on kde-base/arts, go to http://tinderbox.dev.gentoo.org/misc/rindex/kde-base/arts instead. -[23:08.14] media-libs half way -[23:08.14] not for maintaining but for random bugfixing -[23:08.16] *** [Enrico] (n=chiccoro@host224-36-dynamic.16-79-r.retail.telecomitalia.it) Quit (Read error: 104 (Connection reset by peer)) -[23:08.21] media-video undone -[23:08.31] 785 packages -[23:08.34] * scarabeus is sad -[23:08.41] the media-sound apps left on the list are masked for removal or similar -[23:08.43] yeah -[23:08.51] *** g1lt (n=quassel@203-79-94-158.cable.telstraclear.net) has joined #gentoo-kde -[23:08.52] just set allways arts never when there is optional in ebuild in eclass? -[23:08.56] that might close few? -[23:08.57] there's lots to be done, i can handle it by opening some bugs for teams -[23:09.05] to speed it up -[23:09.20] did similar when i killed gtk+-1.2 from 50%+ pkgs the another summer -[23:09.24] :P -[23:09.32] death to arts -[23:10.09] can we quick vote on "let's remove arts from use defaults immediately?" -[23:10.12] ;) -[23:10.19] ssuominen: voted allowed already -[23:10.21] just do it -[23:10.24] * ssuominen does -[23:10.35] ssuominen: will you be our asignee for arts thing? you seems to enjoy it ;} -[23:11.49] don't mind handling it so why not -[23:11.56] okey -[23:12.04] i will sent you the eclass update then -[23:12.08] for arts removal -[23:12.18] btw how much packages probably has arts HARDDEP? -[23:12.21] can it be found out? -[23:12.22] over the half way, there will always be a maintainer or two who attacks you for removings on false grounds (hit few of those on the gtk+-1.2 road) -[23:13.04] you see how much it hurts mine heart? ;] -[23:13.05] well in media-sound i've fixed about 50% pkgs to not dep on arts anymore -[23:13.08] so painfull ;] -[23:13.10] it was totally false -[23:13.29] well they can state it to us, probably anouncal on -dev might be good -[23:13.30] and removed about the optional dep on 25% and remaining 25% got punted -[23:14.13] but i guess there's no hurry -[23:14.21] but giving it a small boost won't hurt -[23:14.23] ;) -[23:14.24] yes -[23:14.26] :] -[23:14.48] *** mikkoc (n=mikko@host161-90-dynamic.0-87-r.retail.telecomitalia.it) Quit (Remote closed the connection) -[23:14.52] *** Devrethman (n=quassel@209.90.234.102) has joined #gentoo-kde -[23:15.29] anything else we have for kde3? -[23:15.37] *** YaCK (n=brayan@unaffiliated/yack) Quit (Client Quit) -[23:15.38] kill it? -[23:15.48] *** geo27 (n=quassel@lns-bzn-30-82-253-130-209.adsl.proxad.net) Quit (Remote closed the connection) -[23:16.13] look ppl i told you i have no motivation in this thing any more, what i did was to make sure it can work with kde4 -[23:16.29] tampakrap: ok we should recruit someone for that -[23:16.41] since this thing works, we have to tell ppl *asap* that we have no motivation for maintaining it any more -[23:16.43] tampakrap: i really agree that you dont have to push it so hard forward if you dont have the motivation -[23:16.49] it started not to compile you know :) -[23:17.02] And to have security issues! -[23:17.04] tampakrap: open the requirement on the stuffing needs -[23:17.18] scarabeus: nope, add it to our project page -[23:17.19] no, no, kde3 doesn't need maintainer -[23:17.25] it would be best to have it handled by some dev determined to stay with kde3 -[23:17.29] just various bugfixing by ppl who use it -[23:17.43] yeah somebody determined using it would be nice -[23:17.43] at least in kde team there is none... -[23:17.49] :) -[23:17.52] well carlo... -[23:17.58] last seen on february -[23:18.09] when he broke quite few packages with wrong eapi2 bump -[23:18.45] well, nobody is as experienced in eapi2 bumps like we are :P -[23:18.49] so we reaaaally need someone -[23:18.52] reavertm: yeah :D -[23:18.57] we are masters :D -[23:19.07] *** Skim[ihz] (n=skim@skim.static.corbina.ru) has joined #gentoo-kde -[23:19.21] sping is interested -[23:19.40] who is sping -[23:19.44] where is sping -[23:19.51] give us sping! -[23:19.53] jmbsvicetto: will you use your hat and send an email to -dev plz? -[23:19.59] sebastian ping, currently doing GSoC -[23:20.02] scarabeus: just drop 'packages up for grab' list on gentoo-dev with `200 kde3 ebuilds that kde team doesn't care about anymore :D -[23:20.07] *** sean345 (n=sean345@c-76-105-5-254.hsd1.ca.comcast.net) has joined #gentoo-kde -[23:20.10] *** BCMM (n=bcmm@unaffiliated/bcmm) has joined #gentoo-kde -[23:20.16] rofl -[23:20.21] jmbsvicetto: could we do it? -[23:20.22] :DDDDDD -[23:20.27] pipping* -[23:20.38] *** Varox (n=Varox@p4FD46B43.dip.t-dialin.net) has joined #gentoo-kde -[23:20.38] the PackageMap guy -[23:20.48] oh i see -[23:20.54] and is he on irc from time to time? -[23:21.07] yes -[23:21.12] but i assume he is uberbusy with gsoc on the other hand -[23:21.17] yes -[23:21.30] he will return to recruitment after gsoc -[23:22.17] tampakrap: about kde3? ok -[23:22.39] jmbsvicetto: wait for summary i have 2 mails for you probably :D -[23:22.39] scarabeus / reavertm: no :\ -[23:23.02] ok we are probably done about the topic for now, at least until gsoc is over -[23:23.05] no (no we can't drop kde3 on maintainer-needed) -[23:23.17] that was joke :) -[23:23.31] i can supervise the commits -[23:23.34] jmbsvicetto: it was really joke :] -[23:23.41] *** spatz (n=spatz@unaffiliated/spatz) Quit (Remote closed the connection) -[23:23.44] but for bugfixing i doubt it -[23:23.57] ok i anounce the meeting over then :] diff --git a/meeting-logs/kde-project-meeting-log-20090820.txt b/meeting-logs/kde-project-meeting-log-20090820.txt deleted file mode 100644 index ad6bf17..0000000 --- a/meeting-logs/kde-project-meeting-log-20090820.txt +++ /dev/null @@ -1,545 +0,0 @@ -[20:55:28] 57 secs -[20:55:40] =] -[20:56:45] okey -[20:56:50] i guess we will have to wait -[20:57:05] since 3 devs; 2 hts and 2 exherbos are not exactly desired combo -[20:57:18] I'm here -[20:57:19] lol -[20:58:00] --> bonsaikitten (i=quassel@gentoo/developer/bonsaikitten) has joined #gentoo-meetings -[20:58:02] --> dagger (n=quassel@gentoo/developer/dagger) has joined #gentoo-meetings -[20:58:12] that helped... a bit :) -[20:58:23] --> yngwin (n=yngwin@gentoo/developer/yngwin) has joined #gentoo-meetings -[20:58:25] --> Ingmar (i=ingmar@exherbo/developer/ingmar) has joined #gentoo-meetings -[20:58:33] --> ayoy (n=ayoy@cs78245237.pp.htv.fi) has joined #gentoo-meetings -[20:58:43] here -[20:59:10] ok -[20:59:14] looks better :] -[20:59:19] so for the tampakrap -[20:59:21] http://www.pastebin.cz/b594e8e991906a -[20:59:30] i count him as excuses due to personal matters -[20:59:41] --> Gentoochild (n=bla@vpn5.rz.tu-ilmenau.de) has joined #gentoo-meetings -[20:59:43] please read the above paste -[20:59:50] pesa has no internet currently -[21:00:35] and ayoy is being grilled by his recruiter -[21:01:03] ok -[21:01:16] anyone said that he will be late? -[21:01:32] otherwise i just wrote up our roll-call, i count everyone whom joined as here -[21:01:34] not that i know -[21:01:42] ok -[21:02:08] ok so i would say lets start with topic 1 -[21:02:12] i'm having a headache, so i'd like to keep this short on my end -[21:02:37] for that i count as relevant tampakraps opinion, and reavertm's they are the last one working on it -[21:02:51] so since tampakrap said it in mail i would ask reavertm if he has something to add -[21:02:52] scarabeus: I'll talk to tampakrap, but 2 things about the KDE3 overlay -[21:03:07] scarabeus: 1. Let's call it kde-junk, kde-sunset, or something like that. -[21:03:27] jmbsvicetto: no problem i have all powers about gitosis -[21:03:36] scarabeus: 2. We can't drop any ebuilds from the tree before at least the end of the year -[21:03:37] just sent me after decided name -[21:03:51] with 2 i agree -[21:03:56] The reason is that we shouldn't tie an overlay to a specific kde version -[21:03:57] i would start it after 4.4 -[21:04:01] if nothing evil happen -[21:04:17] At least not before we get 2 KDE4 minor versions marked stable -[21:04:22] I is here, mostly :) -[21:04:38] So if we got 4.2 and 4.3 marked stable, then we could consider dropping 3.5 from the tree -[21:04:38] we'll probably need an announcement and a news item and any other possible means of communication to alert current kde3 users that they have to add the overlay if they want kde3 -[21:04:59] a few months before we remove it -[21:05:04] that is simple news item -[21:05:13] ad it can go hand in hand with mask :] -[21:05:23] i think 3 month mask for this is good idea :] -[21:05:26] I think we should make such news after first kde4 goes stable -[21:05:32] its simple but it can also be devastating if we forget :p -[21:05:44] and before i forget "DID ANYONE FIND SOME CONTRIBUTORS?" -[21:06:10] I suppose we'll find some gentoo devs still with 3.5 -[21:06:13] iirc sping showed some interest before the summer -[21:06:37] he's resuming recruitment process now -[21:07:00] will you talk to him and find out? -[21:07:07] *mind -[21:07:08] i can yes -[21:07:28] I don't know if my opinion counts, but I really agree to dagger, you should announce that even befor kde4 is marked as stable. It may be very painful for some users to make the change. -[21:07:49] he has point ^ -[21:08:16] scarabeus: kde3 packages moved to overlay won't be subject of package.mask, will they? -[21:08:17] some people dont like kde4 and we wont change it. We just need to make sure they've got enough time to get use to overlay -[21:08:28] (they shouldn't imho) -[21:08:29] we just need to make sure that people will have the overlay added before we remove the ebuilds -[21:08:32] reavertm: wont -[21:08:39] and i agree we reavertm we shouldnt mask it -[21:08:40] I would suggest announcing loudly and often, in many venues so that (hopefully) very few users are taken by suprise -[21:08:41] (just have keywords dropped probably) -[21:08:44] and it needs to be stable before it is marked stable -[21:08:46] scarabeus: news item, planet blog entries, forums thread, front page announcement, ... ;) -[21:09:04] jmbsvicetto: sounds good -[21:09:40] jmbsvicetto: can you do it, please please our PR farry -[21:10:22] i'd wait with too widespread announcements until there is a stable candidate -[21:10:45] indeed -[21:11:00] well i was not saying NOW i mean when the time will come -[21:11:04] (which movesus towards second topic) -[21:11:04] that moves us to point no 2 -[21:11:25] wait a bit, i have one problem with kde3 -[21:11:44] i have seen that debian ship more patches marked as security for kde3 than we even have as bugs -[21:11:55] --> ahf (i=ahf@irssi/staff/ahf) has joined #gentoo-meetings -[21:12:14] we need people now to start maintaining kde3 -[21:12:49] or mask it right after we stable first kde4, dont say remove just mask for sec-issues -[21:13:17] kde3 is dead end. I think we need to decide how long are we going to maintain it -[21:13:26] users wont be happy, but i have to agree -[21:14:04] I'd suggest faster gentoo stable releases so that we can keep up with stable version being the one actually yet supported by upstream -[21:14:08] i think we can write some news item onto the homepage/spread as news -[21:14:20] and if noone will volunteer to work on it in 7 days... -[21:14:22] for example 4.2 branch is no longer mainataned... -[21:14:26] scarabeus: ok -[21:14:30] scarabeus: About the news -[21:14:48] i agree, we need to recruit kde3 maintainers immediately -[21:14:49] --> tampakrap (n=tuxicity@gentoo/developer/tampakrap) has joined #gentoo-meetings -[21:15:04] tampakrap: you, here, how, why -[21:15:11] go home! -[21:15:14] just for logs bye -[21:15:14] reavertm: What do you mean about the package.mask? Do you mean masking KDE3 ebuilds now or after they're moved to the overlay? -[21:15:16] ^^ -[21:15:58] jmbsvicetto: he was worried if we would keep the mask in tree after we move it to the overlay, which is NO -[21:16:13] what scarab said -[21:16:19] if we mask it, we might as well move it -[21:16:40] scarabeus / reavertm: I see and I agree with you - no -[21:16:55] no, users sometimes hate overlays, unmasking is simple -[21:17:00] or we actualy can let them decide -[21:17:10] But we shouldn't mask it until some time after we get KDE-4 marked stable -[21:17:14] i would start with the anouncing call for maintainers on homepage and on all pcs -[21:17:27] then we will know if someone cares -[21:17:32] we can recruit the peeps -[21:17:35] we have the powah -[21:17:37] :] -[21:17:37] I'm sorry, but half my brain is being pulled to #gentoo-userrel -[21:17:55] jmbsvicetto: yes that we mentioned too, after at least 1 kde4 stabled -[21:18:48] but if there are security issues that nobody is fixing, we may need to mask earlier -[21:19:04] jmbsvicetto: anouncement on homepage and as newsitem if noone reply in timely manner (week) then after -[21:19:04] kde4 is stabilised we will right away mask it as security threat. then it will live until -[21:19:04] kde4.4 but masked/or in overlay (to be decided). -[21:19:16] this is my braindead summary -[21:19:51] agreed -[21:19:55] I would say make kde4.a stable, than make kde4.b stable and mask kde3 -[21:20:23] unless critical bugs will force us to make it earlier -[21:20:30] dagger: there must be security ones -[21:20:32] mask* -[21:20:49] just browse debian patches -[21:20:51] another thing to consider when ditching KDE3 is whether all kde3 apps are available for kde4 (like k3b) -[21:21:06] k3b for kde4 works perfectly -[21:21:10] Gentoochild: security has privilege -[21:21:13] (was jsut an exampolke) -[21:21:14] dagger: not really -[21:21:14] mythtv seems to be a problem -[21:21:30] I wonder whether leaving kdelibs:3.5 + some apps would be a problem -[21:21:32] reavertm: I'm using it 2-3 times a week for cd dvd5/9 - all fine -[21:21:43] reavertm thats what i was thinking as well -[21:22:00] maybe we can leave kdelibs3 and a few apps around for a little longer (like +6 months) -[21:22:10] yngwin: I wouldn't mask it, but after we get one KDE4 version marked stable, we should start warning users *publicly* to the status of KDE3 security -[21:22:13] dagger: try writing udf image wth verify - it will lock on 50% on disk eject, but that's off topic -[21:22:29] jmbsvicetto: what are those security issue? khtml? -[21:22:37] yngwin: If that upsets upstream, I don't care. Maybe it might lead someone to start fixing issues -[21:22:41] reavertm: khtml as starters -[21:22:42] jmbsvicetto: no it's very simple: if there are security issues they need to be fixed or the affected packages masked -[21:22:47] there was some more in kdelibs and parts -[21:22:56] simple tracking debian can work -[21:22:57] maybe it's easier just to dump kde desktop (along with affected apps) and leave kdelibs + some apps that are known to work -[21:22:59] but we need that maintainer -[21:23:23] I use Kile very often, and the kde4 version of if is far far away to be usable... -[21:23:35] --> ABCD_ (n=ABCD@gentoo/contributor/abcd) has joined #gentoo-meetings -[21:23:53] yngwin: As a Gentoo policy, you're right. But in that case we should probably have masked KDE-3 a few months ago -[21:24:03] yes -[21:24:11] jmbsvicetto: yes but now we will have stable replacement -[21:24:14] so let's try to make things right asap -[21:24:29] <-- ABCD (n=ABCD@gentoo/contributor/abcd) has quit (Nick collision from services.) -[21:24:32] i would say wait with this decision we can wait for the anouncement and proceed if noone appears -[21:24:33] could someone PM me the logs from " this is my braindead summary" through my re-joining? -[21:24:48] <-> ABCD_ is now known as ABCD -[21:24:50] I suppose masking the only stable kde release is not an option so please make sure we have one left :P -[21:25:08] sure hold on -[21:25:45] reavertm: if no maintainers step up, that is currently our only option -[21:26:38] yngwin: ok -[21:26:48] then we should do as scarabeus said -[21:27:07] can we make a poll on forums, to see how many users still use kde3 and how many moved to kde4? -[21:27:33] yngwin: but we should all be aware that even when kde-4 gets marked stable, it's very unlikely that any arch besides x86, amd64, ppc and ppc64 will get it marked stable soon -[21:27:34] yes we can -[21:27:35] dagger: well usage is not our issue, we need maintainers -[21:27:37] of course it will represent only small percentage of users, but should give us some guidelines -[21:27:51] hey there -[21:27:54] jmbsvicetto: i bet on hppa -[21:28:01] jmbsvicetto: sure, i dont think it will be marked stable soon on any arch -[21:28:09] yngwin: so masking kde-3 will upset quite a few users from these arches, but it will also upset people in the other arches -[21:28:35] scarabeus: Don't forget ia64 or sparc -[21:28:42] so the key is to get some ppl to step up and maintain&fix -[21:28:55] yes -[21:29:01] so exactly what i said -[21:29:05] scarabeus: sparc is still tied to qt-webkit dying with alignment issues -[21:29:20] so no cookies for sparc -[21:29:32] jmbsvicetto: i agree it is bad solution, but it is worse to leave it rot around -[21:29:40] at least 1 maintainer -[21:29:48] it is not so hard, the ebuilds are mostly cleaned and fixed -[21:29:56] they just need the patches and testing -[21:29:57] scarabeus: And unfortunately, it seems each day KDE upstream is more concerned with Windows,OS/X than with Linux alternative arches -[21:30:15] i expected that one -[21:30:34] scarabeus: I'm not arguing against your proposal. I'm just making a few "warning" ;) -[21:30:46] so you can show the logs when they blame you :P -[21:30:48] :DDDDD -[21:30:58] they can still unmask or use overlay if they want kde3 -[21:31:02] i would say lets go for next subject -[21:31:22] agreed -[21:32:06] i summarised it really nicely and jorge as boss can tweak it more to reflect us so we all write our proposals for it -[21:32:15] jmbsvicetto: one Q, did you see carlo lately? -[21:32:31] jmbsvicetto: he did kde3 commits when he was around, so that is why i ask :] -[21:33:18] the awkard silence... -[21:33:36] okey so for the 4.2 stabling i would say vote? -[21:34:04] i vote hell no -[21:34:05] i say we go for 4.3 -[21:34:10] hell no -[21:34:13] so no =] -[21:34:21] 4.3 is the way to go -[21:34:25] I vote.. wait for 4.3.1 -[21:34:34] -*- yngwin is with reavertm -[21:34:45] there's one 'problem' -[21:34:51] yeah, 4.3.1 sounds like the best candidate -[21:34:53] you know my opinion but for the record 4.3 -[21:35:00] kde 4.3 will need phonon-4.4pre -[21:35:08] the snapshot is stable -[21:35:11] where is the issue -[21:35:20] what snapshot -[21:35:21] which is good as it works very well, just doen't look official (and it's not, it's our snapshot) -[21:35:26] phonon -[21:35:39] reavertm: i would say it is ook -[21:35:46] it works peachy for everyone around here -[21:35:49] second thing - akonadi-server sqlite USE flag could be masked in profile -[21:35:59] reavertm: why? it is so borked? -[21:36:04] i didnt get time to test it yet -[21:36:13] scarabeus: ok -[21:36:13] scarabeus: carlo? no -[21:36:13] no prblems with phonon -[21:36:42] scarabeus: I'll have to double check, but I think he's got under undertakers view -[21:36:42] no idea, works for me, but upstream says sqlite threads support is broken sometimes and may cause data loss when using sqlite backend -[21:36:47] scarabeus: meaning is subject to retirement for inactivity -[21:36:54] jmbsvicetto: understood -[21:37:00] and I think would just need better testinb whether it's really the case -[21:37:04] About KDE4, 4.2.4 -[21:37:08] data loss = mask it -[21:37:15] If we wait for 4.3, time will fly by us -[21:37:35] 4.2.4 is not stable, boss -[21:37:35] (mysql is enabled by default for now and sqlite is marked as experimental in pkg_postinst anyway) -[21:37:40] 4.3.0 has some nasty bugs that upstream has admitted already and 4.3.1 shouldn't be out before 1st or 2nd week of September -[21:37:42] neither is 4.3.0 -[21:37:48] jmbsvicetto: yes and no. 4.2 is no longer maintained, and 4.3.1 will give us some time to fix some bugs in 4.3 -[21:37:58] Add at least 1 month to that for asking for it to be marked stable and we'll be getting very close to the year's end -[21:38:38] yep, but i think we need 1 month to fix all the issues we have in the tracker anyway -[21:38:39] yngwin: I think 4.2.4 is not a perfect release, but it's getting very close and will allow us to have a stable version almost 2 months before 4.3 -[21:38:52] I believe having 4.3.1 stable by the time 4.3.3 is released sounds good -[21:38:55] of course before anyone thinks of any kde4 stabilization, blocker bugs needs to be fixed first -[21:38:59] 4.2.4 is usable, but certainly not stable -[21:39:13] 4.2.4 is my vote - but majority rules ;) -[21:39:23] yeah we rule and you rock :] -[21:39:28] (you know the joke right?) -[21:39:35] -*- reavertm knows -[21:39:35] 4.3.0 is more stable than 4.2.4 ;) -[21:39:45] -*- scarabeus confirm -[21:39:50] If i can vote, I vote on 4.3.1, 4.3.0 crashes sometimes... -[21:40:03] much more than 4.2.4 in fact -[21:40:09] actually stability wise i have never had plasma crash yet on 4.3.9999 (and there were some on 4.2 for me) -[21:40:16] i never had a crash on 4.3.0, but saw some bugs about it -[21:40:36] i'm having plasma issues with both 4.2.4 and 4.3.0 -[21:41:05] my vote is to go with 4.3.1 (or 4.3.0 with some patches added) and if so - remove 4.2.4 from tree -[21:41:18] well, not on 4.2 anymore as i upgraded both boxes now -[21:41:24] the only plasmoid which crashes plasma for me is microblogging = 100% crash rate -[21:41:30] reavertm: I don't mean a plasma crash, but dolphin crashes, konqueror crashes sometimes, and plasma crashes :D but it isn't often and it "recover" itself all the times here -[21:41:56] I doubt anyone still uses 4.2 - adding 4.3 umasked was epic kill for idea of stabilizing 4.2 -[21:42:01] on 4.2.4 i had plasma crashes completely freeze up X -[21:42:23] i am for that removal -[21:42:26] 4.2 -[21:42:27] so, do we need to count the votes than? -[21:42:36] dagger: no need, only boss was for 4.2 -[21:42:36] or is it decided -[21:42:40] yngwin: i can be video drivers issue, I have never had a X freeze up with kde 4.2.* -[21:42:49] nvidia -[21:42:53] yngwin: ati -[21:42:59] nvidia, worksformetm -[21:43:08] what reavertm said -[21:43:10] btwwho is working on stable bugs? -[21:43:20] i saw only reaver commenting on them and i closed few -[21:43:24] but the list is still large -[21:43:29] intel 4500hd and nvidia here. Nvidia doesn't like new kernel and heci (from staging) driver -[21:43:34] i need to ask you to pick 1-2 from there and fix them -[21:43:39] some of them are gfx driver issues -[21:43:54] yeah, we need them fixed asap -[21:44:16] ok, can we move on? -[21:44:33] i want to hear that they read what i wrote ^ -[21:44:39] :D -[21:44:57] summary of no. 2 please :) -[21:45:32] http://www.pastebin.cz/22046 -[21:45:34] here you are -[21:45:50] --> Coopy (n=Coop@p4FEDA352.dip.t-dialin.net) has joined #gentoo-meetings -[21:46:01] looks good -[21:46:28] yngwin: next topic is yours -[21:47:07] ok, we're ready to add qt4-tng.eclass to portage, no alternative names have been proposed -[21:47:39] i plan to do a review this weekend and send it to -dev ml for rfc -[21:48:06] qt4-superstar could go? -[21:48:09] qt4-meh -[21:48:11] :] -[21:48:12] lol -[21:48:15] qt4-blah ? -[21:48:17] qt4-v2 ? -[21:48:23] qt5 -[21:48:25] :D -[21:48:26] qt4-thisistheoneyouwant -[21:48:27] im a bit worried about tng, it sounds good and all -[21:48:31] ayoy: LOL -[21:48:39] <-- |Francis| (n=kvirc@AGrenoble-152-1-28-162.w82-122.abo.wanadoo.fr) has quit (Remote closed the connection) -[21:48:48] but what if we want to replace it again in the distant future -[21:48:59] what is tng? -[21:49:01] qt4-tng sounds a lil bit like star trek, but I think we can live with it ;p -[21:49:04] well, you can send bikeshedding proposals once the rfc is on ml -[21:49:04] well you can live with one damn eclass like us -[21:49:08] it doesnt sound like it -[21:49:10] Ronis_BR: the next generation -[21:49:11] it is startrek -[21:49:12] :p -[21:49:16] O_o -[21:49:30] wierd :) -[21:49:39] to baldly go where no-one has gone before -[21:49:44] --> |Francis| (n=kvirc@AGrenoble-152-1-28-162.w82-122.abo.wanadoo.fr) has joined #gentoo-meetings -[21:49:48] -*- wired wonders if after tng we'll have the-empire-strikes-back or something -[21:49:51] :P -[21:49:55] to baldly compile what noone else was able to do -[21:50:03] wired: lol -[21:50:08] wired: good name for kde3 overlay maybe? -[21:50:13] :D -[21:50:16] lol -[21:50:21] yngwin: i am open for proposals -[21:50:27] and i have strong feelings for this one -[21:50:31] :} -[21:50:32] eheheh -[21:50:38] but isn't qt4-tng or whatever meant to replace the old qt4.eclass? -[21:50:47] eventually yes -[21:51:00] qties4.eclass -[21:51:01] :D -[21:51:07] we can't just dump the old one and put the new one in place -[21:51:11] no -[21:51:12] you cant -[21:51:13] dagger: sure -[21:51:17] you would break the ebulds -[21:51:22] *current -[21:51:22] yep -[21:51:24] yes we need a migration -[21:51:30] you guys should really "learn" how to make drastic eclass changes in place like we do :D (with no new eclasses involved) -[21:51:33] qt4-tng is a gentoo version with patches or not? -[21:51:36] unless you want to check all ebuilds that use qt4.eclass wrt new functionality -[21:51:39] reavertm: see this is reason why i slapped you everytime for backcompat -[21:51:50] scarabeus: with kde-misc? :P -[21:51:58] its TNG folks -[21:52:05] does picard look like kirk to you? -[21:52:07] :D -[21:52:10] reavertm: yep :] -[21:52:20] kirk had better chicks -[21:52:22] they had skirts -[21:52:23] ok, back to the point please -[21:52:24] <-- Coopy (n=Coop@p4FEDA352.dip.t-dialin.net) has quit ("Leaving") -[21:52:29] ok ok -[21:52:33] i think tng is done -[21:52:49] as far as i'm concerned yes -[21:53:02] or just qt4-0.1.eclass -[21:53:10] (then 0.2 for next revision :P) -[21:53:13] "Backcompat is to still commit in the present the errors commited in the past" -[21:53:15] jmbsvicetto: you should push your versioned eclasses idea -[21:53:28] ok anyway -[21:53:36] the last thing is bit brainstorming -[21:53:42] what shoudl we focus on in future -[21:53:45] too bad you can't do it in place -[21:54:32] I remember seeing an agenda item in some email about the unversioned sets -[21:54:35] sorry guys - mind at userrel -[21:55:11] ABCD: i was waiting on jorge to come back so i left it as totaly last -[21:55:19] scarabeus: ok -[21:55:21] scarabeus: That idea wasn't mine, I just pulled it out of the dust ark ;) -[21:55:38] :] -[21:55:46] ok any ideas/proposals what we should focus -[21:55:51] we will have new recruits -[21:55:51] scarabeus: The versioned eclasses -[21:55:58] jmbsvicetto: i understood -[21:56:07] and for them we need something creative to do -[21:56:12] we cant just leave them fix bugs -[21:56:14] same for us -[21:56:22] if i would only fix bugs i would went insane -[21:57:10] in qt team we are actively looking at adding new qt4-based packages all the time -[21:57:13] i had idea about branding, but then i cant draw -[21:57:22] :) -[21:57:33] so someone else would have to mentor the idea -[21:57:34] documentation could use more work too -[21:57:49] I had an idea of qt-based portage gui -[21:57:56] but then I wouldn't use it -[21:58:00] :D -[21:58:06] ayoy: noone would I think :p -[21:58:09] :) -[21:58:10] scarabeus: There's always the "fix upstream build system" idea ;) -[21:58:21] there was a kde(3?) one iirc -[21:58:21] scarabeus: branding is actually a lovely idea, remember that gentoo kstart icon quantumsummers had? -[21:58:24] we need artists -[21:58:25] I have some task, not sure whether suitable for newcomers -[21:58:40] i have tasks not suitable for myself :D -[21:58:44] so go on -[21:58:45] :] -[21:58:47] I need eclass for odbc driver management -[21:59:01] supporting iODBC and unixODBC interfaces -[21:59:35] well that is totaly not beginner work -[21:59:37] ok, next -[21:59:40] I'm sorry guys, but I will have to leave you now. I need to pick up my wife. -[21:59:48] registering/unregistring drivers, in similar way like in debian, (but separately - one for iODBC and one for unixODBC) -[21:59:56] c ya dagger -[22:00:21] (it should be easy, mostrly it's just invocation of unixodbc tool with creating some files in /etc) -[22:00:33] well if you find interested recruit go for it -[22:00:36] --> Francois (n=francois@193.253.141.72) has joined #gentoo-meetings -[22:00:50] reavertm: question. how is your reviewing going by? -[22:01:08] I'm lazy to send fixed quizzes -[22:01:25] gosh -[22:01:31] please do so -[22:01:34] sooon -[22:01:35] :] -[22:01:35] nevermind -[22:01:47] ok last topic is SETS -[22:01:53] I hate the current state -[22:01:56] i preffer metas more -[22:02:12] so we need someone to write proper specs for what we need from sets -[22:02:12] <-- |Francis| (n=kvirc@AGrenoble-152-1-28-162.w82-122.abo.wanadoo.fr) has quit (Read error: 104 (Connection reset by peer)) -[22:02:21] and talk about it with zac -[22:02:27] and even better help him implementing -[22:02:34] jmbsvicetto: ^ ? -[22:02:38] oh yes, have anyone read bug 272488 ? -[22:02:40] am i right? -[22:02:53] https://bugs.gentoo.org/show_bug.cgi?id=272488 -[22:03:04] i did i liked -[22:03:08] reavertm: That sounds like an eselect and not eclass (odbc) -[22:03:09] you volunteer? -[22:03:29] scarabeus: I'll take this one -[22:03:47] scarabeus: I've been meaning to write about it for a *long* time, but I keep postponning it -[22:03:48] jmbsvicetto: use teh bug as base, i like the idea -[22:03:57] scarabeus: Can I ask you to poke me about it until I do? ;) -[22:04:54] jmbsvicetto: hmm, not really, it would be eclass for packages that provide odbc driver -[22:04:55] reavertm: I know the bug. My plan is to get back to the basics about sets -[22:05:07] it's not about switching between iodbc vs unixodbc -[22:05:07] if you promise you wont mark me as your counter person for next lead vote ;] -[22:05:09] :D -[22:05:11] ok can do -[22:05:13] (it's determined at compilation time) -[22:05:18] I wonder when gentoo guys will look at https://bugs.gentoo.org/show_bug.cgi?id=268891 -[22:05:18] reavertm: ok, then I misunderstood. sorry -[22:05:46] scarabeus: Are you affraid instead I'll point to you when it gets time for the next election? ;) -[22:06:04] :D -[22:06:20] okey -[22:06:28] anything else for the sets, we will leave them to you -[22:06:32] and poke you about it :] -[22:06:42] jmbsvicetto: I think 2.2 style sets are dead end -[22:07:02] confusing syntax -[22:07:39] what i want is kde-latest-release sets -[22:07:58] that is quite hard to make but i see the point :] -[22:08:00] so that 4.2.4 would be automatically updated to 4.3.0 -[22:08:19] yngwin: that's basically unversioned sets ;) -[22:08:21] also i think we should stop encouraging set usage in docs -[22:08:24] yes -[22:08:33] the unversioned sets work like that :) -[22:08:39] they dont -[22:08:44] too much package fuzz movement -[22:08:52] / -[22:09:07] scarabeus: they do - the problem is our "non-stopping" upstream ;) -[22:09:42] ok, anything else for the meeting? -[22:10:01] scarabeus: They have what we call here "bicho de carpinteiro". They can sit still for a minute and thus keep moving packages left and right, adding new ones, killing old ones and finding new and better ways to make distros life harder ;) -[22:10:11] do you guys think we should move the plasmoids from kde-testing to the tree? -[22:10:13] The can't sit still* -[22:10:24] wired: we can -[22:10:30] wired: How good do you think they are? -[22:10:32] just test them for leaks -[22:10:36] and crashes -[22:10:38] everytime -[22:10:40] plasma is core -[22:10:44] if it crashes it is PITA -[22:10:48] jmbsvicetto: some of them are pretty good, others i have no idea -[22:10:59] wired: then add the one you like -[22:11:00] i mostly test that they build and occasionally that they load -[22:11:09] wired: I don't see a problem with adding good ones -[22:11:21] but you really have to test them -[22:11:24] and what scarabeus said ;) -[22:11:31] ok so on a per-plasmoid basis -[22:11:36] kk -[22:11:55] well, kde developers doesn't test their code sometimes, so we should -[22:11:56] you have already discussed about kdeprefix i think, haven't you? -[22:12:15] Ronis_BR: that was decided long ago, not matter of this meeting -[22:12:15] Ronis_BR: yes, it's dead (for now) -[22:12:24] ok -[22:12:30] too bad, but ok :) -[22:12:40] Ronis_BR: we accept patches -[22:12:40] :D -[22:12:54] Ronis_BR: that was decided at the June meeting :) -[22:13:12] ok i would like to dismiss the meeting for this moth -[22:13:14] any objections? -[22:13:25] ABCD: sorry, it is the first time that I hear about gentoo meetings :) -[22:13:39] scarabeus: Before we go, when should we have the next meeting? -[22:13:41] Ronis_BR: kde.gentoo.org its on the page, logs+summary -[22:13:53] I suppose we don't need more meeting recently - just people eager to work on issues :P -[22:13:54] 17.9. -[22:13:57] jmbsvicetto: ^ -[22:14:02] 3rd thursday in the month -[22:14:09] 19:00 utc -[22:14:15] if noone found it really evil or bad -[22:14:17] right -[22:14:33] Oh!!! -[22:14:38] scarabeus: i will be on holiday that week -[22:14:39] scarabeus: actually we could just meet in two weeks to evaluate work done -[22:14:40] One last item I forgot to add to the meeting -[22:14:50] Anyone willing to help solar about the 10.0 release? -[22:15:00] I'll have to check my class schedule for Fall semester again, but I think that will work (it does fall in the middle of the day here, though) -[22:15:10] jmbsvicetto: what kind of help -[22:15:15] I want to help with KDE (and if I can compiz), but it would be great if more people could help -[22:15:18] -*- scarabeus busy with x11stabling/overlays rework -[22:15:54] yngwin: solar and a few others are working on catalyst specs to build a live-dvd with x86/amd64 to celebrate Gentoo's 10th birthday -[22:16:08] catalyst.... -[22:16:22] well thats release team work -[22:16:23] jmbsvicetto: can they add ~ packages? -[22:16:35] yngwin: there is no such team iirc -[22:16:36] :D -[22:16:37] they could add kde 4.3 :) -[22:17:11] -*- yngwin sends thunderbolts scarabeus' way -[22:17:13] because if kde3 will be there, we can simply grab sabayon, it will be more promotial -[22:17:23] and polished :P -[22:18:15] scarabeus: There's an release team -[22:18:26] But this is a "special edition" -[22:18:39] scarabeus: The point is to have KDE4, not 3.5.10 -[22:18:40] solar or agaffney? -[22:19:33] <-- Francois (n=francois@193.253.141.72) has quit (Client Quit) -[22:20:27] ...? -[22:20:36] release tem -[22:21:30] http://www.gentoo.org/proj/en/releng/ -[22:22:24] ok guys anyway i have to run -[22:22:31] here is the summary: http://dev.gentoo.org/~scarabeus/0908summary.txt -[22:22:33] do logs yourself -[22:22:36] jmbsvicetto: ^^ -[22:22:39] download it NOW -[22:22:44] :D -[22:23:08] scarabeus: ok -[22:23:12] <-- tbeadle (n=quassel@division.aa.arbor.net) has left #gentoo-meetings ("http://quassel-irc.org - Chat comfortably. Anywhere.") -[22:23:34] * scarabeus has changed topic for #gentoo-meetings to: "Rem tene, verba sequentur || Keep to the subject and the words will follow" -[22:23:50] scarabeus: can't find the file in packer -[22:23:54] pecker* -[22:24:29] jmbsvicetto: it downloads, its in public_html probably :D -[22:24:48] jmbsvicetto: i have logs, do you need them? -[22:24:51] -*- yngwin out -[22:25:14] scarabeus: please ignore me -[22:25:32] wired: I can't connect through http at the moment, but thanks -[22:25:55] wired: I got it from Tomas. I was just showing signs of my "split brains" :\ -[22:26:03] heheheh -[22:26:09] no problem -[22:26:20] did you log the meeting or you want me to give you my log? -[22:26:57] <-- ABCD (n=ABCD@gentoo/contributor/abcd) has left #gentoo-meetings ("http://quassel-irc.org - Chat comfortably. Anywhere.") -[22:27:50] jmbsvicetto: ^^ -[22:29:25] wired: I didn't log -[22:29:36] wired: Thanks for reminding me I forgot to add a rule to my irssi about this -[22:31:37] <-- ayoy (n=ayoy@cs78245237.pp.htv.fi) has left #gentoo-meetings ("kbai") -[22:32:27] jmbsvicetto: yw -[22:32:42] jmbsvicetto: so where do you want log? pecker? -[22:35:05] jmbsvicetto: ~wired/kde/200908_meeting.log -[22:36:24] wired: thanks -[22:40:10] :) -[22:41:49] scarabeus: I have another request for you - starting Saturday, poke me for the logs/summary ;) -[23:10:08] \part -[23:10:16] <-- Gentoochild (n=bla@vpn5.rz.tu-ilmenau.de) has left #gentoo-meetings ("Konversation terminated!") -[23:17:09] btw you can leave now, next on the list is gnome meeting, and i dont think you want to slack around that ;D -[23:27:43] gnome meeting? nice diff --git a/meeting-logs/kde-project-meeting-log-20090917.txt b/meeting-logs/kde-project-meeting-log-20090917.txt deleted file mode 100644 index 5cbdcf5..0000000 --- a/meeting-logs/kde-project-meeting-log-20090917.txt +++ /dev/null @@ -1,572 +0,0 @@ -[22:01:31] *** Joins: wired (n=wired@gentoo/developer/wired) -[22:01:32] *** Joins: ayoy (n=ayoy@cs78245237.pp.htv.fi) -[22:01:55] *** Joins: dabbott (n=david@gentoo/developer/dabbott) -[22:02:07] *** Joins: toralf (n=toralf@g224122197.adsl.alicedsl.de) -[22:02:33] *** Joins: Battousai (n=bryan@maduin.southcape.org) -[22:03:44] * wired makes sure logging is on -[22:04:59] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) -[22:05:07] I'm here -[22:05:09] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) -[22:05:39] scarabeus: jmbsvicetto? -[22:05:44] *** Quits: ABCD (n=ABCD@gentoo/developer/abcd) (Read error: 104 (Connection reset by peer)) -[22:06:02] *** Joins: ABCD (n=ABCD@gentoo/developer/abcd) -[22:07:24] *** Quits: |Francis| (n=kvirc@AGrenoble-152-1-48-33.w82-122.abo.wanadoo.fr) (Remote closed the connection) -[22:07:35] wasn't it moved to friday? :P -[22:08:02] scarabeus sent "correction" email -[22:08:02] :p -[22:09:06] oh, I was already here -[22:09:08] yeah -[22:09:11] didn't i hilight you? -[22:09:18] :P -[22:09:25] scarabeus said he might not make it, who else is late? -[22:09:25] I'm not sure how well my connection is going to hold up, so... -[22:09:29] Yeah, but I had forgot I was around here -[22:10:27] * jmbsvicetto makes mental note - win 76 -[22:10:29] Anyone logging? -[22:10:37] everytbody -[22:10:43] i am -[22:10:55] yngwin won't be coming, scarabeus too -[22:10:56] ok -[22:11:02] we're missing patrick, tampakrap -[22:11:11] and some more qt representatives -[22:11:26] ayoy spatz and Pesa are here -[22:11:33] hwoarang is on long devaway -[22:11:36] Let's give them a few more minutes? -[22:11:38] yngwin is away too -[22:11:47] we're waiting for bonsaikitten? -[22:12:05] i pinged them -[22:12:07] *** Joins: bonsaikitten (i=quassel@gentoo/developer/bonsaikitten) -[22:12:08] good, on his way :) -[22:12:19] *** Joins: tampakrap (n=tuxicity@gentoo/developer/tampakrap) -[22:12:29] good -[22:12:43] So, who wants to chair this one? -[22:13:01] I could use the break to get ready another thing I'm working on -[22:13:34] hello -[22:14:14] jmbsvicetto: i'll do it -[22:14:45] good, do we have decisive power? -[22:14:46] lets get going, first topic, 4.3 stabilization -[22:14:58] wired: thanks -[22:15:04] to vote stuff and such? it's quite few of us -[22:15:26] wired: roll call first -[22:15:47] here -[22:15:58] reavertm: I don't think we have much to vote today. It's more about getting processes started -[22:16:02] here -[22:16:04] that was done, but present yourselves for the record if you want :) -[22:16:26] here -[22:16:38] here -[22:16:46] i am -[22:16:56] ok, wired, move on -[22:17:20] first topic, kde 4.3 stabilization -[22:17:26] are we still going with 4.3.1? -[22:17:34] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) -[22:17:38] here -[22:17:52] yaah, we're going with 4.3.1, I wanted to bring this topic to... -[22:18:14] gather some manpower to fix blocker bugs (or talk about dropping some blockers) -[22:18:38] are there any specific blocks we should focus on? -[22:18:50] https://bugs.gentoo.org/show_bug.cgi?id=277868 -[22:18:50] is there a list/tracker? -[22:18:54] this is bug -[22:19:09] btw meeting agenta: http://archives.gentoo.org/gentoo-desktop/msg_1abe5bf232579eabb51aadc3d80b397b.xml -[22:19:15] wired: yes -[22:19:18] in case you don't have the mail available -[22:20:10] 12 bugs -[22:20:18] One thing we need to do ASAP is adding the patches being sent to the packagers ml -[22:20:28] i agree -[22:21:14] if we could focus these 2 weeks ideally we could request stablereq right after the 1 month period -[22:21:26] yes -[22:21:38] *** Joins: [Enrico] (n=chiccoro@gentoo/contributor/Enrico) -[22:21:49] I've already set java as default backend so one bug less (about redland crashing) -[22:21:58] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) -[22:22:03] great -[22:22:03] and there's postinst message -[22:22:35] so guys please do your best so we can finally have kde4 in stable :D -[22:22:43] We should also start opening stabilization bugs for deps: automoc, strigi, soprano, phonon. Anything else? -[22:23:04] are we stabling the phonon snapshot? -[22:23:22] yes, it works fine -[22:23:30] (it has unstable API) -[22:23:44] well it'll have to do if thats all we've got -[22:23:58] it's known to work anyway -[22:24:05] ok -[22:24:08] what's the minimum working version? -[22:24:25] * wired looks ar reavertm -[22:24:29] at -[22:24:38] And we need to get it stable or there'll be no stable KDE-4.3.1 -[22:25:12] 4.3.1 should od -[22:25:23] do -[22:25:33] but... mplayerthumps would need changes -[22:25:48] By the way, we're including KDE-4.3.1 in the 10.0 livedvd, so we should try to get it stable around October 4th -[22:25:49] (disabling phonon backend - as it only works with latest phonon) -[22:25:59] otherwise kde would pull mplayer... -[22:26:22] reavertm: can 't we leave it out? (mplayerthumbs) -[22:26:39] why should we? part of kdemultimedia -[22:27:00] whats wrong with having mplayer as a dep (besides an extra dep)? is it not working ok? -[22:27:44] reavertm? -[22:27:45] I suppose it is, whatever if you like one could go with 4.3.1 phonon and that change in mplayerthumbs -[22:28:08] reavertm: I mean if it's too much trouble to get it working with current deps, we can leave it out for now and get it marked stable later (perhaps even on 4.3.2 or later releaes) -[22:28:11] I won't die for this cause, 4.4pre is just not worse than 43.1 -[22:28:34] jmbsvicetto: well we have tested the phonon snapshot extensively -[22:28:47] wired: ok -[22:29:04] as long as its an exception (snapshots) ;) -[22:29:10] I even asked some kde devs about it :P -[22:29:36] jmbsvicetto: is there an issue with stabling it -[22:29:36] ? -[22:29:43] ok -[22:29:52] * wired kicks isp for lag -[22:30:07] anyone else wanna say anything about stabilization? -[22:30:25] apart from get to work? :) -[22:30:30] yeah -[22:30:43] it isn't possible to have it fully stabilized until october 4th -[22:30:58] well, we need more stable testers ... -[22:31:42] *** Joins: alexxy (n=alexxy@gentoo/developer/alexxy) -[22:31:48] alexxy :) -[22:31:51] hi all! -[22:31:53] bonsaikitten: I use stable system :P -[22:31:59] sorry that i'm late -[22:32:02] ooh :) -[22:32:14] (with exceptions for kde and its deps) -[22:32:15] isnt meeting was schedulet for tommorow? -[22:32:22] initially it was -[22:32:24] alexxy: scarabeus sent a correction email -[22:32:25] the problem is that the one month period is beyond that date -[22:32:28] he failed at the date -[22:32:31] nevermind, you missed nothing -[22:32:43] not to mention the time that arch teams need -[22:33:15] tampakrap: no its not, you added the ebuilds on sept 1st -[22:33:15] the problem is getting archs to stable it in 3 days -[22:33:15] assuming we have fixed bugs -[22:33:33] one month with no open bugs -[22:33:50] wired: 4.4_pre? Preferably we should do 4.3.1 instead, but if 4.4_pre solves other issues, let's go with it -[22:33:54] i hope i'm wrong on this one... -[22:34:16] tampakrap: sure, but we can start the work to get it marked stable asap -[22:34:30] jmbsvicetto: 4.4_pre20090520 yeah, thats the one we have in ~testing now -[22:34:50] tampakrap: we can file an "early request" bug -[22:35:00] tampakrap: it's up to arch teams whether they want to mark it stable or not -[22:35:02] ah ok then -[22:35:07] and we also have one extra motive -[22:35:09] tampakrap: and for the livedvd we only need amd64/x86 -[22:35:10] livedvd -[22:35:33] ok let's hope this will work then -[22:35:47] I recommend we do a mini meeting next week -[22:35:56] may be -[22:35:57] to check on the state of bugs -[22:35:59] tampakrap: Besides, I think we're starting to have many amd64/x86 users on KDE-4 -[22:36:00] nice idea -[22:36:16] wired: good idea -[22:36:49] same day next week? 24th? -[22:37:20] fine by me -[22:37:35] great, i'll send the email, we can adjust if needed -[22:37:36] wired: sure -[22:37:57] lets do our best and close all bugs :D -[22:38:07] ok enough with this then, lets proceed -[22:38:17] kde3.5, kde-sunset -[22:38:28] who's taking care of this and can give us an update? -[22:38:33] tampakrap?/ -[22:38:41] there is no progress in that subject -[22:38:59] apart from the fact that scarabeus created the overlay :P -[22:39:01] On that spirit, I'd like to ask all of you interested in the livedvd to join #gentoo-ten get the ISOs, test them and fix any KDE bugs -[22:39:06] so nobody is interested - good :) -[22:39:19] reavertm: heh -[22:39:20] I'm "owing" an email about it -[22:39:28] jmbsvicetto: lol click send -[22:39:48] The official email putting the "death seal" on KDE-3.5 -[22:39:51] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) -[22:39:55] ah that one -[22:40:25] is anyone else interested in helping make the move to kde-sunset? -[22:40:39] besides tampakrap? :P -[22:40:45] no! -[22:40:53] it should rot and die -[22:40:56] hehe -[22:40:56] reavertm: think positive, we'll get rid of it from the tree -[22:40:58] :D -[22:40:58] i agree noone else is needed -[22:41:07] we just need to stabilize kde4 and kill 3 -[22:41:08] wired: I can help move the ebuilds there -[22:41:22] great -[22:41:34] not sure if we need scarabeus to give us access to it or if he added us all -[22:42:03] ok, next item -[22:42:06] kdeprefix -[22:42:09] wait -[22:42:12] about kde3 -[22:42:15] yeah? -[22:42:26] i have set some rules before moving ebuilds to kde-sunset -[22:42:49] you should make Documentation/CODE -[22:42:50] i sent them in the previous meeting through scarabeus because i wasn't present then -[22:42:55] ah ok -[22:43:05] nice idea #2 -[22:43:25] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) -[22:43:29] OK -[22:43:34] anyone else anything about kde3? -[22:44:06] moving on then -[22:44:08] kdeprefix -[22:44:18] not sure what scarabeus had in mind when he added it to agenda -[22:44:32] perhaps removing it completely? -[22:44:49] I think there's no need to drop it from eclass -[22:44:51] to much work :P -[22:44:59] well its not usable in current state -[22:45:06] and its masked -[22:45:08] and it causes much more bugs -[22:45:22] wired: I asked him to add this point to the agenda -[22:45:25] so let it stay masked =) -[22:45:33] we explicitly don't support any kdeprefixed installations -[22:45:41] jmbsvicetto: ok, what did you have in mind? -[22:46:09] The point is we should send an email letting those using kdeprefix of the new breakage and warning them they should really move out of +kdeprefix -[22:46:25] I think we should still keep code in mind that it may be enabled as some point -[22:46:25] +know -[22:46:36] but this mail is needed -[22:47:07] jmbsvicetto: ok, but they should know already, portage should have screamed when we masked it -[22:47:28] but an email (and perhaps a blog post, i could do that) would help -[22:47:42] That's all I'm after -[22:47:44] a news item maybe? -[22:47:50] post a sticky in the forums, many go there -[22:48:05] I think it is mentioned already -[22:48:13] in stick in Desktop Environment -[22:48:33] okay.. who wants to send the email? -[22:48:52] Gentoo KDE Lead volunteered, no? :) -[22:49:10] *** Parts: [Enrico] (n=chiccoro@gentoo/contributor/Enrico) -[22:49:10] hehe -[22:49:11] (jmbsvicetto) The point is we should send an email -[22:49:16] I did -[22:49:30] :) -[22:49:31] ok -[22:49:34] I'll write a blog post -[22:49:57] anyone else have anything on kdeprefix? -[22:50:18] * reavertm will add one quick point to agenda later -[22:50:18] moving on -[22:50:26] qt 4.5 -[22:50:43] some people (and some qt devs apparently?!) say its broken with gcc 4.4 -[22:50:54] is everyone aware of the problem? if not, then qt-4.5 may break with 4.4 -[22:50:58] wired: i dont see any breakages -[22:51:00] do we have any evidence? -[22:51:03] with gcc-4,4 -[22:51:07] not any im aware of -[22:51:11] (apparently when strict aliasing is enabled) -[22:51:36] well -[22:51:39] gcc-4.4. is officially not supported (well, not listed in supported), for 4.5 -[22:51:57] I remember someone reporting breakage with 4.4, and Sput confirming it's known to break, but I personally use it successfully -[22:52:00] isn't it in stabilization process though? -[22:52:03] All I can say is that I haven't noticed any KDE-4.3.1 program crashing with qt-4.5.2 and gcc-4.4 -[22:52:06] and portage already spits QA warnings with gcc-4.3.2 -[22:52:11] does ANY of you have issues with qt 4.5 and gcc 4.4{,.1}? -[22:52:11] cause so far its all blah blah blah -[22:52:11] but no evidence -[22:52:38] i say its FUD until proved otherwise by bug reports -[22:53:07] no problem here, but gcc's warnings are quite scary -[22:53:24] Pesa: what warnings? :) -[22:53:27] I'll ask thiago about details and get back on next meeting (should have done it already..) -[22:53:33] about strict aliasing -[22:53:36] reavertm: alright -[22:53:42] i still think we need proof of breakage -[22:53:45] mhm -[22:54:02] *** Quits: toralf (n=toralf@g224122197.adsl.alicedsl.de) (Client Quit) -[22:54:23] ok, but... -[22:54:34] if let's say it's horrible breakage, what then? -[22:54:44] (and proven) -[22:55:09] is it fixed in 4.6? -[22:55:12] reavertm: The point is that if it's true, we can't get KDE-4.3.1 marked stable -[22:55:16] who thinks we can hold back gcc-4.4 stabilization (with all those ricers around) until 4.6 is out? :P -[22:55:22] well if its strick-aliases, can't we disable it? -[22:55:30] strict* -[22:55:40] jmbsvicetto: as of current stable gcc 4.3.2 we can -[22:57:00] jmbsvicetto: it's not a matter of kde but qt4 (already stable :P) -[22:57:19] hehe -[22:57:28] qt? Who's that? ;) -[22:57:39] jmbsvicetto: want to remove Qt from tree and see if kde works? -[22:57:40] :D -[22:58:25] anyway, we'll need to look into this -[22:58:39] we need to work some procedures in case it's breakage :P -[22:58:44] i wonder if enforcing something like -fno-strict-aliases would work, then again i have no idea of the problem or what causes it -[22:59:14] can we filter flags for anything that builds against qt4? -[22:59:34] I mean *anything* -[22:59:40] nope -[22:59:42] not really -[22:59:44] (with qt4 itself) -[22:59:56] but maybe building the libs with that flag would be enough -[23:00:01] so if anyone encounters random runtime failures ... -[23:00:04] we really need more info and test cases -[23:00:15] wired: nope, there are templates :) -[23:00:21] unfortunately some code may be inline... templates -[23:00:34] QVector for example -[23:00:41] then we have to try to find more info and failure cases -[23:01:00] the problem, I think, is in 2 headers installed by Qt; the flag would have to be added to every package that uses either header -[23:01:05] and I think thiago talked about QVector suffering from aliasting for example -[23:01:16] i suggest we look for info ( reavertm please ask like you said ) and we talk about this *important* issue on mini-meeting as well -[23:01:26] even sooner in chat if we have updates -[23:01:55] ok -[23:01:58] on my TODO, next? -[23:02:05] great -[23:02:08] if the problem is limited to only some classes, is there a patch we can backport? -[23:02:24] Pesa: well sput said that they're not willing to fix it -[23:02:35] O_O -[23:02:40] we can create one :P (with workaround maybe - like some gcc directive :P) -[23:02:56] but this whole ordeal looks like fud to me, if its serious they will have to fix it -[23:02:56] we can check other distros using gcc 4 -[23:02:56] 4.4 -[23:02:56] for custom patches -[23:03:03] I think that's because there are too many changes 4.5<->4.6 -[23:03:20] i see -[23:03:34] i'll try to see what other distros with gcc-4.4 (if any?! :P) do - if they do anything at all -[23:03:44] they may not know -[23:03:52] you never know -[23:03:53] (kde devs may no know even) -[23:04:00] or there might really be not issue at all -[23:04:04] :) -[23:04:17] next fedora and next ubuntu have gcc 4.4 afaik -[23:04:35] maybe current fedora too -[23:04:43] ok -[23:04:43] wired: well, like you say, if was critical, they would have fixed it -[23:04:52] ayoy: yes thats what i believe as well -[23:04:52] and Qt 4.6 comes out ~December maybe -[23:04:56] fedora has bleeding edge svn gcc version -[23:05:06] they wouldn't leave their only stable release broken -[23:05:09] i hope -[23:05:10] since its test ground for rhel -[23:05:14] exactly -[23:05:21] ok, next please -[23:05:27] right -[23:05:28] it's QVector and QMap that are the issues, I think -[23:05:28] /usr/include/qt4/QtCore/qmap.h:588: warning: dereferencing pointer 'y' does break strict-aliasing rules -[23:05:28] /usr/include/qt4/QtCore/qvector.h:315: warning: dereferencing pointer 'pretmp.11332' does break strict-aliasing rules -[23:05:29] btw, new OpenSuSE uses 4.4 iirc -[23:05:46] we're dwlling on this, lets do our research and return -[23:05:49] dwelling -[23:05:55] wtf is wrong with me today -[23:06:10] next item -[23:06:19] next topic - Qt 4.5.2 stab (ilization) -[23:06:22] yeah -[23:06:28] do it! -[23:06:57] I mean - now - it fixes several issues with kde (including webkit crashes in quassel) -[23:06:59] i don't see why not -[23:07:14] also it makes kdevelop katepart faster (using raster) -[23:07:18] is the exceptions flag issue fixed in the tree already? -[23:07:25] no -[23:07:32] and there's no issue with exceptions in 4.5 -[23:08:02] ayoy: is there a reason to touch exceptions in intree 4.5 ebuilds? -[23:08:05] please leave 4.5 alone -[23:08:26] well, what was the thing that we tested in overlay? -[23:08:30] don't touch, cc arches :) -[23:08:32] not 4.5-related?... -[23:08:50] ayoy: you mean 4.6 tech preview 1? -[23:09:03] i really don't know why we added that flag for 4.5 -[23:09:03] xml-patterns dependent on core w/exceptions -[23:09:05] is it for 4.6? -[23:09:08] yes -[23:09:08] thats 4.6 -[23:09:11] aahhhh -[23:09:12] 4.5 doesn't need it -[23:09:13] sorry :) -[23:09:28] any outstanding bugs in 4.5.2 im unaware of? -[23:09:41] *** Joins: tkmorris (n=unknown@201-66-183-55.paemt704.dsl.brasiltelecom.net.br) -[23:09:47] (how is sip/pyqt4 btw?) -[23:09:48] i don't see any -[23:10:25] reavertm: bug 284707 -[23:10:42] http://bugs.gentoo.org/show_bug.cgi?id=284707 -[23:11:15] very well -[23:11:23] we need Wilkins here -[23:11:56] ok, are we done iin this topic? -[23:12:11] ok then who wants to open the stablereq bug? -[23:13:00] wired: seems like you -[23:13:05] heheh -[23:13:08] alright -[23:13:12] i'll do it -[23:13:16] next item -[23:13:24] eclass unitests -[23:13:32] yeah, I think we could use some -[23:13:39] in kde world at least -[23:14:05] to verify blocks/dependencies,- in general kde-functions -[23:14:41] just a general idea, what do you think -[23:15:03] sounds interesting as for me -[23:15:11] tests to make sure blocks/deps are correct? -[23:15:16] yes -[23:15:16] unit tests are usually a good idea for regression testing -[23:15:26] sounds good -[23:15:26] sto avoid further breakages in eclasses -[23:15:54] sorry guys, I'm being swampped elsewhere. Please poke me if you need anything from me -[23:16:01] sure -[23:16:06] jmbsvicetto: np, whats your thought on unittests? :P -[23:16:36] so.. reavertm you're on this? -[23:16:45] I think nobody really objects, just someone will need to do it -[23:16:54] i may start wriing simple tests -[23:17:03] a headstart would be nice -[23:17:08] ok, next item -[23:17:14] great -[23:17:15] jmbsvicetto: sets :) -[23:17:16] sets -[23:17:48] https://bugs.gentoo.org/show_bug.cgi?id=272488 -[23:17:56] I filed following bug ^ -[23:18:05] it's one of ways -[23:18:16] wired: They're always a good idea -[23:18:19] sets -[23:18:30] i think it's generally accepted fact that current sets doesn't fit best -[23:18:33] sorry, wired I meant about unittests -[23:18:40] reavertm: agreed on that -[23:18:46] jmbsvicetto: ok, reavertm will do the start -[23:19:05] reavertm: yeah i've read that bug, its interesting -[23:19:09] This is another email I'm "owing" us -[23:19:10] so,I wanted to bring your attention on discussion about sets -[23:19:12] but it seems the whole sets thing is "stale" -[23:19:25] is anything being developed by zac/portage team? -[23:19:46] wired: no interest - no need to make progress -[23:20:13] if we present strong interest in some idea, zac may start coding -[23:20:41] PROPERTIES=set has this nice feature that most of syntax is already there and may need a litlle work just to get it done -[23:21:00] (with no operators supported - operators have been disabled from sets anyway) -[23:21:21] s/a little/little/ -[23:21:42] so, please read this bug, form some opinion and comment on this bug -[23:21:48] I think this is everything from me -[23:22:12] anyone any ideas/comments? -[23:22:22] reavertm: I think PROPERTIES="sets" has some interesting points and may be useful in some cases, but I still think the "original" sets are in general better for KDE -[23:22:37] reavertm: very interesting idea -[23:22:48] jmbsvicetto: only for live maybe -[23:22:53] Pesa: it's zac idea :P -[23:23:03] reavertm: I do need to write something about it and until I do, I should shut up as I'm not providing ideas for others to be able to comment on -[23:23:21] jmbsvicetto: ;) -[23:23:29] jmbsvicetto: you did have another idea, no? :) -[23:23:59] properties set would only need us to maintain 'metapackages' -[23:24:25] and i personally don't need anything else (even as a maintainer) -[23:24:49] wired: my main point is that a list of package atoms can be more versatile -[23:25:05] jmbsvicetto: USE flags? -[23:25:10] wired: just to give you an example, I think that would be a clever way to fix the PDEPEND problem of QT -[23:25:20] or dedicated USE_EXPAND variable? -[23:25:26] jmbsvicetto: maybe instead of trying to write a spec, you could write a short comment @ reavertm's bug to get discussion going? -[23:25:38] reavertm: I know what you mean and that's where optional deps would need to be supported by sets -[23:25:41] (comment with a short description of what you're thinking) -[23:26:11] wired: I'm not planning to write a spec, but I need to tie myself to a chair and write a few ideas before I can get people talking about them ;) -[23:26:18] heheheh -[23:26:28] you could trying the other way around -[23:26:36] start a discussion and let it tie you to the chair to answer -[23:26:38] :) -[23:26:53] you mean trolling? :) -[23:27:13] throwing ideas to each other isn't necessarilly trolling :) -[23:27:44] reavertm: maybe you could ask zac to make a sample implementation of properties -[23:27:48] if its easy to implement -[23:28:21] for us to verify it's usefulness? :P -[23:28:30] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) -[23:28:41] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) -[23:28:46] if its easy to implement yeah, itd be nice to have some hands on and might give us more ideas -[23:29:24] wired: just imagine metapackage that pulls everything it's listed there even when uninstalled :P -[23:29:31] some new portage guy could also do it for excersice :P -[23:29:31] exercise -[23:29:41] reavertm: That's what metapackages already do ;) -[23:29:44] this is what properties=set is -[23:29:54] jmbsvicetto: uninstalled... -[23:30:04] or reemerged -[23:30:20] reavertm: The new behaviour is for meta packages to pull all packages when they're already installed and or to remove all packages when uninstalling -[23:30:37] reavertm: ok, you meant uninstalling -[23:30:43] 'new behaviour'? never heard of it -[23:31:25] reavertm: I mean that the goal of the PROPERTIES="set" proposal is to have the PM do that with those meta-packages - thus it's a new behaviour -[23:31:27] yes, so it's easy to imagine how it works -[23:31:36] sure -[23:31:42] wired: ^ :P -[23:31:52] :) -[23:32:03] ok so we didn't get anywhere with sets -[23:32:10] of course, for official implementation it will need GLEP and such -[23:32:15] It doesn't address the optional deps (and I don't mean the use deps) and or set operations (math set operations) -[23:32:34] which could be very useful -[23:32:45] jmbsvicetto: what is 'optional deps'? USE_EXPAND variable wouldn't work? -[23:32:58] let me give an example -[23:33:05] operators - of course - we could use those -[23:33:13] (but not really blocker for me :P) -[23:33:27] let's say we want to have in the @kdebase set, kdebase-startkde as the only required dep (with all of its deps) -[23:34:07] So anyone having @kdebase in their system could remove at will any package in the @kdebase set and the PM would respect it, except if it was kdebase-startkde or one of its deps -[23:34:46] So emerge -uDav @kdebase would only update the installed packages - would work by default as emerge -uDav @kdebase/@installed -[23:34:49] so 'install all by default' but allow uninstall -[23:34:55] yes -[23:35:20] please comment on bug :) -[23:35:21] For instance, I might want to have the @kdenetwork set, but I really hate krfb and I don't want it around -[23:35:25] hehe -[23:35:34] how do you reemerge the whole set? -[23:35:39] @kdebase/@all ? -[23:35:45] wired: ^^ See, I'm already being asked to tie myself to chair ;) -[23:35:53] jmbsvicetto: yeah, it worked -[23:35:55] jmbsvicetto: :D -[23:36:04] jmbsvicetto: keep going! =] -[23:36:40] wired: That would need some discussion and documentation, but I could see emerge -uDav @ only updating the installed (and required deps) and emerge -av @ installing all packages in the set -[23:36:43] --keep-going -[23:36:50] you can attach channel log :P -[23:36:52] --jobs=5 -[23:36:58] -jobs=512 -[23:37:05] no @ oeprators -[23:37:19] keep it simple and stupid :P -[23:37:30] alright, so this should continue in bug, we should all ping jmbsvicetto once a day to tie him to the chair -[23:37:33] :D -[23:37:42] The tricky part is that the PM will need to store sets and need to use them for dep resolution -[23:37:50] hehe -[23:37:52] but is there. just needs attention -[23:38:04] bug* -[23:38:22] reavertm: another example - emerge -C @kdebase - 3 years from now when the sets are long gone ;) -[23:38:50] EAPI="10" ? :) -[23:39:06] but we should start to make people forget about '@' :P -[23:39:38] alright -[23:39:43] ok, anythig else -[23:39:44] we're closing in 2 hours -[23:39:52] reavertm: you wanted something extra to discuss about? -[23:40:10] ah yes -[23:40:18] versioning eclasses -[23:40:35] I think we really need that -[23:40:42] but just as 'stamp eclass version to be able to guess from 'environment' which eclass is really used -[23:41:19] some EVERSION_kde4_base=number (incremented with every file.eclass commit) would work -[23:41:27] reavertm: versioned eclasses were a good idea that never took off -[23:41:37] I could be even posisble to do it as pre-commit hook -[23:41:50] reavertm: that sounds doable -[23:42:02] reavertm: hmm, let me check something -[23:42:04] jmbsvicetto: I only would like to stamp version, not use for dependencies or such -[23:42:18] reavertm: what for then? -[23:42:25] reavertm: what you want is already there - # $Header$ -[23:42:44] reavertm: what we need is a way to put that in the environment.bz2 -[23:42:45] jmbsvicetto: but it's not in environmeny as varianle -[23:42:52] yes, I understand -[23:42:59] reavertm: but there might be a way to get it -[23:43:35] reavertm: hmm, thinking a few more seconds about it, are you sure it's not there? -[23:43:46] reavertm: iirc, the complete eclass is supposed to be in environment.bz2 -[23:44:15] with all comments stripped -[23:45:06] export "EVERSION_${ECLASS//-/_}"=1 -[23:45:15] for simple manual approach -[23:45:30] some quick thinking, could we have eclass wrappers loading "custom-versioned" eclasses based on ebuild PN/PVs? -[23:45:32] (pre-commit hook would be more clever) -[23:45:37] reavertm: right -[23:45:46] reavertm: maybe we could ask Zac to keep the version in the file -[23:45:57] reavertm: It seems to me it would be very useful for other cases as well -[23:46:08] how would he gather such info? -[23:46:14] He already does -[23:46:33] i mean, eclass version -[23:46:48] what he he does is checking some timestamp I suppose -[23:46:49] environment.bz2 picks the used eclasses. Currently the comments are being stripped, but it seems it could be useful to keep the 3rd line in the eclass -[23:47:23] reavertm: I'm going after a "simpler" solution -[23:47:32] avoid using anything CVS specific as we might want to move away from that one day -[23:47:35] yeah, and may even be sufficient -[23:47:53] if that was doable we could have kde4-meta in ebuilds, kde4-meta-1 and kde4-meta-2 for example and kde4-meta would inherit per case, wouldn't that be easy to implement and practical? -[23:48:02] jmbsvicetto: actually it won't -[23:48:17] reavertm: why not? -[23:48:35] jmbsvicetto: or at least we should set out own header in pre-commit anyway -[23:48:57] spatz: The current discussions include using the git md5 for similar purpose -[23:49:00] (as overlay eclasses are usually copy-paste to tree, so don't have cvs version signature) -[23:49:16] reavertm: but the minute you commit an eclass to the tree, it gets a version -[23:49:32] reavertm: and we could be using commit hooks in the overlay for the same goal -[23:49:33] jmbsvicetto: the point is I don't want to work it only with tree -[23:49:49] yes, ^ -[23:50:08] "or at least we should set out own header in pre-commit anyway" -[23:50:09] I'm not arguing against commit hooks, just saying that for the tree we already have it ;) -[23:50:12] jmbsvicetto: reavertm is what im saying doable? -[23:50:41] * reavertm reads -[23:50:49] wired: I'm too tired to think about it and am I'm no expert, but I think invariancy rules don't allow that -[23:50:57] -am -[23:51:22] wired: but it includes some eclass dependencies -[23:51:28] wired: or you'll have to use the "safe vars" to do that if/case -[23:51:29] sure it's easy to be done -[23:51:51] think eclass bumping, big version changes would not affect old ebuilds/eclasses if that worked -[23:52:00] and we don't need to get eclass versioning in portage -[23:52:29] anyway, are we done for tonight? -[23:52:34] it's just a matter what inherit depending on PV -[23:52:40] I think we are -[23:52:43] reavertm: i know, i wonder if portage would like it -[23:52:46] we are -[23:52:50] unless anyone wants to add something -[23:52:53] reavertm: PV is one of the "safe vars" ;) -[23:53:14] its seems noone wants -[23:53:19] dismissed -[23:53:20] jmbsvicetto: it's not safe unless it's marked readonly :) -[23:53:33] :) -[23:53:34] meeting ends, until next thursday :) -[23:53:49] wired: can you please upload the log to the kde project space? -[23:53:56] I can do the summary in the weekend -[23:54:35] jmbsvicetto: cvs? sure -[23:58:48] *** Parts: ayoy (n=ayoy@gentoo/developer/ayoy) diff --git a/meeting-logs/kde-project-meeting-log-20090924.txt b/meeting-logs/kde-project-meeting-log-20090924.txt deleted file mode 100644 index d82099c..0000000 --- a/meeting-logs/kde-project-meeting-log-20090924.txt +++ /dev/null @@ -1,230 +0,0 @@ -[22:07:55] sooooo -[22:07:59] who's here? -[22:07:59] that would rock :) -[22:08:16] meetings are quite understaffed recently :P -[22:08:21] yeah i have a feeling -[22:08:23] here -[22:08:24] blame scarabeus -[22:08:26] we'll be missing a lot today -[22:08:27] I'm here -[22:08:35] ROLLCALL :D -[22:08:52] * ABCD is here -[22:08:57] * reavertm reporting -[22:08:58] <--tampakrap but due to family issues i may leave without notice -[22:09:29] *** Joins: alexxy (n=alexxy@gentoo/developer/alexxy) -[22:09:36] hi all -[22:09:42] yo -[22:09:44] heya alexxy -[22:09:46] hey alexxy -[22:09:50] shouting brings ppl -[22:09:52] * wired is impressed -[22:10:08] it's good you're here alexxy because I've planned last minute agenda topic that is sort of related to you :) -[22:10:13] lol -[22:10:23] he wont be happy -[22:10:24] :p -[22:10:33] I think in longer run he will -[22:10:39] :) -[22:10:39] hehe -[22:10:46] omg =) -[22:10:49] so lets wait 5 more minutes -[22:11:09] maybe jmbsvicetto and bonsaikitten will show up -[22:11:41] we're also missing spatz -[22:12:53] * wired orders some food -[22:13:38] btw i have a rather unstable internet connection these days, so i may disappear in the middle of the meeting :( -[22:14:40] jmbsvicetto mentioned to me he might not make it -[22:14:59] and I'm present, but not conscious -[22:15:10] * reavertm slaps bonsaikitten -[22:19:25] alright -[22:19:30] lets begin -[22:19:35] Hi -[22:19:38] w00t -[22:19:42] that's timing -[22:19:42] :p -[22:19:48] yeah -[22:20:02] hey boss -[22:20:14] but i'll leave sorry -[22:20:34] cya -[22:20:59] Hi everyone -[22:21:04] jmbsvicetto: :) -[22:21:04] hi :) -[22:21:10] I'm also present, but not very "conscious" -[22:21:33] maybe we should look into that, it seems to be spreading -[22:21:33] :p -[22:21:43] ok.. -[22:21:54] lets start with kde stabilization -[22:22:07] can someone please outline the current bugs state? -[22:22:26] there are a few left -[22:22:57] two java (some hotspot issue with non-sun jvms) related, two grub issues (patch is attached to one of them) -[22:23:14] some deps are also pending stabilisation -[22:23:42] I've eliminated two more today (one as test-request and second marked as not blocking stabilization) -[22:24:15] anything we can't solve in the following days, or something we should focus on? -[22:24:21] *** Parts: nim_ (n=nim@adsl14-107.lsf.forthnet.gr) -[22:24:32] Pesa: one is probably yours? (consolekit and dbus related) -[22:24:58] yep, it shouldn't block stabilization imho -[22:25:07] it's not a regression afaik -[22:25:11] one could try to applyt hat grub patch from bug 242736 and see whether it works -[22:25:21] i'll try that -[22:25:36] We need to apply all the patches sent to the packagers ml -[22:25:44] jmbsvicetto: in overlay -[22:25:44] it's nice to see policykit went stable on x86/amd64 -[22:25:55] In particular the ones that prevent some kdepim packages from crashing and kmail from eating imap mails -[22:26:04] reavertm: Great! Thanks -[22:26:06] https://bugs.gentoo.org/show_bug.cgi?id=241638 - also sci team would need to add some pkg_postinst -[22:26:13] nice -[22:26:20] jmbsvicetto: only ldap. I yet to see imap crash patch posted -[22:26:40] reavertm: hmm, I could swear I noticed an email about that -[22:27:04] well, my 4.3.9999 branch is still crashing occasionally so it's not fixed -[22:27:37] reavertm: <200909131956.22847.mcguire@kde.org> <- mailid -[22:28:01] please someone slap sci team to add that pkg_postinst message about the possible need to reemerge cln and/or libqualculate in case some linking problems appear -[22:28:49] reavertm: I've forward the mail to you -[22:28:56] jmbsvicetto: ah, that one, yeah -[22:29:43] jmbsvicetto: i dont see any problems with kmail related to imap -[22:29:55] * alexxy uses it on dayly basis -[22:30:05] alexxy: its something about moving folders -[22:30:07] neither do I (use it all the time on 2 PCs) -[22:30:08] and its ugly -[22:30:09] it sometimes crashes kmail on exit -[22:30:22] iirc you can lose a folder full of emails :P -[22:30:26] alexxy: It's an upstream commit -[22:30:39] (the patch) -[22:30:39] hmm -[22:30:56] my kmail can handle imaps folders with 100k+ mails -[22:30:59] the only problem I can see with kmail/kontact is that it sometimes lunches two instances on startup and when you close any of them it crashes -[22:31:09] someone needs to bump doxygen 1.6.1 to fix bug https://bugs.gentoo.org/show_bug.cgi?id=282598 -[22:32:06] https://bugs.gentoo.org/show_bug.cgi?id=275326 can be probably maked as non-blocker since java is now enabled by default (and there's postinst message warning that redland is known to not work) -[22:32:19] (btw it seems to be fixed in trunk soprano) -[22:32:45] sounds good -[22:33:05] reavertm: mind adding all the bugs you know about as blockers to the stabilization bug? -[22:33:29] jmbsvicetto: I'm just reading this list -[22:33:38] about doxygen - if nerdboy doesnt bump it in the next few days we can do it i guess -[22:33:48] if there are some new 4.3.1 issues that should be maked as blockers, then wel... -[22:33:53] Also, can anyone please open bugs for the KDE deps (automoc, strigi, soprano, phonon, etc), assign it to us and cc amd64 / x86? -[22:34:34] I'll create stabilization list for 4.3.1 -[22:35:33] ok -[22:35:35] separate bug for each dep? -[22:35:49] jmbsvicetto? -[22:35:53] In this case, we can have a single bug for all deps -[22:36:54] I'd like someone (or more of you) to take a look at recent 4.3.1 bugs that may be considered blockers -[22:36:55] alright -[22:37:29] if you're bored that is :) -[22:37:31] i'll have a look this weekend -[22:37:47] reavertm: I want to start looking at some, but work is leaving me dead tired when I finally get home :\ -[22:38:03] jmbsvicetto++ i have the same issue and this weekend im working... -[22:38:06] stupid deadlines -[22:38:23] ok, I think that's it when it comes to kde stabilization, anything else here? -[22:38:29] alright, anything else pending for stabilization? -[22:38:43] lets move on to Qt -[22:38:47] before we talk about gcc -[22:38:53] quick update on stabilization -[22:39:07] after talking with yngwin i pushed news item in -dev -[22:39:13] about the use flag changes -[22:39:26] i'll request stabilization after I've added the news item -[22:39:38] probably on saturday -[22:39:46] since i need to wait 72 hours -[22:39:53] nice :) -[22:39:55] cool -[22:40:05] sooooo -[22:40:21] did anyone get any info, crashes or anything else on qt 4.5 w/ gcc 4.4 combo? -[22:40:26] gcc and qt4.. -[22:40:32] no! -[22:40:39] ftr no crashes for me -[22:40:47] nope -[22:41:00] nope. I'm using 4.4.1 and 4.5.2 and all is fine -[22:41:02] it may not be that severe considering no other distros I looked into made any patches for aliasing -[22:41:14] reavertm: did you talk with upstream? -[22:41:16] wired: still no noticeable crashes here -[22:41:35] anyway - it affects all template classes like QHash, QList, QMap, QVector and maybe some other -[22:41:40] also no crasghes here with qt-4.5.x -[22:41:46] well -[22:41:51] if no one can replicate crashes -[22:41:57] worksforme -[22:42:02] :) -[22:42:06] it may be enough to add -fno-strict-aliasing somewhere to make it even less severe -[22:42:28] we could -[22:42:31] other way (thiago asuggested) is to simply (providing it's simple) - backport those classes from 4.6 -[22:42:44] but why bother touching something -[22:42:45] that works -[22:42:48] keep in mind -[22:42:52] that users are best testers -[22:42:56] and we don't have bug reports :) -[22:42:59] thats a good sign :P -[22:43:05] * alexxy has several crashes with qt-4.6 and kde4 and amarok -[22:43:21] well, yes, we may need to wait for some fireworks because maybe it's not really needed -[22:43:41] where would you add -fno-strict-aliasing? remeber those classes are templates... -[22:43:44] Oh, let me thank whoever has been doing the latest taglib{-extras} and amarok bumps -[22:44:09] if we wake one morning and bugzilla is full of Qt4 crash duplicates we'll worry about it, but seriously this is fud, there's no way they wont fix it if it ever breaks -[22:44:31] wired: fine with me -[22:44:47] well, this may not be a fud, but we've seen several aliasing-related warnings on gentoo for multiple packages -[22:44:59] so it's not a reason for panic -[22:45:19] alright -[22:45:28] so, let's wait for user/testers feedback, hmm? -[22:45:31] thats settled until a storm comes then -[22:45:39] :) -[22:45:39] ok -[22:45:44] reavertm: your floor :) -[22:45:50] last (hidden) agenda item :) -[22:46:00] I've had a couple of crashes that might be related, but I can't be sure -[22:46:25] ABCD: gather coredumps and/or just backtraces then -[22:47:06] last agenda item - stop shipping unstable svn snapshots - several reasons: -[22:47:26] - they need to be repacked (not really an issue) -[22:47:38] - they are known to be broken -[22:48:10] - they somewhat distract users from using tagged packages in portage (4.3.1) and such -[22:48:47] i dont really mind, but yeah, especially the early ones could be avoided -[22:48:51] for users' sake -[22:48:55] (of course we're not talking about dropping beta1, beta2, rc1, rc2 .. releases as those have some tagging involved, not just auto-tagging) -[22:48:57] what about providing only beta/rc version? -[22:49:06] lol nvm -[22:50:07] alexxy: you used to bump them, what do you think about not doing it anymore? :) -[22:51:37] well there some people who relay use them =) -[22:52:03] alexxy: apart from yourself? :) -[22:52:12] yep -[22:52:26] sorry, phone -[22:52:33] I say if someone wants to do them let's have snapshots -[22:53:02] as long as we have alexxy to make em eh? :P -[22:53:05] the point is, people come here and report that they are broken (like pykde4 + some temporary svn issues) and expect us to fix it -[22:53:28] and I'd prefer kde devs were not bothered with this :P -[22:53:57] oh, and they makes repoman full takes longer :) -[22:54:18] we could add ewarn-that-no-one-reads to snapshot ebuilds *** NO SUPPORT ANYWHERE *** :P -[22:54:21] reavertm: then simply add something like -[22:54:22] (whatever this means in english :P) -[22:54:35] reavertm: I agree with bonsaikitten, but we should add a note that may have been lost with time - let's add a pkg_postinst for those ebuilds telling users not to report bugs to Gentoo -[22:54:42] snapshot is known to be broken so report all busg about them to bugs.kde.org -[22:54:43] =) -[22:54:46] to eclass -[22:54:53] omg -[22:55:03] something like that, yes -[22:55:10] they'll come down to us with grenades man -[22:55:11] lol -[22:55:15] also - less versions - less synchronization work -[22:55:17] okay with me, so long as it's conditional on [[ -z ${I_KNOW_WHAT_I_AM_DOING} ]] :) -[22:55:28] (the message, that is :) ) -[22:55:31] I know not all of you do ebuild synchornization work but.... :) -[22:55:58] and I don't mind dropping those versions, either :) -[22:56:13] at least I'm not going to touch them anymore -[22:56:59] and I don't want to see blocks involving 4.3.56 -> 4.3.57 changes in ebuilds :P -[22:57:11] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) -[22:57:12] so lets leave it at "as long as someone is interested lets keep em and add a fat warning in eclass" -[22:58:03] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) -[22:58:12] great -[22:58:15] actually we should only provide blocks that involve versions that are going to be in tree -[22:59:11] pesa [21:57:13] so lets leave it at "as long as someone is interested lets keep em and add a fat warning in eclass" -[22:59:40] fine with me, thanks :) -[22:59:57] i don't really use them -[23:00:34] reavertm: why? if something has rdep "! so, anything else left for today? -[23:01:18] i think we're good -[23:01:22] assuming all goes well -[23:01:35] next week we'll be ready -[23:01:47] ABCD: it's about always increasing bloat and complexity of those blocks -[23:01:48] whoever closes the last blocking bug should bug all the rest -[23:02:06] and begin stab(ilization) procedures :) -[23:02:29] reavertm: that's why I created a add_blocker function that takes care of all that stuff [except that I was told I shouldn't use it yet...] -[23:02:39] *** Parts: Pesa (n=Pesa@bluemchen.kde.org) -[23:02:52] ok, then I'm going to do something "stupid" like watching tv or playing a stupid psp game ;) -[23:02:55] I know -[23:03:23] jmbsvicetto: yay! heheh, i'll fire up my xbox :P -[23:03:45] :) -[23:03:48] later -[23:03:53] meeting end! -[23:04:00] jmbsvicetto: i'll add log same place :) -[23:04:24] wired: thanks diff --git a/meeting-logs/kde-project-meeting-log-20100225.txt b/meeting-logs/kde-project-meeting-log-20100225.txt deleted file mode 100644 index 04fa9dd..0000000 --- a/meeting-logs/kde-project-meeting-log-20100225.txt +++ /dev/null @@ -1,612 +0,0 @@ -[21:27:14] ok let's start -[21:27:23] roll call plz -[21:27:26] !herd kde -[21:27:28] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, ssuominen, tampakrap, tgurr, wired -[21:27:48] here -[21:28:17] . -[21:28:43] here -[21:28:56] * alexxy here or there -[21:29:00] alexxy: indeed :P -[21:30:19] . -[21:30:25] Sput: we need you for this one, present? -[21:31:03] lets start with kdepim -[21:31:14] jorge is going to be around in ~10 minutes -[21:31:22] hmm -[21:31:26] so the relevant tasks even for him should be that way preserved :] -[21:31:31] TOPICS: http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/meeting-2010-02-25;h=dafe5aa85c43ba9737c783576af83c972ea82afa;hb=594ec14216daa0f2f331295d4baff3e0f6d78a5c -[21:32:14] ok about kdepim and enterprise useflag -[21:32:32] also can we discuss snapshots for 4.5 pre alphas? -[21:32:33] =) -[21:32:50] ohnoes -[21:32:51] sure, along with this -[21:33:11] *** Quits: j0hu (~quassel@quassel/contributor/j0hu) (Read error: Connection reset by peer) -[21:33:19] also using lxc as testbead for testing kde builds -[21:33:25] the kdepim issue is about the trunk kde i don't know if anyone of you is interested in it -[21:33:30] * alexxy prepared some containers -[21:33:55] tampakrap: what issue? -[21:34:01] kmail is broken in current trunk, i tried to package the enterprise branch which is supposed to work -[21:34:26] why we should care about trunk? -[21:34:31] afaik the enterprise branch should be available for releases as well -[21:34:39] reavertm: because that's what's going to be in 4.5 -[21:34:44] enterprise branch should be availible for everything -[21:35:01] scarabeus: jmbsvicetto and i talked with a kde dev [cant recall his name right now] who told us enterprise branch is what they really care about -[21:35:24] we should just monthly generate our own kdepim tarball from that branch -[21:35:27] and be done with it -[21:35:34] maybe even forgot about non-enterprise :] -[21:35:36] considering the [crappy] state of kdepin right now, thats a good idea -[21:35:39] two packages failed to compile from enterprise stuff, plus a flag isn't possible for trunk as ebuilds are different -[21:35:40] kdepim* -[21:36:28] 1) there is enterprise related cmake switch in cmakelists.txt - maybe it should be used when bulding enterprise branch -[21:36:47] am i right that kmail is broken because of mail storage migrartion to akonadi? -[21:36:49] 2) still don't see why we should care :P -[21:37:02] reavertm: enterprise should actually work OK -[21:37:08] and kde devs care about it not breaking -[21:37:17] at least thats what we've been told -[21:37:18] :p -[21:37:22] i agree with reavertm, too much work, maybe we should just wait -[21:37:28] too much work for nothing -[21:37:29] problem is it does not follow kde release schedule -[21:37:44] it is released with each even release -[21:37:51] especially if apparently they're going to merge it eventually? -[21:38:40] no its not going to be merged -[21:38:49] now, I've not tried to build it yet - is it possible to use our ebuilds? -[21:38:59] or it differs too much so that it's impossible? -[21:39:04] okay, i am having hardware issues with my trunk machine and don't know when it will be back, so i can't work on it any more -[21:39:10] it differs too much -[21:39:21] it's not impossible, it is way too much work -[21:39:21] Hello -[21:39:26] tampakrap: you are talking about trunk, we are talking about releases -[21:39:28] hey jmbsvicetto -[21:39:34] sorry for being late -[21:39:37] i'm talking about enterprise itself -[21:39:40] I confused the hour again :\ -[21:39:52] * spatz is back -[21:40:16] and my opinion is the same for the snapshots, way too broken to be provided to users -[21:40:45] i can announce it and blog it, whatever, that we can't provide them if you agree -[21:40:49] other issue, how are we going to provide it? split like kdepim? -[21:41:15] yes, it needs different branch of ebuilds -[21:41:44] anyone willing to work on it? -[21:41:54] and probably blocking kdepim... -[21:42:01] or just postpone it for next meeting? -[21:42:03] exactly -[21:42:17] ok i personaly cant promise i will devote time to it :/ -[21:42:30] so it would need some maintainer, even non dev -[21:42:39] just in overlay so we see the potential -[21:42:44] and then we can put it into tree -[21:42:48] agreed -[21:42:50] i could announce it -[21:43:28] ok we should anounce global call if we find someone interested, i think we can help with basics but are busy enough to do it ourselves -[21:43:38] tampakrap: so could you sent it to dev-anounce and desktop mls? -[21:43:45] although i doubt there will be someone willing to do so much work for nothing -[21:43:47] I'm not interested in kdepim, so I won't be working on it -[21:44:05] yes, even blog the whole kdepim problem in trunk -[21:44:34] and thus i'm against providing the snapshots ( alexxy ) yet -[21:45:02] yeah no snapshot until .70 as with 4.4 should be done -[21:45:16] *** Joins: Civil (~Civilian@95-27-138-158.broadband.corbina.ru) -[21:45:16] .85 I would say even :P -[21:45:21] haha -[21:45:25] no =) -[21:45:27] .70 -[21:45:28] .70 is enough for ricers :D -[21:45:28] beta 1 :P -[21:45:30] 4.5.1? :P -[21:45:33] aka alpha0 -[21:45:34] =) -[21:45:36] btw, word of warning -[21:45:45] when kmail is ready i'd say -[21:45:52] dev.ge.o will migrate to new hardware soon, so expect a day or two of confusion -[21:46:02] thats good to know :] -[21:46:07] thanks patrick -[21:46:33] ok i think we should get back on track with topic one :] -[21:46:38] i think we are ready on this (btw i'm writing summary as soon as we speak) -[21:46:55] so we dont jump over those carefully written numbered topics in chaotic order :] -[21:47:08] ok back to topic one: new leader elections -[21:47:26] candidates: jmbsvicetto, scarabeus, plz vote (devs only) -[21:47:28] bring it on! -[21:47:48] I vote yes ;) -[21:47:52] DrEeevil: you cant -[21:47:53] pick -[21:47:55] i vote scarabeus (sorry jorge :) ) -[21:48:11] DrEeevil: :P -[21:48:12] I'd like to hear manifesto from both! ;) -[21:48:17] * reavertm runs -[21:48:22] lol -[21:48:23] tampakrap: no hurt feelings ;) -[21:48:45] not to break kde and keep it working for everyone of us :] and provide my qa tools for kde -[21:48:49] i vote for scarabeus =) -[21:48:53] scarabeus: nothing prevents us from having more than one lead, but let people choose -[21:48:58] note that this manifesto wont change for me if not voted for :] -[21:49:03] hmm -[21:49:09] what qa tools? -[21:49:11] or lets have two leads -[21:49:12] =) -[21:49:20] if its possible -[21:49:22] i have quite few scripts that checks x11 state -[21:49:25] i like that idea too -[21:49:26] no, just one to rule them all :) -[21:49:32] and i can adjust it for kde -[21:49:38] no, one leader is enough -[21:49:39] which i plan for month or so already :D -[21:49:42] we are a large herd -[21:50:00] actualy multiple leads are weird, just pick guys -[21:50:08] it does not matter to jorge or me who wins :] -[21:50:16] we just comply to the 1 year election rule :] -[21:50:21] how many members with voting power are here? -[21:50:33] lets vote and find out -[21:50:34] ;p -[21:50:39] 9 -[21:50:56] sorry 10 -[21:51:12] what about 5:5 ? -[21:51:22] reavertm: that would not amuse me -[21:51:36] ok, let's hear it -[21:51:47] in case 5:5 i'll change my vote :P -[21:51:47] * ABCD votes scarabeus -[21:51:55] * reavertm votes scarabeus -[21:51:56] * alexxy votes scarabeus -[21:52:03] scarabeus: I'll break the tie ;) -[21:52:03] * tampakrap votes scarabeus -[21:52:11] * wired votes scarabeus -[21:52:14] * spatz votes scarabeus -[21:52:15] * jmbsvicetto votes in scarabeus -[21:52:20] lol -[21:52:23] ok ok ok -[21:52:23] nice -[21:52:25] i get it -[21:52:38] like it or not you're lead -[21:52:38] :p -[21:52:39] * scarabeus votes for jmbsvicetto :] -[21:52:39] congrats now abuse your powah :P -[21:52:40] I said before I would prefer to have someone else being lead ;) -[21:52:47] scarabeus: No!!!! :P -[21:52:48] * wired remembered -[21:53:04] Congratulations Tomas -[21:53:13] scarabeus: \o/ congrats :) -[21:53:22] Now everyone i guess we should drink something good in favor of our good benevolent now-ex lead. So on Jorge :] -[21:53:38] and thanks, lets i will try to not doom us all :] -[21:53:59] * wired has a beer open =] -[21:54:05] * scarabeus too -[21:55:02] ok little girls you played enough for today, now let's move on -[21:55:15] Review work flow for KDE minor bumps and improve collaboration with arch teams -[21:55:48] 1) BUG -[21:55:48] 2) keywordlist -[21:55:48] 3) portage addition -[21:55:48] 4) profiles touching -[21:56:00] this should be workflow from now-on so we dont touch anyones toes -[21:56:13] scarabeus: The Founder Power has been bestowed on you for #gentoo-kde ;) -[21:56:22] * ssuominen votes scarabeus -[21:56:28] abcd * gentoo/xml/htdocs/proj/en/desktop/kde/index.xml: We have a new lead! -[21:56:36] :P -[21:56:57] ssuominen: ha ha ha :D -[21:57:10] all cards have been played already ;) -[21:57:15] scarabeus: I propose something different -[21:57:31] jmbsvicetto: i just wrote this one after start with jer, and then i got distracted -[21:57:38] jmbsvicetto: how does your approach look? -[21:57:43] if its better just make it policy -[21:57:44] :] -[21:58:01] its once per 6 months, and it wont hurt to have written down somewhere in Documentation/ -[21:58:14] good idea, whatever we decide on this should be forwarded as a global policy -[21:58:23] scarabeus: 1) Ask arch teams to test new deps in the overlay. 2) If they don't want to use the overlay, try to add a snapshot or a early release masked in the tree and ask them to keyword it -[21:58:35] scarabeus: then your policy -[21:59:06] i don't like this approach -[21:59:18] well, your 3) would be done before, so it could be 3) unmask in the tree -[21:59:18] what if they do something stupid while using the overlay? -[21:59:56] tampakrap: I might not have been clear, I meant to let them try the ebuilds from there and for us to add their keyword -[22:00:07] tampakrap: I'm not giving commit access -[22:00:07] jmbsvicetto: sounds sane -[22:00:18] altho i dont think about that snapshot into main tree -[22:00:20] i was not clear -[22:00:26] deps can go if released -[22:00:28] but not the kde -[22:00:33] I don't like snapshots in tree either -[22:00:33] it is annoying 280 packages -[22:00:38] i meant what if they use other testing ebuilds while using the overlay? -[22:00:42] its 4 hours commit -[22:00:47] (even if those are kde deps just) -[22:00:58] scarabeus: The snapshot as a last resort if upstream doesn't have a release 2 weeks / 1 month before getting the new version in the tree -[22:01:27] but only for deps -[22:01:32] no touching of kde-base/ itself -[22:01:35] I'm only talking about new deps -[22:01:35] there is problem - we have no arch team members in kde team -[22:01:40] we have -[22:01:42] for amd -[22:01:43] :D -[22:01:48] only ssuominen, but we would need some for other archs -[22:01:58] me stable for amd64 from time to time -[22:02:00] i can keyword arm and mips -[22:02:01] =) -[22:02:09] scarabeus: It's 30 minutes if you commit at category level. -[22:02:38] Philantrop: i know, but i managed to clash 3x already with someone else :] -[22:02:42] if you commit in 10 threads then it takes about 5 minutes -[22:02:45] even when i announced it :D -[22:02:46] to commit whole kde -[22:02:54] and since keywording kde is quite a bottleneck .. kde dev (which clearly uses kde) could do it faster -[22:02:56] hmm i could thread bump tool indeed -[22:03:13] scarabeus: force commit and kick anyone interfering from the herd. That's what I did. :-> -[22:03:30] scarabeus: i added kde 4.4.0 in about 5-7 minutes to tree -[22:03:35] * ABCD is x86-linux and amd64-linux -[22:03:38] working with 10 threds -[22:03:48] *threads -[22:04:05] ok lets write out the rules on the Documentation -[22:04:09] and i will thread the bumptool -[22:04:11] its quite simple -[22:04:44] <- not a part of amd64, just have stable chroot for xfce/kde/xorg/base-system/media -[22:05:05] i also stable only when i have long night :D -[22:05:19] but people mostly dont complain if qa guys stable on archs they can test :] -[22:05:53] i would say this topic should be reviewed on next meeting with respective prepared documentation for approach in the overlay, anyone some additions? -[22:06:33] no problem in this, i just hope there will be something prepared until next meeting -[22:06:59] ok kde-4.3.5 then :] -[22:07:01] i think we can use lxc containers instead of chroots -[22:08:03] so we are waiting on archies only, are there any issues with it? -[22:08:35] what's advantage of lxc over chroot? -[22:08:49] (which I can boot to natively as well) -[22:08:58] it run separate system in separate namespace -[22:09:10] so its more closer to vms -[22:10:28] VM's -[22:10:29] =) -[22:10:38] ok back to topic -[22:10:46] so we are waiting on archies only, are there any issues with it? -[22:11:25] anyone? -[22:11:35] not that I've seen, as an archie :D -[22:11:55] ok next one -[22:12:03] *** Joins: aboow (house5@gateway/shell/bshellz.net/x-vhnffmhwlxzbhinj) -[22:12:05] tampakrap: won't be really online until in about 1 hour -[22:12:06] sitting in the train currently with shaky net -[22:12:24] just one addition, dont remove 4.3.4, just wipe out 4.3.3 and 4.3.4 in one step when 4.3.5 is ready :] -[22:12:34] if anyone gets remove ideas :P -[22:12:35] Sput: ok we can talk then -[22:12:51] kde 4.4 status -[22:12:51] s/anyone/alexxy/ -[22:12:59] * alexxy has remove idea of old kde's -[22:13:00] :) -[22:13:01] :D -[22:13:15] referring to kdepim: if we found a way to package the current 4.4 kdepim in a way that it works with -9999 (no idea, copying the ebuilds from 4.4 into some overlay and renaming them to -9999) that should be more or less easy -[22:13:21] as 4.4 kdepim is supposed to work with trunk kde -[22:14:22] Sput: we can talk about it later, the other members have already expressed their opinions and you are messing with the topics now :) -[22:14:34] back again to kde 4.4 -[22:14:46] any known problems? blockers? -[22:14:55] yeah it is slightly flaky -[22:14:57] archies =) -[22:15:02] i got few crashes in kwin and plasma -[22:15:24] also, congrats scarabeus :) -[22:15:25] few crashes in krunner and plasma -[22:15:27] me too, so i guess 4.4.1 will be the stable candidate -[22:15:30] also the virtuoso migration is not exactly funky working out of the box for some -[22:15:36] 4.4.1 or 4.4.2 -[22:15:41] 4.4.2 most likely -[22:15:42] we shall see after 4.4.1 release -[22:15:51] ok -[22:15:51] i would rather wait too -[22:15:58] judging from the past... -[22:15:59] anything else on 4.4? -[22:16:20] i guess not -[22:16:32] jmbsvicetto: amarok and mysql 5.1 status -[22:16:32] *** Joins: hwoarang (~mystical@gentoo/developer/hwoarang) -[22:16:49] poor Jorge -[22:17:03] oh wait, akonadi is indifferent... -[22:17:26] virtuoso migration failed for me -[22:17:31] amarok works with mysql 5.1 -[22:17:33] ok -[22:17:38] if it compiled with -FPIC -[22:17:42] so, amarok and mysql-5.1 -[22:18:01] Fortunately it's way better than I feared when I added it to the agenda -[22:18:32] The ebuilds have been updated and no one complained for the past 3 days(?) so it seems users are getting used to it ;) -[22:18:43] AIUI, amarok[-embedded] should work just fine - amarok[embedded] has the same problems with 5.1 that it did with 5.0 - namely, that we need a libmysqld.so again -[22:18:50] A few people are still following the bug, but we can live with it as is -[22:19:03] ABCD: exactly -[22:19:52] there's another quirk, preserved-libs will keep the libmysqld.so for those upgrading, which does allow amarok to work (it happened here), until we have an abi / api incompatible change -[22:20:32] that is for amarok to work with mysql-5.1 - but that might cause serious issues "sooner than later" -[22:20:56] in any case, I've resumed my work to get a working patch, so let's see if I can do this before we have to elect a new lead ;) -[22:21:31] :D -[22:21:40] thank you x-boss -[22:21:47] how about we stop supporting the embedded part :] -[22:21:51] and just force full amarok -[22:21:58] patch-- -[22:21:58] ? -[22:22:00] like akonadi does -[22:22:01] ^^!! -[22:22:08] let them have it! -[22:22:20] that should teach those bastards :P -[22:22:30] :D -[22:22:38] ok anything else? serious? -[22:22:42] ok lets go for koffice -[22:22:47] i guess i should answer that one -[22:22:59] problem with koffice is that expect graphic tools it is totaly unusable -[22:23:00] * reavertm fixed kword recently -[22:23:02] go on -[22:23:11] and it needs all deps reviewed and updated based on cmakelists -[22:23:36] i personaly use only krita and dont care about rest of the bunch so it needs some dedicated guy whom will actualy use the stuff -[22:23:49] i will take this one but i may need your help -[22:24:01] query still works :] -[22:24:19] *** Quits: aboow (house5@gateway/shell/bshellz.net/x-vhnffmhwlxzbhinj) (Disconnected by services) -[22:24:49] anything else? -[22:24:57] nop, nothing from me to add -[22:25:13] ok knetworkmanager -[22:25:19] scarabeus: no harm in keeping embedded for now -[22:25:25] jmbsvicetto: oky -[22:25:33] ok we need snapshot -[22:25:40] and monthly refreshed snapshot probably -[22:25:43] scarabeus: if I can get a patch for mysql, we can make it simple again -[22:25:45] knetworkmanager crashes plasma here, i didn't prepare a snapshot i just tested with live ebuild -[22:25:46] who is willing to take that one out :] -[22:25:59] tampakrap: well plasmoid can be disabled -[22:26:07] tampakrap: most people are interested in kcm module -[22:26:22] we need monthly refreshed snapshot from svn -[22:26:23] i didn't use the plasmoid -[22:26:31] only the system tray item -[22:26:35] the same thing -[22:26:39] sure -[22:26:40] kcm is in systemsettings -[22:26:45] tampakrap: is it working? -[22:26:53] kcm wasn't working though :) -[22:26:58] ok -[22:27:03] so anyone uses NM these days -[22:27:07] or are we all on wicd? -[22:27:16] i guess i didn't have time to test it since it was crashing -[22:27:43] i can prepare a snapshot but it will need a lot of testing and i'd prefer if someone with non-crashing results would do it -[22:27:58] i'm on openrc init scripts and wpa_gui -[22:28:18] *** Joins: jmrk_ (~jmrk@dslb-088-064-075-227.pools.arcor-ip.net) -[22:28:19] tampakrap: ok just add it masked to main tree -[22:28:25] and lets ask users for testing and feedback :] -[22:28:29] anyone else? no? -[22:28:50] good question, there is quite few more team members :P -[22:28:55] who is willing to do this one? :] -[22:29:36] ABCD / reavertm? -[22:29:51] there is also DrEeevil whom enjoy the user feedback anyway :D -[22:30:04] I don't use NM -[22:30:19] tampakrap: i got it -[22:30:22] tampakrap: coordinate with dagger -[22:30:28] tampakrap: afterall he is maintainer of NM -[22:30:34] ah yes -[22:30:39] ok next topic -[22:30:45] * reavertm does have static network -[22:31:14] the documentation is fine, i updated it about a month ago, if you all want can take a look and propose fixes -[22:31:19] two issues though: -[22:31:32] 1) jmbsvicetto promised to clean up the member list -[22:31:48] which will be probably my task now :/ -[22:32:01] 2) i have an open bug about xdm configuration which i don't like, i'd like your feedback -[22:32:09] i will sent mail to everyone who does not have 5 commits month into kde cat -[22:32:13] scarabeus: I sorted it asciibetically for you (except your name is at the top) :D -[22:32:34] ABCD: lovely, you earn the big plus point :P -[22:32:50] http://bugs.gentoo.org/attachment.cgi?id=220755&action=view -[22:33:08] scarabeus: also plz remove qt members they are still there -[22:33:34] tampakrap: yeah -[22:33:44] tampakrap: I'll talk to scarabeus about that -[22:33:46] a small note: i didn't add the usefull links in the guide as jmbsvicetto pointed as they are not that useful :P -[22:34:00] tampakrap: recommend dejavu and droid fonts for christ sake -[22:34:26] tampakrap: other than that you should point to x11 guide which should describe xdm config iirc -[22:34:39] cool -[22:34:43] i like that -[22:35:26] last point: i'm going to blog about kde3 removal and the kde-sunset existence, so that ppl will hopefully stop filling stupid kde3 bugs anymore -[22:35:38] its only gnu_andrew -[22:35:45] and he will fill them anyway just to annoy us -[22:36:05] heh -[22:36:07] i don't have to say anything else about the docs, just i am waiting for you to take a look plz -[22:36:24] remove kdeprefix from docs -[22:36:31] kde guide is way too red -[22:36:45] funny, i agree on that -[22:36:51] friendly 'notes' everywhere -[22:37:10] it's impossible to follow -[22:37:11] :D -[22:37:22] yeah just wipe out kdeprefix from docs is good idea -[22:37:34] about kde3 and kde-sunset, my opinion is that we did one thing wrong -[22:37:49] also maybe sets... -[22:37:56] my initial goal was never to make kde-sunset a "dumping ground" to be mastered by users alone -[22:38:01] info about sets - remove as well? -[22:38:14] reavertm: i think we can have a note about sets, but keep metas as the default option -[22:38:27] nah sets are weird -[22:38:31] they are bbd now -[22:38:32] jmbsvicetto: i'm sure everyone knows that, but you can't force devs to work on it :) -[22:38:39] jmbsvicetto: i'm still following the kde-sunset commits -[22:38:43] I'd rather have an overlay with commits just by devs and trusted committers (akin to sunrise) and another overlay with free access by users -[22:38:55] jmbsvicetto: well your idea assumes devs are interested -[22:38:59] but now it's too late, so we'll have to live with it as is -[22:38:59] jmbsvicetto: we have none of those -[22:39:00] :p -[22:39:15] * jmbsvicetto cries for sets -[22:39:34] jmbsvicetto: not in this implementation, sorry -[22:39:34] I know (devs and KDE3) -[22:39:55] ok, i guess we are done -[22:39:56] pretty much all gentoo devs have commit access to that overlay.. -[22:40:48] the following two topics are long time ideas i had -[22:40:54] drop prefixes from kde ebuilds (like kdeartwork etc) -[22:40:59] I use NM with the plasmoid and both work great -[22:41:01] trunk though. -[22:41:22] if anyone dares to remove the plasmoid from -9999 I will keel him -[22:41:23] :) -[22:41:23] tampakrap: things like kdebase-data... you think it should just be "emerge data"?! -[22:41:45] well no -[22:41:48] drop prefixes? no -[22:41:51] but for kdebase-startkde yes -[22:41:56] add prefixes? more likely :P -[22:41:58] or for the artwork ones -[22:42:01] please no another dev-haskell/ -[22:42:09] try emerge opengl or emerge x11 -[22:42:20] startkde makes sense -[22:42:20] or zlib for that matter -[22:42:23] or chromium :) -[22:42:29] same with emacs -[22:42:35] yeah i think it is not worth the gain -[22:43:11] whatever I try to install, it tells me that I need to choose between sam app-emacs/XXX and /XXX -[22:43:15] we dropped -plugin- from xfce-extra/'s for a long time, and I can tell you... it was, nothing but a pain -[22:43:29] tampakrap: oh, and kdeartwork-kscreensaver can't be "kscreensaver", because kde-base/kscreensaver is kdebase-workspace -[22:43:34] scarabeus: you wanted to add prefixes some time ago -[22:43:41] ok i got your point -[22:44:04] to have module precede package name - like kdegames-sth -[22:44:22] reavertm: i thought of it bit more, and it would just take too much time :] -[22:44:22] reavertm: it's the same i guess, too much pain, doesn't worth it -[22:44:29] so that one can easily know what module is this withour reading ebuild -[22:44:41] grep KMMODULE is simple :D -[22:44:47] or KMNAME -[22:44:48] :] -[22:44:53] yest, misleading -[22:44:55] well, i don't want to emerge kdepim-kmail -[22:45:04] module = kdepim, not subdir in kdepim -[22:45:20] KMMODULE is a bit unfortunate name... -[22:45:39] never mind -[22:45:43] indeed, sadly i dont want to redesing the eclass again :D -[22:45:52] reavertm: i bet you dont want either -[22:45:52] we have one convention already -[22:46:01] we all agreed i guess not to touch anything -[22:46:06] next? -[22:46:21] for those that are in multiple module, we have plasma-apps, plasma-workspace, plasma-runtime -[22:46:25] same with solid- -[22:46:35] let's just keep it when needed -[22:46:40] change kde-meta (and @kde-*) to include all modules (plus the developer specific ones) -[22:46:44] reavertm: sure -[22:46:52] i dont get what are you proposing with this topic :P -[22:47:08] it should include even kdesdk? -[22:47:11] thats baad idea -[22:47:24] 99% of users dont want it -[22:47:31] they just emerge kde-meta cause they are lazy -[22:47:45] that's what i'm proposing yes -[22:47:54] -1 -[22:48:07] and how is kdewebdev more useful? -[22:48:23] on the other hand, we don't get bugreports for them because nobody is using this -[22:48:25] how about a developer something flag? -[22:48:33] exactly! -[22:48:43] (less bugs -> more fun) -[22:48:53] hm tampakrap useflag would be bad, not supported on sets right? -[22:49:00] sorry -1 from me -[22:49:00] tampakrap: developer useflag could work on meta -[22:49:03] but what for sets -[22:49:06] its baad idea -[22:49:15] if user wants it he can merge kdesdk-meta -[22:49:19] or kdewebdev-meta -[22:49:29] kdewebdev is already in kde-meta -[22:49:41] introduce a new set? kde-lazy? :p -[22:49:47] kde-meta shouldn't be used by users -[22:49:53] why? -[22:49:59] at least i think sets should include them all -[22:50:01] +1 for tampakrap's proposal, we should have everything in there. -[22:50:11] i except kde-meta to install everything -[22:50:32] expect* -[22:50:33] wired: I hope you "expect", not "except" :D -[22:50:39] expect gr -[22:50:43] for me kde-meta is http://websvn.kde.org/trunk/KDE/ -[22:50:54] a "recommended" USE flag could be introduced to skip stuff not needed by users -[22:50:55] ABCD: he uses qt with the "exceptions" use flag ;) -[22:51:10] kdeexamples O_o? -[22:51:23] if you add the kdebindings stuff to kde-meta, I'm sure we'll get a few interesting bug reports ;) -[22:51:44] (wom 96 -[22:52:01] ok then, i'll rephrase: how about a developer something use flag in metas and include everything in sets? -[22:52:10] we can have kdefull-meta -[22:52:13] or somethingl ike -[22:52:14] at least for sets it makes sence, users can create their own -[22:52:17] kde-burnmycomputer -[22:52:27] but not kde-meta -[22:52:35] it is full blown working kde desktop -[22:52:37] not full kde -[22:52:44] i still prefer the use flag idea -[22:52:57] lets discuss this on alias -[22:53:06] well, we can have kde-meta installa all, but advice to use kdebase-meta instead -[22:53:08] in gentoo-desktop -[22:53:14] or that -[22:53:23] but there will be duncan -[22:53:24] ok let's discuss it in the mailing list, i'll start the thread -[22:53:28] and who is going to read that :D -[22:53:32] i won't -[22:53:36] i have work to do -[22:53:43] you know -[22:53:52] gmail used to automatically clasify duncan as spam -[22:54:12] cool next topic -[22:54:14] 13 - stabilization of misc kde apps -[22:54:17] :P -[22:54:25] qa scripts can help with that -[22:54:27] wired promised a script :) -[22:54:32] for qt also -[22:54:34] but we have quite too much packages -[22:54:39] in kde -[22:54:43] it takes some time to compute -[22:54:43] L:D -[22:54:48] oioi i had to do that for kde as well ^_^ -[22:54:57] wired: okey your job :P -[22:55:01] ok i'll repromise to the new lead as well -[22:55:03] show us cookies on next meeting :D -[22:55:06] i have a todo file now! -[22:55:08] :P -[22:55:11] next week plz -[22:55:13] max -[22:55:20] scarabeus: kick him please :D -[22:55:26] last topic shut up -[22:55:28] 14 - patches of kde-packager -[22:55:57] i was kinda busy with exams last month i was not following the ml -[22:56:08] reavertm maybe knows anything? -[22:56:19] ABCD is suposed to apply kde-packager patches -[22:56:22] or jmbsvicetto i think he brought up the subject -[22:56:28] as was decided on one of the former meetings -[22:56:42] well, there are some and they need to be applied as they appear.... -[22:57:00] yeah, there have been a few patches sent to the packagers ml that didn't go applied -[22:57:00] ABCD: will you handle it? -[22:57:12] I lag here a bit (also due to limited time recently) -[22:57:14] anyone else willing to help on this? -[22:57:15] I think there are 3 for 4.4 by now -[22:57:26] I hadn't be able to get on the list until very recently, so I haven't seen those patches yet -[22:57:50] i am qute busy in x11 tracking so i cant do such pernament task for kde sadly :/ -[22:57:53] ABCD: I thought I had asked for everyone to be put in the ml -[22:58:18] I'll try to follow the ml -[22:58:29] ok, jmbsvicetto / ABCD will you handle this? -[22:58:34] in the least I can open a bug with the patch / patch link -[22:58:42] sure that too -[22:59:15] scarabeus should be able to add new people to the ml, but in any case I can always poke rdeiter and the kde infra team to get it done -[22:59:22] I'll look into it too -[22:59:28] great -[22:59:39] alexxy: what did you want to talk about? -[22:59:46] jmbsvicetto: thx for the hint, be sure i will ask anything i would not know how to do :] -[22:59:58] scarabeus: any time you need -[23:00:26] alexxy: ping -[23:00:47] i have 1 thing: we need another kde HT lead, i cant do herd testers lately due to limited time, and it would be sad if we loose that nice recruit count, dont you think? -[23:00:52] anyone wants to pick that one up? -[23:01:38] which are the requirements? -[23:02:00] tampakrap: be on irc, actively follow the new recruits and help them -[23:02:03] and motivate them -[23:02:09] like devrel said, a few children and 'mature' attitude ;) -[23:02:11] come on you saw me in action as one of the closest -[23:02:18] you know what i did :] -[23:02:23] ok i'm not good at it -[23:02:39] *** Quits: willikins (~rbot@gentoo/bot/Willikins) (Read error: Operation timed out) -[23:02:51] i tend to insult ppl like wired three times per day before food -[23:03:14] good training is actualy teaching :] -[23:03:29] ok we keep it as-is and i will anounce on alias :] -[23:03:40] reavertm: I'm on devrel ;) -[23:03:47] tampakrap: pong -[23:03:48] =) -[23:03:57] alexxy: topics you wanted to discuss? -[23:04:00] ok /me has to disappear -[23:04:02] so have fun -[23:04:03] make it quick plz -[23:04:06] and dont break a shit -[23:04:07] :D -[23:04:11] reavertm: I guess I'm "old enough" at least ;) -[23:04:16] hehe -[23:04:18] seems we already discussed them all -[23:04:19] =) -[23:04:24] cool -[23:04:27] meeting closed -[23:04:32] i'll prepare the summary -[23:04:32] yep -[23:04:52] it was cool to moderate you all, next time don't bring your dolls plz -[23:05:55] * tampakrap joke fail -[23:05:59] dolls? I didn't knew I had to bring mine!! -[23:06:51] o_O -[23:12:24] *** Quits: reavertm (~quassel@gentoo/developer/reavertm) (Remote host closed the connection) -[23:15:20] *** Joins: reavertm (~quassel@bsb151.neoplus.adsl.tpnet.pl) -[23:15:21] *** Quits: reavertm (~quassel@bsb151.neoplus.adsl.tpnet.pl) (Changing host) -[23:15:21] *** Joins: reavertm (~quassel@gentoo/developer/reavertm) -[23:22:53] *** Parts: spatz (~spatz@gentoo/developer/spatz) -[23:23:37] reavertm: ping -[23:23:59] hmm? -[23:24:23] sorry for doing this, yngwin requested to add to topics the desktop profile split but i failed to push :P -[23:24:45] is there anything we should discuss (in ml i guess) or can we proceed on this? -[23:24:53] no, please do -[23:25:14] we voted on this already, no? -[23:25:19] yes -[23:28:02] *** Quits: jmrk_ (~jmrk@dslb-088-064-075-227.pools.arcor-ip.net) (Quit: Konversation terminated!) -[23:35:05] tampakrap: does this mean it is going to be implemented now, or? -[23:35:13] yes -[23:35:19] i will do it -[23:35:22] ok, tnx -[23:35:27] i 'll write it in summary too -[23:35:34] so you can have proof :) -[23:35:36] good :) -[23:36:02] otherwise i will just remove the ridiculous mysql requirement from desktop profile myself ;) -[23:36:04] sorry for not bringing this up, i thought i pushed it diff --git a/meeting-logs/kde-project-meeting-log-20100318.txt b/meeting-logs/kde-project-meeting-log-20100318.txt deleted file mode 100644 index 52960de..0000000 --- a/meeting-logs/kde-project-meeting-log-20100318.txt +++ /dev/null @@ -1,206 +0,0 @@ -[22:02:03] alexxy / bonsaikitten / dagger / jmbsvicetto / lxnay / mrpouet / reavertm_ / scarabeus / spatz / wired -[22:02:05] meeting time -[22:02:12] http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/maintainers/meetings/meeting-2010-03-18;h=b056be61645fbd793cf07cb9d0eb968e961cb2c1;hb=HEAD -[22:02:21] who is here? -[22:02:25] mesa here -[22:02:29] me -[22:02:39] boss around -[22:02:44] although my connection is flaky -[22:02:47] ping me when it gets to subprofile stuff I guess. Preoccupied 30 more mins -[22:03:00] leio: i was about to ping me -[22:03:07] ok let's skip it for now -[22:03:12] s/me/you -[22:03:18] well, in that agenda it's last item anyway.. -[22:04:11] let's wait another 10 mins, many ppl are away -[22:04:31] -*- alexxy here ;) -[22:05:54] I will start with the lighter thing -[22:06:00] since there were no objections to new rules -[22:06:01] --> willikins (~rbot@gentoo/bot/Willikins) has joined #gentoo-meetings -[22:06:10] woohaa bot is back -[22:06:13] !herd kde -[22:06:16] i will start enforcing them -[22:06:36] where is the draft first of all? -[22:06:39] so i will thin up team list probably -[22:06:40] and why isn't it in git? -[22:06:52] what for my rules? -[22:06:55] i sent you mail -[22:07:06] ok, commit it in git :) -[22:07:36] http://dev.gentoo.org/~scarabeus/kde-team-rules.html -[22:08:04] i would have to find that rst first :P -[22:08:15] pong -[22:08:28] ok let's start now -[22:08:29] I just need a minute to put my things down and I'll be back -[22:08:34] again who is here? -[22:08:51] scarab -[22:09:09] -*- spatz ← -[22:09:09] !herd kde -[22:09:26] (it responds to pm at least) -[22:09:36] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, tampakrap, tgurr, wired -[22:09:57] -*- wired o/ -[22:10:25] -*- alexxy partialy there or here or somwhere else -[22:11:09] scarabeus: go on with the removal of members plz -[22:11:18] what's the news on this? -[22:11:28] well you didnt complain -[22:11:35] so i will put down a list, and clean up -[22:11:46] you had 1 month to write objections to my rules list :] -[22:12:14] just to note, it has nothing against the named developers, i just preffer that people know who is maintaining it -[22:12:59] here -[22:13:02] anything else on this? -[22:13:31] only if you have questions -[22:13:58] questions? anyone? -[22:14:52] so, people are going to be removed from the team, i repeat: questions? -[22:15:13] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, tampakrap, tgurr, wired -[22:15:38] let's move on -[22:15:46] Review work flow for KDE minor bumps and improve collaboration with arch teams -[22:15:49] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, tampakrap, tgurr, wired -[22:15:51] scarabeus: ^^? -[22:16:09] it was written last time, wasn't it? -[22:16:56] we were going to continue the discussion today -[22:17:10] unless nothing new is going to be said -[22:17:14] jmbsvicetto: ^^? -[22:17:39] tampakrap: iirc I had only one change and it was accepted -[22:18:42] ok -[22:18:43] next -[22:18:54] KDE-4.4 status -[22:19:09] 4.4.1 is out, you said that ppl reported problems with 4.4.0 -[22:19:14] i didn't have any at least -[22:19:22] i saw few people working on bindings finaly in overlay -[22:19:25] which is great -[22:19:41] indeed -[22:19:57] can we have 4.4.1 as a stable candidate? regressions? blockers? -[22:20:02] It's working great here -[22:20:10] I don't have kdepim or kdebindings, though -[22:20:28] kdepim is great, kdebindings needs work -[22:20:40] I've got full kde-4.4.1 and it's good. I had problems migrating from 4.3.x with kmail, but it's all ok now -[22:20:50] i guess we should pay attention on this and if there are no further problems we can have it as a stable candidate -[22:21:02] schedule? -[22:21:33] 4.4.1 works great here too - and on colleague's system as well (users are best test :P) -[22:21:50] i guess start of next month? scarabeus? -[22:22:06] ok, i saw no more issues too -[22:22:18] just check regressions against 4.3 -> 4.4 migration -[22:22:19] фдыщ нуы -[22:22:23] and ok for 4.4.1 patch -[22:22:24] yep -[22:22:31] 4.4.1 works great -[22:22:41] also we use it at university -[22:22:45] as De for students -[22:23:06] scarabeus: start of next month is ok? -[22:23:25] yup -[22:23:26] meaning two weeks from now? -[22:23:36] no, stable bug -[22:23:43] sorry misread :P -[22:23:44] yes -[22:24:14] unless there aren't any other things here, we can move -[22:24:21] --> dilfridge (~quassel@gateway.maximilianeum.mhn.de) has joined #gentoo-meetings -[22:24:34] enterprise useflag for kdepim stuff (a use flag to follow the enterprise branch of the kdepim repo, only for trunk) -[22:24:54] nobody sent any mail or word about working on it -[22:24:58] so we should move it to todo -[22:25:04] until someone feels motivated enough -[22:25:04] i lack the hardware to proceed on this, plus i asked for help, noone answered -[22:25:19] Sput: anything you want to say on this? -[22:25:36] i dont know anything about it, but would like to get some information. what's different in enterprise branch? -[22:26:04] does enterprise branch contain support for Openchange/libmapi? -[22:26:27] (that's required for propler M$ exchange 2003/2007/2010 support) -[22:26:31] enterprise branch for kdepim is the actual branch were kde developers care about -[22:26:39] since kdepim trunk is broken right now -[22:26:47] it's supposed to stay stable while everything else is being ported to akonadi (and broken in the meantime) -[22:26:47] dagger: it is the branch that is more stable/solid, developers care about that one, because they are payed for that branch -[22:27:14] so I guess it's not part of "default" kdepim right? -[22:27:20] ok, we'll move this topic for next meeting, since there is no progress -[22:27:22] right -[22:27:50] let's move -[22:27:52] koffice status -[22:28:10] new koffice is released, i did a simple rename, and it currently is in hilarious status -[22:28:18] some packages don't even compile -[22:28:53] -*- scarabeus told you so -[22:29:04] i'll try to fix it, but i'll need help, anyone willing to help me is welcome -[22:29:16] i might -[22:29:25] current ebuilds are hardmasked in overlay, tarball is not released yet -[22:29:31] okie -[22:29:55] and we should be quick on this and try to have a schedule for stabilization too -[22:30:17] as it also new packages -[22:30:34] btw i can help with quick-ish stabilization on amd64 -[22:30:42] sure -[22:30:47] tampakrap: enterprise branch is based on pre-akonadi kdepim and supposedly works -[22:30:56] but a USE flag isn't gonna cut it, the packages are too different -[22:31:20] also we might have to check what they have outside of kdepim, I think they even ship a hacked kdelibs -[22:31:26] o_O -[22:31:33] kdelibs-lite! -[22:31:34] ;p -[22:31:37] (but Paul Adams told me it should work fine with 4.5) -[22:31:41] yes, we need a different branch for this -[22:32:01] there was a mail recently on kde-scm-interest where steveire detailed how branches work -[22:32:23] kdepim is in the process of moving to git (as the rest of KDE) -[22:33:05] in any case, the enterprise5 branch is going to be based on KDE 4.5, the enterprise4 branch is based on KDE 4.4 -[22:33:47] ok thanks i'm going to add those info in a mail and try to revive the issue to users -[22:34:19] moving to next one -[22:34:19] also, it seems like KDAB doubts that they manage to get kdepim fixed in time for KDE 4.5 -[22:34:34] there will be a meeting in a few weeks where they are going to decide what to do -[22:35:11] one problem is that they got their branching all wrong and lost tons of commits for kmail trunk -[22:35:25] because people were comitting to the wrong branch... -[22:35:45] okie -[22:35:50] next one -[22:35:56] change kde-meta (and @kde-*) to include all modules (plus the developer specific ones) -[22:36:12] there were some ppl in the mail i send that liked my idea -[22:36:21] so i'd really like to move on this -[22:36:24] scarabeus: ^^? -[22:36:29] with useflag you can go ahead -[22:36:29] im still in favor of this if we use a USE flag -[22:36:31] I still don't like that -[22:36:49] At least not in kde-meta without a use flag -[22:36:51] dev || sdk -[22:36:59] both are nice use flags :) -[22:37:01] jmbsvicetto: what i said above :P -[22:37:05] :P -[22:37:34] ok, i'll add sdk useflag to kde-meta -[22:37:47] and leave sets as they are -[22:37:52] not as IUSE default :P -[22:37:54] i don't care about sets anyway -[22:37:58] of course not -[22:38:00] lol -[22:38:02] +1 -[22:38:27] sdk will contain bindings, kdewebdev and kdesdk? or should i leave bindings for now? -[22:38:53] do they work? -[22:39:03] they do not mostly] -[22:39:09] do they build? -[22:39:12] there are ppl working on them, so i guess they will in the near future -[22:39:20] scarabeus: which bindings do not work? -[22:39:31] csharp afaik -[22:39:35] if they build i vote on adding them, get people's attention :) -[22:40:11] ok, i'll leave them out for now then, and add them later when they all build -[22:40:24] afaik we don't even have a meta for bindings -[22:41:19] thank you for this, next one is patches of kde-packager -[22:41:32] jmbsvicetto / ABCD(absent): any news on this? -[22:42:18] tampakrap: sorry not yet -[22:42:34] so i guess you need help on this? -[22:42:39] I'll focus on this for 4.4.1 onwards -[22:42:40] any more ppl willing to help? -[22:43:07] i have to work on something different, so i have to blob out, so enjoy the rest of the meeting, i will reply to pongs, but wont read -[22:43:07] for latest topic i am with lieo (malformed for no highlight) -[22:44:10] no worries -[22:44:15] scarabeus: is it something with leads that makes them be away all the time? -[22:44:20] :D -[22:44:27] j/k ofc, c ya later -[22:44:46] let's raise the topic in next meeting to see if there will be any progress then -[22:45:05] last topic and most important -[22:45:10] split of desktop profile -[22:45:21] leio / yngwin: your attention plz :) -[22:45:47] :) -[22:46:40] leio: as i told you before, i really like the idea of mixed profiles and i am willing to work on it -[22:47:08] I like that idea as well -[22:47:11] but i can't have an eta as i don't have a stable schedule atm and i don't even know how much time it wants to be finished -[22:47:16] me too, but i expect that will take a while to implement -[22:47:23] --> pesa (~Pesa@host124-126-dynamic.52-82-r.retail.telecomitalia.it) has joined #gentoo-meetings -[22:47:27] so i'd really like to proceed on commiting the patches i have prepared -[22:47:50] so any objections? something wrong with them before i commit? -[22:48:48] no objections -[22:49:38] i haven't tested them (and i don't use the desktop profile :p) but i really like the idea, +1 -[22:51:06] <-- pesa (~Pesa@host124-126-dynamic.52-82-r.retail.telecomitalia.it) has left #gentoo-meetings ("Konversation terminated!") -[22:51:20] leio seems away, so if you want you anything more you can pm me -[22:51:38] i'll commit it this sunday fyi, i'll be out of town the next two days -[22:52:10] well, you know what I think -[22:52:26] (was here at start, but had a phone call afterwards) -[22:53:36] cool, i'd take it as a :thumbup from the gnome team and proceed -[22:53:42] we have had the single desktop profile situation for, what? four years? So even waiting 3 months more to get the better method implemented would sound fine in my book, but as I can't work on that myself, I can't well argue against more subprofiles meanwhile -[22:55:00] point taken -[22:55:32] i guess the meeting is over, I'd also like to inform you i have updated docs, please check for any issues diff --git a/meeting-logs/kde-project-meeting-log-20100604.txt b/meeting-logs/kde-project-meeting-log-20100604.txt deleted file mode 100644 index 3f12f31..0000000 --- a/meeting-logs/kde-project-meeting-log-20100604.txt +++ /dev/null @@ -1,282 +0,0 @@ -[21:59:58] * scarabeus has changed topic for #gentoo-meetings to: "Gentoo meetings | KDE Team meeting | topics: http://paste.pocoo.org/show/222007/" -[22:00:43] -*- ABCD is here -[22:00:45] lets get slowly started -[22:00:51] so step 0: roll call -[22:00:51] -*- dilfridge is here -[22:00:52] -*- wired suprizingly here -[22:00:52] who is around -[22:01:02] --> krytzz (~quassel@quassel/user/krytzz) has joined #gentoo-meetings -[22:01:17] thats all? -[22:01:22] lol -[22:01:34] --> deathwing00 (~deathwing@gentoo/developer/Deathwing00) has joined #gentoo-meetings -[22:01:37] -*- ABCD is here (again, because I said it before roll call started) -[22:01:38] w00t? -[22:01:50] wot? -[22:01:52] ok, before anyone brings up any topic -[22:01:56] let me say just one thing -[22:02:39] my commit access will be disabled starting this month June 2010 and will be re-enabled July 2011, as I will be doing an MBA that will take most of my time away, besides I was promoted to team leader in Flumotion and that adds me even more workload -[22:02:48] said that, good luck guys :) -[22:02:58] deathwing00: cheers, and happy birthday :] -[22:03:01] you really think you won't have time for 1 commit? hehe -[22:03:15] good luck to you too :) -[22:03:35] --> mschiff (~mschiff@d000042.adsl.hansenet.de) has joined #gentoo-meetings -[22:03:37] :) -[22:03:38] !herd kde -[22:03:38] thanks -[22:03:38] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, tampakrap, tgurr, wired -[22:03:43] wake up rest of you -[22:03:47] there is more than 10 people -[22:04:16] scarabeus: laters then :) -[22:04:24] I'll still be around in jabber ;) -[22:04:25] hmm... time for small talk... -[22:04:27] <-- deathwing00 (~deathwing@gentoo/developer/Deathwing00) has quit (Quit: Leaving.) -[22:04:47] ok, lets get started, and i will kick their asses later -[22:05:02] so 4.4 and its stabilisation -[22:05:08] rrrrrrringdingding! -[22:05:12] the bug is not moving anyhow promisingly -[22:05:36] many things are there since 4.3.x times -[22:06:10] yes the main quesiton is -[22:06:16] how about we put 4.4.4 to main tree -[22:06:21] and ask for stabilisation in 1 week -[22:06:25] no matter what is left -[22:06:43] sounds fine to me - 4.4.4 should just be bugfixes on 4.4.3, right? :D -[22:06:46] but basic thing i would like to say is that i would like to see designated team that would handle the stables -[22:06:49] probably not better nor worse than 4.4.3 -[22:06:52] they will run the stable -[22:07:05] and will be responsible for proactively stabling and pestering us all for fixing stable bugs -[22:07:12] -*- dilfridge hears some coconuts in the background -[22:07:48] well who else besides me runs 4.4.[34] here still? -[22:08:15] i have 4.4.3 -[22:08:16] sorry, got distracted -[22:08:16] :] -[22:08:18] -*- ABCD doesn't because his hard drive broke -[22:08:28] jmbsvicetto: by accident you dont run stable huh? ;} -[22:09:40] I runn 4.4.4 -[22:09:46] also good -[22:09:48] So any other ideas how to handle this situation? -[22:09:51] run* -[22:10:09] well the only other alternative would be to stable 4.4.3 -[22:10:10] scarabeus: about the 1 week we must be ready for arch teams to tell us they'll wait the usual month -[22:10:31] nah, they wont get to that bug before the month will come anyway -[22:10:37] in any case, I think the most important issue is the deps. Are we sure all 4.4.4 deps are marked stable? -[22:10:50] expect amd64 and x86 which mostly will do what we ask them -[22:10:52] did the deps change from 4.4.3? -[22:11:17] dependecies were not changed -[22:11:22] ABCD: 4.4.3 isn't stable, right? iirc, the latest stable is 4.3.5 -[22:11:29] yes -[22:11:34] scarabeus: and no, I don't run stable -[22:11:55] also, what about kdepim? Will that only affect 4.5? -[22:11:58] jmbsvicetto: i think our problem is that we all rock on ~ or even further -[22:12:01] -*- dilfridge has a fully stable x86 chroot rotting somewhere -[22:12:10] jmbsvicetto: kdepim is affected only 4.5 and it is next topic :] -[22:12:20] jmbsvicetto: it isn't, but if its deps were stable, then there shouldn't be much of an issue -[22:12:21] dilfridge: sadly you are not dev yet whom can fill those requests :] -[22:12:30] scarabeus: that's to be expected -[22:12:35] (us running ~) -[22:12:41] yes -[22:12:49] but then we would expect archies to fill stablerequests -[22:12:56] we have tons of various packages just in ~ -[22:13:00] but anyway ~ is better than ~+pmasked -[22:13:03] because nobody ever bothered to fill the bugs -[22:13:15] it's up to us to ask for packages to be marked stable, but it's up to arch teams to take care of it -[22:13:31] (and to wait for 30days...) -[22:13:36] yes, and who else would have better motivation to ask for stables than people running it -[22:13:40] I'm planning to add a request for amarok soon -[22:13:56] but I need to check the status of the deps -[22:14:16] I'll probably go for 2.3.0.90 or 2.3.1 directly and then drop all the older versions -[22:14:50] sounds sane :] -[22:14:56] I'm also likely to merge amarok and amarok-utils as I don't see any interest on amarok-utils -[22:15:10] so i guess my plan with arch team wont work since we dont have anyone interested in it :P -[22:15:21] so only question left is which version 4.4.3 or 4.4.4 -[22:15:31] devs plz pick :] -[22:15:35] jmbsvicetto: sounds also sane :] -[22:15:39] well, most of us already have the blessing to do the work for amd64 -[22:16:05] I'd say 4.4.4 if we can convince the archies to do it in 7 days instead of 30 -[22:16:06] at this point, we can probably target 4.4.4 -[22:16:16] ok -[22:16:28] 3 out of 5 attending devs -[22:16:32] added to summary -[22:16:37] next topic then -[22:16:40] kdepim 4.5 -[22:16:45] ugh -[22:16:49] ABCD: past history has showed that it takes a bit more than 1 or 2 weeks since we plan to ask for a package to get marked stable and to the request get to the arch teams ;) -[22:17:12] i also vote for 4.4.4 -[22:17:19] btw we can stable amd64 ourselves -[22:17:26] --> raxas (~raxas@charybdis-1-pt.tunnel.tserv6.fra1.ipv6.he.net) has joined #gentoo-meetings -[22:17:28] besides, has anyone hit any regression from 4.4.3 to 4.4.4? -[22:17:28] yes yes -[22:17:33] no -[22:17:47] one last thing before we move on to kdepim -[22:17:48] I haven't, but I didn't check the kdm user thing yet -[22:17:56] No regressions from 4.4.3->4.4.4 here -[22:18:14] we will probably be drowned in akonadi problems when 4.4.x gets stable -[22:18:25] dilfridge: aware of that :/ -[22:18:29] hmm, I did restart kdm on my desktop and it's working, so I don't think that's an issue afterall -[22:18:41] (i was always too lazy to file a bug, but on my 3 machines it never started working properly) -[22:18:57] -*- scarabeus does not even have kdepim installed -[22:19:00] too big pile of... -[22:19:06] anyway -[22:19:10] we have 3 options at our hands -[22:19:12] I like(d) it... -[22:19:15] dilfridge: if you mean about kdepim, I don't have it installed locally :P -[22:19:22] ship kdepim from trunk with 4.5 releases, our tarballs -[22:19:30] make 4.5 work with 4.4 kdepim -[22:19:36] or finaly package enterprise branch -[22:19:48] scarabeus: Perhaps we should start by making 2 questions: -[22:19:59] 1. Which devs care or want to "mess" with kdepim -[22:20:06] second is probably the easiest, as all distros wil do that right? -[22:20:32] krytzz: second is indeed easiest -[22:20:39] 2. and depending on that we can just start a vote on the forums/mls/* explaining the issue to the users and getting a "vote" on how to proceed -[22:20:42] jmbsvicetto: alexxy was interested but sadly is not here -[22:20:55] i am definitely not interested in kdepim -[22:20:59] if that part of kde disappeared -[22:21:01] i would be happy man -[22:21:10] among with semantic-desktop team -[22:21:11] :D -[22:21:21] I don't plan to touch kdepim too -[22:21:23] -*- dilfridge would probably skip that release then as he need kdepim -[22:21:42] dilfridge: pst, we switched to claws and thunderbird, they works -[22:21:49] hehe -[22:22:01] I've always used FF and TB, so no change for me ;) -[22:22:11] ok so seems noone is interested in this topic -[22:22:18] so lets postrpone it, i will sent mail to alias -[22:22:23] and i will pray that someone reply -[22:22:24] scarabeus: what about my proposal? -[22:22:27] what about reavertm, he did some work with pim :p -[22:22:37] jmbsvicetto: the forums are good idea, but first we need to pass step 1 -[22:22:43] scarabeus: we could set a plan like the following: -[22:23:09] 1. give developers one week to express what they feel about kdepim and to see if anyone volunteers to work on it -[22:23:43] 2. if that fails or we can't find anyone willing to do it, make a public announcement about the issue, explain it and give a few options to users: -[22:24:11] 2.1 have interested parties show up and work in the overlay to get it done - (what can be given as option to the community) -[22:24:18] ok -[22:24:25] 2.2 have users vote for us to just ignore kdepim until it gets working -[22:24:26] will 4.5 be released one month afterwards? in that case you could postpone the whole 4.5 release for 1 month? -[22:24:26] from what I heard, kdepim may show back up in 4.5.1 or 4.5.2 -[22:24:28] that sounds like nice sumup -[22:24:37] 2.3 give the above 3 options for someone to work on -[22:25:23] ABCD: with shitload of bugs -[22:25:40] that's beside the point :D -[22:25:41] jmbsvicetto: added your approach to summary, since it sounds like only sane :] -[22:25:45] that's what 4.5.3456 will be for -[22:26:02] koffice-2.2 -[22:26:09] dilfridge: i saw you working on it :] -[22:26:18] yes and it works afaik -[22:26:21] That's another thing I don't plan to work on -[22:26:24] so wanna be designated maintainer? -[22:26:38] puh... I'm not actively using it so bad choice... -[22:26:53] (whenever I tried ooo did the job better) -[22:27:13] but I can look after it a bit yes -[22:27:33] scarabeus: we could perhaps use this chance to ask for volunteers to work on koffice and kdepim -[22:27:50] (not that I expect a horde to show up) -[22:28:19] well we need 2.2.0 in main tree stabilised asap -[22:28:26] because 2.1 is seriously useless -[22:28:29] I'd rather volunteer for some kdepim stuff than koffice... -[22:28:49] :DDD -[22:28:55] <-- brk (~brk@r9dq22.net.upc.cz) has quit (Ping timeout: 260 seconds) -[22:28:57] dilfridge: s/and/and or/ -[22:29:00] lets try same approach as for kdepim then -[22:29:27] NEEEXT :D -[22:29:44] so dagger sent me mail -[22:30:01] if we would accept pulse patches -[22:30:01] that makes it work in kmix -[22:30:02] for now on we have policy that we dont backport patches -[22:30:41] so lets vote about wheter to accept patches or be strictly what upstream sends -[22:30:57] scarabeus: since when? we always tried to follow upstream as closely as possible, but if someone is willing to apply a back-port and to keep it working, why not? -[22:31:03] -*- alexxy here =) -[22:31:07] just write upstream/distro-patches based on what you want (only devs) -[22:31:15] jmbsvicetto: acutaly we declined quite few backports -[22:31:39] jmbsvicetto: for konsole in example -[22:31:42] as long as we don't want to do it and there's no one in the team willing to do it, it's ok by me -[22:31:57] scarabeus: iirc, ssuominem applied that patch again -[22:32:27] I don't follow commits closely, but by reading the bugzilla mail, I think a few have been applied -[22:33:12] so lets keep status "if you keep it backported and polished you can have it..."? -[22:33:17] backports++ from me if they fix stuff ;) -[22:33:32] scarabeus: together with the old "you break it, you fix it" ;) -[22:33:43] jmbsvicetto thats a must :P -[22:34:05] ok added to summary -[22:34:13] now the topic that is quite important -[22:34:23] oh and about pulseaudio, I no longer care!! /me is using phonon-vlc :) -[22:34:37] lol -[22:34:42] so inactive people in team -[22:34:45] what the f**k is everyone doing -[22:34:51] there is 17 people in the team -[22:34:54] -*- jmbsvicetto goes hidding in the back -[22:34:55] ... -[22:34:56] :D -[22:35:14] scarabeus: I guess the other 16 guys are very active :P -[22:35:14] on this meeting we have star attendance of 5 developers -[22:35:24] very very active -[22:35:24] well -[22:35:40] he he =) -[22:35:50] scarabeus: you're to blame for this instance -[22:35:58] you chose FRIDAY EVENING -[22:36:05] failday for meeting :p -[22:36:09] i dont mind attendance for meeting -[22:36:11] scarabeus: talking for myself, I took a lot of work when things were stalled, then you guys all started doing so much, I got used not needing to do too much ;) -[22:36:16] its beerday -[22:36:16] =) -[22:36:24] but there is almost no activity on tree or ovelray by team members in kde area -[22:36:29] right... only people without friends are online now -[22:36:38] not counting few active ones -[22:36:45] krytzz: thanks :P -[22:36:48] so since joining team is really simple -[22:36:50] \o/ -[22:37:10] i would like to ask all those who are not really into working at least bit on kde remove themselves from herd -[22:37:17] they are mostly active in other areas of gentoo -[22:37:31] scarabeus: Now you know how fun it is to have the pointy hat ;) -[22:37:36] and it would at least show me list of people i can count in -[22:37:56] scarabeus: thats not going to work, most of them aren't even here :P -[22:38:11] and i will forceremove everyone who dont have at least 1 commint in last 2 months -[22:38:17] wired: it will be on summary -[22:38:36] they can join in back and be active -[22:38:51] or just commit here and there with our permission as other nonteam devs do now -[22:39:14] bonsaikitten: that counts you too ;] -[22:39:35] scarabeus: ok, let me be clear about my commitment: I plan to do amarok as long as no one takes it out of me, I'm interested in phonon-vlc for the moment, I also have an interest on kdenetwork. I try to look at bugs and I get interested on stuff sent to packagers. I do however have a few other areas where there aren't active people on, so they sometimes take priority -[22:39:40] <-- ABCD (~abcd@gentoo/developer/abcd) has quit (Ping timeout: 265 seconds) -[22:40:03] jmbsvicetto: you do commits in packages that have herd kde -[22:40:19] jmbsvicetto: there are people that didnt do any commit in those 2 named months back any of that -[22:40:21] scarabeus: yeah, that's fine with me -[22:40:23] yeah, but I know I don't do many commits -[22:40:26] (i did some research) -[22:40:33] -*- alexxy plays with beta/rc/snaphsots stuff -[22:40:34] jmbsvicetto: but you do something :] -[22:40:34] I'm mostly honorific member ;) -[22:40:51] the last thing i did was fix koffice 2.1.81 -[22:40:51] ;p -[22:40:55] there is thin line between something and nothing -[22:41:27] -*- jmbsvicetto gives a swift kick in bonsaikitten's honorific *slacker* member :P -[22:42:04] jmbsvicetto: you sound fat! -[22:42:08] you know I was looking at the slacker definition the other day and it said also known as bonsaikitten or patrick -[22:42:11] ;p -[22:42:12] bonsaikitten: :P -[22:42:22] wired: hehe -[22:42:31] =) -[22:42:50] ?D -[22:42:52] ok -[22:42:58] =P -[22:42:59] wired: He has a bit to learn to catch some champs ;) -[22:43:00] i guess that is all of mine topics -[22:43:03] omg -[22:43:04] so -[22:43:08] you have something to discuss -[22:43:19] http://paste.pocoo.org/show/222014/ -[22:43:19] a 40 minutes meeting? O_O -[22:43:23] also here is current summary -[22:43:25] my 50 cents about kdepim -[22:43:29] i planned 10 minutes for each -[22:43:34] we were faster -[22:43:52] i plan to package tarballs for 4.5.0 -[22:43:54] =) -[22:44:14] nice -[22:44:18] alexxy: that is mostly too late :P now you will have to work with others over mail : -[22:44:19] ] -[22:44:29] reavertm: what are you planning to do with the cmake-utils eclass and was there any reason for the revert? -[22:45:52] alexxy: also remember that people will want to kill you if you blow up their mail client :D -[22:46:03] 1 thingie, anyone did log? -[22:46:06] for the log... -[22:46:07] :] -[22:46:12] i have just summary -[22:46:14] sure -[22:46:19] i have log -[22:46:21] =) -[22:46:45] so do i \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-log-20100902.txt b/meeting-logs/kde-project-meeting-log-20100902.txt deleted file mode 100644 index 4da84bc..0000000 --- a/meeting-logs/kde-project-meeting-log-20100902.txt +++ /dev/null @@ -1,234 +0,0 @@ -[21:14:55] roll call -[21:15:02] 1 -[21:15:05] 2 -[21:15:07] 3 -[21:15:18] we lost abcd -[21:15:28] 4 -[21:15:34] and i am number five -[21:15:55] i would like to have a small talk about amarok in the -end if jmbsvicetto manages to find us -[21:15:59] either way: -[21:16:02] not even a quorum (for most definitions of "quorum") -[21:16:08] -http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/maintainers/meetings/meeting-2010-09-02;h=e5a2764f178127e3f04e3311c12563b68a1b8dbe;hb=HEAD -[21:16:15] here's the agenda -[21:16:23] 1) KDE-4.5 status and plans to put it in Portage -[21:16:29] reavertm: you can start -[21:16:39] ok, here it is: -[21:17:04] there are following issues I'd consider a blockers -[21:17:26] (unless we say - screw you users - upstream) -[21:17:53] https://bugs.kde.org/show_bug.cgi?id=230247 -[21:18:47] hmm here everything works fine _since_ the upgrade to -4.5.0 -[21:19:02] result - you need to start any akonadi-client app twice -in order to use it (first start will make akonadi start bug won't detect that -it started) -[21:19:18] but I'm not logging in/out very often -[21:19:38] one blocker - kwin FBO bug has been fixed (commit -reverted as I requested) -[21:19:56] remaining ugly bugs: multiple plasma glitches in system -tray -[21:20:20] plasma glitches were highly reduced in 4.5.1 -[21:20:31] not seen for a while -[21:20:37] https://bugs.kde.org/show_bug.cgi?id=246931 -[21:20:45] if the akonadi bug is the only blocker i'd say let's -put it in tree, and let the people know about it -[21:20:46] no, they are still there -[21:21:02] tampakrap: and spam out bugzilla for no reason? -[21:21:20] ah that yes that is still there... I got used to that -bug... -[21:21:27] https://bugs.kde.org/show_bug.cgi?id=247144 - another -plasma glitch (folderview) -[21:21:39] and most important - memory leaks in plasma-desktop -[21:21:49] (minor leaks, but they are there) -[21:22:19] dolphin tooltips issues as well as nepomuk related -crashes seen to be gone at least -[21:22:49] i'd suggest let's put it in tree, but announce those -bugs and make it clear that it's not going to be stabilized -[21:22:50] oh, and one bug present in 4.4 alteady - -https://bugs.kde.org/show_bug.cgi?id=247204 -[21:23:07] i'm getting enough spam on IRC already, and i think it -is usuable enough -[21:23:21] that's my opiniion, but it is your call mostly -[21:23:24] with that state I don't think *any* 4.5 patch release is -going to be stabilized, I won't allow it -[21:23:31] there are regressions in every major release but that's why -we have testing. 4.5.1 seems good enough for tree -[21:23:50] seconded (I personally can work with it fine) -[21:23:53] unless we clearly communicate - "we know it's broken - -we reported bugs and they keep being ignored" -[21:24:17] reavertm: give me a list of the bugs, i can put them on -the meeting summary -[21:24:18] 4.4 took a lot of time to be stabilized because of -regressions too, that's how kde works, apparently -[21:24:26] and put the summary on my blog on planet gentoo and kde -[21:24:32] I won't wrange any 4.5 bugs in our bugzilla, I want to -make it clear :P -[21:25:09] spatz: plasma devs utilized 'Broken Development Model" -that's why -[21:25:31] I'm not pointing fingers, just stating facts :) -[21:26:05] ok, we made our points, reavertm: your call -[21:26:13] tampakrap: fine, but you'll blog about it :) (with bug -links there) -[21:26:14] since you fixed a couple of upstream bugs -[21:26:23] aah, one more blocker -[21:26:32] but on our side - handbooks handling -[21:26:38] yes that is true -[21:26:51] something is seriously broken there -[21:27:01] bug #? -[21:27:28] bug 296345 -[21:27:29] since 4.5 - docbooks are no longer bundled - so for -every +handbook we need to pull docbook stuff like for kdelibs -[21:27:30] dilfridge: https://bugs.gentoo.org/296345 "kde 4.4.4: -Compilation error when creating help search index - bad xslt pattern"; Gentoo -Linux, KDE; NEW; ashl1future@gmail.com:kde@g.o -[21:27:49] ah different problem -[21:27:52] err, i meant different handbook issue -[21:28:40] if there is no bug #, let's open one, fix that first -and then put 4.5.1 to tree -[21:29:12] I can fix it anyway (my handbook isse) - for instance by -introducing KDE_HANDBOOK eclass variable instead of +handbook in IUSE (that -could hold additional handbook dirs as well) -[21:29:41] ok -[21:29:49] anything else on this? -[21:30:10] I think this is it wrt kde 4.5 -[21:30:29] i have one more thing to say about it -[21:30:36] not so relevant -[21:31:11] ? -[21:31:12] http://bugs.gentoo.org/show_bug.cgi?id=335123 -[21:31:43] hmm, works for me... -[21:31:45] these patches don't apply to kdepimlibs 4.5.0 and i -don't know if by applying them to 4.4.5 only will break 4.5 as well -[21:31:59] i can reproduce here and the patches worked on my 4.4.5 -laptop -[21:32:23] so, any ideas? -[21:32:36] does it affect only kde 4.5 + kdepim 4.4? -[21:33:00] or it's some general bug? -[21:33:01] the patches are meant for 4.4.5 only, haven't tested to -4.5 -[21:33:32] but i don't want to introduce a new bug by applying the -patches to kmail 4.4.5 and not to kdepimlibs 4.5.x -[21:34:08] I'd prefer them to appear in svn.. -[21:34:13] never had this problem here -[21:34:51] ah they are not taken from svn -[21:34:54] nice point -[21:35:04] ok thanks -[21:35:10] next issue i guess -[21:35:20] 2) KOffice 2.2 status -[21:35:35] -*- reavertm shuts up -[21:35:46] i was away because of my thesis and vacations for too -long, anyone knows the blockers of keeping this away from tree? -[21:35:48] needs bump to 2.2.2 (I had no time yet but that should -not be difficult) -[21:36:10] there is a "workaround" -[21:36:13] -*- reavertm disagrees, he saw multiple cmake changes and file/dir -additions/removals -[21:36:24] ok have not checked yet -[21:36:58] considering kchart -[21:37:10] I see when do svn update in koffice occassionally, it -needs someone to closely follow up - and in our case when it's been abandoned -for a while - full review from scratch likely -[21:37:27] The libraries do not link if kchart is not built at the -same time, so what I did was -[21:37:48] do make a dummy ebuild for kchart for the meantime. -[21:37:51] KMCOMPILECONLY can be used -[21:38:06] well it is done in koffice-libs -[21:38:17] but I wanted to keep something named kchart in portage -[21:38:26] so later upgrade remains painless -[21:38:42] is it standalone app? -[21:38:55] so, now koffice-libs also installs kchart, and kchart -does, well, nothing -[21:39:13] no I think only library -[21:39:37] i see -[21:39:43] apart from that nobody gave me negative feedback on -2.2.1 yet -[21:39:50] i'd appreciate if there were more comments on the bug -[21:39:56] http://bugs.gentoo.org/show_bug.cgi?id=322147 -[21:39:59] then should be in koffice-libs imho - I'd like to avoid -creating excessive libraries like used to be in kdepim -[21:40:00] --> pesa -(~Pesa@host169-125-dynamic.52-82-r.retail.telecomitalia.it) has joined -#gentoo-meetings -[21:40:02] and i could help you with it -[21:40:20] i agree with that -[21:40:48] fine with me... but the plan is that kchart can be -built separately again with 2.3 -[21:41:33] is it already done in the live ebuilds? -[21:41:47] did not check yet -[21:41:51] ok -[21:41:51] maybe they'll just add some host for that kpart, then -kchart ebuilds will be justified, (but libkchart should still be in -koffice-libs imho) -[21:42:28] it can be embedded in any koffice app after all -[21:43:07] ok, i'm done with it, dilfridge any further comments? -[21:43:15] I'm kind-of-away from tomorrow for a week, so if -anything should be done quickly I'm out -[21:43:30] but I guess its not that urgent -[21:43:34] -*- reavertm needs to remember how it was decided - koffice-libs -contains full functionality and kword for instance only word processor -application (but kpart is provided by koffice-libs) - or installing kword -makes kpart available -[21:43:35] indeed -[21:44:08] if the kpart is used by other ebuilds too it should be -in koffice-libs -[21:44:15] else the split makes no sense -[21:44:35] we can find that out with the dependencies / linking -[21:44:47] since now all apps are for sure compiled after kchart -[21:44:52] no, kparts are runtime-only things mostly -[21:45:03] ok true -[21:45:20] (well, buildtime+runtime, but can be missing at runtime) -[21:45:45] i'd say we could give 2.2.1 a try -[21:45:59] -*- dilfridge keeps fingers crossed -[21:46:11] ok -[21:46:24] next? -[21:46:27] fine, but I'd suggest full review of them (for instance -to check whether all koffice subdirs are packaged in ebuilds) -[21:46:54] reavertm: teach me how to do that, please! :) (in two -weeks) -[21:47:35] ok next -[21:47:49] for next issue i would like alexxy but he seems not to -be here -[21:47:57] simple - take a look at koffice/ and check subdirs one -by one against koffice ebuilds (KMEXTRA, KMCOMPILEONLY, KMEXTACTONLY) -[21:48:25] ok -[21:48:48] 3) KDEPIM beta packages are released -[21:48:51] i'll skip it -[21:49:00] and add a gentoo-desktop thread instead -[21:49:05] we just want whole koffice covered (or some parts -*intentionally* skipped) -[21:49:14] ok -[21:49:27] skip it please -[21:49:36] I don't want kdepim betas in overlay :P -[21:49:47] (there are live ebuilds already) -[21:50:11] sebas stated in his blog that upgrade and downgrade -would be easy since configs don't affect each other -[21:50:50] either way, we'll discuss it in gentoo-desktop -[21:50:55] 4) open floor -[21:51:20] about digikam -[21:51:41] the patches are cleaned up a lot, but it's not -completely finished yet -[21:52:02] <-- spatz (~spatz@gentoo/developer/spatz) has quit (Ping timeout: -276 seconds) -[21:52:23] reavertm: if you want to have a look at it go ahead, -but dont send anything upstream yet. -[21:52:46] at least 1.4.0 should now build fine -[21:53:04] I'll talk with the sci guys about clapack. -[21:53:11] I'll wait -[21:53:21] i'm also going to unmask knerworkmanager very soon, -please test -[21:53:34] i'm a bit worried about the versioning though -[21:54:47] ah, as of open floor - I encourage people working with -live and tagged ebuilds to use kde-misc/kde-overlay-servicemenus -[21:55:07] what does it do? -[21:56:00] I've added simple Compare/Merge service menu - in -dolphin select two files one by one to have them open in kompare (where you -can interactively sync them) -[21:56:15] to avoid manual copy paste -[21:56:17] w00t -[21:56:19] nice -[21:56:43] last issue, i'm going to remove a few inactive people -from the team -[21:57:14] and if there is not anything else, i guess i should -close the meeting -[21:57:33] thanks -[21:58:08] meeting is over diff --git a/meeting-logs/kde-project-meeting-log-20110210.txt b/meeting-logs/kde-project-meeting-log-20110210.txt deleted file mode 100644 index 8adcf02..0000000 --- a/meeting-logs/kde-project-meeting-log-20110210.txt +++ /dev/null @@ -1,566 +0,0 @@ -[21:01:20] lets roll -[21:01:27] rollcall lads -[21:01:29] !herd kde -[21:01:29] (kde) abcd, alexxy, dilfridge, jmbsvicetto, patrick, reavertm, scarabeus, spatz, tampakrap -[21:01:32] wait wait -[21:01:43] ohhh -[21:01:47] -*- jmbsvicetto hides -[21:01:54] i completely forget about meeting -[21:02:30] tampakrap: sup -[21:03:14] need to ping more people -[21:03:22] here -[21:03:24] so lets wait on tampy -[21:03:53] bonsaikitten: you are around? -[21:04:01] aye aye captain -[21:04:11] he is square =) -[21:04:26] (not for much longer i hope) -[21:04:41] anyway, let's go -[21:05:39] --> krytzz (~quassel@quassel/user/krytzz) has joined #gentoo-meetings -[21:06:36] so there are two guys whom can be lead -[21:06:38] --> papillon81 (~papillon8@g230050057.adsl.alicedsl.de) has joined #gentoo-meetings -[21:06:41] bonsaikitten and tampakrap -[21:06:45] greets -[21:06:50] so guys do you accept nomination? -[21:07:14] yes, and i nominate you and jmbsvicetto as well -[21:07:21] no!! -[21:07:33] -*- papillon81 nominates scarabeus, too, but knows he can't vote -[21:07:46] -*- scarabeus humbly does not accept the nomination, cause he does not use this mess anymore :) -[21:07:52] LOL -[21:07:55] -*- reavertm nominates scarabeus -[21:08:00] GUYS! -[21:08:20] -*- jmbsvicetto nominates scarabeus as well - just to be consistent -[21:08:22] ok i nominate reavertm -[21:08:23] lol -[21:08:25] --> dilfridge (~quassel@gentoo/developer/dilfridge) has joined #gentoo-meetings -[21:08:36] i also nominate dilfridge -[21:08:45] because i like his hair style -[21:08:48] scarabeus: I guess we won't have a vote without a second candidate, so yes -[21:09:26] grr sorry having slight dsl problems -[21:09:27] -*- alexxy also nominates scarabeus and tampakrap =D -[21:09:30] grr sorry having slight dsl problems -[21:09:37] err -[21:09:37] ok, so we have nominations for: tampakrap, bonsaikitten, scarabeus, jmbsvicetto, reavertm and dilfridge. Anyone else? -[21:09:47] ah -[21:10:01] here -[21:10:09] tampakrap and bonsaikitten accepted. I refused. Others? -[21:10:30] i refuse -[21:10:32] -*- reavertm nominates alexxy for good behaviour and tree bumps -[21:10:44] no!!!!!! -[21:11:02] so, reavertm and dilfridge, do you accept your nominations? -[21:11:10] alexxy: I'm counting you as refusing -[21:11:19] yep =) -[21:11:23] jmbsvicetto: you write summary>? -[21:11:28] no, i will -[21:11:29] scarabeus: NO!! :P -[21:11:34] ook i am -[21:11:40] scarabeus: just helping to summarize points -[21:11:48] I'm not gonna refuse, but I'm not the best choice... I may drop offline for a while at any point because of real-life workload -[21:11:50] I WILL WRITE THE SUMMARY -[21:11:53] well, I can accept but be advised I'm not active any more as I used to -[21:12:04] scarabeus: who's going to protect the children now that you won't be lead? -[21:12:19] so it seem we have 4 candidates: tampakrap, bonsaikitten, reavertm and dilfridge -[21:12:30] seems* -[21:12:46] so, how do we vote? -[21:12:53] Should we open an "election window" so everyone in the team can cast their vote? -[21:13:02] nopes -[21:13:03] here -[21:13:03] huh? -[21:13:04] now -[21:13:06] attending -[21:13:06] one way would be to vote to the kde alias or gentoo-desktop ml -[21:13:11] jmbsvicetto: dilfridge said no -[21:13:28] he said he is NOT going to refuse -[21:13:29] scarabeus: I read it as "I'm not going to refuse" -[21:13:39] jmbsvicetto: correct -[21:13:48] ah -[21:13:51] so 4 candidates -[21:13:52] ok, how do we vote? only one choice? -[21:14:10] poll? -[21:14:10] yeah one choice -[21:14:16] one choice -[21:14:31] Do you want to vote by email / irc / votify? Do we want a public or private election? -[21:14:39] oh dear -[21:14:43] just asking -[21:14:55] I can vote now, by irc -[21:14:57] I don't have any preference -[21:15:08] now over irc one person -[21:15:08] Do we have enough KDE team members around to do it? -[21:15:11] kthx -[21:15:13] yes we do -[21:15:14] no preference here either -[21:15:17] good -[21:15:19] by irc =) -[21:15:21] i watch this stuff -[21:15:29] !herd kde -[21:15:30] (kde) abcd, alexxy, dilfridge, jmbsvicetto, patrick, reavertm, scarabeus, spatz, tampakrap -[21:15:50] please acknowledge your presence :) -[21:15:51] to get elected someone needs to get 5 votes - at least on the first vote count. Agreed? -[21:15:52] abcd and spatz seem to be missing -[21:15:54] abcd and spatz missing or not active -[21:16:15] abcd present but inactive -[21:16:32] 5 out of 9 - to get > 50% -[21:16:38] ok -[21:16:56] so, shall we vote? -[21:17:28] -*- reavertm present and active -[21:17:34] present -[21:17:38] present -[21:17:42] present -[21:17:44] present -[21:17:47] present -[21:18:02] that's at least 7 as far as I can tell -[21:18:19] present -[21:18:37] means we can do irc vote now -[21:18:47] public vote acceptable? I am indifferent -[21:18:55] just go public -[21:18:58] why to hide -[21:19:03] (come on as retiring one ic -[21:19:04] yes, any opposition? -[21:19:09] an just decide that) -[21:19:11] not from me -[21:19:14] no opposition here -[21:19:17] public -[21:19:24] go ahead public -[21:19:30] so, votes? -[21:19:41] vote: tampakrap -[21:19:42] -*- dilfridge votes tampakrap -[21:19:54] -*- bonsaikitten votes for tampakrap -[21:20:00] -*- tampakrap votes reavertm -[21:20:05] -*- alexxy votes for tampakrap -[21:20:06] -*- reavertm votes tampakrap -[21:20:31] tampakrap: -[21:20:39] -*- jmbsvicetto votes tampakrap -[21:20:43] that's 6 for tampakrap already, which is a simple majority -[21:20:46] I guess that counts as a majority -[21:20:56] tampakrap: Congratulations ;) -[21:20:58] yep -[21:21:03] thank you ladies -[21:21:03] congrats -[21:21:04] I like efficiency :) -[21:21:10] i'm going to dissapoint you for sure -[21:21:24] that's why we voted you ;) -[21:22:01] =D -[21:22:06] which means 9% of the agenda is DONE! Yeah! -[21:22:26] ok i'm going to chair the rest of the meeting -[21:22:35] 1) status regarding hal -[21:22:55] it is dead, not needed in 4.6, i'm going to convert samuli's forum post to guidexml -[21:22:59] anything else to say here? -[21:23:01] anyone still running hal here? -[21:23:01] well, when 4.5 is ouot, we won't need it anymore -[21:23:18] (and 4.4) -[21:23:38] ok -[21:23:41] anything else about it? -[21:23:49] I'd say wait for 4.6.1 and then remove 4.5 from tree, then HAL can die -[21:24:02] discussion about the future of 4.6 is later in the list -[21:24:10] ah, 4.4... -[21:24:14] ook we need to keep it until 5 -[21:24:17] 4.6 is stable -[21:24:22] typo with the 5 -[21:24:36] http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/maintainers/meetings/meeting-2011-02-10;h=3d4869e4043c080750c68b2c7da66cfaf10f3c0d;hb=298fad1df1839ec400a346a9c60036a96e0b440e -[21:24:40] topics here btw -[21:24:51] ok we're done with hal, next -[21:24:56] 5 2) should we try to form a "stable kde devs" team? meaning just call for volunteers on the dev ml? -[21:25:01] 2) should we try to form a "stable kde devs" team? meaning just call for volunteers on the dev ml? -[21:25:07] that was my idea -[21:25:17] please elaborate -[21:25:18] basically many of us are running 9999 -[21:25:46] and right now the distance between 9999 and stable is so huge that it can be difficult to test stable bugfixes -[21:25:52] my opinion is we don't need it, we usually stabilize fast, with the great exception of 4.5 -[21:26:03] by '9999' you mean 4.x.9999 as well? -[21:26:07] the problem may go away on its own with 4.6 -[21:26:08] we dont sta le -[21:26:12] misc apps are slow -[21:26:15] seriously -[21:26:24] some of them were stabilised by me with the last cleanup -[21:26:29] who cares? i will stabilize them on user request -[21:26:31] other than that nobody bothers opening bugs -[21:26:38] and by me and dilfridge as well -[21:26:48] we may forget about this point if we get a 4.6 stable soonish -[21:27:07] and if we drop older releases -[21:27:13] again, discussion about 4.6 future is later in the list, so let's skip this point for now -[21:27:20] dilfridge: agreed? -[21:27:23] but as long as we want to keep 4.4 still around, we should ask for some "stable testers" on the dev-ml -[21:27:24] yes -[21:27:27] agreed -[21:27:29] anything else here? -[21:27:34] no -[21:27:43] noone? -[21:27:48] ok, next: -[21:27:52] 3) kde-git/eclasses migration and status, move kdepim 4.6 beta in tree masked -[21:28:13] reavertm / Sput / scarabeus (i don't know who else) did some cleanings in the eclass -[21:28:13] ok i cleaned a mess we had in eclass -[21:28:17] now reaver is focused on it -[21:28:21] how is its status? can it be merged? ETA? -[21:28:30] sput is main person responsible for packages from my PoV -[21:28:34] aka he tests -[21:28:42] (but he is on date now) -[21:28:46] eta is upstream is insane -[21:28:52] cause it will take quite some time -[21:28:52] ? -[21:28:54] ok -[21:29:03] we need git-2 in tree first (what else do you mean by 'merge'?) -[21:29:15] yeah git-2 is progressed as we speak -[21:29:22] migrate, not merge -[21:29:23] i need to talk with ulm a bout some variale names -[21:29:48] ok, so 1) git-2 in tree 2) review/test 3) move to tree -[21:29:53] can we have an ETA? -[21:30:14] and anything specific we should test? -[21:30:20] git2 14 days -[21:30:29] i want to hear if all features are implemented -[21:30:34] and if we lack something -[21:30:40] (i want to keep that mess minimal) -[21:30:48] i might to remove 2 cloning apoproaches and keep only one -[21:30:52] (the submodules one( -[21:31:10] kde4-* seems to work - I don't think anyone will ever implement KMEXTRA-aware kde4-meta_src_unpack for git though -[21:31:53] has anyone tried koffice? -[21:31:58] yes -[21:32:02] it works -[21:32:05] dilfridge: wfm -[21:32:19] but with that calligra /&/&%(/& its prbably getting more complicated again -[21:32:21] i could complain about integration of tha tone shit -[21:32:22] ok good -[21:32:26] but go ahead -[21:32:37] we can get koffice out -[21:32:47] sure, do it -[21:32:49] actually I think that it should go out -[21:32:56] once I have the time... -[21:33:01] yes, i agree, i can help -[21:33:07] ok cool -[21:33:08] do you want to move the code to ebuilds directly? -[21:33:29] I have not made any plans at all -[21:33:32] so far -[21:33:49] but I think the only real issue is unpack/prepare -[21:33:50] anyway, moving the koffice bits out of the eclass is very wise thing to do -[21:33:55] reavertm: idea on how to do it? -[21:34:09] i already removed most bits sunshines -[21:34:20] of koffice? -[21:34:20] good -[21:34:26] yeah -[21:34:30] i didn't notice -[21:34:34] ok cool -[21:34:36] even better! -[21:34:51] so, ETA? scarabeus? -[21:34:53] a month? -[21:34:55] less? -[21:35:19] there's still some koffice stuff in kde4-meta though -[21:35:39] i need to work on git-2 first -[21:35:43] so not sooner than month -[21:35:58] ok, if you can compile a list of todo for that we could help -[21:36:03] I think deadlines would be unreliable anyway -[21:36:12] for the record mostly -[21:36:17] no deadlines just planning -[21:36:36] anyway, i think we are done here -[21:36:46] 4) Shall we drop useflags kdeenablefinal and/or kdeprefix to simplify code? -[21:36:56] shall we vote on this? -[21:37:00] no -[21:37:05] i really object -[21:37:09] the impementors should tell us -[21:37:14] kdeprefix - jorge -[21:37:18] we have about 10 bugs about kdeenablefinal, no big deal -[21:37:19] kdeenable - reaver -[21:37:25] my opinion: keep kdeenablefinal (it's upstream stuff), drop kdeprefix (it fills up our eclasses with cruft) -[21:37:25] and i want kdeprefix -[21:37:27] please keep kdeenablefinal at least (it's cheap) -[21:37:40] kdeenable final should stay i agree -[21:37:45] the guy that filed the bugs for kdeenablefinal provided patches -[21:37:46] but kdeprefix i dont see anyone using it -[21:38:00] i plan to do it actually -[21:38:21] i want to switch back to live as my main desktop -[21:38:31] and i don't want a chroot as i did in the past -[21:38:34] some packages cannot be kdeprefixed (bindings for instance) -[21:38:41] hmm -[21:38:42] i plan to work on them -[21:38:50] no, they can't -[21:38:51] why we still need kdeprefix? -[21:39:00] it will confuse end users -[21:39:05] it's a feature, we don't "need" it -[21:39:13] reavertm: why they can't? -[21:39:18] it makes our eclasses way too complicated -[21:39:36] -*- reavertm doesn't think kdeprefix is complicated -[21:39:52] why can't they be prefixed? i haven't looked at the code yet -[21:39:52] it definitely isn't like it used to be -[21:39:57] i suppose you did -[21:39:59] it is qutie clear -[21:40:07] but qutie few apps are not kdeprefix aware -[21:40:09] (misc one) -[21:40:19] and it has quite few bugs noone attendet to -[21:40:25] *ded -[21:40:52] ok then, give me time till the next meeting to test it and i'll report back -[21:40:55] tampakrap: actually bindings may work but sip files needs to be slotted -[21:41:08] i plan to work on the misc apps and python packages -[21:41:25] judge 1st it's worth your time -[21:41:31] -*- reavertm thinks it isn't -[21:41:37] no, having to maintain a chroot is -[21:42:12] well i use live on my laptop -[21:42:22] and its only DE here -[21:42:37] anyway, do we all agree to keep kdeenablefinal and kdeprefix and bring the topic back again? -[21:42:38] -*- dilfridge thinks a laptop can crash in more than one way anyway :D -[21:43:05] mumble... ok -[21:43:44] i see no objections, next: -[21:43:51] 5) Dropping of semantic-desktop useflag with guide update (mostly even kdebase needs it on now) -[21:44:06] i fixed it for plasma-workspace -[21:44:09] i would reat -[21:44:13] i had to write an upstream patch -[21:44:16] rather preffer it to be still availible -[21:44:25] virtuoso and semantic stuff is not something most might want -[21:44:46] our ebuilds are broken, upstream still has support for the useflag -[21:45:11] plasma-workspace along with libplasmaclock causes trouble with kdepimlibs due to our splitting -[21:45:16] i'll dig in more -[21:45:16] tampakrap: your fix suck -[21:45:17] does anyone know how this will develop for 4.7? -[21:45:32] tampakrap: i dont want libkdepim as harddep for it -[21:45:38] it doesn't, it was approved by aseigo -[21:45:44] what harddep? -[21:45:49] what are you talking about? -[21:45:56] wait wait, libkepim != kdepimlibs -[21:46:03] and what happens when kdepim-4.6 goes in tree? -[21:46:50] https://projects.kde.org/projects/kde/kdebase/kde-workspace/repository/revisions/5701ee97f896bf25de5dfbcc2699695794f25b34 -[21:47:06] this is the patch, where do you see a harddep? -[21:48:11] anyway, our affected ebuilds are plasma-workspace/libplasmaclock and kdeplasma-addons -[21:48:19] ah i am talking about plasma workspace -[21:48:21] :) -[21:48:22] i saw the code, the problem is in our side -[21:48:27] first of all, libkdepim is from KDEPIM, and it's not kdepimlibs -[21:48:33] the patch is in plasma-workspace -[21:48:59] anything else needs kdepimlibs? -[21:49:11] nothing needs it, it is still optional -[21:49:30] why do we have this agenda item then? :P -[21:50:00] --> dilfridge_ (~quassel@gentoo/developer/dilfridge) has joined #gentoo-meetings -[21:50:01] i have no idea, i am just pointing out that the item is invalid, the problem is in our side -[21:50:06] <-- dilfridge (~quassel@gentoo/developer/dilfridge) has quit (Ping timeout: 240 seconds) -[21:50:16] ok in that case ebuilds need fixing -[21:50:22] before we can stable 4.6 -[21:50:26] yes, we have open bugs and i am working on it -[21:50:49] 6) Making +consolekit and +policikit or removing the useflags as whole (non working stuff run-as is annoying) -[21:51:00] no idea about this one -[21:51:12] thats from me -[21:51:26] if those two are not around most of the user perms stuff is not working -[21:51:31] so users might complain a lot -[21:51:31] I remember from some upstream bug report that one of them is now required -[21:51:41] so i would go and just make it required -[21:51:42] really -[21:51:51] if not it is just broken (not supported anymore) -[21:52:02] <-> dilfridge_ is now known as dilfridge -[21:52:04] <-> dilfridge is now known as dilfridge_ -[21:52:06] <-> dilfridge_ is now known as dilfridge -[21:52:37] is it too much load if we make them harddeps? -[21:52:42] nope -[21:52:45] like 5 more deps -[21:52:48] sure then -[21:52:49] people will whine, as usual -[21:53:04] it kind of forces a more modern system, but makes debugging for us easier -[21:53:04] for sure -[21:53:11] what about macos? -[21:53:19] do they have different KAuth backend? -[21:53:37] http://techbase.kde.org/Development/Tutorials/KAuth/KAuth_Basics -[21:53:47] -*- dilfridge thinks the weird guys should be handled later -[21:54:19] i don't see anything arch specific there -[21:54:33] no, because it may determine we can't harddep them -[21:54:43] do we have them enabled by default? -[21:54:48] if not, can we do this instead? -[21:55:40] people should know that they need some things as deps to have a DE like KDE run normally -[21:55:47] tampakrap: https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/show/kdecore/auth/backends -[21:56:21] yeah -[21:56:38] so, should we ask upstream? -[21:56:47] i could mail those guys listed in the changelog -[21:56:59] no need -[21:57:06] or we could enable it by default for everything but mac -[21:57:08] I'd add IUSE defaults -[21:57:20] reavertm: please not -[21:57:30] people WILL try to switch it off -[21:57:42] it does not help -[21:57:45] yes -[21:57:55] it doesn, then we can say - screw you, you disabled it -[21:58:08] yeah, elog -[21:58:14] reavertm: it's a use flag so people think its optional -[21:58:16] endofstory -[21:58:24] and we have wasted time trying to find the problem and added additional cruft to the eclass -[21:58:31] and elog gives me the right to invalid their bug -[21:58:38] it's also enabled by default which means there's some thinking behind it -[21:59:12] we may be in the land of infinite options but not in the land of infinite support manpower -[21:59:37] i agree with IUSE defaults ftr -[21:59:50] maybe use.force :P -[22:00:02] god just drop it and let the 4 people complain -[22:00:05] reavertm: that's ok I guess -[22:00:06] (someone can use.mask if one wants) -[22:00:09] come on we threw mysql their way -[22:00:11] and nobody whine -[22:00:12] d -[22:00:15] nowdays -[22:00:16] :D -[22:00:19] drop it! -[22:00:51] reavertm: your call :P -[22:01:02] i don't care much -[22:01:40] -*- reavertm thinks the one who is going to do the job, should decide -[22:02:37] I'm prefer not to drop use flags though -[22:02:39] reavertm: ok your call -[22:02:52] reavertm: tampakrap is the one who decide in the end nowdays :) -[22:03:02] it's not really a harddep if one wants just kdelibs + misc stuff -[22:03:13] yeah i don't like dropping the useflag -[22:04:04] does use.force have precedence over use.mask? -[22:05:02] (I mean, is it possible for etc/portage/*/use.mask to disable use.forced flag? -[22:05:17] no idea -[22:05:55] anyway, it is taking too long, let's decide in the mailing list instead -[22:06:02] -*- reavertm votes for use.mask -[22:06:08] use.force* -[22:06:11] i'll send the mail, we can get some feedback from users as well -[22:06:21] ok -[22:06:30] use.force is easily done and reversible -[22:07:20] and should be hard enough for users to switch off -[22:07:24] dilfridge: agree to continue in the ml? -[22:07:29] ok -[22:07:36] thank you -[22:07:39] 7) AT/overlay/bugzie access policy -[22:07:43] this is mine -[22:08:07] scarabeus: i need a clear list on who has access to the overlay, who has editbugs privs and who is a KDE AT -[22:08:11] and compile a page -[22:08:38] and i need to define a rule for ATs, and get all those priviledges together -[22:08:40] tampakrap: ahem you have access to the list -[22:08:41] do you agree? -[22:08:46] i dont have it -[22:08:53] and i upgraded everyone to at already -[22:08:56] lol, i know, i'm just saying -[22:08:58] who can potentially have elevated rights in bugzie? -[22:09:04] only real devs? -[22:09:11] even users -[22:09:19] which we are watching -[22:09:31] "arch testers", "overlay committers" -[22:09:32] the one who has finished ebuild quiz, has gone through an AT/HT review session and someone is watching him -[22:10:14] so, define two groups of people in addition to ATs? -[22:10:28] hmm? -[22:10:39] what two groups? -[22:12:14] ATs, overlay commiters -[22:12:20] is that what you just said? -[22:13:06] nono I was just trying to make a point to papillon81 -[22:13:44] ah k -[22:13:53] scarabeus: i need your idea on what to do here -[22:14:03] in effect, the two groups would be "overlay committers" and "bugedit", but I'm not sure if it would make sense to make just one group for that -[22:14:08] i have no idea how to clean up this mess -[22:14:11] simplifies things -[22:14:25] eg Sput refuses to become an AT, doesn't want ot finish ebuild quiz -[22:14:40] just have two groups, access ; access + bugedit which == AT -[22:14:44] we could have overlay commiters and full ATs but i don't like it -[22:15:48] anyway, i'll compile the list first and bring the topic up again -[22:16:04] who is going to be AT lead now? or should we drop the title? -[22:16:15] i find it a bit useless, like every lead position :P -[22:16:45] drop it -[22:17:16] no volunteers :P -[22:17:23] next: -[22:17:25] 8) livedvd issues -[22:17:28] who knows, AT lead does more recruiting work imho -[22:17:31] likewhoa: anything to say here? -[22:17:47] reavertm: do you want the position then? -[22:17:50] nothing really just a few request made by users -[22:18:11] tampakrap: hell no -[22:18:27] thought so :) -[22:18:33] i added an icon to the kde start menu and some users wanted to know if kde can make use of it, also some users wanted to know if there were any gentoo centric kde themes -[22:18:37] likewhoa: shoot now that we are all here :) -[22:18:57] -*- dilfridge runs -[22:19:06] -*- likewhoa pulls dilfridge back with some cookies -[22:19:22] well, tbh i need someone to do some graphics work if we are going to implement branding -[22:19:33] and i couldn't find anyone the last two years -[22:19:49] tampakrap: poke a3li -[22:19:59] he hates kde -[22:20:11] i can also do graphics but won't be available for that until mid march -[22:20:30] tampakrap: i made the wallpapers for the livedvd, not the one on the desktop but the others ones -[22:20:37] i think jmbsvicetto used one for FOSDEM -[22:21:25] well, if you are willing to help here i'm all in add it to the tree -[22:21:29] but a kde gentoo centric theme would be ideal and can be part of the branding USE flag -[22:21:35] sure -[22:21:46] let's do some work first and bring the topic back again -[22:21:56] ok -[22:22:08] anything else? -[22:22:13] no -[22:22:19] cool thanks -[22:22:28] please everyone test the dvd :) -[22:22:31] in #gentoo-ten -[22:22:44] use zsync so you don't waste bandwidth on new releases -[22:22:51] net-misc/zsync that is -[22:23:03] next: -[22:23:06] 9) documentation status -[22:23:16] pretty please everyone read the documentation -[22:23:36] help me to complete the tips and troubleshoot with 4.6 specific parts -[22:24:09] i wanted to say something more about this one but i forgot it -[22:24:19] anyway, i'll merge the last two topics: -[22:24:26] 10) 4.6 (and misc apps with 4.6) status -[22:24:33] 11) early discussion about 4.6 stabilization -[22:25:03] i'm listening, i vote early for 4.6.1 stabilization :) -[22:25:16] stabilize 4.6 as quick as possible. 4.6.1 -[22:25:41] i need more feedback about misc apps though -[22:25:57] stabilize early. 4.6.1 should be fine. -[22:25:57] for example, knetworkmanager is broken and i lack the hardware to test currently -[22:25:58] knetworkmanager is waiting for ubuntu -[22:26:12] sorry? -[22:26:27] 4.6... doesn't feel worse than 4.5 -[22:26:34] i talked with wstephenson about it yesterday -[22:26:39] strange, I know -[22:26:40] do we want to wait for kdepim? if we say "stabilize fast" that means no -[22:26:50] i don't get you at all, sorry -[22:26:56] it is waiting for ubuntu to do what? -[22:27:11] tarball release /me thinks -[22:27:38] well, let's wait for kdepim to get a proper release first :) -[22:28:14] kubuntu are 'a bit worried' that it will be before KNM is ported to 0.9 -[22:28:49] tampakrap: what exactly is broken in you opinion? -[22:28:59] i have no idea, i saw a bug report -[22:29:07] but my laptop is off now and i can't test -[22:29:12] something about kwallet i think -[22:29:25] i would like more to know though about this -[22:29:35] well. i can look into it. also there are some nice patches from the pardus guys -[22:29:36] eg dilfridge: how is digikam/koffice in 4.6? -[22:29:42] fine -[22:29:56] reavertm: printing? -[22:29:59] any progress? -[22:30:02] 2.2.2 (stable) is broken but 2.3.1 is good -[22:30:36] printing.. some people report it works -[22:31:02] since when is kde supposed to do printing? =) -[22:31:09] since 4.4 -[22:31:15] "supposed" -[22:31:27] I thought that feature was disabled with 4.0 ... -[22:31:40] I bump scp usually on time, scp-kde - I'd prefer it to be still in ~arch -[22:32:00] the feature was not ported to kde4 at all, you're right -[22:32:55] anyway, we can discuss it next month after 4.6.1 gets a release -[22:33:08] i remembered what i wanted to say about documentation -[22:33:10] http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=tree;f=Documentation;h=d7e234375abd5fc61c4d7dae47adaf57d9efcac1;hb=HEAD -[22:33:12] nothing to discuss here, printing will not go stable -[22:33:36] i'm going to port them to guidexml (CODE, README etc) or merge them with the guide -[22:33:47] good idea -[22:34:00] i'll need feedback to the documentation though (pretty please) -[22:34:15] i think we are done -[22:34:21] *) open floor -[22:34:32] did anyone of you hear from the digikam guys? -[22:34:45] dilfridge: i am talking with will (suse) -[22:34:54] to shutup him abvout the opensuse argument -[22:34:56] so wait a bit -[22:34:58] ok... what's the general feeling there -[22:35:00] ok -[22:35:01] cross distro coord takes lot time -[22:35:03] what argument? -[22:35:25] so opensuse doesn't mind slotting and bundled libs? -[22:35:27] tampakrap: "opensuse likes the libs bundled" -[22:35:35] yeah good idea -[22:35:46] https://bugs.kde.org/show_bug.cgi?id=265328#c6 -[22:35:57] plus debian and others already agreed not to ship digikam2 -[22:36:05] if the issue is not resolved -[22:36:09] scarabeus: please bring svuorela to the table -[22:36:19] reavertm: he? -[22:36:21] ah -[22:36:32] debian guy -[22:36:43] we met him in fosdem -[22:36:49] scarabeus: remember? -[22:36:53] yep -[22:37:01] that s why i said ah -[22:37:07] anyway will do so -[22:37:07] will anyone join me in desktop summit this year? :) -[22:37:14] aug 6th berlin -[22:37:15] where it is? -[22:37:21] http://www.desktopsummit.org/ -[22:37:29] likely not me, other plans... -[22:37:42] if i make it (99% i will) i'll apply for a gentoo talk -[22:37:53] last year we were invited to do the talk -[22:37:59] oh, Berlin. that's good -[22:38:04] berlin sounds good -[22:38:15] but i would need to couchsurf somewhere :) -[22:38:27] reavertm: how about you? -[22:38:39] very unlikely -[22:39:18] hmm, August... who knows.. -[22:40:05] ok ladies, i think that's all -[22:40:47] thanks \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-log-20110331.txt b/meeting-logs/kde-project-meeting-log-20110331.txt deleted file mode 100644 index 84ecd70..0000000 --- a/meeting-logs/kde-project-meeting-log-20110331.txt +++ /dev/null @@ -1,370 +0,0 @@ -[20:07:42] !herd kde -[20:07:42] (kde) abcd, alexxy, dilfridge, jmbsvicetto, patrick, reavertm, scarabeus, spatz, tampakrap -[20:07:43] -*- alexxy here -[20:07:47] roll call please -[20:07:49] -*- dilfridge here -[20:07:57] here -[20:08:00] -*- scarabeus blurps -[20:08:14] dilfridge: wanna chair? -[20:08:17] for change -[20:08:21] uh oh -[20:08:36] err ok -[20:09:01] hehe the topic still links to last meeting -[20:09:16] so... -[20:09:26] let's look at the agenda. -[20:09:42] 1) kde-git/eclasses migration and status -[20:09:58] since I dont do live, what's the status? -[20:10:23] scarabeus: ^^ git eclass status? -[20:10:47] -*- ABCD can't stay too long -[20:10:48] i got nice hint from exherbo guys and currently am attempting it to make bare checkouts even with submodules -[20:10:57] so if i manage to do that it would be epic -[20:11:17] oook, I remember the discussion on the ml -[20:11:20] but i didnt have time to focus on it lately -[20:11:22] can i get an option to use non-bare checkouts instead? -[20:11:25] as i blaged -[20:11:42] it is easy to override those commands as-is already -[20:12:07] i guess the more interesting question is does it still work then -[20:12:34] -*- dilfridge can symlink /bin/echo to /usr/bin/portage -[20:12:55] but anyway -[20:13:33] the hard question: scarabeus: what's your guess how long this will take? very roughly? -[20:13:52] few days when i work on it so i can test everything -[20:14:18] afaik kde eclasses don't need anything, we are only waiting for git-2 to hit tree first -[20:14:26] correct me if i'm wrong -[20:14:54] if it is so it is quite easy to make them git.eclass dependant -[20:15:17] since there are no live ebuilds in main tree it does not affect anything by default -[20:15:18] meaning they would also work with current git.eclass? -[20:15:32] ah ok -[20:15:51] yeah, i'll prefer those eclasses to hit tree before 4.6.2 -[20:16:07] so we can get proper testing from the stable candidate -[20:16:07] that could be pretty soon (today is official tagging day) -[20:16:26] yeah, this week -[20:17:11] do you want to selectively patch the main tree eclass or just copy everything from overlay (better)? -[20:17:14] can you paste us the link of the topics please? -[20:17:38] http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/maintainers/meetings/meeting-2011-03-31;hb=HEAD -[20:17:48] i'd like a quick review first, a patch in the alias or in -desktop would be preffered -[20:18:03] ok -[20:18:22] I'm asking because we "collect differences" between tree and overlay -[20:18:46] i would like to hear from reavertm before merging them -[20:18:47] at some point it would make sense to sort this out -[20:18:50] true -[20:18:54] we could ask for comments on -dev as is -[20:19:01] i don't know if he had any todo for the eclasses we are missing -[20:19:07] or that -[20:19:09] at least you others could work on the stuff people point out -[20:20:01] so, summarizing: we should do a review of the current overlay eclasses... -[20:20:08] yup -[20:20:10] * figure out what actually depends on git-2 -[20:20:15] why -[20:20:18] that does not matter -[20:20:26] i can move it to git.eclass in 20 secs -[20:20:32] git-2 is not showstopper -[20:20:35] ok -[20:20:40] even better -[20:21:20] * collect a todo list (or make reavertm send us his) -[20:21:37] * and review the current differences between tree and overlay -[20:21:53] any volunteers? :D -[20:22:28] i'm not the eclass expert -[20:22:39] anyway -[20:22:48] back to teh agenda -[20:23:01] 2) move kdepim 4.6 beta in tree masked? -[20:23:07] opinions? -[20:23:13] no -[20:23:18] 1) it is outdated -[20:23:24] true -[20:23:24] 2) it depends on updating eclasses first -[20:23:27] 2) there is no eclass support for it yet :P -[20:23:30] true -[20:23:39] but anyway, it is too outdated -[20:23:49] anyone in favour? -[20:24:07] and upstream kdepim will create new kdepim snapshots when a core kde developer asks to -[20:24:13] huge mess -[20:24:22] wtf -[20:24:27] they should release that shitz :D -[20:24:28] i could create our own snapshots, but i don't care enough to be honest -[20:24:34] I guess that answers the question -[20:24:36] most people are getting annoyed :) -[20:24:47] any news about an official release (schedule)? -[20:25:14] no -[20:25:21] :( -[20:25:26] tampakrap: is there any kdepim version that can work with 4.5.5, 4.6* ? -[20:25:28] kde* -[20:25:28] they said about an rc1 but apparently it didn't make it -[20:25:35] yes, 4.4.10 -[20:26:12] tampakrap: so we can use kdepim-4.4.10 with kde-4.5.5/4.6 to move forward? -[20:26:32] seems so -[20:26:40] and sorry for anticipating the next point -[20:26:42] if you are talking about a stable candidate, yes, 4.4.10 is fine -[20:26:55] yes -[20:27:20] ok... following the logical order of things instead of the numerical one... -[20:27:32] 5) 4.6 status / stabilization / important bugs -[20:27:48] apart from the blockers list on the tracker, no idea -[20:27:53] major is that akonadi integration in basic pkgs -[20:28:01] and i guess that tracker catched everything -[20:28:05] we have 5 or 6 major blockers, i am aware of all of them -[20:28:13] what akonadi integration? -[20:28:28] given the current status with upstream about 4.6, anyone sees any reason to delay getting 4.5.5 marked stable instead of keep waiting for a possible 4.6 stable candidate? -[20:28:30] the -semantic-desktop failure bug? -[20:28:33] yep -[20:28:57] 4.5.5 is completely broken -[20:29:23] general question: how many of you get akonadi errors on login? -[20:29:40] i don't -[20:29:49] and i use kdepim and kdepimlibs master -[20:30:03] tbh, I never checked -[20:30:33] I always get and have not been able to solve that... maybe I should start collecting info... -[20:30:37] ok -[20:30:44] I use what I was forced to use with 4.6.1 (having to enable semantic-desktp) -[20:30:56] let's have a quick look at the blockers -[20:31:19] three of them are about -semantic-desktop and -kdepimlibs support -[20:31:28] one is about kdepim 4.4.10 translations -[20:31:34] i don't remember the others -[20:31:42] Bug 353048 -[20:31:44] dilfridge: https://bugs.gentoo.org/353048 "kdebase/kwin-4.6 USE=-opengl does not compile"; Gentoo Linux, KDE; NEW; sefi:kde -[20:31:51] this is fixed upstream -[20:32:05] and the fix may be in 4.6.2 if it is backported in 4.6 branch -[20:32:34] Bug 353726 -[20:32:35] dilfridge: https://bugs.gentoo.org/353726 "kde-base/plasma-workspace-4.6.0 should not depend on kdepimlibs"; Gentoo Linux, KDE; REOP; ikandros:kde -[20:32:41] yeah i mentioned that -[20:32:56] i'm on it -[20:33:16] Bug 353730 -[20:33:19] dilfridge: https://bugs.gentoo.org/353730 "kdeplasma-addons-4.6.0 USE=-semantic-desktop fails to build without akonadi/semantic-desktop"; Gentoo Linux, KDE; REOP; KeithBHarrison:kde -[20:33:23] this is probably related -[20:33:25] and that -[20:33:41] Bug 357545 -[20:33:43] dilfridge: https://bugs.gentoo.org/357545 "kde-l10n-4.6.1 wants to overwrite kde-misc/konq-plugins-4.4.0-r1 files"; Gentoo Linux, KDE; NEW; panard:kde -[20:33:53] no idea, scarabeus^^ -[20:33:56] that should HOPEFULLY be fixed with 4.6.2 -[20:34:02] as it is pretty trivial -[20:34:11] tampakrap: i told you that they have to use konq-plugins-4.6.1 -[20:34:19] tampakrap: if they do so no clashes -[20:34:28] ok, so we should adjust deps -[20:34:33] dilfridge: plz2fix -[20:34:34] they got the release of 4.6.1 completely screwed up there -[20:34:50] later -[20:35:03] Bug 357959 -[20:35:04] no blocker, remove it from the list please -[20:35:05] https://bugs.gentoo.org/357959 "kde-base/nepomuk-4.6.1: nepomuk service stub crashes after update"; Gentoo Linux, KDE; NEW; dilfridge:kde -[20:35:09] or lower severity -[20:35:30] done -[20:35:41] your nepomuk bug, can't reproduce -[20:35:42] that one is pretty annoying but an upstream problem -[20:35:46] a user reported something -[20:36:09] yes but I dont think it is gentoo-only -[20:36:18] hey, upstream says it is fixed -[20:36:32] yes 462 -[20:36:34] good -[20:37:40] Bug 359979 -[20:37:41] dilfridge: https://bugs.gentoo.org/359979 "media-libs/xine-lib crash with MKV WebM"; Gentoo Linux, Applications; ASSI; rezbit.hex:media-video -[20:37:44] a bit obscure -[20:37:47] huh? -[20:37:52] vlc is default -[20:37:55] kde upstream says it's a xine-lib bug -[20:38:10] probably this should not be a blocker either -[20:38:15] oh guys -[20:38:16] I think we should close all phonon-xine bugs as CANTFIX -[20:38:23] i would make phonon-gstreamer default -[20:38:26] not the vlc -[20:38:28] blocker removed -[20:38:35] i find bit stupind to demand videoplayer -[20:38:36] for that -[20:38:41] not phonon-gstreamer, please -[20:38:46] -*- dilfridge bangs on the table... open floor is later :) -[20:39:03] ok back to the actuall agenda -[20:39:05] dilfridge: open floor is for people outside the team ;) -[20:39:17] jmbsvicetto: so you rather pull in the vlc? -[20:39:18] :) -[20:39:29] xine does not work -[20:39:34] scarabeus: I think that's what upstream expects us to use as default -[20:39:40] so do we agree we should consider 462 as "potential stable candidate"? -[20:39:43] (I'm not sure though) -[20:39:45] scarabeus: if you consider webkit part of the environment, then you'll need a video player ;) -[20:39:47] i didnt see it yet -[20:40:02] jmbsvicetto: gstreamer can manage over phonon -[20:40:07] jmbsvicetto: and i use mplayer -[20:40:11] I don't think we should see 462 as a stable candidate -[20:40:19] jmbsvicetto: well we have to -[20:40:22] one magic word -[20:40:23] HAL -[20:40:29] why not? -[20:40:30] :| -[20:40:33] +1 -[20:40:39] that releases will be broken forewer -[20:40:39] hal should be dropped -[20:40:45] just take look on what upstream does :) -[20:40:52] because I don't believe they'll be able to "not break" kdegraphics on this release -[20:40:55] so we just have to bite it and sadly release somehow -[20:40:58] +1, unless upstream breaks 4.6.2 even worse -[20:41:09] It's not about "stability" or it working, but about KDE being able to package the release -[20:41:33] well 4.6.1 works pretty well -[20:41:37] yes but I expect that the kde git migration will take another century or so -[20:41:46] alexxy: minus the semantic-desktop stuff ;) -[20:41:47] (while we dont even start...) -[20:41:53] yeah -[20:42:02] I don't expect it to *ever* be completely done -- see kde-wallpapers -[20:42:02] also we still need kdepim stuff -[20:42:06] hey, infra is busy -[20:42:38] oook -[20:42:39] tampakrap: My only issue with 4.6.2 is that I expect us to get a broken release (packaging wise). If the regressions about akonadi/pimlibs get fixed, I have no issue with it being marked stable -[20:42:40] and they again doing something with git,kde.org and projects.kde.org -[20:42:46] i said already kdepim 4.4.10 is fine along 4.6, don't make me repeat it in caps -[20:42:58] I still antecipate we may get some "angry" users, but there's little we can do about it -[20:43:15] we'll always get some angry users -[20:43:18] those are issues with the sponsors, even we have those kind of issues -[20:43:21] actualy now i see how childish i was when i look on the tiny issues with 4.5 ;P -[20:43:21] don't confuse things -[20:43:24] anyway -[20:43:32] we can talk about that again in three weeks -[20:43:35] i could've stabled some of that :) -[20:43:48] yes. -[20:43:50] nah i would give it 14 days for the stablebug if everything works -[20:44:06] we are behind schedule for that stuff for freedesktop stuff -[20:44:14] 3 weeks is 1 week after tagging, 2 weeks after release -[20:44:20] yep works -[20:44:23] well given that kde-462 will take another week or so, we can for sure have another meeting before the stablebug filing -[20:44:38] ok -[20:44:42] we are not behind if samuli is acting like a maniac about hal without proper documentation / announcements -[20:44:49] true -[20:44:53] <+willikins> New bug: https://bugs.gentoo.org/?????? Marked KDE-4.6.2 stable (URGENT) - HAL needs to die -[20:44:57] scarabeus: ^^ ? ;) -[20:45:08] DIE DIE DIE -[20:45:09] jmbsvicetto: something like that -[20:45:19] btw we can smash in solid4.6 -[20:45:19] :D -[20:45:25] and pretend everything is perfect xD -[20:45:37] so -[20:45:41] now for the optional stuff -[20:45:45] scarabeus: you mean solid-4.5? -[20:45:46] also there can be another issue -[20:45:55] because of nm-0.9 stuff -[20:45:59] nm? -[20:46:05] networkmanager -[20:46:07] what about it? -[20:46:09] jmbsvicetto: nah, hal is out since 4.6 :) so we can stable just solid :P -[20:46:11] new api -[20:46:14] totaly different -[20:46:18] but it does not matter -[20:46:23] current solid will not work with it at all -[20:46:23] since knetworkmanager is already working on it -[20:46:27] and it wont use solid at all -[20:46:43] ok -[20:46:46] i know -[20:46:52] scarabeus: right, so you want to kill solid-4.5 :P -[20:46:57] and they working on solid backend for it -[20:47:11] jmbsvicetto: 4.4 -[20:47:11] better to kill kde < 4.6 -[20:47:19] jmbsvicetto: we talk about stable :D -[20:47:38] what alexxy said -[20:48:37] so, summary: need some stable kde-4.6 in the near future, as the pressure is rising(tm) -[20:49:08] next point -[20:49:16] 3) Shall we drop useflag kdeprefix to simplify code? -[20:49:16] "The problem is that bindings are not prefixed, and a possible fix (proposed -[20:49:16] by reavertm) would be to slot sip. tampakrap said he'll work on this, and bring -[20:49:16] the topic back in next meeting." -[20:49:39] any news? -[20:49:41] can i get another month please? -[20:49:45] busy with gsoc proposal -[20:49:49] does any of us use kdeprefix? -[20:49:58] i started using it -[20:50:05] you're the boss, but does anyone actually use it? -[20:50:05] but i'm still stuck on my 4.6 -[20:50:08] hmm -[20:50:26] it's masked i don't see why you want to drop it -[20:50:33] for testing better to use VMs -[20:50:34] if we drop kdeprefix, we can simplify a *lot* of things -- including slotmoving everything to :4 -[20:50:38] like lxc or xen -[20:50:52] no it isn't better -[20:50:53] and the eclasses will be much simpler -[20:50:55] alexxy: or even just a chroot -[20:50:59] i will have to maintain to boxes then -[20:51:11] its simple -[20:51:20] share binary packages across them -[20:51:23] My feeling for a long time is that kdeprefix also needs to die -[20:51:30] it's not simple -[20:51:34] use KSM to save your memory -[20:51:36] and so on -[20:51:38] different use flags different configurations -[20:51:46] it's not a resource problem -[20:51:57] it'a a pain in the neck having to maintain an extra box -[20:52:05] wait, sorry, I mean kdeenablefinal, not kdeprefix -[20:52:08] its not too hard -[20:52:30] I liked kdeprefix, but as it needs upstream work and we can't get their collaboration, I no longer object to killing it -[20:52:30] ok, let me disagree -[20:52:45] anyway, i want that useflag but if you guys want we can go on a vote -[20:52:59] -*- alexxy running many VM's @works to test new stuff (like experimental gromacs patches and so on) -[20:53:02] -*- ABCD votes to kill it -[20:53:09] -*- alexxy also -[20:53:12] -*- dilfridge votes to kill it -[20:53:57] -*- jmbsvicetto abstains -[20:54:29] I'd say since that is less than 50% of the team we dont change anything for now. -[20:54:43] make vote over ml so everyone state the opinion -[20:55:10] for now decision postponed again -[20:55:17] next point -[20:55:26] 4) Making +consolekit and +policikit on by default or removing the useflags as whole (non working stuff run-as is annoying) -[20:55:26] "No consensus was reached, the topic will be continued in the gentoo-desktop mailing list." -[20:55:26] Mailing list query resulted in two user voices for "default on but still configurable" -[20:55:30] I have to leave now, as I have a meeting in ~1 hour that's ~55 minutes away -[20:55:38] cya -[20:55:41] cu -[20:55:44] about the flags, people want them -[20:55:59] additionally people want udev deps optional as well -[20:56:00] yes but do we want to maintain them? -[20:56:22] i still support the profile/kde and use.force solution -[20:56:33] udev deps at least have to be removed with USE=prefix -[20:56:39] tampakrap: udev and policykit optional deps needed to have kde on kernels other than linux -[20:56:58] and prefix can't do udev/polkit/consolekit -[20:57:14] I don't see a point for the kde profile, but I just use linux/amd64/10.0 -[20:57:25] *bsd/solaris/hurd cant have udev -[20:57:44] polkit may still work -[20:58:16] dilfridge: are the above sufficient to you? -[20:58:22] anyway. are there any objections to making +consolekit and +policykit on by default in the ebuilds, and forcing them in the kde profile? -[20:58:28] so if we will have udev deps unconditional we should drop prefix/*bsd and all non native linux stuff -[20:58:48] dilfridge: I don't have an issue with IUSE defaults and don't use the kde profile -[20:58:59] yeah no objections -[20:59:01] dilfridge: its good idea -[20:59:07] ok -[20:59:13] alexxy: I'd prefer to maintain prefix compatiblity, if possible -[20:59:25] then we go with that I'd say -[20:59:32] last point -[20:59:35] open floor -[20:59:53] anything else to discuss? -[20:59:56] also gentoo prefix can be used instead of kdeprefix =D -[21:00:10] well -[21:00:28] alexxy: that is actually interesting... gentoo on gentoo :))) -[21:00:28] we again have problems with arches like x86-fbsd ppc* -[21:00:45] -*- alexxy uses prefix on rhel4 cluster -[21:01:09] alexxy: ppc is still recovering from their lost boxes -[21:01:13] what problems? -[21:01:26] unkeyworded deps as usual -[21:01:30] I need to resume my discussion from council with arch teams -[21:01:42] oh -[21:01:50] yeah but xarthisius is pretty helpful and responsive -[21:01:52] that's their problem, not ours -[21:02:28] last time i masked some use flags or whole kde release on arm ppc ppc64 and x86-fbsd -[21:02:28] it's mainly about giving a friendly poke if something is really needed I think -[21:03:17] I dont know nothing about x86-fbsd -[21:03:46] i dont know anybody who is using it -[21:03:48] ok -[21:04:00] but kde has ~x86-fbsd keywords -[21:04:03] dilfridge: aballier -[21:04:29] yes but aballier afaik was only contact to a user somewhere -[21:04:45] !bug 357403 -[21:04:46] https://bugs.gentoo.org/357403 "[KDE] Please keyword kde-4.6 deps to unmask needed useflags"; Gentoo Linux, Ebuilds; NEW; alexxy:kde -[21:05:04] dilfridge: he lost his bsd boxes -[21:05:06] well i can setup x86-fbsd VM -[21:05:14] ok -[21:05:46] If I find time to reconfigure my home network I can do arm at some point -[21:05:48] i may already have one -[21:05:49] http://choqok.gnufolks.org/2011/03/choqok-is-going-to-leave-kde-for-gnome/ -[21:05:52] he would like to resume his work on bsd -[21:06:04] dilfridge: what arm board do you have? -[21:06:11] openrd -[21:06:57] so, summary: about keywords nothing really changed :] -[21:07:06] anything else? -[21:07:21] or shall we call it a day? -[21:08:14] -*- dilfridge takes this as "no, and yes" -[21:08:26] I'll post the log -[21:08:33] could one of you please make the summary? -[21:08:40] i'll handle the summary -[21:08:43] ok cool -[21:08:46] tomorrow, i'm about to pass out -[21:08:49] :) -[21:09:16] cheers and thanks for being here :D diff --git a/meeting-logs/kde-project-meeting-log-20110602.txt b/meeting-logs/kde-project-meeting-log-20110602.txt deleted file mode 100644 index 19ab44d..0000000 --- a/meeting-logs/kde-project-meeting-log-20110602.txt +++ /dev/null @@ -1,553 +0,0 @@ - ok let's start - !herd kde - (kde) abcd, alexxy, dilfridge, jmbsvicetto, patrick, reavertm, -spatz, tampakrap - roll call - 1 - 2 --*- dilfridge hears bonsaikitten munching in the distance - 3 - -http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=Documentation/maintainers/meetings/meeting-2011-05 - agenda ^^ - jmbsvicetto: here? - until he shows up, anyone familiar with the status of 4.7 so far? - nope - here - so, 4.6.80 - can you give us a brief summary of the betas please? --*- alexxy here - I think I got most of kdebase, kde-utils, kde-graphics, -kde-games and kde-network working - alexxy then bumped the rest - about the status of the upstream tree / tarballs: - most problematic is kdebindings - I think no package is working - status of upstream tree / tarballs: - about kdebindings... I vaguely remember an e-mail longtime ago -when kde-4.7 was started, where the new split was explained - i recall that too - kdebase was split on 3 tarballs - kdebase, kde-runtime and -kde-workspace - do you think we should rename our metas? - the info is available in the readme.modularization of the -tarball - http://old.nabble.com/kdebindings-split-td30617636.html - http://paste.pocoo.org/show/399690/ - The question is will they stick to the names or not - at this point I think they haven't made up their minds yet - but they have the repos ready - don't they follow their repo naming schema? - alexxy: ^^ - I'm not sure they're doing it consistently - >:| - for example, smoke (which I think is a single repo) was split -into 3 tarballs ---> Skiarxon (~quassel@ppp091138207078.dsl.hol.gr) has joined #gentoo-meetings - smokegen, smokeqt, smokekde - sec - like in the deptree - can i have a list of the bindings tarballs? - I'm not sure as I didn't had the time to go after the repos. I -based my work in the existing tarballs and on the live ebuilds - which were in -very good shape!!! - i'd like to compare with the repos right now - I can give you the tarballs names for them. I still think -there's a missing krosspython, but after 3 emails I've yet to get a proper -reply - i follow the list, yes - so as I said: smokegen, smokeqt and smokekde - jmbsvicetto: I'd hope the live ebuilds were in good shape -- I use them -myself :) - here are the repos for referrence: -https://projects.kde.org/projects/kde/kdebindings - smoke is consistent so far --*- alexxy also use live =) but now gonna switch to betas - perlqt, perlkde, qtruby, qyoto, korundum, kimono and pykde4 - tampakrap: ok, then the live ebuilds need to be updated as well - perl is consistent - should we pkgmove smoke to smokegen, or just add a block on -smokegen to smoke? - everything is checked - block, because we're not changing :4.4 and :4.6, I'd think :) - the tarballs are consistent to the names in the -README.MODULARIZATION file - ruby is consistent - ABCD: only 4.7 is involved - dilfridge: everything is - :) - tampakrap: pkgmove moves *every* version unconditionally - so, to get kdebinding we need to start by spliting smoke. I -wasn't sure if the live ebuild was ok or not, so I didn't start that - (you *cannot* use a versioned atom in that spot) - so, we follow upstream's repos for kdebindings since the tarballs -and repos, do we all agree? - yes - ABCD: correct, i got you wrong - yes - seems a good idea - and I'm for blocker, not move - also seems we need something to do with kross* modules - If no one beats me to it, I'll work on it this weekend - blocker is one way - alexxy: what about them? where are the tarballs? :) - tampakrap: no tarball for krosspython - mia - tampakrap: dunno =) - if you want, prepare the live ebuilds then - tampakrap: the README mentions the pykde4 tarball, but it no -longer includes any code - i believe they'll follow the repo names as the rest of the module - this is about the only really crucial piece of binding because of -plasma... - jmbsvicetto: sorry? - where is the pykde4 code then? - sorry, I'm mixing tarballs - ok, we're done with bindings - jmbsvicetto: give us the modules that are monolithic please - kdepim is one of them, what else? - kdegames - kdeutils - kdenetwork - those haven't migrated yet correct? - kdenetwork - kdemultimedia --*- tampakrap checks - kdetoys - kate (kinda), kde-baseapps, kde-runtime, kde-workspace, -kdeaccessibility, kdeadmin, kdeartwork, kdegames, [kdelibs], kdemultimedia, -kdenetwork, kdepim, kdeplasma-addons, kdesdk, kdetoys, kdeutils, kdewebdev - kdesdk - kdegames, kdeutils, kdenetwork, knemultimedia, kdesdk are still in -svn - oh yeah, kate was also fun - also kdetoys, kdeaccessibility, kdeadmin, kdeartwork - kate is now the name of the module, so I had to update the -eclass as we hadn't "predicted" that case and the src_unpack was failing - so, i'd say let's keep them as they are - kdelibs is something we need to watch out. There's some doubt -whether it'll be split kdelibs and kdelibs-experimental - one by one please - don't mix them - kdelibs-experimental is not going to be a tarball - it is an experimental repo - yes, but kdelibs-4.6.80 had a dep on libs from it. Dirk ended up -"smashing" it all together in kdelibs-4.6.80 - ...one that's currently *required* by kdelibs proper - yeah - which was a mistake ---> devurandom (~devu@unaffiliated/devurandom) has joined #gentoo-meetings - there was a discussion in the ml whether that dep was a mistake -or not. I don't recall the conclusion - so, about the ones that haven't migrated yet - anyone knows if this will be done during 4.7? - it's likely - causing more mess? - of course :) - we're fsck'd then - oh well - probably with kde-5.0 they'll move to mercurial... - anyway - lol - what about the kde-* ones? should we change our metas? - kde-baseapps kde-runtime kde-workspace - What's the name of the repos? - the same - personally i'd prefer sticking to the repos name - and tarballs name of course - in that case it would make sense - unless they decide to rename -it again - no they won't - we could perhaps wait for next beta release, just to be sure ;) - sure - of course, that means we'll have to check for `has_version -kde-base/kdebase-runtime-meta || has_version kde-base/kde-runtime-meta` -everywhere - i think we covered all the monolithic/not converted yet tarballs -so far - yes - it is a major change - at this point I don't think krosspython will be fixed on this -release (Dirk already said a kdepim issue would have to wait for next release) - ok - so, what about kate? - it should be working now ---> ni1s (~ni1s@1-1-4-36a.dre.sth.bostream.se) has joined #gentoo-meetings - do you also fix the 4.7 lives? -<-- ni1s (~ni1s@1-1-4-36a.dre.sth.bostream.se) has left #gentoo-meetings - I actually forgot to test it on my test box :\ - I started by touching 4.6.80. I think ABCD and alexxy applied -the changes to 9999 now - I don't know anything about 4.7.9999 - there is no 4.7.9999 yet - because upstream hasn't branched - lol? - they tagged from master? - yeah -- just like they usually do for the betas :) - ok that sucks - so, how's 9999 then? - alexxy probably knows best - 9999 is fine -- I forward ported most of the -4.6.80 changes so that we -can bump 4.6.85 (or whatever) from 9999 -- note that okular-4.6.85 will be -coming from its own tarball, not the "monolithic" kdegraphics-4.6.*.tarball - (or it should be -- they just finished that split) - great, thanks - speaking of kdegraphics - so, anything else on monolithiks/no migrated yet - heh. also i think we can drop eclass foo from all :live tarballs - before proceeding to the splitted/migrated ones? - the kdegraphics libs are tagged from the same branch as the ones -distributed with digikam - since we now know how they will be packaged - alexxy: the if blocks? - meaning with 4.7 the incompatibilities will go away - sure, I already did it for 4.6.80 ebuilds - yeah - so we should do it for :live - ABCD: did you push those changes to 9999? - alexxy: already done -- 4.6.9999 keeps it, though - jmbsvicetto: yeah - also i'm going to make universal ebuild for kde-l10n (that should -support :live and regular tarballs) - good - dilfridge: yours - ? - you were saying that kdegraphics... - fyi, if/when slotting gets dropped, 4.x.9999 will become something like -4.x.49.9999 to keep versions in order - the kdegraphics libs are tagged from the same branch as the ones -distributed with digikam - so our problems with digikam will go away - cool - ABCD: what do you mean? - slotmove everything back to 0? - tampakrap: yeah - are you crazy?? - not 4? - tampakrap: that would seem to be the goal of dropping the -slotting - i don't see a reason to do that - i think it makes sense - the main reason we had slots to begin with was +kdeprefix -- kdeprefix -will be gone as of Monday next week - dilfridge: if we want to drop kdeprefix, we should drop the -slots - jmbsvicetto: yes that is what I mean - we should definitely drop the slots - yeah, but 4.x.49.9999 doesn't - dilfridge: I don't know if we should use :0 or :4 :) - 0 or 4 is all the same - and why are slot 4 so bad? - not when 5 comes along :) -<-- devurandom (~devu@unaffiliated/devurandom) has left #gentoo-meetings - then you admit to introduce kdeprefix later? :P - 4.x.49.9999 makes actually a lot of sense - tampakrap: 4.x.11 < 4.x.49.9999 < 4.x.80 (4.{x+1} beta 1) - 4.x.80 (4.{x+1} beta 1) < 4.x.9999, which means that portage would see -it as a downgrade - what is the big problem with slot 4 anyway? - yes, 4.x.49.9999 sounds good, even though we could argue that -4.x.49 would be the same - i don't understand - jmbsvicetto: given the differences between kde-3 and kde-4, I -would not rule anything out with kde-5 - tampakrap: I don't have a problem with slot 4. I'm just saying -that have slot=4 or slot=0 is all the same for the PMs - tampakrap: the idea is to get the versions in some sort of order, such -that 4.x.y, where y < 50 is KDE 4.x, and 4.x.y where y > 50 is KDE 4.{x+1} - ABCD: I agree, but as I said, 4.x.49 would be as good as -4.x.49.9999 - there should never be any 4.x.49 release - or they'll have to -modify their release numbers ;) - except at some point maybe someone will introduce a 9999-magic in -portage... - jmbsvicetto: 4.x.49.9999 makes it a bit more obvious that it's live -(and I think at least one PM assumes that it can't be a live ebuild if it -doesn't have "9999" in the version) - and the 9999 use is a "design" option, not a requirement - repoman does that similarly - PMS doesn't acknowledge 9999 as special, afaik - repoman is based on eclass inheritance, iirc - I think paludis does (I remember hearing something about that) - I know portage uses inherit() to determine what "live" is - in any case I don't have anything against 4.x.49.9999 - ok - i must admit i still don't understand - I just fell 4.x.49 is smaller and if it works as well (which I -think it should) we may want to use that - but since the rest of the team does, i step aside - tampakrap: what part don't you understand? - tampakrap: what don't you understand? The ordering? - 1) why slotmove a million ebuilds to 0 again 2) what is 49? - tampakrap: why slotmove? it makes upgrading *much* easier (no more -nasty blockers) - well i think we still should have slots =) - please no slots anymore - ok - it makes life so much simpler and without kdeprefix there is no -real reason for it - there will be kde5 next year - not sure - so we should have at least one slot - tampakrap: as we're dropping kdeprefix, there won't be any more -reason to have different slots for each version - yes, that's ok - I'd go for "move everything to 4" - +1 - 2) what is 49? It's less than 50, which is the arbitrary cutoff used to -determine if 4.x.y is part of KDE SC 4.x or KDE SC 4.{x+1} - tampakrap: and if we put all packages in the same slot, we can -simplify the eclasses - ok - about slot=0 or slot=4, that is something that only has meaning -to humans, not to the PM - put everything to 4 then? - quick vote - 0 or 4 - whatever slot you want to use - +1 for :4 slot - 4 - 4 --*- ABCD doesn't care - I can live with both. 0 would be more "accurate" if we don't -want to have kdeprefix anymore, 4 otherwise - i don't intend to slotmove all the kde-misc ebuilds again - by dropping slots, we need to update all deps to use versions -and not slots - and we won't have kdeprefix (the actual flag might live for a short -while longer, but if it does, it will just be to do pkg_setup() { use -kdeprefix && die ....; ....; }) - jmbsvicetto: they already do -- except when USE=kdeprefix - ABCD: about 49, since 4.x.80 are 4.x+1, why not just use this? - and deal with an extra number? --*- ABCD isn't sure what you're trying to say, tampakrap - tampakrap: the idea is that the first release KDE will ever do -of a new version is 4.x.50 - that's what they've written in their release "rules" - yes, but the tarballs are shown after 4.x.80 - before that there is only live ebuilds - sure, but since 4.x.50 is a new version, 4.x.49 should be used -as the last version of a version - tampakrap: they've released tarballs for alphas before, with lower -numbers - they won't anymore though - bah, terrible language :\ - they said that interested parties can get the tarballs from -redmine or gitweb - tampakrap: why take the chance? - i don't think there is a chance here but anyway - 49 it is - tampakrap: 4.x.50 should never be used for version 4.x - -recently the most they've been getting is 4.x.7 anyway, right? - true - anyway, i think we all agree here - and 49 is just an arbitrary number that is definitely between the last -4.x release but before the first 4.{x+1} release (and I've hardcoded the -4.x.50 assumption in other places) - ok - next - the "50 limit" is already in the eclass - jmbsvicetto / alexxy status of migrated/ split modules? - yeah - do we follow upstream there? should we? - besides the missing krosspython, everything else should be -working - I think we should - (follow upstream) - actualy most of migrated and splited modules has same spliting as we -do - on 4.6.80 we're already doing it - one by one - kde edu, check? - https://projects.kde.org/projects/kde - kdeedu we are 100% following upstream - kde graphics, check? - the split on our end is complete - for both - kde base - kdegraphics, they didn't finish splitting in time for 4.6.80, but -should be done for 4.6.85 - (we might want to package the new mobipocket repo, though -- I'll look -into that) - kdebase is consisted of three monolithic and two split repos as i -see - so we're fine here -- {Day changed to Fri Jun 3 00:00:00 2011} - plus one more (kinda) monolithic repo: kate :D - kwrite moved from kde-baseapps to kate - kdepim/kdepim-runtime is monolithic, check - yeah - how are we on that area? - tampakrap: they may split it - kate/kwrite i mean - kdepim is NOT going to get split - and nothing that migrated is going to change - kdepimlibs/kdelibs are monolithic on both sides - last question: - is the bump ready from our side? - should i announce it? update docs? - bump of what? - 4.6.80 - in general - tampakrap: we should run more tests and still need to fix some -stuff - tampakrap: its NOT ready - what's missing please? - tampakrap: upstream to release a kross-interpreters tarball :D - if you speak now you may get more help :P - yeah, apart from that :) - kdebindings - =) - kdebase + kdegraphics + kdemultimedia + kdenetwork + kdeedu + -kdegames + kdetoys + (most of) kdeutils, should work - afaik kdebindings is broken. I don't know kdepim status - assuming that you disable anything that needs krosspython (pykde4 -probably should work, I would think) - ok, so i suppose i should not recommend people to update to it at -all - pykde4 build on my test system. I haven't tested it though - jmbsvicetto: kdepim should work - not at this stage - I'd wait for a krosspython release (probably next beta) - ok, so what's needed from our side? - tampakrap: for the above list, I can say my testing system is -running. I'm not using too many kde apps on it though - I'm using it mostly as a build box, some browsing (FF), kwrite, -kopete and general DE use - cool - thank you guys for handling it - good job - I haen't tested the games or kdeedu apps yet - i don't have to say anything else on 4.7, if anyone has to say -something speak now - sorry for the commit noise, but I'm a "old grumpy" dev ;) - we'll kick your ass later - dilfridge: next topics are yours - ho hum - use flag defaults for kde subprofile (bug 365251) - tampakrap: https://bugs.gentoo.org/365251 "Use flag defaults for -the desktop/kde profile"; Gentoo Linux, KDE; CONF; dilfridge:kde - ok... all that I listed were (as far as I remember) not in the -desktop profile - maybe we just go quickly through use-flags and vote whether they -should be enabled in the kde profile (NOT forced of course) - 1) cups - I think this is a clear usability improvement - isn't the system-config printer broken? - and hardmasked? - eww - possibly - as I stated when the kde profile was created, I don't like the -idea too much, but as I don't use it, I don't care - cups: no - we'll come back to that topic later ("open floor") - ok - 2) dri, xcomposite, xinerama - +1 - since kwin heavily relies on all that stuff - 3) -gnome - no - this is to avoid problems like the recent glib-networking desaster - don't need it -- I don't think desktop/ sets +gnome anyway :) - ok then not - true - 4) nsplugin - since konqueror provides a plugin container - no opinion - no strong opinion here either, so maybe lets forget about it - 5) semantic-desktop :) - yes! - as it is needed by kdepim - 6) xscreensaver - to provide more eyecandy - +1 - opengl - gles - -1 on gles, I think - (unless I'm mistaken) - opengl +1, gles -1 - as I thought that gles was primarily for embedded, or something like -that - but +1 on opengl - kwin will work with it better then with opengl - opengl is already in desktop - there we go :) - if you use gallium drivers - that's not a reason to force it in every kde user - ok that's it for me on this topic, I summarize: - these are defaults, not forced :) - we add the following flags to the default use flags in the kde -subprofile: - wait i want more - ok - qt, qt4 - qt4 is in desktop - qt? - not - qt is old apparently - declarative - yes - kipi - yes - phonon? - is that enabled already? - no - we should add it - ok - and qt3support? - is this being dropped by upstream? - in desktop - i know - if it's being dropped of 4.7 we should consider dropping it from -desktop - good question, I know they are working in that direction - ah and plasma - is that enabled? - no, I'll add it to the list. qt3support maybe worth a mail to the -releaseteam - ok - that's all - "declarative dri kipi phonon plasma semantic-desktop xcomposite -xinerama xscreensaver" - ^ any further comments? - ok then with your ok I'll add this later to the profile - no, i want to announce it first - ah ok - fine - anything else? - next topic would be kdeprefix status - we already discussed it i suppose - yes - ok next... - kde-4.6.3 - should be fine, i don't see bugs :) - I would like to file a stablereq in a week or so (30days etc), -just so stable keeps up - bug reports that is - ok... if there are any problems or if you have any objections, -talk to me please :) - that's all? - from the agenda, yes - *) open floor - open floor- one point from me - shoot - i was kind of crazy enough to mail tgurr about cups-1.4 -stabilization - basically I can go ahead sorting the remaining bugs etc - this may take some time, but at some point I hope we'll have some -news there - that's all - ok - and one point from me: - we lost scarabeus, we need new people - i mean, what comes next? losing jmbsvicetto? --*- jmbsvicetto slips away - we should all move on to qa and recruit diego for kde :D - actually, he was a kde guy long ago - did not know that - tampakrap: all I can say about that is that I'm trying to use my -council hat to ensure we fix the issues that affected Tomas motivation - Diego and Dan Armak started kde on Gentoo, I think - if not, they maintained kde on gentoo for many years - we need scarabeus and ssuominen back - at this point and unless people change, that seems unlikely - btw, meeting closed, thanks for coming diff --git a/meeting-logs/kde-project-meeting-log-20110831.txt b/meeting-logs/kde-project-meeting-log-20110831.txt deleted file mode 100644 index b935c55..0000000 --- a/meeting-logs/kde-project-meeting-log-20110831.txt +++ /dev/null @@ -1,479 +0,0 @@ -[00:13:23] !herd kde -[00:13:23] (kde) abcd, alexxy, dilfridge, jmbsvicetto, mschiff, patrick, reavertm, spatz, tampakrap, thev00d00 -[00:13:28] meeting start -[00:13:32] First topic: KDE 4.7.0 stabilization (without kdepim) -[00:13:43] +1 -[00:13:45] +1 -[00:13:45] dilfridge: reason to do so? we usually stabilize after the .0 release -[00:13:50] no bugs -[00:13:57] fyi i object, i have plenty -[00:14:04] the upgrade went perfectly smooth here -[00:14:34] and there are also no significand new things on bugzi -[00:14:35] tampakrap: I haven't hit any more bugs than usual -[00:14:39] but bugs is a general problem of kde not only 4.7.0, I am running 4.7.49.9999 here -[00:14:42] fwiw kdepim works fine here as well, why don't we stabilize this one as well? -[00:14:53] maybe with .2 ` -[00:14:55] ? -[00:15:09] I'll leave kdepim for those of you that actually use it :P -[00:15:18] i use kdepim-4.4 -[00:15:28] kdepim 4.4 is obsolete, no bugfixes, no security updates -[00:15:29] kdepim is special: I think there the newest version is better these days -[00:15:35] can't we keep them both and just notify users? -[00:15:39] sure -[00:15:40] and let them decide on what they want -[00:15:41] (speaking of the *2 versions) -[00:15:56] but i still object on stabilizing .0, i have some plasma regressions -[00:16:04] like? -[00:16:08] and of course we don't get such bugs, since they are upstream -[00:16:17] i have problem on focus -[00:16:17] I guess .1 is not far away right? -[00:16:24] has there ever been a version without plasma regressions? -[00:16:31] another i have is that taskbar entries are not highlighted correctly -[00:16:32] tagging tomorrow, technically -[00:16:44] release sept 6 isnt it? -[00:16:50] I have som eprobs here too: a windows that had a notify, tends to keep that status in the window bar -[00:17:04] but maybe messed up because of 2 migratet categories -[00:17:22] ok -[00:17:26] so -[00:17:29] mschiff: I have the same, sticky red quassel for example -[00:17:39] consensus seems to be more, stabilize 4.7.1 -[00:17:41] my opinion is to stabilize .1 (after a meeting decision) WITH kdepim -[00:17:46] Thev00d00: exactly, I think its what tampakrap also meant -[00:17:52] but let the users know first -[00:17:59] document everything etc -[00:18:08] news item maybe -[00:18:08] maybe even put a news item out as well -[00:18:20] ok fine with me -[00:18:29] +1 for .1 with pim -[00:18:38] anyone else? -[00:18:53] But 4.4 should stay in tree for some time -[00:18:58] yes -[00:19:07] I'll take care of it as good as possible -[00:19:15] +1 for .1 -[00:19:24] ok -[00:19:32] then -[00:19:34] ok, prepare a news item, and take care of the documentation then, and after next month's meeting we'll decide on 4.7.1 -[00:19:48] anything else? -[00:20:05] so not stabilize .1 as its available? -[00:20:11] next topic then -[00:20:28] no, after meeting -[00:20:36] tampakrap: I'd try to decide the stabilization by email -[00:20:53] no problem -[00:20:54] mschiff: at earliest 30days after release, so we have lots of time -[00:21:02] anyway, next topic -[00:21:06] 2) Road towards KDE 5 - what news is there from the Desktop Summit? -[00:21:16] who was at the Desktop Summit? -[00:21:20] ah that was me!! -[00:21:21] you -[00:21:44] so, i learned there that Qt 4.8 is NOT going to be split -[00:21:51] Qt 5 will -[00:21:58] into what? -[00:22:03] and we have plenty of time to worry about KDE 5 -[00:22:09] into small parts -[00:22:10] =) -[00:22:14] even atoms -[00:22:22] even Thiago didn't tell me details -[00:22:26] oh dear, radiation alert -[00:22:29] I'd *really* like split tarballs -[00:22:36] tampakrap: is there any eta for kde5? -[00:22:39] a 200M download when you need 10M is a bit sad -[00:22:46] about a year or so? -[00:22:51] not yet, but we have plenty of time -[00:22:52] work started in kdelibs -[00:23:00] framework branch -[00:23:07] and they won't do big changes like the 3->4 transition -[00:23:41] that's what some core KDE developers (like Aaron Seigo and David Faure) said in their presentation -[00:23:59] will there be a kde 4.8? -[00:24:03] yes -[00:24:11] but Alex has been talking about using the bump to get some ABI incompatible changes -[00:24:31] also seems something is going to happen with nepomuk -[00:24:33] that has been mentioned multiple times in the release ml -[00:24:37] that was the plan, it changed somewhere in the middle -[00:24:45] hmm -[00:24:52] unless you are talking about something else -[00:25:15] I heard some rumour about kdelibs basically remaining at 4.7? -[00:25:46] i also took part in a release team BoF along with Slackware, Fedora, openSUSE packagers and a GNOME release team guy -[00:25:58] chaired by Sebastian Krugler and Dirk Muller -[00:25:59] Alex also worked on getting all KDE cmake files that were ok for kitware into 4.8.0 (?) and created the new cmake-extras packages -[00:26:02] package* -[00:26:20] they talked about the splitting of modules, how to handle it and about future KDE releases -[00:26:28] dilfridge: They've been saying there won't be a kdelibs-4.8 -[00:26:36] ok -[00:26:41] so nothing big is expected -[00:27:04] are you talking about the superbuild package? -[00:27:20] No, that was their "reply" to slackware -[00:27:46] no idea what you're talking about then -[00:27:57] afaik there will be kdelibs 4.8 and KDE SC 4.8 -[00:27:59] The cmake-extras package is a package that Alex has "sponsored" to have all cmake files that can't be accepted into cmake by kitware -[00:28:09] ah yes -[00:28:13] i recall now -[00:28:18] tampakrap: that's not what has been talked in the kde relase ml -[00:28:21] what does have to do with us? -[00:28:21] Alex ? -[00:28:33] but I haven't talked to anyone about this nor was I at the Desktop summit :P -[00:28:33] Alexander Neundorf, main buildsystem guy -[00:28:35] ah -[00:28:50] i follow the kde release team, never saw such thing :/ -[00:29:15] tampakrap: What I'm saying is that they've talked about doing incompatible changes. I hear from you that is not what they're going to do -[00:29:36] they were, but things changed in Qt, thus in KDE -[00:29:42] that's what i know so far -[00:30:13] but they had also decided on not having KDE/ branches and just branches and now in the kde-scm ml they're almost reverting that because of the talks other KDE devs had on kde-core-devel that appearantly didn't follow the kde-release or kde-scm mls -[00:30:27] tampakrap: ok -[00:30:49] anyway -[00:31:03] if big changes are going to come we'll know them in time -[00:31:07] we always did -[00:31:08] true -[00:31:44] https://plus.google.com/photos/116381667574498856310/albums/5637225108859383905 <-- and here are the photos for those who haven't seen them, to make you jealous -[00:31:50] :D -[00:31:59] anything else here? -[00:32:12] not from me -[00:32:29] or me -[00:32:57] ok -[00:32:57] 3) The NetworkManager-0.9 mess -[00:33:03] hehe -[00:33:05] no idea here -[00:33:09] the basic summary is -[00:33:23] A gnome-3 requires networkmanager-0.9 -[00:33:37] B kde does not support networkmanager-0.9 -[00:33:52] A seems to be set in stone -[00:33:57] dilfridge: knetworkmanager works fine with nm09 -[00:34:04] B is being worked on -[00:34:07] yes -[00:34:14] and i use this combination on my laptop -[00:34:16] dilfridge: wasn't the delay on solid? -[00:34:27] also in git master of kdelibs there is a stub for nm09 -[00:34:33] for solid -[00:34:38] what alexxy is using and what we have in the tree now is the nm09 branch -[00:34:38] I don't use knetworkmanager, nor networkmanager, so I don't know anything about it -[00:35:00] that is basically sponsored by fedora, as they have the same problem -[00:35:04] and it seems to work ok -[00:35:13] it mostly works -[00:35:16] excetp wimax -[00:35:17] =) -[00:35:34] so my cell modem and wifi + vpn works fine -[00:35:43] didn't someone put a masked knetworkmanager 0.9 compatible in tree? -[00:35:46] the only problem with it is that the knetworkmanager developers do not really support it but have different plans (or lack of motivation) -[00:35:52] tampakrap: yes me -[00:36:04] basically it is a fedora-fork -[00:36:09] dilfridge: no -[00:36:15] its different approcah -[00:36:30] fedora has patched nm09 with nm08 compatibility layer -[00:36:41] nm or knm? -[00:36:46] nm -[00:36:52] knetworkmanager developers were in summit, why didn't you tell me earlier to talk to them? :/ -[00:36:53] strange -[00:36:59] anyway -[00:37:01] and its own patched version of knm -[00:37:21] oh dear :-/ -[00:37:21] probably the best thing is to just stick to the nm09 branch -[00:37:23] there 3 impletation of nm09 support in knm -[00:37:34] first one is fedora -[00:37:45] second nm09 branch from knm devs -[00:37:52] and third libqtnm -[00:38:00] that is worked on -[00:38:08] we use second one -[00:38:15] since its only working -[00:38:15] what's libqtnm? -[00:38:34] i dont remember how its called correctly -[00:38:40] anyway -[00:38:45] but they want to create qt lib fro nm -[00:38:45] alexxy: shall we continue using nm09 branch, what do you think? -[00:38:45] since it works, and it is in tree -[00:38:49] what is the problem? -[00:39:02] tampakrap: there is no real problem -[00:39:08] dilfridge: i think that it will be best chois at this time -[00:39:25] the purpose was only to make people aware that this may become problem at some time -[00:39:34] but right now I agree with alexxy -[00:39:42] summarize the problem please, i'm confused -[00:39:59] dilfridge: there will be no problems with migration -[00:40:09] since nm settings are stored by nm -[00:40:10] chaotic situation, many different approaches, no clear upstream -[00:40:15] and not by applet -[00:40:47] alexxy: ok -[00:40:53] so summary: no problem -[00:40:57] :D -[00:40:57] but we have something that works at the moment, so let's just wait for upstream to fix their mess -[00:41:13] ok -[00:41:16] next point? -[00:41:18] next issue -[00:41:31] meh it's me again -[00:41:34] 4) Does anyone still have an overview of the glib-networking/libproxy problem? -[00:42:05] pacho was quite insistent that we have a look at this -[00:42:15] because it blocks a big fat sec bug -[00:42:58] i don't use that app at all -[00:43:49] it's pulled in eg by firefox -[00:44:15] I went through the >100 comments and tried to make sense of it yesterday -[00:44:20] dilfridge: I can't help as I don't use it as well -[00:44:30] I never had the problem myself either -[00:44:34] which flag in firefox? -[00:44:45] dont remember sorry -[00:44:57] a guy put a summary there did you look at it? -[00:45:14] yes, me :]... I *believe* the problem is fixed -[00:45:22] but believing = not knowing -[00:45:31] does anyone else know anything? -[00:45:54] I do not have it installed -[00:45:58] I recommend the gnome guys just go ahead... -[00:46:04] any dupes? any activity in the bug? -[00:46:21] not anymore for a while (that's why I think it's ok now) -[00:46:42] go on then -[00:46:56] ok I'll tell them to just go ahead -[00:47:08] next topic -[00:47:21] 5) Suggestion - splitting the Gentoo KDE Guide into two pages -[00:47:21] 1) main page: main tree, stable and ~arch things only -[00:47:21] 2) poweruser page: overlay, live ebuilds, sets, kde-sunset -[00:47:31] who added this topic? -[00:47:33] my suggestion -[00:47:38] and I'd be willing to do it -[00:47:45] but only if you think it's good -[00:47:47] that's a no :) -[00:48:02] from the very beginning i wanted that guide to be monolithic -[00:48:14] else there will be a lot of duplication -[00:48:40] plus readers will be able to jump from one topic to another (eg see the existence of the overlay quickly, and maybe prefer the live ebuilds or snapshots) -[00:49:01] there are tags there as well, append #kde4_6 and similar -[00:49:02] I think it should always be clear what the guides refers to: ~arch or stable -[00:49:11] it is -[00:49:45] -*- dilfridge is slightly distracted by some dirndls walking past the window -[00:49:47] people don't go by branch, they go by KDE version -[00:50:39] anyway, anything else here? -[00:50:42] no -[00:50:48] the guide needs update -[00:51:09] what kind of update? -[00:51:15] hald -[00:51:18] -- -[00:51:23] the removal instructions -[00:51:33] live branches -[00:51:37] not correct -[00:51:52] true, give me a patch :) -[00:52:08] I hald really still being used? -[00:52:15] and maybe some info from the upgrade 4.4 guide -[00:52:24] mschiff: no -[00:52:33] j0hu: are you willing to update it? -[00:52:45] should we kill the upgrade guide and merge some info into the main guide? -[00:52:50] will do after finishing the quizz -[00:53:08] merge info: yes, kill the upgrade guide: not yet -[00:53:31] anything else? -[00:53:50] go ahead -[00:53:59] not here -[00:54:11] 6) Build system architecture bug -[00:54:15] +s -[00:54:24] bug 358059 -[00:54:26] tampakrap: https://bugs.gentoo.org/358059 "cmake-utils.eclass PREFIX is not defined"; Gentoo Linux, Eclasses and Profiles; CONF; meka:kde -[00:54:45] no idea about the consequences -[00:55:02] I was kind of hoping that reavertm would turn up -[00:57:06] if it is defined either way -[00:57:12] why defining it earlier is a problem? -[00:59:02] but wha does the patch kill the /usr default? -[00:59:15] I dont understand problem nor solution -[00:59:28] I only looked at the patch -[00:59:40] mschiff: see line 7 -[01:00:01] I'm more concerned about lines 32/33 -[01:00:29] why suddenly add the prefix at a place where it was not needed before?! -[01:01:20] hm, seems a bit strange to me -[01:01:40] this is wrong indeed -[01:01:44] seems like $libdir must not be set this way -[01:01:46] the rest is fine imho -[01:02:10] if it was set to /usr it will end up in /usr/usr/lib -[01:02:45] ok shall we kill the 32/33 chunk and test the rest in the overlay? -[01:03:03] not sure -[01:03:08] me neither -[01:03:08] we need more eyes indeed -[01:03:19] CC scarabeus and reavertm there and ask them -[01:03:22] I'll try to persuade scarabeus -[01:03:25] yes -[01:03:36] next one -[01:03:44] the rest ist nothing special -[01:03:54] 32/33 is the only real change -[01:04:07] ok -[01:04:09] next -[01:04:13] bug 356681 -[01:04:15] tampakrap: https://bugs.gentoo.org/356681 "Please remove media-libs/phonon dependency from kde-base/kdelibs"; Gentoo Linux, Ebuilds; CONF; hwoarang:kde -[01:04:32] i don't like this one, and i am not willing to work on this -[01:04:45] jmbsvicetto: is it a good solution to create a virtual/phonon? -[01:05:41] I fear that the number of problem sources could explode with more than one implementation :| -[01:05:56] sorry, I was looking at the patch for the previous bug -[01:06:01] YEEEHAH -[01:06:03] can we hide it under a kde flag? -[01:06:09] btw, the only "real change" in there seems to be the following: -[01:06:10] - SET (CMAKE_INSTALL_LIBDIR ${libdir} CACHE PATH "Output directory for libraries") -[01:06:11] ...sorry I missed most of the meeting (I just got back from a family dinner, which I was rudely informed was more important than this :D) -[01:06:11] err sorry -[01:06:13] + SET (CMAKE_INSTALL_LIBDIR ${PREFIX}/${libdir} CACHE PATH "Output directory for libraries") -[01:06:22] -*- dilfridge just read "CURRENT STATUS OF MANUSCRIPT: Editorially approved for publication" -[01:06:53] jmbsvicetto: thats what I was saying -[01:06:57] -*- alexxy still waits for similar resolution from jpcs -[01:06:59] about phonon, are they compatible now? -[01:07:00] and in the eclass: -[01:07:04] # Eclass respects PREFIX variable, though it's not recommended way to set -[01:07:04] # install/lib/bin prefixes. -[01:07:04] # Use -DCMAKE_INSTALL_PREFIX=... CMake variable instead. -[01:07:22] cause qt-phonon was behind phonon for a long time -[01:07:39] no idea about qt-phonon -[01:07:43] and i don't care tbh -[01:07:56] I'll see what I can do about this one -[01:08:14] I still think we should prefer media-libs/phonon to x11-libs/qt-phonon, though -[01:08:15] i'm asking if a virtual is fine, or if we can do this but introduce a kde useflag there so that media-libs/phonon is default -[01:09:03] we could say something like " kde? ( media-libs/phonon ) !kde? ( virtual/phonon ) " -[01:09:17] dilfridge: kdelibs? -[01:09:23] f.ex. -[01:09:31] yes, in other kde apps as well -[01:09:34] if that is possible and even works -[01:09:35] i like it -[01:09:46] dilfridge: if so, how's that any different from the current || ( media-libs/phonon x11-libs/qt-phonon ) ? -[01:09:58] anyone willing to work on these? (virtual/phonon AND qt-phonon for kdelibs) -[01:10:15] with !kde you can run kdelibs also with qt-phonon then -[01:10:20] not me -[01:10:20] a guy with -kde can get qt-phonon -[01:10:22] tampakrap: I'll have to check, but we used to support qt-phonon on kdelibs. We just defaulted to phonon -[01:10:37] I'll work on it -[01:10:45] ok cool -[01:10:46] dilfridge: then someone dropped the old conditional -[01:10:49] ok, have a look at both the virtual and the kde flag -[01:11:10] tampakrap: I don't know if we gain anything with the virtual (for KDE) -[01:11:30] i believe we are -[01:11:41] not only for kdelibs, but for other kde apps -[01:12:00] put virtual/phonon there instead of the conditional you pasted earlier -[01:12:03] seems cleaner -[01:12:20] until you think how to prefer media-libs/phonon over x11-libs/qt-phonon -[01:12:53] that's for kdelibs (solved by the flag) -[01:13:08] other kde or non-kde apps don't need to prefer anything -[01:13:08] I'll look at it and then talk to you -[01:13:13] sure -[01:13:28] bug 332829 -[01:13:30] tampakrap: https://bugs.gentoo.org/332829 "Inconsistency between distro's KDE4WorkspaceConfig.cmake and the actual layout"; Gentoo Linux, Library; CONF; cheepeero:kde -[01:13:50] i talked about it with reavertm, someone needs to work on it -[01:13:54] 99% it will work -[01:14:16] tampakrap: tell me if you need chroot testing -[01:14:33] not sure if anyone wants to do this in his main system first -[01:14:37] i can't work on it, someone else has to do it -[01:14:59] volunteers? -[01:15:08] whats this about? -[01:15:28] the internal configuration of the kde build variables is somehow messed up -[01:15:53] it makes problems for building apps outside portage -[01:16:27] that's about my whole understanding -[01:16:42] so do we have some qt developer in the team? -[01:16:54] dilfridge: that whole deal of building apps outside of portage, is something we should probably talk about again -[01:16:57] oh -[01:17:03] -*- Sput forgot to check this channel -[01:17:07] ABCD: ^^ wanna work on it? -[01:17:20] Sput: do you use kdevelop? -[01:17:23] mschiff: that needs cmake understanding, not Qt -[01:17:33] it is easy to test, there is a patch there already -[01:17:50] when we started with kde-4.X, we were clear that we supported portage and building packages with our ebuilds (we have ebuilds for all releases, snapshots and live) and that we wouldn't bother with supporting people that want to install software outside portage -[01:17:57] I still think that should be our stance -[01:18:06] tampakrap: yeah I meant someone who is gerneally developing something with qt or kde... -[01:18:32] jmbsvicetto: yes but if someone wants to use kdevelop? -[01:18:40] dilfridge: RESO:CANTFIX; KDE4WorkspaceConfig.cmake can only be installed by one package (for hopefully obvious reasons), yet must change when other packages are installed (breaking checksums) :) -[01:19:01] like, use the application to program something? -[01:19:11] dilfridge: if I understand the issue, get upstream to do a release -[01:19:56] dilfridge: if the problem is with testing applications built with kdevelop, I'd say the real issue is cmake -[01:20:00] jmbsvicetto: no, I mean if upstream is using gentoo?! -[01:20:15] dilfridge: I know how much KDE developers hated auto-tools, but this is a price you pay for using cmake -[01:20:37] well... it's not really my problem -[01:20:55] what I could do is feed the patch into a chroot and rebuild kde -[01:21:00] and look at the result -[01:21:09] ok -[01:21:34] do you think that would be enough testing? -[01:21:46] the package is libkworkspace, file is /usr/lib/cmake/KDE4Workspace/KDE4WorkspaceConfig.cmake -[01:21:54] and build kdevelop from source -[01:21:55] dilfridge: I've talked with Diego about the next bug, and even though we shouldn't be setting RPATH to /usr (KDE), if I understood the issue correctly, that alone won't fix the issue as the other applications (kdevelop?) are setting RPATH themselves -[01:22:34] bug 380415 -[01:22:37] dilfridge: https://bugs.gentoo.org/380415 "Qt and KDE libs and plugins should not have an RPATH"; Gentoo Linux, KDE; CONF; realnc:kde -[01:22:49] we could also drop the /usr/qt4 RPATH for QT as it's part of LDPATH -[01:22:56] tampakrap: could this be fixed in qt? -[01:23:04] i can't decide -[01:23:18] hehe agenda topic for next qt meeting -[01:23:27] One issue I talked to Diego but didn't understand is what kind of impact this might have for security -[01:23:27] sure, can you test beforehand? -[01:23:31] -*- dilfridge pushes the pile of papers to the next guy -[01:23:39] just reading backlog... fwiw, I've been using nm09 with knetworkmanager and USE=nm09 for quite a while, it works fine -[01:24:06] if anyone tells me how to disable RPATH in qt, yes -[01:24:27] and there won't be a kdelibs-4.8 release (the master branch is frozen now, and people are working in the frameworks branch) -[01:24:53] The user on that bug seems to want the QT/KDE libs built without RPATH so that if he builds and installs an app in /usr/local and (as I understand it), he adds a plugin to /usr/local the lib will "link" to that plugin - my question is won't that allow having system libs linking to user-controlled paths? That sounds dangerous -[01:25:21] jmbsvicetto: only if they are in LDPATH I guess -[01:25:29] jmbsvicetto: the point with Qt's RPATH of /usr/lib*/qt4 is that the qt team was going to *drop* it from LDPATH as soon as was practical -[01:25:35] The issue is that they are not in LDPATH -[01:25:56] better put, that is the complaint and what Diego was pointing out. If it's not in LDPATH it won't "magically" work -[01:26:00] and if someone is adding a local dir to LDPATH before system dir, that is his own stupidity -[01:26:25] ABCD: understood. That means the request cannot be fulfilled then -[01:26:40] dilfridge: sure -[01:27:04] dilfridge: but what they wanted was the libs to have no rpath so they could "link" to a lib anywhere - that's what sounds dangerous to me -[01:27:22] dilfridge: the default actually puts /usr/local/lib first before everything else (note, /usr/local/lib64 isn't mentioned until after /lib64 and /usr/lib64) -[01:27:32] dilfridge: and I don't use KDevelop at the moment -[01:27:39] dilfridge: even though, from what Diego told me, that won't work as without RPATH the system will only look under LDPATH -[01:27:39] /usr/local/lib is still root:root -[01:27:41] see /etc/env.d/00basic -[01:27:49] true :) -[01:28:44] ok I guess this is effectively going to be decided by the qt team -[01:28:48] so I don't know enough about this, but hope any change we do won't open any unwanted "doors" -[01:29:47] any more thoughts about this? -[01:29:52] dilfridge / tampakrap: No comments or objections from me to the next 2 (final) items -[01:30:42] the last two items are the simple ones -[01:30:51] no objections from me either -[01:31:16] my opinion: a) add libXkbfile globally, b) remove the useflag -[01:31:43] yes and yes -[01:31:43] do the libs/progs with RPATH set also have RUNPATH set? If so, then LD_LIBRARY_PATH overrides it anyway, so... :D -[01:32:56] (I think cmake uses the proper ld(1) options that make the linker set DT_RPATH *and* DT_RUNPATH) -[01:32:56] as for the Qt5/KDE5 thingy: Qt5 will be released next spring or so, KDE will take longer... work on kdelibs is going on in the framework branch -[01:33:04] >:| -[01:33:24] we need the qt herd to provide us with Qt5 ebuilds soonish (and I hope the eclasses still support proper slotting) -[01:33:44] I think some eclass magic is needed to make kdefoo 4.8 depend on kdelibs >= 4.7.0 -[01:33:48] Sput: argh... which gets back to the last issue -[01:33:48] Sput: i thought frameworks is going to be kdelibs 4.8 -[01:33:55] ABCD: yes but that is doable -[01:34:01] tampakrap: no, frameworks is not going to be 4.8 -[01:34:10] there won't be a kdelibs-4.8 -[01:34:10] dilfridge: that is "I think I'm going to have to write some eclass magic ..." -[01:34:12] and what is it going to be then? -[01:34:46] ABCD: or fakebump kdelibs to 4.8 :) -[01:34:51] well, probably what we call "KDE 5" although I'm sure the KDE promo team is going to come up with yet another naming scheme in time :P -[01:34:54] tampakrap: too much work :D -[01:35:07] Sput: there is no KDE 4, so how could there be a KDE 5? :) -[01:35:11] Sput: indeed -[01:35:18] ok let's wait then -[01:35:22] KDE is a community, you can't attach a version number to something like that :) -[01:35:22] ABCD: exactly -[01:35:22] Bulshytt! -[01:35:26] tampakrap: that's why last time there was a talk on #-kde about this I said we were going to have some fun like in the early KDE-4 days -[01:35:56] the frameworks branch ist going to be the next incarnation of kdelibs, currently they work on reorganizing/cleaning up/splitting kdelibs, as soon as Qt5 is released they'll port it over -[01:36:01] tampakrap: we're going to have kde-4.8 depending on kdelibs-4.7 and we may even have kdeA-4.8, kdeB-4.9, etc -[01:36:03] the rest of KDE will follow suit only later -[01:36:28] jmbsvicetto: that's only assumptions, just wait for the release -[01:36:29] if upstream slots things properly, I think we should slot; otherwise everything goes in :4 (which we might want to make :0 instead :D) -[01:36:37] there will be more kdelibs-4.7.x releases, but I don't think a 4.8 ever unless they changed plans again -[01:36:50] ABCD: nononono, what with :4 and :5 then? :O -[01:37:11] we certainly will have to slot Qt versions -[01:37:14] -*- dilfridge thinks we cannot really predict the upcoming chaos -[01:37:16] ABCD: no gain in moving to :0 again -[01:37:17] not sure about KDE -[01:37:26] ABCD: besides, don't forget some people still use kde-3.5 ;) -[01:37:44] Enable auto-destruct sequence -[01:37:50] Sput: qt is slot 4, isn't that sufficient? -[01:38:05] some people dont know how to remove 3.5 :P -[01:38:05] tampakrap: it is, if slotting still works in the eclasses -[01:38:26] it is, why shouldn't it? :) -[01:38:35] anyway, people, don't panic -[01:38:43] tampakrap: well, we've removed proper slotting support from the KDE eclasses -[01:38:48] who knows what the qt herd did :) -[01:38:51] you are all making assumptions here, just wait for the next release to show up -[01:38:55] tampakrap: because it hasn't been tested in a long time ;) -[01:39:06] lol -[01:39:15] tampakrap: well, Qt5 is already under development (and I will start working with it in a few days), I'd love to be able to install it into Gentoo -[01:39:23] (without removing qt4 obviously) -[01:39:46] Sput: unless we get ABI deps, I suspect you're going to have *great* pain trying that -[01:40:07] true, nothing's going to be so smooth for sure -[01:40:09] unless every binary sets the correct RPATH :P -[01:40:14] major versions ahead, red flag -[01:40:34] jmbsvicetto: well, used to be the case that just calling the correct qmake version would set everything up correctly... -[01:41:01] this is going nowhere -[01:41:02] I'm just saying, we need to be aware of Qt5 being right around the corner already -[01:41:06] let's just wait and see -[01:41:12] it's not something that'll hit us in a few years -[01:41:18] tampakrap: no need for anyone to stuck his head in the ground, but it's probably wise to look over the ship's border in case a huge wave rocks the boat ;) -[01:41:20] dilfridge: this is open floor, of course it's not going nowhere :) -[01:41:33] -*- dilfridge gets himself a drink -[01:41:39] -*- Sput has a beer -[01:41:49] -*- tampakrap drunk his already -[01:41:52] meetings are long, eh :) -[01:41:57] -*- Sput has moar in the fridge -[01:41:58] and btw, MEETING IS OFF -[01:42:08] summary tomorrow diff --git a/meeting-logs/kde-project-meeting-log-20120116.txt b/meeting-logs/kde-project-meeting-log-20120116.txt deleted file mode 100644 index aa6bc0d..0000000 --- a/meeting-logs/kde-project-meeting-log-20120116.txt +++ /dev/null @@ -1,630 +0,0 @@ - meeting starts now - roll call again please: alexxy / ABCD / jmbsvicetto / dilfridge / -johu / mschiff / Thev00d00 --*- johu here - here --*- alexxy here --*- alexxy here again and again =D - here --*- alexxy like quantum particle here and not here with non zero probability - first topic: elect new lead - nominations? --*- johu nominates tampakrap - Do we really want to do it at this meeting? - raise your complain please - Nothing prevent us to anticipate the election, but that means -the 2011 term had only 11 months and that for the future the election will -happen before FOSDEM - we could vote whether we want to vote - or we could just vote by acclamation at fosdem :D - When dilfridge mentioned this topic at IRC, I got the impression -the point was to talk about the election, not to have it today - i dont care, maybe I just misunderstood - me dont care too - If no one has any reason to do it today, I'd have us wait 3 -weeks - lead is bad for your health anyway - ok, skipped for next meeting - you guys can pick Theo at FOSDEM and then we can do a mail tally -just to record it - hehe - he he - next topic --*- alexxy seems like cannot participate fosdem this year - As in the past, I'll keep abstaining from kdepim issues :P - What shall we do with kdepim-4.4 (15 minutes) - * Discuss/vote: At the moment KDEpim-4.4 is still fully -functional, no known - regressions. Functionality of KDEpim-4.7 is slowly stabilizing, -with occasional - pains. Do we want to keep KDEpim-4.4 in the main tree? - dilfridge: yours - well... - I'm happy with how it is now - means, keep 4.4 for the moment, but also keep stabilizing newer -4.[78] versions - i dont care about kdepim 4.4 as long its work we can maintain it - right - at the moment it's zero work - to maintain it - it's just about giving people a choice - It's up to you, but if that's what you think, I see no reason to -change the status quo - if it's zero work, why remove it then? - a note from upstream they want to change migration to import ... - rumors - if this feature will come we can think about removing - hmm? - dilfridge: how about use kde-4.[78] kde-l10n for old kdepim-4.4? - you'll have to explain why... - to not keep separate kdepim-l10n - alexxy: this doesnt work as i know - it partly works, some translations are broken afterwards - alexxy: I don't think that'll work - alexxy: the l10n of kdepim-4.4 and kdepim-4.7 is not compatible - well then we should add kdepim-l10n to rdeps then - and its not much work to create the kdepim-l10n - ok =) - good - any additions? - then we should add kdepim-l10n to rdeps for all kdepim packages - final resolution: we keep it there, we'll have to create l10n -though - to make it pull kdepim-l10n - alexxy: wasn't there a kdepim-base package? - alexxy: that could be added there - sorry very late guys, reading backlog - Or did that become kdepimlibs? - kdepim-meta pulls kdepim-l10n with nls useflag - http://paste.pocoo.org/show/535829/ - same as kde-meta pulls kde-l10n with nls useflag - dilfridge: i have this flag - can we make that nls flag global in kde packages then? - and i dont have kdepim-l10n installed - ok - tampakrap: why make it a use flag for all packages? - i mean, global like semantic-desktop, put it in every kde package - alexxy: we'll sort this out - because i for example want only konsole and am an xfce user - tampakrap: I'd try to add it to a base package - like kdelibs -for non-pim packages - but i also want translations of konsole - or that, kdelibs is also acceptable - he he =) - +1 for tampakrap - alexxy: thanks :P - +1 from me - dilfridge / jmbsvicetto: nls in kdelibs, acceptable? - we could do the following: have the eclass add kde-l10n and if -needed kdepim-l10n to rdeps if any lingua is set - tampakrap: yes but that does not solve the kdepim-l10n problem - adding the rdep in the eclass is better - tampakrap: that's what I suggested :P - dilfridge: rdep via use flag - =) - =D - ok fine, add useflag to all kde packages: if "nls" is set, pull -*-l10n - dilfridge: Is there no base kdepim package that we could do the -same as in kdelibs? - no, unfortunately not - Please don't add it to all kde packages - Why do we want a use flag to all packages when all it does is -pull one dep? - kdepimlibs would be a candidate, but it's not really used by all -afaik - well - It would make sense to add it to all packages if the packages -tarballs add the l10n stuff and we could enable/disable for each package - kdepimlibs is separate from kdepim - err - sorry - libkdepim - yes, that works - Don't all kdepim packages depend on libkdepim? - so, kdelibs for kde-l10n and libkdepim for kdepim-l10n, -acceptable? - let's try that, yes. - s/add/had/ - tampakrap: yes - alexxy / johu ^^ - tampakrap: yep - good, i'll do it - excellent. - actually, i'll assign it to a non-dev to do it - :D - for practice - he he - for idella4? - anything else here? - he is very active - =) - no, i have a list of interested people, don't worry - he is indeed - =) - never mind - anything else here? - next topic: - 4. kdeenablefinal revisited (15 minutes) - * Discuss/vote: See last test run bug #353246. Should we -provide this - feature anymore? What is the purpose nowadays, in fact of -upstream keep - going split the huge packages (kde frameworks, kdepim)? --*- johu had a kernel panic :-/ - dilfridge: ^^ yours again - not mine - no its mine - i want get rid of this mess - well, add your names next to the topic next time people - tampakrap: https://bugs.gentoo.org/353246 "[Tracker] -kdeenablefinal build failures"; Gentoo Linux, KDE; CONF; dilfridge:kde - tampakrap: last time we agreed to let it be as esigra was doing -all the work and we just left the bugs alone ;) - tampakrap: is it still works? - or do we still need this - upstream do not maintain it active - and it seams only one user uses it - most upstream devs don't even know about its existance - and i do not see the purpose - tampakrap: I still have no interest in it and won't shed any -tears if we drop it --*- dilfridge does not care either way - but anyway, it doesn't make much sense that now most packages are -split in separate git repos - so lets kill it - =) - yes! - like we did for kdeprefix - =) - ok, do it - thanks --*- Thev00d00 woops - hehe - anything else? --*- dilfridge wants to close the bugs - ok will purge it tomorrow - and closes the bugs as well - next topic: - 5. phonon-xine removal (5 minutes) - * Discuss/vote: Upstream declared it as dead. Already masked -since 1. Dec - 2011. We have two other working and maintained backends. -Current open bugs - #359979, #397585. - who? - i - write your name next time or i'll come to germany and choke you - kill it =D - eofl - *rofl - is this still the latest? or are they resuming development since -xine-1.2 is out? - But yeah bitrot should be removed - dilfridge: I was going to ask about it - have a look at p.k.o - johu: did you ask any upstream devs about it? - dilfridge: the reason for the p. mask was that we thought it was -completely dead, but now it seems there are people working on t - it* - i'm not aware of anything official - tampakrap: it was announced as dead with kde 4.6.0 - johu: yes, but xine itself was considered to be dead. Now it -seems it might not be - jmbsvicetto: well, 3 commits in 12 months... - we have to ask in #phonon - I've moved to phonon-vlc a long time ago, so I have no direct -interest in xine/phonon-xine - dilfridge: hmm, that doesn't seem to active to me - * #phonon: Cannot join channel (+i) - you must be invited - in any case, I think we should make sure before we kill it - thats why we mask it - wait people - i'll ask apachelogger - if xine is still dead, then let's kill phonon-xine. Otherwise, -we can keep phonon-xine for a few more weeks / months to see if anything turns -out of it - i asked apacheloger, depending on the answer i get we'll act -accordingly - apacheloger = upstream phonon dev - acceptable? - yes - I also asked on #kde-multimedia, let's see - dilfridge: seems like #phonon is redirecting to #kde-multimedia - anything else here? - next: - 6. qt-4.8 (5 minutes) - * Short discussion about potential problems. - i updated to 4.8, everything seemed fine apart from kdenlive - no glitches, no compilation failures - ! - anyone here who updated with kde-4.7.x ? - i'll switch if it in tree - yes, i updated to qt 4.8 and kde 4.7.4 - I updated 3 machines, no problems at all with kde-4.8 beta/rc - kokeroulis: if you want to speak just do it - on Qt 4.8 there is an issue with the pointers - dilfridge: I'm just running ~arch these days - they are not killed - but updating a running kde-4.7.4 made all kde programs segfault in -oxygen style until I rebuilt kstyles - there is a post on plasma-devel ML - ok - let's see - johu: you could help us (qt) about it - wired should know better - and pesa - tampakrap: you can ask me to join the herd :P - i'll send you an invitation - kokeroulis: how serious is that issue? - and how much does it affect us? - I suggest we make two revs of kstyles-4.7, one requiring qt-4.7, -one requiring qt-4.8 ---> forces a rebuild, one problem solved - +1 - +1 - +1(external) - tampakrap: it seems a alot. Because some upstream devs has -mention that the KDE 4.8 should be shipped with Qt 4.8, so we will fix it -until the major upgrade of the binary distros. Otherwise all the binary distro -will ship KDE with this issue on their major version - dilfridge: how are you going to manage the revision numbers? - jmbsvicetto: by hand... -r0 & -r10 ... - I'll figure somethign out - it only requires talking to qt - just put one in overlay until 4.8 is out - exactly - and mask it together with qt-4.8 - dilfridge: sure, but I meant the numbers. So we can use 9 -revisions for kde-4.7. OK :) - kokeroulis: do you have a link to the ml post? - dilfridge: -http://mail.kde.org/pipermail/plasma-devel/2012-January/018493.html - ook --*- dilfridge librarian mode - tampakrap: shall we move to RPATH ? - there are more about this conversation but the web archives have -some issue about that - dilfridge: i found it. -http://lists.kde.org/?t=132630064900003&r=1&w=2 - jmbsvicetto: dunno - anyway, is it so important to discuss it now? can we continue the -discussion in the mailing list or next meeting? --*- wired is here :) - next meeting^ - tampakrap: wired: any plans to move qt-4.8 to the main tree (even -masked)? - wired: issues with qt 4.8? - dilfridge: unmasked, prolly sometime next week (near end), unless you -kde guys have any serious issues with it - heh - wired: no only kdenlive failed to build - that makes the priority a bit higher - mmmmmm qt-4.8-y goodness - wired: afaik no serious problems - it appeared to be a tiny fixable problem - at least I'm running it - I have not hit the problem yet that kokeroulis mentioned - wired: issues/tracker to help? - omg - it's starting - what? - tampakrap: hadn't had the time to do anything yet, no major issues -afaik, just opportunities to fix things :) - [21:55:23] ago * gentoo-x86/app-misc/strigi/ -(strigi-0.7.7.ebuild ChangeLog): - [21:55:23] Stable for amd64, wrt bug #396359 - [21:55:23] (Portage version: 2.1.10.41/cvs/Linux x86_64) - [21:55:26] CIA-4: https://bugs.gentoo.org/396359 "KDE -4.7.4 and dependencies stabilization"; Gentoo Linux, Keywording and -Stabilization; CONF; dilfridge:kde - https://bugs.gentoo.org/396359 "KDE 4.7.4 and dependencies -stabilization"; Gentoo Linux, Keywording and Stabilization; CONF; -dilfridge:kde - lololol - dilfridge: you will get a lot of highlights now - right. - wired: i have not used the Qt 4.8, so i don't know if there is -any big issue.... - ok good - kokeroulis: i've installed it on my two main workstations and it works -fine, however I don't have KDE anywhere ^) - anything else here or shall we move? - move - move it baby - wired: talk to me please before you bump qt - 7. Dropping RPATH from installed binaries (5 minutes) - * Short discussion- any objections to testing this in the -overlay eclasses and later - moving it to the main tree if it works? - dilfridge: sure, was planning to anyway :) - this is mine - we already removed the RPATH from qt libraries successfully - with no real benefit probablhy - ;p - it's possible because we add the qt library dir to /etc/ld.so.conf - whats the purpose? - well, all binaries built by qmake not also have no RPATH - dilfridge: I don't agree with dropping RPATH from binaries on -Linux - I'd say simplifying things - what can break? - we do not need two pointers to the lib dir - dilfridge: and by dropping it from the Qt eclass we were -supposely telling the linker to use what KDE defined - and not building -binaries with empty RPATH - dilfridge: just leave #gentoo-commits for a while :) - no, the plan was to get rid of the RPATH entirely - dilfridge: the issue is that binaries with empty RPATH have an -higher security sensitivity - err... why? - dilfridge: the reason we set the RPATH is to ensure that a user -is not able to "subvert" a legitimate binary by having it use libraries on a -exploited dir - dilfridge: if you have a binary A that uses library B and you -allow the user to specify the library dirs in which A should check for B, you -allow the user to add a "compromised" B library to a dir he controls and with -that you allow A to be compromised - dilfridge: at least that's my understanding. I might be wrong - LD_LIBRARY_PATH is ignored for setuid - and you could always copy a normal binary and set its RPATH - jmbsvicetto: with LDPATH and LD_LIBRARY_PATH i wonder if RPATH is -really preventing what you're talking about - wired: but LDPATH is controlled by root, right? - system files as well - dilfridge / wired: in any case, if you guys are not sure, I -think we should talk with the hardened team before dropping RPATH from -binaries - and with the prefix team probably :| - that has to happen before qt 48 goes to main tree - we should track down diego - I'll try to talk with Diego about it - ah, he's coming to fosdem - he's alive and kicking @twitter ^_^ - anything else? - I haven't caught him on jabber in a while :-\ - move? - move, decision postponed - 8. To eselect Boost or not to eselect boost (10 minutes) - We need to figure out what is actually the best desired -behaviour :| - who? - dev-zero - :] - newest info was that eselect goes away - see comments in the bug - we need to discuss this on the mailing list - but boost maintainers seem to prefer always building against -newest version - so lets talk to dev-zero and if this not help dev ml --*- tampakrap is confused - ok now i get it - so move? - no move - at least not to tree - move to next topic i mean - yeah^ - * dev-util/cmake picks always the latest boost. - * Fix in overlay since 13. Dec. Move to tree? - https://bugs.gentoo.org/show_bug.cgi?id=335108 - I still think this should be moved to the gentoo-dev ml - tampakrap: this is the same^ - This is far more involving that just kde, and can affect any -package using cmake - like mysql-5.5 ;) - * cmake-utils.eclass PREFIX is not defined, any progress? - https://bugs.gentoo.org/show_bug.cgi?id=358059 - johu: raise the topic in the ml then? - tampakrap: seems that this my part - @boost - [22:14:00] dilfridge: pxine is dead - [22:14:09] no plans to revive - johu: the arguments from dev-zero about the use of boost should -also be discussed as boost should be compared to gcc, python, ruby, etc - dilfridge: so we can remove it - fine with me - johu: I think so, yes --*- johu will do this - i will send a 10 days last rite - hey guys I am very sorry, I slept away two hours ago... :-/ - " * cmake-utils.eclass PREFIX is not defined, any progress?" - the last comment from this bug was that reavertm want to investigate, -but nothing happend - johu: use the usual 15 days, please - jmbsvicetto: its masked since start of dec - johu: otherwise someone will complain about it and we'll get in -an argument that will likely be less useful than just waiting 15 days ;) - johu: I know, but mask is not the same as last-rite and I -believe it's more productive to wait 5 more days than get in an argument for -not having followed policy - jmbsvicetto: fine with me - move to next? - see some lines above - the cmake PREFIX bug - johu: that one will require work with the prefix team, no? - jmbsvicetto: it would be good if reavertm were here - maybe he have infos about that - johu: That won't be easy as grobian is not a fan of cmake and it -does seem to have base flaws to support prefix - jmbsvicetto: not really afaik - that is not something related to "Gentoo prefix" - more like, cmake build magic - dilfridge: sorry, then I must be thinking at another bug - jmbsvicetto: yeah you think about the other cmake bug - the macosx request - ok, can we skip that then for next meeting? - reavertm is not here today - Ah, now I recall this bug - I still don't see what that patch actually fixes - That patch assumes prefix is defined and if it's empty it -doesn't add /usr - yes - I still think that patch is wrong - better still, that patch moves the definition of prefix to the -start and then does the same as it was doing before - so the only real change there is the following: - - SET (CMAKE_INSTALL_LIBDIR ${libdir} CACHE PATH -"Output directory for libraries") - + SET (CMAKE_INSTALL_LIBDIR ${PREFIX}/${libdir} -CACHE PATH "Output directory for libraries") - everything else is just a "format" change - ok - so the question is whether libdir should or should not be -relative to prefix - tampakrap: anyway, we can move to next bug :) - thank you - * Remove hard dep on media-libs/phonon from kde-base/kdelibs - https://bugs.gentoo.org/show_bug.cgi?id=356681 - https://bugs.gentoo.org/show_bug.cgi?id=388041 - Has upstream fixed the bug that made us add the hard dep? - no - iirc, knotify would stuck if we didn't had phonon in the system - phonon still requires at least a backend to work - and taking out phonon from kdelibs is not possible - so WONTFIX / UPSTREAM ? - so we have to postpone this to kde frameworks? - can you build kdelibs against qt-phonon? - so, kdelibs still needs phonon and we can't substitute it with -qt-phonon yet - no, we asked upstream already - dilfridge: and i think you did actually :) - I only asked if you need a backend to phonon - not if qt-phonon were a substitute to phonon - you are in the channel, ask them about it now then :) - I would like us to be able to drop the phonon dep, but upstream -doesn't allow us to present that choice to users :-\ - so resolution? - let's ask upstream first - but i'm 99,99% sure it's not possible - and if not, close it as UPSTREAM - ok move on - just did - * Eclass problem with handbook without LINGUAS. - https://bugs.gentoo.org/show_bug.cgi?id=372457 - idella4: do you have find something out? - that's an obscure one - ^ - ?? - about this bug? - yes - well you caught me on the hop - I seem to remember working it - I had it compile effectively without LINGUAS set from memory - but -handbook was causing the flaw - that must be around a week ago - maybe I left some good comment in the bug --*- dilfridge gets a drink - ok, is there anything to discuss here? - no - * MacOSX request for cmake-utils.eclass: - Remove force of CMAKE_BUILD_WITH_INSTALL_RPATH=TRUE - https://bugs.gentoo.org/show_bug.cgi?id=398437 - -> can easily be done, because the FORCE affects only prefix -anyway - jmbsvicetto: here we go^ - jmbsvicetto: ^^ is that the one you confused earlier? - no reason to drop that hard requirement - yes - bah, sorry. I meant to say, no reason *not* to drop that hard -requirement - so let's do what prefix asked - thats sound reasonable - move on? - fine with me - we've reached kde-base/kcolorchooser by now --*- johu is watching the chat monitor - * Revise the change "semantic-desktop? -> semantic-desktop=". - Why was the change needed. - https://bugs.gentoo.org/show_bug.cgi?id=396491 - dilfridge: if you want, we can highlight you a bit on -#gentoo-kde ;) - yeah well reavertm is still not here - hehe - i am fine with dropping the '=' - so, I never liked that semantic-desktop? -> semantic-desktop= -move, but it was done with the argument that we were getting strange and -unexplicable bug reports and that it was causing issues in the upstream bug -tracker - I dont see why we should allow "?" - because nobody gains from it - +1 @ dilfridge - once you have kdelibs with semantic-desktop, you have all the -dependencies - dilfridge: As I don't want semantic-desktop at all, being able -to just enable it where I'm forced, would be a plus. But I think we should try -to be consistent - but dont you need kdelibs[semantic-desktop] for any -semantic-desktop enabled package? /me confused - can we skip it for next meeting? - sure - yawn - good - OPEN FLOOR - there were real reasons that we agreed with to have -semantic-desktop= back then (we as in the kde team, even if I disagreed) - dilfridge: ? allows that - yes - dilfridge: the point with = was that I would have to had every -kde package built with semantic-desktop if just a single one required -semantic-desktop - scarabeus was the one to push that decision - tampakrap: talk to scarabeus in office about that - tampakrap: I feel like were starting to have a "memory issue" in -the KDE team. We got enough new people recently that some of the old issues -are being raised again as the team (or a substantial part of the team) doesn't -know the history behind them - jmbsvicetto: i believe that is reasonable though, things change, -new decisions are taken - tampakrap: that means we should probably start thinking about -providing better documentation for decisions so that people know sometime -later whey they were done - technically it should be in the meeting logs - i agree with the documentation, and it is entirely my fault - i'll do my best from now on though - open floor: cleaning up herd? - again? - tampakrap: I don't think it's a bad thing. I'm just stating that -I've noticed it and that we should perhaps rethink a few things in how we -operate ;) - i did that in less than a year :( - jmbsvicetto: +1 - !herd kde - (kde) abcd, alexxy, dilfridge, jmbsvicetto, johu, mschiff, -patrick, reavertm, spatz, tampakrap, thev00d00 - spatz? - patrick? - tampakrap: Hey, at this point in time I'm the "oldest" kde dev -around ;) - patrick is special - yes, let's kick jmbsvicetto out - meow - :D - tampakrap: hehe, "special" ;) - tampakrap: I've told you at this point I only care about amarok -and related packages :P - johu: i'll talk to spatz, ok - can somebody make me wise? --*- jmbsvicetto blesses johu with wiseness - thx - :) - Patrick I suspect is soon to wake up - another topic for open floor: - !time bonsaikitten - dilfridge: I don't know where bonsaikitten is, (s)he should use -!time set / to let me know - idella4: I can finally make fun of Patrick at some hours without -risking him replying to me ;) - China - when the Cat's away - I'm doing a kde release party here in prague a week after fosdem, -probably at suse office, you are all invited - idella4: He used to be more time online than me :) - he is on-line alot - see he is in my timezone - tampakrap: It seems I'm too "heavy" to catch the fiber optic to -your office :P - tampakrap: travelling already that weekend, sorry - tampakrap: otherwise I would take your invitation and go check -the "blankets" ;) - you loose - oldies - anyway, meeting closed - i'll do the summary, someone upload the log please diff --git a/meeting-logs/kde-project-meeting-log-20120322.txt b/meeting-logs/kde-project-meeting-log-20120322.txt deleted file mode 100644 index 63e1ef7..0000000 --- a/meeting-logs/kde-project-meeting-log-20120322.txt +++ /dev/null @@ -1,282 +0,0 @@ - so let the party begin - 1. Roll call --*- tampakrap here - ABCD, alexxy, bonsaikitten, dilfridge, jmbsvicetto, mschiff, scarabeus, -tampakrap, Thev00d00 --*- dilfridge here --*- alexxy +1 --*- mschiff here --*- johu of course too - yo - ok lets move on - 2. Electing a new team leader --*- johu nominates tampakrap - I decline - other proposals? - yes, dilfridge - why not - scarabeus are you interested? - he he - may be scarebeus? - johu: are you interested? - =D - are you guys insane - why the hell i would like to be lead :) - i would have to start actually care - scarabeus: because you are veteran - scarabeus: didnt you care? or you turned to m$ win camp? --*- tampakrap nominates johu and dilfridge - ok lets vote if no other proposals show up - scarabeus: so you agree for nomination? - nop not accepting :) - let someone new do it --*- johu votes for dilfridge --*- dilfridge votes for johu - hmm --*- creffett stays out of this one - cycle dependency? - :D - maybe we could recompile one with USE="-doc" to fix it --*- tampakrap votes for dilfridge - +1 for dilfridge - +1 dilfridge - dilfridge++ - ok 5:1 - bless the new lead - (nothing against johu i just want to see dilfridge enjoy my post -:P) - :P - the post is mine - thx tampakrap for your work as lead - thanks guys - you are welcome - congrats dilfridge!! - yeah thanks tampakrap --*- tampakrap kicks dilfridge - ow - =P - 3. Dropping RPATH from installed binaries (5 minutes) - * Short discussion- any objections to testing this in the overlay -eclasses and later - moving it to the main tree if it works? - ghmm - may it hert someone? - dropped rpath should work as is, so do it - +1 - doesn't debian disable it too - I dont see any problems - hmmm - +1! then - lets give the removal a try from me - it's basically a patch in kdelibs afaik - to one of the cmake files - I can prepare that, I've looked into the thing before - (but have not tested the result before) - why was it introduced? - it's default in the kde buildsystem - and imho a bug in cmake - i think it was here for sloted kde versions - the logic is: - * add a RPATH entry for every library dir that is not in the -system library directories * - the cmake bug, in my opinion, is: - * directories in ld.conf are not automatically considered as -system library dirs, but only some static list of dirs * - our qt4 is in a "non-default path", usr/lib(64)/qt4 - so cmake adds it to the RPATH - but that's not needed because we add it already to ld.conf with an -environment file - s/ld.conf/ld.so.conf/ - any objectiosn from the crowd? - fine by me - kill it =D - ok we move on - we can introduce the patch with 4.8.2 and move it to the main tree -then - 4. Bugs (30 minutes) - * Remove hard dep on media-libs/phonon from kde-base/kdelibs - https://bugs.gentoo.org/show_bug.cgi?id=356681 - https://bugs.gentoo.org/show_bug.cgi?id=388041 - dilfridge: yes its next week - ok I'll make the patch for 481, it should apply just the same to -482 - qt-phonon will be removed with qt5... - or should it bee || x11-libs/qt-phonon ? - upstream says "technically you can replace phonon with qt-phonon, -but that's just stupid because you lose functionality" - (kde upstream) - reasonable^ - so maybe ewarn if qt-phonon is there but accept it - we should go the other way - i think we get into a lot of trouble with not much gain - remove qt-phonon if desired - but not the other way around - exactly, I believe we should keep phonon as is --*- johu votes for as is --*- dilfridge votes for as is and close bug as wontfix - I mean if someone knows what he does and *wants* qt-phonon? - I wonder why Markos added that bug... - find me one first - alexxy: your opinion? - otoh if it will be dropped soon... ok +1 for keep it as is - i dont think its good idea - we should keep it to make kdelibs functional - ok i will take of the bug after meeting summary - * Eclass problem with handbook without LINGUAS. - https://bugs.gentoo.org/show_bug.cgi?id=372457 - anybody had a deeper look in to this? - no... it's pretty confusing code - the handbook code is quite magic :) - you need reavertm to explain that - we need reavertm in every team meeting :D - skip for next meeting? mail reavertm? - dilfridge: your first lead task - hehe - I'll try - next bug - * Revise the change "semantic-desktop? -> semantic-desktop=". - Why was the change needed. - https://bugs.gentoo.org/show_bug.cgi?id=396491 - dilfridge: Mission directive for you: Find reavertm and make him fix -handbook =D - was before my time - scarabeus: ^ that's for you - johu: the goal was to enforce it everywhere - it is ment to be global useflag only - so set in make.conf or not set at all - some packages rely on semantic-desktop capablities in other ones - and this was easiest way how to ensure that user wont fuckup - and this is valid today - I approve that change - it should still be - ok tampakrap you are the volunteer for that bug - ack - 5. Open floor (15 minutes) - kwin does not build anymore without opengl support (or at least -gles) - yes - tampakrap: so what with the stabilisation - fwiw, I'll become upstream of kportagetray and hopefully -plasma-emergelog, I'll work on those next week and probably will release stuff - scarabeus: i would suggest 4.8.2 - dMaggot: cool - what stabilization? - ah, kde sc - what's still bad in 481? - I would suggest 4.8.1 asap, it has tons of bugfixes - many crashes as well - I would stabilize it asap imho - I mean I'm running it and it seems to work finr - 4.8.2 has some important fixes too - fine - each version have important fixes - the keywords not restored so far - question is: are those regressions since 4.7 - definitely not - scarabeus: no =D - scarabeus: in kmail, I think - it only features - and keywords is johu's job :D - no, kmail got much more stable again - tampakrap: and you have the query for the bugs :) - kmail works with lkml imap dir - kmail 4.8.1 is already heaven comapred with 4.7.4 - with 300k+ mails - trust me i am runnig stable kde now - and sometimes it does interesting stuff - don't trust him, he is running opensuse - scarabeus: stable?! - lol - see my stabling of akonadi-server :) - anyway - to solve some bugs - https://bugs.gentoo.org/show_bug.cgi?id=407709 - ahh opensuse =D --*- tampakrap votes for 4.8.1 with passion - its not stable =D --*- dilfridge votes for 4.8.1 --*- johu votes for 4.8.2 - johu: see this is regression, if 4.8.1 goes stable just shovel the -patch to 4.8.1 - alexxy: i run stable gentoo , hardened stable gentoo - +1 for 4.8.1 - Linux arcarius 3.2.2-hardened-r1 #8 SMP Thu Mar 22 12:23:02 CET -2012 x86_64 Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz GenuineIntel GNU/Linux - scarabeus: hardened desktop? - alexxy: yep, same as dilfridge --*- johu will prepare stabilisation - hmmm - i may try it on laptop =D - johu: lemme know when you have list, i can showel it to my desktop -and test - though I dont use hardened kernel yet... but I'll change that soon - scarabeus: did you enabled grsec? or you use only pax? - any other topics in the open floor? - am I allowed to bring one up? - sure - (if it hasn't been discussed at a meeting previously), what to do -about all of the dbus-related test failures? - sigh - its open floor so anyone allowed - ignore them? - because with a lot of them, we're patching out tests to the point -where the test suites are pointless - honestly I dont know what to do there - alexxy: both - many of the testsuites are not even used by upstream devs - my personal suggestion would be: - which is really ssad - the best solution for the test failures woold be to get virtual-dbus -eclass running - * if only one test / two tests of many fails, disable with patch - I was looking at that - * otherwise restrict - if you can make it work, that would be great - but I've given up hope a bit - also, - the problem with virtual-dbus is that we'd have to dig into the kde -eclasses - because you can't run a bash command in the virtual-dbus -environment - dbus is a communication tool, so the tests need something to talk -to (i.e. a kde desktop environment) - which means the tests may want to start up an entire desktop -environment in the virtual session - :| - I also have a quick topic when you finish with the dbus tests - I haven't got anything else on the matter - creffett: if you get this to work, great... - OK my topic: - dilfridge: I'll keep poking, no promises :P - tampakrap: go ahead - welcome new members: creffett (he has open bug), kensington ( he -has open bug as well), dastergon (he doesn't have open bug yet, but he has the -priviledge to be my friend) - :) - and welcome to scarabeus - another ugly greek :P - :) welcome! --*- creffett waves - welcome ;) --*- mschiff has another little one: I am a bit short of time working in kde -herd because we are building our new home here... but this will calm down in -May, so I hope to have more time again then... - scarabeus: the greek community is growing fast !! - yeah, now that I left :( - any other topics? - another short one - I'm going to stop doing kde things and spend 99% of my gentoo time -in infra --*- dilfridge sets linewidth in tampakrap's irc client to 20chars - since mentees are shortened out and I don't have the leader -position any more - sad - :*{ - hey we'll miss you! - not really, you don't need me - scarabeus: kick him from me in the office - :D - 3 - 2 - 1 - meeting is over diff --git a/meeting-logs/kde-project-meeting-log-20120419.txt b/meeting-logs/kde-project-meeting-log-20120419.txt deleted file mode 100644 index a8b0471..0000000 --- a/meeting-logs/kde-project-meeting-log-20120419.txt +++ /dev/null @@ -1,169 +0,0 @@ - ok that's 5min warning... so let's do quick roll call - i didnt tryed ppc - =) - !herd kde - (kde) abcd, alexxy, dilfridge, jmbsvicetto, johu, mschiff, patrick, reavertm, scarabeus, tampakrap, thev00d00 - arm and mips yes - roll call please :) - here - here - here - ay for the captain - :P --*- kensington waves --*- alexxy hides in superstrings continium =d - oh dear - p-branes - lol - ok... since we dont actually have much agenda... - 1) what do we do with kde-4.8.2? file stablerequest as soon as the 30days are done? - too much load for the arch teams, I'd suggest to skip one version - Personally I think we may as well wait for .3 - ok - Is it still due May 1st? - I'm fine with both - yes - so next stabilization would be 483 end of may - and we can maybe add some patches to single packages if there are super-ugly bugs - ok - anyone against "next is 483"? --*- johu is here - i would like to ask you to open bugs for misc apps - they are often working in testing and completely weird in stable - so please jump over our herd packages and fill stablereqs where fit - sounds reasonable - scarabeus: volunteer? - how is euscan doing with the kde packages? - working good - euscan is great - but iksaf still didnt include my request to differ between versions in testing and in stable - eg green only when latest is in stable - otherwise orange - get it - good idea, no volunteer so far, we'll all have to do a bit each - dilfridge: i do it every week on mo/tue - but i cheat - i dont open bugs - :D - i ahve stable boxes - so i stable right away - you can automate that - ok - there is one more question from me, and then I have all off my heart: - 3) is anyone against a stablereq for calligra-2.4.0 ? (after the magic 30days) - no bug reports so far - NO please do it - lets get rid of the koffice foo - and it would be awesome to get rid of koffce - is it dead? - koffice ist kaput - there were some discussions to move it to SC - it is life, Jim, but not as we know it... - did you read in the last year any news update in koffice? - more like zombie - even the last blog posit of tzander was a year ago - tampakrap: that suggestion led to a lot of opposition, it was seen as some scheme to give koffice a more official status than calligra - but I stopped following the fuss at some point - ok seems like nobody opposes - anyone else has anything else? - yes kde481 is table - :) - hehe - at least for amd64, x86 - yeah pretty nice chair it is - 4) arm stable in kde 49x? - is qt stable in arm? - 472 - 474 in porgress - johu: I actually like the idea, but I dont have an arm machine that could run kde decently - 48x not decided yet - hm ok nvm - I mean, the number of arm gadgets will go up more and more - while ppc machines are falling apart - we can do this for sabayon folks - we could also think about packaging plasma-active - how about asking in a blog post for volunteers? - i dont see sane to run gentoo on arm machines right of the box now :) - scarabeus: at least kde runs pretty well, people say (with hw graphics accel) - tampakrap: what should the volunteers do exactly? - arch testing - obviously :) - ok - dilfridge: do you got any answer from reavertm abouy the open issues/questions? - yeah well it's an idea - johu: no - hm :-/ - tampakrap: I'll ask the arm guys about this, if they like the idea I'll blog - ah yes I remember one more thing - what you guys want from Maciej? - 5) the ewarns about the tar commands, they are completely useless even for devs. can they go away again? - ask reavertm :) - :) - they can go away - scarabeus: most questions are eclass related - :D - poor you :P - but wait were there someone else with me working on that - i know, JORGE! - bug 358059 - dilfridge: https://bugs.gentoo.org/358059 "cmake-utils.eclass PREFIX is not defined"; Gentoo Linux, Eclasses and Profiles; CONF; meka:kde - that is actually the only one left - all the rest is imho done - linguas - or i missed something? - kensington has found the problem I think - we just need to doublecheck the solution - dilfridge: ack on the patch - ok - it actually fixes stuff i wrote there in first place :D - it was creffett - ok sorry - scarabeus: I'll try to understand it myself over the weekend, and then... - |:] - basically now the prefix is defined on 5 places - this defines it on one place - and then just uses such var - so it is correct - only weird line is this one: - -SET (CMAKE_INSTALL_LIBDIR ${libdir} CACHE PATH "Output directory for libraries") - +SET (CMAKE_INSTALL_LIBDIR ${PREFIX}/${libdir} CACHE PATH "Output directory for libraries") - "but when i think of it ; it looks correct - we can always test in overlay - nah rest of the patch is harmless - just check one package if it puts shit into /usr/usr/lib64 - and if not it is correct - hehe - ok - anything else to discuss? - 6) open floor - SLED will have kde4.8 "soon" - cough - cough - ok - that means they consider kdepim-4.8 stable enough? - isn't it? :) - on my work desktop it's ok - tampakrap: i dont think there is plan to build kdepim too :P - it's built already - the obs repo is linked from the opensuse 12.1 one - suse ich will sie nicht nimm duse - lol - it - seems - like - we - can - close - the - meeting? - next time i have to organize the meeting it seems - :P - hehe thanks in advance! - no, give it to a new guy - who writes summary? - whoever asks first :P - go away - ok I'll do it - cheers & thanks everyone - thx for chairing - byes diff --git a/meeting-logs/kde-project-meeting-log-20120517.txt b/meeting-logs/kde-project-meeting-log-20120517.txt deleted file mode 100644 index 6a87757..0000000 --- a/meeting-logs/kde-project-meeting-log-20120517.txt +++ /dev/null @@ -1,324 +0,0 @@ - 1. roll call - !herd kde - (kde) abcd, alexxy, creffett, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, tampakrap, thev00d00 --*- johu is here --*- dilfridge here --*- creffett is somewhere around here --*- kensington of course - 2. Add LINGUAS support to cmake-utils.eclass - kensington: looks like itterative process which should coverage - hehe --*- alexxy here - :P - err there's one more part for 1. :) - first of all a big welcome for our new team members kensington and creffet :D --*- creffett waves --*- johu applaudss - ok that was it from me :D - kensington: what would your linguas implementation cover? - kensington, how did you forget to add "make everyone congratulate us" to the agenda? - creffett: I wrote that before we finished recruiting, so that's my excuse :P - basically, just copy straight out of qt4-r2, so need to stick an ugly loop adding linguas_X in packages that need them - *no need - for x in ${LANGS}; do - IUSE+=" linguas_${x}" - done - hm ok would reduce some ebuild code - any objectsion to that? - is there an standard handling for the linguas handling planed? - no idea - it would be nice, but I do not know of any - but the code looks everywhere the same - just use a "safely unique" variable name for x and unset it afterwards again - do we need to send to -dev about it too? - i have no objections - no objections - no objections... hic... - 3. Live KDE ebuilds are unconditionally test restricted - btw may be we can write generic linguas.eclass? - kensington: but gentoo-dev can not hurt - alexxy: there was already a discussion about that on -dev?! - alexxy: nice idea but that needs to be bikeshedded on -dev - generic eclass would be nice, but I don't know if there's much beyond those three lines that are portable between build systems / packages ? - johu: yep it was about a year ago - probably not. - ah ok, dont remember - re 3: I say leave them as restricted, because we have enough trouble already with the official release tests - well... anyway. I think whoever runs live kde with tests seriously needs some disruptions. - :D - but, from a practical point of view, creffett is right - he he - i use 9999 on my laptop - but i didnt enabled tests =D - i would say enable them with the magic var! - its not a bug deal - I_REALLY_REALLY_KNOW_WHAT_I_AM_DOING - big - haha - dilfridge: I like that idea :P - ynauv - yet not another useless variable^ - how about we just add it to the usual I_KNOW_WHAT_I_AM_DOING ? - who sets this should be able to handle the fallout - test enable on I_KNOW_WHAT_I_AM_DOING - dilfridge: better to use YEP_I_REALY_REALY_SURE_THAT_I_WANT_BIG_HEADACHE - ... AND_I_PROMISE_TO_NEVER_EVER_FILE_BUGS - can we become serious? :) - Yessir. :) - I_KNOW_WHAT_I_AM_DOING___SERIOUSLY - test enable on I_KNOW_WHAT_I_AM_DOING - agreed - I agree with johu - +1 - sounds fine, +1 - reavertm nice to see you sir - :) - 4. KDE 4.8 stabilization and powerpc - ok thats my topic - i added it because gcc47 was dep to keyword it - elaborate on it please :) - but JoseJX told me some hours ago that he will keyword it tonight - it was a mistake with gcc47 - cool - but they need qt 481 - i think b) can be seen as obsolote - Hey - ok sounds good - I'm the PowerPC rep I guess - hey JoseJX :) - but we should discuss if ppc64 make sense - I'd really like to not drop keywords if possible - JoseJX: whats your opinion about that? - KDE still runs well on my G5 - I can see the argument for dropping ppc64 from stable, but keeping unstable, since we don't really have the manpower to handle it. - There's also the fact that most of our users are not running ppc64, even on ppc64 machines - Most are set up with a 32bit userland (the ppc keyword) - I think that already happened some time ago, at the moment we only have stable "amd64 ppc x86" - scarabeus said that ppc64 are serve machines - dilfridge: I think that's reasonable - but if the gcc-4.7 problem is gone, we should try to keep things as they are (ppc ~ppc64) - That's what I'm aiming for now - ppc/~ppc are definitely fine - but makes ppc64 realy sense? - I'm still working on testing ~ppc64 - thats the first question we should find a answer - I do know that we might have some TOC issues, which might make this all moot anyway on ppc64 - But those will be fixed when gcc-4.7/4.8 is ready - is there any ~1line summary for that? /me does not have a clue - I'll try to explain - ELF on ppc builds tables of function calls, but on ppc64, the tables get too big and the TOC runs out of space because the pointers are 2x bigger. - but gcc-4.7 stable will hapen maybe 2013... - Basically linking > 32MB (I think that's the size) doesn't work on ppc64 because the jumps are too big - We can work around it with --minimal-toc and that's what we have been doing. - That's the short version - JoseJX: are there lot of desktop systems with ppc64? - ok... what's the problem with (for kde) global --minimal-toc ? - dilfridge: None that I'm aware, but ranger would be the better one to ask. - ok - johu: Honestly? No. - johu: I run it on my G5, but I'm sure I'm an edge case - ok, makes no sense to me to keep ppc64 then - johu: but ~ppc64 is not really a problem... - I think that's where I'm at too - anyone else has an opinion? - I agree there's no need for stable keywords, but if possible, I'd like to keep the unstable ones. - ok please vote on keep ~ppc64: - -1 - +1 - 0 - 0 - or keep ~ppc64 - i dont currently have any ppc hw - 0 - so i cannot test - meh - seems we cant find a decision here so lets keep it... - Well, how about this. If everything is working when I do the ~ppc keywording later today, I'll also mark ~ppc64. If not, I'll let it drop. - +1 - +1 - i will raise this issue again for sure ;) - +1 - =D - why not, +1 - johu: That's fair. I don't see what dropping unstable keywords helps with though? - JoseJX: because server systems != desktop systems - I've tried already to build a ppc/ppc64 qemu chroot but right now this fails because of a qemu-static bug - and KDE is for sure a desktop/tablet env - johu: Only new ppc64 machines are server systems, but in the past, we had the PS3/G5 both which definitely were not server systems --*- dilfridge thinks mips tablet and runs fast... - did someone say mips? :D --*- creffett hands dilfridge a cobalt raq2 - keywords all the archs! - JoseJX: ok i think you can do your job tonight ;) - JoseJX: and big thanks for that - Okay! Thanks guys. I have to get back to work, but I'll probably be doing the keywording around midnight EST. - Just for a heads up! - JoseJX: if the work load is to big to stable 483 you can wait for 484 - johu: No worries - When is 4.8.4 expected? - Would it be better for us to wait? - 484 is tagged end may - it's always one month later - In either case, we need to go forward with the unstable keywords first, so that won't change - so we will start with stable mid june - makes sense - Okay, we'll probably target 4.8.4 for stable on ppc then, figure one month in unstable gets us to June anyway - yes - As long as that's fine with you guys - its totally finee - sure - Great! - :) - JoseJX: thanks for being here - kensington: procede pls - No worries, later! - 5. Bugs - bug #380899 - kensington: https://bugs.gentoo.org/380899 "Trying to change full name in KDE System Settings results in error or crash"; Gentoo Linux, KDE; UNCO; gentoobugzilla:kde - there is a workaround that disables that feature from ubuntu, do we want to apply that? (looks like upstream doesn't care about the bug) - kensington: i saw a other solution, fallback to nickname on reviewboard - kensington: you have good connections to upstream try to talk to them - johu: if we are thinking of the same patch, it didn't work - still crashed - hmm - seems like the feature does not work, why not disable it - I suspect once the code is fixed our patch will not apply anymore and we will notice - https://git.reviewboard.kde.org/r/104965/ - kensington: this one?^ - johu: no, I was thinking of a different one, sorry - does that really fix the same problem? - i am not realy sure --*- dilfridge confused - I don't think so, the issue from the bug is systemsettings hangs because it can't talk with chfn properly - i would suggest try to talk to upstream and if you get no good answer or proper response disable it - +1 - say 2 weeks time limit - ok who's going to do it? - ok I will - ok next pls - bug #410347 - kensington: https://bugs.gentoo.org/410347 "app-cdr/k3b: use media-libs/musicbrainz:3 instead of :1"; Gentoo Linux, Applications; CONF; pacho:kde - reavertm: you probably know more about this one - we can probably just drop musicbrainz altogether - last time I checked there was no musicbrainz:3 support at all in k3b (but it was long time ago) - well k3b has not changed much lately - mhm, that's what the comments on the bug indicate - (I mean, there's api difference between those two) - I agree with creffett, I couldn't find any evidence that musicbrainz is actually being used anymore - in gentoo terms k3b would be maintainer-needed - :1 is obsolete - drop it - ack - bug #405181 - kensington: https://bugs.gentoo.org/405181 "dev-util/cmake: FindPythonLibs behaviour broken by Gentoo patches"; Gentoo Linux, KDE; CONF; gentoo-bug:kde - meh - i hate it - the best way woudl be to - * remove the patches - * and force cmake onto a specific python version via commandline defines - that _should_ work - but I have not tried yet - sounds good, should we try that then? - yes, but no guarantees it'll work - bug #410139 - kensington: https://bugs.gentoo.org/410139 "kde-misc/networkmanagement-0.9.0 and kde-misc/networkmanagement-0.8_p20110714 wrong doc dir specified"; Gentoo Linux, KDE; UNCO; gritoo:kde - cant never reproduce this... - ditto - couldn't see how it might be run into, looking at the eclass :( --*- creffett guesses funny user settings - we could ask for the environment and the eclass debug log - maybe it was fixed with the eclass changes that we introduced? - but I dont have any other ideas - (maybe funny variables in make.conf?) - ok I can try to take care of this one, it's obscure enough to be interesting - RESOLVE NEEDINFO - hehe - bug #383733 - kensington: https://bugs.gentoo.org/383733 "kde-misc/interceptor - KDE4 Plasmoid - intercept (catch) the log info from the syslog"; Gentoo Linux, Ebuilds; CONF; fitzadam:maintainer-wanted - this one's mine --*- johu dont need the package and have no interest in it :P - basically, it's a plasmoid that requires an init script and modifications to the system's syslog configuration - I also thinks it's overkill and potential security problem - and there's continuing trouble with using the FIFOs required - so, I suggest we resolve wontfix - but we could show it to recruiters as replacement for w... - haha - nah, it's not quite _that_ bad - rating 65% - creffett: not talking about your ebuild, just about the general problem :D - wontfix, or just take us off cc and suggest sunrise? - latter - maybe someone will pick it up - bug #406353 - kensington: https://bugs.gentoo.org/406353 "dev-util/cmake-2.8.6-r4 - stop Xvfb after failed test phase"; Gentoo Linux, KDE; UNCO; toralf.foerster:kde - good catch - if tests die, virtualx can't kill Xvfb it started - will be a problem too for virtualdbus (coming soon!) - is there any phase we could use to clean it up? - i'm asking in #-portage - kensington: are you making any progress on virtualdbus? - I looked at it some, but couldn't figure out a way to make it work for bash commands - I had the same problem, but it seems to work by just exporting the appropriate envvars - oh? - I'll talk to you about it later, then, but I'd love to hear your progress - creffett: this is my work in progress http://dpaste.com/749504/ which is working reliably for the package I've been testing with, systemsettigns - cool, I'll have a look later - k - seems we might need some input from zmedico et al here - let's see if any of them responds - next topic! - 5. open floor - dilfridge: whats the arm state? You wanted to ask the guys - no really definite response yet - only people that replied did not have fast enough machine - hm - (remember this is many gadgets and embedded stuff) - ok postponed - my open floor is ^, I'll bring it up again when there's no more calls to ugly_hack() - hehe - anyone else? --*- dilfridge hears the silence - yes - kde-4.9 beta is coming out soon - kde 483 stable and the last outstanding bug - the dav foo! - right - anyone has a dav-based calendar server? - do we want to stable -r2 which have the upstream "fix" but no positive feedback or just use r0 which is fucked up for sure - -r2 in case of doubt imho - someone will be unhappy either way - some feedback on the upstream bug saying it's still not fixed, but it might be a different but similar bug - yes i read this too - the other people have different problems - +1 on -r2 then - so if noone raise objections i give ago the go tomorrow after keywording ppc/ppc64 is done... - awesome - cool, anything else? --*- johu needs more beer - meeting over then :P - organization question, who writes the summary? - +1 - always whoever asks first :D - always johu i guess - creffett: make a draft i review it! - next time creffett is chairing - :D - dilfridge: if 7 days over i do it for sure on my own as last time with you lazy guy :P - dilfridge: out of contact at the time, sorry - hehe - creffett: ah yes have a great time, when does your trip start? - which reminds me: I'm disappearing from the 20th through june 15th - ^^ - creffett: set your devaway then please - I will - and I'll forward my gentoo mail to the email address I get to use on the boat which doesn't cost me money to use, but I won't be committing or anything - enjoy your trip - I'll try - and dont think about gentoo in this time - we will save some bugs for you - thanks :P - s/save/make/ - 3 - 2 - 1 - end diff --git a/meeting-logs/kde-project-meeting-log-20120621.txt b/meeting-logs/kde-project-meeting-log-20120621.txt deleted file mode 100644 index f34603e..0000000 --- a/meeting-logs/kde-project-meeting-log-20120621.txt +++ /dev/null @@ -1,143 +0,0 @@ -[21:08:37] !herd kde -[21:08:39] (kde) abcd, alexxy, creffett, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 -[21:08:40] ok -[21:08:41] roll call -[21:08:49] -*- alexxy -[21:08:52] -*- dilfridge -[21:08:56] -*- scarabeus -[21:09:00] -*- tampakrap :) -[21:09:06] :) -[21:09:14] (:) -[21:09:16] dilfridge: so you have two lazy ex-leads :D -[21:09:19] hehe -[21:09:31] not counting those so lazy that they dont attend :D -[21:09:46] alexxy: btw summer camp looks intruging so far, working on convincing gf to go with me there :P -[21:10:05] scarabeus: I said I accept -[21:10:08] scarabeus: if you need invitation i can create one -[21:10:26] tampakrap: wanna go to russia mid summer to see gentoo summer camp?; i forgot to ask ya at office -[21:10:41] tampakrap: and for the above sentence you can say goodbye to your left arm -[21:10:47] hehe -[21:10:56] ok let's do this quick and painless -[21:11:04] point 2) -[21:11:10] move 484 to tree -[21:11:35] dilfridge: move it =) with reverted changes to kdelibs -[21:11:37] i suggest *revert the kdelibs commit that needs newer soprano, *move to tree, *stable as usual if nothing happens -[21:11:39] yes -[21:12:06] adn scarabeus said same, so basically we have 100% agreement -[21:12:12] cool -[21:12:16] next point -[21:12:21] 3) 490 -[21:12:31] so far I'm really happy with 4.8.90 -[21:12:32] it should be in tree -[21:12:35] as ~arch -[21:12:37] what do you think? -[21:12:49] i'm running it on laptop -[21:12:52] me too -[21:12:54] we agreed to add last rcs only back -[21:12:55] its pretty stable -[21:13:15] scarabeus: ? dont understand -[21:14:18] few year back we decided to add only last rc if desired -[21:14:36] scarabeus: nah I dont mean 4.8.90, but 4.9.0 -[21:14:57] and that should be fine for sure -[21:15:00] ah sorry for the fuzz then -[21:15:02] yep -[21:15:11] ok that's 3 yes :) -[21:15:11] i can give ya spin on stable when you decide to roll that -[21:15:19] yeah -[21:15:30] next point -[21:15:34] 4) udisks2 -[21:15:53] nothing really to decide yet, but please test -[21:16:00] 4.8.90 and later has the patch -[21:16:13] Philantrop says it has performance issues -[21:16:17] it works (tm) -[21:16:22] ok -[21:16:33] worst case we revert that in 490 -[21:16:46] dilfridge: well if we ask pva to test, he will find tonns of bugs -[21:16:48] alexxy: Check your .X.errors or whatever it's called. Doesn't it have a *ton* of devices being listed? -[21:16:50] hehe -[21:16:59] since he has funny karma -[21:17:03] devnum: 66305 dev file: "/dev/md127p2" -[21:17:03] devnum: 64512 dev file: "/dev/dm-0" -[21:17:03] devnum: 66306 dev file: "/dev/md127p3" -[21:17:03] devnum: 64512 dev file: "/dev/dm-0" -[21:17:28] Adding device "/org/freedesktop/UDisks2/block_devices/md127p3" -[21:17:28] Adding device "/org/freedesktop/UDisks2/block_devices/md127p4" -[21:17:28] Adding device "/org/freedesktop/UDisks2/block_devices/nbd0" -[21:17:28] Adding device "/org/freedesktop/UDisks2/block_devices/nbd1" -[21:17:30] and so on -[21:17:31] dilfridge: Exactly. That stuff slows down file requesters pretty badly if you have more than a handful. -[21:17:32] well i have all my lvm2 volumes listed -[21:17:49] ~12 volumes -[21:17:52] on my laptop -[21:18:05] dilfridge: That happens *every* time a file requesters is opened. -[21:18:11] and i cant say that adding usb flash drive works slow -[21:18:14] let's hope the RH guys fix it up, they should be interested in it too -[21:18:29] I'll watch the fedora repo really hard -[21:18:34] alexxy: You don't notice any difference in performance? -[21:18:59] Philantrop: yep i dont see any *visible* difference -[21:19:10] alexxy: Interesting. Which KDE version? -[21:19:19] 4.8.90 -[21:19:26] alexxy: Hm... 4.8.4 here... -[21:19:42] *4.8.3 actually. -[21:19:57] well... let's just test... but one user on #gentoo-kde also reported slowdown -[21:19:59] 4.8.4 has same kdelibs -[21:20:20] alexxy: True. Are you guys applying any other special patches? -[21:20:26] -*- dilfridge wonders what happens if you still have /dev/fd0 -[21:20:28] dilfridge: its like infamous kernel iowait bug -[21:20:41] it may depend on hw -[21:20:44] not really, no, imho -[21:20:52] dilfridge: cannot access /dev/fd0: No such file or directory -[21:20:59] Philantrop: yep i have some special patches in kernel -[21:21:13] but they are for mm subsystem -[21:21:20] dilfridge: Do you notice any slowdown? -[21:21:21] like memory deduplication -[21:21:24] and so on -[21:21:32] alexxy: Ok, and for KDE? -[21:21:45] I only upgraded today, so the kile that I started with the agenda was the first app to use it... -[21:21:49] kde from kde overlay -[21:21:55] nothing special -[21:22:20] alexxy: Weird... I wonder what's causing it then. -[21:22:27] -*- alexxy uses texmaker -[21:22:33] the list of patches for kdelibs looks harmless -[21:23:10] ok anyway -[21:23:14] next point -[21:23:21] 5) -[21:23:23] bugs -[21:23:33] I think we should postpone this since kensington is not here -[21:23:46] any objections? -[21:24:24] seems not -[21:24:47] which brings us already to the very last point, -[21:24:51] 6) open floor -[21:24:56] anyone has anything to discuss? -[21:25:04] -*- dilfridge gets a sandwich, brb -[21:25:10] yes -[21:25:37] don't forget the gentoo miniconf please, I desperatedly need speakers -[21:25:58] yeah -[21:26:23] is there already anything desktoppy? -[21:26:49] -*- alexxy can talk something about hpc and clusters -[21:26:50] whatever you want -[21:26:59] but i'm not sure if i will take part -[21:27:03] I'd prefer a workshop where people can participate -[21:27:08] but a talk is also fine -[21:27:09] i'll come, just not sure about time for preparation -[21:27:12] we have our own room -[21:27:39] tampakrap: simple workshop - how to crate smal cluster with rm in 30 minuts -[21:27:40] =) -[21:27:46] packaging plasmoids for fun and profit -[21:28:30] both sound awesome -[21:29:09] -*- scarabeus haz to cook, cya laterz lads -[21:29:19] ok lets think about this a bit, but we will organize something for sure -[21:29:50] alexxy: +1 -[21:30:15] -*- alexxy still not sure about visum -[21:30:20] or I could tell something about LinuxGPIB and lab device control with Perl, but that's not for participation, only coolness factor -[21:30:44] yeah the old problem :| -[21:31:21] actualy its simple one =) -[21:31:32] ? -[21:32:24] anyway -[21:32:27] anything else? -[21:33:08] -*- dilfridge listens to the silence -[21:33:42] perfect -[21:33:47] that's it then cheers! -[21:34:02] meeting closed -[21:34:13] i think we just made a new speed recoed -[21:34:19] :) \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-log-20120816.txt b/meeting-logs/kde-project-meeting-log-20120816.txt deleted file mode 100644 index c6ea614..0000000 --- a/meeting-logs/kde-project-meeting-log-20120816.txt +++ /dev/null @@ -1,539 +0,0 @@ - 1. Roll call - !herd kde - (kde) abcd, alexxy, creffett, dilfridge, jmbsvicetto, johu, -kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 - you're repeating yourself --*- creffett is still here --*- johu is here --*- dilfridge is here --*- tampakrap is here - tampakrap wanna rejoin? - no --*- dilfridge thinks we should just do it - jmbsvicetto / Thev00d00 ? --*- ago here too - :D - ok meeting opened - 2. KDE SC stabilization (15 minutes) - * Discuss/vote the options: - a) First 4.8.5 as decided in a former meeting, then 4.9.1 / 4.9.2. - b) Skip 4.8.5, start with 4.9.0 / 4.9.1 directly. - c) Other? - tampakrap: do you know anything about kde-stable subproject? - here - isn't 4.8.5 mostly bugfix? - yes - problem is, noone of the team is running it - yes we can stable it realy fast because of no new deps... - judging from prior experience, we should probably skip 4.9.0 - and all ~arch users have already upgraded to 4.9 - dilfridge: wrong i run 4.8.5 on netbook - dilfridge: I'm here to run it - ok cool & cool :) - there are 2 issues: da translation and a missing theme for splashx - the translation compile error should occure on kdepim-l10n as we split -this up - are there fixes / workarounds? - if we decide on option b) i would start with 4.9.1 as upstream done a -lot of bug fixing since 4.9.0 - dilfridge: yes we can patch it - both? - for l10n - my question is whether it fixes any bugs that are relevant to us - with the theme i hadnt a look so far - creffett: which version? - johu: 4.8.5 - we had two fixed tracking bugs as i remember right - any opinions about the direction a) b) c)? - A imho --*- dilfridge votes a) - ++a, then on to 4.9.1 --*- johu votes a) - I'm here FYI - Thev00d00: then use your voice :P --*- Thev00d00 reading backlog - a) - After the vote I would just add a note, plese give me a voice when I can - ago: can we do 485 faster than the 30 days? - johu: sure, for amd64 and x86 - b) - but scarabeus can do it on ppc :P --*- ago hides - ago: feel free to do and say whatever you want... btw if you leave -and rejoin you'll be op in #gentoo-kde :] - dilfridge: thanks... - speaking of scarabeus... - summary: majority is for 485 and continue with 491/492 afterwards - dilfridge: no need to leave - /cycle - ah ok - 3. Solaris patches (5 minutes) - * We apply many patches to support Solaris, but there seems to be no -prefix - keyword. Does anyone know anything about them? If we are supporting -Solaris, - Kensington would like to push these patches upstream. Does anyone -have - access to a box to test if they are still useful? - that was kensingtons topic but we can talk about it --*- dilfridge wanders off in search of a beer --*- johu personally dont cares about minor arches in kde point of view... - ok, is know that every +1 releases is better than the precedent, but in -this case I would copy kernel's team strategy about stabilization, they -stabilize always non the first release, e.g. x.x.7/8 so, since the stable kde -works pretty good, how sound think to stabilize a major release of 4.9? - e.g. 4.9.4 - instead aof proposed 4.9.1 - ago: the past has shown that with start of stabilization we fixed a lot -of bugs - and .1/.2 are in common the most valuable releases - johu: yes, sure, but for me, go to 4.8.5 to 4.9.1(in that case) seems -like a regression, since there will be a lot of bugs - I don't prefer agos idea - Thev00d00: reason? - ago: which bugs to you mean " since there will be a lot of bugs"? - /s/to/do/ - I think ago means upstream bugs - johu: mean usually bugs of first release - dilfridge: yes - thats why i prefer not to stable a .0 release - we're more concerned about finding Gentoo / packaging bugs, and -having two runs of stabilization inside one 4.X cycle helps there - johu: me too, but I'm only said to increase that .0 :P - ok we are finished now with 2) ? - ago: the kernel moves a lot faster than kde and they used to -have parallel development - jmbsvicetto: yes, but is just the concept to stabilize not the first -release - ago: thats what we are doing :D - ago: kde basically throws away the previour minor release when -they launch a new one. So it's very unlikely we'll get a 4.8.6 with any fixes -and 4.9.4 will likely take around 4 / 5 months - I think we should target .1 ... usually we go for .2 anyway then -:D - people will moan - they like fast fast stabilisation - :-) - keep ppc please in mind... - Thev00d00: who wants a newer kde, go to ~arch - the stable users expect minor bugs as possible - thats right! - 3. Solaris patches (5 minutes) - * We apply many patches to support Solaris, but there seems -to be no prefix - keyword. Does anyone know anything about them? If we are -supporting Solaris, - Kensington would like to push these patches upstream. Does -anyone have - access to a box to test if they are still useful? - that was kensingtons topic but we can talk about it - ago: how about this, - we now decide "490 will never go stable, we talk about 491 when -it's out for a while" - dilfridge: fine - and then we can always still say we wait for a later release - if it's too buggy. - the one problem with testing is, --*- johu is chairing - many problems for users occur when they upgrade major version --*- creffett suggests hitting people with the gavel until they move on - so, many problems we will only see once many people upgrade to 4.9 - but anyway, this is not urgent now - so let's continue - so where are the dinosaurs? - [21:40:05] 3. Solaris patches (5 minutes) - [21:40:05] * We apply many patches to support -Solaris, but there seems to be no prefix - [21:40:05] keyword. Does anyone know anything -about them? If we are supporting Solaris, - [21:40:05] Kensington would like to push these -patches upstream. Does anyone have - [21:40:05] access to a box to test if they are -still useful? - [21:40:07] that was kensingtons topic but we can -talk about it - whats about the solaris stuff? --*- creffett votes "no opinion" - well reavertm is obviously logging but away, I sent scarabeus a -reminder but got no reply yet - jmbsvicetto? --*- dilfridge thinks "remove the patches if noone is interested in a keyword" - johu: solaris? I don't know anything about it - ok then we can give kensington the go to drop it - johu: I'd ping the prefix team about that. If we get no reply, -drop them and wait for someone to cry about them ;) - ? - jmbsvicetto: good statement lets move on - 4. KDE stable subproject (10 minutes) - * Discuss the new KDE stable subproject, as proposed by ago. - ago: its your turn :P - well - I explain all in a mail sent to all, anything not clear? - or everyone didn't look at it? - how many ppl do you have gathered so far? --*- johu likes the idea but testers are not very long term motivated in -general - johu: this is the point of start for new developers interested to join -kde - in gentoo obviously - I think we can always use more people who run stable/stable -candidate and fix bugs there - because most kde devs run 9999 - I honestly don't see if there's much to gain from having -separate sub-projects for HTs and stable KDE, but if there are enough people -wanting to do stable kde work and not general HT work, then go for it - ok, since there is the time, let me re-explain for all :) - well, we don't really have an active HT group last I checked... - creffett: yes - jmbsvicetto: the HT project seems dead - creffett: but what would prevent anyone from being a member of -HT and do stable work? - obviously :D - [21:49:39] dilfridge: The last I heard, Qt was broken on -Prefix. Once that is fixed, the solaris patches should become relevant. - so the goal of kde-stable is involve people without doing ebuild quiz - jmbsvicetto: I have no problem with that, but we kind of need to -restart the project first - ago: I understand, but I don't think there's much to gain from a -stable sub-project. If you get people interested on that, I won't object, -though - Now the quiz for arch/herd tester has been changed, but I remember When -I did it for arch tester...is a pita - creffett: jmbsvicetto: johu: we could see it as an alternative -approach to HT - dilfridge: HTs did a more general job - ok - dilfridge: they also helped with patches, testing stuff, -following upstream (live) commits - jmbsvicetto: when members counts our HT project? - but to be clear, I don't have anything against a stable -sub-project. If you can gather people wanting to do that, great :) - I just find ago's idea very useful, because our kde team work is -often much focussed on the bleeding edge, and only the one guy leading the -stabilization runs the candidate - +1 dilfridge - i would vote for a more upstream oriented direction - like kdepim bug day - johu: I think there are a lot of people interested in kde (in general), -we do it for improve QA on gentoo --*- dilfridge gets a headache hearing "kdepim bug day" - take a aspirin :P - how about we start by re-establishing a KDE herd-testing group - @all: which members counts ht project? - and from there, if we have time, inclination, and interest, we make -a sub-group for stable - I know many people and AT that runs kde, they will happy to help - creffett: better not, we should really focus this on "stable" - dilfridge: why not general testers first? - so let me summarize: we have no objections, ago takes care of -establishing that group of people and updates our site - creffett: because it's getting to "undefined"... - any additions? - vague - johu: ok, I'm just asking about HT, if there are no people, we just make -it as dead? - ago++ - yes - yes - ++ - last chance, any additions? - yes - [21:57:12] dilfridge: dunno. feel free to drop all -non-upstreamed stuff. - kde-stable probably will inherit things from HT, e.g. you can ask a test -to any member and/or similar, we can document it - so, see it as an improvement from HT without quiz - sounds reasonable I think - fine - agreed - 5. Bugs (30 minutes) - * app-cdr/k3b: Excessive use of REQUIRED_USE (and wrong combination - USE="lame"+"encode") REQUIRED_USE was added, otherwise USE="-encode -lame" - does nothing. https://bugs.gentoo.org/show_bug.cgi?id=417235 - Options: - 1. Revert to original behaviour - we don't care that -USE="-encode lame" - does nothing - 2. Keep the REQUIRED_USE, but rename lame -> mp3 - 3. Drop the encode flag, but move the optional RDEPS to an elog - 4. Drop the encode flag and keep optional RDEPS (current -behaviour) - kensington is not here, any opinions? - #2 - 2 - tampakrap: you wanna rejoin? :D --*- dilfridge has no opinion - I said no! - :D - _ /msg Chanserv add #gentoo-kde tampakrap ... - i am so forgetful --*- johu votes for 2 - 2 is fine - * cmake-utils.eclass: add support for dev-util/ninja - https://bugs.gentoo.org/show_bug.cgi?id=430608 - do we want to support two different build systems? - i would vote for an new eclass that inherits cmake.eclass - I'd suggest we only allow this with I_KNOW_WHAT_I_AM_DOING - AFAIK ninja just generates make files? - nope it's a make alternative - cmake generates the files for ninja, as it generates Makefiles for -make - oh I see - actually, before we decide on this one someone should try to build -whole kde with the new generator :D - and no, I'm not volunteering --*- johu has a lot of things to compile as x86 arch member, no interest - we can add this to the eclass - I am willing to build/test stuff - +1 for applying the patch - but the generator variable should only be respected if -I_KNOW_WHAT_I_AM_DOING is set - but not willing to fix or patch anything - to avoid an insane number of bugs - imho - if there is anything to compile give me a list - :D - same as tampakrap here - I don't think I_KNOW is needed - yeah after all it needs to be set in ebuild or make.conf - but make should be preferred - even if ninja is present - for sure - agreed then? - yes - can we at least have some elog about untested backend? - or einfo - elog spam FTL - how about, - we only output a message if the build fails - must be possible somehow - then telling "please use make backend before reporting bug" - yeah, sounds good - bad idea, elog beforehands is sufficient - * app-office/calligra-2.4.3: move fonts to separate packages - https://bugs.gentoo.org/show_bug.cgi?id=427910 - for every make based package? :( - *make - didnt I close that one already - dilfridge: i know you closed the bug but i want to discuss this - argh android - ok --*- creffett thinks it's pointless to split off a few small files here for no -appreciable gain - is there an license breakage? - isn't there a license violation by splitting oxygen-icons? :) - we dont split it :P we remove svgas - tampakrap: not really since we use the bindist useflag I think... - dilfridge: I think there would be a license violation if we -didn't provide a way to get the official tarball - dilfridge: but we should probably ask licenses@ about that - from technical point of view this is a totally senseless bug.... - there is no purpose at all (you save some kbs on HD) and get with new -bumps maybe more work - we could extend LICENSE var if its needed... - the overall reaction to this bug seems to be a definite "meh." - mhm - "we are not debian" :P - le sigh - [22:24:41] New bug: https://bugs.gentoo.org/431680 -"app-office/calligra-2.5.0 has dev-db/mysql automagic"; Gentoo Linux, KDE; -CONF; nikoli:dilfridge - * www-client/rekonq-1.0: please move Nunito-Regular.ttf to separate -package - https://bugs.gentoo.org/show_bug.cgi?id=427914 - this is the related bug to the last one... - its ONE file! - same reaction - recruit the guy to do those things by himself - the question is, are these fonts already somewhere else... - tampakrap: do it - he is in #gentoo-kde btw - but even then, if versions differ we're creating the bugs from -hell - tampakrap: yes we know :] - so summarize? - summary: RESOLVED DONTCARE - cleanest way would probably be "the fonts are already in a -dedicated font package, so we depend on it and delete them locally" - but creating a new font package for one file, NO - creffett: ++ :D - and if versions differ that may lead to strange problems - so I think I'm with creffet - whats about the license problem? - that needs to be spelled out in detail first - who asks license@? - as long as we dont even know if there is a license problem, ... --*- creffett files a bug to add "DONTCARE" as a bugzie option - RESOLVED MEH - this log is public... - dilfridge: how about to involve upstream? - good luck - we can do it, and calligra upstream is usually responsive, but -before that we need to figure out if there actually IS a problem - and a gain by the move - so, anyone figure out if there is a license problem, and a gain by -the move, - and then I can talk to calligra upstream (who know me) - anybody interested? - ok i take that as no - * net-libs/libkolabxml-0.8.0[php] fails - https://bugs.gentoo.org/show_bug.cgi?id=430858 - The cause here appears to be that FindPHP4.cmake does not look in - /usr/include/php5.*. (and there is no FindPHP5.cmake). This -potentially means - that every search for PHP in cmake is broken (though it appears that -nothing - in kde-base at least has IUSE="php, explaining this not being -caught) - my turn - I've upstreamed this one, but just wanted to see if anyone else has -opinions on it - this issue is connected to kde491 stable :P - it is? - sounds good to push this upstream - its a dep of kdepim-runtime, if we solve this properly we can servce -users the feature - mmkay - well - question 1: does anyone know of a KDE package that actually -uses/deps on PHP? - not that i know.... - yes - a kdevelop plugin - kdevelop parts - yes - hm, I'll look at that - and it's working pretty well actually - tampakrap: i miss you - but basically what happens here is libkolabxml calls -FIND_PACKAGE(PHP4 5.3 required) or something to that effect - <3 - because there is no FindPHP5 module - but regardless of that, our PHP is in /usr/lib/php${PV} - there is no module in official cmake or kde packages you mean? - or noone ever wrote one? - tampakrap: no official module - a google search turned up a couple custom ones, but basically all -they did was replace "php4" with "php5" which still doesn't solve things - then ask kensington to try to push one upstream - since he is pretty known in buildsystem now - my concern here is that I don't know if there's a nice way to do -this for Gentoo's PHP style - is there a nicer way to specify the paths available than listing -every PHP minor version? (e.g. 5.3, 5.4, 5.5 when it comes out...) - creffett: good proposal from tampa, kensington knows a lot of cmake -stuff - johu: okay, will shoot him a note - creffett: not sure about that, I still remember the FindBoost pain - listing every minor version does not look dirty to me tbh - tampakrap: we then have to bump the modules every time a new PHP -comes out - other distros don't slot their php generally - if you want to avoid that, then you need to write a proper build -system first - 6. Open floor (15 minutes) - I know, deal with it - tampakrap: "deal with it" wasn't quite what I was hoping to hear :P - life is hard :) - http://dev.gentoo.org/~dilfridge/shirts-from-hell-small.jpg - so, regarding open floor, and since I missed the discussion for HT -and stable subproject - may I revive the topic? - is ago still here? - ago is chuck norris - ago: ^ - he is everwhere - (ago's highlight works only with the :) - ok so - in short - scarabeus I think invented to have HTs back then, with the first -candidate being me - but it turned out to be a failure as an idea, since people that -wanted to do ebuild stuff were fine with just overlay access - and the HT status offers a cloak only, which is bullshit - so, I decided in a previous meeting to stop that and just have a -list with overlay committers - indeed :) - and try to make them directly developers - so, if you are going to invent any sub-project again or whatever --*- johu wants reviewboard or similiar for overlay access by users - don't put any paperwork there, and try to motivate people to get -dev status directly - johu: clone the repo in gentoo's github account, there's your -reviewboard - tampakrap: that doesnt solve the problem that they can push the -official overlay - don't follow - they can send merge requests, they can easily get account without -quiz (just by asking) - so what's the problem? - just go for a moment in another place :) - btw kde is one of the best-staffed projects I know at the -moment... - anyway, I think I made my point regarding the HT subproject, feel -free to ping me for anything regarding getting new contributors - I'm interested - either to provide experience or mentor people - tampakrap: the goal is have more testing, not just rename HT project - tampakrap: my - arg - ignore me - _ /ignore johu - done - :D - ago: you want to create a project that does what exactly? - sorry for asking but you had internal discussion I suppose instead -of doing it in gentoo-desktop ml :) --*- johu will prepare kde 485 next week - take care of testing next stable version on a completely stable -environment - ok, my personal opinion is that you don't want a subproject or a -new team for that - you need to document procedure, write intergration tests maybe, -and put it somewhere under QA - and make it more general, as it doesn't seem to me something that -can be kde only - alternatively: - KDE upstream have a QA team now that test the betas when they come -out, you could ask for their suggestions and ways of working - and cooperate in order to have a good set of products BEFORE the -next major release hits distros (and ours as well) - tampakrap: but we're NOT talking about KDE betas here - tampakrap: wait, you can't know more details about it, let me explain :) - true, we are talking about QA tests before stabilization - which is something that I'm doing professionally the past 8 months -:) - we're talking about all the problems that always ONE guy had to -fix, the one gentoo-kde dev who is overseeing the stabilization and the only -one still running that version :P - tampakrap: now we have decided t ostabilize 4.8.5, so when johu will -prepare a list I will start to test and use it in the next time but I can't -ask to other member/tester to use beta or software that have potentially bugs, -because they will use it ~ as a primary system --*- dilfridge thinks we should close the meeting, his laptop battery is giving -up... - yeah sorry - dilfridge + + - we can move the discussion in gentoo-kde - no no - i have topic too - Quassel for android needs nick completion... - Thev00d00: ++ - Sput: ^ - i will start with moving defaulting KDE_SCM to git - err sorry, wrong person - any objections? - no, sounds ok - what is still in svn? - 1/3 i would guess - there you go then :-) - we'll probably have portage in git before they finish - Thev00d00: afaik it has if you long-tap the search button or something - kdegames for example, but svn2git rules are heavily in construction - since the upstream migration is far over 50% then, I see no -problem with switching default - ok thanks] - Sput: it works! my word :-) - meeting is over, thanks to all - johu: thanks for chairing :D - G'nite all diff --git a/meeting-logs/kde-project-meeting-log-20120927.txt b/meeting-logs/kde-project-meeting-log-20120927.txt deleted file mode 100644 index 256c308..0000000 --- a/meeting-logs/kde-project-meeting-log-20120927.txt +++ /dev/null @@ -1,260 +0,0 @@ -[21:02:16] http://wiki.gentoo.org/wiki/Project:KDE/Meeting/2012-09 -[21:02:21] !herd kde -[21:02:22] (kde) abcd, ago, alexxy, creffett, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, tampakrap, thev00d00 -[21:02:25] 1. roll call -[21:02:26] present -[21:02:32] hello boys -[21:02:33] -*- johu here too -[21:03:56] --> scarabeus (~scarabeus@gentoo/developer/flyingspaghettimonster/scarabeus) hat #gentoo-meetings betreten -[21:04:03] so what is turnabout today? -[21:04:20] 4 ppl as last time... -[21:04:24] nice cloak. -[21:05:06] if i look to the herd member list there is something wrong -[21:05:17] I even announced it this time -[21:05:22] iknow -[21:05:29] well some cant attend, like jorge -[21:05:35] --> tampakrap (~tampakrap@gentoo/developer/tampakrap) hat #gentoo-meetings betreten -[21:05:38] ahoj -[21:05:43] nazdar -[21:05:58] nadrazi -[21:06:16] thats, railwaystation -[21:06:20] I know -[21:06:23] good -[21:06:35] pristi zastavka, nadrazi liben -[21:06:45] or pristi stanice -[21:06:54] never managed to separate them -[21:07:12] --> B-Man (~aaron@108.171.119.130) hat #gentoo-meetings betreten -[21:07:13] they are synonyms -[21:07:16] so they are the same -[21:07:23] but mhd says zastavka -[21:07:32] the teacher told me that one is the subway station and the other is ground station (metro, bus) -[21:07:57] tehcnically stanice could be a building and zastavka something small like the box with the sign -[21:07:59] so yea -[21:08:26] and what does the metro say btw? -[21:08:43] fucking not sure -[21:08:43] --> Thev00d00 (~v00d00@gentoo/developer/TheV00d00) hat #gentoo-meetings betreten -[21:08:48] hello -[21:08:50] i ignore it for few years already -[21:08:52] hello Ian -[21:08:55] sorry I'm late -[21:09:00] Jsem černý řidič -[21:09:02] anastum? -[21:09:13] johu: nerozumim -[21:09:45] a nastup, found it -[21:10:11] johu: I am black driver? :D -[21:10:18] scarabeus: yes -[21:10:38] google translate -[21:10:44] Ukončete prosím výstup a nástup, dveře se zavírají -[21:11:54] i always wanted after this message see emergency hydraulic close as i seen on tank -[21:12:01] woosh, click, scream, blood, ... :D -[21:12:23] bullshit -[21:12:43] <-- B-Man (~aaron@108.171.119.130) hat das Netzwerk verlassen (Quit: Konversation terminated!) -[21:13:07] but it closes so slowly :-) -[21:13:30] --> mrueg (~mrueg@rueg.eu) hat #gentoo-meetings betreten -[21:13:41] drunken ppl approved -[21:15:00] johu: i would say you wont get more people ;) -[21:15:15] !herd kde -[21:15:17] (kde) abcd, ago, alexxy, creffett, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, tampakrap, thev00d00 -[21:15:20] 1. roll call -[21:15:58] present -[21:16:04] ahoj -[21:16:04] . -[21:16:07] here -[21:16:34] ! -[21:16:38] beep -[21:16:48] hi -[21:16:51] 2. Elect new herd lead -[21:17:30] cue question of how many herd leads to have -[21:17:35] any nominees beside mee? -[21:18:01] johu: you still want to find someone else to do it huh? :D -[21:18:27] scarabeus: sure! -[21:18:29] johu: If you want not much active lead I can do it, but be sure I wont be proactive :D -[21:18:36] not me. -[21:18:54] ok second nominee scarabeus -[21:19:04] scarabeus and johu both lead would be awesome -[21:19:05] I vote johu -[21:19:16] how about have two leads? -[21:19:24] how about 6? -[21:19:25] scarabeus is to old and grouchy -[21:19:29] we'll have plenty of backups -[21:19:41] -*- johu votes for scarabeus -[21:19:55] ago: you need only one for the outside comunication, with devrel, recruiters, etc -[21:20:30] Thev00d00: the word is Grumpy :P -[21:21:23] -*- tampakrap votes for johu -[21:21:42] -*- tampakrap points out that scarabeus is saying *censored*, no leads are required actually -[21:21:55] tampakrap: do you re-joined? -[21:22:01] -*- creffett votes for johu -[21:22:04] tampakrap: only LEAD can approve new members for recruitement -[21:22:14] no idea, I was highlighted for the meeting :) -[21:22:18] tampakrap: and that is the reason why we started with leads :D -[21:22:22] plus I have nothing to do right now :) -[21:22:28] tampakrap: ok your vote will be counted -[21:22:30] in 2k9 with jorge -[21:22:37] we didnt have one for like 2 years before :P -[21:22:50] I really have to disagree, even team members is vague -[21:22:56] scarabeus / ago please vote -[21:23:06] -*- scarabeus votes johu -[21:23:15] -*- ago votes johu -[21:23:26] johu: didn't help ya :P -[21:23:29] for example, you've been doing heavy kde work (eg wrote the cmake eclass) way before joining as official developer -[21:23:31] i see -[21:23:41] -*- mschiff votes johu -[21:23:51] how does your opinion in that state count less than any other (inactive?) member -[21:24:20] ok vote finished -[21:24:30] 3. KDE 4.9 stabilization (15 minutes) -[21:24:40] Possible blocker, please discuss and vote: -[21:24:45] kde-base/konsole-4.9.0 - freezes on double-click (bug #430286) -[21:24:46] johu: https://bugs.gentoo.org/430286 ">=kde-base/konsole-4.9.0 freezes on double-click"; Gentoo Linux, KDE; UNCO; Martin.vGagern:kde -[21:24:51] - kde-base/nepomuk-core-4.9.1 - constantly segfaults after login into kde (bug #435112) -[21:24:52] johu: https://bugs.gentoo.org/435112 "kde-base/nepomuk-core-4.9.1 constantly segfaults after login into kde"; Gentoo Linux, KDE; UNCO; bu9zilla:kde -[21:24:56] kde-base/kmail-4.9.1 - problems creating imap folder (bug #434156) -[21:24:58] johu: https://bugs.gentoo.org/434156 "kde-base/kmail-4.9.1: Problems creating imap folder"; Gentoo Linux, KDE; CONF; dilfridge:kde -[21:25:18] so vote finished without celebration? -[21:25:22] you must be kidding me -[21:25:34] my gf will celebrate me -[21:25:41] -*- tampakrap CONGRATULATES HIS MENTEE JOHU AND OPENS ANOTHER KOZEL!!! -[21:25:54] congrats johu ;) -[21:26:01] thanks -[21:26:25] tampakrap: kozel means what? -[21:26:27] johu: we can give you a badge :P -[21:26:31] johu: beer brand -[21:26:38] johu: first two are blockers -[21:26:47] johu: the kmail is not critical even tho annoying -[21:27:17] then i have 2 bad messages from upstream no progress on the 2 blockers for 492 -[21:27:36] johu: good luck as lead =) -[21:27:51] ago: sure, i will need it -[21:28:21] johu: so, I'd say to wait 493 -[21:28:50] ago: or wait for fix and backport to 492 if there is a solution in the meantime.... -[21:29:05] not a bad idea.. -[21:29:18] well i would like 4.9 as it fixes few bugs i am experiencing -[21:29:25] in all cases we need upstream fix before decide and do anything -[21:29:41] but not over everything, so the blockers could be backported but we should not proceed without them -[21:30:20] scarabeus: 100% ack -[21:30:56] ok, i will watch upstream and ping back if there is a fix -[21:31:07] a cannot reproduce 430286 here -[21:31:48] mschiff: me neither but its acked by arch users as well, happens from time to time -[21:32:10] * Status report of kde stable subproject (ago / creffett ) -[21:32:39] well -[21:32:51] the page project is up and appears complete -[21:32:53] http://www.gentoo.org/proj/en/desktop/kde/kde-stable/index.xml -[21:33:19] I asked via query feedback to johu creffett scarabeus tampakrap Thev00d00 and seems fine -[21:33:45] I want to raise two objections here though -[21:33:48] And using current git kdepim (well two days old or three) and akonadi 9999 I cannot reproduce 434156 -[21:34:04] I will fix it time to time If I will notice there is e.g. the same thing not clear for more than one people -[21:34:13] 1) this subproject does NOT need a separate alias, it does NOT need an alias even, just use gentoo-desktop ml -[21:34:47] tampakrap: what is the "cost" associated with making a new alias? -[21:35:01] no cost, and I am not talking as infra now -[21:35:08] I'm talking as a guy interested in that stuff -[21:35:09] tampakrap: this subproject can also ack on other kde-* stable request -[21:35:30] so, my opinion is that all the moves of those guys should be 100% public, thus ml is the best option here -[21:35:57] (which is a principal of gentoo) -[21:35:58] ago: sorry, I don't understand what you mean -[21:36:03] or I don't see your point -[21:36:22] tampakrap: if we have people interested in this stuff, why they must follow gentoo-desktop? -[21:36:47] instead of read only the possible mail sent from bugzilla -[21:36:54] you see it totally wrong -[21:36:57] let me elaborate -[21:37:15] there is a number of guys interested in testing/doing basic qa in kde -[21:37:26] they can 1) follow the kde bugzilla account -[21:37:36] 2) coordinate their efforts in #gentoo-kde channel -[21:37:50] 3) communicate in gentoo-desktop mailing list -[21:37:58] this way you have the following advantages: -[21:38:07] 1) people follow the official gentoo-kde team work -[21:38:23] 2) people use the same communication means as the gentoo-kde team does -[21:38:40] tampakrap: for first 1 you mean add them on kde@gentoo.org ? -[21:38:46] 3) people don't have private communication media, so all of their work is public -[21:39:12] having them to follow the official getnoo-kde work and media makes them closer to the team, thus closer to becoming full getnoo devs which is the goal -[21:39:35] and NO I am not talking about adding them to kde alias, following the kde bugzilla account is different than adding them to the kde alias -[21:40:22] that's all from me, flame on -[21:41:07] ago: i updated the page as we talked about the english -[21:41:32] tampakrap: probably you know that the bureaucreacy in gentoo is not well at all. So the goal here is take advantage of the normal user that using kde and 1) don't like to become a dev 2)don't have the time or don't want follow the ML and IRC -[21:42:11] I strongly disagree here, the procedure in becoming a gentoo developer is one of the best things we have imho -[21:42:26] and I prefer it 100% to the one that for example upstream kde has -[21:42:55] me too, but there are a lot of people that disagree with you and me -[21:42:55] and I still don't see your point, if they don't want to become full developers they won't, noone is pointing guns to heads -[21:43:31] let me explain the point -[21:44:02] if you want become a dev, usually you are interested to follow IRC, bugzilla, ML -[21:44:33] if you are not interested to do it and we say: you must follow them, the response from the user will be: do it by yourself -[21:45:28] and nobody will populate the subproject -[21:45:46] from kde parent herd i want to get feedback of the subproject, if you can handle that i am fine with the non-standard communication -[21:46:23] I see it now, you are creating a project for people that are not interested in becoming gentoo developers -[21:46:34] tampakrap: yes -[21:46:38] and with that project you don't want to motivate or change their mind -[21:46:52] then sorry but I will have to go on the other side an not support your project -[21:47:12] who are interested to do it can start with arch tester or directly with dev -[21:47:15] if people don't care about becoming gentoo developers (which in my little blue eyes means "no interest in the distro") -[21:47:21] then I don't care about them either -[21:48:00] sorry, still disagree with that move -[21:48:06] tampakrap: I'm thinks the same but you need to think at one point. -[21:48:44] If I can 'devolve' to gentoo 2h per day, I can think to become a dev -[21:49:12] If I have not time to do it, but I can help using everyday KDE unstable, I can contribute without lose time -[21:50:01] sorry, don't agree -[21:50:19] and I said why I don't agree, and I don't want to repeat myself -[21:50:55] this is fine, but does not mean we will not do it -[21:50:59] so, good luck with that, I see your point of creating that project, but I am making it clear that I don't want to support it -[21:51:19] no, that means that you are going forward normally, and I will shut up -[21:51:25] ok anything else, beside that? -[21:52:54] tampakrap: we have a lot of way to join gentoo and go to become dev, this is the only one that will not do it. We will see what will happen, and in case change the rules or what is needed -[21:53:00] lets see how this is working when we have the next stable candidate -[21:53:30] 4. EAPI 5 eclass support (15 minutes) -[21:53:41] Discuss the needed changes. -[21:55:13] scarabeus: you are council member and have a good overview about the eclasses and the new features -[21:58:21] sub slots and slot operator deps are new -[21:58:22] johu: you guys dont need to change much -[21:58:58] only the slot operators might be usefull and implemented -[21:59:20] but basically enhancing the eapi case for 5 will break nothing -[21:59:50] ok i will enable it after 492 bump in overlay -[22:00:36] is it implemented in portage yet? -[22:00:42] is there an example of the slot operators? -[22:00:46] Thev00d00: yes -[22:01:32] I was looking at: http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=blobdiff;f=eapi-cheatsheet.tex -[22:01:40] alpha130 and the appropiate ~version -[22:02:49] 5 Bugs (10 minutes) -[22:02:58] dev-util/cmake-2.8.6-r4 - stop Xvfb after failed test phase (bug #406353) -[22:02:58] This occurs because VIRTUALX_COMMAND could be a bash function that dies, and virtualx.eclass does not use nonfatal. -[22:02:58] Discuss the patch - could there be any fallout? -[22:02:59] johu: https://bugs.gentoo.org/406353 "dev-util/cmake-2.8.6-r4 - stop Xvfb after failed test phase"; Gentoo Linux, KDE; UNCO; toralf.foerster:kde -[22:03:47] if you dont disaggree, i think this can be skipped was added by kensington and has already the ack from x11 herd and a user (Franz Fellner) -[22:06:00] silence = ack for the patch? -[22:06:39] no opinion here, didn't look all that closely -[22:07:26] looks sensible to me -[22:08:51] same as creffett -[22:09:04] kde-base/kdebase-pam should use system-local-login instead system-auth in their pam.d files (bug #422495) -[22:09:04] User session is not created when using systemd -[22:09:04] Discuss and vote on proposed changes in duplicated bug (bug #433173) -[22:09:15] johu: https://bugs.gentoo.org/422495 "kde-base/kdebase-pam should use system-local-login instead system-auth in their pam.d files"; Gentoo Linux, KDE; UNCO; egorov_egor:kde -[22:09:17] johu: https://bugs.gentoo.org/433173 "kde-base/kdebase-pam please enable systemd seat using system-local-login"; Gentoo Linux, KDE; RESO, DUPL; eulenreich:kde -[22:09:52] -*- Thev00d00 has no opinion on this one -[22:10:27] has anybody tested if there were any impacts when not using systemd? -[22:10:58] the question is is anybody using systemd and can do the positive test? -[22:14:02] mschiff: is not stable atm I'd say no -[22:16:19] hm] -[22:17:53] ok we will add this after 492 in overlay and ask for testing -[22:18:05] any objections? -[22:18:18] <-- creffett (~creffett@gentoo/developer/creffett) hat das Netzwerk verlassen (Ping timeout: 240 seconds) -[22:19:19] sounds sensible. I guess the guys on the bug can report the positive, we can check without sysd -[22:19:38] go ahead -[22:19:39] johu: no -[22:19:44] ok -[22:20:01] last but not least -[22:20:02] Open floor (15 minutes) -[22:20:11] 6 -[22:20:12] Thev00d00: we will found a way to test :=) -[22:21:34] and i rush for bed i wake up early tmrw -[22:21:36] so cya -[22:21:45] sweet dreams -[22:22:57] --> creffett (~creffett@gentoo/developer/creffett) hat #gentoo-meetings betreten -[22:23:12] i will do the summary (first time in wiki) -[22:23:29] <-- reavertm (~reavertm@gentoo/developer/reavertm) hat das Netzwerk verlassen (Ping timeout: 246 seconds) -[22:23:52] will need feedback because we have to port the old summaries to the wiki after that too -[22:24:48] anything else? -[22:24:55] can't we just link to them? seems like wasted effort toporrt -[22:25:01] to port -[22:25:23] but nope -[22:25:27] i dont want to have 2 places for that... -[22:25:58] you don't, you have a current and an archive :-) -[22:27:23] i will find a minio..eh volunteer for this work -[22:28:35] -*- creffett volunteers kensington -[22:28:51] last chance to raise your voice -[22:29:46] ok next meeting in 3 weeks, maybe with a new stable candidate... -[22:30:49] thanks all meeting is over \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-log-20121108.txt b/meeting-logs/kde-project-meeting-log-20121108.txt deleted file mode 100644 index 2735ef7..0000000 --- a/meeting-logs/kde-project-meeting-log-20121108.txt +++ /dev/null @@ -1,119 +0,0 @@ -[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 diff --git a/meeting-logs/kde-project-meeting-log-20130117.txt b/meeting-logs/kde-project-meeting-log-20130117.txt deleted file mode 100644 index b01d24d..0000000 --- a/meeting-logs/kde-project-meeting-log-20130117.txt +++ /dev/null @@ -1,212 +0,0 @@ -[19:58:11] * dilfridge has changed topic for #gentoo-meetings to: "Gentoo Meetings | FOSDEM talk -> #gentoo-fosdem ! | KDE team meeting 17 Jan 1900 UTC http://wiki.gentoo.org/wiki/Project:KDE/Meeting/2013-1" -[19:58:46] --> creffett (~creffett@gentoo/developer/creffett) hat #gentoo-meetings betreten -[20:04:33] (kde) abcd, ago, alexxy, creffett, dastergon, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 -[20:04:38] 1. roll call -[20:04:46] -*- dastergon is here -[20:04:51] -*- mschiff here -[20:04:52] -*- dilfridge here -[20:05:02] -*- creffett is here -[20:05:50] -*- alexxy partialy here -[20:06:05] wow, we actually reached our minimum for a meeting -[20:06:11] I may faint. -[20:06:35] I'll give a couple more minutes for any stragglers, then we'll get started -[20:08:41] -*- alexxy need some sleep, group theory is cool but... -[20:08:49] I'm here and late :-) -[20:09:04] also cooking ;-) -[20:09:11] good enough for me, let's get this show on the road -[20:09:32] 2. Keywords -[20:09:59] <-- EM3RY (~quassel@204.12.167.10) hat das Netzwerk verlassen (Ping timeout: 248 seconds) -[20:10:07] we dropped ppc64, but do we want to add any stable/testing keywords? -[20:10:36] -*- creffett would be interested in getting arm stabilized at some point -[20:11:38] --> dMaggot (~user@201.227.175.3) hat #gentoo-meetings betreten -[20:13:17] creffett: +1 -[20:15:23] 3. CMake minimum requirement -[20:15:35] kdelibs-4.10 will require CMake 2.8.8 as a minimum. Should we bother enforcing this (given that 2.8.9 is already the lowest version in-tree)? If so, where - kdelibs, KDE eclass, or even CMake eclass? -[20:16:12] err sorry got distracted -[20:16:23] arm is great -[20:16:51] re 3) I'd say kde eclass -[20:16:54] just to make sure -[20:17:21] +1 for 3 -[20:17:48] cmake-utils.eclass says CMAKE_MIN_VERSION="${CMAKE_MIN_VERSION:-2.8.4}" -[20:17:58] maybe it's reallly easiest there -[20:18:09] (change the default min version to 2.8.8) -[20:19:01] sounds good to me, I'll go make that change -[20:19:03] +1 -[20:19:24] +1 -[20:19:44] 4. Bugs -[20:19:56] --> lmiphay (~lmiphay@86-45-44-228-dynamic.b-ras2.prp.dublin.eircom.net) hat #gentoo-meetings betreten -[20:19:58] x11-themes/oxygen-gtk: Rename x11-themes/oxygen-gtk to x11-themes/oxygen-gtk2. Import x11-themes/oxygen-gtk3 from the overlay or we keep x11-themes/oxygen-gtk with 2 slot and rename x11-themes/oxygen-gtk3 to x11-themes/oxygen-gtk. -[20:20:21] basically, split it or slot it? -[20:21:07] what does gnome team say? -[20:21:21] I don't know if we've asked gnome team -[20:21:35] they should know best -[20:21:55] okay, will ask them -[20:21:55] x11-libs/gtk+ itself uses slots.. -[20:22:40] I know that some packages have weird methods of handling gtk+ 2 vs. 3 -[20:22:57] *shrug* -[20:23:12] we'll ask GNOME team about it -[20:23:17] media-libs/qt-gstreamer - split out QtGlib (bug #439198) discuss, vote -[20:23:38] I wrote upstream about that -[20:23:53] and another question I had (basically gstreamer 1.0 support) -[20:24:02] unfortunately haven't got a reply about it -[20:24:09] okay -[20:24:19] I actually have a similar problem -[20:24:29] I'm using gstreamer 1.0 from the gnome overlay -[20:24:37] and haven't been able to update telepathy ever since -[20:25:00] I personally am not in favor, my comments are on the bug but basically I think that it's making things needlessly complex and if upstream eventually does split it out we'll write an ebuild then -[20:25:08] can we differ this decision at least for a coumple of weeks? -[20:25:18] I'll try to ping upstream about this again in the weekend -[20:25:32] sounds good to me -[20:25:41] any further comments on this one? -[20:25:50] I'll take that item and will inform of any updates -[20:26:11] okay -[20:26:19] kde-misc/polkit-kde-kcmodules: Store polkit configuration changes to /etc instead of /usr (bug #438790) Discuss/vote: long-term solution -[20:26:24] -*- creffett shudders at this one -[20:26:53] here, the main question is "what does upstream think" -[20:27:14] there was a thread about it on the release list some time ago -[20:27:18] mhm -[20:27:33] there was no response on the upstream bug itself -[20:27:51] imo nothing but the package manager should ever change anything in /usr -[20:28:33] I think I summarized the responses from the list a couple meetings ago, but the general idea was that a bunch of distros have their own custom patches to change things, and upstream basically said "uh, why are we still doing this if everyone patches it out" -[20:29:41] and sometimes they learn from it and fix it -[20:30:16] and they said that in Frameworks 5 you'll be able to export XDG_CONFIG_DIRS to specify these things -[20:30:32] there are actually two issues here, since kdm does the same thing -[20:31:33] and for that, a number of distros just symlink /usr/share/config/kdm to /etc/kde/kdm -[20:32:33] that's because kdm doesn't use kconfig for its settings -[20:33:00] --> toralf (~toralf@d227155.adsl.hansenet.de) hat #gentoo-meetings betreten -[20:34:16] <-- toralf (~toralf@d227155.adsl.hansenet.de) hat das Netzwerk verlassen (Quit: Konversation terminated!) -[20:34:35] note that all of the proposed solutions were for main KDE, not polkit-kde-kcmodules, the general consensus on that one was "we're not shipping it" -[20:34:41] so...opinions on what to do? -[20:36:30] does it fix a bug? -[20:36:48] https://bugs.gentoo.org/show_bug.cgi?id=438790 -[20:37:50] it has a temporary fix of CONFIG_PROTECT, but no long-term fix -[20:38:36] how about symlinking this to somewhere in /etc? -[20:38:49] could work -[20:38:55] I'll experiment with that and report back -[20:39:19] Change the default DB backend for app-office/akonadi-server (bug #441596) Discuss/vote: there are some comments that the mysql backend brings improved stability/performance -[20:40:03] any input here? this seems like one that needs reavertm's input -[20:40:36] I've found that mysql is much better -[20:40:49] that is on a high power desktop -[20:41:01] but stability wise much nicer -[20:41:29] I am using postgres as backend... but I would not make that the default ;) -[20:41:43] you all know the kde wiki page about this? -[20:41:50] I don't -[20:41:53] moment -[20:42:20] http://techbase.kde.org/Projects/PIM/Akonadi/Database -[20:43:50] okay -[20:44:00] hmm well I would say make mysql default -[20:44:01] only real problem with the "full databases" as mysql or postgresql is that e.g. a laptop crash (dead battery) may leave you with a broken database -[20:44:14] agreed -[20:44:17] but then, you basically only lose a cache, so why bother -[20:44:24] vote: make mysql the default backend? -[20:44:25] +1 -[20:44:27] +1 -[20:44:35] not with goto settings, no -[20:44:42] s/goto/good/ -[20:44:56] mschiff: what do you mean? -[20:45:06] YOu can configure postgres to be safe -[20:45:25] --> tampakrap (~tampakrap@gentoo/developer/tampakrap) hat #gentoo-meetings betreten -[20:45:26] to be protected agains broken database -[20:45:33] hi -[20:45:37] ah ok -[20:45:40] hi dad -[20:45:43] because of battery problem etc -[20:46:02] hi tampakrap -[20:46:36] mschiff: ok so you say, the crash problem is not fundamental -[20:46:43] I had mysql running for quite a long time with akonadi on my laptop and never had an issue with it -[20:46:46] ok -[20:46:48] right -[20:47:23] and I *had* cases where it crashed or I had to switch it off the hard way -[20:47:26] so again -[20:47:31] vote: make mysql the default backend? -[20:47:37] +1 -[20:47:40] +1 -[20:47:50] +1 -[20:47:57] +1 -[20:48:00] cool -[20:48:16] remember changing the default useflag settings in the ebuild... -[20:48:23] I'll note it on the bug -[20:48:37] -*- dilfridge thinks this will improve our relations to the kdepim guys -[20:49:05] is it that bad? 8-) -[20:49:06] dilfridge: and maybe with the improved relations you can do something about kmail? ;) -[20:49:14] sigh -[20:49:20] what do you want, a miracle? -[20:49:39] app-office/akonadi-server-1.9.0: add Qt 5 support (bug #450412) How do we want to start rolling out qt5 support in general? -[20:49:47] I already thought of porting kmail-4.4 to kdepim-4.10 -[20:50:17] I am looking at the git logs of kdepim quite often... they are really doing a lot in fixing bugs since some time... -[20:50:53] our overlay has a kmail-4.4.11.1-r100.ebuild, that is my personal playground -[20:51:03] (does not build right now) -[20:51:05] as I understand it, qt4 versus qt5 has to be global, you can't have both at once -[20:51:29] bastards -[20:51:52] haven't tried qt5 yet (I masked it) but I don't think one blocks the other (in terms of ebuilds, don't know about builds) -[20:52:17] there are some comments in the bug about how you can't have, say, qt5 libs and a qt4 consumer -[20:52:45] question number 1: should we start adding qt5 support? -[20:52:49] right, that's the type of issues I would expect: you probably would have to rebuild everything to use one or the other -[20:53:00] <-- ABCD (~quassel@gentoo/developer/abcd) hat das Netzwerk verlassen (Ping timeout: 245 seconds) -[20:56:02] any comments? -[20:56:18] --> ABCD (~quassel@gentoo/developer/abcd) hat #gentoo-meetings betreten -[20:56:38] how? -[20:57:04] adding the USE flag to packages that have support? -[20:57:05] what? -[20:57:23] but KDE SC itself will not support qt5 right? -[20:57:33] (4.xx) -[20:57:53] did qt team say anything how they want the useflags? eg. either qt4 or qt5, or only a qt5 useflag that disables qt4 support, or... ? -[20:58:09] -*- creffett adds this one to the "talk to other teams" list -[21:00:00] 5. Open floor -[21:00:05] afterwards kde will need akonadi[qt4] or akonadi[-qt5] -[21:00:07] yeah -[21:00:18] someone please tell the qt guys not to be ridiculous -[21:00:29] a category "qt" is a joke -[21:00:30] -*- creffett nominates kensington in his absence -[21:00:43] "qt-base" if anything :D -[21:00:50] no, the joke is suggesting dropping the qt-prefix -[21:01:00] noooo at is much better -[21:01:05] bug 450818 is goint to bite our... well, you know, our feet -[21:01:10] *qt -[21:01:23] qt/core, qt/dbus, etc., etc....sure, let's just drop a bunch of name collisions into the tree -[21:01:33] there's still no nswer fro teh qt team, from qt upstream, etc -[21:03:43] dMaggot: pesa's question should be answered (re: where is it from, has it been upstreamed) -[21:04:47] https://bugreports.qt-project.org/browse/QTBUG-29082 -[21:05:05] <-- ABCD (~quassel@gentoo/developer/abcd) hat das Netzwerk verlassen (Ping timeout: 245 seconds) -[21:06:08] works for me -[21:06:42] creffett: right, I should have updated the bug with that info -[21:06:50] dMaggot: just done -[21:07:00] what else do we have for open floor business? -[21:07:26] cookie distribution -[21:07:36] fine -[21:07:40] cookies to all who attended -[21:07:56] -*- dilfridge munching -[21:07:57] and some cookies for tampakrap's baby -[21:08:10] plasma-active is about half packaged in my local overlay so far -[21:09:03] --> ABCD (~quassel@gentoo/developer/abcd) hat #gentoo-meetings betreten -[21:09:27] I'm still trying to figure out how to package "maliit", which is a dep of one of the packages which provides the input method framework (if anyone has a good example of a package that is configured by way of qmake, please let me know) -[21:10:39] eww -[21:10:42] but other than that it's nearly ready to hit the overlay, though I'm not going to package the patches until the next Active release because they don't apply to latest KDE and I really don't want to respin a few hundred line long patch -[21:10:56] I'll probably be putting it in category plasma-active -[21:11:13] push it! and then write to -dev and request kde-active category... -[21:11:40] it can wait until we've actually tested the packages :) -[21:11:58] plasma-active is less easier understood than kde-active I'd say... -[21:12:09] yeah, but the official name upstream is plasma active -[21:12:20] :| -[21:12:27] eh, we can bikeshed it once I'm finished packaging -[21:12:28] they are really branding specialists -[21:12:48] mhm -[21:13:09] any other business for open floor? we still have time -[21:13:19] kde-plasma-active? -[21:14:08] Is anybody else using the 49.9999 packges? -[21:15:15] mschiff: no but I'm already on .98 -[21:15:25] k -[21:15:34] just for the record -[21:15:58] I had a good time using 4.9.49.9999 and will keep to do so with 4.10 (already do) -[21:15:58] mschiff: kensington: btw the pykde4 patch that I added does not help, I still get a sandbox violation -[21:16:08] in pykde4-4.9.98 -[21:16:20] there is one more commit that could cause it -[21:16:28] -> weekend or anyone else -[21:16:59] kensington is working on porting all python dependencies to python-r1.eclass btw -[21:17:09] nice -[21:19:39] I don't envy him that -[21:20:58] nothing else? /me finds a gavel -[21:21:17] *bam* meeting adjourned -[21:21:27] yeah yeah yeah :) -[21:21:46] ;) -[21:21:53] * dilfridge has changed topic for #gentoo-meetings to: "Gentoo Meetings | FOSDEM talk -> #gentoo-fosdem !" \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-log-20130321.txt b/meeting-logs/kde-project-meeting-log-20130321.txt deleted file mode 100644 index 98ea3da..0000000 --- a/meeting-logs/kde-project-meeting-log-20130321.txt +++ /dev/null @@ -1,368 +0,0 @@ -[20:02:32] !herd kde -[20:02:32] (kde) abcd, ago, alexxy, creffett, dastergon, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 -[20:02:41] roll call: -[20:02:47] -*- ago obviously here -[20:02:51] * dilfridge has changed topic for #gentoo-meetings to: "Gentoo Meetings | KDE team meeting Thu 21/Mar/2013 19:00 UTC, agenda http://wiki.gentoo.org/wiki/Project:KDE/Meeting/2013-03" -[20:03:00] -*- dilfridge obviously here -[20:03:08] -*- creffett here -[20:03:11] -*- dastergon here -[20:03:39] is needed a minimum number of people to start? -[20:03:44] 5, I think -[20:03:52] not really, more something like a minimum 5min waiting :D -[20:03:57] Do you guys need anything from me? -[20:04:09] ok, we are jmbsvicetto probably a vote for the lead -[20:04:14] err -[20:04:20] s/ok, we are// -[20:04:24] jmbsvicetto: nothing specific I think -[20:04:32] Are we voting for a new lead? -[20:04:44] yes no maybe -[20:04:47] I guess so? -[20:04:49] Shouldn't that have happened on last FOSDEM? -[20:05:12] jmbsvicetto: no -[20:05:14] we should indeed reintroduce that tradition -[20:06:20] ok, next roll call at 19:15 -[20:06:48] --> lmiphay (~lmiphay@86-45-45-142-dynamic.b-ras2.prp.dublin.eircom.net) hat #gentoo-meetings betreten -[20:07:19] kensington, creffett: since you handle the announce of the meeting in the lists, please cc kde-stable next time. -[20:07:29] well, I've been away for a long time, so you're all more qualified than me about the kde issues. I trust your opinion and will go with the majority vote -[20:07:36] lol -[20:07:52] ago: okay -[20:08:10] --> scarabeus (~scarabeus@gentoo/developer/flyingspaghettimonster/scarabeus) hat #gentoo-meetings betreten -[20:08:17] pookaboo -[20:08:24] -*- jmorgan1 here -[20:08:31] whoaa, our flyping spaghetti monster is here? O_O -[20:08:40] even the *flying* ;) -[20:09:25] -*- creffett wonders why we always have such good turnout when someone besides me sends the email :P -[20:09:26] jmbsvicetto: and we too need to plan out delivery of your camera finaly :D i am still walking around it and puting it to various shelfs... it still does not fit into czech republic :D -[20:09:50] scarabeus: hehe -[20:09:52] scarabeus: sorry about that -[20:10:11] scarabeus: If things go as well as I hope, I'll be asking you soon to send it to me ;) -[20:10:20] splendid :-) -[20:11:27] anyway, I'm sorry guys but I need to leave now. Have a good meeting -[20:13:32] ago: roll call no2 ? -[20:14:17] dastergon: just wait another min -[20:14:22] i guess ago is waiting for the clock to strike 20:15 :] -[20:14:52] http://www.portale.it/orario.php :D -[20:14:58] im going to add myself to herd -[20:15:05] any objections? -[20:15:26] !herd kde -[20:15:26] go for it -[20:15:26] (kde) abcd, ago, alexxy, creffett, dastergon, dilfridge, jmbsvicetto, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 -[20:15:30] 2° roll call: -[20:15:30] nope not here, go for it -[20:15:36] -*- ago here -[20:15:38] -*- dilfridge present -[20:15:45] jmorgan1: you can add, but still pretty female would make me more happy :D -[20:15:46] -*- dastergon here -[20:15:46] jmorgan1: you are welcome -[20:15:50] -*- scarabeus around -[20:15:51] here -[20:16:04] <-- ABCD (~quassel@gentoo/developer/abcd) hat das Netzwerk verlassen (Read error: Connection reset by peer) -[20:16:21] --> ABCD (~quassel@gentoo/developer/abcd) hat #gentoo-meetings betreten -[20:16:38] ok, we are 5, we can go ahead? -[20:16:46] ok we're 6, we go ahead -[20:17:06] 1) Project lead (5 minutes) -[20:17:30] any volunteers? -[20:17:32] Last time the vote was between johu_ and scarabeus....so is scarabeus available to do it? -[20:17:38] is there someone else? -[20:17:54] well -[20:18:04] I could, I guess -[20:18:42] creffett: go for it, everyone deserves the hat from time to time :P -[20:18:46] if the only alternative is that the current situation continues, I could do it, but I'm not infinitely happy about it -[20:19:05] creffett: excellent! -[20:19:18] ok, creffett for the lead is fine for me: +1 -[20:19:33] -*- dastergon votes creffett :) -[20:19:37] creffett++ -[20:20:07] jmorgan1: feel free to approve disapprove also if you are fresh here -[20:20:38] i concure -[20:20:40] creffett: take my sentene as ++ for you :-) -[20:20:51] okay then. -[20:20:53] jmbsvicetto: still here for the vote? -[20:21:14] that's a comfortable majority already -[20:21:31] congrats creffett ! -[20:21:36] -*- creffett bows -[20:21:40] autokick in -kde done :P -[20:21:42] cheers -[20:22:09] next point -[20:22:14] 2) KDE 4.10.1 stabilization (10 minutes) -[20:22:46] I'm all for it, it works nicely -[20:22:49] this is a rapid bug search https://bugs.gentoo.org/buglist.cgi?quicksearch=4.10.1&list_id=1622108 -[20:23:05] dilfridge: vincent/peratu reports that does not work for him on ppc -[20:23:20] i filed one bug on ppc64 -[20:23:22] and jmorgan1 reports a failure of rocs -[20:23:24] we should add the kwin (window unref) patch, it is in stable branch -[20:23:26] ;) -[20:23:52] ok, the ppc situation is a big regression -[20:23:59] the rocs problem, we cannot do much about it, it's a gcc ICE -[20:24:16] you should show it to vapier -[20:24:18] https://bugs.kde.org/show_bug.cgi?id=316988 -[20:24:25] 4.9.5 works on ppc/ppc64 -[20:25:00] jmorgan1: could you try gcc-4.7 ? -[20:25:25] sure, for rocs failure? -[20:25:28] yes -[20:25:29] jmorgan1: I usually saw this kind of error on machine with broken hw..how's the status of your? -[20:25:31] ok -[20:25:52] I will check too on my chroot -[20:26:09] yes, i'll look into both hw and gcc-4.7 -[20:26:16] any progress for arm? is the time to do it? -[20:26:55] jmorgan1: is this bug reproducible on ppc64? https://bugs.kde.org/show_bug.cgi?id=316988 you are able to use the session? -[20:27:46] eww -[20:27:50] I know that backtrace -[20:28:17] ago: i'll take a look this evening -[20:28:19] dMaggot: ^ please have a look, does that look familiar to you too? -[20:28:26] dilfridge: checking... -[20:28:38] dMaggot: you are upstream? -[20:29:44] ago: I fixed that crash in other archs -[20:30:07] the question is, why is it still around on ppc? -[20:30:19] or is it a similar but different problem? -[20:30:26] ok, I merged 4.10.1 on 2 machines...looks ok for both...my vote is yes for amd64/x86 and not now for ppc/ppc64/arm -[20:30:40] +1 -[20:30:52] +1 -[20:30:57] -*- ABCD is alive (and forgets when meetings are because they always are when he's normally supposed to be at work) -[20:31:04] sounds good (after adding kwin patch), +1 -[20:31:07] +1 -[20:31:31] +1 -[20:32:02] awesome. -[20:32:03] scarabeus: ? -[20:33:05] next -[20:33:18] wait -[20:33:26] who will open and generate the list? =) -[20:33:31] creffett: could you? -[20:34:00] ago: sure, I'll handle it tonight -[20:34:17] creffett: please also grab the kwin patch from git KDE/4.10 branch -[20:34:20] ah +1 from me -[20:34:28] i am still half page to the log :D -[20:34:33] creffett: ok, please send me and I check it with repoman before open the bug -[20:34:43] will do -[20:34:50] 3) Remove -Wl,--fatal-warnings ??? (5 minutes) -[20:35:16] that's mine -[20:35:20] It gave problems? -[20:35:30] basically we get build failures every now and then -[20:35:40] not frequently, most are on arm -[20:35:40] there have been a couple bugs lately that come from that being enabled -[20:35:56] it will NOT be removed upstream -[20:36:19] -*- dilfridge had a discussion with a couple of kde bigshots about it -[20:36:49] dilfridge: how sounds enable it with a var? -[20:36:49] usually, the linker warning should be fixed in the package, not ignored -[20:36:59] so who has problem is able to drop it -[20:37:35] not easy, because it is fixed in cmake files installed by kdelibs -[20:38:45] technically developer profile should enable it -[20:38:52] we should not enable it on desktop profile -[20:38:54] we could add some magic to the eclass that patches package cmake files and disables it on request, but that may be more pain than before -[20:38:55] ok, I have not particular vote for it, if it is needed, do it -[20:39:14] scarabeus' idea sounds ok, the question is how to best do it -[20:39:41] easiest way would be to conditionally patch kdelibs with a useflag -[20:39:50] that applies to all kde packages then -[20:42:01] -*- creffett is a bit nervous about conditional patching like that -[20:42:04] however that is not really elegant and does not do it "the Gentoo way" -[20:42:24] dilfridge: nope, just remove it from the cmake files -[20:42:30] and then append it in profile ldflags -[20:42:38] but discussion on -dev prior enabling it treewide -[20:42:44] all the linking issues are actual errors -[20:42:49] so fixing them is benefitical a lot -[20:42:56] makes sense -[20:42:58] +1 -[20:43:21] I vote with the majority -[20:43:29] -*- dilfridge thinks we need diego back before we can ever enable it treewide -[20:44:26] dilfridge: the tbox script are public :) -[20:44:40] ok, suggestion by scarabeus: remove -Wl,--fatal-warnings from cmake files and start a discussion to enable it in the dev profile treewide -[20:44:43] opinions? -[20:44:47] +1 from me -[20:45:07] +1 with the majority (as I said) -[20:45:13] you can run tbox stuff yourself, just commit it to qa-reports git repo with proper script calls, the box is done it executes by-cron everything required -[20:45:19] +1 sounds fine with me, disscussion is good -[20:45:30] what is tbox? -[20:45:49] tinderbox -[20:45:59] automated build test system -[20:46:12] +1 from me -[20:46:38] tinderbox the fear of the gentoo dev :P -[20:46:47] creffett: ^ -[20:46:58] cool, i'll look into it -[20:47:07] ago: no opinion -[20:47:09] 0 -[20:47:57] that's three yes and two "0", I guess that is a yes -[20:48:06] ok, scarabeus's suggestion is approved -[20:48:29] scarabeus: mind start the discussion on -dev? -[20:49:37] there is just an update for the ppc crash: https://bugs.kde.org/show_bug.cgi?id=316988#c3 -[20:49:44] does anyone use the dev profile? -[20:50:13] -*- dilfridge looks somewhere else -[20:50:16] creffett: I will ask vincenti if works for him, if yes I can ask qt@ if we can stabilize that version and open the bug -[20:50:40] ago: okay -[20:50:41] jmorgan1: I use default -[20:50:53] jmorgan1: not many, but still you can also add that to the default LDFLAGS in your make.conf -[20:51:00] 4) [semantic-desktop=] (5 minutes) -[20:51:08] <-- dMaggot (~user@201.227.175.3) hat das Netzwerk verlassen (Remote host closed the connection) -[20:51:10] i'll test qtcore upgrade as well, i have both ppc, ppc64 -[20:51:47] ago: no subscription to -dev -[20:51:51] ago: so i can't start the chat -[20:51:55] --> dMaggot (~user@201.227.175.3) hat #gentoo-meetings betreten -[20:52:13] ago: scarabeus: I'll do it -[20:52:34] scarabeus: subscriptions are open :P -[20:52:47] 4) [semantic-desktop=] (5 minutes) -[20:53:03] so the = on semantic desktop was because it was needed due to broken deps -[20:53:10] nowdays it is pointless as everything was fixed -[20:53:14] so you can switch to ? -[20:53:20] ok excellent -[20:53:25] anyone objecting? -[20:54:03] go for it -[20:54:11] maybe we do that with 4.10.2, so nothing big changes before the stabilization -[20:54:11] sounds good -[20:55:04] good -[20:55:14] dilfridge: +1 you right -[20:57:01] have to change rooms, brb -[20:57:10] ok cu -[20:57:12] next on the agenda? -[20:57:27] 5) Remove obsolete news entries -[20:58:12] fine for me. I'd say to leave at least the last 2011-05-22-kdeprefix -[20:58:44] if people haven't upgraded from kdeprefix by now... -[20:58:47] we should remove it, because getting kdeprefix news on a *NEW INSTALLATION* is stoopid -[20:59:10] right to -[20:59:14] o* -[21:00:32] besides kdeprefix use flag was masked since 2009 -[21:00:54] +1 for removing the listed items -[21:01:14] +1 -[21:01:26] +1 -[21:02:47] +1 -[21:03:01] Like -[21:03:56] dastergon: ^ -[21:05:17] +1 from me, cleaning old stuff sound fine -[21:05:28] s/sound/sounds -[21:05:44] ok, next point -[21:05:54] Bugs (10 minutes) -[21:06:08] x11-themes/oxygen-gtk opinion? -[21:06:31] do it the same way as gtk+, i.e. two slots -[21:10:02] sorry I don't understand it at all -[21:10:21] we already have 2 slots in tree, what we should import from the overlay? -[21:10:28] Rename x11-themes/oxygen-gtk to x11-themes/oxygen-gtk2. Import x11-themes/oxygen-gtk3 from the overlay or we keep x11-themes/oxygen-gtk with 2 slot and rename x11-themes/oxygen-gtk3 to x11-themes/oxygen-gtk. -[21:11:29] indeed you are correct -[21:11:59] probably the only thing that should be done here is delete the live ebuild in the overlay -[21:12:11] that bug it was also a topic in January's meeting -[21:12:24] ok, probably we forgot to delete it -[21:12:28] -*- creffett has to move buildings, back in 10 or so -[21:12:55] hmm when I move buildings that usually takes longer, need to find a forklift first... -[21:16:18] ok, probably all of us is busy? I don't see an active partecipation, maybe we want discuss about bugs in the next meetings ? -[21:16:23] err -[21:16:40] ago: just keep pushing :) -[21:16:44] <-- creffett (~creffett@gentoo/developer/creffett) hat das Netzwerk verlassen (Ping timeout: 255 seconds) -[21:18:12] kde-base/kde-meta ebuild improvement proposal (bug #456248, bug #460634) -[21:18:13] dilfridge: https://bugs.gentoo.org/456248 "kde-base/kde-meta ebuild improvement proposal."; Gentoo Linux, KDE; RESO, WONT; voron1:kde -[21:18:16] opinions? -[21:19:04] the attachment is not a diff :P -[21:19:06] wth -[21:19:31] the question has been asked and silence has fallen -[21:20:08] I agree with the quote "if you don't want all kde packages, you shouldn't use kde-meta". -[21:20:32] ok, real diff for all: http://bpaste.net/show/85433/ -[21:20:37] imho we could add (few, 1-2) useflags, as eg. "games" -[21:21:00] nah, too much -[21:21:21] ago: it makes sense if the useflag switches stuff off across several metas -[21:21:24] I agree with jmbsvicetto, so leave as is for me -[21:21:40] --> iamnr3 (~quassel@78.142.111.42) hat #gentoo-meetings betreten -[21:21:40] e.g. disables all games in all packages (not just kdegames) -[21:21:50] but just disabling one sub-meta makes not much sense -[21:21:55] yeah -[21:22:04] so, maybe just leave it as it is now -[21:22:10] +1 -[21:22:34] we can improve documentation to explain that -[21:22:54] or not :D -[21:23:17] scarabeus: ^ ? -[21:23:28] --> creffett (~creffett@gentoo/developer/creffett) hat #gentoo-meetings betreten -[21:24:07] -*- creffett back if meeting is still going on -[21:24:29] we couldn't end the meeting without the lead :p -[21:24:33] creffett: it is... just talking about useflags in metas -[21:24:34] i dont like uses on this -[21:24:37] oh, this one -[21:24:45] but i let you guys pick whatever rocks on your day -[21:24:53] we should prolly just propagate custom sets -[21:24:56] what was our original rationale for "no uses in meta packages"? -[21:25:01] no sets please -[21:26:53] back -[21:27:20] ok I think the best conclusion is "no additional useflags now" -[21:27:43] yes -[21:27:55] 5) +1 - remove old items -[21:28:10] -*- dastergon agrees with dilfridge -[21:29:02] +1 no useflags, I guess -[21:30:33] yo -[21:30:34] next -[21:30:44] Add 'app-arch/unzip natspec' to profiles/targets/desktop/kde/package.use (bug #457934) -[21:30:45] dilfridge: https://bugs.gentoo.org/457934 "Add 'app-arch/unzip natspec' to profiles/targets/desktop/kde/package.use"; Gentoo Linux, Eclasses and Profiles; UNCO; wyatt.epp:kde -[21:31:07] makes sense imho -[21:31:15] go for it -[21:31:22] kensington is adding useflags there anyway -[21:32:02] any further opinions? -[21:32:08] 1, -[21:32:11] 2, -[21:32:14] 3, -[21:32:17] yes -[21:32:18] seems not. -[21:32:20] yes -[21:32:41] ok -[21:32:45] remaining bugs -[21:32:47] dilfridge: is natspec enabled only for the kde profile? -[21:33:09] it would be only for the kde profile, yes, anything else needs discussion with more people -[21:33:40] I guess it should be enabled when people use kde also with other profiles, what do you think ? -[21:33:40] 5 more bugs to go, then we're finished -[21:34:04] ago: well, if we depend anywhere on unzip, we could just depend on that useflag too -[21:34:41] but we don't -[21:34:45] not in kde-base -[21:34:55] i think we should support kde profile not just kde use flag -[21:35:26] ok -[21:35:27] next bug -[21:35:41] Bug 435584 - kde-base/kdelibs - patch to fix directory icon breakage for NFS mounts since KDE 4.7.4 -[21:35:42] dilfridge: https://bugs.gentoo.org/435584 "kde-base/kdelibs - patch to fix directory icon breakage for NFS mounts since KDE 4.7.4"; Gentoo Linux, KDE; UNCO; nitro:kde -[21:36:03] basically nfs and samba are treated as slow filesystems, and icon loading is turned off. -[21:36:12] use reqests to revert that commit -[21:36:35] no real opinion here -[21:37:21] dilfridge: as said, maybe we can discuss this with more people partecipation -[21:37:24] :) -[21:37:26] ok -[21:37:36] in the grand scheme of thigns, I don't think this one matters enough to merit a patch -[21:37:39] I have a proposal as open floor -[21:37:52] so...I'd say resolve wontfix and point out that we already do support epatch_user -[21:37:59] ago: slacker marks for kde meetings? -[21:39:02] dilfridge: ahaha no. the herds contain 14 people, but in the meeting there are always few. So probably we can make a file where someone can say the time preference and in case we can review the meeting time ? -[21:39:10] e.g. kensington is unable to partecipate -[21:42:06] ok shall we close the meeting and continue next month? -[21:42:13] one more item -[21:42:18] open floor ?? -[21:42:28] im looking to stable kde-4.9.5 on ppc64 -[21:42:34] ok -[21:42:48] i think ppc is already stable -[21:43:14] bugs can be assigned to me if needed -[21:43:58] objections? -[21:44:20] jmorgan1: do it to me :) I will handle as kde-stable -[21:44:33] then since it will be stable, you are welcome as ppc64 member -[21:44:40] ago: ok, cool -[21:44:45] oh, to kde-stable? -[21:45:06] you can add as x86_64 too then -[21:45:19] jmorgan1: but, since we will stabilize 4.10.1 in few time and remove 4.9.5, make sense stabilize 495 now? -[21:45:42] well, let me test qtcore upgrade to fix rocs issue -[21:45:51] if that works, then no stable 4.9.5 -[21:45:54] just 4.10.1 -[21:46:14] i'll check in the next 24h or so -[21:46:20] jmorgan1: ok.... -[21:46:21] have an answer -[21:46:42] thx -[21:46:55] dones -[21:48:30] anything else for open floor? -[21:48:36] yeap -[21:48:36] nothing here -[21:48:48] dastergon: go ahead -[21:48:58] last weekend I put up somre repos for qt-gstreamer -[21:49:06] that split the qt-glib thing from qt-gstreamer -[21:49:14] kensington is following on the bug reports upstream -[21:49:20] no news from upstream yet -[21:49:30] for those who didn't know I joined bugday team and I am trying to revive that day -[21:49:59] I'd like to enable the bugday flag in any bugs that you think -[21:50:23] it would be good -[21:50:29] to close them that day -[21:51:55] what do you think about some herd's bugs ? -[21:52:44] -*- dilfridge thinks it's too late to think -[21:52:56] -*- creffett thinks the same, and it's only 5PM here :) -[21:53:30] i think its a good idea assuming the bugday team has reasources to resolve/track them -[21:55:36] i have to drop off - next meeting -[21:57:25] anything else for open floor? -[21:58:35] nope -[21:59:12] I'm good -[21:59:12] ago: wanna close the meeting? -[22:01:21] ok -[22:01:28] -*- dilfridge bangs on the table -[22:01:30] meeting closed \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-log-20130523.txt b/meeting-logs/kde-project-meeting-log-20130523.txt deleted file mode 100644 index 7048a7b..0000000 --- a/meeting-logs/kde-project-meeting-log-20130523.txt +++ /dev/null @@ -1,407 +0,0 @@ -[21:01:12] Hello -[21:01:16] hola -[21:01:17] I am here -[21:01:23] Hallihallo -[21:01:26] --> scarabeus (~scarabeus@gentoo/developer/flyingspaghettimonster/scarabeus) hat #gentoo-meetings betreten -[21:01:32] sup -[21:01:36] though I may be going soon, so lets get this party started :) -[21:02:50] 1. roll call -[21:03:01] !herd kde -[21:03:01] (kde) abcd, ago, alexxy, creffett, dastergon, dilfridge, jmbsvicetto, jmorgan, johu, kensington, mschiff, patrick, reavertm, scarabeus, thev00d00 -[21:03:07] here -[21:03:12] here -[21:03:15] here -[21:03:15] here -[21:03:16] -*- johu here -[21:03:18] -*- alexxy here -[21:03:32] wow, 6 people :D -[21:03:45] +scarabeus -[21:03:53] 2. Optional semantic-desktop support -[21:04:18] Some parts of KDE upstream no longer have optional support for semantic-desktop. We currently work around this by using ugly hacks but it is fragile causing bugs like bug #468104 and bug #465322. It is apparently easy to disable semantic-desktop features at runtime. -[21:04:19] johu: https://bugs.gentoo.org/468104 "kde-base/plasma-workspace-4.10.2 build error with Nepomuk2"; Gentoo Linux, KDE; CONF; christopher.smith:kde -[21:04:24] the herd is populated by 15 people...I wondering if we need to talk about the hour preference of the meeting -[21:04:29] Options: -[21:04:29] Do nothing and add more fixes/hacks as bugs crop up -[21:04:29] Track upstream more closely and support optional semantic-desktop only where supported by upstream (noting that find_package() can be controlled these days unless it explicitly has a REQUIRED) -[21:04:30] Drop semantic-desktop USE flag completely -[21:05:00] ago: wrong topic -[21:05:08] -*- dilfridge suggests "drop useflag completely and focus efforts on more worthwhile issues" -[21:05:09] -*- Thev00d00 votes for: Drop semantic-desktop USE flag completely -[21:05:17] TBH, I have kde on my netbook because of -semantic-desktop, with semantic-desktop enabled it was too much slowly...so I'd like to see it as -is -[21:05:35] ago: just disable the file indexer, then you are fine -[21:05:37] but you can disable it on runtime -[21:05:43] go with dropping -[21:05:47] nowdays it is not so broken -[21:05:50] ok lets vote -[21:05:52] and the off switch finaly works -[21:05:53] I'm also not really using semantic-desktop -[21:06:06] who is for drop? -[21:06:11] -*- ago votes do nothing -[21:06:12] -*- dilfridge is for drop -[21:06:24] -*- johu +drop -[21:06:48] and clearly also scarabeus and Thev00d00 as seen above -[21:06:59] do nothing -[21:07:23] (better would be to kill semantic-desktop, but that isn't an option) -[21:07:27] i guess kensington is for it too because he bring it up on the table -[21:07:36] ok, so lets drop -[21:07:49] jmbsvicetto: the switch now really works, so you have it built but disabled :-) -[21:07:50] ok whats the course of the action then? -[21:07:59] do we need an news item? -[21:08:06] remove the useflag in -4.10.49.9999 -[21:08:15] no in 9999 -[21:08:18] johu: no because no action on user part is required -[21:08:29] scarabeus: yeah and I also should systemd when I build udev, but don't have to use it ... -[21:08:37] -*- jmbsvicetto refrains from making more comments -[21:08:58] -*- dilfridge does not want to hear the word systemd anymore today... -[21:09:00] i would suggest to drop it with 4.11 -[21:09:16] ++ -[21:09:26] we could blog about how to disable it at runtime -[21:09:32] time enough to get the people informed by news item etcs -[21:09:36] dilfridge: good idea -[21:10:18] ok i will blog about it -[21:10:48] we can decide on a news item in the next meeting (june) -[21:11:49] any other actions we need to do for the drop? -[21:12:21] simplify code, afterwards -[21:12:35] check dependencies in external packages -[21:12:54] [semantic-desktop] -> [semantic-desktop(+)] -[21:13:06] (we can already do that now) -[21:13:25] yes -[21:13:47] 3. Drop oldpim? -[21:14:12] yes / no / maybe -[21:14:12] mask now immediately? -[21:14:12] See also this link http://dilfridge.blogspot.de/2013/05/personal-experience-and-opinion-kmail2.html -[21:14:12] against -[21:14:19] yes -[21:14:20] i.e. no -[21:14:36] sorry, -EDON'TCARE -[21:14:36] we do not gain much by dropping it -[21:14:47] -*- Thev00d00 -EDON'TCARE -[21:14:57] (the only real cruft is the -l10- splitting) -[21:15:16] its not much effort to keep it in tree, so also EDON'TCARE -[21:15:19] impact on eclasses is 0 -[21:15:33] real question, is there someone that uses it? -[21:15:42] me :) -[21:15:45] from the comments yes -[21:15:57] --> reavertm (~reavertm@gentoo/developer/reavertm) hat #gentoo-meetings betreten -[21:16:10] dilfridge: what is the state about the bugs you blogged before? -[21:16:21] kleopatra works fine again -[21:16:26] ago: I don't use kdepim and only have parts of it installed because of semantic-desktop -[21:16:34] the other stuff still exists but is nonfatal -[21:16:45] I meant if there is someone apart dilfridge -[21:17:01] only real bug is that you can't set sent mail folder per identity anymore -[21:17:09] --> mschiff (~mschiff@gentoo/developer/mschiff) hat #gentoo-meetings betreten -[21:17:16] ^ ^ -[21:17:51] --> Guest43157 (46c082af@gentoo/developer/creffett) hat #gentoo-meetings betreten -[21:17:54] i would suggest as everytime it comes on table, lets wait until its not working with new kde sc release -[21:18:18] any objections, if not i move to the next topic -[21:18:21] ? -[21:18:41] yep. postpone. if anything pops up, assign bug to me with kde in cc -[21:18:46] <-> Guest43157 heißt jetzt creffett|mobile -[21:19:04] 4. Handling of systemd patches -[21:19:10] let's just agree on a consistent way of handling it (as long as noone from kde team runs systemd) -[21:19:19] I run it -[21:19:23] :) -[21:19:25] Yay -[21:19:25] -*- creffett|mobile is here, sorry. Dinner running late -[21:19:40] i already run it on my netbook -[21:19:43] If there is somthing to test, feel free to cc me everytime -[21:19:43] BUT -[21:20:20] what i miss in the whole discussion is the fact that systemd is about standardization -[21:20:33] and not about boot time -[21:20:36] My general opinion about systemd unit files is that we should wait / let it up to upstream -[21:20:56] and if we add thousands of patches downstream the goal is totally failed -[21:21:03] I personally am unwilling to work on it (kde or elsewhere on Gentoo) -[21:21:19] well -[21:21:33] and we never add patches to add new features in kde packages... -[21:21:45] I'd suggest also to forward upstrem the patch we see in the bugzilla -[21:21:50] let kde upstream handle the stuff -[21:21:53] I also don't like getting tons of bugs to add systemd support to X, Y, Z. Those wanting systemd should be convicing X, Y and Z to support it -[21:22:06] how about "feel free to add patches that have been accepted upstream" -[21:22:50] whats the point to backport this when the release is in 8 weeks? -[21:23:24] dilfridge: If the patch is going to be added by upstream, if someone else (not me) is doing that work and it doesn't break or affect those running openrc, no objection from me -[21:23:56] jmbsvicetto: ++ -[21:24:24] jmbsvicetto: well, that comment was intended as "reply to our systemd guys" -[21:24:35] But people will still complain "I gave you the file, it's trivial to add" -[21:24:42] I use systemd -[21:24:56] I am happy to support the systemd patches/unit files -[21:25:03] possibly with ago -[21:25:16] I think we're running into the same trap as the dev ml -[21:25:24] creffett|mobile: I think that we need to check if thservice start -[21:25:27] We should not worry too much about small support files -[21:25:43] apart kdm do we have a lot of packages that installs an init script? -[21:25:46] but just add them if they are helpful and do not hurt otherwise. -[21:25:49] we dont need to discuss the small unit files.... -[21:26:16] the only thing worth discussing are significant patches for code -[21:26:18] its already added in kde-base/kdm -[21:26:45] and i add the gentoo unit file in upstream bug -[21:26:52] last kdm works for me -[21:28:15] if we start to add not reviewed source code patches i will leave the herd for sure -[21:28:38] its not about systemd, its about the correct way -[21:29:04] johu: we suggest to add the code to kde codereview, if it is accepted then we will include -[21:29:23] ++ -[21:29:26] ++ -[21:29:28] ago: thats what i have done in the bug -[21:29:53] ok let me try to summarize: -[21:30:19] So this means we as a herd from now on will only apply patches that have been accepted upstream? -[21:30:24] johu: and that's the correct way, so let's continue -[21:30:41] but if our packages does not install a init script, we don't need to discuss anymore -[21:31:32] "Small support files as e.g. unit files that affect only systemd but do not interfere with other software can be added locally but should eventually be upstreamed. Patches for adding functionality should be accepted upstream first." -[21:31:41] sounds ok? -[21:32:01] dilfridge: so long as this is not only for systemd -[21:32:01] sound like music -[21:32:01] yes -[21:32:10] good here -[21:32:20] Thev00d00: basically it's already the policy... -[21:32:21] ++ -[21:32:47] refreshing a policy is a good thing -[21:33:01] 5. Bugs -[21:33:16] bug 438790 -[21:33:18] johu: https://bugs.gentoo.org/438790 "kde-misc/polkit-kde-kcmodules: Store polkit configuration changes to /etc instead of /usr"; Gentoo Linux, KDE; IN_P; nikoli:kde -[21:33:27] sigh -[21:33:58] Nothing from upstream yet on that -[21:34:31] didn't other distros patch that? maybe we could attach someone's code to that bugreport... -[21:34:39] By the time they have a fix frameworks 5 will be out and this will be irrelevant -[21:34:40] who was working on that bug, it was in my off time -[21:34:47] Me -[21:34:57] i think this is fixed in fedora -[21:35:52] there was a thread about it on the release-team ml I think (but I dont have my archive here) -[21:36:21] I believe so, but am not sure, and it worries me that most dostros said they don't ship that module -[21:36:46] http://pkgs.fedoraproject.org/cgit/kdelibs.git/tree/kdelibs-4.6.90-kstandarddirs.patch -[21:37:47] err -[21:37:53] that was the link posted in the ml thread -[21:37:54] ... -[21:37:54] how do I get that page to show code? -[21:38:33] maybe they have dropped it in the meantime -[21:38:43] http://pkgs.fedoraproject.org/cgit/kdelibs.git/tree/kdelibs-4.10.0-kstandarddirs.patch -[21:38:46] more useful -[21:38:51] I will try that patch when I return from vacation and we can include it in the next bump -[21:39:22] is there an chance to get it upstreamed? -[21:39:34] we're just falling into our own trap :D -[21:39:39] creffett|mobile: ^ -[21:41:37] Well yeah -[21:41:42] when the bug is not in hurry we could try to get it in before 4.11 -[21:42:17] actually that looks small enough so it's realistic -[21:42:17] But this is a fairly major issue -[21:42:47] And I repeat that most distros do not ship this module -[21:43:01] yes, which lets me wonder why -[21:43:10] (does fedora?) -[21:43:13] yeah we could drop the package... -[21:43:27] -*- Thev00d00 votes drop it -[21:44:24] I think it isn't officially released -[21:45:21] no opinion here -[21:45:28] I vote make it no longer a kdelibs dep -[21:46:07] thats not a complete solution -[21:46:21] either we fix it or we drop it -[21:46:22] what does the package actually do? -[21:47:33] ^ ^ -[21:47:33] i guess you can manage the polkit rules -[21:47:37] Not sure tbh -[21:48:03] so we're going through a lot of pain because of something buggy that noone uses or even knows what it's good for. awesome. -[21:48:39] lastrite? -[21:48:51] vote! -[21:49:11] options? -[21:49:31] 1. get fedora patch upstream -[21:49:45] (and patch polkit-kde-kcmodules as required for that) -[21:50:17] 2. get rid of it -[21:50:34] 3.? -[21:50:53] 3. drop it as kdelibs dependency and drop it to ~arch -[21:51:03] -*- ago votes 1 -[21:51:04] 3 -[21:51:15] -*- dilfridge does not care -[21:51:15] -*- johu votes 1 -[21:51:30] --> creffett (~creffett@gentoo/developer/creffett) hat #gentoo-meetings betreten -[21:51:33] there we go -[21:51:36] much better -[21:51:59] <-- creffett|mobile (46c082af@gentoo/developer/creffett) hat das Netzwerk verlassen (Disconnected by services) -[21:52:12] scarabeus, jmbsvicetto ? -[21:52:24] alexxy? -[21:53:00] I reluctantly vote punt it, with the caveat that we should make sure that punting it doesn't completely hose KDE before we send the lastrite -[21:53:31] not for me to decide -[21:53:38] you guys just voted to have policy upstream first -[21:53:39] :D -[21:53:45] so you cant just rape it right away -[21:53:47] :D -[21:54:00] it was never realy released :P -[21:54:34] ^^ -[21:54:41] perhaps retire it to kde overlay only? -[21:54:50] thats option -[21:54:56] wipe it from stable ebuilds would work -[21:54:58] bugs persists in overlay too -[21:55:05] people shouldn't have this in their world files to start with, the only thing pulling it in is kdelibs -[21:55:22] yes, but for most people it won't matter anymore -[21:55:44] creffett: you started to work on the bug you can decide on you own as lead ;) -[21:56:02] we will cover your decision with full force -[21:56:04] -*- creffett puts his lead hat on -[21:56:16] -*- creffett thinks that we need a nice pope hat or something to mail around between leads -[21:56:18] anyway -[21:56:27] bug 444952 -[21:56:29] johu: https://bugs.gentoo.org/444952 "Add KDE Plasma Active support"; Gentoo Linux, KDE; CONF; creffett:kde -[21:57:02] unless someone seriously objects, I say move polkit-kde-kcmmodules to overlay, remove kdelibs dep, and re-evaluate if and when they get their act together upstream -[21:57:15] creffett: the lead gets a beer stein on the head at fosdem... -[21:57:25] whats the state? why we need to discuss this? -[21:57:29] plasma-active was added to the overlay under kde-active category -[21:57:43] why not kde-base/ -[21:57:48] if anything needs to be discussed, it's basically "when and how to move it to tree" -[21:58:05] scarabeus: no real reason besides it not strictly being part of the KDE SC or whatever they call it these days -[21:58:12] scarabeus: because it's not strictly part of KDE SC? -[21:58:19] nice timing. -[21:58:41] kde-frameworks wont be part of kde sc too.... -[21:58:44] it's not really KDE is the thing, it's a plasma product -[21:59:04] (which is a sub-product of KDE, I know) -[21:59:21] the kde thing is going away anyway... we should already prepare renaming ourselves... -[21:59:21] well how many packages it is -[21:59:28] no new category unless it is more than 10 -[21:59:42] ...9. -[22:00:03] next question, what's a more appropriate category? do we agree that it should go in kde-base? -[22:00:15] kde-active is fine. -[22:00:28] creffett: you could package the telepathy active client... -[22:00:38] then you would have 10 -[22:00:40] hehe, then it's 10 -[22:00:53] that's the other thing, it's not entirely ready because there are a lot of related products that aren't fully packaged yet -[22:00:54] okey you suckers are covered here -[22:00:55] :P -[22:01:04] lets keep it in testing in cvs -[22:01:08] more eyes more bugs -[22:01:18] not ready to be moved yet -[22:01:36] since I haven't had the time to go through all of the stuff on the website listed as "supporting plasma-active" -[22:01:43] oh, and I honestly haven't actually had the chance to test it :P -[22:01:58] my proposal, keep it in overlay -[22:02:08] it completely screws up the display of my laptop, and I don't have a mobile device I can sacrifice to the cause -[22:02:15] make an wiki article/howto and all is fine -[22:02:29] okay -[22:02:39] and maybe even put a little traffic on -desktop for once? :P -[22:02:46] email out a request for testing -[22:02:50] yeah or blog about it -[22:03:16] bug 456750 -[22:03:18] johu: https://bugs.gentoo.org/456750 "kde-base/plasma-desktop[-rss] unintuitive dependency on kde-base/libplasmaclock[-holidays]"; Gentoo Linux, KDE; UNCO; alpine.art.de:kde -[22:03:30] I need to leave. See you guys later -[22:03:42] jmbsvicetto: thanks for your presence -[22:03:48] cu -[22:04:19] I g2g in a minute also, anything else left on the agenda? -[22:04:27] yes bugs -[22:04:40] (and open floor) -[22:04:48] the use should be renamed -[22:04:53] i never understood why we call it rss :D -[22:05:10] scarabeus: propose a name -[22:05:22] -*- creffett has no idea what these use flags actually control -[22:05:23] $(cmake-utils_use_with rss KdepimLibs) -[22:05:29] aha! -[22:05:33] it enables fucking semantic desktop -[22:05:41] just bind it in -[22:05:41] lol -[22:05:44] AHAHA old topic -[22:05:51] then yeah, calendar/semantic-desktop might be more appropriate -[22:05:53] call it semantic-desktop and hard-enable it in 4.11 :) -[22:06:11] just to more spam -[22:06:13] rss? ( -[22:06:13] we get rid of it when we do -semantic-desktop -[22:06:14] $(add_kdebase_dep kdepimlibs 'semantic-desktop?') -[22:06:16] $(add_kdebase_dep libplasmaclock 'holidays') -[22:06:17] ) -[22:06:19] !rss? ( $(add_kdebase_dep libplasmaclock '-holidays') ) -[22:06:20] it was even automagic there :D -[22:06:21] why does holidays actually need a use flag? -[22:06:25] thats reasonf or the - -[22:06:46] creffett: it crashed when you had kdepimlibs without semantic and libplasmaclock and holidays -[22:06:53] ah. -[22:06:55] okay -[22:07:06] ok we will solve it with 4.11 ;) -[22:07:14] i will take of it -[22:07:16] care -[22:07:39] bug 461684 -[22:07:40] johu: https://bugs.gentoo.org/461684 "kde-base/kwin: backport patch to remove tearing on Intel systems"; Gentoo Linux, KDE; UNCO; mike:kde -[22:08:32] yeah do it -[22:08:36] we have this up for discussion because... -[22:08:52] ... because it's large and intrusive -[22:08:57] ah -[22:09:07] that is an absurdly long discussion upstream -[22:09:09] also see https://bugs.kde.org/show_bug.cgi?id=307965 -[22:09:12] "I am not sure if this is a good idea since there is upstream discussion about specifically avoiding KDE/4.10 branch due to the invasive nature of the patch and potential for regressions." kensingtion -[22:09:31] i would vote against it! -[22:09:46] we should just add it into the next 4.10.X release, and if there are problems we could always revbump without the patch again -[22:10:03] so it gets some time in ~arch for testing -[22:10:11] -*- creffett has no opinion here -[22:10:12] Its going to be in 4.11 so any issues will get to use soon enough -[22:10:27] no strong opinion here either -[22:11:21] stay with upstream -[22:11:22] users can always use user patches with kde packages... -[22:11:39] ok let's leave it out then -[22:11:50] mm, true, and we do support userpatch -[22:12:32] bug 468002 -[22:12:34] johu: https://bugs.gentoo.org/468002 "kde-base/kdelibs-4.10.2 ELOG output includes Your homedir is set to ${HOME}/.kde4"; Gentoo Linux, KDE; CONF; rich0:kde -[22:12:38] fast vote -[22:12:40] punt it -[22:12:41] can be removed -[22:12:42] -*- johu ++ -[22:12:44] punt -[22:12:48] kill it -[22:12:52] ok thanks -[22:12:56] -*- Thev00d00 loves the word punt -[22:13:02] on second thought... -[22:13:09] nah, kill it. :) -[22:13:12] bug 468894 -[22:13:14] johu: https://bugs.gentoo.org/468894 "Please restore kde-base/plasma-workspace-4.10.1 because of a bug"; Gentoo Linux, KDE; UNCO; gentoo:kde -[22:13:16] fast vote -[22:13:18] there is absolutely no reason for people to see that message anymore :P -[22:13:27] no -[22:13:31] no -[22:13:31] -*- creffett votes no -[22:13:39] NI! -[22:13:41] also looking forward to the KDE long-term support release :P -[22:13:52] wrong topic :D -[22:14:33] eh, it's related, since it's talking about keeping older versions -[22:15:09] the bug he mentioned was already in 4.9 -[22:15:23] true -[22:15:25] -*- creffett shrugs -[22:15:39] 6. Open floor -[22:15:57] cmake-utils now has inlined patching support in overlay -[22:16:27] going to eapi-bump the last few EAPI < 2 packages myself soon since it's been plenty of time for the maintainers to do it -[22:16:50] which reminds me to remind you to make a tracker out of the monolithic bug mess -[22:17:08] and that reminds me to say "meh, I'm bumping it all myself" -[22:17:33] fine but in the future make TRACKER bugs.. -[22:17:38] will do -[22:18:04] i have at least 2 more topics -[22:18:42] i dont like that kde-stable is not using our mail alias -[22:19:33] all the things that tampakrap mentioned when the sub-projects are true in my opinion -[22:20:10] hmm? anything I missed? -[22:21:03] you can read the log from last october again, its only my opinion no need for action at the moment -[22:22:13] and additionally i had the feeling that the stabilization of 4.10.1 was to early for the 4.10 -[22:22:58] so enough bad vibrations: -[22:23:27] as you may noticed i am back with full force as you may noticed in the last weeks -[22:23:37] who are you, again? ;) -[22:24:50] kensington's offtopic: There is a prototype reviewboard instance setup for use with the KDE overlay[1] -[22:25:01] http://astralcloak.net/~kensington/rb/ -[22:26:12] i would rather see running gerrit gentoo instance for all projects -[22:26:19] *like to -[22:27:02] gerrit++ -[22:27:33] we could ask kensington if he wants to host a test gerrit instance -[22:27:40] to compare -[22:27:43] gerrit is overcomplicated -[22:27:47] imho -[22:28:13] patches of patches of patches -[22:28:21] dilfridge: not really -[22:28:24] worked with both -[22:28:29] and gerrit is actually easier -[22:28:38] for usage on both sides -[22:28:41] reviewer and submitter -[22:28:48] ok -[22:28:53] no opinion here -[22:29:09] in lo i just do "gerrit push" and "gerrit review id" if i feel like not using gui -[22:29:22] and on web interface i can inline comments and approve commits directly -[22:29:28] so i can do that even from tablet -[22:30:21] ok -[22:30:29] so who is setting up a test instance? :D -[22:30:35] lets ask kensington to host a gerrit instance to test it and compare with reviewboard and then decide which we want to push into gentoo infra -[22:30:57] btw did anything come from that gitlab discussion? -[22:31:05] theo didnt mind if someone is willing to maintain it -[22:31:58] hm he should care about his hom(i)e herd -[22:32:24] any other topics? -[22:32:28] nothing here -[22:33:04] FYI git kdenetwork migration is in progress -[22:33:39] thank you all -[22:33:42] meeting closed -[22:33:52] g'nite -[22:34:51] nn -[22:35:02] 'night -[22:35:02] <-- creffett (~creffett@gentoo/developer/creffett) hat #gentoo-meetings verlassen -[22:35:39] nite \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-log-20140329.txt b/meeting-logs/kde-project-meeting-log-20140329.txt deleted file mode 100644 index d8a842a..0000000 --- a/meeting-logs/kde-project-meeting-log-20140329.txt +++ /dev/null @@ -1,456 +0,0 @@ - 1. Roll call (5 minutes) - !herd kde --*- creffett|irssi here - (kde) ago, alexxy, creffett, dastergon, dilfridge, jcallen, jmbsvicetto, jmorgan, johu, kensington, mrueg, mschiff, patrick, reavertm, scarabeus, thev00d00 --*- scarabeus beeps - hi - pong. --*- johu here - 2. EAPI 4 kde4.eclasses deprecation (10 minutes) - - KDE overlay is fully migrated to EAPI 5 and all older EAPI's are banned - - No issues known with EAPI 5 - - Discuss and vote - question: I know we've handled this in-overlay, but what's the state of packages in-tree? --*- jcallen is here - i bumped alot to EAPI 5 - let me check. - (would be nice if pkgcore worked enough to give us the EAPI-by-eclass breakdown) - so its only a question of stable requests and some packages not maintained by us - pkgcore-9999 works good enough now - and it fixed on qa-reports I think - yes qa-reports is fixed - really. - thats why i started to do the tree EAPI 5 work - news to me - we should ban it in the overlay and in the tree once that's cleaned up - kde-base: 21, kde-misc: 20 eapi 4 packages (eapi per cat) - so...bump the requirement in-overlay, news item on -dev or -dev-announce, file bugs? - http://qa-reports.gentoo.org/output/eapi-per-eclass/kde4-base.eclass/4.txt - ^^ most of them have already EAPI 5 rev bumps - cool - then stablereq and request cleanup - yup - around 20th april we can start mass stabilization and see whats left - so eapi4 ban would mean drop kdepim 4.4.x, right? - mrueg: I wish - nope - are those not EAPI 5? - we just bump them to EAPI 5 - yeah - i poked dilfridge about it already and he wants to do it - probably no need for a revbump, tbh - creffett|irssi: just checked for knotes still eapi=4 - kk - creffett|irssi: it's stable packages - kensington: blarg - anyone who wants to keep EAPI 4? - punt it - ok vote: - no need to keep, but what is the need to punt it? - I know it's stable, but I doubt the bump will actually change installed files, and those aren't using any eaapi features, afaik - just progress? - +1 burnintae - *burninate - +1 - mrueg: for 4 -> 5 not much, but eg. it might let us assume subslot support for something in the future - should be fine for 4->5 so +1 - creffett|irssi: we have already subslots implement for kde-base in the eclass - johu: oh, right, forgot about those - revbump it is. - kensington: i just wonder if ebuilds in overlays will fail because eclass disallows in the past, dropping <3 let us clean up a lot of junk from the eclasses - *non-kde - overlays - mrueg: not our problem - they will, that's their problem, we will announce as per usual - we announce it - they fix their own - okay sounds good. :) - +1 - I did a couple of the 'major' ones for the las ttime - we make a tracker for the packages not maintained by us - yup; I can do that if you'd like - creffett|irssi: lets do it after the mass stabilization - it would be nice to get a repoman error if eapi is deprecated for used eclass - okay - mrueg: that would require eclasses have a DEPRECATED_EAPIS sort of variable - which would be nice, admittedly - creffett|irssi: raise that topic in qa please - yep - :) - johu: in portage, actually :P - mrueg: file a bug :) - probably talk to TomWij - or file a bug ;) - will do. - next topic - I would look into it if I had time in the next...two months. - 3. KDE overlay contribution model (10 minutes) - mmkay - - We have a github mirror, which offers pull requests, reviews and comments - - Allows us to get more QA for user contributions - - Proposal: Drop all user ssh keys from overlay and promote the github contribution model (for example with a overlay news item) - - Discuss and vote --*- creffett|irssi is in favor of switching to github/pullreq model and dropping users' keys - I am against dropping all user ssh keys --*- mrueg wants to wait until infra deploys gitolite-3 on gogo - mrueg: what offers gitolite-3? - johu: easier mirroring - we should encourage pullreqs for more user contributions, but I think some users is fine to commit directly - kensington: hmm, that's valid - kensington: but where you draw the border - that said, there have been a couple problematic commits as of late - one user drop one not - I don't think we even have a list of who has access - thats easy question for infra... --*- creffett|irssi asks - right now mirroring means someone with access to both repositories does this on git push and pull, right? - dastergon can probably help with that - mrueg: yes, no server automation is currently supported - so we come back to the question of who we want to have access - infra won't do a hook, and github need to contact their support to have them mirror - kensington: please propose the criteria which user can proceed to commit and who not - imho it should be consistent - the thing is that most commits I've seen have been devs; of non-devs, there have only been a couple committing regularly, and at least one of those has been subpar - iow, we don't have a high non-dev commit rate to start with I think - we could allow only pushes to a non-master branch for users and merge it regularly - it's impossible to have a list of checkboxes - in general, makes enough patches that are good seems like a good rule, it worked in the past - nah just do it simple, they start with pull requests and if they are good they get the commit access directly, if they screw up they loose it - scarabeus++ - good enough for me - that's what we used to do anyway, except with patch on bugzie instead of pull request - but do we keep everyone's access? - also *lose... :D - for those interested: - 13:28 <@a3li> hi creffett|irssi, I'd have this list of additional keys besides all developers for you: caleb christian civil creffett cryos dastergon dessa devurandom dmaggot eliasp genstef helgc - idella4 johu kensington krytzz letharion lxnay mattepiu mrueg mschiff mva okias ronis_br skiarxon spatz sput terietor tgurr travlr wizzleby wohnout yngwin - I...uh..have no idea who half of those people are. - :P - and the other half is people that went on to be devs :p - yup - so do we want to keep all of those? - i raised this topic to make the contribution easier for non-devs and as github is generally accepted i think this is the consistent way - for example clean up wiki page with contribution info - remove hackers file etc etc - yeah --*- johu thinking in long term to a git migrated tree :D - johu: heh. --*- creffett|irssi drinks - can anyone add a instruction how to mirror both repositories? - last time i tried to merge a pull request on my own overlay, it went all mad. - so for the moment, any objections to leaving current contributors with access and switching to encouraging everyone else to use github pullreqs? - ++ - fine by me - mrueg: I personally use github "merge on command line" instruction, then rebase and push - otherwise you can merge in github ui, pull, then push to gogo - mrueg: you have to add another remote to you local git clone - kensington, scarabeus: any objections? - jcallen: and you - creffett|irssi: no, since this is the current process anyway :p - kensington, johu: an example gitconfig would be nice. ;) - well, that's a majority - johu: your turn - mrueg: http://bpaste.net/show/195334/ - http://dpaste.com/1763251/ - thanks - looks like i did something wrong here. http://bpaste.net/show/pqp20cn2F7hNvn7aQjWI/ ;) - so please vote on the general plan - I have no problem with cleaning up at least some of the access list, I agree there have been some 'interesting' commits lately - with the exception of not dropping keys at once - +1 - +1 - +1 - ok i will prepare a news item and send it to kde - @ - we can optimize it then - sounds good - next topic - 4. KDE Frameworks 5 (15 minutes) - yay! - Overview: KDE Frameworks - New kde-frameworks eclass needs internal review/feedback. It's not yet ready for -dev ml due to potential major changes for workspaces and applications. - It appears (final strategy not confirmed yet) that rather than one SC as seen in KDE 4 there will be 3 groups released separately: frameworks, workspaces, and applications. We should consider how this should be categorised. kde-frameworks is currently approximately 60 packages, with the potential for future 30+ additional packages. Potential scheme which is consistent with existing categories (see gnustep for -libs precedent): - frameworks -> kde-frameworks/kde-libs - workspaces -> kde-base - applications -> kde-apps - See Naming scheme, Dicuss and vote - wheeeee - what about kde-misc? - people are going to complain about us having three categories. - there's precedent, see gnustep - didn't say no precedent, said there will be complaining ;) - i would follow naming scheme from upstream-> frameworks -> kde-frameworks - a lot of frameworks stuff is designed to be not so kde-specific, so I think they deserve their own category - that said, the suggested split sounds good to me - -workspaces -> kde-workspaces - -applications -> kde-apps - we also may want to consider doing something with kde-misc, but that's a different question for a different day - kde-misc stuff doesn't fit into any of those other categories - kensington++ - I mean more like there's a lot of cruft in there - that I doubt anyone uses - like I said, different question for a different day - yeah, it could use some testing, I last-rited a youtube package in there that is probably broken for years - johu: that means for the mean time 5 categories, right? - kde-apps, kde-base, kde-frameworks, kde-misc, kde-workspaces - I agree with johu, but I think we will get a lot of pushback on -dev - yup. - i think it is a good idea to seperate the release groups - just move the two proposals to -dev - and see how it turns outr - question: when is kde 4 set to stop getting releases - creffett|irssi: when there is a stable kf5 based release - kde-{workspaces,apps} - creffett|irssi: maybe there's also a trinitiy project for that - do we want to support kde sc 4 and kf 5 installed in parallel? - frameworks is about to hit beta, and workspaces is about to hit alpha - kf5 is almost co-installable with kdelibs - kde-runtime will be co-installable, kde-workspace will not - well, at least we have time before the tree move to get flamed - who raises the cat discusion to -dev - ? - just think about a package depending on kwin for example - I would like to have some team agreement, because the runtime/workspaces split is about to happen and I want to package asap - +1 from me - mrueg: kwin will not be co-installable, but not much depends on it anyway - i have no objections, please dont re-introduce a kde-prefix again - also, I volunteer kensington for emailing the ML :P - kensington: just thinking if we want to deal with slots or categories - ooh! - kde-prefix! - so kde-base/kwin:4 or kde-base/kwin because kwin:5 will be in kde-frameworks or somewhere else. - all kde5 stuff is already in slot 5 - vote on: kde-frameworks, kde-workspaces, kde-apps - +1 - +1 - if -dev is against it we should go with kde-apps, kde-libs, kde-base - kde-base for kde4, kde-misc for everything else - probably eclass can use the category to decide which release group the package is - so we don't need anything like TIER=1 inside of the ebuild - mrueg: it's all in split repos - TIER=foo was only for frameworks stuff when it was still in kdelibs - ack - kensington: ah okay - didn't know that :) - anything left to discuss for now on kf5? - yup - lately there was a discussion to merge qt-overlay and kde-overlay? - if anyone has a free moment, check the eclass, there are a few design decisions that could use a review - what about the ebuild naming scheme? - mrueg: i dont see the purpose, the split was decided with the herd split and thats totally fine - johu: i don't know, can't both sides profit from a shared repository? - there's not much crossover - the only commonality, really, is qt5 - mrueg: there was a time where no qt herd exists and the qt stuff was maintained by kde - I actually did not know that - and then the split was decided because of the reason that there is no much crossover - though that explains the large number of qt people in our repo's access list :P - but what would be the drawbacks of a joint repository? - because kde is just one consumer - the effort to merge it and people migrating to it I guess - we have high kde commit rate because of the monthly releases and someone who dont want to have extra kde stuff but newest qt stuff is pushed to get all those changes... - johu: probably we can work on seperate branches and with a joint master branch - naming scheme is important if we end up using kde-base for kde5 stuff --*- johu is against a re-joined qt-kde repo - mrueg: eww - and if not it would be nice to not have to manually pin ebuilds to a branch they don't match - okay :) - i see we better stay at status-quo :) - kensington++ - so, we can either just update the sets (eg. kde-live pulls in kcalc-9999 and kwin-4.12.49.9999) or make fake versions like 4.9999 - sets sounds more reasonable - ++ - ++ - but this decision is a little bit influenced by the cat discusion on -dev - yeah - yup - also, I think kde-workspaces will end up to be not many packages - maybe kde-base fits here okayish - it's being split into 12 repos, probably only that many packages - kensington: i would suggest to write the -dev mail as soon as possible and then do the reasonable move! - johu: I will wait 1 or 2 days until the split is done, to get an accurate number of packages - if 12 repos = 12 packages, a new category for that will be definitely be rejected - we could discuss this per mail if it is realy urgent and needs a fast decision - johu++ - I will mail a draft to the alias depending on what happens upstream - ++ - ++ - anything left on kf5? - otherwise I guess it will just be kde-frameworks/libs + kde-base - btw kensington thank you for your great work - mhm - btw, mimetypes is fixed upstream in case you didn't see :-) - kensington++ - 5. Bugs (15 minutes) - bug 445392 - johu: https://bugs.gentoo.org/445392 "kde-base/konsole-4.9.3, x11-terms/xterm: backgroundcolor is not reset when scrolling"; Gentoo Linux, Applications; UNCO; toralf.foerster:kde - RESO NOTOURBUG - ++ - c7 - ++ - ++ - hello - i dont want to do upstream work - hi ago - hey ago - sorry for the delay, I had a prob. - good enough, will mark it - bug 456360 - johu: https://bugs.gentoo.org/456360 "kde-base/print-manager looking for org.fedoraproject.Config.Printing"; Gentoo Linux, KDE; CONF; kirelagin:reavertm - erm : bug 445392 vanished away / was solved in the mean while (at least with 4.12.3+4.11.7) - https://bugs.gentoo.org/445392 "kde-base/konsole-4.9.3, x11-terms/xterm: backgroundcolor is not reset when scrolling"; Gentoo Linux, Applications; UNCO; toralf.foerster:kde - toralf: that's good news - johu: that bug confuses me. - printer stuff needs gnome bla to get full working, so there was a proposal to split stuff up - but i got lost by all those user comments - is reavertm around lately? - haven't seen reavertm, no - in the last years not realy - I guess the real solution is to improve the splitting, we can see how other downstreams do it - add a minimal useflag to system-config-printer-gnome and activate that in kde profile by default? - minimal useflag triggers the patch - mrueg++ - it would be cleaner to do the split - but this would be more effort - mrueg: volunteer? - johu: maybe upstream accepts the patch - if eta is 1 month + x, i can take a look at it - otherwise, i'm short on time - it's all one package upstream I think? - i guess yes - bug 482652 - johu: https://bugs.gentoo.org/482652 "[kde overlay] dev-db/virtuoso-server-7.0.0 fails to integrate with akonadi/nepomuk"; Gentoo Linux, KDE; CONF; johannes.hirte:reavertm - do we realy need virtuoso-7? - nope - nepomuk is going away - \o/ - BOOM - lets keep the bug open and then last rite virtuoso when nepomuk is gone... - +1 as virtuoso comaintainer :P - does it work on x86 anyway? - nope - nope! - virtuoso upstream stoped caring about...pretty much anything - so I'm fine with burninating - we can close that bug, there's no new development of nepomuk obviously - 14:22 < johu> mrueg: volunteer? - oops, sorry - stupid putty paste buffer - kensington: yeah but you will always get version bump requests even when it makes no sense - lets move on then - but i am fine with it to drop the stuff - there's still the other bug about it open - bug 490600 - johu: https://bugs.gentoo.org/490600 "kde 4.11.3 missing oxygen theme after update"; Gentoo Linux, KDE; CONF; nikhatzi:kde - this is re-occuring with kstyles/qt updates - what is there that we can do? - how about to just add a einfo/ewarn? - johu++ - yeah - we would need a eclass/portage mechanism to get this proper fixed - I'm still not sure exactly which package is triggering the breakage though - i guess qtgui - bug 497314 - johu: https://bugs.gentoo.org/497314 "No standard directories created after login to KDE"; Gentoo Linux, KDE; UNCO; oldium.pro:kde - kensington: whats to discuss there? - what (if anything) to do - do we want to add a useflag for that? - if we do /etc/skel we have to coordinate with other desktops - kensington: please do - its the proper way - or we can copy the env thing from hnome - copy & paste is dirty - please do the skel way - what package do we put it in? - kde-env - ? - sgtm - sure - we might as well just copy the gnome env file then, it's less copy-and-paste then manually creating a bunch of directories - /usr/portage/gnome-base/gnome-session/files/10-user-dirs-update-gnome-r1 - ok if you say its easier faster and not that dirty, "Just do it" - make it so! - 6. Elect new lead (10 minutes) - i'll have to leave now - !herd kde - (kde) ago, alexxy, creffett, dastergon, dilfridge, jcallen, jmbsvicetto, jmorgan, johu, kensington, mrueg, mschiff, patrick, reavertm, scarabeus, thev00d00 - nominees - I will go again if nobody desperately wants the role - creffett|irssi++ - i nominate johu too - thanks accepted - Xfce has the same code as /usr/portage/gnome-base/gnome-session/files/10-user-dirs-update-gnome-r1 in startxfce4 - at upstream level (where it really belongs) - creffett|irssi, but, but, I was hoping you'd be portage lead...;) - dol-sen: NOPE. - ssuominen: what is your opinion on what we should do, as the resident freedesktop expert :D --*- dol-sen goes back into hiding in the corner - do we have any more nominees? - i would nomintate dilfridge but i guess he has enough work with council - and he is not here to dis-/agree - yeah - all right - ok do we want to do this via mail? - then let's vote - I have no preference - i have the feeling that to less people are here... - mrueg just left the building - okay, then I'm good with email voting - ++, I have to go too - kensington: got nothing unexpected to say :) I'd add the file like gnome has, but at the same time, also write a patch that does the same and file upstream ticket - creffett|irssi: check please the kde mail alias with herd members...there are some not following the mails - johu: uh, I can't right now, but off the top of my head reavertm isn't on the list - and possibly dastergon? - creffett|irssi: scarabeus too i guess - scarabeus isn't I think - and mschiff maybe too - yeah - so better check - ssuominen: ok, I'll go ahead with that, thanks --*- creffett|irssi can't do that until tomorrow night - creffett|irssi: yeah lets say let us do the vote within 10 days - kk - 7. Open floor - nothing here - kde 4.12.x target - kensington: the problem is that desktops have started relying upon these directories in very early start, so xdg-user-dirs upstream refused the xdg .desktop autostart file for it, with notes that it would then execute too late in the process - kensington: so thats why we are stuck at calling the executable like this... otherwise i would have added the .desktop file long time ago - johu: .3 then .5 later? - good enough for me - just 5? :D - + whatever kde-workspaces it is - well, probably arch teams will struggle to do .4 as well - do we have any serious blocker left for .3? - not afaik - keywording for minor archs :p - as maintainer we can always decide to drop stable keywords - the problem is we have no stastics who realy uses kde on ppc,ppc64 - every time we try to drop we get a couple people complaining - i dont think it is useless to have them stable, as the kde-stable team has no test plan just a OK and ago only makes build tests on it - I suggest we go ahead with kde-stable asap then CC archs in a week or so - kensington: but the good question is which arches? :) - the current ones, we can discuss dropping them if they are still lagging when we want to remove 4.11 - i dont want to add kde-stable anymore - there is no real benefit from the sub-project - I saw some conflict no previous stable bugs - in either case I think we should be good to CC archs ones the 30 days is up - it is working well here, and there have been no bug reprots - will create a list --*- johu when nobody cries at home - heh. - anything left for open floor? --*- creffett|irssi needs to get going, later folks - thanks all - johu: thank you for running the meeting :) - don't forget to review kde-frameworks.eclass, or otherwise be stuck with my awful design until kde 6 :-) - kensington: i always review commits - kensington: kde-misc/akonadi-git-resource for kde overlay - johu: where does it display it? - kensington: extra folder in the left tree view - interesting, I will check it out - oh, kmail... - kensington: http://ctrlv.in/311477 - I will try kmail again with baloo some time - 9999 :) - in my opinion we should rename 9999 to 666 :) \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-log-20140810.txt b/meeting-logs/kde-project-meeting-log-20140810.txt deleted file mode 100644 index fde8e8a..0000000 --- a/meeting-logs/kde-project-meeting-log-20140810.txt +++ /dev/null @@ -1,389 +0,0 @@ - 1. Roll call - !herd kde - (kde) alexxy, creffett, dastergon, dilfridge, jcallen, jmbsvicetto, jmorgan, johu, kensington, mrueg, mschiff, patrick, reavertm, scarabeus, thev00d00 --*- alexxy here --*- kensington here --*- johu here too - pong - me too - good 5 is enough to start - 2. kde4-*eclass GCC minimum version (10 minutes) - Please discuss and vote on raising gcc minimum version to 4.7 - Open Bugs: - bug #462550 - [4.6/ICE] sys-devel/gcc-4.6.3 Segmentation fault (program cc1plus) compiling kde-base/rocs-4.10.1 on ppc64 - bug #471770 - =kde-misc/homerun-1.0.0 - fails to build with bug #508324 - kde-base/kig-4.13.0 fails to build with johu: https://bugs.gentoo.org/462550 "[4.6/ICE] sys-devel/gcc-4.6.3 Segmentation fault (program cc1plus) compiling kde-base/rocs-4.10.1 on ppc64"; Gentoo Linux, KDE; CONF; jmorgan:toolchain - johu: https://bugs.gentoo.org/471770 "=kde-misc/homerun-1.0.0 - fails to build with johu: https://bugs.gentoo.org/508324 "kde-base/kig-4.13.0 fails to build with 3rd bug is one of the stable blockers --*- dilfridge|mobile here - we did it in kde5.eclass and already there was a complaint - kensington: why do people complain? - only one... - nah we do these rises quite periodically - mrueg: because it unconditionally required it for every package - and people complain - but still they should use latest-stable anyway - kensington: okay, i don't consider that relevant. - do it - and gcc 4.7 is stable for >few months - raise it - its bare minimum - so its good to raise it to 4.7 - ok official vote: - or there are some arch that dont support it? --*- alexxy vote for gcc 4.7 in deps - +1 - +1 - +1 - ok fine - 2. KDE SC 4.13.3 stabilization (15 minutes) - bug #517344 - KDE SC 4.13.3 + KDE Workspace 4.11.11 stabilization - semantic-desktop refactoring (old semantic stack -> nepomuk use flag, new semantic stack -> semantic-desktop use flag): Are we happy with it? Do we need an news item? - Baloo alternate KCM: Now that upstream provides an option to disable indexing in their KCM, do we still want to hack the alternate KCM into the baloo ebuild? - Please discuss and vote to stabilize KDE SC 4.13.3 - https://bugs.gentoo.org/517344 "KDE SC 4.13.3 + KDE Workspace 4.11.11 stabilization"; Gentoo Linux, Keywording and Stabilization; CONF; johu:kde - i would disable the hack otherwise +1 - ack with scarabeus - not sure about news item - Same here - if there is possibility to disable indexing using upstream kcm then there no need to hack alternative one - can we do a news item conditional on installed with -semantic-desktop ? - i dont care about the alternate kcm - i want to punt alternate kcm hack from ebuild, it's still around if someone wants to install it himself - fine by me^ - fine^^ - are we happy about baloo performance? - only have ssd to test on laptop - it's improved over nepomuk - EDONTCARE - any objections to 4.13.3? - no, it's a good target - No - use flag refactoring was OK? - sgtm - ok first vote on the topic: 4.13.3 is our next stable candidate - refactor worked out well, i think everything was converted - ++ - +1 - + - + - ok now about the procedure - kde-stable looks dead to me - no mail after ago's reitrement - so i will add arches directly - so should we dissolve the project? - fine, it's been very quite release in ~arch anyway - which leads to the question which arches @-dev mail about ppc/ppc64 - or can we reactivate them for kde5 somehow? - Talk to pl - ppc - Ask them - who was elected to be lead of the 2 herds? - Imho we don't need ppc stable - But if they want... - johu: jmorgan iirc - Gotta go, have fun... - ok i will contact him when we have the stable list in place - which will require some work to catch up all pkgs about the use flag refactoring - ppc 32 bit is a dead arch - its only exist in routers - don't they need to go stable at the same time anyway? - yes thats why they have to be IN the list - alexxy: ack - so it may be safe to drop them - i will ask them if they want to keep stable keywords - if x86 32bit somehow alive since some still use it - even if there no processors which run only 32bit mode for 10 years - yeah some ppl install still 32 env on 64 systems... - however x86 32bit can be considered dead in quite near future - ok last question in this topic if there is no objections on this. Do we need a news item? - johu: they still wann be paladins and play necromants games - +1 for news item - ++ - + - +1 - there was some confusion about 2 use flags when it hit ~arch - ok volunteer? - users should know or they will scream - kensington: native speaker, you wanna do this? - sure - ok fine, so in some weeks we will have a new stable kde - next topic - 4. KDM (5 minutes) - jmbsvicetto suggested to rethink kde-base/kdm as a dependency in kde-base/kdebase-meta:4, as kdm will not exist after KDE 4 and users might have already migrated to something else. Do we want to add IUSE="+display-manager" with RDEPEND="display-manager? ( || ( x11-misc/lightdm-kde x11-misc/sddm kde-base/kdm ))"? If so, which order? - Please discuss and vote to make kdm optional (and if yes on the proposed solution/order) - kill'em =D - make it optional, add display-manager IUSE, order: not sure about it. - sounds reasonable -> RDEPEND="display-manager? ( || ( x11-misc/lightdm-kde x11-misc/sddm kde-base/kdm )) - kde upstream supposed to use sddm? - right? - for kde5+ - may be it good to create virtual/display-manager - for kde4 let's keep the default the same - yeah the order for kde4 should be untouched - and for :5 i would vote for sddm - as upstream is heavily contributing to sddm - we can worry about :5 later, we don't even have meta packages for it yet - kensington: is on my long todo list - kensington: i'll create them =D - i'm run it @work - anything to add before vote? - tbh dm shouldn't even be pulled in kde 5 meta pacakge; we don't pull in xorg-server - also sddm should work for wayland - that i wanna give a try - on laptop - OK please vote on making dm optional and keep current order untouched for :4 - +1 - +1 - +1 - there is no current order, it's just kdm - just put there or with kdm first - "s/current order/kdm default" - makes more sense kdm use flag then - since kdebase-meta is just a list of kdebase packages - display-manager sounds more generic - and sddm isn't even stable - we just need one stable in the RDEPEND options ;) - thats not the problem - any other opinion about the use flag name? - ok, silence - So please vote on use flag name: a) display-manager b) kdm --*- kensington doesn't care about flag name - so let's go with display-manager - fine - does it mean kde:4 display-manager? ( kdm ) or display-manager? ( || ( kdm lightdm sddm ) ) --*- kensington votes for the first one - i'd be okay with both --*- creffett|irssi here - and i think jmbsvicetto, too. - display-manager - i would say give freedom to the ppl: display-manager? ( || ( kdm lightdm sddm ) ) - iirc he just wanted an option to disable kdm there - Gentoo is all about choices - don't use a meta package for pulling in kdebase packages then - its outlined in our official guide --*- creffett|irssi passes johu a drink - you can still choose what you want, but the kdebase-meta pulls in all kdebase-packages - wallpapers use flags pulls in kde-wallpapers, not || ( kde-wallpapers gnome-wallpapers ) - ok all arguements on the table? - vote on a) only kdm controlled by the use flag b) even more options, like lightdm sddm gdm? - a - b - a - all those sleeping birds - creffett|irssi, alexxy, scarabeus? - b - b - lightdm[kde] or just lightdm? ;) - come on scarabeus say a then we have a draw - suggest we do || ( kdm virtual/display-manager) then - ++ - += - last chance to object^ - there's no virtual/display-manager ? - 5. Phonon backend (5 minutes) - mrueg: thats an good argument - kensington: where do you find it? - it doesn't exist yet, alexxy suggested to create it - fine by me, but please do it fast as it needs to be stabilized too - otherwise i would vote for kdm only - and do the long track for 4.14 - sgtm - ok next topic, - 5. Phonon backend (5 minutes) - The current default backend is gstreamer, the same as in Kubuntu, and has the greatest number of features. However, upstream now chooses VLC as the default. Should we switch or remain the same? - Please discuss and vote on switching to vlc as default backend - switch to vlc - vlc - vlc - no opinion - p-gstreamer has such a low commit rate - also 1 vlc is nicer than 100 gstreamer-badugly-foo - btw. what about phonon-qt7? - homepage is dead, last snapshot in tree is from 2011 - +vlc - mrueg: if you want last rite it and see what happens - mrueg: i look forward to punting it along with all other unmaintained prefix kde stuff - http://quickgit.kde.org/?p=phonon-quicktime.git looks deadish - kensington: please do so :) - there was complaints last time i tried...but still nobody would even test it - so probably it will disappear when kde4 is gone - kensington: try it again - 6. KDE 5 - a) Categories (10 minutes)[edit] - kde-frameworks has already been approved on gentoo-dev. Plasma 5 is currently 23 packages, should it go in its own category (kde-workspaces?)? If so, we would likely need a new category for applications (kde-apps?) and eventually remove kde-base (and kde-misc?). --*- kensington doesn't know - why not use kde-misc instead of kde-apps? - kde-frameworks, kde-workspaces, kde-misc - it will have official kde and third party applications in the same category then - kde-plasma? - its the official wording for the DE so why not following it for the category - and then would make kde-apps sense to me - otherwise i would stick to kde-base - kensington: post pone this topic? - i guess - b) Moving to tree (10 minutes) - Qt 5 will be in the tree soon (masked). Are we happy to move KF5 / Plasma 5 after that's done? - kde-workspaces looks better - its good to move --*- johu is for KF5 tree, plasma 5 overlay when qt5 hits the tree - at least releases - kf5 are nonsence without apps and plasma - so its like all or nothing - its not the best user experience when almost all kde apps are not ported - yeah - but we can keep it masked - that's a feature, not a bug - alexxy: wrong tomahawk already uses a kf - so if someone wanna use it they will - it's expected behaviour to use kde4 apps and porting will be slow - i guess at christmas time big porting will happen - arroundish - will plasma-active get into the tree somewhere in the near future? - oh sorry. - nvm - OK vote 1) When Qt5 hits the the KF5 will be added too - tree - ++ - ++ - johu: kf5 + plasma - otherwise ++ - ++ - (without plasma) - 2) When Qt5 hits the tree Plasma 5 will be added too - -1 - -- - ++ - ++ for plasma-5.1 - 4.0 was the same story - plasma is pretty stable though - but the kde4 apps looking ugly - kensington: is the package splitting done? - kensington: +1 i use it as default DE @work - i didn't notice, maybe we have different themes - only porblem is that it doenst work with 2 monitors - mrueg: which splitting? - and there are a lot of usability issues unresolved - kensington: dolphin:5 etc.? - 2:2 - mrueg: we didn't work on it yet, hoping upstream will split repos - there's not even release schedule yet so we've got some time - i take my lead head on and say lets revisit the topic with 5.1 release - kensington: i'd say get it into the tree, when this is done - we have no hurry to rush at the moment - mrueg: applications are on a different release cycle to plasma - kcalc may well be released at a different time to dolphin eg. - kensington / alexxy are you fine with postpone the plasma decision? - yep - fine, probably 5.1 will be released before qt5 in tree anyway - he he =D - or 6.1.... - 7. Bugs (15 minutes) - first one: 456360 - bug 456360 - johu: https://bugs.gentoo.org/456360 "kde-base/print-manager looking for org.fedoraproject.Config.Printing"; Gentoo Linux, KDE; CONF; kirelagin:reavertm - was this discussed last meeting? - i think so, don't remember the outcome - ok then we need to grep the last log and see what we are going to do - bug 492434 - johu: https://bugs.gentoo.org/492434 "lib-net/libnm-qt should depend on systemd or consolekit (was: kde-misc/plasma-nm should depend on kdm[consolekit])"; Gentoo Linux, KDE; UNCO; cruzki123:kde - not much we can do unless someone volunteers to do the package split - i think it was me to check whats going on, but haven't found time for that - RESOLVED WONTFIX imho as networkmanager already provides those flags - which one actually requires it? libnm-qt or networkmanager - plasma-nm is not useable without consolekit/systemd - but it depends on libnm-qt which depends on networkmanager - and networkmanager already provides the requested use flags... --*- kensington no opinion - its dependency chain - as plasma-nm is the only consumer of libnm-qt - so libnm-qt should depend on nm with any of this use flags - can't libnm-qt depend on || ( networkmanager[consolekit] networkmanager[systemd] )? - yeah we can add that^ - fine RESOLVED FIXED soon (tm) - bug 497314 - johu: https://bugs.gentoo.org/497314 "No standard directories created after login to KDE"; Gentoo Linux, KDE; UNCO; oldium.pro:kde - kensington: last comment from you - meh - do we even want to do something downstream? - if its a hack no - if its doable without hack fine by me - kensington: what about comment 4? - but at least some progress on this would increase user experienc - sounds good. - mrueg: we can do it, it's kind of hacky but it works - kensington: is this for plasma5 needed too? if yes i would vote for an upstream action! - as we want to get rid of such things - yeah - samuli mentioned /etc/skel solution, i'll ask him about that too - ok lets see if the bug is unresolved next meeting ;) - I dont care about dirs acutaly - bug 497734 - johu: https://bugs.gentoo.org/497734 "www-client/rekonq-2.4.0 should RDEPEND on kde-base/kdebase-kioslaves"; Gentoo Linux, KDE; CONF; rossi.f:kde - kensington: last comment from user responded to your question, so whats left here to get a RESOLVED? - i could reproduce with my config, but not his - so we can 1) add the dep 2) too bad use runtime-meta 3) tell upstream not to use ioslaves to display a blank page - 2) - +3) - or 1) - ok seems i have no opinion on that - does kdebase-kioslaves add many dependencies? - (if you're using gnome and want rekonq as a browser) - not much beyond kdelibs - okay, then 1) + 3) - ^ - ++ - bug 511570 - johu: https://bugs.gentoo.org/511570 "[kde overlay] KDE Frameworks requires gcc 4.5, not 4.8"; Gentoo Linux, KDE; UNCO; matthew:kde - topic 2) revisited for KF5 - well we did raise it to gcc-4.7? - (for kde-4) - 1. too bad 2. conditional on package type - yeah we did - if we raise for kde4 to gcc47 its fine to have gcc48 for kf5 - Is there a need for 4.8? - i guess we would get a lot of bugs if we lower it to gcc45 - why not use 4.7 for both (if it works) - plasma 5 requires 4.8 - ah okay - the 4.8 is fine - thats the reason^ - (just asked because 4.7 is stable, 4.8 is testing) - WONTFIX imho - +1 - 4ю8 шы ашту - sorry - 4.8 is fine --*- alexxy on 4.9 already --*- johu too - kensington: did you test kf with 4.5? :) - no, it's just the upstream claim - i don't even have 4.5 installed - 4.5 is too old - i guess nobody will test it from herd as we already on newer - newer version more interesting - kensington: so thats a closing reason for it, we dont have the manpower to support such old setup - bug 514384 - johu: https://bugs.gentoo.org/514384 "cmake-utils.eclass: please deprecate all those fancy cmake-utils_use_*"; Gentoo Linux, Eclasses and Profiles; CONF; mgorny:kde - yeah, it's less relevant anyway since we move to 4.7 - -- - no problem to add the function he wants, but a lot of the existing functions are useful - kensington:++ - same opinion - maybe we can grep to see if there's some old unused function to remove - and dilfridge already expressed his opinion in the bug - yeah do it so - 8 Open floor (15 minutes) - kde member of the month: kensington for his great effort on KF5/Plasma5 and upstreaming - cheers - and next month it may be pesa to get Qt5 into the tree - i did a big reshuffle of cmake-utils in overlay, it tests ok locally for ages so i'd like to move that - it's mostly cosmetic - we are almost done with EAPI4, do we need to announce it on -dev? - <10 pkgs - don't think it's required, maybe some overlay users care - ok i need to leave, my food is ready - Thank you all - johu++ \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-summary-20090212.txt b/meeting-logs/kde-project-meeting-summary-20090212.txt deleted file mode 100644 index 288437c..0000000 --- a/meeting-logs/kde-project-meeting-summary-20090212.txt +++ /dev/null @@ -1,34 +0,0 @@ -KDE PPLE AROUND: -alexxy, tampakrap, wired, hwoarang, scarabeus, yngwin, Sput, jmbsvicetto, reavertm, krytzz, -EXCUSED: -cryos, deathwing00, tgurr -NOT EXCUSED: -the rest :P - -Review of previous: -update for 4.2 went ok. Some minor issues :] -there is missing review for pyqt/pykde and printing stuff, that will be deffered until somebody step up for the fixing/testing. - -This one: -droping of 4.1. - tampakrap - -voting for leader -> jmbsvicetto, he get 7 voltes from devs (alexxy, tampakrap, hwoarang, scarabeus, yngwin, deathwing00) rest is not around so deal with it :] -all hail to the new leader jmbsvicetto :P - -prefixing and using multiple versions of the kde in one prefix -> cooperation with upstream -installing libs and things versioned and use eselect to pick the one we want... -read the log around 21:30 and keep going for this one -jmbsvicetto, reavertm, maybe somebody more - -3.5 - dropping the old .7 and .8 -poke archies about stabling and checking keywords on .9 -alexxy is going to do this one - -patches sharing with other distros -new patching glep, help wanted and i welcome any critic on current state (on mail until i anounce on -dev). -http://dev.gentoo.org/~scarabeus/patches-glep.html -scarabeus - -pykde - needs love, unprefixing probably, who will do it? - -and more and more... \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-summary-20090401.txt b/meeting-logs/kde-project-meeting-summary-20090401.txt deleted file mode 100644 index 168f528..0000000 --- a/meeting-logs/kde-project-meeting-summary-20090401.txt +++ /dev/null @@ -1,74 +0,0 @@ -Roll call: -KDE devs: alexxy, bonsaikitten, cryos, hwoarang, jmbsvicetto, scarabeus, tampakrap, yngwin -KDE ATs: krytzz, reavertm, wired - -Agenda for the meeting: -- unprefixing misc stuff -- moving plasmoids to the tree -- kde3 state -- moving printing to the tree -- upstream responses on packaging snapshots -- removing dead members -- pykde fixing -- handling kdeprefix for base... eselect? -- koffice status / what is needed -- moving meeting to another date (about 2 weeks before release of upstream so -we can talk about what is needed to be done for current release) -- stable live status (if the guys working on it shows up ;]) - - - Removing kdeprefix for apps not in kde-base - reavertm explained that the goal was to drop the kdeprefix use flag for all apps - outside of kde-base and that he already started the work for it (including a rewrite - of the eclasses) in the dropped-kdeprefix-on-non-kde-base branch in the kde-testing - overlay. This means deprecating NEED_KDE in favor of KDE_REQUIRED and KDE_MINIMAL, so - that packages are built not against the newest available KDE (when there's more than - 1 version) but instead to the oldest - respecting KDE_MINIMAL. - There was a long discussion about kdeprefix, its purpose, benefits and alternatives. - The final consensus was to follow reavertm's solution. - - - KDE3 state - tampakrap explained the eclasses are ready to move all packages under /usr/kde/3.5. - He's still testing ebuilds and could use the help of 2 people to test kde-misc apps. - wired and jmbsvicetto offered to help. tampakrap will prepare a list of packages and - we're going to search for people through the page and a mail to the dev ml. - To start the work on getting KDE4 marked stable, we agreed to get this work done by - the end of the month - we'll be masking 3.5.9 monos as soon as we get 3.5.10 marked - stable. - - - Moving Plasmoids to the tree - Plasmoids were moved to kde-misc category and will be added when they're tested - with +kdeprefix - - - Adding printing packages to the tree. - We've decided to hold this until KDE-4.3. - - - Upstream response to the packaging snapshots mail - No reply again. As we're being ignored, we've decied to repackage the snapshots. - - - Removing dead members - jmbsvicetto will go over the retirement bugs and will send emails to the members - that are MIA. He will get the team membership cleaned before next meeting. - - - pykde fixing - There are some problems with having more than one pykde version with +kdeprefix - as it installs files outside the prefix. The solution might be to "unprefix" it - or to have a new package just with the python files. In any case, patrick was - "nominated" to work on this. - - - handling kdeprefix for base ... eselect - After some discussion we agreed eselect was not the solution - - - koffice status / what is needed - scarabeus informed the team that koffice-2.0 is going to be released at the end - of the month and asked what we should do about it. scarabeus suggested to have - the stable release hardmasked in the tree. We agreed to try to get one of the - rcs in the tree before that to allow users to test it. - - - moving meeting to another date - We decided to have KDE meetings at the 3rd Thursday of the month. - - - stable live status - We didn't discuss this topic. - -As a final note, jmbsvicetto reminded people that we still have a *few* open bugs -and that we should all try to help get that number down. diff --git a/meeting-logs/kde-project-meeting-summary-20090521.txt b/meeting-logs/kde-project-meeting-summary-20090521.txt deleted file mode 100644 index 8b52f4f..0000000 --- a/meeting-logs/kde-project-meeting-summary-20090521.txt +++ /dev/null @@ -1,182 +0,0 @@ -21.5.2009 - KDE Meeting -Roll-call: wired, alexxy, scarabeus, dagger, hwoarang, tampakrap, bonsaikitten, krytzz, yngwin, civil, papillon81, reavertm, lxnay, cryos, jmbsvicetto - -Cryos legitimely excused from not attending much, new baby on the route. Grats to him! :] - -Doc handling -- doc == aplication handbook or handbook, to be decided... -- enable +doc/handbook by default for kde-base -- aplication api documentation - scarabeus write mail asking for some global useflag for it on -dev -- rename doc useflag to handbook with 4.3 again :D -- make it more handleable by eclass rather than in the ebuilds -- lxnay volunteer to do the packages update in overlay -- so priority coruse is: - - mail to dev asking how to do it - - wait a bit and if nothing constructive comes up do the rename for 4.3 - -kde3 -- kill arts, all misc apps needs it removed and be stabled before 3.5.10 stabling -- stable 3.5.10, all kde related misc apps needs to be revbumped/verbumped and stabled before it -- tampakrap starts handling 3.5.10 stabilisation - stable bug asap 15.6. deadline -- writing doc about kde3/4 mixing - tampakrap - -kdeprefix -- long discussion about support of kde4 +kdeprefix install in kde3 and gnome, will chat with reaver about it on aproperiate bug -- add ewarn for user when installing with +kdeprefix so we assure he knows what he is messing with. (controled same like live warning) - -kde 4.3 -- libknotification already handled, pdepend for kdelibs. -- policykit looks ok -- so no much work for 4.3 itself - -kde/kde3 useflag -we voted about it, result: -kde - latest supported kde 4, 5, whatever -kde3 - for now kde 3 series, when kde5 is out there will be kde4 useflag and so on,... -as long as new version is expected to be highly experimental we will have kdeX where X is the version number. When proper support in portage arrives it mutate into kde and older kde mutate to kdeY where Y is X-1 - -phonon -- ship snapshot into the tree with kde 4.3 -- separating xine part to be able use qt-phonon instead of normal phonon with kde - probably reaver - -CODE: -improve it, and add requirements we find out that are needed -since next meeting the code will be considered final, and not folowing it will be punished - -relwithdebuginfo: -deffered after some work on it, not worth efforts - -GUIDE: -tampakrap promised to write the guide for kde3/4 mix that will cover also kde4 installing - -kdebindings: -scarabeus + reaver: invent some logic there; delegate work to other HTs - -sabayon: -discuss the topic more with joost_op at some other more convinient time -so far done -> -bugs from ppl with @sabayonlinux.org will be handled legitimely as our bugs -and we will reflect them as HTs for kde team so we dont have recheck reported things (aka we trust sabayon devs :}) - ------------------------------------------------- -Qt topics ------------------------------------------------- - -Rollcall Qt herd ----------------- - -- hwoarang, tampakrap, yngwin present -- carlo absent -- recruits wired, Pesa and spatz present - - -Meeting length --------------- - -The KDE Project meeting was going on for too long, all agreed. It was suggested -that it would be good to have more frequent and shorter meetings. Also, Qt -topics could be discussed early in the meeting. Details will be discussed at -another time. - - -Phonon issues -------------- - -KDE herd has asked us to introduce a kde useflag for ebuilds depending on:: - || ( x11-libs/qt-phonon media-sound/phonon ) -so that media-sound/phonon can be preferred for KDE users, as a workaround for -current portage shortcomings. yngwin will work out a proposal for affected Qt -ebuilds. - -Also, the suggestion was offered to split the backends from phonon into -separate packages (gstreamer from qt-phonon, and xine from kde's phonon), so we -could have one phonon core package (most likely x11-libs/qt-phonon). It was -decided that this is worth looking into. - - -Recruits --------- - -As to the status of recruits for the Qt team: - -- wired is done with the quizzes, so he only needs grilling by a recruiter and - can be expected to become a full dev within the next few weeks -- Pesa has been very active already in contributing -- spatz just joined us as newest recruit -- sping is busy with GSoC and will continue recruitment process after that, he - is especially interested in Qt3/KDE3 maintenance - - -Qt status in tree ------------------ - -- bug 266201: 4.5.1 is going stable, but arches are taking their time (only - alpha and ppc so far) -- bug 270475: bug in the eclass about the platform switch, which affects - chroots and some arches like ppc, a solution is being worked on in the - overlay -- bug 235685: webkit sigbus on sparc, we will try to get upstream to fix it, in - the meantime we can use a patch on sparc only (and maybe on other arches like - alpha) -- bug 270769: ppc rendering fix will be fast-tracked for stabilization -- bug 209626: make qt eclasses ready for eclass-manpages, hwoarang offered to - take care of this -- bug 224951: qt4-qtruby has been hardmasked for a while, so we should fix or - remove the package; decided we'll work on it to see if it's fixable, - otherwise ask ruby herd to agree with removal; yngwin will commit his - intermediate work to overlay -- bug 236341: Pesa and hwoarang will work on removing automagic deps from PyQt4 -- bug 43827: qvfb and related embedded ebuilds could be proxy-maintained, we - will approach users that might be interested - - -Overlay -------- - -As mentioned during the discussion of the KDE overlay's CODE document, we -should start using similar commit policies, especially starting the commit -message with $PN. - -Both 4.5.9999 and 4.9999 versions of Qt ebuilds in overlay are actively -maintained and used, so status is OK. - -A lot of packages are being moved from overlay to the official tree, so work -there is progressing well. Pesa will work with ali_bush to get the latest -version of qtjambi into the tree. - - -Eclasses --------- - -There has been discussion on -dev ML about blocking mixed Qt versions. Paludis -doesn't handle the blocks and dependencies the same way portage does, but it -was concluded that the proposal currently in overlay, which works fine with -portage, is the best solution so far, so we will go ahead and implement that in -the official tree as well. - -It was also decided to remove the custom-cxxflags useflag and the default -strip-flags from the qt4-build.eclass, as testing has shown that Qt is not as -sensitive to optimized flags anymore. We will let this change coincide with -committing the 4.5.2 (next release) ebuilds into the official tree. - -There has been a lot of development going on in the qt4-edge.eclass (the -overlay version of qt4.eclass). We have implemented additional default phases -for src_configure and src_install, the eqmake4 function has seen a lot of -improvements, and there is experimental functionality for handling translation -files. - -We decided to add that as a new eclass to the official tree, once the ongoing -work on eqmake4 and translations crystalizes. We will then mark the old eclass -as deprecated and open a tracker bug for migration of packages to the new -eclass. There was some brainstorming about naming the new eclass, but -bikeshedding is to be continued outside of the meeting. - - -Elected Qt team lead --------------------- - -As we are now a fast growing team, yngwin felt the need to bring up the issue -of elections for a Qt team lead, as he assumed the position when no one was -looking after qt herd. The decision was this is not needed, as the team members -are unanimously happy with the current situation of yngwin being the de facto -leader. diff --git a/meeting-logs/kde-project-meeting-summary-20090618.txt b/meeting-logs/kde-project-meeting-summary-20090618.txt deleted file mode 100644 index 1a7b140..0000000 --- a/meeting-logs/kde-project-meeting-summary-20090618.txt +++ /dev/null @@ -1,51 +0,0 @@ -Rollcall: -yngwin, scarabeus, tampakrap (delayed), hwoarang, spatz, Pessa, alexxy, reavertm, wired, patrick, jmbsvicetto (late) -Carlo: slackermark - -Topics: - -Formulate some kind of official policy for qt3 apps and their future -- Qt3 apps will follow the KDE3 example and will share one overlay for the stuff with it. Users will maintain it. -- Addition to main tree of new Qt3 apps is *highly* discouraged. -- Qt3 useflag is being marked as discouraged (removal from profiles and so on) since NOW :] -- A draft with ideas for it will be sent to the -dev ml by yngwin - -Solving the python issues within KDE4 - currently with +kdeprefix KDE 4.2 and 4.3 can't live next to each other due to packages installed into site-packages for python. -- the issues running new pykde with old pykde using apps must be tested (pykde from 4.3 and python apps from 4.2) -- if above test prove not working, KDE misc apps will be forced to look into slotted dir in site-packages folder -- will be done by reavertm and patrick -- this issue is a stabilisation blocker - -Solving the final question about kdeprefix. -- voting about kdeprefix mask in profiles (users can still unmask it, but kde is not as solid as with -kdeprefix) -For this vote our HT reavertm was allowed to vote since he is one of the few whom spent their time on it and are capable of handling kdeprefix. -reavertm = mask -scarabeus = mask -jmbsvicetto = can live with mask -patrick = abstain -alexxy = mask -- outcome was that it will be masked in profiles. -- alexxy will add the mask and adjust the guide. - -Handle the PyQt3 qscintilla dependencies -- it seems that the Qt team has not decided if there is an issue or not. :P -- it will probably be mostly fixed by removal of Qt3 from profile. See topic no. 1. -- amarok will have python useflag removed and needed scripts will be removed -- introduce blocker between PyQt and PyQt4 - -KDE 4 Stabilisation. -- Jorge decided to target 4.2 for stabilisation. -- stabilisation bug will have to be opened -- tracking bug will have to be opened and bugs wrangled (volunteers??) - -Review the useflags we enable by default in Qt herd -- rename gtkstyle to gtk in qt-gui -- drop IUSE defaults for useflags enabled by desktop profiles - -Progress of KDE3 mess and way how anyone can help (here we call even for non-kdeteam devs) -- KDE3 misc apps are slowly moving forward - mail to dev asking for help :] -- arts flag removal is also slowly moving - (scarabeus will remove optional dep on arts by blocking it in eclass if scarabeus get some time, or anyone else can do it) - mail the dev ml announcing its death, and asking maintainers for cooperation. -- mail the dev ml announcing we need some KDE3 dedicated dev diff --git a/meeting-logs/kde-project-meeting-summary-20090820.txt b/meeting-logs/kde-project-meeting-summary-20090820.txt deleted file mode 100644 index 280f93b..0000000 --- a/meeting-logs/kde-project-meeting-summary-20090820.txt +++ /dev/null @@ -1,41 +0,0 @@ -Roll-call: -pesa - excused (no net) -tampakrap - excused (family issues) -scarabeus, ABCD, ayoy, patrick, dagger, jmbsvicetto, revartm, wired, yngwin - -KDE-3: -- As discussed before, the KDE team is going to move all KDE3 ebuilds to an overlay. The new -overlay hasn'te been named yet, but will probably be called kde-junk, kde-sunset or something -similar as we plan to use it for KDE stuff that is removed from the tree. -KDE3 is going to be moved to the overlay either after KDE-4.4 is out if nothing evil happens, -or after we get 2 KDE4 minor versions marked stable - which likely means around the end of -the year. -- We are still looking for KDE maintainers. It seems sping might be interested - yngwin will -talk to him. -- Due to the current state of the KDE3 tree source, the lack of support by upstream and the -increasing security concerns, it's likely that we'll mask KDE3 soon. We're delaying the mask -until we get a version of KDE4 marked stable - unless more security issues crop up. -We plan to make an anouncement on Gentoo homepage and to write a news item about the status -of the KDE3 tree and the security implications. -We plan to keep KDE3 around in the tree until KDE-4.4 is released (but it will likely remain -masked) until it's moved to the new overlay. -- Before we remove KDE3 from the tree, we plan to have a news item, planet blog entries, forums -thread and front page announcement about it so the kde3ers won't scream for help all over the -place - jmbsvicetto. - -KDE-4: -- It was decided by a vote not to ask for 4.2.4 stabilization. It will be dropped from the tree. -- Instead, the current plan is to get 4.3.1 marked stable. For that, we need to focus on the -bugs in the tracker[1] and everyone needs to work on it. - -QT4-TNG eclass: -Will be sent for review onto -dev in a week with the -tng name. No better name found out. - -Future projects: -- Documentation polishing -- Branding the KDE -- Fix upstream buildsystem to allow install of different versions into a shared prefix - -Sets: -. Adjust it as for bug #272488 or from the ground up for exact specs we need - -jmbsvicetto (we need to poke him about it often so he won't forget to do it) diff --git a/meeting-logs/kde-project-meeting-summary-20100225.txt b/meeting-logs/kde-project-meeting-summary-20100225.txt deleted file mode 100644 index 38e8cd4..0000000 --- a/meeting-logs/kde-project-meeting-summary-20100225.txt +++ /dev/null @@ -1,66 +0,0 @@ -1) New KDE Team Leader elections: -Scarabeus is the new leader with the majority of votes, congratulations - -2) Review work flow for KDE minor bumps and improve collaboration with arch teams -We decided to skip this topic for next meeting, after preparing some documentation -on how arch teams can approach packages in the kde overlay. For the record, scarabeus -proposed this model: (1) BUG (2) keywordlist (3) portage addition (4) touching profiles -while jmbsvicetto proposed first to ask arch teams to test new deps in the overlay, if -they don't want to use the overlay, try to add a snapshot or an early release masked in -tree and ask them to keyword it, then follow scarabeus' policy. - -3) KDE-4.3.5 stabilization -The KDE team is ready on this, we are just waiting for arches to finish. When they -do, we will remove both 4.3.3 and 4.3.4 from tree. - -4) KDE-4.4 status -4.4.0 seems very unstable, people are hitting crashes with krunner and plasma, and -the virtuoso migration was not smooth for everyone. Thus, we agreed that 4.4.1 or -4.4.2 will be a stable candidate, depending of the status of 4.4.1. - -5) amarok / mysql-5.1 status -jmbsvicetto reported that it seems to work for most people for the past three days as -noone complained. Just amarok[embedded] needs a libmysqld.so as mysql-5.0 did. Jmbsvicetto -said he resumed his work to get a working patch again. - -6) enterprise useflag for kdepim stuff (a use flag to follow the enterprise branch of the -kdepim repo, only for trunk) -The problem is that kdepim in trunk currently is broken, more specifically kmail as mail -storage is being migrated to akonadi, and it seems it will stay broken for a while. Tampakrap -tried to package the enterprise branch a week ago, but some packages failed to compile, so -it may need more work. There is also an enterprise switch in CMakeLists.txt, but since we are -splitting the module, we need a new batch kdepim ebuilds that will block the current kdepim ones. -This will allow us to have an always working kdepim though. It seems a lot of work that noone -seemed interested to do, so we decided to announce it in gentoo-desktop mailing list and call -for help. Tampakrap will do it. -Speaking of trunk, we also discussed about the 4.5 snapshots, and if we should provide them. We -decided that since kdepim is broken, we won't package them yet, until version 4.4.70. Alexxy -will take care of them. - -7) koffice status -Scarabeus said that current koffice needs review of its depedencies based on CMakeLists.txt. -Tampakrap will do it and bump it in tree. - -8) knetworkmanager status -Tampakrap said that knetworkmanager seems crashy, but people want it, so we will ask dagger to -create snapshot, as he is the networkmanager maintainer. - -9) documentation status -Documentation seems fine, reavertm proposed to remove kdeprefix and maybe sets refference from -the guide. Tampakrap will take care of it. -Scarabeus with the help of jmbsvicetto will clean up the member list. - -10) drop prefixes from kde ebuilds (like kdeartwork etc) -Noone agreed on this. - -11) change kde-meta (and @kde-*) to include all modules (plus the developer specific ones) -Tampakrap proposed to have every single KDE module in kde-meta (including the developer ones -like kdesdk and kdewebdev). Many members were opposed, so the idea of a developer USE flag -for kde-meta was introduced. The discussion will be continued in gentoo-desktop mailing list. - -12) stabilization of misc kde apps -Wired owes us a script that checks for stable candidates in tree. - -13) patches of kde-packager -Jmbsvicetto and ABCD will take care of applying or opening bugs about patches that were -announced in kde-packager mailing list and need to be applied. diff --git a/meeting-logs/kde-project-meeting-summary-20100318.txt b/meeting-logs/kde-project-meeting-summary-20100318.txt deleted file mode 100644 index 1c4f5db..0000000 --- a/meeting-logs/kde-project-meeting-summary-20100318.txt +++ /dev/null @@ -1,38 +0,0 @@ -1) Removal of innactive KDE team members -Since there were no objections last month for scarabeus' draft, he'll proceed in -removing some members that don't follow the rules. The draft is at -http://dev.gentoo.org/~scarabeus/kde-team-rules.html - -2) Review work flow for KDE minor bumps and improve collaboration with arch teams -Nothing more was to be said from the last meeting, both scarabeus and jmbsvicetto's -proposals were accepted. - -3) KDE-4.4 status -4.4.1 seems to be a good release, with not many problems so far. Also, there were -people working on the kdebindings which was suffering mostly. It will be a stable -candidate, and the bug will be openned at start of next month. - -5) enterprise useflag for kdepim stuff (a use flag to follow the enterprise branch of the -kdepim repo, only for trunk) -The call for help didn't bring in any volunteers, so there was no progress on this. Sput told -that this is very important to be fixed, as kdepim may not be ready for KDE 4.5. Tampakrap will -try again to raise the issue in ml. - -7) koffice status -KOffice still is in bad status, tampakrap and wired will work on this. - -8) change kde-meta (and @kde-*) to include all modules (plus the developer specific ones) -Following last meeting's discussion on this, tampakrap opened a mail asking for people's -opinion on this in the gentoo-desktop mailing list, and many people liked the idea. So, -with scarabeus' permission, tampakrap will add this to kde-meta ebuilds. Kdebindings will -stay out for now until they all compile. - -9) patches of kde-packager -No actions were done on this, jmbsvicetto said he'll try to take care of it. - -10) Split desktop profile -After a long discussion in gentoo-dev and gentoo-desktop mailing lists, and with the -approval of the gnome and qt teams (the leads mostly, leio and yngwin), tampakrap -will finally split the desktop profile to kde and gnome subprofiles. Leio raised the -need of a better profile system that will support mixed profiles. Tampakrap liked the -idea and is willing to work on this, but it is going to be long-term diff --git a/meeting-logs/kde-project-meeting-summary-20100604.txt b/meeting-logs/kde-project-meeting-summary-20100604.txt deleted file mode 100644 index dcd7c9b..0000000 --- a/meeting-logs/kde-project-meeting-summary-20100604.txt +++ /dev/null @@ -1,21 +0,0 @@ -Meeting topics: -0) roll-call -ABCD, alexxy, dilfridge, wired, scarabeus, deathwing00, patrick, jmbsvicetto -1) KDE 4.4 Stabilisation process. - creating stable team within kde team -We will add 4.4.4 to main tree, and start the required processes 7 days from that point. -No stable team since noone volunteer. -2) KDE 4.5 KDEPIM approach - a. give developers one week to express what they feel about kdepim and to see if anyone volunteers to work on it - b. if that fails or we can't find anyone willing to do it, make a public announcement about the issue, explain it and give a few options to users: - b.1 have interested parties show up and work in the overlay to get it done - (what can be given as option to the community) - b.2 have users vote for us to just ignore kdepim until it gets working - b.3 give the above 3 options for someone to work on -3) Koffice 2.2 and designated maintainer choice -we shall try same approach as for kdepim to see if anyone is interested -4) Accepting major patches that alter stable branch (pulseaudio) [vote] -so lets keep status "if you keep it backported and polished you can have it..." together with the old "you break it, you fix it" -5) People in the team and their inactivity -Everyone in team is asked to reconsider their status. If they are not really active team members they should just remove themselves. -Everyone with no evident work on kde packages for last 2 months will be removed from the team. -Anyone who wants to join back or just join is welcome and just need to ask and be active. -6) open floor \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-summary-20100902.txt b/meeting-logs/kde-project-meeting-summary-20100902.txt deleted file mode 100644 index ff368de..0000000 --- a/meeting-logs/kde-project-meeting-summary-20100902.txt +++ /dev/null @@ -1,37 +0,0 @@ -1) KDE 4.5 status and plans to put it in Portage - -We agreed that KDE 4.5.1 is suffering of some important bugs, and after -a long discussion we decided to put it in portage, but it will never -make it to stable branch. We are mentioning the upstream bugs, as we -think that users should be aware of them before updating: - -- https://bugs.kde.org/show_bug.cgi?id=247144 -- https://bugs.kde.org/show_bug.cgi?id=246931 -- https://bugs.kde.org/show_bug.cgi?id=230247 <-The most important - -Also, keep in mind that KDE SC 4.5 lacks the KDEPIM suite, so users -should use KDEPIM 4.4.5 instead, which is also stable in portage tree. -In case of an update it should be smooth. - -2) KOffice 2.2 status - -There are a few issues with it. The bump to 2.2.2 won't be so easy, -and most of the linking taking place in koffice-libs is not perfect. -dilfridge and tampakrap will take care of it, but it may not happen soon. - -3) KDEPIM beta packages are released - -This was skipped as alexxy, our snapshots master, was absent. It will -be discussed in gentoo-desktop mailing list - -4) Open Floor - -- dilfridge reported that digikam is almost ready, he cleaned up the -patches a lot and will tell reavertm when to move them upstream -- tampakrap reported that he is going to unmask knetworkmanager -- reavertm encouraged people working with live and tagged ebuilds to use -kde-misc/kde-overlay-servicemenus. It is a simple Compare/Merge service -menu, to avoid manual copy paste. -- tampakrap, as substitute leader, is going to remove some inactive team -members, as there were a lot of notices in the past. - diff --git a/meeting-logs/kde-project-meeting-summary-20110210.txt b/meeting-logs/kde-project-meeting-summary-20110210.txt deleted file mode 100644 index c38edf6..0000000 --- a/meeting-logs/kde-project-meeting-summary-20110210.txt +++ /dev/null @@ -1,107 +0,0 @@ -Present: alexxy, dilfridge, jmbsvicetto, scarabeus, tampakrap -Absent: ABCD, spatz -HTs: krytzz, papillon81 - -0) Elect new lead - -nominees: -Accepted: bonsaikitten, dilfridge, reavertm, tampakrap -Refused: alexxy, jmbsvicetto, scarabeus - -results: -scarabeus -> tampakrap -dilfridge -> tampakrap -bonsaikitten -> tampakrap -tampakrap -> reavertm -alexxy -> tampakrap -reavertm -> tampakrap -jmbsvicetto -> tampakrap - -tampakrap is the new KDE Team Lead - -1) Status regarding hal - -Since KDE SC 4.6 is out, we don't need it anymore. As soon as 4.6 -gets stable, hal can die. - -2) Should we try to form a "stable KDE devs" team? Meaning just call for volunteers on the dev ml? - -dilfridge stated that since most of the kde team members use ~arch, -stable seems to lag behind. The problem is very obvious now, mainly -because we haven't stabilized 4.4. The problem will go away as soon -as 4.6 gets stable though. -Apart from main kde, the misc apps are also slow in stabilization. -We expect users to request for stabilizations in bugzilla. - -3) kde-git/eclasses migration and status, move kdepim 4.6 beta in tree masked - -reavertm, Sput, and scarabeus did a major cleanup in our eclasses -and added git support to eclasses and ebuilds. In order to migrate -the eclasses to tree we will need to get git-2.eclass in tree first -(it is now in kde overlay as well). ETA: not less than a month. As a -side note, we decided to remove koffice-specific codeout of the eclasses. - -4) Shall we drop useflags kdeenablefinal and/or kdeprefix to simplify code? - -First of all, both useflags are masked. We agreed to keep kdeenablefinal, -since it is an upstream feature. About kdeprefix, the problem is that -bindings are not prefixed, and a possible fix (proposed by reavertm) -would be to slot sip. tampakrap said he'll work on this, and bring the -topic back in next meeting. - -5) Dropping of semantic-desktop useflag with guide update (mostly even kdebase needs it on now) - -This entry is invalid, semantic-desktop is not needed by kdebase. -The problem is in our ebuilds (plasma-workspace is semi broken, -kdeplasma-addons is completely broken). We have open bugs for those, -the problem is clearly in our side. - -6) Making +consolekit and +policikit or removing the useflags as whole (non working stuff run-as is annoying) - -scarabeus and dilfridge are in favour of dropping them, since it -caused a lot of trouble debugging various user reports. reavertm -prefers adding it to IUSE defaults. No consensus was succeeded, -the topic will be continued in the gentoo-desktop mailing list. - -7) HT/overlay/bugzie access policy - -Since we don't have a clear list of who is an HT and who isn't, we -decided to compile a list, and state what priviledges the HT has. -(HT = Herd Tester). Some people don't have time/motivation to complete -their ebuild quiz, thus we'll have two groups of people: - * full HTs (overlay access, editbugs, access to ktown, IRC cloak) - * overlay commiters -We decided to drop the KDE HT Lead title, seems rather useless. - -8) LiveDVD issues - -LiveDVD comes with KDE SC 4.6 as default DE, and we called likewhoa -(the guy behind it) to report any issues. He said that everything -seems to be fine, but random users wanted the cool gentoo graphics -to be applied to in-tree ebuilds as well. The KDE Team is willing -to do that, likewhoa said he'll provide us some artwork and we'll -discuss again the USE="branding" issue. - -9) documentation status - -There has been a major improvement in the guide, added some 4.6 specific -tips and troubleshooting parts, we need to add a hal->udev migration -guide, and migrate some texts that are in kde overlay to guidexml. - -10 & 11) 4.6 (and misc apps with 4.6) status , Early discussion about 4.6 stabilization - -KDE SC 4.6 is going fine, we all agreed that 4.6.1 could be a good -candidate, we'll discuss it again after its release. About a 4.6 -KDEPIM version, no idea yet, we'll have to wait on upstream moves first. -Most misc apps seem to be fine with 4.6 as well. - -*) Open floor - -One major issue is digikam, it comes with lots of bundled libraries, -which violates the Gentoo QA Policy. We heard that Debian has same -thoughts on the matter, we'll have to bring them to table. Relevant -bug report: https://bugs.kde.org/show_bug.cgi?id=265328 - -Desktop Summit! We were invited last year to Akademy to give a talk -about Gentoo-KDE, noone made it. Some of us expressed interest for -this year's event, which combines GUADEC and Akademy. \ No newline at end of file diff --git a/meeting-logs/kde-project-meeting-summary-20110602.txt b/meeting-logs/kde-project-meeting-summary-20110602.txt deleted file mode 100644 index 772a257..0000000 --- a/meeting-logs/kde-project-meeting-summary-20110602.txt +++ /dev/null @@ -1,44 +0,0 @@ -rollcall -ABCD, alexxy,dilfridge,tampakrap,jmbsvicetto - -1) KDE SC 4.6.80 bump - -jmbsvicetto and alexxy did a great job so far about it, with ABCD -forward-porting the commits to the live ebuilds. It is not ready yet though, -and we'd not recommended to users yet, unless they know what they are doing. -Upstream split some of the tarballs in order to follow the repos for 4.7. We -were very lucky so far, and upstream's split was very similar to ours, apart -from kdebindings, which we'll have to re-package to follow them. - -2) Drop of kdeprefix useflag - -The kdeprefix USE flag is announced to be dropped this Monday. As a result, -we'll have to move all ebuilds to slot 4. We could move them to 0 as well in -order to drop the slotting entirely, but since most of them are already 4 it -will prevent us from doing another massive slotmove. - -3) Useflags in kde profile - -It was decided these useflags to be added to the kde profile: declarative, -dri, kipi, phonon, plasma, semantic-desktop, xcomposite, xinerama, -xscreensaver - -4) KDE SC 4.6.3 stabilization - -First of all, dilfridge deserves congratulations for taking care the -heavy job of doing the 4.6.2 stabilization, along with Qt 4.7 and a large -number of other Qt and KDE applications. Keep in mind that this was a really -hard job to do, since the previous stable version was 4.4.5. Things are now -back in order now, with 4.6.2 fully stabilized and 4.4 completely removed -(finally). 4.6.3 is the next stabilization target, to keep stable tree up to -date. - -*)Open floor - -Andreas said he is interested in doing some cups work, which we hope to affect -KDE and desktop users in general. - -We lost scarabeus, one of our top developers. Thus, -we'd like to remind anyone that we always appreciate the help of new people. -If you are one of the guys that already has access to the overlay, time to -complete your ebuild and end quiz then! diff --git a/meeting-logs/kde-project-meeting-summary-20120116.txt b/meeting-logs/kde-project-meeting-summary-20120116.txt deleted file mode 100644 index bb34fcd..0000000 --- a/meeting-logs/kde-project-meeting-summary-20120116.txt +++ /dev/null @@ -1,70 +0,0 @@ -1. Roll call -alexxy, jmbsvicetto, dilfridge, johu, mschiff, tampakrap, Thev00d00 - -2. Electing a new team leader -Since one year is not over yet, it will be skipped for the next meeting. - -3. What shall we do with kdepim-4.4 -KDEPIM 4.4 is not supported any more by upstream, but on the other hand -KDEPIM2 is still too buggy. We had a discussion if we should remove it -completely or if we should continue maintain it, despite the compatibility -bugs that started to emerge with newer KDE versions. Final decision is that we -will continue support it as long it works with newer KDE SC releases. We'll -keep the kdepim-l10n split package to provide the translations for it. - -4. kdeenablefinal revisited -Since upstream doesn't seem to care about it much, plus it doesn't make much -sense now that there are many split tarballs, we decided to remove it the next -day after the meeting. - -5. phonon-xine removal -KDE upstream acknowledged that this is not maintained anymore. It's already -masked since 2011/12/01. Will be last rited and removed 15 days afterwards. - -6. Qt 4.8 -We expect no big issues with it. Kdenlive is the only known application that -does not build at the moment and will be patched. kde-base/kstyles-4.7.* needs -to be rebuilt after the upgrade, which we'll solve with a combination of -revbump/dependencies (otherwise KDE apps using oxygen style crash). - -7. Dropping RPATH from installed binaries -Postponed for next meeting, need more info from reavertm and/or hardened herd. - -8. To eselect Boost or not to eselect boost -No final decision was taken, discussion will be moved to -dev mailing list. - -9. Bugs -* dev-util/cmake picks always the latest boost. -* Fix in overlay since 13. Dec. Move to tree? -https://bugs.gentoo.org/show_bug.cgi?id=335108 -see 8. - -* cmake-utils.eclass PREFIX is not defined, any progress? -https://bugs.gentoo.org/show_bug.cgi?id=358059 -Postponed for next meeting - -* Remove hard dep on media-libs/phonon from kde-base/kdelibs -https://bugs.gentoo.org/show_bug.cgi?id=356681 -https://bugs.gentoo.org/show_bug.cgi?id=388041 -Although it is possible to build kdelibs against qt-phonon, it is not -recommended by upstream. Decision postponed for next meeting. - -* Eclass problem with handbook without LINGUAS. -https://bugs.gentoo.org/show_bug.cgi?id=372457 -Needs more analysis. Postponed. - -* MacOSX request for cmake-utils.eclass: Remove force of -* CMAKE_BUILD_WITH_INSTALL_RPATH=TRUE -https://bugs.gentoo.org/show_bug.cgi?id=398437 -That was a request by the Gentoo Prefix team, and is accepted - -* Revise the change "semantic-desktop? -> semantic-desktop=". Why was the -* change needed. -https://bugs.gentoo.org/show_bug.cgi?id=396491 -We had split opinions on this. Skipped for next meeting, as we need -reavertm's input on this. - -10. Open floor -Tampakrap will make a KDE SC 4.8 release party in Prague, more info coming soon. -Qt meeting on Thursday 26th Jan. -See you at fosdem :) diff --git a/meeting-logs/kde-project-meeting-summary-20120322.txt b/meeting-logs/kde-project-meeting-summary-20120322.txt deleted file mode 100644 index 478887b..0000000 --- a/meeting-logs/kde-project-meeting-summary-20120322.txt +++ /dev/null @@ -1,76 +0,0 @@ -1. Roll call -alexxy, dilfridge, johu, mschiff, scarabeus, tampakrap - -2. Electing a new team leader - -nominees: -Accepted: dilfridge, johu -Refused: tampakrap, scarabeus - -results: -johu -> dilfridge -dilfridge -> johu -tampakrap -> dilfridge -alexxy -> dilfridge -mschiff -> dilfridge -scarabeus -> dilfridge ----------------------- -dilfridge:5 - johu:1 ----------------------- -dilfridge is the new KDE team leader with the majority of votes. -Congratulations!!! - -3. Dropping RPATH from installed binaries -Add a RPATH entry for every library dir that is not in the system library -directories in ld.conf are not automatically considered as system library -dirs, but only some static list of dirs. -Everyone agreed on RPATH removal. We will introduce a patch with KDE SC 4.8.2 -to remove the RPATH and move it to the main tree. - -4. Bugs -* Remove hard dep on media-libs/phonon from kde-base/kdelibs -https://bugs.gentoo.org/show_bug.cgi?id=356681 -https://bugs.gentoo.org/show_bug.cgi?id=388041 -Upstream says "technically you can replace phonon with qt-phonon, but that's -just stupid because you lose functionality". Another argument against it, is -that qt-phonon will be removed with qt5. We wont fix the bug and keep phonon as -hard dep. johu will take care of the bug after meeting summary is available. - -* Eclass problem with handbook without LINGUAS. -https://bugs.gentoo.org/show_bug.cgi?id=372457 -The handbook eclass code is pretty confusing for all in meeting present -members. It was written by reavertm. We decided that we will mail reveartm to -fix handbook eclass code, because he has the most knowledge in it. dilfridge -will take care of contacting him, it's his first lead task. - -* Revise the change "semantic-desktop? -> semantic-desktop=". -https://bugs.gentoo.org/show_bug.cgi?id=396491 -Some packages rely on semantic-desktop capabilities in other ones. tampakrap -is volunteers to take care of the bug. - -5. Open floor -* KDE 4.8 stabilization -KWin does not build anymore without opengl support. kde-base/kmail-4.8.1 -crashes, but upstream patch can be backported. KDE SC 4.8.1 has tons of -bugfixes, compared to to 4.8.0. The majority votes for KDE 4.8.1 as stable -candidate. johu will prepare stabilization. - -* Test failures -creffett brought up dbus-related test failures. johu recommended to get -virtual-dbus eclass running. dilfridge suggested if one or two test fails -or restrict. The problems with virtual-dbus is that you can't run bash -commands in it's environment. creffett will be responsible for this. - -* New members -Welcome to three new members of the project: creffett, kensington and -dastergon. They are in the process to become gentoo developer and mentored by -tampakrap. creffett and kensington have already open 'new developer' bug. -dastergon doesn't have an open bug yet. - -* Comeback -scarabeus re-joined KDE herd. Welcome back!!! - -* Reduced work time -mschiff mentioned that he will not have much time for the KDE herd due to -real life priorities, he will be back in may. tampakrap will spent most of his -time for gentoo infra team. diff --git a/meeting-logs/kde-project-meeting-summary-20120419.txt b/meeting-logs/kde-project-meeting-summary-20120419.txt deleted file mode 100644 index 267ca5b..0000000 --- a/meeting-logs/kde-project-meeting-summary-20120419.txt +++ /dev/null @@ -1,41 +0,0 @@ -1. Roll call -alexxy, dilfridge, kensington, johu, scarabeus, tampakrap, thev00d00 - -2. KDE SC 4.8.2 stabilization after it is 30 days in tree? -KDE SC 4.8.1 is stable for amd64 and x86, ppc is still pending. We decided to -skip the stabilization for KDE SC 4.8.2 to reduce the work load for the arch -teams. Scarabeus suggested that we can stabilize other kde herd related -packages in the meantime. No objections, so we will walk over the packages, -search for candidates and file stable bug requests. - -3. Calligra 2.4.0 stabilization after it is 30 days in tree? -We are getting more and more bugs related to koffice. Calligra is the -successor of koffice. Qt 4.8.1 stabilization will be needed before, as a build -requirement for calligra. No arguments or objections against stabilization, -which will end up in replacement of koffice with the normal last rite -procedure. - -4. Do we want to stabilize KDE SC 4.9.x on arm? -The number of arm gadgets will go up more and more, while ppc machines are -falling apart. KDE SC should work on arm. Sabayon would benefit by -stabilization too. We will need Qt 4.8.x stable on arm before. Unfortunately -none of the kde herd members have the hardware to test it. So we will need -volunteers/testers for that. Additionally we could think about packaging -plasma-active too. Dilfridge will ask arm herd about the idea, if they like -it, he will blog about it. - -5. Remove tar command ewarns in eclasses? -They are useless and anoying nowadays. Scarabeus acknowledged that they can be -removed. - -6. Open bugs -* Bug #358059 - cmake-utils.eclass PREFIX is not defined -Scarabeus acknowledged that the patch is correct. We will test it in kde -overlay first. - -* Bug #372457 - doc dir is not correctly disabled by kde4-functions.eclass if -NOT kde-base and LINGUAS is unset -Chris Reffet found a solution. We will test it in kde overlay first. - -7. Open floor -* Tampakrap mentioned that SLES will have KDE 4.8 soon. diff --git a/meeting-logs/kde-project-meeting-summary-20120517.txt b/meeting-logs/kde-project-meeting-summary-20120517.txt deleted file mode 100644 index 463ee86..0000000 --- a/meeting-logs/kde-project-meeting-summary-20120517.txt +++ /dev/null @@ -1,73 +0,0 @@ -1. Roll call -alexxy, creffett, dilfridge, johu, kensington, reavertm - -Welcome new developers kensington and creffett. Thanks to JoseJX for -participating as member of the powerpc team. - -2. Add LINGUAS support to cmake-utils.eclass -Agreed to add a loop like that in qt4-r2.eclass to reduce ebuild code. It -expands the contents of LANGS to IUSE as linguas_*. A generic linguas handling -is not planed yet. - -3. Live KDE ebuilds have tests restricted -The usefulness of tests on live ebuilds was brought into question, since there -are enough problems with tests on normal releases. Agreed to enable tests when -I_KNOW_WHAT_I_AM_DOING is set. - -4. KDE 4.8 stabilization and PowerPC -The stabilization and keywording was pending up to the team meeting date, -because of gcc47 as requirement to restore the keywords on ppc/ppc64. This -blocker was mistaken added. PowerPC needs just Qt 4.8.1 to keyword KDE 4.8. -So there are no reasons the discuss to drop the ppc support from kde-base. -We never stabilized a KDE version on ppc64, because ppc64 has problems with -the size of the table of contents for ELF function calls that will be fixed -with gcc 4.7. johu ask for voting on dropping ppc64 at all. No real -majority/opinions about it. JoseJX prefers that ~ppc64 not be dropped from KDE -keywords. Agreed that JoseJX would keyword ~ppc, and if there were no problems -would also keyword ~ppc64, topic will be revisited. - -5. Bugs -* Trying to change full name in KDE System Settings results in error or crash -https://bugs.gentoo.org/380899 -There is an existing workaround to disable the change full name functionality. -kensington will talk to upstream about the issue, and if there is no good -response in 2 weeks' time, we will apply the workaround. - -* app-cdr/k3b: use media-libs/musicbrainz:3 instead of :1 -https://bugs.gentoo.org/410347 -Agreed that musicbrainz:1 is obsolete and that k3b does not appear to actually -use musicbrainz even when enabled. Dependency on musicbrainz will be dropped. - -* dev-util/cmake: FindPythonLibs behaviour broken by Gentoo patches -https://bugs.gentoo.org/405181 -Dilfridge said that we should remove the patches and use command-line defines -to force specific python versions, agreed to test that. - -* kde-misc/networkmanagement-0.9.0 and kde-misc/networkmanagement-0.8_p20110714 -wrong doc dir specified - https://bugs.gentoo.org/410139 -Nobody has been able to reproduce the bug. Dilfridge suggested asking for more -information and will investigate further. - -* kde-misc/interceptor - KDE4 Plasmoid - intercept (catch) the log info from -the syslog - https://bugs.gentoo.org/383733 -creffett suggested dropping this request because it requires too many big -configuration changes for a plasmoid. Agreed to remove kde from CC list and -suggest taking the ebuild to sunrise. - -* dev-util/cmake-2.8.6-r4 - stop Xvfb after failed test phase -https://bugs.gentoo.org/406353 -Need input from gentoo-portage team about what phase could be used to clean up -xvfb after test failures. Kensington mentioned that the same issue will affect -virtualdbus. - -6. Open Floor -* KDE 4.9 Beta -Dilfridge reported that KDE 4.9 beta is coming out soon. - -* Groupdav calendar bug in kdepim-runtime -Discussed whether to stabilize kdepim-runtime base version or -r2, which has a -possible fix for https://bugs.gentoo.org/show_bug.cgi?id=415401 but no -positive feedback. Agreed to go with -r2. - -* creffett away -creffett will be out for a month on a trip with little internet access. diff --git a/meeting-logs/kde-project-meeting-summary-20120621.txt b/meeting-logs/kde-project-meeting-summary-20120621.txt deleted file mode 100644 index 6f246e9..0000000 --- a/meeting-logs/kde-project-meeting-summary-20120621.txt +++ /dev/null @@ -1,39 +0,0 @@ -1. Roll call (4 minutes, 5 minutes planned) -Present: alexxy, dilfridge, scarabeus, tampakrap - -2. Move KDE 4.8.4 to the tree, and in which variant? (1 minute, 5 minutes planned) - It seems that the problems have been solved with a) newer soprano or b) reverted commit. - Which way do we want to go? -All in favour of reverting the commit in kdelibs and pushing 4.8.4 to the tree to work -with "old" soprano. - -3. Once it's out, should we move KDE 4.9.0 to the tree? (3 minutes, 10 minutes planned) - Currently 4.8.90 looks quite solid, so this is a real option. -All in favour of adding 4.9.0 to the main tree as ~arch - -4. Udisks2 (8 minutes, 5 minutes planned) - On request from Samuli I've added the Udisks2 patch from RedHat to kdelibs. This - *replaces* the udisks:0 solid backend with a new udisks:2 version. Has according - to Wulf (Philantrop) still some issues. - Feedback? Experiences? Keep for 4.9.0 or (temporarily) ditch again? -No decision, some discussion with alexxy and Philantrop about the problem. We'll keep -watching Fedora's code and talk to the Fedora maintainers. - -5. Bugs (1 minute, 30 minutes planned) - * app-cdr/k3b: Excessive use of REQUIRED_USE (and wrong combination USE="lame"+"encode") - REQUIRED_USE was added, otherwise USE="-encode lame" does nothing - Options: - 1. Revert to original behaviour - we don't care that USE="-encode lame" does nothing - 2. Keep the REQUIRED_USE, but rename lame -> mp3 - 3. Drop the encode flag, but move the optional RDEPS to an elog - 4. Drop the encode flag and keep optional RDEPS (current behaviour) - https://bugs.gentoo.org/show_bug.cgi?id=417235 -Postponed since the principal actors involved were absent. - -6. Open floor (10 minutes, 15 minutes planned) -tampakrap asks for more speakers and workshop organizers at the Gentoo miniconf October in -Prague. Some ideas are thrown around, nothing definite yet. - -[21:34:02] meeting closed -[21:34:13] i think we just made a new speed recoed -[21:34:19] :) diff --git a/meeting-logs/kde-project-meeting-summary-20120816.txt b/meeting-logs/kde-project-meeting-summary-20120816.txt deleted file mode 100644 index b68e32f..0000000 --- a/meeting-logs/kde-project-meeting-summary-20120816.txt +++ /dev/null @@ -1,95 +0,0 @@ - -KDE team meeting summary - - -1. Roll call -KDE team members present: -ago, creffet, dilfridge, jmbsvicetto, johu, tampakrap, thev00d00 - - -2. KDE SC stabilization: discuss/vote on the following options: -a) First 4.8.5 as decided in a former meeting, then 4.9.1 / 4.9.2. -b) Skip 4.8.5, start with 4.9.0 / 4.9.1 directly. -c) Other? - -After some discussion, a vote resulted in 5 votes for a), 1 vote for b). 4.8.5 -has two remaining (upstream) issues (da translation error and a missing theme -for ksplashx) which will be locally addressed in time before stabilization. - -Ago suggested that we should follow the Kernel crowd, and only ever stabilize a -late release in every KDE series ("x.x.7/8"). Most of the other team members -were against that idea, since -* we'd find Gentoo-specific problems only very late then (when the large crowd - migrates) -* and people will complain if we wait with stable upgrades too long. -As a compromise we settled on "4.9.0 will never go stable, we talk about 4.9.1 -when it's out for a while". - - -3. Solaris patches: We apply many patches to support Solaris, but there seems to -be no prefix keyword. Does anyone know anything about them? If we are supporting -Solaris, Kensington would like to push these patches upstream. Does anyone have -access to a box to test if they are still useful? - -Nobody present had any opinion or cared about the solaris stuff. As a result it -was decided to drop the patches. - -On #gentoo-prefix this was ack'ed later by darkside for the prefix team. ryao -noted there that Qt is broken on Prefix at the moment, and that the KDE patches -could become relevant again after that is fixed. - - -4. KDE stable subproject: Ago proposed a "KDE stable subproject" some time ago -via mail. The idea is that the subproject members test KDE stable candidates on -an otherwise completely stable system as soon as we decide on a stable -candidate, to make fast and bug-free stabilization possible as soon as its -30days in the tree. - -Discussion led to various points: -* Ago is mainly thinking of Gentoo-specific stable candidate QA. -* The "stable subproject" obsoletes the (dead) "herd testers" subproject which - we tried to start up some time ago. -* No quiz required for participation. -* Johu suggested a more upstream-oriented direction ("like kdepim bug day"), - which however seems like a different endeavour. -* In the end, there were no objections, Ago takes care of establishing that - group of people and updates our site. - - -5. Bugs - -5a. Bug 417235: app-cdr/k3b: Excessive use of REQUIRED_USE -Majority decision was to keep the REQUIRED_USE, but rename lame -> mp3 - -5b. Bug 430608: cmake-utils.eclass: add support for dev-util/ninja -It was decided to apply the patch and make building with ninja possible; -however, if the build fails a message about using an unsupported backend -should be logged (if possible). - -5c. Bug 427910: app-office/calligra-2.4.3: move fonts to separate packages -and related bug 427914: www-client/rekonq-1.0: please move Nunito-Regular.ttf -to separate package -Most people present did not really care. Consensus was -* Find out if there is any license problem with the status quo. -* If yes, talk to upstream and try to solve the problem with them. -Nobody volunteered to research the license situation. - -5d. Bug 430858: net-libs/libkolabxml-0.8.0[php] fails -The cause here appears to be that FindPHP4.cmake does not look in -/usr/include/php5.*. (and there is no FindPHP5.cmake). This potentially means -that every search for PHP in cmake is broken (though it appears that nothing in -kde-base at least has IUSE="php", explaining this not being caught). Consensus -was to provide upstream with a FindPHP5 module and ask for inclusion. - - -6. Open floor - -6a. Further discussion about the stable subproject -Tampakrap notes that for recruiting devs a subproject with overlay access is not -the most efficient way, since people tend to be happy with overlay access and -are reluctant to go through the actual recruiting process. We should try to -motivate people to become full developers. In addition he offers to mentor -people. - -6b. Default KDE_SCM -Johu proposes to switch this to git. Noone opposes. diff --git a/meeting-logs/kde-qt-projects-meeting-log-20091119.txt b/meeting-logs/kde-qt-projects-meeting-log-20091119.txt deleted file mode 100644 index 7f1c17b..0000000 --- a/meeting-logs/kde-qt-projects-meeting-log-20091119.txt +++ /dev/null @@ -1,959 +0,0 @@ -[20:45:05] toum toum -[20:46:51] sssh -[20:48:34] *** scarabeus changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 1: Upstream split packages (per kde-scm-interest mail i told you to read)' -[20:52:39] *** Joins: zizo (n=Zizo@host214-182-dynamic.4-87-r.retail.telecomitalia.it) -[20:52:59] *** Parts: zizo (n=Zizo@host214-182-dynamic.4-87-r.retail.telecomitalia.it) -[20:56:35] *** Joins: PSYCHO___ (n=scarabeu@gentoo/developer/scarabeus) -[20:56:35] *** ChanServ sets mode: +o PSYCHO___ -[20:57:05] darn 3g con -[20:59:38] so... meeting time? :) -[21:01:16] yup -[21:01:19] indeed -[21:01:27] anyone can record the histroy? -[21:01:38] i cant log, because quassel is not entirely cooperating right now -[21:01:39] * wired logging -[21:01:48] for the log <- scarabeus -[21:02:04] ok so lets start with rollcall -[21:02:05] even if I seem down my znc/bouncer will keep logging, im on a 3g connection right now (dsl is down) -[21:02:33] *** Joins: spatz (n=spatz@gentoo/developer/spatz) -[21:03:18] *** Joins: ayoy (n=ayoy@gentoo/developer/ayoy) -[21:03:39] *** Joins: mrpouet (n=quassel@gentoo/developer/mrpouet) -[21:03:45] ok so anyone else here? -[21:04:02] *** Joins: wohnout (n=wohnout@88.86.113.238) -[21:04:02] me -[21:04:09] you are so lame -[21:04:11] me -[21:04:12] !herd kde -[21:04:13] (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, ssuominen, tampakrap, tgurr, wired -[21:04:13] * wired here -[21:04:13] and me -[21:04:17] !herd qt -[21:04:18] (qt) abcd, ayoy, carlo, hwoarang, spatz, tampakrap, wired, yngwin -[21:04:18] PSYCHO___: stop talking and start working -[21:04:19] roll call -[21:04:22] present -[21:04:22] :D -[21:04:24] I'm here -[21:04:27] HERE -[21:04:46] only qt people -[21:04:52] spatz: it is required only to say it once -[21:04:53] mostly present -[21:04:58] while(1) printf("HERE\n"); :D -[21:05:03] PSYCHO___: here :D -[21:05:04] okay ==> [ ] -[21:05:34] some get kde 3.5 killer... errr.... ssuominen here as well! :P -[21:05:43] ok thats not exactly attendance i expected -[21:06:10] scarabeus: lets wait at least 5 more minutes -[21:06:42] im also worried that some people might show up in an hour or so... -[21:06:46] ok -[21:06:59] because of DST? -[21:07:04] *** Joins: Sput (n=sputnick@quassel/developer/sput) -[21:07:04] yeah -[21:07:15] happened last time -[21:07:23] they can use date -u -[21:07:29] so thats not exactly excuse -[21:07:45] no'ones trying to excuse them -[21:07:47] dst stinks -[21:07:47] :P -[21:07:56] * spatz uses date -u -[21:09:17] so? -[21:09:28] so -[21:09:28] agenda? -[21:09:30] time's up, lets go! -[21:09:42] yngwin: agenda is on -desktop-ml in that mails -[21:09:43] scarb has first item @ /topic -[21:10:00] i will put them onto the topic as we will be going -[21:10:03] thats scattered -[21:10:22] * wired fixes agenda -[21:12:07] ok -[21:12:09] agenda: http://dpaste.com/122485/ -[21:12:30] thanks -[21:12:32] read it while i clean it up a bit -[21:13:00] what about starting from Qt since KDE has a lot to talk about? -[21:13:52] Ingmar: btw are you around? -[21:14:14] updated agenda: http://dpaste.com/122486/ -[21:14:36] ok lets roll -[21:14:51] 21.15 already -[21:14:58] true -[21:15:03] PSYCHO___: are you presiding? -[21:16:02] ok so lets start -[21:16:06] i was smashing my net a bit -[21:16:48] internet has swine flu -[21:17:26] yeah looks so -[21:17:29] * wired whistles -[21:17:36] !herd kde -[21:17:37] PSYCHO___: (kde) abcd, alexxy, carlo, cryos, dagger, deathwing00, jmbsvicetto, keytoaster, lxnay, mrpouet, patrick, scarabeus, spatz, sping, ssuominen, tampakrap, tgurr, wired -[21:17:38] aarfff dinner time :( -[21:17:42] so listen up -[21:18:08] anyone of you did read that mail from Ingmar? or you just idled like usual? -[21:18:21] yes we did -[21:18:22] * spatz read it -[21:18:25] * wired did read it -[21:18:27] i did -[21:18:36] http://article.gmane.org/gmane.comp.kde.scm-interest/724 -[21:18:46] there is my response to that mail thread -[21:19:06] give us a min to read -[21:19:08] it is how i imagine layout that would suit us packagesr best -[21:20:29] *** Joins: j0 (n=quassel@g227216073.adsl.alicedsl.de) -[21:20:29] anyway the question that waits here: "Is anyone willing to work on this?" -[21:21:15] yes -[21:21:26] did you get any response from upstream? -[21:21:33] nope, this mail is last in that thread -[21:22:16] so we are waiting until upstream responds to that first, or not? -[21:22:39] actualy nope, i expect someone coordinate with ingmar and prepare full proposal to them -[21:22:55] because my 6 lines about layout are not exactly "full proposal" -[21:23:00] upstream surely knew we have split kde -[21:23:11] yes they do -[21:23:12] the real question is, do they really want to take this route? -[21:23:40] well some stated that they would like it, some otherwise -[21:23:48] i've also seen discussions about splitting in the past going nowhere (two at least) but never mind -[21:24:10] well this time they are migrating to another SCM so it might have better chance to win :] -[21:24:18] agreed -[21:24:42] does Ingmar (ping) have anything else to say in this topic? (apart from what you said in the mail?) -[21:25:19] well he is aparently not around, so the interested person will have to mail him or irc him at some better time -[21:25:30] do binary distros (pretty much everybody) have split packages or monolithic ones? -[21:25:46] debian has them split -[21:25:52] after compilation tho -[21:25:56] hello -[21:26:05] they compile them in monolithic way and ship them in split way -[21:26:08] hey Ingmar -[21:26:09] scarabeus, tampakrap hi -[21:26:18] hello -[21:26:54] doesn't matter how they do it, only whether they do it. if this change forces everybody to split their packages whereas now they have monolithic ones we might face some opposition -[21:26:56] scarabeus: as you said, i'd like to see upstream move to a buildsystem layout more similar to what xorg has -[21:27:19] scarabeus: i'm less interested in splitting out the libs, or base, but the debian packager i talked to found that more important than anything else -[21:27:34] spatz: other distros follow upstream's way, so they will be forced to change it -[21:27:36] presumably because they can easily split the rest after buil -[21:27:39] d -[21:27:45] s/can/can & already do/ -[21:28:21] well from what we can say the initiative to do the thing will have to cover 2 areas) explaining what to do and how ) showing some example repo done that way -[21:29:04] yeah -[21:30:04] so ANY volunteers for this? -[21:30:09] yes -[21:30:21] and you? -[21:30:29] Ingmar: also i would like to see at least one relevant upstream guy acking that we are not just wasting our time -[21:30:30] I am, obviously :) -[21:31:01] well, let's start with a proof of concept for one module -[21:31:04] i myself will try to help -[21:31:48] i'd put together a proof of cencept first & see what they say on the relevant mailinglists -[21:32:01] ok that sounds reasonable -[21:32:12] splitting kdenetwork or kdeedu might be quite easy -[21:32:24] Ingmar: did you get any affirmative responses from other packagers (and more importantly) by any upstream developer? -[21:32:51] scarabeus: i was thinking kdenetworok, so yeah :) -[21:33:09] tampakrap: packagers yes (debian & gentoo, didn't ask anyone else), didn't ask any specific upstream devs -[21:33:20] ok -[21:33:33] Ingmar: also we should steal some irc channel to have it covered, i guess we cant chit-chat on g-kde or e-kde since its bit offtopic :] -[21:33:36] on the kde-scm-interest ml, some were in favor, and some where against -[21:34:16] any name ideas? :] -[21:34:39] #kde-split -[21:34:41] /j #kde-build-split :) -[21:34:48] ok -[21:35:01] *** Parts: wohnout (n=wohnout@88.86.113.238) -[21:35:23] anything else on the subject? -[21:35:36] i would say that for meeting we covered it -[21:35:46] i personaly will try to motivate few more people -[21:35:52] but that is non-meeting subject :] -[21:36:03] Ingmar: apart from kde-scn-interest ml, any other mailing lists you'd like to see us subscribed? -[21:36:55] kde-buildsystem -[21:37:08] well, if you have more minions, you know where to send them :) -[21:37:20] okz -[21:37:41] ok i think we're done with this for now -[21:37:48] next topic plz? -[21:37:54] first topic plz :) -[21:37:55] tampakrap: now something qt i would say -[21:38:00] since there is more qters -[21:38:09] scarabeus: lets just do the agenda?! -[21:38:27] as you wish -[21:38:33] ok documentation -[21:38:41] *** scarabeus changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 1: Documentation' -[21:38:43] stabilization first -[21:38:44] *** scarabeus changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 2: Documentation' -[21:38:54] http://dpaste.com/122486/ -[21:38:56] *** scarabeus changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 1: stabilisation' -[21:39:35] ok so since only samuli is working on it with me has anyone looked on the bug -[21:39:43] or attempted to fix blocker bugs -[21:40:04] bug # plz? -[21:40:15] * wired hasn't looked at kde 4.3.3 bugs lately, but will -[21:40:25] bgu 292455 -[21:40:26] bug 292455 -[21:40:28] spatz: https://bugs.gentoo.org/292455 "KDE 4.3.3 stabilization request"; Gentoo Linux, Applications; NEW; ssuominen@g.o:kde@g.o -[21:40:41] bug 2: Documentation -[21:40:43] erm -[21:40:43] PSYCHO___: https://bugs.gentoo.org/2 "How do I attach an ebuild."; Gentoo Linux, Ebuilds; RESO, FIXE; tneidt@fidnet.com:hallski@g.o -[21:40:45] damn this -[21:40:49] as spatz said -[21:40:51] lolz -[21:41:02] lol -[21:41:28] so 13 bugs -[21:41:47] i can try to help this weekend -[21:41:50] i want each member of kde team to fix at least 1 -[21:42:28] 12 bugs, 3 stable req and 1 keyword req -[21:42:29] also i want someone to look on current open bugs -[21:42:40] and decide which should be blocking the stabling -[21:42:50] and on this i want volunteer that will actualy do it -[21:43:05] and also close the remaining kde3 bugz -[21:43:13] we can't really do much with keyword/stable requests -[21:43:43] are still there are normal bugs, and not all bugs are now blocking the stabilisation even if they should -[21:43:47] so who will do it -[21:45:13] ok i'll do it since noone is interested -[21:45:19] meaning the bug wrangling -[21:46:11] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 2: documentation' -[21:46:12] ok -[21:46:19] next topic -[21:46:41] as i stated -[21:46:54] I want devoted person focusing on updating our documentation with nedy -[21:47:02] as wired I can try to help this week end (I've an exam tomorrow and I've to finish a project) -[21:47:04] yes but i disagree with that -[21:47:45] tampakrap: so how would you do the documetnation -[21:47:53] everyone of us should just realize that documentation is *VERY* important and write two words before a major update or whatever -[21:48:01] apart from that i have another idea that you may like -[21:48:31] *** Joins: ssuominen (n=ssuomine@gentoo/developer/ssuominen) -[21:48:38] speak up :] -[21:48:43] since guidexml requires gorg in order to have a fully rendered (human readable) doc -[21:49:15] i have created an svn repo in my home server that checks out through a hook to a gorg-accessible path -[21:49:22] so it can be read immediatelly -[21:49:48] i can give access to the team here to my home server so we can *ALL* (and i mean ALL, even HTs) develop the guide -[21:49:56] no excuses about permissions etc -[21:50:13] unless you can provide us such a hook, since you have access in overlays.g.o -[21:50:14] well that was done even on git server remember -[21:50:16] I agree, so +1 -[21:50:27] i wrote complete guide in overlay as non-dev -[21:50:59] yes but i'm talking about an immediate co to an xml gentoo.org-like site -[21:51:17] which makes things easier -[21:51:25] this once again shows the shortcomings of guidexml -[21:51:42] well ok -[21:51:48] tampakrap: you then write up something and enforce it -[21:52:01] well, i don't agree with that, it shows that noone cares about docs which is sad -[21:52:38] come on, i just stated something, we can proceed in voting i guess, or go in your way then -[21:53:20] well i am willing to use it, problem is that noone else will edit it, its the same problem as is now -[21:53:36] we can give it a shot -[21:53:37] we can keep those guides in our public_html folders to see it right-away -[21:53:39] until next meeting -[21:53:42] but noone edit it anyway -[21:53:50] that's not the same -[21:53:56] but we should *also* have someone in charge -[21:54:18] well i wanted someone in charge -[21:54:22] so he can say -[21:54:26] that someone would check other commits and will _in_time_ get closer to the docs team -[21:54:30] sorry I'm late; I forgot about the time change :( -[21:54:31] i could be in charge of docs since i am the main editor a while now, but i don't like this idea -[21:54:36] You XY wrote module for AB but did not document it, so do it now. -[21:55:12] so actualy devs introducing something new will be somehow forced to do the docs -[21:55:38] because "anyone does docs and we are happy" simply is NOT working -[21:55:43] the problem is that we don't update the docs BEFORE the change (minor or major) -[21:56:31] well that would be responsibility of doc master, to point when and what needs to be changed -[21:56:35] and that won't change by itself, even if we could write the docs in speech-to-text app -[21:57:22] i dont expect the lead to do the work, but delegate to other devs, and if those wont document, i am even willing to remove them from team -[21:57:31] okay i could do that but i'd expect from the members to respect more the documentation part -[21:58:31] okay if noone has a problem with that then i'll take charge of this position -[21:58:40] *** Quits: ayoy (n=ayoy@gentoo/developer/ayoy) (Remote closed the connection) -[21:58:52] tampakrap++ -[21:58:53] *** Joins: ayoy (n=ayoy@cs78245237.pp.htv.fi) -[21:58:53] ok -[21:59:06] i'll also introduce my system to gentoo-desktop mailing list (i hope devs+HT's are subscribed there) -[21:59:09] PSYCHO___: huh ? remove them from team ? for that ? (I agree document is an important thing does not matter) ... but blame them instead -[21:59:23] while we're on the docs subject, note that I'm taking care of Qt docs -[21:59:27] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 3: upstream coordination' -[21:59:32] mrpouet: it is even more important that coding -[21:59:42] just recall what hapened when we masked kdeprefix -[21:59:46] I meant it's a bit....excessive -[21:59:51] mrpouet: its seriously important for users -[21:59:56] mrpouet: and we present our work to users -[22:00:00] tampakrap: I said that I was agree :] -[22:00:02] mrpouet: we need to be 100% covered there -[22:00:22] (document is important) but the consequence is.... excessive imho -[22:00:41] mrpouet: now noone cared, so i will be really evil until they start to care -[22:00:52] well -[22:00:55] i must say -[22:01:04] docs have always been one huge strength of gentoo -[22:01:08] *** Joins: Pesa (n=Pesa@bluemchen.kde.org) -[22:01:13] and lately they're degrading fast -[22:01:15] PSYCHO___: sadistic :P -[22:01:17] so I like this initiative -[22:01:29] lets bring them back :) -[22:01:42] hello :) -[22:01:49] ok so lets loko onto the next toppic -[22:01:51] second late to the party -[22:01:57] :D -[22:02:01] as i can see some people had really the problem with TZ -[22:02:02] :D -[22:02:05] Pesa: hi :) -[22:02:12] Pesa: or you know that you are 1h late? :P -[22:02:17] uhm... -[22:02:20] 1h :O -[22:02:25] he does not -[22:02:27] date -u -[22:02:29] Pesa: ^^ -[22:02:32] damn! timezone :s -[22:02:43] Pesa: I had the same issue :D -[22:02:43] sorry -[22:02:50] ok so lets get to the topic :] -[22:02:56] you'll read logs, lets go! -[22:03:09] who is willing to track upstream patches, and apply them where required -[22:03:10] yep -[22:03:30] wired: or do like me, have a linux clock setting up to UTC :D -[22:03:43] this requires also requesting backports from TRUNK to branch on upstream -[22:04:50] PSYCHO___: you meant a unique guy ? other devs can't import patches from upstream ? -[22:05:03] (it's ambigous) -[22:05:11] they can, but should coordinate with him -[22:05:14] (at least for me with my fuc*$*$$* english) -[22:05:16] it can be even more people -[22:05:29] the point is that we would have the patches applied where needed -[22:05:34] in both overlay/tree -[22:05:57] PSYCHO___: mhhh... personally I could be interested -[22:06:01] Hello -[22:06:05] boss! -[22:06:06] sorry for being late -[22:06:08] jmbsvicetto: hi -[22:06:09] :) -[22:06:09] currently we mostly wait on upstream to release new version -[22:06:11] welcome jmbsvicetto -[22:06:14] hello boss -[22:07:09] Hi everyone -[22:07:16] ok, come on guys, he is half gnome, at least one more volunteer ;] -[22:07:20] its not that hard job :] -[22:07:30] i could help but not that much -[22:07:36] because i am mostly trunk user -[22:08:00] PSYCHO___: what's up? -[22:08:08] :( -[22:08:10] PSYCHO___: it's not an argument :p -[22:08:16] jmbsvicetto: you want log so far? -[22:08:17] Am I 1 hour late?? :| -[22:08:18] i want someone to coordinate patches with upstream :] -[22:08:20] I'm half gnome... and ? :D -[22:08:21] someone dedicated :] -[22:08:22] jmbsvicetto: you are :P -[22:08:49] * jmbsvicetto failed to read UTC :\ -[22:09:05] wired: yes, please (logs) -[22:09:30] jmbsvicetto: ok i'll wgetpaste then hold on -[22:09:49] PSYCHO___: reavertm and ABCD would be perfect for this i guess -[22:09:49] ABCD: how about you? dont want to do this? :] -[22:10:02] tampakrap: exactly my thinking, but reaver is not around now -[22:10:47] the silence after i ask someone something :D hilarious -[22:11:12] PSYCHO___: that would mean I'd actually have to figure out if commits to trunk are relevant/apply on the 4.3 branch... -[22:11:22] (which means more work :( ) -[22:11:26] btw, after this topic, I've another one (tiny) -[22:12:00] trunk after .70 is 90% incompatible with current branch -[22:12:19] (I'm pretty sure you will agree, but I wanted to talk about that during meeting anyway) -[22:12:28] jmbsvicetto: http://dpaste.com/122503/ -[22:12:30] ABCD: i mean more watch what bugs they fix, and ask them to patch it for branch too -[22:13:02] something like "i know you fixed crash X for trunk, but the error is in branch too, so could you fix it too so others dont have to wait for 4 months?" -[22:13:05] wired: thanks -[22:13:28] and second responsibility would be just applying what users add to bugzilla as patches from upstream -[22:13:39] deciding if it is worth or not and so on -[22:13:45] PSYCHO___: so long as someone files a Gentoo bug, and mentions the upstream bug; otherwise I'd never find it :) -[22:13:48] i dont expect that person to review all commits -[22:13:59] ABCD: thats the idea :] -[22:14:09] i dont expect you to browse the upstream one ;] -[22:14:20] in that case, it shouldn't be too difficult -[22:14:58] i know, i just want someone to do it -[22:15:07] so i wont meet 20 days open bug with patch from upstream -[22:15:29] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic 4: kde3 removal' -[22:15:39] ssuominen: around? -[22:15:50] ok as you might noticed kde3 is going away -[22:15:56] next topic, ssuominen is in progress of it :P -[22:15:57] its quite flawless i can say -[22:16:04] * tampakrap points at #-commits -[22:16:09] http://dev.gentoo.org/~scarabeus/kde3almostgone.png -[22:16:09] wave your hands while you still can -[22:16:19] its going awayyyyyyyyyyyy -[22:16:19] this is what it did to our bugs -[22:16:27] so i want to hear one thing only here -[22:16:34] is something more required on that matter from us? -[22:17:17] nothing i can think of -[22:17:26] me neither -[22:17:30] ssuominen is really doing a great job with this -[22:17:31] thats why i wanted ask others -[22:17:40] bye-bye bugs :D -[22:17:57] wontfix closing is fast :P but dont get used to it :D -[22:18:10] :D -[22:18:20] lets go to RDEPENDs -[22:18:22] * tampakrap is waiting for kde5 - kde4-removal -[22:18:41] tampakrap: go ahead and write kde5 then! -[22:18:42] jmbsvicetto: boss its your area -[22:18:52] jmbsvicetto: so elaborate why rdepend use deps are bad -[22:19:30] *** Joins: pontecorvo (n=pontecor@93-183-229-187-dynamic.retail.datagroup.ua) -[22:19:36] okeey, anyone else? :] -[22:19:41] :P -[22:19:51] i personally like use flags for rdepends -[22:20:06] but i'd like to hear why they're bad from those who don't -[22:20:13] * PSYCHO___ dont care, einfo was always enough for me -[22:20:17] wired: well it is poluting the ebuild -[22:20:21] they are not entirely required -[22:20:27] its not pollution -[22:20:31] so einfo with install X for feature Y -[22:20:42] its only a few words and its helping you do things pre-emerge -[22:20:50] wired: if you stabilise package, it is polution, if you have to wait on optional rdepend to be stabilised -[22:21:07] in that case -[22:21:12] lets work on a per case basis -[22:21:41] for example, obvious or important rdepends could go in use flags, others in info -[22:21:46] that actualy might work -[22:22:33] if an rdepend disables/enables half the package's functionality, it should definately have a USE -[22:22:45] if its a hidden option in the 3rd menu from the right -[22:22:53] it could live without it :P -[22:22:56] *** Quits: pontecorvo (n=pontecor@93-183-229-187-dynamic.retail.datagroup.ua) (Remote closed the connection) -[22:23:35] but we *must* make sure we have einfo if we don't have USE -[22:23:36] make it policy -[22:23:41] thats sound sane -[22:24:05] agreed -[22:24:12] add to CODE maybe? -[22:24:15] yeah -[22:24:27] oh sorry -[22:24:30] *** Joins: pontecorvo (n=pontecor@93-183-229-187-dynamic.retail.datagroup.ua) -[22:24:30] yeah, *docs* man -[22:24:40] ok someone can grab it from summary later then -[22:24:41] :D -[22:24:41] :] -[22:24:41] sorry, reading backlog -[22:24:51] i would kick you now, but we are in meeting -[22:25:04] jmbsvicetto: not entirely smart thing to do during continuous meeting :D -[22:25:16] PSYCHO___: It isn't that rdepend use flags are bad, it's just that there are too many -[22:25:34] at least it used to be too many -> quanta was the best/worst(?) example -[22:25:53] yes, because we are following upstream -[22:26:24] jmbsvicetto: well thats why it is per decision basics -[22:26:33] svn plugin can be controled by svn useflag -[22:26:34] wired / PSYCHO___: I'm not sure they cause so many issues when marking it stable -[22:26:46] we can always have a use flag masked in a profile -[22:26:50] jmbsvicetto: I DO, i try to stable such package right now -[22:27:05] :P -[22:27:09] PSYCHO___: I was trying to catch something ;) -[22:27:16] i think what i said above is good as a rule of thumb -[22:27:43] devs should decide per case depending on the importance of the deps -[22:27:47] so we don't end up with 30 RDEPEND USE flags -[22:27:48] :p -[22:27:54] I don't have a problem with a case-by-case, but then we'll get a bug for each package that we don't provide a use flag :P -[22:28:18] wontfix, because that's how we want it -[22:28:34] or fix, because we did a second thought -[22:28:38] * jmbsvicetto puts user cloak: I want use flag X for installing package Z when I install package Y!!! -[22:28:46] http://www.pastebin.cz/26457 -[22:29:06] jmbsvicetto: we already have wontfix bugs like that -[22:29:08] Ingmar: I'll try to poke you later, but I'm also interested in upstream's work on splitting KDE -[22:29:11] its up to us, not user decision -[22:29:16] yes, I know -[22:30:28] ok, i guess we covered our last point -[22:30:34] so lets move to qt issues :] -[22:30:37] w8 -[22:30:39] wait plz -[22:30:49] mrpouet has sth to add -[22:31:04] hm? -[22:31:11] or had :P -[22:31:15] mrpouet: u here? -[22:31:21] i have to say something too -[22:31:36] tampakrap: then speak :] -[22:31:38] go ahead -[22:31:42] i'll start since mrpouet is somewhere else :P -[22:32:13] recently i fixed a bunch of live ebuilds, reported issues, patches etc -[22:33:07] since i recompile kde and qt live packages very frequently, i would like your permission to create a doc which will track live ebuilds' upstream and downstream bugs, etc -[22:33:15] which are broken and need love etc -[22:33:43] if you think that a doc is not appropriate i could do a page in gentoo-wiki for example -[22:34:11] tampakrap: go ahead, try to motivate some non-team people to help you -[22:34:18] tampakrap: so you can recruit your minions ;P -[22:34:30] on that note, we could create a script -[22:34:31] no way, you are the ht lead -[22:34:34] that picks up your daily rebuild -[22:34:44] and generates a webpage of what failed and what worked -[22:34:45] :p -[22:34:52] you mean something like dirk-dashboard? -[22:34:52] ;] -[22:34:57] contonuous integration -[22:34:57] or something like bump-tool? -[22:35:07] http://dev.gentoo.org/~scarabeus/vystup.html -[22:35:08] something like buildbot? -[22:35:27] a script that takes logs and uploads them somewhere -[22:35:29] something like that PSYCHO___ -[22:35:45] like the thing gnomies have -[22:35:49] tampakrap: well do it if you want it -[22:35:55] i can create a custom script if we don't have something ready -[22:36:03] we don't -[22:36:05] ok ok -[22:36:09] covered -[22:36:11] just give me the logs :P -[22:36:28] ok so lets moove to the qt since mrpouet is not around -[22:36:36] wait a minute -[22:36:47] it seems not covered -[22:37:06] wired: the script would be usuable if it could automatically take the build.logs from the failed packages -[22:37:11] and upload them somewhere -[22:37:33] tampakrap: its not entirely meeting material, and we have meeting already for 1h30minutes... just discuss this with wired on -kde afterwards :] -[22:37:33] yeah -[22:37:37] and we can add a comment next to each one of them, like upstream bug or whatever -[22:37:39] we'll talk about it off list -[22:37:43] off meeting* -[22:37:43] ok ok -[22:37:51] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic QT 1: qt mono package' -[22:37:58] !herd qt -[22:38:00] (qt) abcd, ayoy, carlo, hwoarang, spatz, tampakrap, wired, yngwin -[22:38:14] surprisingly i am here -[22:38:21] one of our biggest issues -[22:38:26] with the split ebuilds -[22:38:29] the USE flag madness -[22:38:31] is now solved -[22:38:38] because anything < 4.5.3 is off the tree -[22:38:41] \ö/ -[22:38:41] lol, when? -[22:38:54] i still see people struggling with it -[22:39:03] because they are updating to 4.5.3, not? -[22:39:11] yes -[22:39:12] yay -[22:39:19] once they update, we're done with this shit -[22:39:29] so its solved from our side -[22:39:50] the only thing left is the Qt update blocker madness -[22:40:01] but i think people are beginning to understand that b blocks are autosolvable -[22:40:05] but we'll still have to support latecomers for a long time -[22:40:28] we'll have to support latecomers no matter what -[22:40:39] yngwin: agreed, but that doesn't really change anything if we merge splits into a monolithic -[22:40:45] s/anything// -[22:41:05] it would, but anyway -[22:41:28] i mean, they'd still have to do some migration work -[22:41:38] like update with no blockers -[22:41:40] :) -[22:42:06] yes, but that would be clearer than the current mess with blockers and useflags - portage is just not giving very clear feedback to users -[22:42:20] i agree with the feedback thing -[22:42:45] but with the useflags issue _mostly_ gone, do you feel the blockers are good enough a reason to change things? -[22:42:52] well, we could say that that's a portage bug ;) -[22:43:09] it is mostly a portage problem yes -[22:43:16] xorg packages, for example, don't have blockers for maximum versions, only minimal, so users see less blockers -[22:43:18] well portage should shut up about autosolved blocks -[22:43:20] but we'll have to work with portage -[22:43:29] i dont understand why it writes them out -[22:43:36] qt has both maximum and minimum version blockers and that's creating weird issues -[22:43:39] most users get only confused -[22:43:43] imo the right way to do this is fix portage -[22:43:58] i really want to get into portage development but i just can't these days -[22:44:01] *** Joins: tampakrap_ (n=tampakra@ppp-94-66-145-248.home.otenet.gr) -[22:44:01] why do we need maximum version blockers? -[22:44:04] i am considering doing so in the future -[22:44:16] downgrading Qt isn't really supported anyway -[22:44:31] Sput: you can't mix Qt versions -[22:44:35] Sput: to make sure user has exactly the same version of all packages -[22:44:35] Sput: mixing versions anyhow is neither -[22:44:36] period :P -[22:44:46] wired: i'd like to too ;) -[22:44:51] yes, but the common case is upgrade, yes? -[22:45:01] again, see xorg use case -[22:45:01] to my mind this shows why we need monolithic -[22:45:06] something like MDEPEND -[22:45:07] downgrading doesn't usually work either -[22:45:08] so minimum blockers would be enough to force all qt packages be updated if one is updated -[22:45:12] if package is around then require this version -[22:45:16] otherwise do not care -[22:45:18] so called -[22:45:22] MAGIC DEPENDENCY -[22:45:29] :) -[22:45:38] with only minimum blocks users won't get blockers -[22:45:49] come on its exactly what you want, that might be actualy easy to do with current code -[22:45:55] it will just need new eapi :/ -[22:46:24] PSYCHO___: current code can't do it, i've tried to express it with complex bash but it still shells out blockers -[22:46:27] we need new depend type -[22:46:30] anyway, we said we'd discuss it on ML, which as far as i can see has not happened -[22:46:43] it did not -[22:46:44] wired: i said so, new depend type MDEPEND -[22:46:49] PSYCHO___++ -[22:46:57] who wants to start the ML discussion? -[22:46:58] and it is easy to adjust -[22:47:00] the portage code -[22:47:04] about this -[22:47:13] yngwin: I can -[22:47:19] great -[22:47:22] next topic -[22:47:35] status of qt-tng -[22:47:42] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic QT 2: Status of new qt-tng.eclass' -[22:47:56] I've been reviewing it for last 1,5 hours -[22:47:59] hwoarang said he couldnt continue with this because of circumstances -[22:48:10] i think it's ready -[22:48:12] yes so are we happy with it enough to post it in -dev? -[22:48:26] provided that we remove prepare_translations? -[22:48:45] this one seems not so handy -[22:48:52] tries to address a common case -[22:48:58] let's prepare the eclass for qt@ before sending it off to -dev -[22:48:59] but the common case doesn't really exist -[22:49:06] except there isn't a common case :) -[22:49:14] so lets remove that -[22:49:21] I will -[22:49:23] yes, we already said that -[22:49:38] ok -[22:49:47] ok, ayoy, can you finalize the eclass and send it to qt@ ? -[22:49:47] hey, btw -[22:49:48] *** Quits: tampakrap (n=tuxicity@gentoo/developer/tampakrap) (Read error: 54 (Connection reset by peer)) -[22:49:56] yngwin: yes I can -[22:50:15] great -[22:50:18] then we can all have a look and comment if needed, then send it to -dev -[22:50:21] are we all happy with the eclass name? -[22:50:26] * ayoy is not -[22:50:29] not really -[22:50:36] ayoy: i talked with picard the other day, he said he liked it -[22:50:36] you already voted on it, but didnt decide anything -[22:50:39] i am not but i don't really care -[22:50:41] qt4-edge kicks testicals very hard, I like it -[22:50:51] not -edge -[22:50:54] we need that for overlay -[22:51:03] qt4v2 -[22:51:03] else we'll have to start overriding and crap -[22:51:11] wired: you mean that qt4-edge will stay in overlay? -[22:51:17] we need eclass versioning dammit -[22:51:26] yngwin++ -[22:51:31] ayoy: yes, we need to keep developing there, don't we? :P -[22:51:37] we do -[22:51:43] yngwin: indeed -[22:51:44] indeed, wired is right -[22:51:53] I propose qt4-next :/ -[22:51:58] qt42morow -[22:51:58] better :) -[22:52:03] qt4-v2 -[22:52:08] read it ^ -[22:52:10] qt4evar -[22:52:11] in english -[22:52:16] PSYCHO___: we did :P -[22:52:33] :] -[22:52:41] qt4-blesmrt -[22:52:42] :] -[22:52:43] qt4-r2 -[22:52:45] ok, let's not waste time on bikesheds -[22:52:50] ^^ in the gentoo spirit -[22:52:54] lol -[22:52:56] :) -[22:53:09] i like that, wired -[22:53:10] this meeting is already taking 2 hours :/ -[22:53:16] let's move on -[22:53:17] * spatz likes it too -[22:53:23] :D -[22:53:25] * ayoy too -[22:53:25] so name unchanged -[22:53:27] ? -[22:53:28] ok, qt4-r2.eclass -[22:53:30] no, changed -[22:53:41] next topic -[22:53:46] w00t, we got rid of startrek -[22:53:47] ok 3. -[22:53:50] #gentoo-qt -[22:53:52] do we want it? -[22:53:58] plz no -[22:54:01] no -[22:54:02] i dont see the need -[22:54:02] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic QT 3: #gentoo-qt' -[22:54:05] I'd say we rather need a separate meeting -[22:54:09] than a separate channel -[22:54:11] its already registered and when i was bored I added permissions -[22:54:18] so if you ever feel like it -[22:54:18] :) -[22:54:24] ok, but plz no -[22:54:26] :) -[22:54:47] i think -kde is fine as well, but its there if we need it -[22:54:50] ok, so we all agree on 'no' -[22:54:57] neeeext -[22:55:01] let's keep it -[22:55:01] ok, we have a backup for a nuclear war or sth -[22:55:06] *** PSYCHO___ changes topic to 'KDE Team meeting 19.11. 19:00 UTC: Topic QT 4: einfo mess' -[22:55:12] 4. -[22:55:13] but we'll continue to use -kde for the time being -[22:55:18] it was already cleared out yesterday -[22:55:23] by wired -[22:55:23] btw DONT RUSH -[22:55:32] :D -[22:55:37] the messages only show for qt-core now -[22:55:37] qt-core only -[22:55:37] ? -[22:55:38] so I think it's better -[22:55:41] awesome -[22:55:41] tommy[d] complaint many times about this warning overload -[22:55:48] tampakrap_: i already fixed it -[22:55:51] confined it to qt-core -[22:55:54] yes, change was committed yesterday -[22:55:56] ok, I love it -[22:56:02] cool -[22:56:05] we can (and should) shorten the text, but it's much less spam now -[22:56:10] yeah -[22:56:10] if any more cutting is needed, let us know -[22:56:15] like 11 times less -[22:56:18] lol -[22:56:19] :) -[22:56:21] great, so next -[22:56:24] 5. -[22:56:25] gitorious -[22:56:30] wait -[22:56:32] we could look at the text again -[22:56:38] see if it can be shortened -[22:56:40] only downside is no commit bot coolness -[22:57:02] yngwin: i can do it -[22:57:09] i also like the suggestion to put it in out docs and refer in einfo to our docs page -[22:57:34] wired: ok, do it and let us know what you come up with -[22:57:34] thats not bad either -[22:57:38] k -[22:57:41] will mail qt@ -[22:57:47] i'll do the docs btw -[22:57:48] oooh I like that -[22:57:53] alright -[22:57:53] ok then -[22:57:55] no one thought otherwise :) -[22:57:57] why not github? -[22:58:04] next topic -[22:58:11] tampakrap_: i'll do the Qt docs -[22:58:13] many ppl don't have github accounts but want overlay access -[22:58:17] keep it split so we actually do something -[22:58:24] they can create -[22:58:25] or die -[22:58:37] and gitorious is the new black, or something -[22:58:45] oh -[22:58:48] * ayoy checks -[22:58:53] i like gitorious because you an have more people administer the repo -[22:59:03] can* -[22:59:06] it's better in most ways, except cia.vc integration -[22:59:12] I like the bot we have in #-kde -[22:59:13] the only real disadvantage is cia -[22:59:17] do we care enough? -[22:59:17] i am now the bus factor for github -[22:59:18] yngwin: good point -[22:59:38] no -[22:59:40] i mean kde doesn't have cia either, big deal -[22:59:41] I do only a bit -[22:59:58] not really, cia bot is nice, but there are other ways -[23:00:04] i like the cia wow factor as well, but if gitorious is better/more reliable/more popular -[23:00:09] like capslock -[23:00:11] my commit number got too high because of qting-edge, i almost lost my gentoo/slacker cloak -[23:00:13] lets go there and switch the hooks to keep github in sync -[23:00:25] hey hey -[23:00:26] btw -[23:00:26] ! -[23:00:36] if we switch to gitorious -[23:00:41] we still have github as a backup, no? -[23:00:47] we still have the bot -[23:00:50] period. -[23:00:54] right -[23:00:56] touche -[23:00:58] ayoy++ -[23:00:58] heh right -[23:01:00] new ppl who only have gitorious access won't be able to push to github -[23:01:02] lol -[23:01:02] :) -[23:01:10] spatz: no issues, we'll push for them -[23:01:10] so not really -[23:01:13] so vote for it -[23:01:22] yes, vote -[23:01:27] as in topic it is named as voting for gitorious as main repo -[23:01:28] gitorious -[23:01:30] +1 gitorious -[23:01:40] ok then, +1 gitorious -[23:01:46] gitorious -[23:01:46] gitorious + github as backup -[23:01:54] * spatz switches url order in .git/config -[23:02:17] ABCD? -[23:02:29] abstain -[23:02:33] ok -[23:02:37] btw can we do the same trick with kde-testing to get cia bot there as well? -[23:02:53] lol -[23:03:00] only if people actually push to gitorious as well -[23:03:06] better poke PSYCHO___ to fix it -[23:03:07] :p -[23:03:08] you mean github -[23:03:12] yeah -[23:03:13] :D -[23:03:22] if git.o.g.o has cia integration you don't have to -[23:03:23] ok last topic -[23:03:25] s/gitorious/github/ -[23:03:26] so we need to make an announcement about that, to push to gitorious as main repo, and change layman url -[23:04:05] any volunteers? -[23:04:12] announcement in like -dev? qt2? -[23:04:13] qt@? -[23:04:21] qt@ -[23:04:27] i'll do it -[23:04:30] no big deal :) -[23:05:08] im Qt PR -[23:05:09] :p -[23:05:09] last topic: removal of changelogs from overlay -[23:05:15] that one was mine -[23:05:17] also proj page -[23:05:39] lets remove them, they keep breaking my nerves, git logs are enough! -[23:05:48] NO -[23:05:48] wired++ -[23:05:58] seriously -[23:06:02] why not? -[23:06:05] i can't stand them, overlays shouldnt have changelogs -[23:06:10] duplicate info -[23:06:15] qting-edge is also a training area for new recruits / devs-to-be -[23:06:35] yngwin: most overlays are -[23:06:37] it's good practice to get used to using echangelog -[23:06:43] yngwin++ -[23:06:44] yngwin: repoman will scream anyway -[23:06:53] repoman wont scream -[23:06:57] it doesn't -[23:06:58] I think that's the least of the recruit's problems -[23:07:01] yes, that is why my policy is to use echangelog in all overlays -[23:07:02] spatz++ -[23:07:07] it doesn't scream, it warns -[23:07:10] *** Quits: nirbheek (n=nirbheek@gentoo/developer/nirbheek) ("Gone.") -[23:07:10] repoman ignores changelogs for distributed scms -[23:07:14] spatz: ^ -[23:07:17] PSYCHO___: i meant in cvs -[23:07:20] recruits should be taught to read repoman's warnings :) -[23:07:22] spatz: i wrote the code to portage, so i know about its behaviour -[23:07:32] I mean when they commit to the tree -[23:07:36] as long as portage is using cvs and echangelog, i want us to use it in the overlay -[23:07:47] i really don't like it, i forget it because this is the only overlay we use changelogs -[23:07:47] from the ones i use -[23:07:51] echangelog that is, not cs :p -[23:07:55] cvs* -[23:07:59] lol -[23:08:15] can we vote or do you veto? -[23:08:19] for the record i agree with wired -[23:08:21] :D -[23:08:27] i'd like a vote for this -[23:08:28] :) -[23:08:40] also, for users who checkout the overlay, they may expect changelogs -[23:08:45] i would, anyway -[23:08:56] no overlay has changelogs, so why would they? -[23:08:57] *** Quits: krakonos (n=krakonos@kangaroo.kolej.mff.cuni.cz) (Client Quit) -[23:09:07] I'm for changelogs in the overlay -[23:09:09] yngwin: well users are educated to git log or visit gitweb these days, thanks to kde-testing :P -[23:09:14] because portage does -[23:09:47] besides, git log is blazingly fast, its not like you have to cvs log :p -[23:10:02] echangelog in git is also fast -[23:10:06] ;] -[23:10:07] most users dont know how to handle git -[23:10:20] plz vote and end, i want to go to shower -[23:10:23] ayoy: sure, but when you don't echangelog in most overlays -[23:10:24] they can use the gitorious web-ui -[23:10:27] you tend to forget -[23:10:37] wired: then add echangelogs to other overlays -[23:10:39] PSYCHO___: s/vote/veto/ -[23:10:42] :) -[23:10:56] meh -[23:11:02] yngwin: me dont care you are no longer subproject and you are lead, so it is up to you -[23:11:17] yngwin: 2 months ago i could veto your veto but now it is entirely up to you :D -[23:11:22] lol -[23:11:24] lol :D -[23:11:35] i want better arguments than "I'm too lazy" -[23:11:36] yngwin: we hate you -[23:11:44] yngwin: its not im lazy -[23:11:48] tampakrap_: i'm honoured -[23:11:53] it's that i am lazy -[23:11:54] yngwin: fucked up 3way merge strategy -[23:11:58] its dup info, no real advantages :) -[23:12:03] anyway -[23:12:12] we dropped it because it breaks merges a lot -[23:12:17] it was invented to overcome VCS shortcomings we no longer have -[23:12:27] who merges anything in qting-edge? -[23:12:29] we still have in portage -[23:12:34] I've seen it once maybe -[23:12:39] yngwin: portage is cvs, we need it there -[23:12:45] yes, better spend the echangelog time to help portage to move to git i'd say :P -[23:12:45] because it still has to deal with those shortcomings - we don't -[23:13:09] when the tree moves to git the changelogs would probably be thrown out the window -[23:13:11] wired: yes, and i want the overlay to be similar -[23:13:25] then we will remove them as well -[23:13:27] ofc.... -[23:13:29] * PSYCHO___ throws the orange duck from one hand to another and looks on the clock -[23:13:32] still, cvs commit progress is *very* different from git commit process -[23:13:38] PSYCHO___: it's yellow! -[23:13:46] not this one -[23:13:49] yngwin: if recruits can't handle that difference between qting-edge and cvs, then they shouldn't be devs, really :P -[23:13:51] it's Czech duck -[23:14:10] hmm, there is something to that -[23:14:13] so it has weird dots and lines all over and above it? -[23:14:58] ok i have to go, don't care that much about this subject :P -[23:15:01] ok, let's give yngwin time to think about this and wrap this party up -[23:15:09] yngwin: http://dev.gentoo.org/~scarabeus/0911-meeting_summary.txt fix the FIXME parts, me blobs to shower -[23:15:10] yes, ok -[23:15:10] alright -[23:15:15] yngwin: its up to you, next meeting -[23:15:17] let's continue this topic on ML! :D -[23:15:19] yay! -[23:15:31] wait! -[23:15:35] you all FREEZE! -[23:15:40] wut? -[23:15:45] i'll think about it, and we can discuss it again later, ok? -[23:15:48] lets discuss our project page a bit -[23:15:50] yngwin: OK -[23:15:50] don't forget do update your qting-edge/.git/config to new pushurls :D -[23:15:52] * PSYCHO___ does the squeek sound with his duck -[23:16:05] spatz: send a mail to qt@ about it -[23:16:07] can somebody shut up that PSYCHO? -[23:16:10] lol -[23:16:14] he said freeze -[23:16:29] if you need to go, you can go -[23:16:44] i wrote up a first version, but I'd like feedback from all of you -[23:16:49] stuff that should be there -[23:16:51] stuff that should go -[23:17:06] we can continue discussing this after the meeting, we don't need to hold everybody up -[23:17:11] i do want to ask qt devs if thet would prefer a separate meeting, as these combined meetings take long -[23:17:19] ++ -[23:17:19] no -[23:17:22] YES -[23:17:34] if -[23:17:38] we keep it to 2-3 hours combined -[23:17:40] im fine -[23:17:44] issues concern both teams usually -[23:17:45] a pity is that half of the team will have just 2 meetings -[23:17:47] kde and qt one -[23:18:06] tampakrap++ -[23:18:28] i'll write a mail to kde@ and qt@ and we can discuss it then -[23:18:38] or just desktop -[23:18:40] if we started at 18 UTC or started with Qt stuff I'd be fine -[23:18:42] btw, okay to import my patch in phonon ? :] -[23:18:43] desktop mailing list -[23:18:54] mrpouet: good morning! -[23:19:11] i'm not sure everyone is on desktop ml -[23:19:11] *** Quits: ayoy (n=ayoy@gentoo/developer/ayoy) (Remote closed the connection) -[23:19:19] should be -[23:19:19] wired: did you smoke something ? -[23:19:24] *** Joins: ayoy (n=ayoy@cs78245237.pp.htv.fi) -[23:19:30] mrpouet: lol no i don't smoke ;) -[23:19:45] :p -[23:19:48] have to go bye -[23:19:50] :/ -[23:19:52] bai -[23:19:57] bye tampakrap_ -[23:20:00] cya -[23:20:04] *** Quits: tampakrap_ (n=tampakra@gentoo/developer/tampakrap) (Remote closed the connection) -[23:20:07] wired: what your sentence has to do with my question ? :D -[23:20:07] we're wrapping up anyway -[23:20:31] wired: good job on the project page, I'm sure there will be improvements/additions over time -[23:20:33] mrpouet: i asked you to talk about your issue a while back but you didn't respond :P -[23:20:57] * mrpouet has a girl-friend :( -[23:21:01] yngwin: indeed. thanks -[23:21:11] a girl friend is boring you know.. :D -[23:21:17] mrpouet: so do I, but now its sacred... errr meeting time! -[23:21:28] lol -[23:21:43] wired: aaarfff I know !! :( -[23:22:28] i think we can wrap this up now -[23:22:28] :p -[23:22:38] ok, last call -[23:22:40] mrpouet: tell em about your patch -[23:22:45] before they all leave -[23:22:45] :p -[23:22:51] * mrpouet setups a sighandler for SIGGIRL-FRIEND -[23:23:02] ... -[23:23:09] ohhh better -[23:23:15] ignore signal :D -[23:23:23] ==> [ ] -[23:23:25] ^^ -[23:23:27] mrpouet: you have 2 minutes -[23:23:58] 30s gone -[23:24:07] okay so, I wrote a patch in order to add a support for external subtitles (files) -[23:24:07] lalala -[23:24:39] it works just fine, sandsmark approved it (on upstream) -[23:24:56] it would be nice then to patch kaffeine&dragon -[23:25:10] but before we need to import my patch in phonon -[23:25:24] see https://bugs.kde.org/show_bug.cgi?id=213710 -[23:25:31] m-s/phonon or qt-phonon or both? -[23:25:33] for technical details -[23:25:40] yngwin: m-s/phonon -[23:25:46] ok -[23:26:35] currently we can : auto-detect patch (recursively in the media directory), load a patch manually, setting up the subtitle encoding -[23:26:47] rrraaahhh !!!! fucking shit !!! -[23:26:57] auto-detect subs * -[23:27:03] lol -[23:27:06] s/patch/subs -[23:27:08] o_O -[23:27:15] * mrpouet stabs himself -[23:27:39] you're putting quite a show -[23:27:47] :D -[23:27:50] :D -[23:27:51] looks to me the patch has merit, but i'm not kde herd, and i think PSYCHO___ has left -[23:28:02] the patch work -[23:28:02] s -[23:28:08] pretty well -[23:28:12] :) -[23:28:12] * wired tested it -[23:28:30] so i suggest you open a bug and poke kde team -[23:29:34] there is already a bug :) -[23:29:36] ok, meeting closed -[23:29:38] ------------------------------------- -- cgit v1.2.3-65-gdbad