On Tue, Mar 29, 2011 at 04:25:51PM -0400, Jeff Kunce wrote:
> There seem to be some problems with packages on sourceforge not working with
> buildout. Something about sourceforge is sending two content-length
> headers. Anything the buildout gurus here can add?
>
> Description of problem. Suggest
On 2011-3-29 22:54, P.J. Eby wrote:
At 04:25 PM 3/29/2011 -0400, Jeff Kunce wrote:
There seem to be some problems with packages on sourceforge not
working with buildout. Something about sourceforge is sending two
content-length headers.
Update your setuptools to 0.6c12dev-r88975 for the fix.
On Tue, Mar 29, 2011 at 4:54 PM, P.J. Eby wrote:
> Update your setuptools to 0.6c12dev-r88975 for the fix.
Egads, Philip! Do regular version numbers cost more in your neighborhood?
-Fred
--
Fred L. Drake, Jr.
"A storm broke loose in my mind." --Albert Einstein
_
At 04:25 PM 3/29/2011 -0400, Jeff Kunce wrote:
There seem to be some problems with packages on sourceforge not
working with buildout. Something about sourceforge is sending two
content-length headers.
Update your setuptools to 0.6c12dev-r88975 for the fix.
(If you're using a forked setuptoool
There seem to be some problems with packages on sourceforge not working with
buildout. Something about sourceforge is sending two content-length
headers. Anything the buildout gurus here can add?
Description of problem. Suggests just eliminating sourceforge from allowed
hosts:
http://plone.293351
