From: "宋文武 via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: 48214@debbugs.gnu.org
Subject: bug#48214: inetutils-1.9.4 build fails
Date: Wed, 22 Feb 2023 10:00:26 +0800 [thread overview]
Message-ID: <878rgqqx1h.fsf@envs.net> (raw)
In-Reply-To: <87h7j6eohl.fsf@disroot.org> (Bone Baboon's message of "Thu, 13 May 2021 09:45:42 -0400")
Bone Baboon <bone.baboon@disroot.org> writes:
> 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.
>
Does this issue still exist? Now we have inetutils-2.0 in master, and will
have 2.3 soon after core-updates merged...
next prev parent reply other threads:[~2023-02-22 2:02 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
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 [this message]
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=878rgqqx1h.fsf@envs.net \
--to=bug-guix@gnu.org \
--cc=48214@debbugs.gnu.org \
--cc=bone.baboon@disroot.org \
--cc=iyzsong@envs.net \
/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).