Mark Haney wrote:
> Well, I'm ready and willing to upgrade to KDE 4.2 but I've got an issue.
> I still have KDE 3.5.9 on my system. I probably can kill it, but I'm
> curious as to a solution to my problem.
>
> When I checked on upgrading to 4.2 this is what I got:
>
> [blocks B ] <=kde-base/kdebase-startkde-3.5.10
> ("<=kde-base/kdebase-startkde-3.5.10" is blocking
> kde-base/kdelibs-4.2.0)
> [blocks B ] <=kde-base/kdebase-startkde-3.5.10-r3
> ("<=kde-base/kdebase-startkde-3.5.10-r3" is blocking
> kde-base/kdelibs-3.5.10-r2)
>
> So, I tried to install kde-base/kdebase-startkde-3.5.10-r3 and I got this:
>
> emerge -av =kde-base/kdebase-startkde-3.5.10-r3
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
>
> emerge: there are no ebuilds to satisfy
> "=kde-base/kdebase-startkde-3.5.10-r3".
>
> I don't understand how come I can't seem to find that ebuild?
>
>
I've got an -r5 in my tree, but no -r3. Revisions are quickly excised
when new revisions come out.
When doing something like this, you shouldn't specify exact versions.
For example, try
emerge -av "<kde-base/kdebase-startkde-4"
to simply get the highest kde3 version that's not masked somehow.
Sebastian
