After my last update, portage stopped working. Google led me to
believe it was this bug:
http://bugs.gentoo.org/show_bug.cgi?id=317775
Which was said to be fixed in portage 2.1.9.
So I upgraded from 2.1.8.X to 2.1.9.1, and now portage is even more
broken. Now I can't even use it to
Hello,
whenever I run emerge it aborts with the following error message:
localhost # emerge --sync
Performing Global Updates: /usr/portage/profiles/updates/3Q-2006
(Could take a couple of minutes if you have a lot of binary packages.)
.='update pass' *='binary update' @='/var/db move'
Try this:
rm /usr/portage/metadata/timestamp.chk
emerge --sync
Frank Baumeister wrote:
Hello,
whenever I run emerge it aborts with the following error message:
localhost # emerge --sync
Performing Global Updates: /usr/portage/profiles/updates/3Q-2006
(Could take a couple of minutes if
On Thursday 14 September 2006 14:48, Daniel Iliev wrote:
Try this:
rm /usr/portage/metadata/timestamp.chk
emerge --sync
Unfortunately that didn't fix the problem.
Regards
Frank
--
gentoo-user@gentoo.org mailing list
On Thursday 14 September 2006 14:34, Frank Baumeister wrote:
whenever I run emerge it aborts with the following error message:
[SNIP]
pTraceback (most recent call last):
File /usr/bin/emerge, line 4049, in ?
emerge_main()
File /usr/bin/emerge, line 3770, in emerge_main
On 9/14/06, Frank Baumeister [EMAIL PROTECTED] wrote:
On Thursday 14 September 2006 14:48, Daniel Iliev wrote:
Try this:
rm /usr/portage/metadata/timestamp.chk
emerge --sync
Unfortunately that didn't fix the problem.
Regards
Frank
--
gentoo-user@gentoo.org mailing list
Hi Frank,
On Thursday 14 September 2006 18:17, Drew wrote:
Hi Frank,
Daniel's solution was one suggested in an earlier thread. The other
was to delete your portage tree and reinstall it via web-rsync
followed by a regular sync. The problem has been documented and the
patch is supposed to work it's
Just synced and tried to update world.
Portage updated itself, and then died when trying to exec itself.
I updated from 2.0.53 to 2.1_pre1. The error is:
!!! Failed to complete python imports. There are internal modules for
!!! python and failure here indicates that you have a problem with python
On Sat, Dec 17, 2005 at 09:44:19AM -0200, Bruno Lustosa wrote:
Just synced and tried to update world.
Portage updated itself, and then died when trying to exec itself.
I updated from 2.0.53 to 2.1_pre1. The error is:
!!! Failed to complete python imports. There are internal modules for
!!!
On Saturday 17 December 2005 11:52, Heiko Nock wrote:
On Sat, Dec 17, 2005 at 09:44:19AM -0200, Bruno Lustosa wrote:
Just synced and tried to update world.
Portage updated itself, and then died when trying to exec itself.
I updated from 2.0.53 to 2.1_pre1. The error is:
!!! Failed to
On Sat, Dec 17, 2005 at 01:00:59PM +, replica-solutions.de wrote:
Well, can't even run portage now to check things.
I filed bug 115841 on bugzilla. Is anyone here experiencing the same
thing?
Yes :(
I can't even back out the update, because every major portage command
relies on
Bruno Lustosa [EMAIL PROTECTED] writes:
Just synced and tried to update world.
Portage updated itself, and then died when trying to exec itself.
I updated from 2.0.53 to 2.1_pre1. The error is:
Luckily I did not get that error but emerge then took 'an eternity' to
calculate the world
On Sunday 18 December 2005 01:27, Graham Murray wrote:
Bruno Lustosa [EMAIL PROTECTED] writes:
Just synced and tried to update world.
Portage updated itself, and then died when trying to exec itself.
I updated from 2.0.53 to 2.1_pre1. The error is:
This error has been fixed. I was going to
Hi,
On (18/12/05 07:54), Martins Steinbergs wrote:
I was running update world and after portage was updated to 2.1_pre1 look
what
etc-update did to me. I dont have detailed build log, at least emerge.log
shows nothing suspicious. good there is portage-rescue. Should I file bug?
Yes,
14 matches
Mail list logo
