From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH debcargo-conf 1/8] nvml-wrapper-sys: Update to 0.9.0
Date: Thu, 5 Mar 2026 10:16:45 +0100 [thread overview]
Message-ID: <20260305091711.1221589-2-d.csapak@proxmox.com> (raw)
In-Reply-To: <20260305091711.1221589-1-d.csapak@proxmox.com>
From: Matthias Geiger <werdahias@debian.org>
(cherry picked from commit 797e79a7592084fe27602fc028b8e2d4450b0cc9)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
src/nvml-wrapper-sys/debian/changelog | 6 ++++++
src/nvml-wrapper-sys/debian/copyright.debcargo.hint | 7 +++++++
2 files changed, 13 insertions(+)
diff --git a/src/nvml-wrapper-sys/debian/changelog b/src/nvml-wrapper-sys/debian/changelog
index 99a7824a6b..7974dbd257 100644
--- a/src/nvml-wrapper-sys/debian/changelog
+++ b/src/nvml-wrapper-sys/debian/changelog
@@ -1,3 +1,9 @@
+rust-nvml-wrapper-sys (0.9.0-1) UNRELEASED-FIXME-AUTOGENERATED-DEBCARGO; urgency=medium
+
+ * Package nvml-wrapper-sys 0.9.0 from crates.io using debcargo 2.7.10
+
+ -- Matthias Geiger <werdahias@debian.org> Thu, 25 Sep 2025 14:37:56 +0200
+
rust-nvml-wrapper-sys (0.8.0-1) unstable; urgency=medium
* Team upload.
diff --git a/src/nvml-wrapper-sys/debian/copyright.debcargo.hint b/src/nvml-wrapper-sys/debian/copyright.debcargo.hint
index a50a9ec980..46c531de79 100644
--- a/src/nvml-wrapper-sys/debian/copyright.debcargo.hint
+++ b/src/nvml-wrapper-sys/debian/copyright.debcargo.hint
@@ -12,6 +12,13 @@ Comment:
be correct information so you should review and fix this before uploading to
the archive.
+Files: LICENSE-MIT
+Copyright: 2017 Jarek Samic
+License: UNKNOWN-LICENSE; FIXME (overlay)
+Comment:
+ FIXME (overlay): These notices are extracted from files. Please review them
+ before uploading to the archive.
+
Files: debian/*
Copyright:
2022-2025 Debian Rust Maintainers <pkg-rust-maintainers@alioth-lists.debian.net>
--
2.47.3
next prev parent reply other threads:[~2026-03-05 9:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 9:16 [PATCH common/debcargo-conf/manager/proxmox-perl-rs/qemu-server 00/13] use NVML for vGPU info querying Dominik Csapak
2026-03-05 9:16 ` Dominik Csapak [this message]
2026-03-05 9:16 ` [PATCH debcargo-conf 2/8] nvml-wrapper-sys: release 0.9.0-1 Dominik Csapak
2026-03-05 9:16 ` [PATCH debcargo-conf 3/8] nvml-wrapper: Update to 0.11.0 Dominik Csapak
2026-03-05 9:16 ` [PATCH debcargo-conf 4/8] nvml-wrapper: release 0.11.0-1 Dominik Csapak
2026-03-05 9:16 ` [PATCH debcargo-conf 5/8] nvml-wrapper: Update to 0.12.0 Dominik Csapak
2026-03-05 9:16 ` [PATCH debcargo-conf 6/8] nvml-wrapper: add patch for vgpu ids Dominik Csapak
2026-03-05 9:16 ` [PATCH debcargo-conf 7/8] backport nvml-wrapper-sys 0.9.0-1 Dominik Csapak
2026-03-05 9:16 ` [PATCH debcargo-conf 8/8] backport nvml-wrapper 0.12.0-1 Dominik Csapak
2026-03-05 9:16 ` [PATCH proxmox-perl-rs 1/1] pve: add binding for accessing vgpu info Dominik Csapak
2026-03-05 9:16 ` [PATCH qemu-server 1/2] pci: move mdev related code to own module Dominik Csapak
2026-03-05 9:16 ` [PATCH qemu-server 2/2] pci: mdev: use PVE::RS::NVML for nvidia mdev information Dominik Csapak
2026-03-05 9:16 ` [PATCH manager 1/1] api: hardware: pci: use NVML for querying " Dominik Csapak
2026-03-05 9:16 ` [PATCH common 1/1] sysfs tools: remove moved code Dominik Csapak
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=20260305091711.1221589-2-d.csapak@proxmox.com \
--to=d.csapak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox