Package Details: ring-daemon 2:20170814.2.08cfcc0-1

Git Clone URL: (read-only)
Package Base: ring-daemon
Description: is free software for universal communication which respects freedoms and privacy of its users (formerly known as SFLphone)
Upstream URL:
Keywords: audio chat opendht P2P ring video
Licenses: GPL3
Groups: ring
Submitter: xantares
Maintainer: zorun
Last Packager: zorun
Votes: 58
Popularity: 3.657645
First Submitted: 2015-05-07 20:55
Last Updated: 2017-08-15 22:08

Pinned Comments

zorun commented on 2017-05-25 15:14

With all dependencies except pjproject now in [community], it should be much easier to install Ring!

Latest Comments

ImNtReal commented on 2017-07-26 00:49

Can the tarballs on Github be used instead of pulling a specific commit?

ArchangeGabriel commented on 2017-07-22 13:53

OK, I thought the 1.0 milestone was actually a change in releng from CI to milestone release. If it’s just an indicator of reaching some level of features/stability, then going on with the CI seems OK. ;)

Do you know whether asterisk works well with pjproject-savoirfairelinux? If so, maybe it could even make sense to package pjproject in [community] with savoirfairelinux’s patches while they’re being integrated upstream (which make take a very long while).

zorun commented on 2017-07-22 12:12

1.0 actually brings no particular change, so I see no reason to change the current packaging method (follow the weekly releases of upstream's continuous integration process).

As for [community], the main blocker is the custom pjproject lib, but I'm toying with the idea of pushing this to [community] anyway.

ArchangeGabriel commented on 2017-07-21 21:03

I’ve seen 1.0 has been released upstream, so I have two questions:

– do you know if tarballs matching this release will be made available? I’ve seen this directory, but no 1.0 tarball yet. I suppose you’ll move the package to [community] if that happens, but else?
– why not building from this tarball to avoid pulling the whole git tree?


ArchangeGabriel commented on 2017-06-15 09:32

@devurandom (and anyone else affected by the crypto++ bug): zorun fixed the crypto++ bug in 5.6.5-3 ( You can get back to crypto++ from the repos instead of building the -git package from the AUR.

zorun commented on 2017-06-12 21:59

The issue is fixed with dbus-c++ 0.9.0-7.

zorun commented on 2017-06-03 18:43

I spoke too fast, there is still an issue with dbus-c++:

I will look at it next week. But if somebody comes up with a patch, you're welcome :)

zorun commented on 2017-06-03 18:39

Indeed, the build failure was caused by GCC 7, and I just fixed it by bumping to the latest version.

ArchangeGabriel commented on 2017-06-01 15:00

Since zorun actually checks that it compiles, I guess something changed because of GCC7. Can you confirm that zorun?

Did someone reported it upstream?

jerome2016 commented on 2017-05-30 02:44

it is actually not possible to install this package. Failed to compil.
Hope for ring that one day it will be possible to see it install and running and works well.
good luck...

All comments