Does anyone know where I can find seaf-gc.sh mentioned here http://manual.seafile.com/maintain/seafile_gc.html ?
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)
BunBum commented on 2014-11-24 16:21 (UTC)
Armadillux commented on 2014-11-23 13:44 (UTC)
Did and successfull upgrade sticking to the wiki and using the minor upgrade script suggested by calrama.
Keeping an eye open for problems!
Thx calrama
<deleted-account> commented on 2014-11-16 20:24 (UTC)
@monochromec: Yes. If you look in the above metadata for this package, you will see the github site listed under "Upstream URL"; that is what I was referring to. At that URL you can navigate to their bug tracker (which in this case is the github issue system); the URL you shuold reach that way is the following: https://github.com/haiwen/seafile/issues
monochromec commented on 2014-11-16 20:18 (UTC)
@calrama: thanks for the quick reply! As I'm pretty new to the AUR: by upstream you mean the github site? (as this is an AUR package)
<deleted-account> commented on 2014-11-16 18:35 (UTC)
@monochromec: At first glance this does not look like a packaging issue to me, so I suggest opening a bug report upstream.
monochromec commented on 2014-11-16 18:30 (UTC)
Just stumbled across an issue with seaf-server: executing this with the following parameters produces a SIGILL on an armv7h architecture:
-f -c /mnt/disk/seafile/example.com/ccnet -d /mnt/disk/seafile/example.com/seafile-data -l /mnt/disk/seafile/example.com/logs/seafile.log -P /mnt/disk/seafile/example.com/seafile-data/pids/seaf-server.pid
GDB tells me:
#0 0x40561da8 in _armv7_tick () from /usr/lib/libcrypto.so.1.0.0
#1 0x4055e204 in OPENSSL_cpuid_setup () from /usr/lib/libcrypto.so.1.0.0
#2 0x40010194 in call_init.part () from /lib/ld-linux-armhf.so.3
#3 0x400102f0 in _dl_init_internal () from /lib/ld-linux-armhf.so.3
#4 0x40000c44 in _dl_start_user () from /lib/ld-linux-armhf.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Needless to say, w/o a working seaf-server instance the whole framework doesn't work (including the web frontend).
Happy to provide more information as required.
<deleted-account> commented on 2014-11-11 17:55 (UTC)
@Bunbum: That's because you kept it installed. You did not do "pacman -Rsunc seafile-server", right? Because if you did, it should've been removed. Pip will first try to use the normal site packages (installed through pacman) and not install if not needed. So, if you remove the pacman package after setting up the virtualenv, you will not have any simplejson, since the virtualenv depended on the pacman one. You can fix this, by removing python2-simplejson, and then simple installing seafile-server again. Alternatively, after removing python2-simplejson, do the following:
# /usr/lib/seafile/seafileenv/bin/activate
(seafilenv) # pip install simplejson
(seafilenv) # deactivate
<deleted-account> commented on 2014-11-11 17:54 (UTC)
@Bunbum: That's because you kept it installed. Pip will first try to use the normal site packages (installed through pacman) and not install if not needed. So, if you remove the pacman package after setting up the virtualenv, you will not have any simplejson, since the virtualenv depended on the pacman one. You can fix this, by removing python2-simplejson, and then simple installing seafile-server again. Alternatively, after removing python2-simplejson, do the following:
# /usr/lib/seafile/seafileenv/bin/activate
(seafilenv) # pip install simplejson
(seafilenv) # deactivate
BunBum commented on 2014-11-11 06:27 (UTC)
I followed your steps and reinstalled everything. Now it works. Thank you. Something destroyed my installation during the upgrade... hhmmm...
You should add python2-simplejson to the dependencies. After installation you get following message:
==> Packages no longer required by any installed package:
python2-simplejson
If you remove it seafile does not work anymore.
<deleted-account> commented on 2014-11-10 18:10 (UTC)
@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)
# pacman -R python2-pillow
# pacman -R gunicorn-python2
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.
Pinned Comments