all lists on lists.proxmox.com
 help / color / mirror / Atom feed
* [pve-devel] [PATCH manager/pmg-api 0/2] Fix #6748: correct usage of Term::ReadLine
@ 2025-09-02 18:20 Sebastian Luksch via pve-devel
  2025-09-04 11:56 ` Fabian Grünbichler
  0 siblings, 1 reply; 3+ messages in thread
From: Sebastian Luksch via pve-devel @ 2025-09-02 18:20 UTC (permalink / raw)
  To: pve-devel; +Cc: Sebastian Luksch

[-- 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [pve-devel] [PATCH manager/pmg-api 0/2] Fix #6748: correct usage of Term::ReadLine
  2025-09-02 18:20 [pve-devel] [PATCH manager/pmg-api 0/2] Fix #6748: correct usage of Term::ReadLine Sebastian Luksch via pve-devel
@ 2025-09-04 11:56 ` Fabian Grünbichler
  2025-09-04 17:52   ` Sebastian Luksch via pve-devel
  0 siblings, 1 reply; 3+ messages in thread
From: Fabian Grünbichler @ 2025-09-04 11:56 UTC (permalink / raw)
  To: Proxmox VE development discussion; +Cc: Sebastian Luksch

On September 2, 2025 8:20 pm, Sebastian Luksch via pve-devel wrote:
> 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.

Hi!

thanks for your patches. could you please also send a signed CLA as
described in our Developer Documentation[0] to office@proxmox.com?

thanks!
Fabian

0: https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright


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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [pve-devel] [PATCH manager/pmg-api 0/2] Fix #6748: correct usage of Term::ReadLine
  2025-09-04 11:56 ` Fabian Grünbichler
@ 2025-09-04 17:52   ` Sebastian Luksch via pve-devel
  0 siblings, 0 replies; 3+ messages in thread
From: Sebastian Luksch via pve-devel @ 2025-09-04 17:52 UTC (permalink / raw)
  To: Fabian Grünbichler
  Cc: Sebastian Luksch, Proxmox VE development discussion

[-- Attachment #1: Type: message/rfc822, Size: 5248 bytes --]

From: Sebastian Luksch <bugzilla.proxmox.com@lookshe.org>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager/pmg-api 0/2] Fix #6748: correct usage of Term::ReadLine
Date: Thu, 04 Sep 2025 19:52:59 +0200
Message-ID: <e855fbb33d3dc1bcc9658ecb7912a29e@lookshe.org>

Hi,

thanks for your work maintaining the project. I noticed the request to 
fill out a CLA, and I wanted to share a quick thought.

While I appreciate the importance of formal contribution processes, I 
find the CLA requirements a bit too involved for such small patches, 
especially considering the amount of personal information requested. I'd 
prefer not to go through that process for this minor contribution.

If there's a way to accept small patches under the existing project 
license (AGPL) without requiring a CLA, I'd be happy contributing in 
that manner. Otherwise, I understand if you can't include the patches.

Thanks again for your time and consideration.

Best regards,
Sebastian

Am 2025-09-04 13:56, schrieb Fabian Grünbichler:
> On September 2, 2025 8:20 pm, Sebastian Luksch via pve-devel wrote:
>> 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.
> 
> Hi!
> 
> thanks for your patches. could you please also send a signed CLA as
> described in our Developer Documentation[0] to office@proxmox.com?
> 
> thanks!
> Fabian
> 
> 0:
> https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright


[-- 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-09-05 10:17 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-09-02 18:20 [pve-devel] [PATCH manager/pmg-api 0/2] Fix #6748: correct usage of Term::ReadLine Sebastian Luksch via pve-devel
2025-09-04 11:56 ` Fabian Grünbichler
2025-09-04 17:52   ` Sebastian Luksch via pve-devel

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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal