From: Simon Tournier <zimon.toutoune@gmail.com>
To: webmasters-comment@gnu.org
Cc: 66189@debbugs.gnu.org
Subject: bug#66189: [gnu.org #1975364] Broken link in Guix manual.
Date: Wed, 27 Sep 2023 11:28:14 +0200 [thread overview]
Message-ID: <86msx8hsnl.fsf@gmail.com> (raw)
In-Reply-To: <rt-4.2.16-14-g9a593ee-17542-1695629143-1144.1975364-8-0@rt.gnu.org>
Hi,
> Le Jeu 14 Sep 2023 09:14:20, yuval.langer@gmail.com a écrit :
>> https://ftp.gnu.org/gnu/guix/guix-system-vm-image-e5f7c14.x86_64-linux.qcow2
>>
>> in
>>
>> https://guix.gnu.org/manual/devel/en/html_node/Running-Guix-in-a-VM.html
>>
>> is broken.
Yes, the link is automatically generated by,
@url{@value{BASE-URL}/guix-system-vm-image-@value{VERSION}.x86_64-linux.qcow2}
For instance, today the last manual correspond to Guix revision faf3ca
and the link in this development manual reads,
https://ftp.gnu.org/gnu/guix/guix-system-vm-image-fafd3ca.x86_64-linux.qcow2
To my knowledge, no one is pushing to FTP all these images. As signaled
in the URL, this manual is the development manual (/devel/) continuously
generated and not the standard one carefully checked before release.
Well, discussion about the URL scheme is tracked by #51000 [1].
1: https://issues.guix.gnu.org/issue/51000
Cheers,
simon
next prev parent reply other threads:[~2023-10-02 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-1975364@rt.gnu.org>
[not found] ` <161F0253-4E5D-4057-B74C-27830E91D3E6@gmail.com>
2023-09-25 8:05 ` bug#66189: [gnu.org #1975364] Broken link in Guix manual Therese Godefroy via RT
2023-09-27 9:28 ` Simon Tournier [this message]
2023-10-04 2:39 ` Maxim Cournoyer
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=86msx8hsnl.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=66189@debbugs.gnu.org \
--cc=webmasters-comment@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).