Search Criteria
Package Details: libsearpc 2:3.3.0-4
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: | 88 |
Popularity: | 0.054474 |
First Submitted: | 2013-01-19 15:50 (UTC) |
Last Updated: | 2024-05-09 09:16 (UTC) |
Dependencies (5)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- jansson (jansson-gitAUR)
- python-gobject
- python-simplejson
- git (git-gitAUR, git-glAUR) (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »
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.
tilx commented on 2019-07-19 20:07 (UTC) (edited on 2019-07-19 20:15 (UTC) by tilx)
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:
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?
eolianoe commented on 2018-12-14 18:52 (UTC)
@flying-sheep: python2 will still be needed to build the package so for now you cannot get rid of it :(
flying-sheep commented on 2018-12-12 14:53 (UTC) (edited on 2018-12-12 15:26 (UTC) by flying-sheep)
Could you please make the python2 deps optional or split off a python-searpc package? I’d like to get rid of python2 on my system.
eolianoe commented on 2017-09-03 14:55 (UTC)
« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »