--- Mats Lidell <[EMAIL PROTECTED]> wrote:
> I wrote:
> > I have rebooted since the emerge so there must be
> something else.
>
> Following up on my own posting but after some
> investigation it seems
> like my emerge is confused. If I do "emerge -up
> world" there is nothing
> that needs to be updated but
>
> ---------------------------------------------
> # emerge -up gnome-common
>
> These are the packages that I would merge, in order:
>
> Calculating dependencies ...done!
> [ebuild U ] gnome-base/gnome-common-2.8.0
> [2.4.0]
> ---------------------------------------------
>
> So from my limited understanding of emerge I guess I
> have some work
> getting the portage tree in sync. (Maybe it is time
> for an "emerge
> --update --deep --newuse world" !? or what do you
> suggest? And how could
> this situation occur in the first place?)
>
> Yours
> --
> %% Mats
> --
Hi Mats,
It's working normally.
emerge -up world will only update packages that are
listed in /var/lib/portage/world. OTH, emerge -up
gnome-common behaves just like emerge -p gnome-common.
It is supposed to merge the latest (unmasked)
version.
I gather that gnome-common is not in your world file.
This is normal for packages that are pulled in as
dependencies.
Zac
__________________________________
Discover Yahoo!
Find restaurants, movies, travel and more fun for the weekend. Check it out!
http://discover.yahoo.com/weekend.html
--
[email protected] mailing list
