-
Notifications
You must be signed in to change notification settings - Fork 810
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation requirements/dependencies issues #1343
Comments
@AmosHason closing this since you mentioned on the gitter channel that you were able to solve this by installing sass on your machine. |
@deshraj it only solves the fifth issue. The README should include a step for installing sass. However, all of the other issues are due to requirements/dependencies gaps, and can be solved by editing those files. |
I see. @AmosHason please feel free to go ahead and open a PR adding instructions to install sass in the README. |
Not just sass. I can confirm that the Postgres10.1 has a similar requirement issues as listed in (2). Recent postgres versions appear to be a known conflict with psycopg2.6, which is used in common.txt For me, Mac Sierra 10.12.6 with brew, fresh postgres 10.1, current clone of EvalAI. Here was the output originally from
And after the update, the
|
Regarding the first issue: it's currently impossible to install libpq-dev using pip (see ncbi/python-libpq-dev#1). |
While installing dependencies for the project got the following error.
After changing "psycopg2==2.6.2" to "psycopg2==2.7.1" in requirements/common.txt the dependencies installed correctly. should I make a PR for this issue? |
Thanks, @mlandry22 for pointing this out. Please feel free to create a pull request for the Postgres dependency updates. |
@Obtin: yeah that is a great idea. Please feel free to comment on the thread or create a pull request. :) |
Did anyone check if PostgreSQL 9.6 is compatible with psycopg2==2.7.3.1? If it is, then: Otherwise, Does that sound good @Obtin ? |
Already fixed. Closing this. |
System
OS: Ubuntu 16.04
Python: 2.7.12
pip: 9.0.1
git: 2.7.4
PostgreSQL: 10.0
RabbitMQ: 3.6.12
virtualenv: 15.1.0
Expected Behavior
Following the steps in the repository README, you should not encounter any issues.
Actual Behavior
1. While executing "pip install -r requirements/dev.txt" (step 3)
Collecting psycopg2==2.6.2 (from -r requirements/common.txt (line 15))
Using cached psycopg2-2.6.2.tar.gz
Complete output from command python setup.py egg_info:
running egg_info
creating pip-egg-info/psycopg2.egg-info
writing pip-egg-info/psycopg2.egg-info/PKG-INFO
writing top-level names to pip-egg-info/psycopg2.egg-info/top_level.txt
writing dependency_links to pip-egg-info/psycopg2.egg-info/dependency_links.
txt
writing manifest file 'pip-egg-info/psycopg2.egg-info/SOURCES.txt'
Error: You need to install postgresql-server-dev-X.Y for building a server-s
ide extension or libpq-dev for building a client-side application.
Workaround: execute "apt-get install libpq-dev" first.
Suggested fix: add libpq-dev to the requirements.
2. While executing "pip install -r requirements/dev.txt" (step 3)
Collecting psycopg2==2.6.2 (from -r requirements/common.txt (line 15))
Using cached psycopg2-2.6.2.tar.gz
Complete output from command python setup.py egg_info:
running egg_info
creating pip-egg-info/psycopg2.egg-info
writing pip-egg-info/psycopg2.egg-info/PKG-INFO
writing top-level names to pip-egg-info/psycopg2.egg-info/top_level.txt
writing dependency_links to pip-egg-info/psycopg2.egg-info/dependency_links.
txt
writing manifest file 'pip-egg-info/psycopg2.egg-info/SOURCES.txt'
Error: could not determine PostgreSQL version from '10.0'
Workaround (suggested fix): set "psycopg2==2.7" in requirements/common.txt (see psycopg/psycopg2#594).
3. While trying to execute "bower install" (step 8)
bash: bower: command not found
Workaround: execute "npm install -g bower" first.
Suggested fix: add bower to the dependencies.
4. While trying to execute "gulp dev:runserver" (step 9)
bash: gulp: command not found
Workaround: execute "npm install -g gulp-cli" first.
Suggested fix: add gulp-cli to the dependencies.
5. While executing "gulp dev:runserver" (step 9)
events.js:160
throw er; // Unhandled 'error' event
^
Error: Gem sass is not installed.
Workaround: execute "gem install sass" first.
Suggested fix: add a preceding step in the repository README to execute "gem install sass".
The text was updated successfully, but these errors were encountered: