warning: no previously-included files matching '*.pyc' found anywhere in distribution
Not found:
https://pypi.python.org/simple/plone.recipe.zope2instance/
Not found:
https://pypi.python.org/simple/plone.recipe.zope2instance/
Couldn't find index page for 'plone.recipe.zope2instance' (maybe misspelled?)
Not found:
https://pypi.python.org/simple/
Getting distribution for 'plone.recipe.zope2instance==4.2.20'.
While:
Installing.
Getting section instance.
Initializing section instance.
Installing recipe plone.recipe.zope2instance.
Getting distribution for 'plone.recipe.zope2instance==4.2.20'.
Error: Couldn't find a distribution for 'plone.recipe.zope2instance==4.2.20'.
Do you have shared eggs directories? Did you try to add to a CI configuration?
@idgserpro I just spotted your line where you noticed adding index = doesn't work, for me it does, but with zc.buildout 2.8.0 in my buildout(s). Weird indeed.
Jenkins build jobs will start to fail now as well where bootstrap.py is run.
Couldn't find index page for 'plone.recipe.zope2instance' (maybe misspelled?)
Getting distribution for 'plone.recipe.zope2instance==4.3'.
While:
Installing.
Getting section instance.
Initializing section instance.
Installing recipe plone.recipe.zope2instance.
Getting distribution for 'plone.recipe.zope2instance==4.3'.
Error: Couldn't find a distribution for 'plone.recipe.zope2instance==4.3'.
If you already has cached eggs, there's no error, that's why we're using mkdir eggs && bin/buildout buildout:eggs-directory="eggs" buildout:download-cache="eggs", to force it to always download the eggs.
@mauritsvanrees using the virtualenv and different bootstrap (for buildout 1 and 2) we still get the same error if zc.buildout is pinned to any version different from 2.9.5.
@idgserpro: I need the updated bootstrap.py because otherwise the bootstrap call gives an error. After that finishes correctly, and I ignore the eggs cache, I get the same error as you. It works for me when I add this to your last command:
Now runs successfully. I know it doesn't make sense to have a multiline index (since it expects just one value) but it's funny that didn't work even having just one url.
I confirm that adding the 'index=' line in [buildout] section of my buildout.cfg fixes this problem for me.
Plone 5.0.7 fresh install using unified installer on Debian 9 server with installer generated buildout.cfg.
I did not do anything else with any files such as bootstrap.py or others mentioned here (messing with pieces of buildout at that level is way over my head).
I'd just started trying to install add-ons to this fresh install via the usual means and kept getting the:
Couldn't find index page for product-xyz (maybe misspelled?)
...
Error: Couldn't find a distribution for product-xyz
I found this thread by sheer luck, after a fruitless hour+ searching & trying to solve this - because the thread subject/title has nothing to do with the errors one gets at the buildout user level and is most likely to be searching for help with.
Is it possible to change the title of this thread to make it more findable vs. the actual error msg?
Including the start of the two main error message is great, thanks.
That gives a search for the actual error message something to find.
The last part of the title is not search-useful, nobody will search on that if they get this error. If they know it's about the http/https change on pypi they likely know the solution already.
Just some tips on issue titles from 7+ years software QA/test experience...