unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexandre Hannud Abdo <abdo@member.fsf.org>
To: Simon Tournier <zimon.toutoune@gmail.com>, 71151@debbugs.gnu.org
Subject: bug#71151: time machine breaking
Date: Wed, 5 Jun 2024 19:30:35 +0200	[thread overview]
Message-ID: <f897960e-97e6-84d9-f96f-a7521a8c0f54@member.fsf.org> (raw)
In-Reply-To: <87zfrzo3g1.fsf@gmail.com>

Ni! Well, at least with my current setup, both commands finished fine. Or did you want their outputs?

I no longer have easy access to the other machine, it belonged to a colleague...

.~´

Le 05/06/2024 à 16:43, Simon Tournier a écrit :
> Hi Alexandre,
>
> On Wed, 05 Jun 2024 at 02:05, Alexandre Hannud Abdo <abdo@member.fsf.org> wrote:
>
>>> Using 6ba29e0, it works for me.
>> I saw the issue on two different machines, one with GuixSD another a
>> Debian with Guix freshly installed.
> Is it the same ’guix describe’ for the two machines?  And the same
> revision of guix-daemon?
>
> Could you run:
>
>      guix build /gnu/store/mh01bp841xvcvv8mv6car7l92h6h19rk-curl-7.84.0.drv
>
> ?  And then,
>
>      guix build /gnu/store/mh01bp841xvcvv8mv6car7l92h6h19rk-curl-7.84.0.drv --check
>
>
> Well, my hypothesis is the issue comes from the lack of some substitutes
> when you ran it.  And now, this substitutes is there.  Maybe, the test
> suite of curl – the one mentioned by the backtrace but no specific
> reason that the one :-) – does not pass on your hardware.
>
> Cheers,
> simon
>




  reply	other threads:[~2024-06-05 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 19:31 bug#71151: time machine breaking Alexandre Hannud Abdo
2024-06-04 19:03 ` Simon Tournier
2024-06-05  0:05   ` Alexandre Hannud Abdo
2024-06-05 14:43     ` Simon Tournier
2024-06-05 17:30       ` Alexandre Hannud Abdo [this message]
2024-06-05 17:43         ` Simon Tournier
2024-06-06  2:06           ` Alexandre Hannud Abdo

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=f897960e-97e6-84d9-f96f-a7521a8c0f54@member.fsf.org \
    --to=abdo@member.fsf.org \
    --cc=71151@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).