Your message dated Wed, 14 Jan 2015 18:48:33 +0000
with message-id <[email protected]>
and subject line Bug#774584: fixed in rtpproxy 1.2.1-2.1
has caused the Debian Bug report #774584,
regarding rtpproxy: Deamon does not start as init script points to wrong
executable path
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
774584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774584
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rtpproxy
Version: 1.2.1-1
Severity: grave
Dear Maintainer,
on my system, rtpproxy does not start. I believe the reason is that the
init script contains
DAEMON=/usr/sbin/$NAME
but the binary only exists in /usr/bin. Changing this line in the init
script to
DAEMON=/usr/bin/$NAME
makes the deamon work on my system.
Best regards,
Raphael
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages rtpproxy depends on:
ii adduser 3.113+nmu3
ii libc6 2.19-13
rtpproxy recommends no packages.
Versions of packages rtpproxy suggests:
pn ser | openser <none>
-- Configuration Files:
/etc/default/rtpproxy changed [not included]
/etc/init.d/rtpproxy changed [not included]
-- no debconf information
pgpB4wY8KJVor.pgp
Description: Digitale Signatur von OpenPGP
--- End Message ---
--- Begin Message ---
Source: rtpproxy
Source-Version: 1.2.1-2.1
We believe that the bug you reported is fixed in the latest version of
rtpproxy, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann <[email protected]> (supplier of updated rtpproxy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 12 Jan 2015 19:24:48 +0100
Source: rtpproxy
Binary: rtpproxy
Architecture: source
Version: 1.2.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team <[email protected]>
Changed-By: gregor herrmann <[email protected]>
Description:
rtpproxy - Relay for Real-time Transport Protocol (RTP) media streams
Closes: 774584
Changes:
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)
Checksums-Sha1:
17255948da910dfed4f87773a8326178340af1a4 2138 rtpproxy_1.2.1-2.1.dsc
8b085394f3aaad4cc9a5646bcfe9a1be1742a9d2 5376 rtpproxy_1.2.1-2.1.debian.tar.xz
Checksums-Sha256:
11885e4b9b6cbcfbc9c0cb3e9957ab3517ff3a605a00ff9aee6004ab2cc7ab55 2138
rtpproxy_1.2.1-2.1.dsc
928475423f2f233386443af8848d3e977b54315d73645f99e7268a5a1df70464 5376
rtpproxy_1.2.1-2.1.debian.tar.xz
Files:
79263ba8e4f7651b9b5539a4c2d7ce6b 2138 net optional rtpproxy_1.2.1-2.1.dsc
25057b0bec1a019d1d62b21e08fa9bb2 5376 net optional
rtpproxy_1.2.1-2.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQJ8BAEBCgBmBQJUtBJEXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGRPoP/RBXG8YTP2CnDV6V//og+cuE
ROSv0Q5nMJ6ptOkT+VnLOAGUNlYPGSKOaaDPbkaLGlSKhTQh6mlzRDUJuB1g/3Bc
h6WU8QwcK+Mf4ETAR2wt4gIQCgfAyxBocAi9WjKGGstrGRjw5+9iwjRuTQagtO7k
AUyaK9ABrh4XfGKaIBYOxcMpAkDPIm4PC3KQWOResuoMW4QmBHX4Nwvnu+/Zx1Dz
afWxuNHjOSWhjLndMJ4SgAwwuzyZtEM8Xy+0dkdLE7GpZ+9/uGAshv+6Nt5DPnbF
+M+mQxforv/mCbCHLv5UNd2eHoFSGLfomh0IDTLLWIDFn37w6/iNxXbVKeGWzF5F
25TLeU4tE2080otVIBFU92uMyd5StekApW6Rp1jtao7/JkBPGxibix25iRddKKsu
hpCKGdQxL45lgODwLi4vqu7lIVGbHoJefn2oVMprH+gDnwBuJCEOqHFObhlBun/Z
J63guL8AbJMZKjHMU7FKSb9ld72LSKuR+qESne4WBtHwH3DxOThBXTBqrzh+i6Z4
WbYv0TNji1zYR4eb0vKPTywsJ+g8gZO0GGUHPsdx8K0/uv4noQ/GTySZkgdy+Va3
kUm/eM+H6tss+coXDnPBOrcC2lE06MKLRNFUtET1lLtp3Qbtrq2VdGsmGsMhfJoO
CWoNtR9ggFNkl4lFaE4R
=NLop
-----END PGP SIGNATURE-----
--- End Message ---
