From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Stefan Hanreich <s.hanreich@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: [pve-devel] applied: [PATCH proxmox-firewall v2 1/1] cargo: update proxmox-ve-config
Date: Thu, 13 Mar 2025 14:18:54 +0100 [thread overview]
Message-ID: <gf34zkf7gmd3o3umtcoh3ti5wxu56odlykeqpb4ft5xgqxtwgk@3qfbm5gfbr3x> (raw)
In-Reply-To: <20250313124608.136789-1-s.hanreich@proxmox.com>
applied - but also generally updated d/control to fit the current
dependencies
On Thu, Mar 13, 2025 at 01:46:08PM +0100, Stefan Hanreich wrote:
> Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
> ---
>
> Notes:
> Changes from v1:
> * split from https://lore.proxmox.com/pve-devel/20250123101300.72647-1-s.hanreich@proxmox.com/
> * update d/control
>
> Cargo.toml | 2 +-
> debian/control | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Cargo.toml b/Cargo.toml
> index 31d15be..079fb79 100644
> --- a/Cargo.toml
> +++ b/Cargo.toml
> @@ -6,4 +6,4 @@ members = [
> resolver = "2"
>
> [workspace.dependencies]
> -proxmox-ve-config = { version = "0.2.0" }
> +proxmox-ve-config = { version = "0.2.2" }
> diff --git a/debian/control b/debian/control
> index 7c60d79..935db78 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -9,7 +9,7 @@ Build-Depends: cargo:native,
> librust-insta-dev,
> librust-log-0.4+default-dev (>= 0.4.17-~~),
> librust-proxmox-sys-dev (>= 0.6~),
> - librust-proxmox-ve-config-dev (>= 0.2~),
> + librust-proxmox-ve-config-dev (>= 0.2.2~),
> librust-serde-1+default-dev,
> librust-serde-1+derive-dev,
> librust-serde-json-1+default-dev,
> --
> 2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-03-13 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 12:46 [pve-devel] " Stefan Hanreich
2025-03-13 13:18 ` Wolfgang Bumiller [this message]
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=gf34zkf7gmd3o3umtcoh3ti5wxu56odlykeqpb4ft5xgqxtwgk@3qfbm5gfbr3x \
--to=w.bumiller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal