From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH 2/2] backport nettle-sys
Date: Thu, 12 Oct 2023 10:37:48 +0200 [thread overview]
Message-ID: <20231012083748.1751285-3-d.csapak@proxmox.com> (raw)
In-Reply-To: <20231012083748.1751285-1-d.csapak@proxmox.com>
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
src/nettle-sys/debian/changelog | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/src/nettle-sys/debian/changelog b/src/nettle-sys/debian/changelog
index ca97618c9..d4a2de38a 100644
--- a/src/nettle-sys/debian/changelog
+++ b/src/nettle-sys/debian/changelog
@@ -1,3 +1,9 @@
+rust-nettle-sys (2.2.0-2~bpo12+pve1) proxmox-rust; urgency=medium
+
+ * Rebuild for Debian Bookworm / Proxmox
+
+ -- Proxmox Support Team <support@proxmox.com> Thu, 12 Oct 2023 09:26:52 +0200
+
rust-nettle-sys (2.2.0-2) unstable; urgency=medium
* Package nettle-sys 2.2.0 from crates.io using debcargo 2.6.0
--
2.30.2
next prev parent reply other threads:[~2023-10-12 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 8:37 [pve-devel] [PATCH debcargo-conf boookworm 0/2] update nettle-sys to 2.2 Dominik Csapak
2023-10-12 8:37 ` [pve-devel] [PATCH 1/2] update nettle-sys Dominik Csapak
2023-10-12 8:37 ` Dominik Csapak [this message]
2023-10-12 14:11 ` [pve-devel] applied-series: [PATCH debcargo-conf boookworm 0/2] update nettle-sys to 2.2 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=20231012083748.1751285-3-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