Bug 344683

Summary:	sys-apps/portage: repoman chokes when scanning /usr/portage, python stack dump
Product:	Portage Development	Reporter:	Raymond Jennings <shentino>
Component:	Repoman	Assignee:	Portage team <dev-portage>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	335925
Attachments:	emerge --info python traceback for repoman. timestamp.chk at the time repoman choked.

Description Raymond Jennings 2010-11-08 14:13:10 UTC

I ran repoman against my current copy of the portage tree, and it caused python to dump stack.

I really don't know what's going on here but I really don't think that choking with a stack trace is an acceptable response to whatever was wrong with the portage tree when I checked it.

Reproducible: Sometimes

Steps to Reproduce:
1.  cd /usr/portage
2.  repoman scan

Actual Results:  
It generated a python traceback.

Expected Results:  
I don't know, depends on what made repoman choke.

Since the portage tree is inherently volatile, I've included a copy of timestamp.chk

Really stumped on this one.

Comment 1 Raymond Jennings 2010-11-08 14:14:33 UTC

Created attachment 253625 [details]
emerge --info

Comment 2 Raymond Jennings 2010-11-08 14:15:39 UTC

Created attachment 253627 [details]
python traceback for repoman.

Comment 3 Raymond Jennings 2010-11-08 14:16:17 UTC

Created attachment 253629 [details]
timestamp.chk at the time repoman choked.

Comment 4 Zac Medico gentoo-dev

2010-11-09 01:23:30 UTC

This should be fixed in 2.1.9 (which uses ElementTree instead of minidom).