Arch Linux User Repository

@river_wunsch my bad, I had a local copy of the source tar and the guys at Seafile seems to have force pushed over the tag after its original release (as they love to do).

Just cleanup everything and re-ran updpkgsums, everything should be good in 3.0.12-2.

@orax Thanks for your hard work! Unfortunately, it seems that sha256 needs an update.

@lprobsth I have been facing the same issue for a couple of days. This seems to be related to the update of the seadrive-daemon package that has now finally reached v3 which I needed to update this one.

I was just able to do the update and everything seems to be back to working. There was a weird period where the latest version of both seadrive-daemon and seadrive-gui couldn't be built for Linux due to some weirdness in Seafile's codebase. This has now been fixed with v3.0.12.

I apologize for not being able to fix this earlier. I have been tracking issues and PR for quite some time now and was finally able to push a fix.

Hope this fixes the issue for all person affected.

SeaDrive has completely stopped working for me for no known reason. The $home/SeaDrive directory just is unreadable when the seadrive gui application is started. I can't access the directory with any tools - I'm even unable to delete the directory with "sudo rm SeaDrive". I'm not able to identify the reason: logs show nothing particularly related to the problem, I have reverted the kernel, deleted the seadrive root folder, reinstalled seadrive, fsck'ed the partition, ... I'm wondering if this is related to using an outdated version of seadrive?

In case anyone has the same issue, it seems like there's some compatibility issue between this package and curl 8.10.0.

Even freshly re-compiled, I could not push any data in any library, seadrive logged PUT errors like this one every time:

[09/14/24 18:19:00] http-tx-mgr.c(752): libcurl failed to PUT https://not.my.true.domain.com/seafhttp/repo/8ea86777-a6b8-43d7-9982-b82c1068079e/commit/HEAD/?head=dc12500ae0be2231f802e1578ce4ed74a24365d8: Stream error in the HTTP/2 framing layer.

Downgrading to curl to 8.9.1 (as well as lib32-curl & libcurl-gnutls to be safe, but I assume curl would have been enough) solves the issue.

Given the lack of support for linux over the past months, though, I think I'm just going to switch back to the regular seafile client.

This package has been marked as out-of-date for quite a while, but the latest v3.0 of seadriver-gui has quite a bit of issues to build on Linux. I am slowly working on a set of patches to make it compile, sadly it's now failing at the linking phase as some of the new required methods are not implemented for Linux yet.

Works seems to be going to fix this as part of https://github.com/haiwen/seadrive-gui/pull/404/ which I am monitoring. I am sorry for the delay, but this is a bit outside my area of expertise.

In the meantime, there have been some patches pushed to v2.0 since the release of v3.0 which I have been updating this package for.

EDIT(2024-03-31): Tried building with #404 patch, everything built fine, but libraries do not load. I will continue monitoring the repo/PR to see what is going on there.

For a few days, I've been getting "SeaDrive exited unexpectedly."

Checksums updated, sorry for the delay. It seems that Seadrive GUI had a force-push on the v2.0.27 version on March 24 while it was already release on March 22 when I packaged the update.

Source validation fails. sha256sum does not match.

See @mengsk comment below.

Currently the sha256 sum is b71d6e766f083668b958b2d448c556a2d19e1c52bfcab228a48d6591e0ba3eb1

 curl -L https://github.com/haiwen/seadrive-gui/archive/v2.0.27.tar.gz | sha256sum
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 13.6M  100 13.6M    0     0  13.9M      0 --:--:-- --:--:-- --:--:-- 26.1M
b71d6e766f083668b958b2d448c556a2d19e1c52bfcab228a48d6591e0ba3eb1 *-