Package Details: seafile-client 9.0.11-1

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: 2024-11-14 17:07 (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 »

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!

<deleted-account> commented on 2014-10-31 00:09 (UTC)

@alinmear: If the package has been flagged out of date, then I have been notified of it. If the package remains flagged (that is, I don't unflag it because of an invalid flagging) I will update it when I have the necessary time to test it. Please wait with reminders about it until the end of the following weekend, since it is quite possible that I cannot make the necessary time on the weekdays. I have now - as an exception - updated the packages without testing them to accomodate you this time.

alinmear commented on 2014-10-30 12:23 (UTC)

@calrama. Please update the pkgver=3.1.8! we also need to update the seafile-shared! i uploaded the updated PKGBUILDs as GIST: https://gist.github.com/anonymous/50a36bbdfec30cc83c13

<deleted-account> commented on 2014-10-04 10:07 (UTC)

@jpambrun: The perspective to be used here is a source-based (not binary based !) non-beta build script for a FLOSS (or at least a seemingly so) development project (seafile client), in which stable releases have been marked by providing source archive files for long enough for that to have become the de facto standard (both in FLOSS generally and in seafile specifically). Marking this package as out-of-date - if there is no stable release archive newer than the currently used one - is incorrect, since it cannot be updated without such an archive without becomimg broken. With that being said, the devs from seafile "forget" to do this on a regular basis - on average every third release or so (estimation based on memory) - and when reminded it can appear anywhere between a couple of minutes to a couple of weeks later, but with no shown intention of fixing their imho problematic release procedure. You might want to create a github issue there about the missing tag if you wish, or alternatively create a seafile-client-beta package and use their testing tags (which are pretty much always there the way you expect). For references to my claims you can look hat this packages comment history. It will support the pattern.

jpambrun commented on 2014-10-04 01:26 (UTC)

@calrama: "incorrectly" is a question of perspective; the release was announced on their twitter account on sept 27 and binaries are available for all platforms on their web site since then. They obviously just forgot to create another git tag.

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