all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Rafa Gálvez" <rafa@esat.kuleuven.be>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Giovanni Biscuolo <g@xelera.eu>, 55537@debbugs.gnu.org
Subject: bug#55537: Guix pull after many months fails: substitutes for git-minimal-2.36.1 failed
Date: Tue, 31 May 2022 13:32:37 +0200	[thread overview]
Message-ID: <79e7c36f2c049148d0ab6eb923dd0ac6@esat.kuleuven.be> (raw)
In-Reply-To: <bed0fa1cc7e282e5aec91f907d413bab71035142.camel@telenet.be>

Hi,

  At the end, sudo -i "`which guix`" pull did the trick.

  After updating guix-daemon, I successfully updated normal guix.

  Thanks Giovanni and Maxime for your help!

  Best,

Rafa

On 2022-05-30 17:20, Maxime Devos wrote:
> Rafa Gálvez schreef op ma 30-05-2022 om 16:20 [+0200]:
>> ERROR: In procedure scm-error:
>> no code for module (ice-9 exceptions)
> 
> This one is a known issue, at <https://issues.guix.gnu.org/54546>.
> 
> Greetings,
> Maxime.




  reply	other threads:[~2022-05-31 11:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  7:56 bug#55537: Guix pull after many months fails: substitutes for git-minimal-2.36.1 failed Rafa Gálvez
2022-05-20 18:35 ` Josselin Poiret via Bug reports for GNU Guix
2022-05-25 11:37 ` Rafa Gálvez
2022-05-25 15:27   ` Maxime Devos
2022-05-30  7:55     ` Rafa Gálvez
2022-05-30  9:31       ` Maxime Devos
2022-05-30  9:59       ` Giovanni Biscuolo
2022-05-30 10:18         ` Rafa Gálvez
2022-05-30 10:22           ` Maxime Devos
2022-05-30 10:24           ` Maxime Devos
2022-05-30 14:20             ` Rafa Gálvez
2022-05-30 15:20               ` Maxime Devos
2022-05-31 11:32                 ` Rafa Gálvez [this message]
2022-05-30 13:44           ` Giovanni Biscuolo
2022-05-30 14:22             ` Rafa Gálvez
2022-05-30 10:20         ` Maxime Devos
2022-05-30 14:12           ` Giovanni Biscuolo

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=79e7c36f2c049148d0ab6eb923dd0ac6@esat.kuleuven.be \
    --to=rafa@esat.kuleuven.be \
    --cc=55537@debbugs.gnu.org \
    --cc=g@xelera.eu \
    --cc=maximedevos@telenet.be \
    /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.