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 .. 29 30 31 32 33 34 35 36 37 38 39 .. 47 Next › Last »

dev_arch commented on 2014-07-11 11:22 (UTC)

@calrama: This works, full functionality again. Thank you!

BunBum commented on 2014-07-11 05:40 (UTC)

@calrama you should add this to the wiki ;-)

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

NOTICE: Since some of the dependencies are not currently available in this form in the AUR, here is a list of what you need to get this package running properly right now, and one possible way to obtain them: [gunicorn-python2 == 18.0] Package location: http://pkgbuild.com/git/aur-mirror.git/tree/gunicorn-python2?id=57609a11cc6f21064223e0957e48b9009451619b [python2-djblets] Package location: http://pkgbuild.com/git/aur-mirror.git/tree/python2-djblets?id=b0aaf90aeebdfe73e9a4030f47a587c99512d79b

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

@dev_arch: I was able to reproduce the error on a clean Virtualbox VM and now I know why I never encountered it: it only happens when you start your server without --fastcgi (which I've never done before, since I use seafile behind nginx), because gunicorn is only used when starting that way. Since the problem seemed to be with something relating to gunicorn, I tried looking into the responsible package's[1] past, which lead me to a marvelous page[2] that seems to mirror the AUR with git on a daily basis. There I found that gunicorn-python2 was recently updated from 18.0 to 19.0[3] and inspecting this update revealed that the "gunicorn_django-python2" command was completely removed without substitution from gunicorn[4]. Apparently, seafile(-server) depends on version <=18.0 of gunicorn-python2, which is why I changed the depencency accordingly (although I made it == 18.0). I may make the dependency on gunicorn-python2 optional when I have has time to look at it more, but for now, it stays as it is (mandatory, version 18.0). tl;dr: It's working, see my next post for what you need. [1] https://aur.archlinux.org/packages/gunicorn-python2/ [2] http://pkgbuild.com/git/aur-mirror.git/tree/ [3] http://pkgbuild.com/git/aur-mirror.git/log/gunicorn-python2/PKGBUILD [4] http://pkgbuild.com/git/aur-mirror.git/commit/gunicorn-python2/PKGBUILD?id=b663f35cb02c00bb776eb82680ec1c0a736db9a8

dev_arch commented on 2014-07-10 19:05 (UTC)

@calrama (back from having been away a few days) I just finished installing seafile-server 3.0.4 on a clean Arch install in VirtualBox. To my surprise this yielded the same result. I used yaourt and could try once more manually but doubt it will give any difference. I took python2-djblets-0.8.2-1-x86_64.pkg.tar.xz and django-pipeline-1.3.24-1-any.pkg.tar.xz from the box that initially showed this problem. Could the problem lie with either of those? It might not be just me after all. I am however quickly running out of clues now and any new idea will be gracefully accepted. :-)

<deleted-account> commented on 2014-07-06 22:52 (UTC)

@dev_arch: Hm, ok. Installing the 3.0.3 version of seafile-server should be as simple as getting all the relevant dependencies (libsearpc, ccnet, seafile-shared), changing all 3.0.4 to 3.0.3, calling makepkg -s with skip checksum (or change them yourself), and installing them one by one. I'm not sure whether downgrading seahub will work, but I'd suggest using the minor upgrade script. Sorry I'm not able to help more, but I do not keep any binaries cached (I use yaourt).

dev_arch commented on 2014-07-06 19:44 (UTC)

@calrama: No joy (I cheated with yaourt though, does that count? My evening draws to a close) > The dependency `django-pipeline` demands version `>=1.3.23`but the most recent version is `1.2.24-1`. This came before re-installing django-pipeline so maybe not that strange after all. Aura has a known glitch, related to the changes in AUR, which does manifest itself on this machine (and not my pc): https://github.com/aurapm/aura/issues/246#issuecomment-48098404 I shouldn't have removed version 3.0.3 from my cache, maybe a fresh install with that works. Do you know where to find that or can you provide me with it? Soon I might be in luck with the next version, maybe with rumpelsepp's initiative.

<deleted-account> commented on 2014-07-06 18:35 (UTC)

@dev_arch: Damn, that's a lot of data. But more to the point: Could you try not using aura for the building, but doing it manually (i.e. download the source tarball, unpack it, run makepkg -s, and install, respective for all the dependencies, - except with djblets, of course)? Because if you installed django-pipeline with the PKGBUILD I posted, then you should have django-pipeline == 1.3.24 installed and aura's complaint makes no sense whatsoever to me. > Installing collected packages: django > Found existing installation: Django 1.6.5 > Not uninstalling Django at /usr/lib/python2.7/site-packages, outside environment /usr/lib/seafile/seafileenv > Successfully installed django Not sure about that, since my last upgrade (to 3.0.4) has been a while ago, but I think those lines aren't problematic (but don't quote me on that). I'm sorry about not having any insight, but I simply have not encountered this problem or anything like it and if I had to take a wild guess it might have something to do with you using aura and the recent changes in AUR, but that's a real long shot. @Elektro121: That seems to be the same issue @dev_arch ran into, so you could read his posts and my replies, but in short: I don't know why it's happening and I haven't been able to reproduce it, sorry. But if you find anything wrong with the package / how to fix it, I'll gladly add it.

dev_arch commented on 2014-07-06 18:11 (UTC)

@calrama New evening, new rounds. I went for complete seafile-server re-installation. Without backup of the data though, which is not practical at nearly 1.5TB. Eventually I tried by removing every dependency (without python itself) en re-installing from there. I have python-djblets in my package cache and build django-pipeline with the PKGBUILD you linked to on https://aur.archlinux.org/packages/python-django-pipeline/ I then created a new instance as per the wiki but regretfully the result is the same. For completeness sake: $ sudo aura -A seafile-server aura >>= Determining dependencies... aura >>= Dependency checking failed for these reasons: The dependency `django-pipeline` demands version `>=1.3.23`but the most recent version is `1.2.24-1`. And later when having installed django-pipeline separately during the installation of seafile-server: Installing collected packages: django Found existing installation: Django 1.6.5 Not uninstalling Django at /usr/lib/python2.7/site-packages, outside environment /usr/lib/seafile/seafileenv Successfully installed django At the moment I'm left hoping for an insight from you. Meanwhile I'll try and install on a virgin Vbox Arch. Your efforts are much appreciated regardless!

Elektro121 commented on 2014-07-06 14:57 (UTC)

Problem on seafile-admin def start_seahub_gunicorn(): argv = [ PYTHON, '/usr/bin/gunicorn_django-python2', '-c', conf[CONF_SEAHUB_CONF], '-b', '0.0.0.0:%s' % conf[CONF_SEAHUB_PORT], ] info('Starting seahub...') env = get_seahub_env() if run_argv(argv, cwd=conf[CONF_SEAHUB_DIR], env=env) != 0: error('Failed to start seahub') info('Seahub running on port %s' % conf[CONF_SEAHUB_PORT]) usage: gunicorn_django-python2 [OPTIONS] [APP_MODULE] gunicorn_django-python2: error: No application module specified. The syntax of the app changed, wtf Oo

« First ‹ Previous 1 .. 29 30 31 32 33 34 35 36 37 38 39 .. 47 Next › Last »