Your message dated Mon, 11 Apr 2022 10:00:33 +0200
with message-id <[email protected]>
and subject line Re: Bug#1008284: Naming convention of Debian-introduced files
are too confusing.
has caused the Debian Bug report #1008284,
regarding Naming convention of Debian-introduced files are too confusing.
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.)
--
1008284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008284
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: exim-configVersion: 4.95-4
Content-Type: text/plain; charset="us-ascii"MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: S Egbert <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: exim4-config: naming convention of Debian-specific config files is
confusing
Message-ID: <[email protected]>
X-Mailer: reportbug 7.10.3+deb11u1
Date: Fri, 25 Mar 2022 17:44:45 -0400
X-Debbugs-Cc: [email protected] Version: 4.95-4 Severity: normal Tags: a11y
Dear Maintainer,
File naming convention for several Debian-introduced files are too confusing.
Using Debian Testing exim4-config v4.95-4 package. (I do not know why
`reportbug` is picking up `exim4` version instead of my requested
`exim4-config` package name.
I was thinking maybe it might need to have several Debian-specific files
renamed with respect to different filetypes.
Naming convention could have been more intuitive. Such as:
update-exim4.conf could be better named as update-exim4-conf (or
update-exim4)
update-exim4.conf.conf could be better named as exim4.debian.conf: then we
would know which one to go to exim4.conf/exim4.conf.debian.
update-exim4.conf.template ... whew ... could have been
exim4.conf.template.debian.
/var/lib/exim4/config.autogenerated could have beeen
/var/lib/exim4/exim4.conf.autogenerated.
In reality, Debian should co-opt some standardized prefix (perhaps, `dpkgc-`)
for all package maintainers to use and do that dpkg-reconfigure/dpkg-configure
thingie instead of `update-exim4.conf`.
I made a Bash file script to make heads and tails on WHO is using WHICH config
file(s) and by WHAT Debian config file methods.
Reference:
https://github.com/egberts/exim4-config-check-which
-- Package-specific info:
Exim version 4.94.2 #2 built 13-Jul-2021 16:04:57
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013)
Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS
move_frozen_messages Content_Scanning DANE DKIM DNSSEC Event I18N OCSP
PIPE_CONNECT PRDR PROXY SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz
dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite
Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa tls
Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Malware: f-protd f-prot6d drweb fsecure sophie clamd avast sock cmdline
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
##############################################################################
#
# NOTE: DO NOT USE if `/etc/exim4/exim4.conf` exists
#
# NOTE: DO SET `dc_use_split_configuration` to `no`
# if you do not want `dpkg-reconfigure exim4-config` to
# tamper with your Exim4 settings.
#
##############################################################################
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file
dc_eximconfig_configtype='internet'
dc_other_hostnames='egbert.net'
dc_local_interfaces='127.0.0.0 ; ::1 ; 104.218.48.116 ; 2604:a00:5:1156::116'
dc_readhost=''
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost=''
CFILEMODE='640'
dc_use_split_config='true'
dc_hide_mailname=''
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
dc_local_part='*- : *+ : *_'
dc_main_tls_certificate='/etc/exim/keys/cert.pem'
dc_main_tls_privatekey='/etc/exim/keys/privkey.pem'
mailname:egbert.net
# /etc/default/exim4
EX4DEF_VERSION=''
# 'combined' - one daemon running queue and listening on SMTP port
# 'no' - no daemon running the queue
# 'separate' - two separate daemons
# 'ppp' - only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='30m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# Options for the SMTP listener daemon. By default, it is listening on
# port 25 only. To listen on more ports, it is recommended to use
# -oX 25:587:10025 -oP /run/exim4/exim.pid
SMTPLISTENEROPTIONS='-oX 587:465:25 -oP /run/exim4/exim.pid'
-- System Information:
Debian Release: 11.2
APT prefers stable
APT policy: (991, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-10-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages exim4-config depends on:
ii adduser 3.118
ii debconf [debconf-2.0] 1.5.77
Versions of packages exim4-config recommends:
ii ca-certificates 20210119
exim4-config suggests no packages.
-- Configuration Files:
/etc/email-addresses changed [not included]
-- debconf information excluded
--- End Message ---
--- Begin Message ---
On 2022-03-25 S E <[email protected]> wrote:
> Package: exim-config
> Version: 4.95-4
[...]
> File naming convention for several Debian-introduced files are too confusing.
> Using Debian Testing exim4-config v4.95-4 package. (I do not know why
> `reportbug` is picking up `exim4` version instead of my requested
> `exim4-config` package name.
> I was thinking maybe it might need to have several Debian-specific
> files renamed with respect to different filetypes.
> Naming convention could have been more intuitive. Such as:
[...]
Hello,
I do not disagree that some names could have been chosen better.
However
* these names have been in use for almost twenty years now and are
reflected in countless places and we are accustomed to them abd
* changing some of them is quite involved, easily introducing severe
bugs.
So I do not think the cost/benefit analyses for a painful transition
does not look good to me. I am therefore closing this report.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
