This small patch is worth SRUing to Focal and Hirsute, I added tasks for
those.
** Also affects: postfix (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: sbuild (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: postfix (Ubuntu Hirsute)
I verified that the landed fix also fixes the sbuild autopkgtest
failure:
build-procenvPASS
unshare-qemuwrapper SKIP installation fails and skip-not-installable set
unshare PASS
** Changed in: sbuild (Ubuntu)
Status: Triaged => Fix Released
--
You received this
This bug was fixed in the package postfix - 3.5.6-1ubuntu1
---
postfix (3.5.6-1ubuntu1) impish; urgency=medium
* d/postfix.postinst: tolerate search domain with a leading dot
(LP: #1906970)
-- Paride Legovini Fri, 06 Aug 2021 17:56:03 +0200
** Changed in: postfix (Ubuntu)
** Changed in: postfix (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906970
Title:
dpkg hook hostname error
To manage notifications about this bug
** Merge proposal linked:
https://code.launchpad.net/~paride/ubuntu/+source/postfix/+git/postfix/+merge/406805
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906970
Title:
dpkg hook hostname
** Bug watch added: Debian Bug tracker #991950
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991950
** Also affects: postfix (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991950
Importance: Unknown
Status: Unknown
--
You received this bug notification
My understanding now is that the resolver *tolerates* search domains
starting with a ".", stripping it off. This is very visible in the code
snipped posted by Sergio:
if (dname[0] == '.')
dname++;
and this is the reason "search ." is not really documented: it's not
really useful as in
I can reproduce the sbuild autopkgtest failure locally using
autopkgtest-virt-qemu, but interestingly this doesn't happen on
autopkgtest.ubuntu.com, which tests using autopkgtest-virt-ssh to an
openstack instance. I imagine that platform doesn't have `search .` in
/etc/resolv.conf. which is what
Sergio (~sergiodj) did some digging on `search .` and found out that it
should be supported after all. I'm copy/pasting here his email to
ubuntu-server@lists.u.c for future reference:
=== Message-ID: <87k0msqlzy@ubuntu.com> ===
I think the reporter from #1906970 is right: it seems that
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sbuild (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906970
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: postfix (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906970
Title:
This happened to me when upgrading from Groovy to Hirsute just now, with
the same symptoms as above - I had `search .` in resolv.conf, but
nothing creating that entry in /etc/netplan or in
/etc/systemd/resolved.conf.
I fixed the broken package by fixing the erroneous entry
/etc/postfix/main.cf
The sbuild autopkgtest failure is not observable on the central Ubuntu
CI infra, but it is when running the sbuild autopkgtest locally in qemu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906970
The sbuild autopkgtest failure will be observable with sbuild
0.81.2ubuntu3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906970
Title:
dpkg hook hostname error
To manage notifications about
This also breaks installing postfix in autokgtest and holds back fixing
sbuild's autopkgtest at the moment.
...
/etc/aliases does not exist, creating it.
WARNING: /etc/aliases exists, but does not have a root alias.
Postfix (main.cf) is now set up with a default configuration. If you need to
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906970
Title:
dpkg hook hostname error
To manage
This is just an error in the postfix dpkg script. Having "search ." is
completely valid. I also asked in IRC. In IRC we had consensus that
"search ." is the catch all as it references the DNS-Root domain.
```
[root@ ~]# ls -la /etc/resolv.conf
lrwxrwxrwx 1 root root 32 Nov 25 2019
That indeed contains the offending "search .".
Since the file is managed by systemd-resolved the question becomes where
exactly that comes from.
To ensure this is the case check /run/systemd/resolve/stub-resolv.conf which is
the file that pushes info from systemd-resolved into resolv.conf.
This is the content of the hosts /etc/resolv.conf:
```
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
#
Hi Klaus,
I think the culprit is the misconfigured `search .` domain in
/etc/resolv.conf. However that's not a Docker (image) default: it's just
inherited by the host system. Can you please verify this is the case,
try fixing it in the host system and try the postfix install in docker
once again?
This is the default name of the docker container. That's why I reported
it here. For me it is a problem with the install script. It shouldn't
fail to install within a default docker container.
regarding b) how do I make docker select that automatically? I wasn't
able to find any way to install
Hi Klaus,
>From your log:
newaliases: warning: valid_hostname: misplaced delimiter: cc1a572af0dc..
That comes down to the initial install requiring a fully
qualified domain name.
And your systems seems to have an invalid one for that use case.
There are two paths out of this.
a) fix the
** Description changed:
I tried to install postfix (3.4.13-0ubuntu1) within a Dockerfile (Ubuntu
20.04.01 LTS) and it failed because there is an error in the dpkg info
file.
I'm attaching the log of the 2nd time "apt install -y postfix" is
executed, as it is way shorter and still
23 matches
Mail list logo
