Many thanks, Toby.
Reading between the lines of the howto you referred to, I think, if I am not
mistaken, that the problem was that the monolithic-to-individual-package
migration path built into 3.4.0 was removed from 3.4.1. Somehow this left
the kde-3.4.0 ebuild hanging around as a kind of gh
On Sat, Jul 09, 2005 at 02:41:11PM -0700, Robert Persson wrote:
> A couple of weeks ago I added all the kde-3.4.1 packages to package.keywords
> and then ran emerge -u world and everything updated and ran fine.
>
> Today I tried to emerge -u world and I got
>
> [blocks B ] =kde-base/kdeartwo
A couple of weeks ago I added all the kde-3.4.1 packages to package.keywords
and then ran emerge -u world and everything updated and ran fine.
Today I tried to emerge -u world and I got
[blocks B ] =kde-base/kdeartwork-icewm-themes-3.4* (is blocking
kde-base/kdeartwork-3.4.1)
... blah blah
3 matches
Mail list logo
