Arch Linux User Repository

I have a problem with the sha256-sums.

==> Validating source files with sha256sums...
    v6.3.1-server.tar.gz ... FAILED

After validating this for myself the checksum is indeed different from the one mentioned in the PKGBUILD:

marcus@mri-tp:~/tmp >>> wget 'https://github.com/haiwen/seafile-server/archive/v6.3.1-server.tar.gz'
--2018-06-28 12:15:58--  https://github.com/haiwen/seafile-server/archive/v6.3.1-server.tar.gz
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving github.com (github.com)... 192.30.253.112, 192.30.253.113
Connecting to github.com (github.com)|192.30.253.112|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/haiwen/seafile-server/tar.gz/v6.3.1-server [following]
--2018-06-28 12:15:59--  https://codeload.github.com/haiwen/seafile-server/tar.gz/v6.3.1-server
Resolving codeload.github.com (codeload.github.com)... 192.30.253.121, 192.30.253.120
Connecting to codeload.github.com (codeload.github.com)|192.30.253.121|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 721928 (705K) [application/x-gzip]
Saving to: ‘v6.3.1-server.tar.gz’

v6.3.1-server.tar.gz          100%[==============================================>] 705.01K   469KB/s    in 1.5s    

2018-06-28 12:16:02 (469 KB/s) - ‘v6.3.1-server.tar.gz’ saved [721928/721928]

marcus@mri-tp:~/tmp >>> sha256sum v6.3.1-server.tar.gz
3e21836e374e4c321f87594c7a5f5db516890c9b40f61e102750c84d638dbf37  v6.3.1-server.tar.gz

@ikwyl6 What is your processor architecture?

uname -a

Try to compile with :

makepkg -A

If it compile fine, I'll add your architecture in the PKGBUILD.

I have pogoplug with arm and I can't do a 'makepkg':

$ makepkg ==> ERROR: seafile-server is not available for the 'arm' architecture. ==> ERROR: changelog file (ChangeLog) does not exist or is not a regular file.

==> ERROR: An unknown error has occurred. Exiting...

Any ideas?

@cybertron See the recent comment for the seahub package.

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.