Your message dated Thu, 11 Jul 2013 15:09:10 +0000 with message-id <[email protected]> and subject line Bug#710532: fixed in rfc5766-turn-server 1.8.7.0-1 has caused the Debian Bug report #710532, regarding rfc5766-turn-server: broken synopsis 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.) -- 710532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710532 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: rfc5766-turn-server Version: 1.8.4.2-1 Severity: normal Tags: patch The package synopsis is broken between the short description line and the long description (in a manner specifically forbidden in Debian Policy 3.4.2, so I'm treating this as worse than my usual "Severity: wishlist"). Even with that fixed it's hard to work out what it's trying to say. # Description: server for ICE/STUN/TURN, NAT traversal for VoIP and # WebRTC. [...] Synopsis problem one: the word "WebRTC" has fallen off the end. Synopsis problem two: is the package claiming to be 1) a server (for ICE, or STUN, or TURN), and 2) a NAT traversal for VOIP and WebRTC? Or is it maybe claiming to be a server for 1) ICE, a.k.a. STUN, a.k.a. TURN, 2) NAT traversal for VoIP, and 3) WebRTC? Or maybe... various other valid parsings. Synopsis problem three: ICE is the cover-term for the framework that can make use of STUN and/or TURN, so it makes no particular sense to talk about "ICE/STUN/TURN". In fact I would recommend just not mentioning ICE at all; for anybody who recognises the terms STUN and TURN it's pretty much completely redundant, and for anybody who doesn't it's an extra unexplained acronym. It seems to me you'd be better off with something like: Description: NAT traversal server using STUN/TURN (Or if you really insist on the ICE it could be something like Description: NAT traversal ICE server using STUN/TURN but that's not in my patch.) # Free open source implementation of TURN Server / STUN Server / # Network Traffic Gateway More problems. * This should be an introductory sentence, not a sentence fragment. * It's all very well for the upstream homepage to drone on and on about how this is a free open source implementation of something or other, but Debian packages can take all that for granted. * On the other hand this is where the expansions of STUN and TURN would fit nicely. * There's no particular reason for all this capitalisation; and "Network Traffic Gateway" doesn't even exist as jargon - Google says the homepage for this software is the only place using the expression. * The constant use of slashes to mean nothing in particular isn't helping either. * Missing period. # The TURN Server is a VoIP media traffic NAT # traversal server and gateway. It can be used as a general-purpose # network traffic TURN server/gateway, too. # [...] >From here on it settles down a bit, but there are still one or two relatively trivial issues (such as missing or surplus articles) that I'll fix while I'm patching the description. My revised description, in full: | Description: NAT traversal server using STUN/TURN | STUN (Session Traversal Utilities for NAT) and TURN (Traversal Using Relays | around NAT) are protocols that can be used to provide NAT traversal for VoIP | and WebRTC. This package provides a VoIP media traffic NAT traversal server | and gateway which can be used as a general-purpose network traffic TURN | server/gateway, too. | . | This implementation also includes some extra features. | . | Supported RFCs: | TURN specs: | * RFC 5766 - base TURN specs; | * RFC 6062 - TCP relaying TURN extension; | * RFC 6156 - IPv6 extension for TURN; | * Experimental DTLS support as client protocol. | STUN specs: | * RFC 5389 - base "new" STUN specs; | * RFC 5769 - test vectors for STUN protocol testing; | * RFC 5780 - NAT behavior discovery support. | . | The implementation fully supports UDP, TCP, TLS, and DTLS as protocols between | the TURN client and the TURN server. Both UDP and TCP relaying are supported. | . | Flat files, MySQL, PostgreSQL, or Redis are all supported for the user | repository (if authentication is required). | Both short-term and long-term credentials mechanisms are supported. | For WebRTC applications, the TURN server REST API for time-limited | secret-based authentication is implemented. | . | Load balancing can be implemented either by external networking tools, or by | the built-in ALTERNATE-SERVER mechanism. | . | The implementation is intended to be simple to install and configure. | The project focuses on performance, scalability, and simplicity. | The aim is to provide an enterprise-grade TURN solution. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.8-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rfc5766-turn-server depends on: ii adduser 3.113+nmu3 ii libc6 2.17-3 ii libevent-2.0-5 2.0.21-stable-1 ii libevent-openssl-2.0-5 2.0.21-stable-1 ii libevent-pthreads-2.0-5 2.0.21-stable-1 ii libhiredis0.10 0.10.1-7 ii libmysqlclient18 5.5.31+dfsg-1 ii libpq5 9.1.9-1 ii libssl1.0.0 1.0.1e-2 rfc5766-turn-server recommends no packages. rfc5766-turn-server suggests no packages. -- no debconf information -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular packagediff -ru rfc5766-turn-server-1.8.4.2.pristine/debian/control rfc5766-turn-server-1.8.4.2/debian/control --- rfc5766-turn-server-1.8.4.2.pristine/debian/control 2013-05-16 01:54:50.000000000 +0100 +++ rfc5766-turn-server-1.8.4.2/debian/control 2013-05-31 17:43:42.483892867 +0100 @@ -17,37 +17,38 @@ Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends}, adduser Conflicts: turnserver -Description: server for ICE/STUN/TURN, NAT traversal for VoIP and - WebRTC. Free open source implementation of TURN Server / STUN Server / - Network Traffic Gateway The TURN Server is a VoIP media traffic NAT - traversal server and gateway. It can be used as a general-purpose - network traffic TURN server/gateway, too. +Description: NAT traversal server using STUN/TURN + STUN (Session Traversal Utilities for NAT) and TURN (Traversal Using Relays + around NAT) are protocols that can be used to provide NAT traversal for VoIP + and WebRTC. This package provides a VoIP media traffic NAT traversal server + and gateway which can be used as a general-purpose network traffic TURN + server/gateway, too. . This implementation also includes some extra features. . Supported RFCs: TURN specs: - * RFC 5766 - base TURN specs - * RFC 6062 - TCP relaying TURN extension - * RFC 6156 - IPv6 extension for TURN + * RFC 5766 - base TURN specs; + * RFC 6062 - TCP relaying TURN extension; + * RFC 6156 - IPv6 extension for TURN; * Experimental DTLS support as client protocol. STUN specs: - * RFC 5389 - base "new" STUN specs - * RFC 5769 - test vectors for STUN protocol testing - * RFC 5780 - NAT behavior discovery support + * RFC 5389 - base "new" STUN specs; + * RFC 5769 - test vectors for STUN protocol testing; + * RFC 5780 - NAT behavior discovery support. . - The implementation fully supports UDP, TCP, TLS and DTLS as protocols between - the TURN client and the TURN Server. Both UDP and TCP relaying are supported. + The implementation fully supports UDP, TCP, TLS, and DTLS as protocols between + the TURN client and the TURN server. Both UDP and TCP relaying are supported. . - Flat files, MySQL, PostgreSQL or Redis are all supported for the user - repository (if authentication is required). - Both short-term and long-term credentials mechanisms are supported. - For WebRTC applications, TURN Server REST API for time-limited secret-based - authentication is implemented. + Flat files, MySQL, PostgreSQL, or Redis are all supported for the user + repository (if authentication is required). + Both short-term and long-term credentials mechanisms are supported. + For WebRTC applications, the TURN server REST API for time-limited + secret-based authentication is implemented. . - The load balancing can be implemented either by external networking tools, - or by the built-in ALTERNATE-SERVER mechanism. + Load balancing can be implemented either by external networking tools, or by + the built-in ALTERNATE-SERVER mechanism. . - The implementation is supposed to be simple, easy to install and configure. - The project focuses on performance, scalability and simplicity. + The implementation is intended to be simple to install and configure. + The project focuses on performance, scalability, and simplicity. The aim is to provide an enterprise-grade TURN solution.
--- End Message ---
--- Begin Message ---Source: rfc5766-turn-server Source-Version: 1.8.7.0-1 We believe that the bug you reported is fixed in the latest version of rfc5766-turn-server, 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. Oleg Moskalenko <[email protected]> (supplier of updated rfc5766-turn-server 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: SHA256 Format: 1.8 Date: Thu, 22 Jun 2013 22:50:46 -0700 Source: rfc5766-turn-server Binary: rfc5766-turn-server Architecture: source amd64 Version: 1.8.7.0-1 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team <[email protected]> Changed-By: Oleg Moskalenko <[email protected]> Description: rfc5766-turn-server - TURN and STUN server for VoIP Closes: 710532 Changes: rfc5766-turn-server (1.8.7.0-1) unstable; urgency=low . * (closes: #710532) extra fixes; * Classic STUN RFC 3489 support; * Upstream Makefile fixed; * configure script fixed; * custom configure rule removed from the rules file; * manpage <project-name> added; Checksums-Sha1: 430a35c484b1e0c8983f6a432abb39fcfbfa4bc2 2242 rfc5766-turn-server_1.8.7.0-1.dsc 426feafbcc9c11e41f324e9f06a159e9b8fa29df 211160 rfc5766-turn-server_1.8.7.0.orig.tar.gz 82d5094081d27cc1addac4eaee15f60b8165f587 8120 rfc5766-turn-server_1.8.7.0-1.debian.tar.gz f1275295c5f5f04729a3aef907e47c891dcf991a 282002 rfc5766-turn-server_1.8.7.0-1_amd64.deb Checksums-Sha256: 0ac431f55a2daec6ec387501cb7c6a2a8174b9ab5b369416de29d888f3c2b3f8 2242 rfc5766-turn-server_1.8.7.0-1.dsc a04a0011e3120c1d2b6b3b8a6fb177c3761aa8396a5950f6b405f102a0b23ec2 211160 rfc5766-turn-server_1.8.7.0.orig.tar.gz 913b7e8fac533b07fe0e5701ec1399ecd0f9d2c3c4aca0baa2c75479c75e1722 8120 rfc5766-turn-server_1.8.7.0-1.debian.tar.gz f98f87a3fa7f8119fa866781c59f19f61c8760d7acbb11685d018d8c0eed5cd8 282002 rfc5766-turn-server_1.8.7.0-1_amd64.deb Files: 316fe54aa67295433a9a8c4b8a71d7e0 2242 net extra rfc5766-turn-server_1.8.7.0-1.dsc 6a4104999377d3ecaa5410377b94e9f9 211160 net extra rfc5766-turn-server_1.8.7.0.orig.tar.gz 76cecb77800aadb5542097136fcc8b5b 8120 net extra rfc5766-turn-server_1.8.7.0-1.debian.tar.gz 7027e2f9420ca765ad7e2f43eb84dc67 282002 net extra rfc5766-turn-server_1.8.7.0-1_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJR3roqAAoJEOm1uwJp1aqDveEP/0+YVfazCCPU3FKzQPp7UVwF sXDg/OostlxUxH7EVIqFD+FYJB9VmAw/t5qWT+OYhjnivPh8lZOVwpWgk6yS/Ppz g5pewovqn6HgSbGkZLOGCQQRcwnFPgJs3I9IXLUaABjenwsMtPw9XCuI1Dvden84 SJ3/u7tIvGCyY/045zYgXIb+PDfxfTGHs/W1PuiwYvVV3R3uByBHfGDvawyzabPZ zdN6cvEGqs4/ojxHJIQK+Jzrp6Qy/VIyRlR6hUfHVTpRwhtbwFyvn3Db8DU/c6YC j52OKkpNHmuUc0gs3MxOETtreWfbnKU3RdR7GHHg734ztsvPdGmAMer6N7dBFqCX CLJ4xCckGjg6DQQ3p+UimxrlRDr+Tb4FLolTAayhhIoCloFLjKj7LaXyOJvRQDTt iQcvVafcFJPYgEjl8efwjImcDNxr1bxUE2HBsgFSHdzw50lA0w1z2wO4HcEblV7y 41q/prLO58/uaJPNJFcSIA+QtTWwXKavtkXPQZrpGsQFYiZ2joKOj9ae9SOMyQ37 a2P3CKlVC76z/uW2jC7jNgtDZ88uzLWzTFr1AvdvQs2dRwH/urDbQT8GBQwZLYQv o+v3sMXPmUj2/nnAR5rnHI2QppyRRnTAT1W+8E3cGNpko5hcR5kaOFdmyx+PGZoC 6a+mssVKOPKJQ5ysXHy3 =iCKh -----END PGP SIGNATURE-----
--- End Message ---
