Portage broken during crash

[parressh]

My computer crashed while doing an 'emerge rsync' and I think it blew away a lot or portage files (/var/cache/edb stuff). So now I get all kinds of errors when running emerge. Here's an example of the output I get.

# emerge fwbuilder
portage: Update type "MD5" not recognized.
portage: Update type "" not recognized.
Calculating dependencies \portage: aux_get(): stale entry was not regenerated for net-libs/libfwbuilder-0.10.8-r1; exiting.
!!! list index out of range

!!! Problem in net-misc/fwbuilder dependancies.
!!! 1

Does anyone have any ideas what I need to do to try and fix this? Thanks.

-Matt

[pjp]

First thing would be an rsync, but I doubt that will help.
_________________
Quis separabit? Quo animo?

[parressh]

Yeah, I've done several rsync's, but it hasn't helped.

Here's what happens when I do an emerge -pu world

# emerge -pu world
portage: Update type "MD5" not recognized.
portage: Update type "" not recognized.

These are the packages that I would merge, in order.

Calculating world dependencies /portage: aux_get(): (1) couldn't open cache entry for sys-libs/ncurses-5.2.20020511-r3
(likely caused by syntax error or corruption in the sys-libs/ncurses-5.2.20020511-r3 ebuild.)
|portage: aux_get(): (1) couldn't open cache entry for sys-libs/readline-4.2a-r1
(likely caused by syntax error or corruption in the sys-libs/readline-4.2a-r1 ebuild.)
/portage: aux_get(): stale entry was not regenerated for sys-apps/e2fsprogs-1.32; exiting.
!!! list index out of range

[TheEternalVortex]

Try moving all of the cache files somewhere else, and do an emerge sync.
_________________
-- Andy

[parressh]

That didn't work, but when I moved the folders of the ebuilds that were complaining:

/usr/portage/sys-libs/ncurses/
/usr/portage/sys-libs/readline/
/usr/portage/sys-apps/e2fsprogs/

emerge -pu world worked fine.

Then I did emerge rsync, and I got the same error messages as posted above. Any ideas about that?

[wormie]

I had a nastry crash at one point and it screwed up my portage too. However, I didn't get the same error messages. I also haven't found an easy way to rebuild the world file. qpkg still works, though, so I've manually attempted to do it by going through installed packages and re-emerging them.
You might try doing a fresh emerge of ncurses, readline, and e2fsprogs to rebuild the cache entries. Hopefully this will at least get rid of your error messages. Unfortunately, you may still end up with an out-of-sync world file. Aside from emerging stuff again, I don't know of a way to correct this. With luck, somebody else does.

[parressh]

If I try to emerge portage, this is what eventually happens:

>>> original instance of package unmerged safely.
>>> Clearing invalid entries in dependancy cache...egrep: Update: No such file or directory
egrep: type: No such file or directory
egrep: "MD5": No such file or directory
egrep: not: No such file or directory
egrep: recognized.: No such file or directory
egrep: portage:: No such file or directory
egrep: Update: No such file or directory
egrep: type: No such file or directory
egrep: "": No such file or directory
egrep: not: No such file or directory
egrep: recognized.: No such file or directory
egrep: 11: No such file or directory
wc: write error: Broken pipe
wc: write error: Broken pipe
wc: write error: Broken pipe

It just keeps saying Broken pipe until I kill the process. Does anybody know how to fix that?

[zhenlin]

Sounds like an ancient portage problem. Try upgrading to portage-2.0.44.

If you have successfully rsynced, try finding the portage-rescue tarball and using it.

[parressh]

I used the portage-rescue tarball, but I still see the write error: Broken pipe and other error messages. By the way, I am using 2.0.44.