-
Notifications
You must be signed in to change notification settings - Fork 89
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
Build script stops with building cryptography (and some more errors...) #99
Comments
Thanks for the hint. Currently also having problems building for buster based distros: |
Great to see you changed something. It was just luck to find out whats the problem with cryptography, but i'm a noob in coding, so i'm very limited while fixing those bugs ;-). But i can test it and hopefully there will be a chance to get scrpit working finde as before. |
I managed to build server package now. What i did: Cloned this repo with latest changes, manually set cryptography version (like above), intstalled gvm, installed go1.14 with that and set that to default (with go version 1.14.x from apt it didn't work). |
I've check the
This is comming from buster-backports, as indicated in his repository
To sum up: It is unsual that the build works with older |
See rpi issue haiwen/seafile-rpi#99
I tested and the
The build command:
|
I think i have installed from backports, there are some different versions, but that didn't wortk for me. Maybe i did someting wrong, but with gvm it was really easy and that works. |
FWIW |
You are right, but i have installed 1.14 (and tried with 1.15 too) from backports, and that didn't work, so i installled 1.14 with gvm, what works. Don't know why it didn't with golang from backports repo. Edit: OK, i tried on my second device, with go1.15 from backports and this is what i get: Edit1: Now i have installed 3 versions of go with apt, 1.11, 1.14 + 1.15. Found this about managing multiple versions and switched to 1.14 with update-alternatives --config go.........and voila, no error. Edit2: Switched to go 1.15, missing 'fileserver' now is in place and build was OK. Don't know why build on my other device with gvm/go 1.14 was completed with no error.... |
@nihilistaX Thanks for your comments and your honesty. @Gustl22 I made some research building the seahub_thirdparts python modules (requirements.txt) and this is the working outcome:
The commented lines are the original from the official seahub repository. The uncommented one are the adapted by me, which I tested for build success. Here few comments why I tried to do so:
Edit: Here the updated versions of the modules, which were sucesfully built and which I'm using atm for
|
I found that building 9.0.2 for buster stops with error while building cryptography.
Here >>> i see, that latest version (36.0.1) didnt work with buster, so i manually set cryptography==36.0.0 within requirements.txt.
Before i had to comment out downloading of requirements.txt from server to prevent overwriting with using build script.
Now after this build script runs with success....but only till build-server.py script, this has been moved to /seahub/scripts.
I changed one line in buildscript and got it running, but ended with error...so gave up for now
The text was updated successfully, but these errors were encountered: