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 .. 20 21 22 23 24 25 26 27 28 29 30 .. 47 Next › Last »

<deleted-account> commented on 2015-05-01 18:22 (UTC)

@Almin It worked without any issues for me, did you follow the steps mentioned here[1]. If so, this sounds like a problem for upstream. [1] https://wiki.archlinux.org/index.php/Seafile#Upgrading

Almin commented on 2015-04-28 16:07 (UTC)

Hey guys, upgrading to 4.1.2, running the script, throws an error: ------------------------------------------------------------- This script would upgrade your seafile server from 4.0 to 4.1 Press [ENTER] to contiune ------------------------------------------------------------- Done Updating seafile/seahub database ... [INFO] You are using SQLite3 [INFO] updating seafile database... Traceback (most recent call last): File "/srv/seafile/cubietruck/seafile-server/upgrade/db_update_helper.py", line 329, in <module> main() File "/srv/seafile/cubietruck/seafile-server/upgrade/db_update_helper.py", line 324, in main db_updater.update_db() File "/srv/seafile/cubietruck/seafile-server/upgrade/db_update_helper.py", line 238, in update_db self.update_ccnet_sql(sql_path) File "/srv/seafile/cubietruck/seafile-server/upgrade/db_update_helper.py", line 254, in update_ccnet_sql self.apply_sqls(self.ccnet_db.get_db(dbname), sql_path) File "/srv/seafile/cubietruck/seafile-server/upgrade/db_update_helper.py", line 250, in apply_sqls conn.execute(line) sqlite3.OperationalError: duplicate column name: type Failed to upgrade your database

minus commented on 2015-04-24 13:11 (UTC)

Manually updated to 4.1.2, seems to work, haven't taken a closer look though.

HalosGhost commented on 2015-04-09 17:43 (UTC)

Hello there! Any word on the update to 4.1.x? You've already updated the -shared which makes me think there is a problem with the server? If so, is there anything I can do to help? All the best,

MadMe commented on 2015-03-25 20:04 (UTC)

@danboid A little bit more information would be helpfull... are you using ssl(https)? if yes how did you create the Certificate? How looks your configuration files?(ccnet.conf;seahub_settings.py;nginx.conf[i only used nginx... never used apache]) you have only with the original build for Raspian from the official Download the seahub.sh... So with the package from the Arch Linux you have "seafile-admin" If you wanna start the Server manually: "seafile-admin start --fastcgi" I also build my copy with yaourt. and yes the binaries are no option. But i think this is the wrong place for support you should maybe start a Thread in the forum.

danboid commented on 2015-03-24 16:23 (UTC)

I'm having the same prob as Almin w/ v4.0.6. I can sync and upload with the desktop client and I can login to the web interface but I can't upload or download anything via the web interface. I have tried with both nginx and Apache with the same result - I get a gateway error if anything happens at all. Two suspicious points I've noted that I can't find any reference to are that the web interface and client don't work at all when started with --fastcgi in the systemd script with both nginx and apache. Also, numerous docs make reference to starting seahub with seahub.sh but there is no such script in my installation. I built it using yaourt under ArchARM so I expect using official binaries isn't an option. I'm also disappointed that it seems there is no way to access older versions of files using the GUI desktop client. Thanks for your help!

MadMe commented on 2015-03-23 22:52 (UTC)

@Almin the config files are correct? i guess you will use ssl... Upload works over the web frontend? in seahub_settings.py must be FILE_SERVER_ROOT = 'https://my.domain.net:PORTNUMBER/seafhttp' (dont forget your port and the s in https) and in ccnet/ccnet.conf there must also be the correct line: SERVICE_URL = https://my.domain.net:PORTNUMBER

Almin commented on 2015-03-22 14:59 (UTC)

Hmm... sadly still doesn't work for me. It runs, it syncs desktop clients, but not mobile ones. Downloading from the web frontend also doesn't work.

MadMe commented on 2015-03-22 13:57 (UTC)

Ok i don't know why it worked with a new instance. but it seems like i messed up with the ssl stuff... A New ssl certificate and it works very well:) sorry for spaming :-/ And Thanx for your Help :-D Everything works now really nice for me :-D

MadMe commented on 2015-03-22 09:10 (UTC)

It works with a new instance... With my old instance the client stuck on Connecting to server... Is there a way to debug it?the logs don't say much...

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