You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had 2 issues with the release_archive make target I did not have before. I changed my dev environment, so I'm not sure if it's due to my configuration or not.
This usually happens when using a virtualenv with outdated versions of pip and setuptools, I've seen this recently on Debian Stretch hosts with Python 3.5 virtualenvs. An easy workaround is to pin a minimum version of pip to be used by the virtualenv.
mkdir -p $(ARCHIVE_PREFIX)/{doc,vendor}
This could happen if the path expansion {doc,vendor} fails, e.g. when using sh as the SHELL interpreter. Maybe we should enforce Bash usage in the Makefile?
I had 2 issues with the
release_archive
make target I did not have before. I changed my dev environment, so I'm not sure if it's due to my configuration or not.htmldoc
I had to run
pip install wheel
before installing mkdoc (https://stackoverflow.com/a/44862371/1484919). I don't really know python tools so I'm not sure what was going on here.release_zip
The command
mkdir -p $(ARCHIVE_PREFIX)/{doc,vendor}
while running make wouldn't create the directories properly.However running the command directly from my zsh, it was working properly. Maybe I'm missing some dev package...
The text was updated successfully, but these errors were encountered: