Arch Linux User Repository

@xiota, namcap confirmed (I hadn't noticed because it builds fine in a clean chroot for me) and also uncovered a bad license ID. I fixed both. Thanks!

Hi from your new maintainer. Since 2.0.22-2 this package is built from source instead of harvesting a .deb, simplifying the dependencies.

This package should probably be renamed to seadrive-fuse, as this is what the upstream repo is called. The name seadrive-daemon was inherited from the official .deb (built by the upstream company); it also appears in the usage description. The provided executable is just named seadrive.

@piater...yes please...adopt it !!!!

@C0gnitiveFl0w, are you still maintaining this package? Otherwise I'd like to adopt it.

As amply documented in the Comments, it does not currently build. Moreover, I see no reason to resort to Debian's build; it easily builds from source, without -compat and openssl-1.0 dependencies. I have a working PKGBUILD in local use and would like to transition this package to it.

Could we, by any chance, switch the dependency from libevent-compat to libevent? libevent-compat seems to be broken, and the libevent version seems to work perfectly.

There is once again a version mismatch: only 2.0.15 exists on Ubuntu's servers.

Perhaps it is time to change upstream to seadrive's github?

The following changes fix the problem:

5c5
< pkgver=2.0.16
---
> pkgver=2.0.15
14c14
< sha256sums=('d635d8d679c689d3abe0cf6a3ef4509c3fd5326690e9f887689415c289f93521')
---
> sha256sums=('ecf52a12de7cdbd816f75fd5d87449224f4fad4cfcc73f56955554f3c8ce0156')

For this error:

libevent-2.0.22-stable.tar.gz due of uknown public key 910397D88D29319A

t123yh provides a solution in a comment in https://aur.archlinux.org/packages/libevent-compat:

gpg --keyserver keyserver.ubuntu.com --recv 8D29319A

It works for me, though I don't know whether there is any security issue with it.

Edit: Found a nice article about gpg keys: https://forum.manjaro.org/t/aur-package-fails-to-verify-pgp-gpg-key-unknown-public-key-one-or-more-pgp-signatures-could-not-be-verified/6663

Building from source seems to be rather easy, actually. It is also pretty fast, so I don't see any reason why we should stick to using the debian binaries. Here's a patch for this PKGBUILD to make it build from release tarballs. Also note that the current license seems to be GPL3.

diff --git a/PKGBUILD b/PKGBUILD
index d37acca..ec7c92e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,24 +3,25 @@

 pkgname=seadrive-daemon
 pkgver=2.0.16
-pkgrel=1
+pkgrel=2
 pkgdesc="Daemon part of seadrive"
 arch=('x86_64')
-url="https://www.seafile.com/en/download/ + https://linux-clients.seafile.com/seadrive-deb/focal/pool/main/s/seadrive-daemon/"
-license=('Apache')
+url="https://github.com/haiwen/seadrive-fuse"
+license=('GPL3')
 depends=('libsearpc' 'libcurl-compat' 'libevent-compat'
          'openssl-1.0' 'fuse2')
-source=("http://linux-clients.seafile.com/seadrive-deb/focal/pool/main/s/${pkgname}/${pkgname}_${pkgver}_amd64.deb")
-sha256sums=('d635d8d679c689d3abe0cf6a3ef4509c3fd5326690e9f887689415c289f93521')
+source=("https://github.com/haiwen/seadrive-fuse/archive/refs/tags/v${pkgver}.tar.gz")
+sha256sums=('36d32896cb8f347692fe8357014d709cee9b6a2d15f6bb4670343cd69df22b4c')

-prepare() {
-  cd "${srcdir}"
-
-  tar -xJf data.tar.xz
+build() {
+  cd "seadrive-fuse-${pkgver}"
+  ./autogen.sh
+  ./configure --prefix=/usr
+  make
 }

-package () {
-  cd "${srcdir}"
-
-  install -Dm 755 "${srcdir}/usr/bin/seadrive" "${pkgdir}/usr/bin/seadrive"
+package() {
+  install -Dm 755 \
+    "${srcdir}/seadrive-fuse-${pkgver}/src/seadrive" \
+    "${pkgdir}/usr/bin/seadrive"
 }

Seadrive is now open source:

https://github.com/haiwen/seadrive-fuse

I guess build could be changed to build from source instead of using deb file that often has mismatched versions?