From: Sebastian Luksch via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Sebastian Luksch <bugzilla.proxmox.com@lookshe.org>
Subject: [pve-devel] [PATCH manager/pmg-api 0/2] Fix #6748: correct usage of Term::ReadLine
Date: Tue, 2 Sep 2025 20:20:29 +0200 [thread overview]
Message-ID: <mailman.199.1756915662.418.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 4680 bytes --]
From: Sebastian Luksch <bugzilla.proxmox.com@lookshe.org>
To: pve-devel@lists.proxmox.com
Cc: Sebastian Luksch <bugzilla.proxmox.com@lookshe.org>
Subject: [PATCH manager/pmg-api 0/2] Fix #6748: correct usage of Term::ReadLine
Date: Tue, 2 Sep 2025 20:20:29 +0200
Message-ID: <20250902182031.1080266-1-bugzilla.proxmox.com@lookshe.org>
The update to debian trixie also updated libterm-readline-gnu-perl to version
1.46-1. Since this version it is not possible to create more than one
Term:ReadLine object. These patches fix the last occurences where multiple
objects were created in all active repositories found under
https://git.proxmox.com.
pve-manager:
Sebastian Luksch (1):
use Term::ReadLine->new() only once
PVE/CLI/pvenode.pm | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
pmg-api:
Sebastian Luksch (1):
use Term::ReadLine->new() only once
src/PMG/CLI/pmgconfig.pm | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
--
2.30.2
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-09-03 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 18:20 Sebastian Luksch via pve-devel [this message]
2025-09-04 11:56 ` Fabian Grünbichler
2025-09-04 17:52 ` Sebastian Luksch via pve-devel
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=mailman.199.1756915662.418.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=bugzilla.proxmox.com@lookshe.org \
/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.