From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Hannes Duerr <h.duerr@proxmox.com>
Subject: Re: [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 1/2] debian/control: adjust description and pve-manager dependency
Date: Mon, 2 Dec 2024 09:36:00 +0100 [thread overview]
Message-ID: <748d0d02-9429-4a57-99af-5113ac0e2690@proxmox.com> (raw)
In-Reply-To: <20241120112610.160234-2-h.duerr@proxmox.com>
On 11/20/24 12:26, Hannes Duerr wrote:
> remove the dependency of proxmox-dkms, since this package does not
> exist, and add the dependency of pve-manager, which should be installed
> with every reasonable Proxmox VE installation, so that the package can
> already be installed during the installation.
>
i think that's in reverse? we don't need pve-manager here AFAICT,
but if we want a dependency somewhere, we'd want to add this package
as a dependency of pve-manager, no?
from the current state of this package I don't see a reason to depend on any pve/proxmox packages
> Signed-off-by: Hannes Duerr <h.duerr@proxmox.com>
> ---
> debian/control | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/debian/control b/debian/control
> index 1c19a50..f119bdc 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -8,11 +8,10 @@ Homepage: https://www.proxmox.com
>
> Package: proxmox-nvidia-vgpu-helper
> Architecture: all
> -Depends: proxmox-dkms,
> +Depends: libapt-pkg-perl,
> + pve-manager,
> ${misc:Depends},
> -Description: Proxmox Nvidia vGPU systemd service
> - This package helps with the configuration of Nvidia vGPU
> - drivers by providing a systemd template service which
> +Description: Proxmox Nvidia vGPU helper script and systemd service
> + This package provides a script, that helps with installing all required
> + packages for the Nvidia vGPU driver, and also a systemd template service which
> configures the option SRI-OV per pci-id
> -
> -
_______________________________________________
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:[~2024-12-02 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 11:26 [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 0/2] reduce setup steps for nvidia vgpu drivers Hannes Duerr
2024-11-20 11:26 ` [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 1/2] debian/control: adjust description and pve-manager dependency Hannes Duerr
2024-12-02 8:36 ` Dominik Csapak [this message]
2024-12-02 9:45 ` Hannes Dürr
2024-11-20 11:26 ` [pve-devel] [PATCH proxmx-nvidia-vgpu-helper 2/2] add script to help with the installation of the nvidia vgpu dependencies Hannes Duerr
2024-12-02 8:47 ` Dominik Csapak
2024-12-02 9:45 ` Hannes Dürr
2024-12-02 15:17 ` Thomas Lamprecht
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=748d0d02-9429-4a57-99af-5113ac0e2690@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=h.duerr@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal