145482 – portage-2.1.1 - traceback during emerge metadata

Bug 145482 - portage-2.1.1 - traceback during emerge metadata

Summary: portage-2.1.1 - traceback during emerge metadata

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Interface (emerge) (show other bugs)
Hardware:	All Linux

Importance:	High normal
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-08-29 08:19 UTC by Fab
Modified:	2006-08-29 11:44 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
keyerror traceback (traceback,2.00 KB, text/plain) 2006-08-29 08:20 UTC, Fab	Details
emerge --info (infos,2.86 KB, text/plain) 2006-08-29 08:20 UTC, Fab	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Fab 2006-08-29 08:19:50 UTC

Hi,

After doing an emerge --sync, I got a traceback when updating cache.
Then I update portage from 2.1.1_pre4-r4 to 2.1.1_rc1-r1 and I tried :
   # rm -rf /var/cache/edb && emerge --sync

==> same issue.

I tried to search forums and bugzilla, I found nothing.

Thanks for help.

Comment 1 Fab 2006-08-29 08:20:22 UTC

Created attachment 95375 [details]
keyerror traceback

Comment 2 Fab 2006-08-29 08:20:49 UTC

Created attachment 95376 [details]
emerge --info

Comment 3 Zac Medico gentoo-dev

2006-08-29 11:12:03 UTC

Try `rm -rf /var/portage/metadata/cache && emerge --sync`.

Comment 4 Fab 2006-08-29 11:44:02 UTC

(In reply to comment #3)
> Try `rm -rf /var/portage/metadata/cache && emerge --sync`.
> 

Thanks, that fix it.