public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] applied: [PATCH proxmox-firewall] d/control: drop unused build dependencies
Date: Fri, 24 Jan 2025 13:49:49 +0100	[thread overview]
Message-ID: <1737722973.9sp1wps9xa.astroid@yuna.none> (raw)
In-Reply-To: <20250124121950.717364-2-c.heiss@proxmox.com>

On January 24, 2025 1:19 pm, Christoph Heiss wrote:
> These are simply just of the proxmox-ve-config crate, which was
> moved to a separate repository in
> 
>   aa7692036 ("add proxmox-ve-rs crate - move proxmox-ve-config there")
> 
> and are not used by the other remaining crates.
> 
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
>  debian/control | 5 -----
>  1 file changed, 5 deletions(-)
> 
> diff --git a/debian/control b/debian/control
> index ea2401b..7c60d79 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -7,18 +7,13 @@ Build-Depends: cargo:native,
>                 librust-anyhow-1+default-dev,
>                 librust-env-logger-0.10+default-dev,
>                 librust-insta-dev,
> -               librust-libc-0.2+default-dev,
>                 librust-log-0.4+default-dev (>= 0.4.17-~~),
> -               librust-nix-0.26+default-dev (>= 0.26.1-~~),
> -               librust-proxmox-schema-3+default-dev (>= 3.1.2-~~),
> -               librust-proxmox-sortable-macro-dev,
>                 librust-proxmox-sys-dev (>= 0.6~),
>                 librust-proxmox-ve-config-dev (>= 0.2~),
>                 librust-serde-1+default-dev,
>                 librust-serde-1+derive-dev,
>                 librust-serde-json-1+default-dev,
>                 librust-serde-plain-1+default-dev,
> -               librust-serde-with+default-dev,
>                 librust-signal-hook-dev,
>                 librust-thiserror-dev,
>                 libstd-rust-dev,
> -- 
> 2.47.0
> 
> 
> 
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 
> 
> 


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      reply	other threads:[~2025-01-24 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 12:19 [pve-devel] [PATCH proxmox-firewall] d/control: drop unused build dependencies Christoph Heiss
2025-01-24 12:49 ` Fabian Grünbichler [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=1737722973.9sp1wps9xa.astroid@yuna.none \
    --to=f.gruenbichler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal