all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: 71577@debbugs.gnu.org
Subject: bug#71577: Some Images jobset lack artifacts
Date: Sat, 15 Jun 2024 19:43:17 +0000	[thread overview]
Message-ID: <CAEwRq=q3XeJ8E-TYmsEyRb5phX7FuL0k205ah==X2_wuh7nfgw@mail.gmail.com> (raw)

Hello,

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)

BTW, DL latest page also lacks checksum files to verify integrity.

So I looked at the CI, in the images jobset page (3), and strangely,
some jobs have "Build outputs" download links (but no checksum either),
whereas some other only have "Outputs" which is a store file path:

have downloadable artifacts:
    hurd-barebones.qcow2
    iso9660-image
    pine64-barebones-raw-image
    pinebook-pro-barebones-raw-image

no downloadable artifacts:
    novena-barebones-raw-image
    disk-image

Is that intended or an oversight ?

I think if this is fixed (missing artifacts and checksums), that page
could replace the "Download / Latest" one and the menu link could
directly link here.

WDYT ?

(1) - https://guix.gnu.org/en/download/latest
(2) - https://guix.gnu.org/en/download
(3) - https://ci.guix.gnu.org/jobset/images

-- 
Vincent Legoll




             reply	other threads:[~2024-06-15 20:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-15 19:43 Vincent Legoll [this message]
2024-06-24  8:49 ` bug#71577: Some Images jobset lack artifacts Ludovic Courtès
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='CAEwRq=q3XeJ8E-TYmsEyRb5phX7FuL0k205ah==X2_wuh7nfgw@mail.gmail.com' \
    --to=vincent.legoll@gmail.com \
    --cc=71577@debbugs.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 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.