Package Details: seahub 6.2.5-6

Git Clone URL: https://aur.archlinux.org/seahub.git (read-only)
Package Base: seahub
Description: The web frontend for seafile server
Upstream URL: https://github.com/haiwen/seahub
Licenses: custom:Apache PSF MIT BSD GPL
Submitter: eolianoe
Maintainer: Joffrey
Last Packager: Joffrey
Votes: 6
Popularity: 0.461010
First Submitted: 2017-07-03 09:48
Last Updated: 2018-02-26 11:09

Pinned Comments

Joffrey commented on 2018-02-13 10:56

SEAHUB UPGRADE

Prerequisites :

  • The seafile-server daemon must be stopped
  • You must use seafile user
  • You must be placed in /your/instance/seafile-server/

Make a seahub backup :

mv seahub seahub-old

Copy the new directories

cp -r /usr/share/seafile-server/{upgrade,seahub} ./

Run an upgrade :

./upgrade/concerned-script.sh

Otherly you can use my script seafile-helper available on AUR.

Latest Comments

Joffrey commented on 2018-02-18 16:56

I was sure that pacman will not delete them, as possible I will remove the install file. I started to deploy seahub with minimal dependencies in an isolated environment (docker) for remove unnecessary dependencies.

klemens commented on 2018-02-18 15:05

@Joffrey: Sorry, I did not mean actual random directories but that the package deletes a directory that it has not created (but pacman), which can be really surprising (seem "random") for users. Regarding openjpeg2: You are right, I always remove the ffmpeg dependency, as I don't need video thumbnails and it pulls in quite a large number of dependencies, so I did not notice.

@Captain_Rage: Not exactly what I had in mind, but good to hear that it works for you now! ;-)

Captain_Rage commented on 2018-02-17 23:49

@klemens Nope, that didn't work. However, I went with your tip and simply reverted back to using FastCGI. Now Seahub working flawlessly again. I have no idea what the problem with wsgi is. If I will be forced to use wsgi in the future I will create a support thread. Cheers for the assistance!

Joffrey commented on 2018-02-17 21:23

@klemens compiled all locales is a good idea, I think push it. For your others suggestions I do not agree:

  • "Deleting random directories" ?!? It's two absolute path (correction: ok the install file 'll be delete). You must never modify manually a file or directory in /usr ! No user files should be there.
  • Openjpeg2 is a ffmpeg depend, It is necessarily installed with seafile-server.

Personally, I think that using a venv is a good idea, it avoids installing unnecessary dependencies elsewhere. If you want, you can package seafile-server/seahub and dependencies without virtualenv and propose them on AUR.

klemens commented on 2018-02-17 18:04

The new package works fine for me (including seafile-server), although I still would prefer not using virtual environments (as much).

However, it seems openjpeg2 is still not a dependency (?) and the post_upgrade script is really scary. Deleting random directories can really break stuff, as other packages or the user itself might have some important files in there. Also it is not necessary, as all files in /usr/lib/seafile and /usr/bin/seahub-preupgrade were part of the previous packages and are removed by pacman automatically.

I saw that your helper in the other package supports compiling the languages (although note that it currently misses the js-tanslations: djangojs.po), but why not simply compile all language files at compile time in this package? Something like:

for pofile in /path/seahub/locale/*/LC_MESSAGES/*.po; do
    msgfmt -o "${pofile%.po}.mo" "$pofile"
done

@Captain_Rage: These log files only contain something if there were any errors or any requests at all in the case of seahub_cache. Can you load seahub directly (port 8000 by default) without using a webserver in front of it? Note that in my experience using fastcgi with seahub is not very reliable but a simple reverse proxy has been working fine for several years here. Also it might make sense for you to open a thread in the arch forums or similar, as it is not very easy to follow the discussion here in the aur comments.

Captain_Rage commented on 2018-02-16 23:26

Yet another fruitless day trying to resolve my Seahub issue. I tried deploying a new instance, according to the official manual. Nothing changed, with the exception of

/tmp/seahub.log
/tmp/seahub_cache
/tmp/seahub_django_request.log

now appearing (although the log files stay empty). The thing is.......... Seahub is supposed to install its python dependencies in its own virtual environment with pip, right? The packages in there won't be identical to those installed on the normal system, visible to root, right? I should be able to enter Seahub's virtual environment and see which python packages are installed with pip, right? Nothing works or makes sense.

I run 'source /usr/lib/seahub/bin/activate' to enter Seahub's virtual environment, then 'pip2 list' only to find that the packages are identical to the ones outside the virtual environment (shouldn't 'gunicorn' be visible here, for example?!?) and exit with 'deactivate'.

When displaying the installed files of Seahub using -Ql in the package manager there are files with the name gunicorn. It seems to start using systemd also, but that's it. It simply refuses to work or give out any hint on why it doesn't.

What am I missing? Is it a misunderstanding from my part? Your guidance is dearly appreciated.

Joffrey commented on 2018-02-13 11:21

@Captain_Rage I have pinned the update procedure. I will try to update the wiki soon, this would avoid the problems related to a bad installation.

Joffrey commented on 2018-02-13 10:56

SEAHUB UPGRADE

Prerequisites :

  • The seafile-server daemon must be stopped
  • You must use seafile user
  • You must be placed in /your/instance/seafile-server/

Make a seahub backup :

mv seahub seahub-old

Copy the new directories

cp -r /usr/share/seafile-server/{upgrade,seahub} ./

Run an upgrade :

./upgrade/concerned-script.sh

Otherly you can use my script seafile-helper available on AUR.

Captain_Rage commented on 2018-02-12 00:49

@Joffrey Thank you very much for the feedback. Your comment made me cling on to hope of salvaging my installation. I will try to figure it out. One more question: what is the recommended way of upgrading the Seafile server/Seahub installation? Earlier, when it was still working over here, I used to upgrade the server once a new package had been installed by running seahub-preupgrade as the seafile user (it would download upgrade scripts) and then running any upgrade script up to the current version. Now seahub-preupgrade seems to be gone.

Joffrey commented on 2018-02-11 10:05

@Captain_Rage I do not think anyone can help you, each configuration is unique. But if:

  • Seahub is not accessible to your.ip.local.port:8000 (It's a server problem, look permissons, configurations, run an upgrade... https://manual.seafile.com/faq/)
  • Seahub is not accessible to your.domain.ex (look your reverse proxy conf (gateway given), otherly your hosts file or your DNS conf if you have bought a domain can be also a problem source)

Else you can create a new instance.

All comments