@BunBum: I do not know why they tagged them as a stable release, but I would believe it to be simple human error. Regardless, the update should work if you followed the normal upgrade procedure outlined on the Seafile ArchWiki page. If you still received this error that way, it might be that your virtual environment got messed up, in which case you can try the following:
# pacman -Rsunc seafile-server
# pacman -Rsunc seafile-shared
(the second line should not be necessary, but do it anyway to make certain it hase been removed)
At this point make sure that the virtual python environment for seafile has been removed, i.e. /usr/lib/seafile/ should be empty (or not exist). If necessary, remove everything in /usr/lib/seafile/.
$ yaourt -S seafile-server
(or any other AUR package wrapper, but I tried only with yaourt)
You should now have a working virtualenv. After this, do normal upgrade (but call the minor upgrade script instead of the non-existing 3.1-to-4.0 upgrade script).
By the way, you should not need to install pillow (I removed it from the dependencies explicitly), since it is being installed with pip in the virtual python environment.
Search Criteria
Package Details: seafile 9.0.11-1
Package Actions
| 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) |
Dependencies (8)
- fuse (fuse2)
- libevent (libevent-gitAUR)
- libsearpcAUR
- libwebsockets
- python-future
- sqlite (sqlite-fossilAUR)
- intltool (make)
- vala (vala-gitAUR) (make)
Required by (2)
Sources (2)
<deleted-account> commented on 2014-11-10 18:08 (UTC)
BunBum commented on 2014-11-10 17:56 (UTC)
Why do they tag a release and say it is not a release? ... :-/
After I upgradet to 4.0.0 nothing is working anymore. First I deleted gunicorn because it is not necesarry to be installed. Then I updated everything.
Then I got this error:
Error: Python module "python imaging library(PIL)" not found. Please install it first
After manually installing python2-pillow I get following:
ImportError: No module named gunicorn
After installing gunicorn-python2 (19.1.1-1) from the AUR the service does start without errors, but it does not work anymore. I cant open the seahub webinterface and so on.
<deleted-account> commented on 2014-11-10 16:06 (UTC)
! Important information about the 4.0.0 update !
See here: https://github.com/haiwen/seafile/issues/920
Apparently upstream created a stable tag for 4.0.0 even though it is still in testing (so I updated this package too soon). Since it seems to be working without any real problems I decided not to downgrade the seafile-packages to <4.0.0 for now. Should enough people strongly feel against this decision, I will downgrade the packages. Otherwise there will be a new package release once the stable 4.0.0 is actually released upstream.
Should you choose to update now:
- There is currently no upgrade script for 3.1 to 4.0 at upstream. I have done my update with the minor upgrade script (under the assumption that there where no database changes) and have not encountered any problems so far.
- djblets and gunicorn are no longer PKGBUILD dependencies, they are installed inside the virtual environment for seahub. This removes the need to have these two packages manually installed with pacman at fixed versions.
BunBum commented on 2014-11-10 09:14 (UTC)
@bsergik @calrama
3.0.0 will be shown because it is declared so in their settings.py => https://github.com/haiwen/seahub/blob/master/seahub/settings.py#L403
The guys from seafile does not synchronize everything from their internal Bitbucket repository to their public GitHub repository :-/
<deleted-account> commented on 2014-11-08 14:55 (UTC)
@bsergik: That would be a question for upstream, since the web interface (seahub) is not technically a part of this package - you install it either manually or by calling seahub-preupgrade, the latter of which is just the manual steps bundled together. Personally, I have the same version shown in the web interface and have not had any problems with it so far, but for a proper answer you should still go to upstream.
<deleted-account> commented on 2014-11-08 14:55 (UTC)
@bsergik: That would be a question for upstream, since the web interface (seahub) is not technically a part of this package - you do it either manually or by calling seahub-preupgrade, the latter of which is just the manual steps bundled together. Personally, I have the same version shown in the web interface and have not had any problems with it so far, but for a proper answer you should give go to upstream.
bsergik commented on 2014-11-08 14:38 (UTC)
I get Server Version: 3.0.0 shown in the Web Interface. Is it ok?
<deleted-account> commented on 2014-09-20 10:38 (UTC)
@axil42: See my comment from 2014-07-05 18:59. Short version: Package was taken from me (without asking) and then broken such that it could not be built (whether this is still the case I do not know, but I informed the new maintainer and did not get a positive response). You can try using it, but if you do, and get it to work, please tell me.
<deleted-account> commented on 2014-09-20 10:38 (UTC)
@axil42: See my comment from 2014-07-05 18:59. Short version: Package was taken from me (without asking) and then broken such that it could not be built (whether this is still the case I do not know, but I informed the new maintainer and did not get a positive response). You can try using it, but if you do, please tell me should it work.
<deleted-account> commented on 2014-09-20 10:38 (UTC)
axil42: See my comment from 2014-07-05 18:59. Short version: Package was taken from me (without asking) and then broken such that it could not be built (whether this is still the case I do not know, but I informed the new maintainer and did not get a positive response). You can try using it, but if you do, please tell me should it work.
Pinned Comments