On 6/3/09, alain.didierj...@free.fr alain.didierj...@free.fr wrote:
After three days, emerge --sync still returns the same error message. Is
there
anything I can do on my computer to fix it ?
I don't know the portage internals well enough even to know if my
following suggestion is good or bad
On Wednesday 03 June 2009 09:23:51 Arttu V. wrote:
... I wonder why isn't your profiles directory updated by the sync ...
It gets in the way of portage. As soon as it finds a profile update it can't
handle it aborts whatever it's about to do, even if that's syncing.
I got out of this on one
Selon Nikos Chantziaras rea...@arcor.de:
alain.didierj...@free.fr wrote:
#emerge --sync returns the following error:
Performing Global Updates: /usr/portage/profiles/updates/2Q-2009
(Could take a couple of minutes if you have a lot of binary packages.)
.='update pass' *='binary
alain.didierj...@free.fr wrote:
#emerge --sync returns the following error:
Performing Global Updates: /usr/portage/profiles/updates/2Q-2009
(Could take a couple of minutes if you have a lot of binary packages.)
.='update pass' *='binary update' #='/var/db update' @='/var/db move'
Selon Nikos Chantziaras rea...@arcor.de:
alain.didierj...@free.fr wrote:
#emerge --sync returns the following error:
It's been fixed already. Resync to get the bugfix.
Thanks. I'll have to wait till the fix reaches my mirror.
5 matches
Mail list logo
