Summary: | Original install seems to be autocleaning necessary components like "emerge" during first "emerge system" | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jeff Cunningham <jeffrey> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | VERIFIED NEEDINFO | ||
Severity: | blocker | CC: | jeffrey.k.cunningham |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | requested emerge.log |
Description
Jeff Cunningham
2003-06-14 20:01:39 UTC
portage version that was installed? What stage was this system? Please post /var/log/emerge.log Created attachment 13794 [details]
requested emerge.log
Here is my emerge.log as per your request. I'm not sure it will do any good, as
I went back and did an entire stage 1 reinstall successfully after setting
AUTOCLEAN="no" in /etc/make.conf. The version of portage I'm working with is
2.0.48-r1. I am using gentoo-sources.
What you will notice in the log below is the incredibly frequent restarts that
are necessary to get this to emerge sync from behind this corporate firewall.
It will download at a high rate for maybe ten seconds, then stall. Once in a
while it will restart again for a few seconds, then stall again. At that point
it just times out. To get this to ever finish I had to set the rsync retries up
to 1000 and the timeout down to about 10 seconds (it would never start again
after the second stall). I don't know if there's any relationship between this
problem and portage being "autocleaned" out of existence, but I thought I'd
mention it. Feel free to email me if there's anything else I can tell you.
-Jeff
Without being able to reproduce it it's hard to fix (in case it's a bug and wasn't fixed yet). I have left autocleaning turned off, so I don't know if this bug is fixed or not. But I'm not reading reports of others having this problem anymore either. I'm going to close this on the assumption that this bug has been fixed at some point. Jeff Cunningham |