Re: Bug#710876: [LCFC] templates://ircd-hybrid/{ircd-hybrid.templates}
On Tue, Jun 18, 2013 at 10:24:00AM +0200, Christian PERRIER wrote:
> This is the last call for comments for the review of debconf
> templates for ircd-hybrid.
>
> The reviewed templates will be sent on Thursday, June 20, 2013 to this bug report
> and a mail will be sent to this list with "[BTS]" as a subject tag.
Thanks. I have attached an updated template; I'd apparently failed to
remove the unused no-more-ssl template, and I've rephrased the comment
about Anope to make more sense.
Dominic
Template: ircd-hybrid/restart_on_upgrade
Type: boolean
Default: true
_Description: Restart ircd-hybrid on each upgrade?
Please choose whether the ircd-hybrid daemon should be restarted
every time a new version of this package is installed.
.
Automatic restarts may be problematic if, for instance, the server is
running with manually loaded modules, which will need to be reloaded
after the restart.
.
If you reject this option, you will have to restart ircd-hybrid via
"service ircd-hybrid restart" when needed.
Template: ircd-hybrid/upgrade_secure_links_warn
Type: boolean
Default: true
_Description: Upgrade ircd-hybrid to version without cryptlink support?
The 8.x version of ircd-hybrid includes a change to the way secure server
links are implemented, which is not backwards-compatible with ircd-hybrid 7.x,
from which you are upgrading.
.
If you have any secure server links (cryptlinks) configured with this
server, you should plan to either upgrade all servers in lock-step, or
temporarily configure non-cryptlink server links, to ensure the continuity
of your IRC links.
Template: ircd-hybrid/upgrade_no_services_warn
Type: boolean
Default: true
_Description: Upgrade ircd-hybrid to version without compatible services?
The 8.x version of ircd-hybrid includes a change to the way services are
supported, losing compatibility with hybserv.
.
The recommended services daemon for Hybrid 8 is Anope, but this is not yet
available in Debian. It is planned is to provide such a package in future.
Reply to: