unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: 48214@debbugs.gnu.org
Subject: bug#48214: inetutils-1.9.4 build fails
Date: Sat, 08 May 2021 14:53:28 +0200	[thread overview]
Message-ID: <87lf8p8jzr.fsf@gnu.org> (raw)
In-Reply-To: <87lf8rgy60.fsf@disroot.org> (Bone Baboon's message of "Thu, 06 May 2021 20:55:35 -0400")

Hi,

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

> 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.

>>> 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’.

> 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.

>>> 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.

> 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’.




  parent reply	other threads:[~2021-05-08 12:54 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 [this message]
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=87lf8p8jzr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=48214@debbugs.gnu.org \
    --cc=bone.baboon@disroot.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 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).