[buildout/easyinstall] downloading from a url
Hi All, We have a collection of private eggs served from a simple folder served up by Apache. The following works fine to get these eggs via buildout: [buildout] find-links = http://username:password@server/eggs-index/ However, the following does not find the eggs: bin/easy_install --find-links=http://username:password@server/eggs-index/ eggname However, if I mount up the folder served by apache and do: bin/easy_install --find-links=/mnt/path/to/eggs-index/ eggname ...it works fine. bin/easy_install --find-links=http://username:password@server/eggs-index/eggname-version.tar.gz ...bombs out complaining that authorization is required. So, how come the behaviour of all of these is different? cheers, Chris
At 01:05 PM 6/1/2010 +0100, Chris Withers wrote:
Hi All,
We have a collection of private eggs served from a simple folder served up by Apache.
The following works fine to get these eggs via buildout:
[buildout] find-links = http://username:password@server/eggs-index/
However, the following does not find the eggs:
bin/easy_install --find-links=http://username:password@server/eggs-index/ eggname
However, if I mount up the folder served by apache and do:
bin/easy_install --find-links=/mnt/path/to/eggs-index/ eggname
...it works fine.
bin/easy_install --find-links=http://username:password@server/eggs-index/eggname-version.tar.gz
...bombs out complaining that authorization is required.
So, how come the behaviour of all of these is different?
I can't speak to the buildout part, but if you can do an 'easy_install -vvn ...' with the others, I'd like to see what it's doing.
P.J. Eby wrote:
At 01:05 PM 6/1/2010 +0100, Chris Withers wrote:
Hi All,
We have a collection of private eggs served from a simple folder served up by Apache.
However, the following does not find the eggs:
I can't speak to the buildout part, but if you can do an 'easy_install -vvn ...' with the others, I'd like to see what it's doing.
Heh, okay, got to the bottom of this. The username is an Active Directory username, and so has a domain in it, meaning it also has a forward slash in it... Doubling the forward slash solved the problem... Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
Chris Withers wrote:
Heh, okay, got to the bottom of this. The username is an Active Directory username, and so has a domain in it, meaning it also has a forward slash in it...
Doubling the forward slash solved the problem...
...and by "forward slash", I do of course mean "backslash" :-S Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
participants (2)
-
Chris Withers
-
P.J. Eby