From: Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: 48214@debbugs.gnu.org, me@tobias.gr
Subject: bug#48214: inetutils-1.9.4 build fails
Date: Thu, 06 May 2021 13:14:13 -0400 [thread overview]
Message-ID: <87tunfhjiy.fsf@disroot.org> (raw)
In-Reply-To: <87zgx7hpy0.fsf@disroot.org>
> 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?
next prev parent reply other threads:[~2021-05-06 17:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 2:16 bug#48214: inetutils-1.9.4 build fails Bone Baboon via Bug reports for GNU Guix
2021-05-04 9:09 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-05-06 1:52 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06 14:55 ` Bone Baboon via Bug reports for GNU Guix
2021-05-06 17:14 ` Bone Baboon via Bug reports for GNU Guix [this message]
2021-05-06 20:55 ` Ludovic Courtès
2021-05-07 0:55 ` Bone Baboon via Bug reports for GNU Guix
2021-05-07 1:36 ` Bone Baboon via Bug reports for GNU Guix
2021-05-07 17:53 ` Mark H Weaver
2021-05-08 12:53 ` Ludovic Courtès
2021-05-08 6:30 ` Simon Josefsson via Bug reports for GNU Guix
2021-05-12 21:53 ` Bone Baboon via Bug reports for GNU Guix
2021-05-12 21:59 ` bug#48214: inetutils 1.9.4 builds successfully Bone Baboon via Bug reports for GNU Guix
2021-05-13 13:45 ` bug#48214: inetutils-1.9.4 build fails Bone Baboon via Bug reports for GNU Guix
2023-02-22 2:00 ` 宋文武 via Bug reports for GNU Guix
2023-04-15 11:03 ` bug#48214: Close Andreas Enge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tunfhjiy.fsf@disroot.org \
--to=bug-guix@gnu.org \
--cc=48214@debbugs.gnu.org \
--cc=bone.baboon@disroot.org \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).