- Package:
- proftpd-basic
- Source:
- proftpd-dfsg
- Submitter:
- David Baron
- Date:
- 2011-10-06 11:21:20 UTC
- Severity:
- wishlist
--- Please enter the report below this line. ---
The new conf file has module includes, maditory as of version 1.3.
The daemon will not start because each of these is "already included/operation
not permitted."
Comment the first one, the second one becomes the error and so forth.
Workaround is, of course, to comment all of them until they truly become
necessary.
Debian Release: wheezy/sid
990 unstable www.debian-multimedia.org
990 unstable liquorix.net
990 unstable http.us.debian.org
990 unstable debian.tagancha.org
990 unstable debian.scribus.net
990 unstable debian.pengutronix.de
650 testing security.debian.org
650 testing http.us.debian.org
650 testing dl.google.com
500 stable security.debian.org
500 stable http.us.debian.org
500 stable deb.opera.com
500 karmic ppa.launchpad.net
500 intrepid ppa.launchpad.net
101 experimental-snapshots qt-kde.debian.net
1 experimental debian.co.il
--- Package information. ---
Depends (Version) | Installed
=================================-+-===============
netbase (>= 4.13) | 4.46
libacl1 (>= 2.2.51-3) | 2.2.51-3
libc6 (>= 2.3.4) | 2.13-18
libcap2 (>= 2.10) | 1:2.22-1
libncurses5 (>= 5.5-5~) | 5.9-1
libpam0g (>= 0.99.7.1) | 1.1.3-2
libssl1.0.0 (>= 1.0.0) | 1.0.0d-3
libwrap0 (>= 7.6-4~) | 7.6.q-21
zlib1g (>= 1:1.1.4) | 1:1.2.3.4.dfsg-3
debconf (>= 0.5.00) | 1.5.41
adduser | 3.113
ucf (>= 0.30) | 3.0025+nmu2
debianutils (>= 1.21.0) | 4.0.2
libpam-runtime (>= 0.76-13.1) | 1.1.3-2
sed (>= 4.1.5) | 4.2.1-9
update-inetd | 4.39
Package's Recommends field is empty.
Suggests (Version) | Installed
=================================-+-===========
proftpd-doc |
openssl | 1.0.0d-3
proftpd-mod-mysql | 1.3.4~rc2-4
proftpd-mod-pgsql | 1.3.4~rc2-4
proftpd-mod-ldap | 1.3.4~rc2-4
proftpd-mod-odbc |
proftpd-mod-sqlite |
openbsd-inetd | 0.20091229-1
OR inet-superserver |
So the simple fix is to either have the includes there or in proftpd.conf, but not in both places, obviously. Maybe the duplicated include should not be a fatal error!
This report is not clear. Where and what is the duplication in the distribute files?
The module includes exist both in the modules.conf and in the proftpd.conf after including module.conf. And as I propose, the duplicate include should be flagged and duely ignored rather than be a fatal error.
severity 640363 wishlist tag 640363 + upstream thanks But for an explicit placement of module loading clauses by admin, I see no way to have duplicated lines. Also note that order does matter, so admin has to manage correctly the whole thing by adding in the right file (modules.conf) and in the right place add-on modules.
severity 640363 wishlist tag 640363 + upstream thanks But for an explicit placement of module loading clauses by admin, I see no way to have duplicated lines. Also note that order does matter, so admin has to manage correctly the whole thing by adding in the right file (modules.conf) and in the right place add-on modules.