From: "Ludovic Courtès" <ludo@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: Thu, 06 May 2021 22:55:26 +0200 [thread overview]
Message-ID: <87eeejd1kx.fsf@gnu.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")
Hi,
Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org> skribis:
> 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").
> 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.
> 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
> 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’.
next prev parent reply other threads:[~2021-05-06 20:56 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 [this message]
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=87eeejd1kx.fsf@gnu.org \
--to=ludo@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).