Re: HELP: Fixing a debconf bug in proftpd
On 28.11.2016 21:24, Hilmar Preuße wrote:
Hi,
> we got bug #820984 on debconf a while ago. I'm not very familiar w/
> debconf, hence I had a look into the templates/config delivered w/
> debconf itself.
> I'm my eyes the code in proftpd is about a 1:1 copy of the code in
> debconf, nevertheless it does not work as expected.
>
> 1. Would anybody so kind to have a look at this issue? It is our show
> stopper to get back into testing.
>
We're back in testing, but marked for autoremoval again. Would anybody
be so kind to have a look at this? Attached is the config and the
templates file. Many thanks!
> 2. Is that bug even RC or could we lower it to important and address it
> once we're back in testing?
>
At least this question is answered: it is an RC bug.
Hilmar
--
http://www.hilmar-preusse.de.vu/ #206401 http://counter.li.org
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-english@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.
Template: shared/proftpd/inetd_or_standalone
Type: select
__Choices: from inetd, standalone
Default: standalone
_Description: Run proftpd:
ProFTPD can be run either as a service from inetd, or as a standalone
server. Each choice has its own benefits. With only a few FTP
connections per day, it is probably better to run ProFTPD from inetd in
order to save resources.
.
On the other hand, with higher traffic,
ProFTPD should run as a standalone server to avoid spawning a new
process for each incoming connection.
#!/bin/sh
set -e
# Source debconf library.
. /usr/share/debconf/confmodule
action=$1
version=$2
db_title ProFTPD configuration
db_set shared/proftpd/inetd_or_standalone standalone
db_input high shared/proftpd/inetd_or_standalone || true
db_go || true
Reply to: