From: Simon Josefsson via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Bone Baboon <bone.baboon@disroot.org>,
48214@debbugs.gnu.org, me@tobias.gr
Subject: bug#48214: inetutils-1.9.4 build fails
Date: Sat, 08 May 2021 08:30:08 +0200 [thread overview]
Message-ID: <87bl9l20wf.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87tunfhjiy.fsf@disroot.org> (Bone Baboon via Bug reports for's message of "Thu, 06 May 2021 13:14:13 -0400")
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-05-08 6:31 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bl9l20wf.fsf@latte.josefsson.org \
--to=bug-guix@gnu.org \
--cc=48214@debbugs.gnu.org \
--cc=bone.baboon@disroot.org \
--cc=me@tobias.gr \
--cc=simon@josefsson.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.