@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
Search Criteria
Package Details: seafile 9.0.5-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-03-05 17:47 (UTC) |
Dependencies (8)
- fuse (fuse2)
- libevent (libevent-gitAUR)
- libsearpcAUR
- libwebsockets
- python-future
- sqlite (sqlite-fossilAUR)
- intltool (make)
- vala (vala-gitAUR) (make)
Required by (3)
Sources (2)
mqs commented on 2019-08-16 13:05 (UTC)
hakunamenta commented on 2019-08-16 11:32 (UTC) (edited on 2019-08-16 11:33 (UTC) by hakunamenta)
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?
h44z commented on 2019-07-12 22:53 (UTC)
@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.
tilx commented on 2019-06-04 18:21 (UTC)
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 (UTC)
The sha256sums failed for seafile-6.2.11.tar.gz.
Joffrey commented on 2019-03-03 14:27 (UTC) (edited on 2019-03-03 14:53 (UTC) by Joffrey)
@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 (UTC)
@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 (UTC)
@windowsbomb, you'll not be able to force the installation, look that.
windowsbomb commented on 2019-03-02 11:23 (UTC)
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(https://github.com/haiwen/seafile/issues/1766). 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?
Pinned Comments