Bug#489136: rtpproxy: installation fails
marcus at better.se
Tue Aug 12 07:58:03 UTC 2008
-----BEGIN PGP SIGNED MESSAGE-----
owner 489136 !
Faidon Liambotis wrote:
> Wasn't that fixed in r5916?
That fixed the ownership of the control socket, but it remains to make
it group writable. Currently it looks like:
~$ ls -l /var/run/rtpproxy
- -rw-r--r-- 1 root root 6 2008-08-12 09:49 rtpproxy.pid
srwxr-xr-x 1 rtpproxy rtpproxy 0 2008-08-12 09:49 rtpproxy.sock=
~$ ls -ld /var/run/rtpproxy
drwxr-xr-x 2 rtpproxy rtpproxy 1024 2008-08-12 09:49 /var/run/rtpproxy/
Upstream doesn't want to change this in rtpproxy but suggests to handle
it with an umask. We should just change the init script to do it.
> If so, shouldn't the current version be uploaded to Debian?
Yes, even the current version could be uploaded since it fixes this bug.
But I would much prefer to fix the permissions also since that will
allow it to work out of the box with SER (which in 2.0 packages will
belong to group rtpproxy, which is the whole point of this exercise).
I plan to work on it this week since I need it for my work.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Pkg-voip-maintainers