Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Problem: ss trusty/xenial pkgs have psycopg pip dependency deleted #62

Open
scollazo opened this issue Oct 31, 2017 · 1 comment
Open

Problem: ss trusty/xenial pkgs have psycopg pip dependency deleted #62

scollazo opened this issue Oct 31, 2017 · 1 comment

Comments

@scollazo
Copy link
Contributor

When building with psycopg requirements, there is a bug:

"strip: debian/archivematica-storage-service/usr/share/python/archivematica-storage-service/lib/python2.7/site-packages/psycopg2/stlS8Kcz: Not enough room for program headers, try linking with -N"

The bug is similar to this one: numpy/numpy#7570
@sevein sevein changed the title psycopg is removed from ss requirements Problem: psycopg deleted from SS requirements in deb/trusty Nov 9, 2017
@sevein sevein added the AM17 label Nov 9, 2017
@sevein
Copy link
Member

sevein commented Nov 9, 2017

Adding the AM17 label. We could live without solving this issue but it would be a nice to have.

scollazo added a commit that referenced this issue Nov 15, 2017
@scollazo
xenial ss: remove psycopg dependency
13b2660 
Related to #62.
Also, enable pip index to workaround #84, a we do in trusty
scollazo added a commit that referenced this issue Nov 17, 2017
@scollazo
xenial ss: remove psycopg dependency
30e0155 
Related to #62
sevein pushed a commit that referenced this issue Nov 17, 2017
@scollazo @sevein
xenial ss: remove psycopg dependency
3f2fcb9 
Related to #62
@sevein sevein changed the title Problem: psycopg deleted from SS requirements in deb/trusty Problem: ss trusty/xenial pkgs have psycopg pip dependency deleted Nov 17, 2017
@sevein sevein removed the AM17 label Mar 12, 2018
@sevein sevein mentioned this issue Apr 27, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sevein @scollazo