[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[LCFC] templates://ejabberd/{templates}



This is the last call for comments for the review of debconf
templates for ejabberd.

The reviewed templates will be sent on Tuesday, July 21, 2015 to this bug report
and a mail will be sent to this list with "[BTS]" as a subject tag.


-- 


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
 the full Jabber ID (such as ${user}@${hostname}) is required 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.
Source: ejabberd
Section: net
Priority: optional
Maintainer: Konstantin Khomoutov <flatworm@users.sourceforge.net>
Uploaders: Gerfried Fuchs <rhonda@debian.org>, Philipp Huebner <debalance@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
 ejabberd is a Jabber/XMPP server written in Erlang, featuring:
  * distributed operation with load-balancing across a cluster;
  * fault-tolerant database replication and storage on multiple nodes,
    allowing nodes to be added or replaced "on the fly";
  * virtual hosting (several virtual domains can be served using a single
    ejabberd instance);
  * XMPP compliance;
  * web-based administration;
  * SSL/TLS support;
  * conferencing via Multi-User Chat;
  * IRC transport;
  * Jabber Users Directory, based on users' vCards;
  * service discovery;
  * shared roster.

Attachment: signature.asc
Description: Digital signature


Reply to: