Arch Linux User Repository

What is the acutal upgrade way? I used the seahub-preupgrade function after upgrading the arch packages but this function does not exsist anymore?

Major changes for v6.2.5-2 see ChangeLog : pacman -Qc seafile-server

After upgrade you'll must restart the daemon

The 6.2.5 release is currently broken: The updated seaserv python lib in seafile-server depends on the get_group_repos_by_user function to the seafile python lib added in e16e5401e, but the seafile lib is packaged in the seafile package and not seafile-server. However, this change is not included in seafile version 6.1.4 (it is not even anywhere in the repo and in the seafile-server repo it is only in the 6.2 branch and not in master, really confusing).

I temporarily "fixed" it by manually replacing rpcclient.py with the one from seafile-server…

Either I am too stupid or this is all just a nightmare. I have built and installed all the packages including seahub and seafile-server. By reading the wiki page and remembering my folder structure from before the seahub has been installed as a package I had the following directory structure: /srv/seafile for holding as many subfolders as I plan to run seafile sites on this machine. So it will include at least one folder e.g. files.domain.tld. Inside that folder there should be folders such as ccnet, seafile-data, seafile-server and conf. Seahub files are now part of an installed package inside /usr/share/seafile-server/seahub. No mather how hard I'm trying either on my own or by following advices you are trying to give to me the mysql setup is leading to the situation where the scripts are expecting an /usr/share/seafile-server/seahub copy inside /srv/seafile/files.domain.tld/seafile-server/seahub. Joffreys approach appears to be most straighforward however It still does not work for me. I can create these empty folders /srv/seafile/files.domain.tld/seafile-server/runtime /srv/seafile/files.domain.tld/seafile-server/seahub copy /usr/share/seafile-server/scripts/setup-seafile-mysql.* into /srv/seafile/files.domain.tld/seafile-server and run setup-seafile-mysql.sh. The database and ccnet config gets created however it finishes with a python traceback looking for /srv/seafile/files.domain.tld/seafile-server/seahub/tools/secret_key_generator.py. I will be slowly tinkering with it occassionally and by 2022 I might be able to figure it out. I think this is not meant to be runing in a kind of multi site setup. I do fail to understand what an improvement seahub packaging brings when I do have to copy it to site specific folder anyway.

@all: sorry for the delay with the answers to e-mails and comments, real life is a bit busy for now. Expect an update of all seafile packages by the beginning of January.

@pvagner You do not have too much interest to use a seahub for all your instances, if I understood correctly, because the upgrade must be done manually.

For a MySQL install, I have made a patch:

--- a/scripts/setup-seafile-mysql.py
+++ b/scripts/setup-seafile-mysql.py
@@ -304,14 +304,13 @@
-        self.bin_dir = os.path.join(self.install_path, 'seafile', 'bin')
+        self.bin_dir = '/usr/bin'
         self.central_config_dir = os.path.join(self.top_dir, 'conf')
         Utils.must_mkdir(self.central_config_dir)

     def check_pre_condiction(self):
         def error_if_not_exists(path):
             if not os.path.exists(path):
                 Utils.error('"%s" not found' % path)

         paths = [
-            os.path.join(self.install_path, 'seafile'),
             os.path.join(self.install_path, 'seahub'),
             os.path.join(self.install_path, 'runtime'),
         ]
--- a/tools/seafile-admin
+++ b/tools/seafile-admin
@@ -864,3 +864,10 @@
+    # seahub.db is useless with MySQL and crash the startup!
+    with open(files[3], 'r') as f:
+        for line in f:
+            if 'DATABASES' in line:
+                del(files[2])
+                break
+
     for fpath in files:
         if not os.path.exists(fpath):
             error('%s not found' % fpath)

It works very well free to you to use it now. But I would like that we can discuss to find good solutions for to be introduced in the PKGBUILD :)

It miss an active maintainer for this package. A big thank at @eolianoe who brought a lot of contributions to this package, but now the package is outdated since 1 month and email without answers...

I use seafile-server with MariaDB in production and I hope to see in the future seafile in community repository ;)

@klemens I will try your suggestion however I am still very confused. I've installed seafile-server and seahub packages. I do have scripts and seahub folder inside /usr/share/seafile-server . These are owned by root so seafile user can't write into these folders. It's clear seahub python scripts have to be compiled into pyc or pyo files and language files have to be compiled into gettext mo files. When creating instance specific folders inside /srv/seafile/seafile.whatever.tld the suggestion is to create yet another seafile-server folder with seahub inside or how to do it properly and ideally as efficiently as possible? Might it be possible just doing a bind mount or something similar to use the exact same seahub folder for all the instances? Or am I missing something else?

@pvagner: I haven't tested this completely, as I am using postgresql, but I just played around a bit with the setup-seafile-mysql.{sh,py} scripts:

I first created the instance folder /srv/seafile/test.tld and in it a seafile-server folder like described in the wiki. Then I used the seahub-preupgrade script included in the seahub package to copy seahub and the upgrade scripts into it. Then I copied setup-seafile-mysql.{sh,py} into /srv/seafile/test.tld/seafile-server, but it complained that it could not find seafile and runtime, which can be fixed by just creating these tow folders. Afterwards the script ran fine until it actually wanted to connect to some mysql server, which I don't have.

I am not entirely sure if the seahub copy (reflink on btrfs and possibly xfs) is really necessary. The media/CACHE/ folder only contains some compiled css file in my instance, which possibly can be moved into another folder (like seahub-data). All other generated data is already stored outside.

@klemens So for mysql setup we have to copy the seafile-server folder to instance specific folder and also copy seahub into that? Do we need instance specific seahub copy for each seafile-server instance? Is there no better way?

I packaged seafdav to enable the webdav-support in seafile: python2-wsgidav-seafile. This should work out of the box by configuring dav like described in the seafile manual.

@eolianoe: Feel free to also add this as an optional dependency. I can add you as a co-maintainer if you want.