[gentoo-amd64] Re: Updates other than the masked one

[Duncan]

Martin Herrman posted on Sun, 27 Dec 2009 08:45:50 +0100 as excerpted:

> All,
>
> since about a week or so, the kdebase-runtime-meta package is masked,
> see below. I'm quite sure that in the mean time other packages have been
> updated as well. How can I install these other updates to prevent that
> eventually I have to update a bunch of packages that takes me several
> hours to compile? (of course, without allowing the masked package to be
> installed..)
>
> Thanx,
>
> Martin
>
> ==========================
>
> martindesktop ~ # emerge --update --deep --newuse --pretend world
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
>
> !!! All ebuilds that could satisfy
> ">=kde-base/kdebase-runtime-meta-4.3.4[-kdeprefix,semantic-
desktop,handbook]"
> have been masked.
> !!! One of the following masked packages is required to complete your
> request: - kde-base/kdebase-runtime-meta-4.3.4-r1 (masked by: ~amd64
> keyword)
>
> For more information, see the MASKED PACKAGES section in the emerge man
> page or refer to the Gentoo Handbook. (dependency required by
> "kde-base/kdelibs-4.3.4" [ebuild]) (dependency required by "world"
> [argument])
>
> martindesktop ~ #

Are you running standard amd64 keyword, or ~amd64?  It appears from that, 
that you'd be running amd64 (stable), because it's ~amd64 masked.

So which version of kde (or kdelibs if you only have a few kde packages, 
not most/all of the software collection) is installed?  According to the 
changelog, kde-base/kdebase-runtime-meta was only introduced for kde 
4.3.4, the package didn't exist earlier.  But kde 4.3.4 is ~amd64 
masked.  So why is a package that never existed for previous versions now 
in your world file, or a dependency of something that is, if you're not 
yet running the ~amd64 kde 4.3.4?

If you're running stable amd64 normally, but have whatever parts of kde 
4.3.4 you have installed in your package.keywords file, then you now need 
to add kde-base/kdebase-runtime-meta to it as well, as it's now required 
by kdelibs 4.3.4 (because upstream requires it, see gentoo bug #295456).

Bottom line, if you have (amd64 stable) kdelibs-4.3.3 installed, kdebase-
runtime-meta shouldn't be being pulled in, unless you're trying to 
upgrade whatever kde parts you have to 4.3.4.  If you have 
package.keyworded parts of kde 4.3.4 and have it installed, they you need 
to package.keyword kdebase-runtime-meta (and all the packages it pulls 
in), because it's now a dependency.  Either that, or downgrade back to 
4.3.3 and remove the 4.3.4 package.keyword entries you already have, if 
you aren't prepared to keyword runtime-meta and its dependencies as well.

---

Alternatively, and directly answering your question, tho it won't be 
supported and may not work so well, to get a list of @world upgrades, you 
can (temporarily) add kdebase-runtime-meta (and its dependencies) to your 
package.keywords, then do an emerge --pretend --update, and get a list.  
You can then update (emerge --oneshot package, so it doesn't put extra 
entries in your world file) the ones you want from that list, 
individually.  When you are done updating what you want, you can remove 
the temporary package.keywords, so they're masked again.

But rather than that, I'd seriously recommend either downgrading to 4.3.3 
if you want to stick with stable, or keywording the rest of your kde 
4.3.4 dependencies so all of kde is ~arch and sticking with 4.3.4.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman