Search Criteria
Package Details: libsearpc 2:3.3.0-1
Package Actions
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: | 85 |
Popularity: | 0.000055 |
First Submitted: | 2013-01-19 15:50 (UTC) |
Last Updated: | 2022-11-14 18:24 (UTC) |
Latest Comments
1 2 3 4 5 6 7 Next › Last »
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!
languitar commented on 2020-03-25 14:34 (UTC)
And the hash is invalid again :/
sjoerdos commented on 2020-03-24 13:07 (UTC)
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 (UTC) (edited on 2020-03-21 17:52 (UTC) by illspirit)
matejdro commented on 2020-03-21 10:36 (UTC)
Build fails with:
DasGurke commented on 2019-11-15 11:55 (UTC)
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 (UTC)
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.
1 2 3 4 5 6 7 Next › Last »