Your message dated Sat, 25 May 2024 00:43:06 +0200
with message-id <[email protected]>
and subject line Re: Bug#1071788: inn2: installation fails with "hostname does 
not resolve or domain not set in inn.conf"
has caused the Debian Bug report #1071788,
regarding inn2: installation fails with "hostname does not resolve or domain 
not set in inn.conf"
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.)


-- 
1071788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071788
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: inn2
Version: 2.7.1-1+deb12u1
Severity: wishlist
X-Debbugs-Cc: [email protected]

Dear Maintainer,

When installing the package inn2, the following messages are output, which 
indicate an error 
condition:

Unpacking inn2 (2.7.1-1+deb12u1) ...
Setting up inn2 (2.7.1-1+deb12u1) ...
innconfval: hostname does not resolve or domain not set in inn.conf
innconfval: the FQDN of the server contains invalid characters not suitable for 
Message-IDs
dpkg: error processing package inn2 (--configure):
 installed inn2 package post-installation script subprocess returned error exit 
status 1
Processing triggers for man-db (2.11.2-2) ...
Errors were encountered while processing:
 inn2
E: Sub-process /usr/bin/dpkg returned an error code (1)

Understandably it is necessary for the user to eventually set a valid domain 
name in /etc/news/inn.conf but surely this is not something that the installer 
itself should be throwing an error for.


-- System Information:
Debian Release: 12.5
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-21-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages inn2 depends on:
ii  cron [cron-daemon]              3.0pl1-162
ii  inn2-inews                      2.7.1-1+deb12u1
ii  libc6                           2.36-9+deb12u7
ii  libcanlock3                     3.3.0-1
ii  libcrypt1                       1:4.4.33-2
ii  libdb5.3                        5.3.28+dfsg2-1
ii  libmime-tools-perl              5.510-1
ii  libpam0g                        1.5.2-6+deb12u1
ii  libperl5.36                     5.36.0-7+deb12u1
ii  libpython3.11                   3.11.2-6
ii  libsasl2-2                      2.1.28+dfsg-10
ii  libsqlite3-0                    3.40.1-2
ii  libssl3                         3.0.11-1~deb12u2
ii  libsystemd0                     252.22-1~deb12u1
ii  lsb-base                        11.6
ii  perl [libencode-perl]           5.36.0-7+deb12u1
ii  perl-base [perlapi-5.36.0]      5.36.0-7+deb12u1
ii  postfix [mail-transport-agent]  3.7.10-0+deb12u1
ii  procps                          2:4.0.2-3
ii  sysvinit-utils [lsb-base]       3.06-4
ii  time                            1.9-0.2
ii  zlib1g                          1:1.2.13.dfsg-1

inn2 recommends no packages.

Versions of packages inn2 suggests:
pn  gnupg1      <none>
pn  libgd-perl  <none>
ii  libkrb5-3   1.20.1-2+deb12u1
ii  wget        1.21.3-1+b2

-- Configuration Files:
/etc/news/incoming.conf [Errno 13] Permission denied: '/etc/news/incoming.conf'
/etc/news/inn-radius.conf [Errno 13] Permission denied: 
'/etc/news/inn-radius.conf'
/etc/news/inn-secrets.conf [Errno 13] Permission denied: 
'/etc/news/inn-secrets.conf'
/etc/news/innfeed.conf [Errno 13] Permission denied: '/etc/news/innfeed.conf'

-- no debconf information

--- End Message ---
--- Begin Message ---
On May 25, Tristan Miller <[email protected]> wrote:

> Understandably it is necessary for the user to eventually set a valid 
> domain name in /etc/news/inn.conf but surely this is not something 
> that the installer itself should be throwing an error for.
No, you do not understand the issue.
A valid hostname is needed by ANY inn component, among them the programs 
which need to be run by postinst.

-- 
ciao,
Marco

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to