Emerge: doesn't user latest versions

[f.kater]

Hi,

I'd like to update my kde 3.0.0 to kde 3.0.1 but do not succed :-(
Ether the ebuild isn't found (although it IS there) or the latestest packages are not even concidered.
I've done the following things:

(1) emerge --search "kde"
The output shows 3.0.r3 as being the latest version - but I've already updated portage and 3.0.1 is present on my harddisk...

> * kde-base/kdebase
> Latest version Available: 3.0-r3
> Latest version Installed: 3.0
> Homepage:
> Description:
> ${DESCRIPTION}Base

(2)
If I try to force the update like this the ebuild isn't found and I get an error message:

> emerge --pretend kde-base/kdebase/kdebase-3.0.1.ebuild
>
> These are the packages that I would merge, in order.
>
> Calculating dependencies \
>
> !!! ebuild kde-base/kdebase-3.0.1 not found (possibly blocked by
> package.mask)


(3) I am not really familliar to "package.mask" but here is what I stripped out:

> # kde 3.0.1 - not available for fetching yet, but we lucky packagers
> have it
[...]
> >=kde-base/kde-3.0.1

What can I do?

Thank You for any help!
Felix (Berlin, Germany)

[huw]

wait...

If an ebuild is masked there's usually a good reason, like it doesn't work, or it breaks lots of other apps. It'll be released as soon as the developers are happy....

If you're desparate for life on the bleeding edge you can always d/l the latest KDE CVS code and start from there

[jay]

if you want to use a file that is masked, you have to unmask it, by adding a # before the package name. then you should be able to emerge these files.

If you do an emerge rsync the 3.01 files should be no longer masked
_________________
Do you want your posessions identified? [ynq] (n)