Your message dated Sat, 19 Jul 2008 13:29:37 +0400 with message-id <[EMAIL PROTECTED]> and subject line Re: Suggestions to improve usability of the package: semi-patch has caused the Debian Bug report #286110, regarding Suggestions to improve usability of the package: semi-patch 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.) -- 286110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286110 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: ejabberd Version: 0.7.5-5 Severity: minor 1) Make it easier to start with ejabberd after installing: a. ask the user at the end of installing the package if he wants to configure an account with admin rights: echo "Do you want to create an admin account for ejabberd? (You also can do this manually.)" yes-no if yes: echo "How do you want to name the account?" read accountname echo "Type in the password for $accountname:" read password echo "Are you sure to proceed?" yes-no if yes: ejabberdctl node register $accountname b. add this line to the default config: {acl, admin, {user, "$accountname"}}. c. echo "Do you want to be registration watcher?" if yes: add "{registration_watchers, ["[EMAIL PROTECTED]"]}." to the config file d. restart ejabberd: ejabberdctl node restart e. display this text: "Now use this account to log in with any Jabber client to do administrative tasks or go to URL:5280/admin/ and log in with this account to enter the admin interface. 2) Comment out the transports entries in the Listened Sockets section: in contrast to Jabberd it doesn't harm if you actually don't have the transports running; in that case they just aren't showed. (ps: Of course the transport packages in Debian should be made server indepandant first: contact me if you want more information about how this can be reached in a stable and easy way). 3) Change Welcome message to: "Welcome!", "Welcome to the Jabber Service on {$servername|this server} powered by ejabberd and Debian." 4) Keep up the good work: the package runs very smooth, even without these suggestions! ;-) -- Mvg, Sander Devrieze. xmpp:[EMAIL PROTECTED] ( http://jabber.l4l.be/ )
pgpxiXY3qaOBC.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---Version: 1.1.4-5 I'm closing this bug because its requirements either are done or aren't to be done ever. > 1) Make it easier to start with ejabberd after installing: > a. ask the user at the end of installing the package if he wants to configure > an account with admin rights: > echo "Do you want to create an admin account for ejabberd? (You also > can do > this manually.)" > yes-no > if yes: echo "How do you want to name the account?" > read accountname > echo "Type in the password for $accountname:" > read password > echo "Are you sure to proceed?" > yes-no > if yes: ejabberdctl node register $accountname > b. add this line to the default config: > {acl, admin, {user, "$accountname"}}. > c. echo "Do you want to be registration watcher?" > if yes: add "{registration_watchers, ["[EMAIL PROTECTED]"]}." to the config file > d. restart ejabberd: ejabberdctl node restart > e. display this text: > "Now use this account to log in with any Jabber client to do administrative > tasks or go to URL:5280/admin/ and log in with this account to enter the > admin interface. Is done (admin account name and warning about web-interface are managed using debhelper, registration is disabled by default (started from 1.1.4-5), so registration watchers aren't necessary). > > 2) Comment out the transports entries in the Listened Sockets section: in > contrast to Jabberd it doesn't harm if you actually don't have the transports > running; in that case they just aren't showed. (ps: Of course the transport > packages in Debian should be made server indepandant first: contact me if you > want more information about how this can be reached in a stable and easy > way). Since there's no transports in Debian which use these ports and since admins are usually very suspicious about unknown open ports on their servers I'll not uncomment them. > > 3) Change Welcome message to: "Welcome!", > "Welcome to the Jabber Service on {$servername|this server} powered by > ejabberd and Debian." The current welcome message is fine for me. Moreover it isn't showed to users if the registration is switched off. -- Sergei Golovan
--- End Message ---
