search

ogrisel / wheelhouse-uploader

Script to help maintain a wheelhouse folder on a cloud storage.
MIT License
32 stars 12 forks source link

EnvironmentError: [Errno 2] No such file or directory when installing apache libcloud on appveyor #29

Open ogrisel opened 6 years ago

ogrisel commented 6 years ago

Apparently, the latest libcloud cannot be installed under appveyor with the following error message:

/45a9d3bba612fc3f47ef085a14446a4f68f45ce10070562edff1e9291150/apache_libcloud-2.3.0-py2.py3-none-any.whl (4.9MB)
Could not install packages due to an EnvironmentError
EnvironmentError: [Errno 2] No such file or directory: 'c:\\users\\appveyor\\appdata\\local\\temp\\1\\pip-install-fnscs_\\apache-libcloud\\libcloud/test/compute/fixtures/azure_arm/_subscriptions_99999999_9999_9999_9999_999999999999_resourceGroups_000000_providers_Microsoft_Compute_virtualMachines_test_node_1_InstanceView.json'
Command exited with code 1
ogrisel commented 6 years ago

FYI, this is not appveyor specific, I reproduced it on a local windows machine. pip install apache-libcloud==2.2.1 seems to work though (and upload works both on Python 3.7 and Python 2.7 with that version).

I will probably do a new release to pin to that version for now.

matthew-brett commented 6 years ago

C.f. https://issues.apache.org/jira/browse/LIBCLOUD-1000?jql=project%20%3D%20LIBCLOUD%20AND%20text%20~%20%22no%20such%20file%20directory%22%20ORDER%20BY%20created%20DESC

ogrisel commented 6 years ago

I encountered the encryptfs limitation myself on my linux laptop and I put my venvs folder under a non-encrypted folder in /opt because of that.

But this is not exactly the same problem: pip fails to install apache-libcloud==2.3.0 under windows. The fix is probably to rename that file to something shorter in the libcloud package.

matthew-brett commented 6 years ago

It looks very similar - and the report seems to say that the current release is broken in that respect. Is it possible this is a Windows file path length limitation?

ogrisel commented 6 years ago

It's very likely. I reported:

https://issues.apache.org/jira/browse/LIBCLOUD-1003?jql=project%20%3D%20LIBCLOUD%20AND%20text%20~%20%22no%20such%20file%20directory%22%20ORDER%20BY%20created%20DESC

and linked it to LIBCLOUD-1000.

ogrisel commented 6 years ago

I have also released 0.10.1 as a stopgap with a dependency pinned to apache-licloud==2.2.1