From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 宋文武 <iyzsong@envs.net>
Cc: 65282-done@debbugs.gnu.org, Dmitry Nikolaev <glaz@zho.pa>
Subject: bug#65282: guix-1.3 on Ubuntu-22.04 is broken because of outdated datefudge.
Date: Mon, 21 Aug 2023 16:02:33 -0400 [thread overview]
Message-ID: <87a5ukcgfa.fsf@gmail.com> (raw)
In-Reply-To: <87h6p0y2u0.fsf_-_@envs.net> ("宋文武"'s message of "Tue, 15 Aug 2023 19:14:47 +0800")
Hello,
宋文武 <iyzsong@envs.net> writes:
> Dmitry Nikolaev <glaz@zho.pa> writes:
>
>> The problem with guix-1.3 on Ubuntu-22.04 is not with datefudge. The
>> problem is ci.guix.gnu.org connectivity from Russia.
>
> Hello, you could try follow substitute mirrors if ci doesn't works:
>
> ci mirror: https://mirror.sjtu.edu.cn/guix/
> bordeaux: https://bordeaux.guix.gnu.org
> bordeaux mirror: https://bordeaux-singapore-mirror.cbaines.net
> bordeaux mirror: https://bordeaux-us-east-mirror.cbaines.net
>
> Hope this could be useful, thanks!
That's been reported before (lack of connectivity from Russia); the best
current solution is to remove https://ci.guix.gnu.org from your
substitute servers and use one of the above alternatives.
Also, is there a reason to use Guix 1.3? Guix 1.4 has long been
released.
Closing; thank you for the report.
--
Thanks,
Maxim
prev parent reply other threads:[~2023-08-21 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 5:28 bug#65282: guix-1.3 on Ubuntu-22.04 is broken because of outdated datefudge Dmitry Nikolaev via Bug reports for GNU Guix
2023-08-14 21:10 ` bug#65282: The problem is not with datefudge Dmitry Nikolaev via Bug reports for GNU Guix
[not found] ` <215c94ef-5916-d305-261f-3609e8abcf52@zho.pa>
2023-08-15 11:14 ` bug#65282: guix-1.3 on Ubuntu-22.04 is broken because of outdated datefudge 宋文武 via Bug reports for GNU Guix
2023-08-21 20:02 ` Maxim Cournoyer [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=87a5ukcgfa.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=65282-done@debbugs.gnu.org \
--cc=glaz@zho.pa \
--cc=iyzsong@envs.net \
/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).