From: n.frey@proxmox.com
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-manager 1/5] Fix grammar in ifupdown2 version error message
Date: Fri, 19 Sep 2025 11:33:28 +0200 [thread overview]
Message-ID: <20250919093915.21641-2-n.frey@proxmox.com> (raw)
In-Reply-To: <20250919093915.21641-1-n.frey@proxmox.com>
From: Nicolas Frey <n.frey@proxmox.com>
Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
---
PVE/API2/Network.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/API2/Network.pm b/PVE/API2/Network.pm
index 7fb7667e..fc053fec 100644
--- a/PVE/API2/Network.pm
+++ b/PVE/API2/Network.pm
@@ -873,7 +873,7 @@ sub assert_ifupdown2_installed {
die "you need ifupdown2 to reload network configuration\n" if !-e '/usr/share/ifupdown2';
my ($v, $pve, $v_str) = ifupdown2_version();
die
- "incompatible 'ifupdown2' package version '$v_str'! Did you installed from Proxmox repositories?\n"
+ "incompatible 'ifupdown2' package version '$v_str'! Did you install from Proxmox repositories?\n"
if $v < (1 * 100000 + 2 * 1000 + 8 * 10) || !$pve;
}
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-09-19 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 9:33 [pve-devel] [PATCH pve-manager 0/5] api: add return schemas and fix grammar in ifupdown2 " n.frey
2025-09-19 9:33 ` n.frey [this message]
2025-09-19 9:33 ` [pve-devel] [PATCH pve-manager 2/5] api: add ACME plugin return schema n.frey
2025-09-19 9:33 ` [pve-devel] [PATCH pve-manager 3/5] api: add APT versions " n.frey
2025-09-19 9:33 ` [pve-devel] [PATCH pve-manager 4/5] api: add service state " n.frey
2025-09-19 9:33 ` [pve-devel] [PATCH pve-manager 5/5] api: add replication config read " n.frey
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=20250919093915.21641-2-n.frey@proxmox.com \
--to=n.frey@proxmox.com \
--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