Package Details: seafile-shared 6.0.0-2

Git Clone URL: https://aur.archlinux.org/seafile.git (read-only)
Package Base: seafile
Description: Shared components of Seafile (seafile-daemon, libseafile, python bindings, manuals)
Upstream URL: https://github.com/haiwen/seafile
Licenses: GPL3
Conflicts: ccnet<6.0.0
Submitter: eolianoe
Maintainer: eolianoe (fordprefect, thealchemist)
Last Packager: eolianoe
Votes: 66
Popularity: 6.450226
First Submitted: 2016-08-11 16:38
Last Updated: 2016-09-11 18:18

Dependencies (9)

Sources (7)

  • 0001-Revert-server-put-pids-folder-out-of-seafile-data.patch
  • create-default-conf-dir.patch
  • libseafile.in.patch
  • seafile-admin_virtualenv.patch
  • seafile-server-6.0.0.tar.gz
  • seafile-server@.service
  • seahub-preupgrade

Pinned Comments

eolianoe commented on 2016-09-06 20:07

@pvagner & @thealchemist: I'll be happy to add you as co-maintainers if you have some improvments to make to the PKGBUILD, just send me an e-mail.

I'm stil trying to properly package seahub and by the next week I'll try to repackage seafile according to [1].

[1] https://blogs.seafile.com/2016/08/18/seafile-server-core-changes-license-to-agplv3-and-will-be-separated-from-client-source-code/

Latest Comments

pvagner commented on 2016-09-23 09:21

@thealchemist Thank you! Now I'm using your 6.0.3 packages. I am not using seafile-client on the same machine so I don't need it at present. I am still keeping mysql setup and working seafile client on my todo list, however I don't feel confident enough to be able to suggest final solutions at this time. If I'll get something working, I'll post it here.

eolianoe commented on 2016-09-11 15:39

@thealchemist: I will merge your changes, but with the 6.0.3 version in [1] the
`seaf-daemon` is no more present compared to the 5.1.4 (or 6.0.0) version in [2] and this binary is needed for the client [3,4]

[1] https://github.com/haiwen/seafile-server
[2] https://github.com/haiwen/seafile
[3] https://github.com/haiwen/seafile-client
[4] https://aur.archlinux.org/packages/seafile-client

thealchemist commented on 2016-09-10 18:04

@eolianoe: I flagged the packages that I updated out-of-date

@TesterMcTest and @pvagner: maybe someone from the seafile-forums can help you with MYSQL. Would be nice to have it here.

thealchemist commented on 2016-09-10 17:52

Hi,
I went through all seafile dependencies (libevhtp, libsearpc, ccnet) and updated them to their last version I could find. As far as I can say, it is working fine this way (tested the built on the RPi 2*, file upload through seahub works on a server with SSL/DDNS/nginx). You can find my stuffs here:**
http://s000.tinyupload.com/?file_id=08827869627534314726

If I get this right, there are many changes in version 6.x.x, hence documentation [1] is currently not up-to-date. Generally speaking, the manual mainly covers the binary distribution and configuration is done with supplied scripts. Sadly the sources distribution is not really compatible with the scripts of the binary distribution (i.e. setup-seafile-mysql.sh), hence I found no option to deploy the server with mysql resp. mariadb.

@eolianoe: TMHO the 6.0.3 version is now only the seafile-server so I unified your split package to a single seafile-server. I did not went through the patches so they are still applied.

*not the seafile-rpi package but the "mainline" or development sources.
**does anybody see the irony in using an uploader for such software...

[1] http://manual.seafile.com/

eolianoe commented on 2016-09-06 20:07

@pvagner & @thealchemist: I'll be happy to add you as co-maintainers if you have some improvments to make to the PKGBUILD, just send me an e-mail.

I'm stil trying to properly package seahub and by the next week I'll try to repackage seafile according to [1].

[1] https://blogs.seafile.com/2016/08/18/seafile-server-core-changes-license-to-agplv3-and-will-be-separated-from-client-source-code/

thealchemist commented on 2016-09-06 11:45

I was not alone. I solved the issue by giving executable permissions to the /srv/seafile directory, i.e.
# chmod 711 /srv/seafile
The source was https://forum.seafile.com/t/website-not-working-properly/433

@pvagner: Did you already succeed with 6.0.2 or 6.0.3 and do you think about (co-)maintaining the package?

pvagner commented on 2016-09-01 05:56

@thealchemist sorry for the late reply. No I haven't changed the systemd service file. I am starting like systemctl start seafile-server@thatfoldername I've described in my previous comment. Anyway I'm getting some seahub tracebacks in the django_requests.log so I am just going try tupdating to freshly released 6.0.2 now.

thealchemist commented on 2016-08-23 14:24

@pvagner: This would mean, your setup is the same despite you use a subdirectory as mentioned in the Wiki. This may be the problem. Did you also change the systemd-service accordingly, i.e. replaced both occurrences of %i (wiki: %h) with your directory name?

pvagner commented on 2016-08-22 08:59

@thealchemist The arch wiki instructions worked for me i.e. I've created a user, created a directory for the whole site inside its home folder, created seafile-server directory in that, unpacked corresponding seahub.

thealchemist commented on 2016-08-16 18:50

Hello,

firstly thanks for maintaining these packages. As far as I can tell compiles fine using makepkg or yaourt (Tested on a Cubieboard 2 and Raspberry Pi 2, hence ARMv7). The server also starts when using the systemd service, BUT the seahub web interface is messed, i.e. no images are loaded, instead there is a language list and a login mask when scrolled down. I poke on my nginx configuration for some time now and loosly followed both the seafile documentation (http://manual.seafile.com/build_seafile/server.html --> deployment section) and our own outdated wiki article. My setup only differs in not using a separate <server-url.org> directory.

Any idea what I did wrong?

All comments