Package Details: seafile-client 9.0.13-2

Git Clone URL: https://aur.archlinux.org/seafile-client.git (read-only, click to copy)
Package Base: seafile-client
Description: GUI client for synchronizing your local files with seafile server
Upstream URL: https://github.com/haiwen/seafile-client
Licenses: Apache
Submitter: Localizator
Maintainer: Joffrey
Last Packager: Joffrey
Votes: 168
Popularity: 0.000000
First Submitted: 2012-12-10 17:34 (UTC)
Last Updated: 2025-04-05 18:40 (UTC)

Pinned Comments

Joffrey commented on 2021-05-30 20:06 (UTC) (edited on 2021-05-30 20:11 (UTC) by Joffrey)

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 44 Next › Last »

bionade24 commented on 2021-10-16 12:10 (UTC)

@snack No, it's full of AUR packages. Honestly, at this point just downgrade to 8.0.3 and stick with it. Maybe it's bc my server still runs 7.15. Someone has to take time to debug it correctly.

My checksums:
158237338f3476140a230ff5adff1f6b0e8831f3c2947317348d553deb99fca4 /usr/bin/seafile-applet
8fca5c846fd932d853915b207bbabe3eacffb74e990a24012141b69413913e06 /usr/bin/seaf-daemon
ab10cafcc2951a856a830b7a2686cf87efa62e55bd97ee10656aebd757234a31 /usr/lib/libsearpc.so
70fae0d24bd84ee00b5543f3c1ae676fed72773260081525bb43bf29f24af382 /usr/lib/libseafile.so

snack commented on 2021-10-16 12:02 (UTC)

@bionade24: thanks for the help and sorry for the off-topic question. The problem still persists on my machine, but I se that in your repo you have many other packages. Do you use these instead of the official Arch ones on the machines where Sefile works as expected? If yes then the breakage might come from a non-Seafile package whose version in Arch repos causes the breakage.

bionade24 commented on 2021-10-16 11:27 (UTC) (edited on 2021-10-16 11:28 (UTC) by bionade24)

This will go a bit off-topic (if requested I'll delete it).

@snack The key pacman complains about is a subkey of my key (Or the other way around idk). Answering the dialog will unfortunately not help. The right way is to edit the trust level of the key, which can be achieved faster by using pacman-key --lsign-key <fingerprint>.

snack commented on 2021-10-16 11:26 (UTC)

@bionade: I imported and trusted the key 289AD6AA32857A04ABA587417EAC11ACDBCFBCEB, then pacman -Syy then pacman -S seafile-client seafile libsearpc. Still the same issue.

snack commented on 2021-10-16 11:01 (UTC)

@bionade: I added your [oscloud] repo to my pacman.conf, but when I download its db pacman says:

error: oscloud: key "289AD6AA32857A04ABA587417EAC11ACDBCFBCEB" is unknown

This key is different from the one listed in archwiki:

Key-ID: CB222E7EBC11D682AAC8B317A4A0D73114FDE6FC

Should I trust it? (not a gpg expert here, so sorry if the question is a dumb one). Thanks

bionade24 commented on 2021-10-16 10:27 (UTC)

@snack I would say that should work, too. But you'll only be sure with PGP integrity.

Now upgraded my 2nd device, works fine too.

snack commented on 2021-10-14 08:13 (UTC)

@bionade24: I downloaded the packages from your site manually and the pacman -U.

snack commented on 2021-10-14 08:10 (UTC)

@bionade24: I downloaded the packages from your site manually and the pacman -U.

bionade24 commented on 2021-10-13 20:46 (UTC) (edited on 2021-10-16 10:27 (UTC) by bionade24)

@snack @wudu @ReneS I now updated my system and seafile to 8.0.4. As I've already guessed, it works fine for me and it seems to be a super tricky issue with dirty build environments. So either build in clean chroots or use my repo, but it's not the pkg's fault.

@Joffrey Maybe change the pinned comment to building in a clean chroot.

@snack: You sure youre cache didn't fuck that up? Try pacman -Rsc seafile-client seafile libsearpc && pacman -Scc && pacman -S seafile-client after you added my repo.

Edit: Now also updated my 2nd machine, everything works fine.

ReneS commented on 2021-10-13 15:22 (UTC)

Updated from v8.0.3 to v8.0.4 recently. Now it crashes, this is how you can reproduce the issue:

  1. Start Seafile
  2. In the Seafile window, hover the mouse over the settings button

Reproduced on 2 arch installations.

This is the stack trace: https://pastebin.com/AMmc9pTZ

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 44 Next › Last »