| Git Clone URL: | https://aur.archlinux.org/seafile.git (read-only) |
|---|---|
| Package Base: | seafile |
| Description: | Seafile is an online file storage and collaboration tool |
| Upstream URL: | https://github.com/haiwen/seafile |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | eolianoe |
| Maintainer: | eolianoe (fordprefect, thealchemist, Joffrey) |
| Last Packager: | Joffrey |
| Votes: | 103 |
| Popularity: | 0.637830 |
| First Submitted: | 2016-08-11 16:38 |
| Last Updated: | 2019-08-20 16:37 |
@tovo, yeah...apparently the sha256 sum of the https://github.com/haiwen/seafile/archive/v7.0.2.tar.gz changed again, to: 2424b303fa826321affad0f23341ac46ca085c895f3d6e1345e9b43dc13c2ab3
So this has to be updated in the PKBUILD file. I changed it myself in pamac, before clicking install (or 'apply') then it builds.
@FuelFlo: my workaround is to use seafile-git and seafile-client-git instead.
Yeah, same here... =/
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
libseafile.in.patch ... 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?
Cheers
@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
got % seaf-cli start
Starting seafile daemon ...
seaf-daemon: error while loading shared libraries: libevent-2.1.so.6: cannot open shared object file: No such file or directory
fixed with ln -rs /usr/lib/libevent-2.1.so.7.0.0 /usr/lib/libevent-2.1.so.6
is this a problem with seafile or with libevent?
@eolianoe: I have updated this package to version 7.0.1. Find the updated PKGBUILD and .SRCINFO here: https://drive.google.com/open?id=1xcw0y7qyQ2H7aawHD58oq4XrMVj1vtuZ
I also updated the seafile-client, seafile-server and ccnet-server packages.
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?
The sha256sums failed for seafile-6.2.11.tar.gz.
@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..
Pinned Comments
eolianoe commented on 2018-07-03 20:29
If the checksums are wrong, the reason is here: https://github.com/haiwen/seafile-server/issues/27. This time I released the PKGBUILD to early and will wait for the final announcement to fix the checksums (in the meantime you can ignore them)