From: "Ludovic Courtès" <ludo@gnu.org>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: 71577@debbugs.gnu.org
Subject: bug#71577: Some Images jobset lack artifacts
Date: Mon, 24 Jun 2024 10:49:34 +0200 [thread overview]
Message-ID: <87wmmek9nl.fsf@gnu.org> (raw)
In-Reply-To: <CAEwRq=q3XeJ8E-TYmsEyRb5phX7FuL0k205ah==X2_wuh7nfgw@mail.gmail.com> (Vincent Legoll's message of "Sat, 15 Jun 2024 19:43:17 +0000")
Hi Vincent,
Vincent Legoll <vincent.legoll@gmail.com> skribis:
> I wanted to try a fresh guix in a VM, but the "Download / Latest"
> page (1) does not have the:
> "QCOW2 virtual machine (VM) image"
> "GNU Guix 1.4.0 QEMU Image"
> that is available on the "Download / Standard" page (2)
This is now fixed:
https://guix.gnu.org/en/download/latest/
For the record, the problem was that we’d be removing GC roots too
early, which was fixed here:
https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=489fc437c7b3aa0af41a40d6090eb4c51ced0028
> BTW, DL latest page also lacks checksum files to verify integrity.
Since this process is automated, there cannot be a signature to verify
the authenticity of those binaries (integrity is most likely verified
indirectly via embedded checksums in the container formats).
> no downloadable artifacts:
> novena-barebones-raw-image
> disk-image
>
> Is that intended or an oversight ?
I think it was intentional that we’d only provide the “most useful”
images for download. If you think others should be added, please let’s
discuss it on guix-devel.
Thanks!
Ludo’.
next prev parent reply other threads:[~2024-06-24 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 19:43 bug#71577: Some Images jobset lack artifacts Vincent Legoll
2024-06-24 8:49 ` Ludovic Courtès [this message]
2024-06-24 18:30 ` Vincent Legoll
2024-06-25 14:54 ` Ludovic Courtès
2024-06-25 21:11 ` Vincent Legoll via Bug reports for GNU Guix
2024-07-05 7:43 ` Ludovic Courtès
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=87wmmek9nl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=71577@debbugs.gnu.org \
--cc=vincent.legoll@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 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.