From: Christian Ebner <c.ebner@proxmox.com>
To: Erik Fastermann <e.fastermann@proxmox.com>,
pbs-devel@lists.proxmox.com, pdm-devel@lists.proxmox.com
Cc: Lukas Wagner <l.wagner@proxmox.com>
Subject: Re: [PATCH proxmox 1/3] system-report: add crate for shared report generation
Date: Wed, 29 Jul 2026 14:08:05 +0200 [thread overview]
Message-ID: <bea3bc73-bc06-4fb6-b5de-0a1319ef3b9b@proxmox.com> (raw)
In-Reply-To: <39404168-b9e6-4321-9250-7cd0e6bc6362@proxmox.com>
On 7/29/26 1:55 PM, Erik Fastermann wrote:
> Thank you for the review. Some notes/questions below. I will send the v2
> ASAP.
>
> [snip]
>
>>> diff --git a/proxmox-system-report/debian/copyright b/proxmox-system-
>>> report/debian/copyright
>>> new file mode 100644
>>> index 00000000..77952eba
>>> --- /dev/null
>>> +++ b/proxmox-system-report/debian/copyright
>>> @@ -0,0 +1,18 @@
>>> +Format: https://www.debian.org/doc/packaging-manuals/copyright-
>>> format/1.0/
>>> +
>>> +Files:
>>> + *
>>> +Copyright: 2019 - 2026 Proxmox Server Solutions GmbH
>>> <support@proxmox.com>
>>
>> question: not sure about the copyright timespan here, but since the
>> factored out code lived in proxmox-backup and that has 2019-2026 this
>> is fine I guess?
>
> I checked and for the recently added `proxmox-disks` only 'Copyright:
> 2026' is used and that crate was also factored out from PBS, so I will
> do the same.
>
> [snip]
>
>>> + vec![
>>> + ("proxmox-boot-tool", vec!["status"]),
>>> + ("df", vec!["-h", "-T"]),
>>> + (
>>> + "lsblk",
>>> + vec![
>>> + "--ascii",
>>> + "-M",
>>> + "-o",
>>> + "+HOTPLUG,ROTA,PHY-SEC,FSTYPE,MODEL,TRAN",
>>> + ],
>>> + ),
>>> + ("bash", vec!["-c", "ls -l /dev/disk/by-*/"]),
>>> + ("zpool", vec!["status"]),
>>> + ("zfs", vec!["list"]),
>>> + ("zarcstat", vec![]),
>>> + ("dmidecode", vec!["-t", "bios"]),
>>> + ("lscpu", vec![]),
>>> + ("lspci", vec!["-nnk"]),
>>> + ("ip", vec!["-details", "-statistics", "a"]),
>>> + ("ip", vec!["-4", "route", "show"]),
>>> + ("ip", vec!["-6", "route", "show"]),
>>
>> comment: these commands depend on external executables. So there
>> should be a dependency in debian/control as well.
>
> E.g. `proxmox-disks` calls `zpool` and `sgdisk`, which are also not in
> the `Depends` section. In fact all crates I checked in this repository
> only have other Rust related `Depends`. It looks like either PBS or PDM
> depend on them directly or they are pulled in by the installer.
Right, since this is a lib only and does not produce any executable by
itself, it is not correct to pull these in. Disregard my comment with
respect to that.
> The `Depends` section of PDM or PBS might need some work in general.
> E.g. `iproute2` is missing from PDM `Depends`, but is given for PBS. I
> saw there was a patch which added some to PBS [0], but that was not
> applied to PDM. It would probably be good to check what dependencies
> should be added. Should this be part of this series? What do you think?
Yes, adding a patch to assure such dependencies is especially important
if PBS or PDM are installed on top of a vanilla Debian and not via the
installer.
next prev parent reply other threads:[~2026-07-29 12:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 8:31 [PATCH proxmox{,-backup,-datacenter-manager} 0/3] factor system report into shared crate Erik Fastermann
2026-07-14 8:31 ` [PATCH proxmox 1/3] system-report: add crate for shared report generation Erik Fastermann
2026-07-28 13:59 ` Christian Ebner
2026-07-29 11:55 ` Erik Fastermann
2026-07-29 12:08 ` Christian Ebner [this message]
2026-07-14 8:31 ` [PATCH proxmox-backup 2/3] report: use shared proxmox-system-report crate Erik Fastermann
2026-07-28 13:59 ` Christian Ebner
2026-07-14 8:31 ` [PATCH proxmox-datacenter-manager 3/3] " Erik Fastermann
2026-07-28 13:59 ` Christian Ebner
2026-07-14 9:05 ` [PATCH proxmox{,-backup,-datacenter-manager} 0/3] factor system report into shared crate Erik Fastermann
2026-07-28 13:59 ` Christian Ebner
2026-07-30 11:14 ` superseded: " Erik Fastermann
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=bea3bc73-bc06-4fb6-b5de-0a1319ef3b9b@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=e.fastermann@proxmox.com \
--cc=l.wagner@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