Package Details: seafile 9.0.11-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: 111
Popularity: 0.000000
First Submitted: 2016-08-11 16:38 (UTC)
Last Updated: 2024-11-14 17:06 (UTC)

Pinned Comments

Latest Comments

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

VinTeK commented on 2015-09-20 05:35 (UTC)

@BunBum I had the same problem and found /usr/bin/seafserv-gc solved it. Inside your server's base directory, you'll want to run it with arguments $ seafserv-gc -c ccnet -d seafile-data Don't forget to do a --dry-run first.

Turtizzle commented on 2015-09-15 20:51 (UTC)

After fooling around a little bit, I managed to fix the issue. Installed freetype2, linked /usr/include/freetype to /usr/include/freetype2, installed python2-pillow and tk, uninstalled pillow in the separate seafile-environment (while attempting to reinstall it, it said Requirement already satisfied). I'm not sure what exactly of the above helped, or if all of it was required, but my Captchas started loading. Just leaving this here in case anyone has the same problem...

Turtizzle commented on 2015-09-15 19:37 (UTC)

Captchas (after a few failed login attempts) don't show up for me. I am required to enter one, but the image doesn't load. After further investigation, I narrowed it down to the python error "_imagingft C module is not installed". After some googling, it suggests that PIL might be compiled without freetype support, but I currently don't have the time to look further into it (and I kinda lack the understanding of that separate python environment). Eventually I'll check further, but maybe this helps someone else to save time if the same issue occurs: http://pastebin.com/raw.php?i=SU3RPWYn

<deleted-account> commented on 2015-09-05 15:38 (UTC)

This is the last upstream-based package update from me. Since I have received mail from one from person interested in maintaining, I will not orphan the packages just yet, but in the next couple of days.

kdop commented on 2015-09-03 02:00 (UTC)

I got it working on my Raspberry Pi but needed to install https://aur.archlinux.org/packages/libselinux/ to supply a missing library. It took me the better part of a day to get everything built and configured properly. I generally stuck with https://wiki.archlinux.org/index.php/Seafile until it came time to "Download seahub and extract it:" The appropriately versioned RPi variant is linked from Seafile's download page at https://github.com/haiwen/seafile-rpi/releases I then followed http://manual.seafile.com/deploy/using_mysql.html because sqlite hadn't worked for me the previous go around. After "seafile-admin setup" from the Arch wiki, it was tweaking configuration files and firewalls. Thanks for your awesome work! Could not have done it without @calrama

BunBum commented on 2015-08-14 07:05 (UTC)

Thank you calrama. Unfortunately I don't get it running. Maybe @ddanier can help me out of this? I mean everbody has this problem and should clean up unused data periodically.

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

@BunBum You will at least need to copy it from the /usr/share directory to your seafile-server instance's path (where it would be in the binary distribution) and if it uses python ensure it uses the correct version of python (2). If the script has any dependencies in /usr/share, those will need to be copied, too. I don't have a seafile server on Archlinux anymore, so I can't test any of this.

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

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