I'm using this sha256sum 50d117db2ebde2704cb1a327cf40a4bf6770637497d3bd4c4788a6db40f862cb and it works.
Search Criteria
Package Details: seafile 9.0.11-1
Package Actions
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) |
Dependencies (8)
- fuse (fuse2)
- libevent (libevent-gitAUR)
- libsearpcAUR
- libwebsockets
- python-future
- sqlite (sqlite-fossilAUR)
- intltool (make)
- vala (vala-gitAUR) (make)
Required by (2)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 47 Next › Last »
leocmpro commented on 2018-07-06 15:49 (UTC)
eolianoe commented on 2018-07-04 17:27 (UTC)
@FuelFlo: yes, you just need to use a previous commit (for instance c85dc7a
)
FuelFlo commented on 2018-07-04 14:08 (UTC)
All right, thought there was something wrong. Thx for the work! Is there any way to go back to 6.1.8. with the AUR until 6.2.0 is officially released?
eolianoe commented on 2018-07-03 20:29 (UTC)
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)
j0hannes commented on 2018-07-02 10:28 (UTC)
The checksums are wrong:
seafile-6.2.0.tar.gz ... FAILED
a-bostaurus commented on 2017-05-28 07:36 (UTC)
@hopimet Your advice "You need to re-install seafile-client (not seafile). Then the package will re-compile against the new version of openssl." helped. Great! Thanks a lot!
hopimet commented on 2017-05-27 18:03 (UTC)
@a-bostaurus
You need to re-install seafile-client (not seafile). Then the package will re-compile against the new version of openssl.
a-bostaurus commented on 2017-05-27 14:45 (UTC)
@fbis251 What I tried to do was reinstall, but that did not help.If recompile is something different, I ask you to explain the steps of recompiling to me, because I don't know them.
My system is: 4.11.3-1-MANJARO #1 SMP PREEMPT Thu May 25 20:44:21 UTC 2017 x86_64 GNU/Linux
fbis251 commented on 2017-05-27 13:49 (UTC)
@a-bostaurus You need to recompile the packages and it'll run
a-bostaurus commented on 2017-05-27 13:48 (UTC)
After last update seafile does not work anymore. When I try to launch via terminal it is said: "/usr/bin/seafile-applet
/usr/bin/seafile-applet: /usr/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.2d' not found (required by /usr/bin/seafile-applet)".
Pinned Comments