From: Z572 <zhengjunjie@iscas.ac.cn>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 73811@debbugs.gnu.org
Subject: [bug#73811] [guix-artwork PATCH] website: images: Add VisionFive2 latest barebones image.
Date: Thu, 17 Oct 2024 22:34:54 +0800 [thread overview]
Message-ID: <87v7xq3ii9.fsf@iscas.ac.cn> (raw)
In-Reply-To: <87sesu6cvm.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Thu, 17 Oct 2024 16:08:13 +0200")
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> Hello Zheng. Your patch adds to the download-latest page a good-looking
> link towards
>
> https://ci.guix.gnu.org/search/latest/image?query=spec:images+status:success+system:x86_64-linux+visionfive2-barebones-raw-image
>
> similar to the existing Pinebook Pro link.
>
> However, CI fails to build images at the moment with errors at glibc.
This is fixed on https://git.savannah.gnu.org/cgit/guix.git/commit/?id=7749477876247199b0726d8dc6e93991a0c0c0f2
just need restart ci's cuirass. images jobs latest eval is "13 Oct 15:28 +0200".
>
> I guess it is too soon and this patch should wait until downloads can
> succeed. Although Pinebook Pro has a broken link as well.
>
> That you used an image of a computer screen is ironic, because HDMI
> support has not arrived in upstream Linux last time I checked and
> according to [1], but this is not important IMHO.
or maybe Guix-package.png ? I don't have any good ideas
>
> Regards,
> Florian
>
> [1] https://wiki.postmarketos.org/wiki/StarFive_VisionFive_2_(starfive-visionfive2)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2024-10-17 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 1:50 [bug#73811] [guix-artwork PATCH] website: images: Add VisionFive2 latest barebones image Zheng Junjie
2024-10-17 14:08 ` pelzflorian (Florian Pelz)
2024-10-17 14:34 ` Z572 [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=87v7xq3ii9.fsf@iscas.ac.cn \
--to=zhengjunjie@iscas.ac.cn \
--cc=73811@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).