Package Details: seafile-client 9.0.13-2

Git Clone URL: https://aur.archlinux.org/seafile-client.git (read-only, click to copy)
Package Base: seafile-client
Description: GUI client for synchronizing your local files with seafile server
Upstream URL: https://github.com/haiwen/seafile-client
Licenses: Apache
Submitter: Localizator
Maintainer: Joffrey
Last Packager: Joffrey
Votes: 168
Popularity: 0.000000
First Submitted: 2012-12-10 17:34 (UTC)
Last Updated: 2025-04-05 18:40 (UTC)

Pinned Comments

Joffrey commented on 2021-05-30 20:06 (UTC) (edited on 2021-05-30 20:11 (UTC) by Joffrey)

Please, when you have compilation or execution errors, recompile each component without using an AUR helper before reporting an issue.

Latest Comments

« First ‹ Previous 1 .. 33 34 35 36 37 38 39 40 41 42 43 44 Next › Last »

<deleted-account> commented on 2014-12-03 12:54 (UTC)

@monochromec: See my reply at the URL you linked from 2014-12-03 12:48.

monochromec commented on 2014-12-03 07:43 (UTC)

Noticed an SIGILL issue on an armv7h on both the server and client side. Comment on the server page contains a workaround (https://aur.archlinux.org/packages/seafile-server).

Rook commented on 2014-12-01 16:14 (UTC)

4.0.2 has been released (2014/11/29) : [fix] Fix bugs in syncing with HTTP protocol

issue commented on 2014-11-18 17:26 (UTC)

4.0.1 was just released, fixes the previous segfault aswell

shimi commented on 2014-11-18 15:40 (UTC)

@Perry3D that works, thanks.

Perry3D commented on 2014-11-18 14:11 (UTC)

@shimi: I got the same error. After recompiling seafile-shared and seafile-client it works.

shimi commented on 2014-11-17 17:28 (UTC)

I'm getting this error when trying to run the applet, any ideas? (seafile-applet:9929): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion 'instance != NULL && instance->g_class != NULL' failed fish: Job 1, “seafile-applet ” terminated by signal SIGSEGV (Address boundary error)

<deleted-account> commented on 2014-11-12 16:13 (UTC)

@gnumdk: It was properly released as stable: https://github.com/haiwen/seafile-client/tags By the upstream developers' own convention, stable released have no additional suffix and beta released have the "-testing" suffix. While one upstream developer did afterwards say that 4.0 is still in beta, they have not yet removed the stable tag for it, so upstream (as a whole) has two contradictory statements (if it truly is purely a beta release, they should have renamed the stable tag after noticing the wrong naming - even if this introduces a temporary hassle for people who already pulled the changes). The statement I chose to follow is the release of a properly versioned, stable tarball by their own convention.

<deleted-account> commented on 2014-11-12 16:12 (UTC)

@gnumdk: It was properly released as stable: https://github.com/haiwen/seafile-client/tags By the upstream developer's own convention, stable released have no additional suffix and beta released have the "-testing" suffix. While one upstream developer did afterwards say that 4.0 is still in beta, they have not yet removed the stable tag for it, so upstream (as a whole) has two contradictory statements (if it truly is purely a beta release, they should have renamed the stable tag after noticing the wrong naming - even if this introduces a temporary hassle for people who already pulled the changes). The statement I chose to follow is the release of a properly versioned, stable tarball by their own convention.

gnumdk commented on 2014-11-12 14:51 (UTC)

Seafile 4 is a beta version!

« First ‹ Previous 1 .. 33 34 35 36 37 38 39 40 41 42 43 44 Next › Last »