emerge --sync thinks there is a upgrade when there isnt?

[Yazmon]

Morning,

Im running emerge --sync as per normal, but its coming back with the message that there is a update to portage, but emerge -up world doesnt show it.

In additions I am getting the error 'cannot process /etc'.

Output below...

Code: Select all

wrote 153 bytes  read 898341 bytes  23337.51 bytes/sec
total size is 30936750  speedup is 34.43

>>> Updating Portage cache...  ...done!


 * An update to portage is available. It is _highly_ recommended
 * that you update portage now, before any other packages are updated.
 * Please do so and then update ALL of your configuration files.

[AC][root][/usr/bin][#> emerge -up portage

These are the packages that I would merge, in order:

Calculating dependencies ...done!

[AC][root][/usr/bin][#> emerge -s portage
Searching...
[ Results for search key : portage ]
[ Applications found : 3 ]

Snip....

*  sys-apps/portage
      Latest version available: 2.0.47-r8
      Latest version installed: 2.0.47-r8
      Size of downloaded files: 170 kB
      Homepage:    http://www.gentoo.org
      Description: Portage ports system

Any ideas? Do I need to upgrade manually?

[friction]

I got the same problem, but I didn't really think about it. But at least your not alone

[Yazmon]

Yeah its weird, apart from this and the 'unable to process /etc' message, its othwise working fine!

[MyZelF]

Hi, I'm new to gentoo and I have the same problem!

I tried to update manually portage:

Code: Select all

#emerge portage/sys-apps/portage/portage-2.0.47-r10.ebuild

and doing an

Code: Select all

#emerge sync

I obtain again:

Code: Select all

 * An update to portage is available. It is _highly_ recommended
 * that you update portage now, before any other packages are updated.
 * Please do so and then update ALL of your configuration files.

Then I do:

Code: Select all

# emerge -up system

These are the packages that I would merge, in order:

Calculating system dependencies ...done!
[ebuild    UD] sys-apps/portage-2.0.47-r8 [2.0.47-r10]
*** Portage will stop merging at this point and reload itself,
    recalculate dependancies, and complete the merge.

And the problem "cycles"...

I also noticed that some package that I think should be available (eg. xfree 4.3.0) are masked into portage tree.

Any sugestion?

[wolf@zh]

same problem here.....tried to delete /usr/portage and then rsync, but that didnt' help either...also, xfree4.3.0 is still masked...

[Fragbeestje]

I'm also experiencing this problem.

My emerge -up world, contains some ebuilds (xfree glibc and gcc) with the [UD] tag. So they would downgrade when I do an emerge -u world?

emerging -u almost any package starts reemerging xfree 4.2.1 and gcc 3.2.2
pretty annoying since this takes almost 3 hours.

gcc -v gives me 3.2.2

Is there something wrong with my portage or did I make a mistake upgrading to the newest Xfree and gcc by just emerging the ebuild?

[supenguin]

Same issue here. emerge -p portage gives the following results:

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild R ] sys-apps/portage-2.0.47-r8

[Scottaroo]

Me too! You're definately not alone.

I have 4 boxes running Gentoo and they ALL did this on the last sync (last evening), so I doubt that it's something specific to the boxes.

[The Jaff]

I can verify this behavior too. An 'emerge rsync/sync' says that there's an update to portage but then a 'emerge -u portage' does nothing.

Is there a Gentoo developer who can explain/fix this?

[einstein]

On IRC the answer I was getting to this question, was that it was a known bug, fixed in a currently masked ebuild. so either wait and the next time you sync it should actually be corrected..

here is the bug where this is being tracked..
http://bugs.gentoo.org/show_bug.cgi?id=17316

[Yazmon]

Doh, sorry my bad for not checking the bugs list....

[wolf@zh]

and what about xfree4.3.0? why is ist masked in my portagetree, but not in the online package database?

[MyZelF]

Maybe because some dependencies against xfree 4.3.0 are still marked as unstable (and not shown in online package database)???

[gK]

hey !

it seems the bug was corrected now !

I've emerge sync today an the famous message appears "it's _hihgly_ recommaded to..."...

I emerge portage and emerge downloaded the r10 version... I'm in stable.

sys-apps/portage
selected: 2.0.47-r8
protected: 2.0.47-r10
omitted: none

Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r2)

[pjp]

Portage version...