This bug was fixed in the package rtpproxy - 1.2.1-2.1ubuntu1
---------------
rtpproxy (1.2.1-2.1ubuntu1) vivid; urgency=low
* Merge from Debian unstable. (LP: #1382934) Remaining changes:
- Use dh_autotools-dev to update config.{sub,guess} for new ports.
rtpproxy (1.2.1-2.1) unstable; urgency=medium
* Non-maintainer upload.
* Fix "Daemon does not start as init script points to wrong executable
path":
Since 1.2.1-2, the rtppproxy binary gets installed into /usr/bin instead
of /usr/sbin (due to packaging changes, particularly the removal of
debian/rtpproxy.install).
Adjust the path in debian/rtpproxy.init.
Thanks to Raphael Michel for the bug report.
(Closes: #774584)
-- Jackson Doak <[email protected]> Wed, 14 Jan 2015 21:41:48 +0000
** Changed in: rtpproxy (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382934
Title:
Wrong installation path since trusty release
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtpproxy/+bug/1382934/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
