severity 1011914 minor
tags 1011914 = wontfix
retitle 1011914 lsof: FTBFS during unit tests when hostname cannot be
resolved
forward 1011914 https://github.com/lsof-org/lsof/issues/61
thanks
On Sun, Jun 5, 2022 at 11:13, Lucas Nussbaum <lu...@debian.org> wrote:
Hi Andres,
[...]
This is not related to the build attempting network access (I don't
check against this, so even if it did require network access, the
build
would work just fine).
What happens in AWS is:
- the hostname is ip-10-84-234-245 (for example)
- /etc/hosts contains (on the host)
127.0.1.1 ip-10-84-234-245.eu-central-1.compute.internal
ip-10-84-234-245
- schroot does not copy the host's /etc/hosts to the chroot, because
the
chroot is configured (using sbuild-create-chroot) to use the
'sbuild'
schroot profile, which does not include 'hosts' in
/etc/schroot/sbuild/nssdatabases
As a result, if the hostname cannot be resolved using DNS but only
using
NSS (/etc/hosts), then it cannot be resolved inside the chroot.
I fixed my chroot setup script so that 'hosts' get copied from host,
and
confirmed that lsof now builds fine.
I let you decide whether you want to close this bug, or turn it into a
severity:minor "FTBFS when hostname cannot be resolved".
I am not aware of other packages failing to build in the AWS
environment
because of this issue, so it might be worth keeping track of with a
bug.
Luca
Thanks, I'll keep it open. We have an upstream bug[0] discussing what to
do about the unit tests, which may result in the tests not being run at
all. If that ends up being the case, I will of course close this.
[0] https://github.com/lsof-org/lsof/issues/61#issuecomment-1120611271
