inetutils-1.9.4 build fails

  • Open
  • quality assurance status badge
Details
5 participants
  • Bone Baboon
  • Ludovic Courtès
  • Tobias Geerinckx-Rice
  • Mark H Weaver
  • Simon Josefsson
Owner
unassigned
Submitted by
Bone Baboon
Severity
normal
B
B
Bone Baboon wrote on 4 May 2021 04:16
(address . bug-guix@gnu.org)
87a6pbjlao.fsf@disroot.org
On a x86_64 computer when I run `guix build --no-substitutes --keep-failed inetutils` the build fails because of one failed test.

`guix describe` outputs:

```
Generation 18 May 03 2021 13:15:55 (current)
guix 065d2cd
commit: 065d2cd6ced96ddb38c15a46f798488f61660a33
```

Error message:

```
command "make" "check" failed with status 2
note: keeping build directory `/tmp/guix-build-inetutils-1.9.4.drv-0'
builder for `/gnu/store/immphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv' failed with exit code 1
build of /gnu/store/immphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv failed
View build log at '/var/log/guix/drvs/im/mphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv.bz2'.
guix build: error: build of `/gnu/store/immphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv' failed
```

Test suite contents:

```
===============================================
GNU inetutils 1.9.4: tests/test-suite.log
===============================================

# TOTAL: 15
# PASS: 8
# SKIP: 6
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

SKIP: ping-localhost.sh
=======================

ping needs to run as root
SKIP ping-localhost.sh (exit status: 77)

SKIP: traceroute-localhost.sh
=============================

traceroute needs to run as root
SKIP traceroute-localhost.sh (exit status: 77)

SKIP: tftp.sh
=============

The use of the superserver Inetd in this script requires
the availability of "/etc/nsswitch.conf", "/etc/passwd", and
"/etc/protocols". At least one of these is now missing.
Therefore skipping test.
SKIP tftp.sh (exit status: 77)

FAIL: syslogd.sh
================

../src/logger: ::1:7041: Cannot assign requested address
Registered 24 successes out of 25.
NOTICE: Standard port test was not run.
Failing some tests.
FAIL syslogd.sh (exit status: 1)

SKIP: ftp-localhost.sh
======================

The use of the superserver Inetd in this script requires
the availability of "/etc/nsswitch.conf", "/etc/passwd", and
"/etc/protocols". At least one of these is now missing.
Therefore skipping test.
SKIP ftp-localhost.sh (exit status: 77)

SKIP: inetd.sh
==============

This test requires the availability of "/etc/protocols",
a file which can not be found in the current system.
Therefore skipping this test.
SKIP inetd.sh (exit status: 77)

SKIP: telnet-localhost.sh
=========================

No TTY assigned to this process. Skipping test.
SKIP telnet-localhost.sh (exit status: 77)
```
T
T
Tobias Geerinckx-Rice wrote on 4 May 2021 11:09
(name . Bone Baboon)(address . bone.baboon@disroot.org)
871ramoogd.fsf@nckx
Babs,

Bone Baboon via Bug reports for GNU Guix 写道:
Toggle quote (5 lines)
> FAIL: syslogd.sh
> ================
>
> ../src/logger: ::1:7041: Cannot assign requested address

Looks like the same cause as https://issues.guix.gnu.org/48213:
missing IPv6 support on the host kernel.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCYJEPMg0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW159qkBAJj5ffKeiyGrEHTWuIOGhjI2XSnz6BQdxME3kQUY
NQyHAQC2ElxuYJeSttnjuWSLzPzwjj/sbseKMtp6m8++sj9lBw==
=wnNZ
-----END PGP SIGNATURE-----

B
B
Bone Baboon wrote on 6 May 2021 03:52
(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)
87eeekiq76.fsf@disroot.org
Tobias Geerinckx-Rice writes:
Toggle quote (9 lines)
> Bone Baboon via Bug reports for GNU Guix 写道:
>> FAIL: syslogd.sh
>> ================
>>
>> ../src/logger: ::1:7041: Cannot assign requested address
>
> Looks like the same cause as <https://issues.guix.gnu.org/48213>:
> missing IPv6 support on the host kernel.

Thank you for pointing this out.

I have reported this to the inetutils bug mailing list and asked if the
inetutils test suite could be modified so that syslogd.sh does not fail
if IPv6 is disabled.
B
B
Bone Baboon wrote on 6 May 2021 16:55
(name . Bone Baboon)(address . bone.baboon@disroot.org)
87zgx7hpy0.fsf@disroot.org
Bone Baboon via Bug reports for GNU Guix writes:
Toggle quote (4 lines)
> I have reported this to the inetutils bug mailing list and asked if the
> inetutils test suite could be modified so that syslogd.sh does not fail
> if IPv6 is disabled.

I received this response on the inetutils mailing list:

Toggle quote (10 lines)
> Hi. Thanks for the report. Could you investigate if the
> tests/runtime-ipv6.c program return appropriately? It is supposed to
> check wether the runtime system supports IPv6 or not, and should detect
> this properly on your system (or there is a bug in the self-test code
> elsewhere).
>
> Looking at the code, I don't think a getaddrinfo-lookup is sufficient,
> the code probably need to attempt to listen to a socket too, in order to
> fully test wether IPv6 is disabled globally or not.

I looked for tests/runtime-ipv6.c in the inetutils's build tree. I
could not find it. I looked up the current version of inetutils which
is 2.0. Guix has 1.9.4 of inetutils packaged.

Based on the response I received on the inetutils mailing list it sounds
like updating the inetutils package to 2.0 may resolve this failing
test.

I tried to build inetutils from the file inetutils-2-0.scm attached.
It's only changes are the version number and hash for inetutils 2.0. It
failed with this error:

```
patching file ifconfig/system.c
Hunk #1 FAILED at 25.
1 out of 1 hunk FAILED -- saving rejects to file ifconfig/system.c.rej
patching file ifconfig/system.h
Hunk #1 FAILED at 97.
1 out of 1 hunk FAILED -- saving rejects to file ifconfig/system.h.rej
patching file ifconfig/system/Makefile.am
Hunk #1 FAILED at 26.
1 out of 1 hunk FAILED -- saving rejects to file ifconfig/system/Makefile.am.rej
patching file ifconfig/system/generic.c
Hunk #1 FAILED at 22.
Hunk #2 FAILED at 36.
2 out of 2 hunks FAILED -- saving rejects to file ifconfig/system/generic.c.rej
The next patch would create the file ifconfig/system/hurd.c,
which already exists! Applying it anyway.
patching file ifconfig/system/hurd.c
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file ifconfig/system/hurd.c.rej
The next patch would create the file ifconfig/system/hurd.h,
which already exists! Applying it anyway.
patching file ifconfig/system/hurd.h
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file ifconfig/system/hurd.h.rej
patching file ifconfig/system/hurd.c
Hunk #1 succeeded at 186 with fuzz 2 (offset 11 lines).
Hunk #2 FAILED at 194.
1 out of 2 hunks FAILED -- saving rejects to file ifconfig/system/hurd.c.rej
patching file telnet/sys_bsd.c
Hunk #1 succeeded at 64 (offset 1 line).
Hunk #2 succeeded at 159 (offset 1 line).
Hunk #3 succeeded at 262 (offset 1 line).
Hunk #4 succeeded at 759 (offset 1 line).
source is under 'inetutils-2.0'
applying '/gnu/store/pyjlhc8r3xzm169l6symkm2l9wrab6hl-inetutils-hurd.patch'...
Backtrace:
3 (primitive-load "/gnu/store/401x9biqviwi2xa2sjs9p7c0xsf…")
In ice-9/eval.scm:
619:8 2 (_ #(#<directory (guile-user) 10d7d0> "inetutils-2.0"))
In srfi/srfi-1.scm:
634:9 1 (for-each #<procedure apply-patch (a)> ("/gnu/store/py…"))
In guix/build/utils.scm:
654:6 0 (invoke _ . _)

guix/build/utils.scm:654:6: In procedure invoke:
ERROR:
1. &invoke-error:
program: "/gnu/store/qw20chpgkgbcqmzhs60c8hjl1hmblyc8-patch-2.7.6/bin/patch"
arguments: ("--force" "--no-backup-if-mismatch" "-p1" "--input" "/gnu/store/pyjlhc8r3xzm169l6symkm2l9wrab6hl-inetutils-hurd.patch")
exit-status: 1
term-signal: #f
stop-signal: #f
```
Attachment: inetutils-2-0.scm
B
B
Bone Baboon wrote on 6 May 2021 19:14
(name . Bone Baboon)(address . bone.baboon@disroot.org)
87tunfhjiy.fsf@disroot.org
Toggle quote (25 lines)
> Bone Baboon via Bug reports for GNU Guix writes:
>> I have reported this to the inetutils bug mailing list and asked if the
>> inetutils test suite could be modified so that syslogd.sh does not fail
>> if IPv6 is disabled.
>
> I received this response on the inetutils mailing list:
>
>> Hi. Thanks for the report. Could you investigate if the
>> tests/runtime-ipv6.c program return appropriately? It is supposed to
>> check wether the runtime system supports IPv6 or not, and should detect
>> this properly on your system (or there is a bug in the self-test code
>> elsewhere).
>>
>> Looking at the code, I don't think a getaddrinfo-lookup is sufficient,
>> the code probably need to attempt to listen to a socket too, in order to
>> fully test wether IPv6 is disabled globally or not.
>
> I looked for tests/runtime-ipv6.c in the inetutils's build tree. I
> could not find it. I looked up the current version of inetutils which
> is 2.0. Guix has 1.9.4 of inetutils packaged.
>
> Based on the response I received on the inetutils mailing list it sounds
> like updating the inetutils package to 2.0 may resolve this failing
> test.

On the inetutils mailing list it was suggested that I try inetutils 2.0
on the core-updates branch. I can successfully build inetutils 2.0 from
the core-updates branch even with IPv6 disabled.

What is the purpose of the core-updates branch?

If inetutils follows semantic version numbering then that would suggest
a breaking change to the inetutils API moving from 1.9.4 to 2.0. Can
the Guix master branch provide inetutils 2.0 instead of 1.9.4?

How can I use a package definition from core-updates with guix build or
in a system configuration if it is not available on Guix's master
branch?

What are the reasons I might not want to use a package from the
core-updates branch?
L
L
Ludovic Courtès wrote on 6 May 2021 22:55
87eeejd1kx.fsf@gnu.org
Hi,

Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org> skribis:

Toggle quote (6 lines)
> On the inetutils mailing list it was suggested that I try inetutils 2.0
> on the core-updates branch. I can successfully build inetutils 2.0 from
> the core-updates branch even with IPv6 disabled.
>
> What is the purpose of the core-updates branch?

The ‘core-updates’ branch contains updates to core packages and core
Guix functionality that entails a rebuild of all the packages. In that
branch we put package upgrades that would otherwise lead to too many
rebuilds (info "(guix) Submitting Patches").

Toggle quote (4 lines)
> If inetutils follows semantic version numbering then that would suggest
> a breaking change to the inetutils API moving from 1.9.4 to 2.0. Can
> the Guix master branch provide inetutils 2.0 instead of 1.9.4?

No: ‘guix refresh -l inetutils’ shows that almost 2,000 packages depend
on inetutils.

That said, if needed, ‘master’ could provide 2.0 in addition to 1.9, as
is done for GDB for instance.

Toggle quote (4 lines)
> How can I use a package definition from core-updates with guix build or
> in a system configuration if it is not available on Guix's master
> branch?

You can do better :-), you can install 2.0 from master like so:

guix install inetutils --with-latest=inetutils

Toggle quote (3 lines)
> What are the reasons I might not want to use a package from the
> core-updates branch?

‘core-updates’ is where we put core changes as I wrote, including
experimental changes. That branch also does not receive security
updates in a timely fashion. So it’s really a branch for developers
working on core improvements.

HTH!

Ludo’.
B
B
Bone Baboon wrote on 7 May 2021 02:55
(name . Ludovic Courtès)(address . ludo@gnu.org)
87lf8rgy60.fsf@disroot.org
Ludovic Courtès writes:
Toggle quote (8 lines)
>> How can I use a package definition from core-updates with guix build or
>> in a system configuration if it is not available on Guix's master
>> branch?
>
> You can do better :-), you can install 2.0 from master like so:
>
> guix install inetutils --with-latest=inetutils

Thank you for sharing that command.

I prefer to build locally over using substitutes. When I try to run
`guix build inetutils --no-substitutes --with-latest=inetutils` it does
not complete because there is an interactive prompt. The prompt says
"Would you like to add this key to your keyring
'<path/to/trustedkeys.kbx>'?". I have a substitute server that is
sequentially building packages unattended and this would cause it to
become stuck and make no further progress.

Toggle quote (11 lines)
>> On the inetutils mailing list it was suggested that I try inetutils 2.0
>> on the core-updates branch. I can successfully build inetutils 2.0 from
>> the core-updates branch even with IPv6 disabled.
>>
>> What is the purpose of the core-updates branch?
>
> The ‘core-updates’ branch contains updates to core packages and core
> Guix functionality that entails a rebuild of all the packages. In that
> branch we put package upgrades that would otherwise lead to too many
> rebuilds (info "(guix) Submitting Patches").

Thank you for explaining this.

---

What is the process for a package to be brought into master from core-updates?

---

I would rebuild all the packages on my system if I could use inetutils
2.0. Is there a way that I can rebuild all the packages I am using that
depend on inetutils to use inetutils 2.0 (or more generally any newer
version of package from core-updates)?

Toggle quote (8 lines)
>> Can the Guix master branch provide inetutils 2.0 instead of 1.9.4?
>
> No: ‘guix refresh -l inetutils’ shows that almost 2,000 packages depend
> on inetutils.
>
> That said, if needed, ‘master’ could provide 2.0 in addition to 1.9, as
> is done for GDB for instance.

Would having multiple versions of inetutils in master also create
multiple versions of packages that depend on inetutils for example a
version of isc-dhcp that depends on inetutils 1.9 and another that
depends on inetutils 2.0?

---

Not having inetutils 2.0 in master appears to break how I connect to the
internet using Guix if I do both of these:
* Disable IPv6
** See my previous email in this thread that explains the rationale on
why I am disabling IPv6.
* Build from source

isc-dhcp fails to build because it depends on inetutils 1.9 which is
failing. I am using isc-dhcp when I connecting to the internet.

Toggle quote (8 lines)
>> What are the reasons I might not want to use a package from the
>> core-updates branch?
>
> ‘core-updates’ is where we put core changes as I wrote, including
> experimental changes. That branch also does not receive security
> updates in a timely fashion. So it’s really a branch for developers
> working on core improvements.

Thank you for explaining this.
B
B
Bone Baboon wrote on 7 May 2021 03:36
(name . Ludovic Courtès)(address . ludo@gnu.org)
87fsyzgwai.fsf@disroot.org
Bone Baboon writes:
Toggle quote (3 lines)
> ** See my previous email in this thread that explains the rationale on
> why I am disabling IPv6.

Correction see https://issues.guix.gnu.org/48213#3for my rationale for disabling IPv6.
M
M
Mark H Weaver wrote on 7 May 2021 19:53
87r1iil9ac.fsf@netris.org
Hi,

Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

Toggle quote (12 lines)
> Ludovic Courtès writes:
>>> How can I use a package definition from core-updates with guix build or
>>> in a system configuration if it is not available on Guix's master
>>> branch?
>>
>> You can do better :-), you can install 2.0 from master like so:
>>
>> guix install inetutils --with-latest=inetutils
>
> Thank you for sharing that command.
>
> I prefer to build locally over using substitutes.
[...]
Toggle quote (5 lines)
> I would rebuild all the packages on my system if I could use inetutils
> 2.0. Is there a way that I can rebuild all the packages I am using that
> depend on inetutils to use inetutils 2.0 (or more generally any newer
> version of package from core-updates)?

Right, the problem is that since you're avoiding substitutes, you need
to fix the core 'inetutils' package in order to build your system at
all.

Moreover, you're also having problems with overly aggressive test
timeouts in 'glib' (see https://bugs.gnu.org/48024#20), you'll need to
fix that package as well.

I've outlined one possible way forward here:


However, Ludovic might know of other alternatives.

Regards,
Mark

--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about https://stallmansupport.org.
S
S
Simon Josefsson wrote on 8 May 2021 08:30
87bl9l20wf.fsf@latte.josefsson.org
Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

Toggle quote (3 lines)
> If inetutils follows semantic version numbering then that would suggest
> a breaking change to the inetutils API moving from 1.9.4 to 2.0.

FWIW, inetutils is not following semantic versioning, and 2.0 is
expected to be a simple drop-in for 1.9.4.

/Simon
-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQSjzJyHC50xCrrUzy9RcisI/kdFogUCYJYv8AAKCRBRcisI/kdF
oqXXAQDKZQXpR8rvJtEFRp1RMwdJ0htujo4HILItcjolJMx88QD/RU6rMqZtMznL
M308a16jJRsSGiz7764mpacCqjdzuA8=
=mCLB
-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 8 May 2021 14:53
(name . Bone Baboon)(address . bone.baboon@disroot.org)
87lf8p8jzr.fsf@gnu.org
Hi,

Bone Baboon <bone.baboon@disroot.org> skribis:

Toggle quote (19 lines)
> Ludovic Courtès writes:
>>> How can I use a package definition from core-updates with guix build or
>>> in a system configuration if it is not available on Guix's master
>>> branch?
>>
>> You can do better :-), you can install 2.0 from master like so:
>>
>> guix install inetutils --with-latest=inetutils
>
> Thank you for sharing that command.
>
> I prefer to build locally over using substitutes. When I try to run
> `guix build inetutils --no-substitutes --with-latest=inetutils` it does
> not complete because there is an interactive prompt. The prompt says
> "Would you like to add this key to your keyring
> '<path/to/trustedkeys.kbx>'?". I have a substitute server that is
> sequentially building packages unattended and this would cause it to
> become stuck and make no further progress.

The interactive prompt is about authenticate the source code tarball,
inetutils-2.0.tar.gz. It does not relate to substitutes.

Toggle quote (17 lines)
>>> On the inetutils mailing list it was suggested that I try inetutils 2.0
>>> on the core-updates branch. I can successfully build inetutils 2.0 from
>>> the core-updates branch even with IPv6 disabled.
>>>
>>> What is the purpose of the core-updates branch?
>>
>> The ‘core-updates’ branch contains updates to core packages and core
>> Guix functionality that entails a rebuild of all the packages. In that
>> branch we put package upgrades that would otherwise lead to too many
>> rebuilds (info "(guix) Submitting Patches").
>
> Thank you for explaining this.
>
> ---
>
> What is the process for a package to be brought into master from core-updates?

Submitting a patch the usual way, but making it clear in the subject
line that it targets ‘core-updates’.

Toggle quote (5 lines)
> I would rebuild all the packages on my system if I could use inetutils
> 2.0. Is there a way that I can rebuild all the packages I am using that
> depend on inetutils to use inetutils 2.0 (or more generally any newer
> version of package from core-updates)?

You could maintain your own branch where the default inetutils is 2.0.

Toggle quote (13 lines)
>>> Can the Guix master branch provide inetutils 2.0 instead of 1.9.4?
>>
>> No: ‘guix refresh -l inetutils’ shows that almost 2,000 packages depend
>> on inetutils.
>>
>> That said, if needed, ‘master’ could provide 2.0 in addition to 1.9, as
>> is done for GDB for instance.
>
> Would having multiple versions of inetutils in master also create
> multiple versions of packages that depend on inetutils for example a
> version of isc-dhcp that depends on inetutils 1.9 and another that
> depends on inetutils 2.0?

No; what I suggest above would just address the case where people run
‘guix install inetutils’ or it could change the one in
/run/current-system/profile.

Toggle quote (10 lines)
> Not having inetutils 2.0 in master appears to break how I connect to the
> internet using Guix if I do both of these:
> * Disable IPv6
> ** See my previous email in this thread that explains the rationale on
> why I am disabling IPv6.
> * Build from source
>
> isc-dhcp fails to build because it depends on inetutils 1.9 which is
> failing. I am using isc-dhcp when I connecting to the internet.

Unfortunately I don’t have a good solution for you. :-/

We could change isc-dhcp in ‘master’ so that it depends on inetutils
2.0, but that looks like a band-aid.

Thanks,
Ludo’.
B
B
Bone Baboon wrote on 12 May 2021 23:53
(name . Bone Baboon)(address . bone.baboon@disroot.org)
87sg2rei07.fsf@disroot.org
I have done several pulls since reporting that inetutils failed to
build. I can now build inetutils-1.9.4 successfully. I still have IPv6
disabled. I do not know what the cause of the build failure was. I do
not know why it can now build (likely a recent commit).

Bone Baboon via Bug reports for GNU Guix writes:

Toggle quote (92 lines)
> On a x86_64 computer when I run `guix build --no-substitutes --keep-failed inetutils` the build fails because of one failed test.
>
> `guix describe` outputs:
>
> ```
> Generation 18 May 03 2021 13:15:55 (current)
> guix 065d2cd
> repository URL: https://git.savannah.gnu.org/git/guix.git
> commit: 065d2cd6ced96ddb38c15a46f798488f61660a33
> ```
>
> Error message:
>
> ```
> command "make" "check" failed with status 2
> note: keeping build directory `/tmp/guix-build-inetutils-1.9.4.drv-0'
> builder for `/gnu/store/immphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv' failed with exit code 1
> build of /gnu/store/immphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv failed
> View build log at '/var/log/guix/drvs/im/mphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv.bz2'.
> guix build: error: build of `/gnu/store/immphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv' failed
> ```
>
> Test suite contents:
>
> ```
> ===============================================
> GNU inetutils 1.9.4: tests/test-suite.log
> ===============================================
>
> # TOTAL: 15
> # PASS: 8
> # SKIP: 6
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> SKIP: ping-localhost.sh
> =======================
>
> ping needs to run as root
> SKIP ping-localhost.sh (exit status: 77)
>
> SKIP: traceroute-localhost.sh
> =============================
>
> traceroute needs to run as root
> SKIP traceroute-localhost.sh (exit status: 77)
>
> SKIP: tftp.sh
> =============
>
> The use of the superserver Inetd in this script requires
> the availability of "/etc/nsswitch.conf", "/etc/passwd", and
> "/etc/protocols". At least one of these is now missing.
> Therefore skipping test.
> SKIP tftp.sh (exit status: 77)
>
> FAIL: syslogd.sh
> ================
>
> ../src/logger: ::1:7041: Cannot assign requested address
> Registered 24 successes out of 25.
> NOTICE: Standard port test was not run.
> Failing some tests.
> FAIL syslogd.sh (exit status: 1)
>
> SKIP: ftp-localhost.sh
> ======================
>
> The use of the superserver Inetd in this script requires
> the availability of "/etc/nsswitch.conf", "/etc/passwd", and
> "/etc/protocols". At least one of these is now missing.
> Therefore skipping test.
> SKIP ftp-localhost.sh (exit status: 77)
>
> SKIP: inetd.sh
> ==============
>
> This test requires the availability of "/etc/protocols",
> a file which can not be found in the current system.
> Therefore skipping this test.
> SKIP inetd.sh (exit status: 77)
>
> SKIP: telnet-localhost.sh
> =========================
>
> No TTY assigned to this process. Skipping test.
> SKIP telnet-localhost.sh (exit status: 77)
> ```
B
B
Bone Baboon wrote on 12 May 2021 23:59
inetutils 1.9.4 builds successfully
(address . 48214-done@debbugs.gnu.org)
87pmxvehpn.fsf@disroot.org
Closing bug#48214 because inetutils 1.9.4 now builds successfully even
with IPv6 disabled.
Closed
B
B
Bone Baboon wrote on 13 May 2021 15:45
Re: bug#48214: inetutils-1.9.4 build fails
(name . Bone Baboon)(address . bone.baboon@disroot.org)
87h7j6eohl.fsf@disroot.org
I have reopened bug#48214 because while inetutils-1.9.4 can be built on
x86_64 with IPv6 disabled this command fails on x86_64 with IPv6
disabled `guix build --no-substitutes --system=i686-linux` inetutils`.
This command has the same failing test. Attached is the failing i686
build log.
Bone Baboon via Bug reports for GNU Guix writes:

Toggle quote (92 lines)
> On a x86_64 computer when I run `guix build --no-substitutes --keep-failed inetutils` the build fails because of one failed test.
>
> `guix describe` outputs:
>
> ```
> Generation 18 May 03 2021 13:15:55 (current)
> guix 065d2cd
> repository URL: https://git.savannah.gnu.org/git/guix.git
> commit: 065d2cd6ced96ddb38c15a46f798488f61660a33
> ```
>
> Error message:
>
> ```
> command "make" "check" failed with status 2
> note: keeping build directory `/tmp/guix-build-inetutils-1.9.4.drv-0'
> builder for `/gnu/store/immphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv' failed with exit code 1
> build of /gnu/store/immphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv failed
> View build log at '/var/log/guix/drvs/im/mphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv.bz2'.
> guix build: error: build of `/gnu/store/immphxs1iknnz5rfdhcs4i62j22yshqx-inetutils-1.9.4.drv' failed
> ```
>
> Test suite contents:
>
> ```
> ===============================================
> GNU inetutils 1.9.4: tests/test-suite.log
> ===============================================
>
> # TOTAL: 15
> # PASS: 8
> # SKIP: 6
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> SKIP: ping-localhost.sh
> =======================
>
> ping needs to run as root
> SKIP ping-localhost.sh (exit status: 77)
>
> SKIP: traceroute-localhost.sh
> =============================
>
> traceroute needs to run as root
> SKIP traceroute-localhost.sh (exit status: 77)
>
> SKIP: tftp.sh
> =============
>
> The use of the superserver Inetd in this script requires
> the availability of "/etc/nsswitch.conf", "/etc/passwd", and
> "/etc/protocols". At least one of these is now missing.
> Therefore skipping test.
> SKIP tftp.sh (exit status: 77)
>
> FAIL: syslogd.sh
> ================
>
> ../src/logger: ::1:7041: Cannot assign requested address
> Registered 24 successes out of 25.
> NOTICE: Standard port test was not run.
> Failing some tests.
> FAIL syslogd.sh (exit status: 1)
>
> SKIP: ftp-localhost.sh
> ======================
>
> The use of the superserver Inetd in this script requires
> the availability of "/etc/nsswitch.conf", "/etc/passwd", and
> "/etc/protocols". At least one of these is now missing.
> Therefore skipping test.
> SKIP ftp-localhost.sh (exit status: 77)
>
> SKIP: inetd.sh
> ==============
>
> This test requires the availability of "/etc/protocols",
> a file which can not be found in the current system.
> Therefore skipping this test.
> SKIP inetd.sh (exit status: 77)
>
> SKIP: telnet-localhost.sh
> =========================
>
> No TTY assigned to this process. Skipping test.
> SKIP telnet-localhost.sh (exit status: 77)
> ```
?