Package Details: libsearpc 2:3.2.0-4

Git Clone URL: https://aur.archlinux.org/libsearpc.git (read-only, click to copy)
Package Base: libsearpc
Description: A simple C language RPC framework (including both server side & client side)
Upstream URL: https://github.com/haiwen/libsearpc
Licenses: Apache
Submitter: aclindsa
Maintainer: thealchemist (Joffrey)
Last Packager: Joffrey
Votes: 84
Popularity: 0.65
First Submitted: 2013-01-19 15:50
Last Updated: 2020-03-24 13:58

Latest Comments

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

urldog commented on 2020-09-18 14:19

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

The "new" hash for the 3.2.0 version is 

c479d85e405674c3450eac040abe143af5a9fafe7f1b74926e2a05280ab5420e

tilx commented on 2020-03-25 15:17

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!

languitar commented on 2020-03-25 14:34

And the hash is invalid again :/

sjoerdos commented on 2020-03-24 13:07

Dear maintainer, please update the sha256sum in the PKGBUILD.

If I change it to

cd00197fcc40b45b1d5e892b2d08dfa5947f737e0d80f3ef26419334e75b0bff

the package installs just fine

illspirit commented on 2020-03-21 17:51 

==> Making package: libsearpc 2:3.2.0-3 (Sat 21 Mar 2020 12:40:01 PM CDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources... 
  -> Found libsearpc-3.2.0.tar.gz
==> Validating source files with sha256sums...
    libsearpc-3.2.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

matejdro commented on 2020-03-21 10:36

Build fails with:

==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found libsearpc-3.2.0.tar.gz
==> Validating source files with sha256sums...
    libsearpc-3.2.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
Failed to build libsearpc

DasGurke commented on 2019-11-15 11:55

Oh, I just recognized that upstream has no issue tracker. Does maybe one of the maintainers here have a possibility to reach upstream?

DasGurke commented on 2019-11-15 11:49

There seems to be a Python 2 incompatability with libsearpc. For me Seahub has stopped working, as described at https://aur.archlinux.org/packages/seahub/#comment-715880

There is a proposed workaround at https://forum.seafile.com/t/unable-to-reset-admin-with-python-2-7/10030/3 , but monkey-patching the Python 2.7 core libraries doesn't seem like something a sane person should do.

tilx commented on 2019-07-19 20:07

The latest update broke the version progression by going back from 3.1.0, pkgrel=2 to ver 3.1, pkgrel=1. Now it looks like my installed version is newer:

-> libsearpc: local (1:3.1.0-2) is newer than AUR (1:3.1-1)

Looking at the current release, we're actually on 3.1-latest, which doesn't seem to be a fixed tag, but might change what commit it references. This means that the same version/rel of this AUR package might point at different code at different times, which will also suddenly break the checksums without notice.

Wouldn't it make sense to wait/push for an official, properly tagged release before updating this package?