Portage oddity...

Brains · n00b Joined: 23 May 2003 Posts: 3

Portage has gone a bit odd on me. So far there have been no obvious functionality problems but each time I run an emerge sync and -up world, portage insists that it alternately upgrade/downgrade libxml2. It has also started to show foomatic as an entry in the update list (with an N) even though I unmerged it and qpkg doesn't show anything depending on it.

Anybody want to suggest diagnostic/maint utils or procedures? I've already tried most of the ones I've run across, such as revdep-rebuild and regenworld...

Brains

mabouya · n00b Joined: 15 May 2003 Posts: 39 Location: Matinik

Maybe you should check your useflags... that's the first thing comming to my mind

Brains · n00b Joined: 23 May 2003 Posts: 3

Anything in particular? This is my current USE...
USE="-arts -kde -gnome aalib alsa cdr dga directfb doc dvd fbcon gd ggi jikes maildir odbc pda perl samba slp snmp tiff wmf"

tj · Posted: Sat May 24, 2003 7:13 am Post subject:

if you're syncing from the oregonstate mirror then see this post

change your mirror in /etc/make.conf as described

delete the /usr/portage/distfiles as described

try your emerge from the new mirror - my local one is faster than oregonstate

[/url]

Brains · n00b Joined: 23 May 2003 Posts: 3

Doesn't seem to be an OSU problem since I've been having it for some time before they started having problems... And I'm already using mirrorselect to pick mirrors.

Nuwen · Tux's lil' helper Joined: 20 Mar 2003 Posts: 123

This doesn't sound like a USE or CFLAGS issue to me. As for the first part, does it only try to upgrade/downgrade after a sync? If so, it sounds like your rsync mirror is doing something odd, try changing that.

As for the second, the only thing I can think of is that it's a dependancy added by an updated version of some package, and qpkg isn't picking it up. Try emerge -pu for any packages that show up after foomatic in the update list. If that fails, maybe try emerge regen or downgrading portage or something.