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 .. 36 37 38 39 40 41 42 43 44 Next › Last »

kevincox commented on 2013-11-04 21:26 (UTC)

That's good to have the new Qt applet (the web one kinda sucked TBH) however I get the following error when starting seafile-applet. $ seafile-applet seafile-applet: error while loading shared libraries: libseafile.so.0: cannot open shared object file: No such file or directory

<deleted-account> commented on 2013-10-30 20:38 (UTC)

This package has now been changed to use the new Qt-based seafile-client, as the old one is going to be dropped soon (see the discussion on this issue: https://github.com/haiwen/seafile/issues/406). However, the new client in the seafile-client repository depends on some of the shared core components of seafile, which were previously part of this package; these have been moved out to the seafile-shared package, as they aren't really part of the actual client.

<deleted-account> commented on 2013-08-20 09:31 (UTC)

Thanks for the info, you might simply want to flag out-of-date next time (I've done it this time), though, as that produces less comments (which people have to look through if for some reason the package doesn't work for them). Once ccnet is updated to use 1.8.0 I'll update this.

<deleted-account> commented on 2013-08-20 09:30 (UTC)

Thanks for the info, you might simply want to flag out-of-date next time, though, as that produces less comments (which people have to look through if for some reason the package doesn't work for them). Once ccnet is updated to use 1.8.0 I'll update this.

<deleted-account> commented on 2013-08-20 04:39 (UTC)

Version 1.8.0 is out. I've updated the PKGBUILD here: http://pastebin.com/7x67pFQj I stripped out the sha sums out of pure laziness, sorry about that.

<deleted-account> commented on 2013-08-04 12:06 (UTC)

> Why don't you use the source-releases from https://github.com/haiwen/seafile/releases > They provide a "zip" Download-Link for each tagged release. (1) Because the ccnet package doesn't do it and seafile-client depends on it (2) Because haiwen's tagging is arbitrary and not done in the usual clear way (i.e. only the version number, no extras). > The current package builds, but the web-interface of seafile has a python-error when you click any link in it: I cannot reproduce that error on any of my machines (x86_64 VirtualBox VM, x86_64 Native, i686 Native). The package builds on all of them and I can use all settings / click all links in the web-interface of seafile-client, as well as download / synchronize my libraries with my private server running the seafile server (from the AUR package seafile). Sorry, but I don't know how to help you here.

<deleted-account> commented on 2013-08-04 10:01 (UTC)

(sorry for the many edits, i thought it would work now, but it doesn't) The current package builds, but the web-interface of seafile has a python-error when you click any link in it: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/web/wsgiserver/__init__.py", line 1245, in communicate req.respond() [...] File "/usr/lib/python2.7/site-packages/web/httpserver.py", line 319, in log print >> outfile, utils.safestr(msg) IOError: [Errno 5] Input/output error

<deleted-account> commented on 2013-08-04 09:53 (UTC)

Why don't you use the source-releases from https://github.com/haiwen/seafile/releases They provide a "zip" Download-Link for each tagged release.

<deleted-account> commented on 2013-07-08 12:42 (UTC)

Until now, I've written emails, but I'll write it here once for reference: 1) Seafile gets (at the moment) released here: https://code.google.com/p/seafile/downloads/list 2) Binaries for Seafile are currently released before source tarballs 3) There's no point in flagging seafile-client out-of-date *until* these source tarballs become available, even if new binaries have been released because without the source tarballs, this package cannot be built. Example: At the moment of me writing this comment the latest released source tarball is version 1.7.1 (as is this package), while the latest released binaries are 1.7.3 (they were released two days prior). I cannot update seafile-client to 1.7.3 until i) the source tarball for 1.7.3 gets released (which usually takes a couple of days) ii) the ccnet package gets updated, as usually both get changes that make compiling the client without the exact proper ccnet version not possible. It is sensbile to flag seafile-client out of date as soon as you notice i) and I'll push the new PKGBUILD when notice ii) (and have the time)

<deleted-account> commented on 2013-06-24 12:24 (UTC)

Thanks for flagging out of date, but please don't flag out of date AND comment about it unless the comment has important info, as it sends two mails about the same issue with the same amount of information in them.

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