From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Erik Fastermann" <e.fastermann@proxmox.com>,
<pbs-devel@lists.proxmox.com>, <pdm-devel@lists.proxmox.com>
Subject: applied: [PATCH proxmox-datacenter-manager v3 4/5] d/control: depend on tools used by the system report
Date: Thu, 20 Aug 2026 14:53:26 +0200 [thread overview]
Message-ID: <DKTSAY68SMKW.27VV6Q9FQ0GQF@proxmox.com> (raw)
In-Reply-To: <20260811114332.283776-5-e.fastermann@proxmox.com>
On Tue Aug 11, 2026 at 1:43 PM CEST, Erik Fastermann wrote:
> The report runs ip (package iproute2), top (package procps) and ethtool,
> plus zpool, zfs and zarcstat (package zfsutils-linux) for the ZFS
> sections and proxmox-boot-tool (package proxmox-kernel-helper) for the
> ESP status, none of which were depended on directly.
>
> The ZFS tools and proxmox-kernel-helper are recommendations rather than
> direct dependencies. For the ZFS tools this matches the control file in
> PBS and the proxmox-boot-tool is not required on systems which are not
> running a Proxmox kernel.
>
> Reviewed-by: Christian Ebner <c.ebner@proxmox.com>
> Tested-by: Christian Ebner <c.ebner@proxmox.com>
> Signed-off-by: Erik Fastermann <e.fastermann@proxmox.com>
> ---
> debian/control | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/debian/control b/debian/control
> index e40137e3..00d3d137 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -159,7 +159,10 @@ Rules-Requires-Root: no
> Package: proxmox-datacenter-manager
> Architecture: any
> Multi-Arch: allowed
> -Depends: libproxmox-acme-plugins,
> +Depends: ethtool,
> + iproute2,
> + libproxmox-acme-plugins,
> + procps,
> proxmox-datacenter-manager-docs,
> proxmox-mini-journalreader (>= 1.7),
> proxmox-termproxy,
> @@ -172,6 +175,8 @@ Recommends: ifupdown2,
> proxmox-datacenter-manager-client,
> proxmox-datacenter-manager-meta,
> proxmox-datacenter-manager-ui,
> + proxmox-kernel-helper,
> + zfsutils-linux,
> Description: Manage multiple Proxmox VE cluster and other Proxmox projects
> This package provides the API daemons of the Proxmox Datacenter Manager (PDM)
> which allows one to add multiple Proxmox VE and Proxmox Backup Server
Applied this one already, thanks!
next prev parent reply other threads:[~2026-08-20 12:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 11:43 [PATCH proxmox{,-backup,-datacenter-manager} v3 0/5] factor system report into shared crate Erik Fastermann
2026-08-11 11:43 ` [PATCH proxmox v3 1/5] system-report: add crate for shared report generation Erik Fastermann
2026-08-20 13:32 ` Lukas Wagner
2026-08-20 13:36 ` Christian Ebner
2026-08-20 13:46 ` Lukas Wagner
2026-08-11 11:43 ` [PATCH proxmox-backup v3 2/5] d/control: depend on tools used by the system report Erik Fastermann
2026-08-11 11:43 ` [PATCH proxmox-backup v3 3/5] report: use shared proxmox-system-report crate Erik Fastermann
2026-08-11 11:43 ` [PATCH proxmox-datacenter-manager v3 4/5] d/control: depend on tools used by the system report Erik Fastermann
2026-08-20 12:53 ` Lukas Wagner [this message]
2026-08-11 11:43 ` [PATCH proxmox-datacenter-manager v3 5/5] report: use shared proxmox-system-report crate Erik Fastermann
2026-08-12 9:59 ` [PATCH proxmox{,-backup,-datacenter-manager} v3 0/5] factor system report into shared crate Nicolas 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=DKTSAY68SMKW.27VV6Q9FQ0GQF@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=e.fastermann@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pdm-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