Summary: | Errors in portage Python scripts | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jon M. Hanson <hansonj> |
Component: | Unclassified | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | hansonj |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jon M. Hanson
2002-06-21 13:12:36 UTC
The output didn't paste correctly; could you add it as an attachment? I'm going to have to mail the attachment to you. Bugzilla is refusing to attach the file. After I select the file on my computer to upload, Bugzilla asks me to login again. After I enter my login information again it says that there was no file selected to attach. Can you attach it to this report? What the attachment contains is the result of trying to update Portage following the instructions in the Portage User Guide. I did a: emerge --clean rsync The next step I did is the very first line in the file I'm going to e-mail to you. OK, got the email and will be fixed in the next Portage release. I just wanted to add that I did not see this problem when I did the following steps: emerge rsync emerge --update world The last emerge picked up the new portage and built it without any of the errors I reported when emerging portage by itself (following the directions in the Portage User Guide). |