Feb 01

1. Roll call

johu, hwoarang, pesa, tampakrap, wired

2. Qt 4.8

* cairo fails to build, patched ebuild available in qting-edge, #380013

Cairo build issue is fixed in qting-edge overlay, will be moved together with Qt 4.8.0 to tree.

* qt now defaults to the raster graphicssystem, we should remove raster USE flag, #398283

Wired created a eselect module to choose the Qt graphicsystem. Raster is default, other selectable are opengl, openvg and native. Raster use flag is not needed anymore, qt-gui depends on the new eselect module.

* do we really want to keep qpa USE flag?

qpa and c++0x will be masked in tree.

* are we going to fix #363939 for 4.8?

Wired fixed this bug in qt 4.8.0. Qt 4.8 will be moved to tree on next weekend. Dilfridge prepares kde-base/kstyles-4.7.4 to be rebuild together with Qt 4.8.0 to prevent crashes in KDE apps with Oxygen style.

3. Minor arches and Qt >= 4.7

Upstream supports official amd64, arm and x86, but other arches also considered in configure script. Keep stable keywords for minor arches in Qt 4.6. Wait for minor arches arm, ppc, ppc64 in current stabilization in Qt 4.7.4. Drop sparc keywords in Qt 4.8.0.

4. Overlay migration to git.overlays.gentoo.org

Tampakrap will set up overlay on git.overlays.gentoo.org on next weekend. The new overlay will be renamed to qt instead of qting-edge.

5. Open bugs

* #398885 qdoc3 broken on arm

We will ask the reporter if it works when he builds manually by providing him a configure command to make sure he tries the proper build.

* #394533 Libreoffice crashes in qt on exit

Can’t be reproduced with Libreoffice 3.5.0.1, seems to be resolved by upstream.

* #392433 desktop file name issues

Will be fixed in Qt 4.8.0, so that qt-gui and qt-assistant no longer pass absolute paths to make_desktop_entry().

* #388551 qt-gui[gtkstyle] should depend on gnome-base/libgnomeui-2

We will add a elog message in qt-gui[gtkstyle] saying that for things to work you either need libgnomeui or that variable set properly in your env.

* #382559 qt_mkspecs_dir() returns bad spec directory

The bug will be marked as RESOLVED WORKSFORME, because we can’t reproduce it. Additionally we change the eclass not to use LIBDIR in favor of get_libdir() after Qt 4.8 hits the portage tree.

* #359391 qt4-build.eclass should check for —buildpkgonly before downgrade sanity check

Resolution will be RESOLVED WONTFIX. Sanity check is there for a reason. It’s not a matter of source or binary downgrade.

Jan 21

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 got 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 :)
Meeting Log can be found here
I'm going to FOSDEM, the Free and Open Source Software Developers' European Meeting
Jun 03

1) KDE SC 4.6.80 aka 4.7 beta 1 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

dilfridge 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!

Apr 01

The KDE meeting had the usual monthly meeting yesterday. After a long discussion we decided to switch to add Trinity ebuilds finally in tree. There has been a lot of time we were working on those ebuilds, we consider them mature enough now for end users. Since we lack the manpower to provide support for two DE’s, we will have to move KDE 4 ebuilds in a user-maintained overlay, called kde4-sunset. A Gentoo KDE 4 team may suffice of course, but until that happens, we are obliged by our QA team’s policy to remove any non-maintained / obsolete ebuilds away from our users, especially for security reasons. The following actions will take place in the following days:

  • Add Trinity ebuilds in tree
  • Create a portage news announcement and front page announcement, making their removal official and 
  • Mask KDE 4 ebuilds for removal in 30 days
  • Create the kde4-sunset overlay
  • Move KDE 4 ebuilds in that overlay
  • Call again for help (blog posts, forums etc)
The Trinity project is a very promising project, since it is built on top of KDE 3, the only working KDE version. We wish the KDE 4 developers all the best on their effort, and we hope that other distros will follow our steps.
Feb 25

Since random people poke us in IRC about the same questions, I decided to redistribute the last meeting’s summary in my blog.

0) Elect new lead

Wheee I am the new Leader! I am the head, the boss, the godfather, the lord of the rings, the bourne identity (joke stolen from The IT Crowd). I can’t see how that affects anything though, in my opinion team leaders are useless positions, the council is enough.

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 gentoo-dev mailing list?

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 (Here is the topic).

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. (As a side note, we always welcome new members, either for HT or for full developer status, feel free to contact me).

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 (there is a draft in my devspace, based on this forum post), 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. Also, some of our gnomies may be there, which is a perfect opportunity for some in-person trolling.

Gentoo KDE team meeting Summary and Log

Sep 03

Part of today’s KDE Team meeting:

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:

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.

The whole summary and log can be found at the KDE project space.

The Qt Team also had a meeting one our later, summary and logs at the Qt project space

=-=-=-=-=
Powered by Blogilo

Mar 05

In the last KDE and Qt meetings, there have been many and important changes, so I decided to blog about them to keep users up-to-date. The summaries and logs are available in each project’s site (http://kde.gentoo.org and http://qt.gentoo.org). Both projects have regular meetings, every third Thursday of the month (unless announced otherwise), and very often they have a common one. The channel that hosts us is #gentoo-meetings in Freenode, and everyone is welcome to join us. I will mention only the most remarkable issues that were discussed/decided, which seem to be a lot:

Qt meeting, 19 February 2010

This was delayed one day, so I missed it. I really hate it when I miss Gentoo meetings, as every time they are very fun and challenging, and I like very much interacting with so many Gentoo developers and contributors at the same time. Before proceeding, I’d like to point out that the Qt Project was very recently founded as a separate project, because the Qt Team (sub-herd of the KDE Project) has grown too much and had too many non-KDE issues. The Qt members are doing an awesome work. And here are some of the important issues:

  1. We now have an "unofficial" channel in IRC, and a new shiny Qt Subdomain! So from now on you can find us in #gentoo-qt on Freenode, and our documentation resides in http://qt.gentoo.org (thanks to Robin (robbat2) for setting that up). Of course we will still be available in #gentoo-kde or #gentoo-desktop.
  2. Raster USE flag is going to be on by default. Μάρκος (hwoarang) already blogged about this asking for testing.
  3. Qt 3 has been masked for removal from the tree, along with all Qt 3 packages and the qt3 USE flag. The only blocker for this task was MythTV, which now has a stable Qt 4 replacement in Gentoo. Also, Ben (yngwin) informed the kde-sunset maintainers about this, but so far I didn’t see anyone committing those apps there, so if you want to do it (or do general qt3 and kde3 work), consult this document. (Reminder: kde-sunset is user-maintained overlay, anyone interested can ask for access there, so if you are still interested in Qt 3 and/or KDE 3 packages, please ask for commit access instead of complaining to the Gentoo developers).

KDE meeting, 25 February 2010

This was delayed one week, which was a request by me, so it won’t be during my exams. There hasn’t been a KDE meeting in January, so there were plenty of topics to discuss. I was also the moderator of this one, which made it double fun. In most of the issues there has been some progress, so let’s begin:

  1. We now have a new leader, Tomáš Chvátal aka scarabeus. After a year of Jorge Manuel B.S. Vicetto’s (jmbsvicetto) absolutely perfect leadership, we had the annual elections, were scarabeus was voted by pretty much everyone. He is admittedly very skilled and very active in Gentoo community in general, as a member of QA, X11 and KDE Teams and also a recent council member. I’d also like to give props to my former "boss" Jorge, especially for taking over that old nasty mysql/amarok issue and creating the libmysqld.so patch.
  2. KDE SC 4.3.5 is stable in tree now, and the newly released KDE SC 4.4.1 is available in tree as testing. There have been many problems with 4.4.0 (mostly crashes), so it won’t be a stable candidate for sure. We’ll see how 4.4.1 goes and accordingly decide if this is going to be a stable candidate, or wait for 4.4.2.
  3. Amarok and MySQL 5.1 suffer from the same old libmysqld.so issue. Thus, we strongly recommend to remove the embedded USE flag from both Amarok and MySQL. In fact, it is not anymore enabled by default in the ebuilds. As a side note about MySQL, Akonadi seems to break in some machines with >MySQL-5.1.42. The problem is known to upstream developers, and there have been some workarounds in KDE forum, but I didn’t have time to test any of them yet.
  4. KDEPIM in trunk KDE is currently broken (really just kmail). This is because kmail’s mail storage is being ported to akonadi, so IMAP (I don’t know about the other protocols for sure) doesn’t work at all at the moment. Sput (Quassel developer) proposed to use the enterprise KDEPIM branch, which is supposed to work, as it is being paid by companies. I sent an email asking for help in gentoo-desktop mailing list, with no answers so far. Please see the thread archive (available here) for more info. I would also like to inform you that the KDE Team decided not to provide the usual trunk snapshots until version 4.4.70 (which is going to be the first alphas), because of this KDEPIM issue.
  5. KOffice 2.1.1 is released a month ago, but it is not available to users yet. Actually, it is in tree hardmasked, as it needs a close depedency checking in ebuilds. I was held responsible for this, and I hope till the weekend it will be done, if I get enough help from scarabeus which was the former KOffice ebuilds maintainer, or by anyone else from the KDE Team (there are plenty of people in the Team, I’m sure I’ll find someone to help me). By the way, this is my only KDE todo thing left.
  6. KNetworkManager is now in tree, but also hardmasked. This was in upstream’s kdereview branch, which contains packages that stay there for review by the developers for wider testing, before they move to their final KDE module or extragear branch (take a look at KDE’s SVN repo to get the picture). It was supposed to be released along with KDE 4.4, but it didn’t make it. So, I created a snapshot of the current SVN repository, which seems to have many problems, like crashes, missing features etc. So I guess it will remain hardmasked for a while, and I will continue to update the snapshot once every two weeks.
  7. The KDE Documentation is also one of my playgrounds. I recently updated the guide, and with a quick look I did the following: closed all three bugs regarding the KDE Installation Guide, added more items in Hints and Troubleshooting section, completely removed the kdeprefix reference, replaced the snapshots installation guide with a note that we won’t provide them for now, and done a bunch of small fixes (mostly version corrections and typos).
  8. I raised the issue of kde-meta (and accordingly @kde-* sets) not including all KDE modules. It currently excludes the developer-specific modules like KDESDK and KDEbindings (although it does contain KDEWebDev), and proposed either to include them all in kde-meta or to introduce a developer or sdk USE flag in kde-meta. Some developers were opposed on this, proposing to have a new meta package, like kdefull-meta, an idea which I actually hated. Our final word on this was to open a new discussion thread in gentoo-desktop mailing list, which I did, and review the issue in the next meeting.
  9. Finally, I’d like the attention of everybody here, as the following issue is very very important. In a previous meeting we discussed the split of the desktop profile in gnome/ and kde/ subprofiles. We raised the idea in gentoo-dev mailing list for review, and we had a positive feedback in general. Other DE’s refused to have a special subprofile, so they will stick to the basic desktop profile. What this means is that the desktop profile from now on will not contain GNOME or KDE-specific USE flags, which are transfered to the according subprofile. For users that want both DE’s (or just both DE-specific USE flags) can enable them manually in their make.conf (they are not many after all). The major advantage from the user-side of view is that many unwanted dependencies get stripped off automatically, and from the developer-side of view is that from now on we’ll have a more separate approach when packaging. The patches are ready and sent for review in gentoo-dev mailing list. Currently the result can be seen in the kde-crazy overlay, and here you can see the relevant thread. A news item will also be made before committing, and I hope that the final move will happen next week. I’d like to thank Maciej (reavertm), Ben (yngwin) and Samuli (ssuominen) for their precious help on this. (P.S. This is one of the very few moments that I felt I did some Gentoo development instead of KDE packaging, if you know what I mean :) )

Qt Team meeting Log and Summary
KDE Team meeting Log and Summary

=-=-=-=-=
Powered by Blogilo