strongswan / strongMan

Management UI for strongSwan
https://www.strongswan.org/
Other
114 stars 39 forks source link

Error running setup.py #115

Closed limace255 closed 4 years ago

limace255 commented 4 years ago

Hi there, I want to try this UI for strongswan. When I follow the instructions, I get following errors :

./setup.py install Start strongMan installation

  • Virtualenv usage: virtualenv [--version] [--with-traceback] [-v | -q] [--app-data APP_DATA] [--clear-app-data] [--discovery {builtin}] [-p py] [--creator {builtin,cpython3-posix,venv}] [--seeder {app-data,pip}] [--no-seed] [--activators comma_sep_list] [--clear] [--system-site-packages] [--symlinks | --copies] [--download | --no-download] [--extra-search-dir d [d ...]] [--pip version] [--setuptools version] [--wheel version] [--no-pip] [--no-setuptools] [--no-wheel] [--symlink-app-data] [--prompt prompt] [-h] dest virtualenv: error: unrecognized arguments: --no-site-packages Command '['virtualenv', '-p', 'python3', '--no-site-packages', '/opt/stringman/strongMan/env']' returned non-zero exit status 2

Is this due to my virtualenv package version ? Here is my configuration : python3 virtualenv (20.0.7)

Thanks in advance

limace255 commented 4 years ago

Replacing "no-site-packages" by "system-site-packages" obviously helped, but I'm not sure that it's what you want, by the way

limace255 commented 4 years ago

Ok, sorry for the noise, and not sure if this is the appropriate place for that : I think that during setup.py, packages installation of requirements.txt does not happen inside the virtualenv. I faced some errores after changing " --no-site-packages " by " system-site-packages", but then, at least, te whole process was good. Then, when adding the service, it failed, saying "no gunicorn" in the "env" path. I made following :

tobiasbrunner commented 4 years ago

Thanks for the report. As far as I can tell, --no-site-packages has been deprecated for over 8 years (v1.7) and its behavior has been the default since then. You probably shouldn't replace it with --system-site-packages but just remove it instead. Pushed a fix to the 115-virtualenv-fix branch.