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.
Created attachment 253625 [details] emerge --info
Created attachment 253627 [details] python traceback for repoman.
Created attachment 253629 [details] timestamp.chk at the time repoman choked.
This should be fixed in 2.1.9 (which uses ElementTree instead of minidom).