Summary: | using the -g option to emerge makes emerge crash | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Frank Van Damme <frank.vandamme> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | neilbags |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Frank Van Damme
2005-04-20 05:07:48 UTC
Might wanna check your webserver. That error indicates that it's doing something that isn't a standard starting response. This problem occurs on apache2 and lighttpd but not on apache 1.3. The parsing code doesn't seem to be designed for apache 1.3 only. A workaround is to mask apache2 on the BINHOST server. Another workaround may be to change PORTAGE_BINHOST_CHUNKSIZE on the client, but I havn't had any success with this. (In reply to comment #2) > This problem occurs on apache2 and lighttpd but not on apache 1.3. > The parsing code doesn't seem to be designed for apache 1.3 only. > > A workaround is to mask apache2 on the BINHOST server. > > Another workaround may be to change PORTAGE_BINHOST_CHUNKSIZE on the client, > but I havn't had any success with this. > I meant 'The parsing code seems to be designed for apache 1.3 only.' Still an issue? I don't have the resources to work on this bug anymore. Sorry. Well, would need to see the actual traffic for debugging. |