Bugzilla Bug 115516

if kpackage is merged in world (keeping the version 3.4.3 masked), emerge -uD
world will emerge kdelibs-3.4.1 (and unmerge kdelibs-3.4.3).
The next emerge -uD will re-emerge kdelibs-3.4.3, next one kdelibs-3.4.1, and so
on...

The solution is trivial: unmask kde-base/kpackage-3.4.3

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Guys, you really have to make sure that you mark _all_ relevant kde-base
packages stable at once. This is worse than a minor app not functioning properly
(as ksaysit didn't).

Carlo, I fail to see how this is our fault, it's not a dependency of any of the
kde-meta packages and you didn't list it as an app that needed to be marked
stable in your previous bug.  In fact, from the kdeadmin-meta package:

# NOTE: kpackage, ksysv are useless on a normal gentoo system and so aren't included
# in the above list. However, packages do nominally exist for them.

Should we also mark ksysv stable as well?  Are there any other kde packages that
need to be marked that you didn't tell us about?

"Adding arches to CC to mark KDE 3.4.3 stable.   
   
Notes:   
the release includes   
- kde-base/kde and its dependencies   
- kde-base/kde-meta and its dependencies   
- kde-base/kdesdk, kde-base/kdesdk-meta and deps   
- kde-base/kdebindings-meta and deps   
- kde-base/kde-i18n   
if possible, they should be marked stable at the same time. "  
  
from kdeadmin-meta-3.4.3.ebuild  
# NOTE: kpackage, ksysv are useless on a normal gentoo system and so aren't  
included  
# in the above list. However, packages do nominally exist for them.  
  
in fact, I don't even know why ksysv isn't masked, it's made for redhat style  
rc# setups and about the only thing it can do is start/stop services. Anyways, 
kpackage marked as it can at least recognize gentoo package installs. 

(In reply to comment #2)
> Carlo, I fail to see how this is our fault

Sorry Joe, it was mine. There is no kpackage version marked stable on ppc, so
the problem is x86 only in this case.


Chris, the wording was indeed not the best, but this bug should show you, that
it is a problem. All packages where a previous version went stable, need to go
stable as well.

Should we be marking ksysv, or can we just make it go away?  Also, does anyone
on the KDE team have a list of all packages that should be going stable so we
can avoid anything like this in the future.  Thanks.

I personally don't see any point in keeping the ksysv package, and would be
tempted to remove it. What do others think? Is there any possible reason to
keep ksysv around on a Gentoo system? Unless someone fancies patching it up for
our init layout that is :)

A complete list of split packages and which monolithic packages they come from
can be found in kde-functions.eclass too. May be this information should be
included with future stable requests to help arch maintainers. kpackage seems
to have a minimal featureset and should probably be dropped too if it is of no
use.

Looks like everything the x86 team needs to do is done then :)

Has been fixed.