If the file `timestamp.chk` in the portage tree is corrupted, portage "crashes". If the file, simply does not exists, portage, simply, create it. My suggestion is to handle the `problem` in two different ways: 1) Emerge can consider the file corrupted as a non-existing file, and replace it with a new one. 2) emerge can exits, showing a message where should be explained that the problem could be the corruption of the file timestamp.chk (and you can delete it without risk) Reproducible: Didn't try Steps to Reproduce: 1. 2. 3.
If the file `timestamp.chk` in the portage tree is corrupted, portage "crashes" showing lines like theese: Saltatempo root # emerge sync Traceback (most recent call last): File "/usr/bin/emerge", line 2051, in ? mytimestamp=time.mktime(time.strptime(content[0], "%a, %d %b %Y %H:%M:%S +0000")) File "/usr/lib/python2.3/_strptime.py", line 424, in strptime raise ValueError("time data did not match format: data=%s fmt=%s" % ValueError: time data did not match format: data= fmt=%a, %d %b %Y %H:%M:%S +0000 Saltatempo root #
I've fixed this problem in .51(it's not stable yet). But I forget the bug number.. Anyway, I'm closing this bug. Thank you for reporting.
