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.

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

[seafile-server] Document how official releases were built #2414

Open
zhanghai opened this issue Dec 31, 2020 · 0 comments
Open

[seafile-server] Document how official releases were built #2414

zhanghai opened this issue Dec 31, 2020 · 0 comments

Comments

@zhanghai
Copy link

zhanghai commented Dec 31, 2020

Hi, I'm trying to build seafile-server from source and I came across seafile-rpi's build3.sh which invokes seafile-server's build-server.py, and it seems to generate something similar to the offcial download https://download.seadrive.org/seafile-server_8.0.1_x86-64.tar.gz.

I'm building it with GitHub actions at zhanghai/seafile-server-github-actions-build. However, one strange thing is that although I explicitly set python to 3.6 with GitHub's official action setup-python, the result artifact at https://github.com/zhanghai/seafile-server-github-actions-build/releases/tag/v8.0.1 still contains python2.7 under seafile/lib, unlike the official build which contains python3.6 under seafile/lib64.

Meanwhile, it was announced that ccnet-server was removed in seafile-server 8.0.1, and libccnet.so indeed disappeared from seafile/lib in the official build, but my GitHub Actions build still contains ccnet in a number of places. So it seems the build-server.py in seafile-server is outdated.

Could you provide more information on how exactly was the official 8.0.1 release built (e.g. the latest build script & dependency versions)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant