From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Guillaume <09couplet.bitmap@icloud.com>, pve-devel@lists.proxmox.com
Subject: [pve-devel] applied-series: [PATCH container 0/3] fix #6719: add support for centos 10
Date: Mon, 15 Sep 2025 19:35:59 +0200 [thread overview]
Message-ID: <7dbca17f-d742-4b0a-b316-90b2c8c50ab8@proxmox.com> (raw)
In-Reply-To: <20250823222258.40428-1-09couplet.bitmap@icloud.com>
Am 24.08.25 um 00:22 schrieb Guillaume:
> In order to use CentOS 10, NetworkManager support had
> to be added in place of the network scripts that were removed in
> this major release.
>
> AlmaLinux, for example, chose to name its libsystemd-shared file with
> the major and minor versions separated by an underscore, which was
> not taken into account when determining the version of systemd.
>
> Guillaume (3):
> setup: add underscore in regex to parse systemd version
> setup: add support of el10 and implementing NetworkManager instead fo
> network-scripts
> tests: add tests for centos 10
>
Applied this series now, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-09-15 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250823222258.40428-1-09couplet.bitmap@icloud.com>
2025-08-23 22:22 ` [pve-devel] SPAM: [PATCH container 1/3] setup: add underscore in regex to parse systemd version Guillaume via pve-devel
2025-08-23 22:22 ` [pve-devel] SPAM: [PATCH container 2/3] setup: add support of el10 and implementing NetworkManager instead fo network-scripts Guillaume via pve-devel
2025-08-23 22:22 ` [pve-devel] SPAM: [PATCH container 3/3] tests: add tests for centos 10 Guillaume via pve-devel
2025-09-15 17:35 ` Thomas Lamprecht [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7dbca17f-d742-4b0a-b316-90b2c8c50ab8@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=09couplet.bitmap@icloud.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 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.