[pve-devel] [PATCH promxox-mail-forward v2] fix logging by switching to proxmox-log
Thomas Lamprecht
t.lamprecht at proxmox.com
Mon Jun 16 21:28:34 CEST 2025
Am 13.06.25 um 09:54 schrieb Lukas Wagner:
> The proxmox-notify crate now uses tracing for logging, hence we have to
> set up some tracing logging infrastructure if we want to see any
> messages in the journal. Therefore we switch from the syslog crate to
> proxmox-log, which configures the appropriate layers/subscribers for
> tracing.
>
> Signed-off-by: Lukas Wagner <l.wagner at proxmox.com>
> Reviewed-by: Gabriel Goller <g.goller at proxmox.com>
> ---
> Changes since v1:
> - Use :# to print errors with more context
>
> Cargo.toml | 5 ++---
> debian/control | 4 ++--
> src/main.rs | 20 +++++++++++---------
> 3 files changed, 15 insertions(+), 14 deletions(-)
>
> diff --git a/Cargo.toml b/Cargo.toml
> index 8bbd89e..f23fc61 100644
> --- a/Cargo.toml
> +++ b/Cargo.toml
> @@ -15,9 +15,8 @@ exclude = [ "debian" ]
>
> [dependencies]
> anyhow = "1.0"
> -log = "0.4.17"
> nix = "0.26"
> -syslog = "6.0"
>
> -proxmox-sys = "0.6"
> +proxmox-log = "0.2.8"
> proxmox-notify = {version = "0.5.4", features = ["mail-forwarder", "pve-context", "pbs-context"] }
> +proxmox-sys = "0.6"
This is for bookworm based releases, is this not required for trixie based
releases anymore?
More information about the pve-devel
mailing list