Package Details: seafile 9.0.11-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: 111
Popularity: 0.000000
First Submitted: 2016-08-11 16:38 (UTC)
Last Updated: 2024-11-14 17:06 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 47 Next › Last »

mertemba commented on 2015-03-20 20:07 (UTC)

@MadMe: Syncing (up and down) works for me on linux. My ccnet.log is as follows: [03/20/15 21:00:07] ../common/session.c(432): socket file exists, delete it anyway [03/20/15 21:00:07] ../common/session.c(461): Listen on /srv/seafile/ccnet/ccnet.sock for local clients [03/20/15 21:00:07] ../common/session.c(267): Update pubinfo file [03/20/15 21:00:07] ../common/connect-mgr.c(515): Opened port 10001 to listen for incoming peer connections [03/20/15 21:00:08] ../common/session.c(375): Accepted a local client

MadMe commented on 2015-03-20 19:11 (UTC)

in the ccnet.log of the client i found this: [03/20/15 20:05:55] ../common/processors/rcvcmd-proc.c(492): Add server a28d84vc mydomain.myfritz.net:10001 [03/20/15 20:05:55] ../common/connect-mgr.c(364): [Conn] Start outgoing connect to (null)(a28d84vc39) 85.88.88.47:10001 [03/20/15 20:06:05] ../common/connect-mgr.c(220): [Conn] peer (null)(a28d84vc39) connection fails I think the client shouldnt see the port? a little bit strange for me. (i'm using nginx with https)

MadMe commented on 2015-03-20 19:02 (UTC)

Downloading works like a charm... But syncing wont... with linux an windows... can somebody confirm this? Maybe i killed something in my config as i thought the download problem was there hidden...

<deleted-account> commented on 2015-03-20 13:58 (UTC)

@calrama: That is strange. In any case, thank you for the information, I have updated seafile-server and libevhtp-seafile appropriately, so it should work now.

mertemba commented on 2015-03-20 13:52 (UTC)

I tried a few more things, and apparently the issue is caused by libevhtp 1.2.10. When using libevhtp 1.2.9 downloads work as expected (no difference if using seafile 4.0.5 or 4.0.6).

<deleted-account> commented on 2015-03-20 13:05 (UTC)

@jellysheep: No problem, I just wanted to clarify it. There were no changes from 4.0.5 to 4.0.6 in terms of the PKGBUILD (other than updating version and checksums) that I can remember. If you mean upstream: I am not aware of any.

mertemba commented on 2015-03-20 13:02 (UTC)

@calrama: It is funny that you found my bug report. :) I reopened it as you suggested. Though sorry for blaming your starting script. Were there any packaging/deploying changes introduced from 4.0.5 to 4.0.6? @Varakh: Yeah, this way it works for me, too, I also wrote a systemd service for this. :) Though it does not solve the issue itself, and btw there is a huge difference between installing a binary package from 3rd party site vs. compiling it from source.

Varakh commented on 2015-03-20 12:33 (UTC)

I gave up on this long ago and installed seafile from the website. This did work out of the box. Having this as a package might be easier, but there is nearly no difference when you update it manually: - pkg upgrade = wget :-) - stop server(s) = same thing - execute upgrade scripts = same thing For starting it with systemd: google provides some information on service files. Very easy to have this done manually and avoid problems regarding the predefined aur package here.

<deleted-account> commented on 2015-03-20 12:12 (UTC)

@jellysheep: Thanks for the information about seaf-server not responding. Unfortunately I do not know why, but I suspect there is something wrong with the way this package builds seafile (though I currently do not know what). Also, I found your github issue about this and using seafile-admin is not a faulty way to start seafile. This is the way the manual states[1] you should start self-compiled seafile server instances (not from the binary distribution). In any case, you may want to reopen that issue, I shall investigate further. [1] http://manual.seafile.com/build_seafile/server.html

mertemba commented on 2015-03-20 11:47 (UTC)

Apparently the seafile fileserver (listening on port 8082) does not respond at all. With the binary package downloadable on seafile.com this is not the case. Any ideas?

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 47 Next › Last »