Package Details: seafile 9.0.12-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-02-18 17:52 (UTC)

Pinned Comments

Latest Comments

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

<deleted-account> commented on 2014-04-24 12:45 (UTC)

That is strange. Did you follow this update procedure? 1. Stop seafile-server 2. Update the seafile-server package 3. Download newest seahub and run the upgrade scripts 4. Try to start seafile-server If so, you might want to remove all the related packages and rebuild and install from scratch (this shouldn't touch your libraries) in this order: libsearpc, ccnet, seafile-shared, seafile-server. If neither helps, I don't know what could be the problem, as it works for me. But if you find something wrong in any of the PGKBUILDs that just didn't trigger in my tests, I'll try to fix it.

BunBum commented on 2014-04-24 12:36 (UTC)

After some re-installs, restarts, re-syncs and so on it seems to work now with the local client. Only the webinterface gives me a "Page unavailable" if I want to open a library. Strange...

BunBum commented on 2014-04-24 11:57 (UTC)

Since the last update my seafile installation is not working anymore. I don't know if it was the latest seafile-shared or the latest seafile-server update. I also tried a completely fresh new installation of everything (including the latets seahub v2.2.1-server). No success. I can open the seahub webinterface and I can login. But if I open a library I get a "Page unavailable". My local installed seafile client also tells me a "server error" but nothing more.

<deleted-account> commented on 2014-04-22 19:25 (UTC)

So was I, but dealing with it is a lot less work than trying to get them to follow a consistent release process and clear versioning, because it would involve getting them a build master and eliminating the seafile repo, replacing it with two new repos, one for the shared components and one for the actual server. They also need to overhaul the design of seahub, because it prevents it from being distribution packaged.

BunBum commented on 2014-04-22 19:17 (UTC)

Ok thank you for clarification. I'm going crazy with their versioning! ;-)

<deleted-account> commented on 2014-04-22 19:14 (UTC)

Please have a closer look. Server tags contain the keyword "server". All tags not containing "server" have nothing to do with the server component, but with the shared components between server and client, which the client 3.*.* release needs (and I'll update the client packages tomorrow). I specifically stated > The 3.*.* tags are all either for testing, or client-specific which is the case.

BunBum commented on 2014-04-22 19:11 (UTC)

That's not true. I can see a 3.0.2 tag. Without any testing. See here: https://github.com/haiwen/seafile/releases/tag/v3.0.2 But I don't know the difference between the 2.* branch and 3.*...

<deleted-account> commented on 2014-04-22 19:07 (UTC)

I don't really understand the point of your question, as there's no version later than 2.2.1 officially released for the server: https://github.com/haiwen/seafile/tags The 3.*.* tags are all either for testing, or client-specific. If there's a new version released, I'll update the package, as I've done up till now.

BunBum commented on 2014-04-22 18:37 (UTC)

Are there any update plans to version 3.0.*?

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