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 .. 38 39 40 41 42 43 44 45 46 47 Next › Last »

<deleted-account> commented on 2014-01-28 04:07 (UTC)

Great >.> I wrote a very long explanation and then pressed F5. Sorry, it'll keep it short this time: It isn't included, because it can't be installed system-wide. Every seahub folder can only be used with exactly one seafile server while the binaries produces by this package can be used by as many instances of seafile as you want (no binary blob duplication). As far as I am aware, that's an explicit design decision on their part, which makes it impossible for us to package seahub (as pacman install packages system-wide). Regarding the update: Yes and Nope, upstream version is technically still 2.1.3. 2.1.4 is the testing version (as indicated by the "-testing" suffix). The seafile developers tend to push binaries before sources.

diensthunds commented on 2014-01-28 01:47 (UTC)

Latest upstream version has bumped up to 2.1.4

diensthunds commented on 2014-01-27 21:12 (UTC)

The first comment wasn't worded the way I wanted to get the info across. I didn't install seahub as I still don't understand why it wasn't included in the package, if you do the download from the actual website everything is included and you can set up from there. I don't mind fidling and even had to do that from the official web sites download. I've read through the wiki link you provided and it still seams that you have to do both download the official package to use as a setup and the aur package just to install the binaries. This seems sort of redundant.

<deleted-account> commented on 2014-01-27 10:03 (UTC)

Apparently I was wrong about the missing work-in-progess marking. I've added a new page "Seafile" to the ArchWik. It currently contains the minimal information you should require to setup seafile-server successfully: https://wiki.archlinux.org/index.php/Seafile

<deleted-account> commented on 2014-01-27 09:46 (UTC)

Apparently I was wrong about the missing work-in-progess marking. I'll post a link to the soon-to-be-online wiki page here.

<deleted-account> commented on 2014-01-27 07:50 (UTC)

@diensthund: Also, you seem to have deleted your first post (which requires information needed to understand your second one correctly), so I'll keep the response to that short: The instructions from the seafile-wiki do work if you simply omit the parts that don't apply (and change some of the paths to where this package installs to). It's not overly hard (this is Archlinux, not Ubuntu, so a certain level of manual fiddling and tweaking shold be expected), but I understand that a wiki page entry towards that end would help. But as I said before, the ArchWiki does not have an option (that I could find) to mark a new page as (work-in-progress), so I need to have the entire page in tip-top shape before posting it there in the first place. Here is a (very) early prototype, that contains ALL the commands necessary to setup seafile server on Arch: http://pastebin.com/raw.php?i=yk0g1QHW

<deleted-account> commented on 2014-01-27 07:36 (UTC)

@diensthunds: Have you followed the sseafile setup guidelines? Because it sounds to me like you did not install seahub, so I'll repost my second-to-last post here again, as it contains all the info you should need: You essentially follow the seafile guide from this point onwards to setup seafile (leaving out the parts that don't apply): https://github.com/haiwen/seafile/wiki/Build%20and%20Deploy%20Seafile%20Server%20from%20source#prepare-the-directory-layout You won't have/setup the "src" subdirectory as everything but seahub was installed at system-level. To get the latest seahub version you look at the git tags here https://github.com/haiwen/seahub/tags and select the one matching with package's version, e.g. right now "v2.1.3-server" and download it, set it up in the directory layout described in the first link, and finally do the "seafile-admin setup" stuff. When upgrading, you follow this: https://github.com/haiwen/seafile/wiki/Build%20and%20Deploy%20Seafile%20Server%20from%20source#upgrade-the-seafile-server Also, the upgrade scripts are installed by this package under "/usr/share/seafile-server/upgrade", so use that instead of "seafile-{version}/scripts/upgrade" in the cp -rf line when upgrading.

diensthunds commented on 2014-01-27 03:41 (UTC)

seafile-admin setup gives Error: "seafile-server/seahub/" not found. Please download seahub first. systemctl start seafile gives Failed to issue method call: unit seafile.service failed to load: No such file or directory I'm stuck now not being able to get seafile to run or even setup.

<deleted-account> commented on 2014-01-27 02:03 (UTC)

I have the seafile-server working on x86_64 Arch exactly with these PKGBUILDs here. Regarding updating, if you haven't already, you could look at the links from my last post. The proper procedure is in short: 1) Stop the seafile server 2) Update seafile-server package 3) Update seahub (manually) 4) Run upgrade scripts (manually, they get put into /usr/share/seafile-server/upgrade) 5) Attempt to start the seafile server again I do not know why you needed to install the captcha module, because I have had no problems so far with this version (that includes the seafile-server package and the manually setup seahub). Did you perhaps change any options (e.g. activate a feature) that would require it? Also, that log dosen't look complete to me (I can't see any actual error, just the middle of the trace), so I can't help you there. If you're using x86 or x86_64, my best guess would be that there's something not quite right with your nginx config for seahub; I can't comment on what might be wrong for ARM, but there were users who confirmed that it works like this there. I'm sorry I can' be of much more help here, but you might want to open an issue with the seafile developers (here: https://github.com/haiwen/seafile/issues?state=open). If you to find some problem with the PKGBUILD I'd be happy to include a fix, but as it stands right now, I can't reproduce your problems.

« First ‹ Previous 1 .. 38 39 40 41 42 43 44 45 46 47 Next › Last »