Summary: | after upgrading to 2.1pre7-r2 updating cache fails | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Dariusz Gadomski <darkgod> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dariusz Gadomski
2006-03-28 13:10:53 UTC
It seems that /usr/bin/emerge did not update. It should be a symlink to /lib/portage/bin/emerge. Maybe you only need to create the symlink, like this: rm -f /usr/bin/emerge ln -s /lib/portage/bin/emerge /usr/bin/emerge That should be /usr/lib/portage/bin of course > rm -f /usr/bin/emerge
> ln -s /usr/lib/portage/bin/emerge /usr/bin/emerge
I've just done that but unfortunately cache update is still broken :(
Can you still reproduce this with a newer 2.1pre? I've once hit that too and figured out that i was using an old 'emerge' with a newer portage because I used some nasty quirks. > Can you still reproduce this with a newer 2.1pre?
I'm afraid not. Due to hard drive failure I was forced to install Gentoo once again. I had no problem with 'emerge' on new system.
there's never been a bug *yedimindtrick* |