From: Simon Tournier <zimon.toutoune@gmail.com>
To: wxie@member.fsf.org
Cc: 67979-done@debbugs.gnu.org
Subject: bug#67979: guix pull failed with error
Date: Fri, 20 Sep 2024 17:50:45 +0200 [thread overview]
Message-ID: <874j6atjca.fsf@gmail.com> (raw)
In-Reply-To: <AS1P250MB060531E0A7D84299579DC7F9B0672@AS1P250MB0605.EURP250.PROD.OUTLOOK.COM>
Hi,
On dim., 15 sept. 2024 at 15:08, Wensheng Xie <xiewensheng@hotmail.com> wrote:
> On 二, 2024-09-10 at 16:04 +0200, Simon Tournier wrote:
>> What happens if you run:
[...]
> Thank you for looking into this bug.
>
> After I changed my channel to the official guix channel (slower), the
> problem is solved.
Thanks for your reply. Closing.
Cheers,
simon
prev parent reply other threads:[~2024-09-20 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 0:46 bug#67979: guix pull failed with error Wensheng Xie
2023-12-30 21:03 ` Pavel Korytov
2024-09-10 14:04 ` Simon Tournier
2024-09-15 7:08 ` Wensheng Xie
2024-09-20 15:50 ` Simon Tournier [this message]
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=874j6atjca.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=67979-done@debbugs.gnu.org \
--cc=wxie@member.fsf.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).