From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Cc: Lukas Wagner <l.wagner@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager] api: apt: Return valid utf8 on update
Date: Thu, 6 Nov 2025 18:52:31 +0100 [thread overview]
Message-ID: <176245155052.2370391.10205922849538591413.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250925144931.477293-1-m.sandoval@proxmox.com>
On Thu, 25 Sep 2025 16:49:29 +0200, Maximiliano Sandoval wrote:
> The following call could result in a broken encoding when a package
> description contains unicode characters.
>
> pvesh get /nodes/localhost/apt/update
>
> One potential example of such a package was libnbd0 where the character
> '—' (em dash) was rendered as 'â'.
>
> [...]
Applied, thanks!
[1/1] api: apt: Return valid utf8 on update
commit: 8b8917c7c8d3072c7394947d5a3f7713ecbc34ab
_______________________________________________
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-11-06 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 14:49 [pve-devel] " Maximiliano Sandoval
2025-11-06 17:52 ` Thomas Lamprecht [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=176245155052.2370391.10205922849538591413.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=m.sandoval@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