Just like the title says.
When it got to the part at the end where it says its updating the portage cache, it seems to get anywhere from 80-95% done then i get:
!!! Cannot resolve a virtual package name to an ebuild.
!!! This is a bug, please report it. (virtual/libintl-0)
What the heck do I do now? Now I get that same result whenever I try to use emerge. Help in a non-destructive-to-my-current-configuration kind of way would be much appreciated.
emerge sync killed portage
Message
Remove everything but those two directories in /usr/portage?
Then do what? After that emerge -u portage says:
!!! ARCH is not set... Are you missing the /etc/make.profile symlink?
!!! Is the symlink correct? Is your portage tree complete?
So anyway, tried emerge --sync again and it seems to have gone ok, after it finished it said:
*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.
The next command emerge -u portage failed again with the same error as before.
Then do what? After that emerge -u portage says:
!!! ARCH is not set... Are you missing the /etc/make.profile symlink?
!!! Is the symlink correct? Is your portage tree complete?
So anyway, tried emerge --sync again and it seems to have gone ok, after it finished it said:
*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.
The next command emerge -u portage failed again with the same error as before.
Ah... I should have said to leave /usr/portage/profiles.
It might be easier to run:
This will install portage 2.0.54 without going through emerge.
It might be easier to run:
Code: Select all
ebuild /usr/portage/sys-apps/portage/portage-2.0.54.ebuild mergeWell, I didn't actually delete any of that stuff, just moved it to a backup folder in my home directory so no big deal.
Interestingly enough, this whole fiasco is the end result of me almost NEVER running emerge to update anything. So yeah, the next time I ran emerge -u portage it worked and now I'm ready to start into a habit of updating more regularly to avoid doing this again.
One question left though, I cannot update the hardware abstraction layer without first updating the kernel, mine is 2.6.11, how would I go about running emerge -u world and tell it to skip sys-apps/hal?
Interestingly enough, this whole fiasco is the end result of me almost NEVER running emerge to update anything. So yeah, the next time I ran emerge -u portage it worked and now I'm ready to start into a habit of updating more regularly to avoid doing this again.
One question left though, I cannot update the hardware abstraction layer without first updating the kernel, mine is 2.6.11, how would I go about running emerge -u world and tell it to skip sys-apps/hal?
Ah, good.
Yeah, this happens now and again - the Portage devs make changes to the tree which break older, deprecated versions of portage. It's unavoidable, really; if you want to be able to use portage with a current tree you have to update portage occasionally.
To skip hal, you could temporarily mask it: echo ">=sys-apps/hal-0.5" >> /etc/portage/package.mask.
Yeah, this happens now and again - the Portage devs make changes to the tree which break older, deprecated versions of portage. It's unavoidable, really; if you want to be able to use portage with a current tree you have to update portage occasionally.
To skip hal, you could temporarily mask it: echo ">=sys-apps/hal-0.5" >> /etc/portage/package.mask.