unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Bone Baboon" <bone.baboon@disroot.org>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: 48214@debbugs.gnu.org
Subject: bug#48214: inetutils-1.9.4 build fails
Date: Fri, 07 May 2021 13:53:36 -0400	[thread overview]
Message-ID: <87r1iil9ac.fsf@netris.org> (raw)
In-Reply-To: <87lf8rgy60.fsf@disroot.org>

Hi,

Bone Baboon via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

> 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.
[...]
> 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)?

Right, the problem is that since you're avoiding substitutes, you need
to fix the core 'inetutils' package in order to build your system at
all.

Moreover, you're also having problems with overly aggressive test
timeouts in 'glib' (see <https://bugs.gnu.org/48024#20>), you'll need to
fix that package as well.

I've outlined one possible way forward here:

  https://bugs.gnu.org/48024#80

However, Ludovic might know of other alternatives.

    Regards,
      Mark

-- 
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>.




  parent reply	other threads:[~2021-05-07 17:55 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 [this message]
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=87r1iil9ac.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=48214@debbugs.gnu.org \
    --cc=bone.baboon@disroot.org \
    --cc=ludo@gnu.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).