Arch Linux User Repository

Please, when you have compilation or execution errors, recompile each component without using an AUR helper before reporting an issue.

I recently set up a new machine, and setting up seafile is really weird with the current version. It asks me 4 times for a directory to set up Seafile every time I start it. Not just the first time. I have to click ok four times, then I have to cancel providing login information (which I already have) and then I get the normal seafile window.

Furthermore if I launch it from the console it respects the $QT_AUTO_SCREEN_SCALE_FACTOR sometimes. If I launch it by clicking the icon, it never does that and the scaling is all fucked up and not usable.

Since 6.2.0 is beta anyway, it would probably a good idea to revert this package back to the current stable version. It's not even the current beta version 6.2.1. Maybe it should be split up into seafile-client-stable and seafile-client-beta. But packaging an outdated beta version is not really a good idea.

@Squigly --> that's the problem: https://github.com/haiwen/seafile-server/issues/27

seafile-client 6.2.0 for linux is still beta and the hash will change with every commit. We'll have to wait until they make it final and stop changing the file on github.

It seems that the sha256sum listed in PKGBUILD is wrong (or the file getting pulled down is wrong):

sha256 of file downloaded: ~/.cache/aurman/seafile$ sha256sum seafile-6.2.0.tar.gz 50d117db2ebde2704cb1a327cf40a4bf6770637497d3bd4c4788a6db40f862cb seafile-6.2.0.tar.gz

sha256 from PKGBUILD: a456b8d80e2616f1d58f64448b527b204cadf626661d117ae6d1fdc9115c018e

Indecently, looks like the version was bumped to 6.2.1 couple of days ago.

sha256sum should be b79eb9b7ed93357ef3bf2e125cc1b6a0c5756bc09b5ce8cd3894ee04a992b8cf now

@SchorschD: I'm not able to reproduce your error, even in a clean chroot

Validity check fails for seafile. (seafile-client 6.2.0-3) sha256sum seafile-6.2.0.tar.gz 50d117db2ebde2704cb1a327cf40a4bf6770637497d3bd4c4788a6db40f862cb seafile-6.2.0.tar.gz

If corrected in PKGBUILD build fails with [code] libtool: link: gcc -DPKGDATADIR=\"/usr/share/seafile\" -DPACKAGE_DATA_DIR=\"/usr/share/seafile\" -DSEAFILE_CLIENT -I../include -I../lib -I../lib -I../common -I/usr/include/searpc -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-z -Wl,now -o seaf-daemon seaf-daemon.o job-mgr.o timer.o cevent.o http-tx-mgr.o vc-utils.o sync-mgr.o seafile-session.o seafile-crypt.o diff-simple.o wt-monitor.o wt-monitor-linux.o wt-monitor-structs.o clone-mgr.o seafile-config.o branch-mgr.o fs-mgr.o repo-mgr.o commit-mgr.o log.o rpc-service.o vc-common.o obj-store.o obj-backend-fs.o block-mgr.o block-backend.o block-backend-fs.o mq-mgr.o curl-init.o sync-status-tree.o filelock-mgr.o set-perm.o change-set.o ../lib/.libs/libseafile_common.a -lssl -lcrypto ../common/cdc/.libs/libcdc.a ../common/index/.libs/libindex.a -luuid -lsqlite3 -levent -lsearpc -lgio-2.0 -lgobject-2.0 -lglib-2.0 -ljansson -lz -lcurl -pthread curl-init.o: In function seafile_curl_init': curl-init.c:(.text+0x3c): undefined reference toCRYPTO_num_locks' curl-init.c:(.text+0x7b): undefined reference to CRYPTO_num_locks' curl-init.c:(.text+0x8c): undefined reference toCRYPTO_set_id_callback' curl-init.c:(.text+0x9f): undefined reference to CRYPTO_set_locking_callback' curl-init.o: In functionseafile_curl_deinit': curl-init.c:(.text+0xbe): undefined reference to CRYPTO_set_id_callback' curl-init.c:(.text+0xc6): undefined reference toCRYPTO_set_locking_callback' curl-init.c:(.text+0xe9): undefined reference to `CRYPTO_num_locks' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:536: seaf-daemon] Error 1 [/code]

For seafile-client, sha256sums should be: 5c0118031d0d2d06c76774d4973e7cf2ae60cc1ae51530dffd5ad9ccf2e9892e

In the PKGBUILD, just change: sha256sums=('3b5bbb16e30f70ecf2e4de50e1a1e1f26fb952115e25391e553a1212cf990ddc')

to

sha256sums=('5c0118031d0d2d06c76774d4973e7cf2ae60cc1ae51530dffd5ad9ccf2e9892e')

For seafile, sha256sums should be: a456b8d80e2616f1d58f64448b527b204cadf626661d117ae6d1fdc9115c018e

In the PKGBUILD, just change: sha256sums=('de0e8e1c48326d579fbd300fb2d5737f7bb1c42bd349fe5e53129987606bdfb8' 'a2d7f7cf0c59aba97650af62b3cefd0ceb71a1007c34d9369a88e5769c7f6076' 'c37510109c1de64c774896df39aece240c056b54414d2119fca01860211156ba')

to

sha256sums=('a456b8d80e2616f1d58f64448b527b204cadf626661d117ae6d1fdc9115c018e' 'a2d7f7cf0c59aba97650af62b3cefd0ceb71a1007c34d9369a88e5769c7f6076' 'c37510109c1de64c774896df39aece240c056b54414d2119fca01860211156ba')

Validity check still fails for seafile and seafile-client 6.2.0-2.

sha256sums has changed (as for seafile package) because source was modified one day ago. Need to be corrected in the PKGBUILD. Thank you

It seems like the checksums of seafile (and seafile-client) 6.2.0 are broken again.

==> Validating source files with sha256sums... seafile-6.2.0.tar.gz ... FAILED libseafile.in.patch ... Passed seaf-cli@.service ... Passed ==> ERROR: One or more files did not pass the validity check!