From: Luke Yasuda <jing@jing.rocks>
To: pve-devel@lists.proxmox.com
Cc: Luke Yasuda <jing@jing.rocks>
Subject: [PATCH pve-manager] fix typo risc64 => riscv64
Date: Mon, 5 Oct 2026 19:57:49 +0900 [thread overview]
Message-ID: <20261005105804.1078158-2-jing@jing.rocks> (raw)
Signed-off-by: Luke Yasuda <jing@jing.rocks>
---
PVE/API2/APT.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/API2/APT.pm b/PVE/API2/APT.pm
index 6dd4c261..93562b06 100644
--- a/PVE/API2/APT.pm
+++ b/PVE/API2/APT.pm
@@ -205,7 +205,7 @@ my $apt_package_return_props = {
Arch => {
type => 'string',
description => 'Package Architecture.',
- enum => [qw(armhf arm64 amd64 ppc64el risc64 s390x all)],
+ enum => [qw(armhf arm64 amd64 ppc64el riscv64 s390x all)],
},
Description => {
type => 'string',
--
2.55.0
next reply other threads:[~2026-10-05 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 10:57 Luke Yasuda [this message]
2026-10-05 11:07 ` [PATCH pve-manager] fix typo risc64 => riscv64 Fabian Grünbichler
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=20261005105804.1078158-2-jing@jing.rocks \
--to=jing@jing.rocks \
--cc=pve-devel@lists.proxmox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox