Bugzilla Bug 287697

Package lists to follow

@non devs
Please refrain from *any* discussion here.
Visit bug 277868 if you have any relevant comments regarding stabilization.

Created an attachment (id=206184) [details]
KDE4 packages for stabilization (atom format, can be used as p.keywords)

Notes:

Following USE flags should me masked:
kde-base/plasma-workspace: 'google-gadgets' (does not build/install, not
worthy)
kde-base/{kdeutils-meta,kdeadmin-meta}: 'cups' (printing stuff:
kde-base/{printer-applet,system-config-printer-kde} not entering stable tree
yet)

I think this is it, please proceed.

(with dependencies first that is)

Created an attachment (id=206263) [details]
kdm-4.3.1-r1 -> kdm-4.3.2-r2

Some packages are missing:
networkmanager >= 0.7
>=x11-misc/google-gadgets-0.10.5
=kde-base/printer-applet-4.3.1 and its dependencies
=dev-libs/log4cxx-0.10.0
app-accessibility/epos
=sci-libs/indilib-0.6

As noted in #3, google-gadgets are out completely for this release.

Please mask google-gadgets USE flag for plasma-workspace-4.3.1 -
x11-misc/google-gadgets should be probably masked anyway

kde-base/printer-applet and kde-base/system-config-printer-kde are not meant 
for stabilization (they both work but I'm planning to introduce them when they
support policykit) - should get them removed from metapackages that pull them
for 'cups' USE flag or you could just mask 'cups' USE flag for
<=kde-base/kdeadmin-meta-4.4.0 and <=kde-base/kdeutils-meta-4.4.0 ?

You're right with the rest (epos, indilib, networkmanager) however - I'll file
stabilization bugs for them. Logc4xx is disputable and 'log' USE flag should be
probably masked for app-misc/strigi (all versions) - I used to have some issues
with this library in the past (massive memory leaks).

I think it's safe to start even now with stabilization of: phonon, soprano
qimageblitz, policykit-qt, strigi, akonadi-server as KDE4 is pretty much the
only consumer of those for now in tree (so won't break anything - phonon would
be the only package being used, but it's known to work with already stable
consumers like x11-libs/qt-webkit)

Thanks

For nm please see:
http://bugs.gentoo.org/show_bug.cgi?id=283633

Created an attachment (id=206338) [details]
Silly me, of course kdm-4.3.1-r1 -> kdm-4.3.1-r2

file was right, description was typo, resubmitted to avoid confusion

In case there's any doubt here, as the KDE team Lead, I would like to request
your help to get KDE-4 finally into the stable tree.

As a note, one that I was meant to sent through email a few weeks ago, we plan
to mask and later remove from the tree KDE-3.5 as it stopped being maintained
by upstream a *long* time ago, there's no Gentoo KDE developers concerned with
it and it's starting to have security issues.

We decided to drop networkmanager support for now (can be reintroduced anytime
later).

So, package.use.mask could consist (correcting my recent comment about cups):

# better to deal with this behemoth later
kde-base/plasma-workspace google-gadgets

# leaving system-config-printer-kde and printer-applet in testing
<=kde-base/kdeadmin-meta-4.3.10 cups
<=kde-base/kdeutils-meta-4.3.10 cups

# log4cxx known for memory leaks
app-misc/strigi log

# masked for users in tree (leaves it for overlay users for testing)
# and to give more time for networkmanager stabilization
<=kde-base/solid-4.3.10 networkmanager

Created an attachment (id=206591) [details]
dolphin-4.3.1->4.3.1-r1, kdelibs-4.3.1->4.3.1-r1, kabcclient-4.3.1->4.3.1-r1

amd64 stable

(In reply to comment #14)
> amd64 stable
> 

update: kdelibs-4.3.1-r2 instead of -r1.

I am suffering bug 261446 since kde4 got stabilized for amd64, it doesn't seem
to break anything (this is why I am not sure if should block this bug), but
it's a bit annoying to get this errors in every emerge involving mime database
update :-/

x86 stable, thanks to fauli for testing.
the following packages haven't been marked stable on x86, due to build
failures. please tell me if I have to open bugs for them.
kde-base/krossruby-4.3.1
kde-base/smoke-4.3.1
kde-base/kdebindings-csharp-4.3.1

Please add bug #286192 to the blocker list (bug #280670  has more details)