Package Details: seafile 9.0.13-1

Git Clone URL: https://aur.archlinux.org/seafile.git (read-only, click to copy)
Package Base: seafile
Description: An online file storage and collaboration tool
Upstream URL: https://github.com/haiwen/seafile
Licenses: GPL2
Conflicts: seafile-server
Provides: seafile-client-cli
Submitter: eolianoe
Maintainer: Joffrey
Last Packager: Joffrey
Votes: 110
Popularity: 0.000000
First Submitted: 2016-08-11 16:38 (UTC)
Last Updated: 2025-04-04 12:14 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 47 Next › Last »

BunBum commented on 2015-08-13 13:46 (UTC)

Hmmm ok, thank you. I will try it / do my best. Could you please look into this forum thread as well? https://bbs.archlinux.org/viewtopic.php?id=201021 How do I run the seaf-gc.sh script?

<deleted-account> commented on 2015-08-13 13:28 (UTC)

@BunBum That script[1] is part of seahub, not seafile, which means I consider this an upstream issue: The seafile developers are unfortunately using the wrong shebang "#!/usr/bin/env python" instead of "!/usr/bin/env python2" pretty much everywhere. This package fixes this in all relevant contained files, but not external files. I suggest you open an upstream issue about this, since they should fix all their python-related shebangs to look for the python you require (which in this case is python2 not python, since they explicitly state they do not support python3). [1] https://github.com/haiwen/seahub/blob/5e0d1068411a9970b8c074d1411939c2ce9d82aa/tools/secret_key_generator.py

<deleted-account> commented on 2015-08-13 13:27 (UTC)

@BunBum That script[1] is part of seahub, not seafile, which means I consider this an upstream issue: The seafile developers are unfortunately using the wrong shebang "#!/usr/bin/env python" instead of "!/usr/bin/env python2" pretty much everywhere. This package fixes this in all contained files, but not external files. I suggest you open an upstream issue about this, since they should fix all their python-related shebangs to look for the python you require (which in this case is python2 not python, since they explicitly state they do not support python3). [1] https://github.com/haiwen/seahub/blob/5e0d1068411a9970b8c074d1411939c2ce9d82aa/tools/secret_key_generator.py

BunBum commented on 2015-08-11 07:00 (UTC)

Since the last update I can't run ./upgrade/upgrade_4.2_4.3.sh. I get a File "/home/seafile/myserver/seafile-server/seahub/tools/secret_key_generator.py", line 53 print key ^ SyntaxError: Missing parentheses in call to 'print'. After that I can't start the service because I get a "ImproperlyConfigured: The SECRET_KEY setting must not be empty." I fixed line 53 manually. After that everything works.

<deleted-account> commented on 2015-08-07 19:02 (UTC)

Since I no longer intend to use distributions with systemd for personal use, I will abandon this package no earlier than 2015-09-01. Should someone be interested in maintaining this package afterwards, he or she can contact me in the interim to become co-maintainer and then sole maintainer once I leave, to ensure a smooth transition. If possible, I would like to hand over the following packages over to a single maintainer, since they comprise a dependency graph: libevhtp-seafile, libsearpc, ccnet, seafile-shared, seafile-client, seafile-client-cli, seafile-server

vit commented on 2015-07-11 20:06 (UTC)

Can anyone explain how to setup with mysql? I can't do seafile-admin setup with mysql.

vit commented on 2015-07-09 17:45 (UTC)

Validity checks failed. Please update. ==> Validating source files with sha256sums... v4.2.2-server.tar.gz ... Passed seafile-admin_virtualenv.patch ... Passed seafile-server.install ... FAILED seafile-server@.service ... Passed seahub-preupgrade ... Passed 0001-Revert-server-put-pids-folder-out-of-seafile-data.patch ... Passed

<deleted-account> commented on 2015-06-29 22:50 (UTC)

@simonsmiley It is a relic from the past that I currently do not have the time to fully verify to be superfluous.

thelinuxguy commented on 2015-06-29 22:48 (UTC)

why does it conflict with django? I don't see a reason. There is nothing documented upstream

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 47 Next › Last »