From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com,
Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
Subject: applied: [pve-devel] [PATCH pve-common] Update PVE development setup documentation
Date: Thu, 16 Jul 2026 11:57:35 +0200 [thread overview]
Message-ID: <178419584465.56584.674181217631899390.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260123153939.346440-1-a.bied-charreton@proxmox.com>
On Fri, 23 Jan 2026 16:36:00 +0100, Arthur Bied-Charreton wrote:
> The repository configuration docs contained instructions about Debian
> 12, and they were still referring to pvetest instead of pve-test.
>
> Also updated the package list, removed the packages that don't exist
> anymore and added the ones I needed to install while building some
> subsystems for the first time.
Applied, thanks! Removed some more outdated packages from the list and
updated the path for the enterprise sources: .sources instead of .list
[1/1] Update PVE development setup documentation
commit: f1c3703aab2e6734d450b84f34708ac57b23a3aa
prev parent reply other threads:[~2026-07-16 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 15:36 [pve-devel] [PATCH pve-common] Update PVE development setup documentation Arthur Bied-Charreton
2026-07-16 9:57 ` Fiona Ebner [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=178419584465.56584.674181217631899390.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=a.bied-charreton@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 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.