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

<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.

<deleted-account> commented on 2013-06-24 12:17 (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.

oliver_aur commented on 2013-06-22 12:58 (UTC)

thanks. Looks good now

<deleted-account> commented on 2013-06-21 22:32 (UTC)

Technically, that shouldn't happen, because the python binary gets explicitly set to python2 when configuring (see the ./configure line in the PKGBUILD), so I'd say that this is a bug in upstream; I've included a patch to take care of that for now.

oliver_aur commented on 2013-06-21 22:14 (UTC)

The first line of /usr/bin/seaf-cli needs to be updated in order to successfully run The generic installed version (#!/usr/bin/env python) gives me the following: $ seaf-cli status File "/sbin/seaf-cli", line 105 print "%s not found in PATH. Have you installed seafile?" % prog ^ SyntaxError: invalid syntax If I modify it to be #!/usr/bin/env python2 it works $ seaf-cli status # Name Status Progress # Name Status conf_files synchronized Is there some fancy way I'm missing that enables the correct version of python to be selected without modifying the packaged file?

<deleted-account> commented on 2013-03-07 11:33 (UTC)

I will (as in can only when) update this when ccnet has been updated.

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