Package Details: libsearpc 2:3.3.0-3

Git Clone URL: (read-only, click to copy)
Package Base: libsearpc
Description: A simple C language RPC framework (including both server side & client side)
Upstream URL:
Licenses: Apache
Submitter: aclindsa
Maintainer: thealchemist (Joffrey)
Last Packager: Joffrey
Votes: 87
Popularity: 0.029301
First Submitted: 2013-01-19 15:50 (UTC)
Last Updated: 2023-06-16 09:13 (UTC)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

gromit commented on 2023-06-06 17:51 (UTC)

@mehrad, while that is true they are assumed to be installed as they are part of the base-devel meta package.

mehrad commented on 2023-06-06 15:32 (UTC)

the autoconf and automake are also the dependencies of this package. Without them the libsearpc installation fails.

piater commented on 2023-03-04 08:21 (UTC)

Actually I was wrong; the hash is currently correct. The problem was that libsearpc's reuse of the same archive name (...-latest) for different releases tricked aurutils into thinking it already had downloaded the requested archive, which was in fact stale. Deleting the cached archive triggered download of the current version whose sha256sum does match.

Alad commented on 2023-03-03 14:06 (UTC)

If upstream keeps changing their tags, maybe you should pin to a specific commit instead of downloading a release archive

piater commented on 2023-03-02 08:35 (UTC)

The sha256sum is invalid again...

urldog commented on 2020-09-18 14:19 (UTC)

This fails to build, even using The "new" hash for the 3.2.0 version :) I understand it's difficult to package something where code changes and version number doesn't, but seafile on arch is broken very often. It's not IME in ubuntu-based distros.

IMars commented on 2020-09-09 05:12 (UTC)

The "new" hash for the 3.2.0 version is


tilx commented on 2020-03-25 15:17 (UTC)

The people making Seafile have a habit of re-releasing different code for the same version numbers - I've seen this happen for different Seafile-related packages. The same version tag and associated downloadable blob will give you different code, invalidating the hashes.

Not only is it annoying, it's also not ideal in terms of security. I stopped using Seafile because of this. Apparently I still get notifications from the AUR package, and I'm sad to hear this practice is still going on. Disabling notifications now. Take care, folks!