Package Details: seafile 8.0.4-1

Git Clone URL: (read-only, click to copy)
Package Base: seafile
Description: An online file storage and collaboration tool
Upstream URL:
Licenses: GPL2
Conflicts: seafile-server
Provides: seafile-client-cli
Submitter: eolianoe
Maintainer: Joffrey
Last Packager: Joffrey
Votes: 114
Popularity: 1.52
First Submitted: 2016-08-11 16:38
Last Updated: 2021-10-08 20:13

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

tovo commented on 2019-10-02 07:39

Hi folks,

I'm trying to install seafile 7.0.2-1 as a dependancy of seafile-client but it fails with the following message:

==> Validating source files with sha256sums...

seafile-7.0.2.tar.gz ... FAILED ... Passed

seaf-cli@.service ... Passed

==> ERROR: One or more files did not pass the validity check!

==> ERROR: Makepkg was unable to build seafile.

It seems that the archive signature is wrong. How to fix it?


mqs commented on 2019-08-16 13:05

@hakunamenta I just compiled it again and it works now... I assume that libevent got updated...

see seafile-client where people got the same problem

hakunamenta commented on 2019-08-16 11:32

got % seaf-cli start

Starting seafile daemon ...

seaf-daemon: error while loading shared libraries: cannot open shared object file: No such file or directory

fixed with ln -rs /usr/lib/ /usr/lib/

is this a problem with seafile or with libevent?

h44z commented on 2019-07-12 22:53

@eolianoe: I have updated this package to version 7.0.1. Find the updated PKGBUILD and .SRCINFO here:

I also updated the seafile-client, seafile-server and ccnet-server packages.

tilx commented on 2019-06-04 18:21

The sha256 hash check for 6.2.11 is still failing.

==> Validating source files with sha256sums... seafile-6.2.11.tar.gz ... FAILED

Not sure why. The tagged commit on github says it is from 2019-01-17, while the package update here happened on 2019-03-10. Is the tarball on Github changing independently from the tagged commit? Or is it possible to mess with commit dates and repo history, even for verified commits? Did the checksum work for anybody before @yayel59's comment from 2019-04-19?

yayel59 commented on 2019-04-10 09:46

The sha256sums failed for seafile-6.2.11.tar.gz.

Joffrey commented on 2019-03-03 14:27

@windowsbomb, yes you can use a chroot, a container, a virtual machine... I think Docker is the most practice. But if you use only a machine, I have never used that, "Seadrive" is maybe sufficient (or simply the WEBUI).

Edit: Or a mount point with your filemanager and Webdav..

windowsbomb commented on 2019-03-03 10:23

@Joffrey, thanks for the reply. So, is there any other way that I can install both the server and the client on a same PC?

Joffrey commented on 2019-03-02 14:05

@windowsbomb, you'll not be able to force the installation, look that.

windowsbomb commented on 2019-03-02 11:23

I'm a poor student and I don't have another PC to run the server. So it will be economically for me to install both seafile-server and seafile-client on a same PC. It seems that the conflict between seafile and seafile-server has been "deprecated" since 9 Nov 2018( However, the latest version seafile-6.2.9 and seafile-server-6.3.4-2 in aur repository are still conflict with each other. So is the conflict really solved? For now, can I ignore the conflict and install both seafile and seafile-server by force?