From: Luke Yasuda <jing@jing.rocks>
To: pve-devel@lists.proxmox.com
Cc: Luke Yasuda <jing@jing.rocks>
Subject: [PATCH 3/3 proxmox-rrd-migration-tool] d/control: add missing build-deps librrd-dev
Date: Thu, 8 Oct 2026 15:48:45 +0900 [thread overview]
Message-ID: <20261008065200.1686526-3-jing@jing.rocks> (raw)
In-Reply-To: <20261008065200.1686526-1-jing@jing.rocks>
Otherwise it can't find rrd.h
Signed-off-by: Luke Yasuda <jing@jing.rocks>
---
debian/control | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/control b/debian/control
index eb1e5ff..d44fb09 100644
--- a/debian/control
+++ b/debian/control
@@ -12,6 +12,7 @@ Build-Depends: cargo:native,
librust-pkg-config-dev,
librust-pretty-assertions-dev,
librust-proxmox-async-0.5-dev,
+ librrd-dev,
libstd-rust-dev,
rrdtool,
rustc:native,
--
2.56.0
next prev parent reply other threads:[~2026-10-08 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 6:48 [PATCH 1/3 proxmox-rrd-migration-tool] use libc::c_char instead of i8 to fix mismatched type Luke Yasuda
2026-10-08 6:48 ` [PATCH 2/3 proxmox-rrd-migration-tool] d/control: add missing build-deps rust-crossbeam-channel Luke Yasuda
2026-10-08 6:48 ` Luke Yasuda [this message]
2026-10-08 7:39 ` [PATCH 1/3 proxmox-rrd-migration-tool] use libc::c_char instead of i8 to fix mismatched type Maximiliano Sandoval
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=20261008065200.1686526-3-jing@jing.rocks \
--to=jing@jing.rocks \
--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.