Please find, for review, the debconf templates and packages descriptions for the ejabberd source package.
This review will last from Wednesday, July 08, 2015 to Saturday, July 18, 2015. Please send reviews as unified diffs (diff -u) against the original files. Comments about your proposed changes will be appreciated. Your review should be sent as an answer to this mail. When appropriate, I will send intermediate requests for review, with "[RFRn]" (n>=2) as a subject tag. When we will reach a consensus, I send a "Last Chance For Comments" mail with "[LCFC]" as a subject tag. Finally, a summary will be sent to the review bug report, and a mail will be sent to this list with "[BTS]" as a subject tag. Rationale: --- ejabberd.old/debian/templates 2015-06-24 09:13:56.949463781 +0200 +++ ejabberd/debian/templates 2015-07-08 06:48:44.067323570 +0200 @@ -1,41 +1,45 @@ Template: ejabberd/hostname Type: string Default: localhost -_Description: The name of the host ejabberd will serve: - Please enter the hostname of your Jabber server (in lowercase). +_Description: Host name for this Jabber server: + Please enter the host name of this Jabber server (lowercase). Tempaltes synopsis should rather be prompts than full sentences.... Template: ejabberd/user Type: string -_Description: The username of an admin account for ejabberd: +_Description: Jabber server administrator username: Ditto Please provide the name of an account to administrate the ejabberd server. After the installation of ejabberd you can use this account to log in with any Jabber client to do administrative tasks or go to http://${hostname}:5280/admin/ and log in with this account to enter the admin - interface. Enter the username part here (e.g. ${user}), but use the full Jabber - ID (e.g. ${user}@${hostname}) to log into ejabberd web interface; otherwise it - will fail. + interface. . - Leave empty if you don't want to create an admin account automatically. + You only need to enter the username part here (such as ${user}), but + need to use the full Jabber ID (such as ${user}@${hostname}) to + access the ejabberd web interface. + . + Please leave this field empty if you don't want to create an + administrator account automatically. First paragraph split in two paragraphs for readability. Drop the "otherwise it will fail" part, that seems useless to me (if you enter something wrong, the, yes things fail). Template: ejabberd/password Type: password -_Description: The password for the admin account: +_Description: Jabber server administrator password: Please enter the password for the administrative user. Prompt.... Template: ejabberd/verify Type: password -_Description: The password for the admin account again for verification: - Please reenter the password for the administrative user for verification. +_Description: Re-enter password to verify: + Please enter the same administrator password again to verify that you have typed it + correctly. This wording is the one we propose for all such templates Template: ejabberd/nomatch Type: error -_Description: The passwords do not match! - The passwords you have typed do not match. Please try again. +_Description: Password input error + The two passwords you entered were not the same. Please try again. Ditto Template: ejabberd/invaliduser Type: error -_Description: The username of the admin account is invalid! +_Description: Invalid administrator account username The username you have typed contains forbidden characters. Please respect the JID syntax (http://tools.ietf.org/html/rfc6122#appendix-A.5). If you used - a full JID (e.g. user@hostname), you have to use the same hostname - you typed into the hostname configuration step. + a full JID (e.g. user@hostname), you have to use the same host name + you typed into the host name configuration step. Don't use exclamation marks and do not make a sentence but more a "title" for the synopsis. --
Template: ejabberd/hostname Type: string Default: localhost _Description: Host name for this Jabber server: Please enter the host name of this Jabber server (lowercase). Template: ejabberd/user Type: string _Description: Jabber server administrator username: Please provide the name of an account to administrate the ejabberd server. After the installation of ejabberd you can use this account to log in with any Jabber client to do administrative tasks or go to http://${hostname}:5280/admin/ and log in with this account to enter the admin interface. . You only need to enter the username part here (such as ${user}), but need to use the full Jabber ID (such as ${user}@${hostname}) to access the ejabberd web interface. . Please leave this field empty if you don't want to create an administrator account automatically. Template: ejabberd/password Type: password _Description: Jabber server administrator password: Please enter the password for the administrative user. Template: ejabberd/verify Type: password _Description: Re-enter password to verify: Please enter the same administrator password again to verify that you have typed it correctly. Template: ejabberd/nomatch Type: error _Description: Password input error The two passwords you entered were not the same. Please try again. Template: ejabberd/invaliduser Type: error _Description: Invalid administrator account username The username you have typed contains forbidden characters. Please respect the JID syntax (http://tools.ietf.org/html/rfc6122#appendix-A.5). If you used a full JID (e.g. user@hostname), you have to use the same host name you typed into the host name configuration step.
--- ejabberd.old/debian/templates 2015-06-24 09:13:56.949463781 +0200 +++ ejabberd/debian/templates 2015-07-08 06:48:44.067323570 +0200 @@ -1,41 +1,45 @@ Template: ejabberd/hostname Type: string Default: localhost -_Description: The name of the host ejabberd will serve: - Please enter the hostname of your Jabber server (in lowercase). +_Description: Host name for this Jabber server: + Please enter the host name of this Jabber server (lowercase). Template: ejabberd/user Type: string -_Description: The username of an admin account for ejabberd: +_Description: Jabber server administrator username: Please provide the name of an account to administrate the ejabberd server. After the installation of ejabberd you can use this account to log in with any Jabber client to do administrative tasks or go to http://${hostname}:5280/admin/ and log in with this account to enter the admin - interface. Enter the username part here (e.g. ${user}), but use the full Jabber - ID (e.g. ${user}@${hostname}) to log into ejabberd web interface; otherwise it - will fail. + interface. . - Leave empty if you don't want to create an admin account automatically. + You only need to enter the username part here (such as ${user}), but + need to use the full Jabber ID (such as ${user}@${hostname}) to + access the ejabberd web interface. + . + Please leave this field empty if you don't want to create an + administrator account automatically. Template: ejabberd/password Type: password -_Description: The password for the admin account: +_Description: Jabber server administrator password: Please enter the password for the administrative user. Template: ejabberd/verify Type: password -_Description: The password for the admin account again for verification: - Please reenter the password for the administrative user for verification. +_Description: Re-enter password to verify: + Please enter the same administrator password again to verify that you have typed it + correctly. Template: ejabberd/nomatch Type: error -_Description: The passwords do not match! - The passwords you have typed do not match. Please try again. +_Description: Password input error + The two passwords you entered were not the same. Please try again. Template: ejabberd/invaliduser Type: error -_Description: The username of the admin account is invalid! +_Description: Invalid administrator account username The username you have typed contains forbidden characters. Please respect the JID syntax (http://tools.ietf.org/html/rfc6122#appendix-A.5). If you used - a full JID (e.g. user@hostname), you have to use the same hostname - you typed into the hostname configuration step. + a full JID (e.g. user@hostname), you have to use the same host name + you typed into the host name configuration step.
Source: ejabberd
Section: net
Priority: optional
Maintainer: Konstantin Khomoutov <flatw...@users.sourceforge.net>
Uploaders: Gerfried Fuchs <rho...@debian.org>, Philipp Huebner
<debala...@debian.org>
Build-Depends: debhelper (>= 9),
erlang-asn1, erlang-base, erlang-crypto, erlang-dev (>= 1:15.b),
erlang-eunit, erlang-inets, erlang-lager, erlang-jiffy, erlang-mnesia,
erlang-parsetools,
erlang-p1-cache-tab, erlang-p1-iconv, erlang-p1-mysql,
erlang-p1-pam, erlang-p1-pgsql, erlang-p1-sip, erlang-p1-stringprep,
erlang-p1-stun,
erlang-p1-tls, erlang-p1-utils, erlang-p1-xml, erlang-p1-yaml,
erlang-p1-zlib,
erlang-redis-client, erlang-ssl, erlang-xmlrpc,
hevea, po-debconf, rebar, texlive-latex-base,
texlive-latex-recommended, texlive-latex-extra
Standards-Version: 3.9.6
Homepage: https://www.ejabberd.im
Vcs-Git: git://git.deb.at/pkg/ejabberd.git
Vcs-Browser: http://git.deb.at/w/pkg/ejabberd.git
Package: ejabberd
Architecture: any
Depends: adduser, erlang-base (>= 1:15.b) | ${erlang-abi:Depends},
${erlang:Depends}, openssl, ucf, ${misc:Depends}, ${shlibs:Depends},
erlang-lager, erlang-jiffy, erlang-p1-cache-tab,
erlang-p1-iconv, erlang-p1-mysql, erlang-p1-pam, erlang-p1-pgsql,
erlang-p1-sip, erlang-p1-stringprep,
erlang-p1-stun, erlang-p1-tls, erlang-p1-utils, erlang-p1-xml,
erlang-p1-yaml, erlang-p1-zlib, erlang-redis-client, erlang-xmlrpc
Recommends: ejabberd-contrib
Suggests: libunix-syslog-perl, imagemagick | graphicsmagick-imagemagick-compat
Conflicts: ejabberd-mod-shared-roster-ldap
Provides: xmpp-server
Description: distributed, fault-tolerant Jabber/XMPP server written in Erlang
ejabberd is a distributed, fault-tolerant Jabber/XMPP server written in Erlang.
Its features contain:
- XMPP-compliant
- Web based administration
- Load balancing: can run in a cluster of machines
- Fault-tolerance: database can be replicated and stored on multiple
nodes (nodes can be added or replaced 'on the fly')
- Virtual hosting: several virtual domains can be served using single ejabberd
instance
- SSL/TLS support
- Multi-User Chat (MUC/conference)
- IRC transport
- Jabber Users Directory, based on users vCards
- Service Discovery
- Shared roster
signature.asc
Description: Digital signature
