From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
by lore.proxmox.com (Postfix) with ESMTPS id 30CB31FF16F
for <inbox@lore.proxmox.com>; Fri, 15 Nov 2024 20:27:06 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 76F601B060;
Fri, 15 Nov 2024 20:27:07 +0100 (CET)
Date: Sat, 16 Nov 2024 04:26:49 +0900
To: pve-devel@lists.proxmox.com
In-Reply-To: <20241112190615.3293806-2-jing@jing.rocks>
References: <20241112190615.3293806-2-jing@jing.rocks>
MIME-Version: 1.0
Message-ID: <mailman.346.1731698826.391.pve-devel@lists.proxmox.com>
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
From: Jing Luo via pve-devel <pve-devel@lists.proxmox.com>
Precedence: list
Cc: Jing Luo <jing@jing.rocks>
X-Mailman-Version: 2.1.29
X-BeenThere: pve-devel@lists.proxmox.com
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
Subject: Re: [pve-devel] [PATCH ifupdown2] patches: upstream: python3.12
compat
Content-Type: multipart/mixed; boundary="===============0782358820943063040=="
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
--===============0782358820943063040==
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <jing@jing.rocks>
X-Original-To: pve-devel@lists.proxmox.com
Delivered-To: pve-devel@lists.proxmox.com
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
(No client certificate requested)
by lists.proxmox.com (Postfix) with ESMTPS id 04CCBC56F8
for <pve-devel@lists.proxmox.com>; Fri, 15 Nov 2024 20:27:06 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id D117A1B086
for <pve-devel@lists.proxmox.com>; Fri, 15 Nov 2024 20:27:05 +0100 (CET)
Received: from mail-gw3.jing.rocks (mail-gw3.jing.rocks [219.117.250.209])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
(No client certificate requested)
by firstgate.proxmox.com (Proxmox) with ESMTPS
for <pve-devel@lists.proxmox.com>; Fri, 15 Nov 2024 20:27:02 +0100 (CET)
Received: from mail-gw3.jing.rocks (localhost [127.0.0.1])
by mail-gw3.jing.rocks (Proxmox) with ESMTP id 4441B17D53
for <pve-devel@lists.proxmox.com>; Sat, 16 Nov 2024 04:26:52 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jing.rocks; h=cc
:content-transfer-encoding:content-type:content-type:date:from
:from:in-reply-to:message-id:mime-version:references:reply-to
:subject:subject:to:to; s=mail-gw; bh=DVX7h+w6uOiIqJgy4ztNc0Bmnv
49dEiQbkJ0vkWpkAU=; b=YLjYLsyrquvRifYKMhJxBS4Hd9AGrcJSVMAe55X+gr
KabPQhjfpZKA7sAptNXs7vBif6WW+62Rg2+o+2IquYGa4FNNdsnfwGsAKLdgDRPu
Vh/AHhFWnZyWvwFp/ncbf4oRJ4s272BOq4FPin/EEWttiMyte3KV5PauXZjtN1Cc
Rl5/jHqpLuvcU4ReCQ5Psq5oDaEyNfmQBlz2SIf2lsNS7DmnaJY5zybZQkYSX7fA
ofPONsUdv8TnLRxoIxf+ZGJAnlQl311HHdBJSJAmni0ozXEGC2Fby5zABmq5mYVi
Sth1fDXCXxXoKWh81EhnKQpBVUVd4Bzb+ivHHHlXwzsg==
Received: from mail.jing.rocks (mail.jing.rocks [IPv6:240b:10:f00:1b00::222])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
(No client certificate requested)
by mail-gw3.jing.rocks (Proxmox) with ESMTPS id 9939518197
for <pve-devel@lists.proxmox.com>; Sat, 16 Nov 2024 04:26:49 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=jing.rocks;
s=default; t=1731698809;
bh=Ncg5QKYUj+r5vMZD8TZxE73KTyoTHVUnl797cI3pWEI=;
h=Date:From:To:Subject:In-Reply-To:References:From;
b=GwRVMjlH0bedMBLrl78Bpuydl+NUW+xz5IAtA2sktepVyFcqtTA679850j2RWYEAT
5uYlx9NKwia+Y4r0f/BErxhXU0Ns0WxeoXS9qHxcg6X3u3whCDhIo/PH5/n53LNvyD
jQsdTMOEtBSZV2LTo/r9ZiyyOShYd2/TFgb5pqF/MrS9VeJuOYb7RrD5j9SrcBTKGm
Yt+8e4L29SNpoHh9WKkW1uh9HIcmuJDTjxwWmL+0EuHTU6aiqNXLgZkgq0DJgouejc
enxWV4SL6tVodNXktCJHWhS1ri3p63VAR/7swH+u9mTtBvdhcgb3ACjeOpv6Qq1BXB
bxmGpH3urR/4g==
Received: from mail.jing.rocks (localhost [127.0.0.1])
(Authenticated sender: jing@jing.rocks)
by mail.jing.rocks (Postfix) with ESMTPSA id 82306309E0
for <pve-devel@lists.proxmox.com>; Sat, 16 Nov 2024 04:26:49 +0900 (JST)
MIME-Version: 1.0
Date: Sat, 16 Nov 2024 04:26:49 +0900
From: Jing Luo <jing@jing.rocks>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH ifupdown2] patches: upstream: python3.12 compat
In-Reply-To: <20241112190615.3293806-2-jing@jing.rocks>
References: <20241112190615.3293806-2-jing@jing.rocks>
Message-ID: <312601959cc09c4c022036550dde6215@jing.rocks>
X-Sender: jing@jing.rocks
Content-Type: text/plain; charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit
X-SPAM-LEVEL: Spam detection results: 0
AWL -0.002 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid
DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain
DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain
DMARC_PASS -0.1 DMARC pass policy
KAM_INFOUSMEBIZ 0.75 Prevalent use of .info|.us|.me|.me.uk|.biz|xyz|id|rocks|life domains in spam/malware
KAM_OTHER_BAD_TLD 0.75 Other untrustworthy TLDs
RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information.
RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information.
RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information.
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [jing.rocks,main.py]
Forgot to add "ifupdown2" to [PATCH], so resend. Oops
On 2024-11-13 04:06, Jing Luo wrote:
> Prepare for debian trixie. Upstream has not yet made a new release
> since
> Dec 2023, backporting this commit to make ifupdown2 work on trixie.
> Also
> fixes an RC bug on debian (#1074250). Also fixed a typo in the commit
> msg.
>
> upstream:
> https://github.com/CumulusNetworks/ifupdown2/commit/fc0318378e878ffe639d1d1285936d1256dd67cf
> Signed-off-by: Jing Luo <jing@jing.rocks>
> ---
> debian/patches/series | 1 +
> .../upstream/0001-python312-compat.patch | 27 +++++++++++++++++++
> 2 files changed, 28 insertions(+)
> create mode 100644 debian/patches/upstream/0001-python312-compat.patch
>
> diff --git a/debian/patches/series b/debian/patches/series
> index 7ae3f0a..c14c181 100644
> --- a/debian/patches/series
> +++ b/debian/patches/series
> @@ -14,3 +14,4 @@ upstream/0001-scheduler-import-traceback.patch
>
> upstream/0001-addons-vxlan-fix-compare-between-remote-ips-and-old_.patch
>
> upstream/0001-scheduler-avoid-waiting-for-stdout-eof-of-etc-networ.patch
> upstream/0001-vxlan-fix-vni-filter.patch
> +upstream/0001-python312-compat.patch
> diff --git a/debian/patches/upstream/0001-python312-compat.patch
> b/debian/patches/upstream/0001-python312-compat.patch
> new file mode 100644
> index 0000000..c36482f
> --- /dev/null
> +++ b/debian/patches/upstream/0001-python312-compat.patch
> @@ -0,0 +1,27 @@
> +From fc0318378e878ffe639d1d1285936d1256dd67cf Mon Sep 17 00:00:00 2001
> +From: Jan Huijsmans <huysmans@koffie.nu>
> +Date: Tue, 9 Jul 2024 09:03:25 +0200
> +Subject: [PATCH] Bug #296: python 3.12 compatibility
> +
> +Since python 3.2, readfp needs to be replaced by read_file.
> +Python 3.12 dropped the readfp function.
> +
> +Patch provided as PR by me, as the original reporter failed to do
> +so since 4-4-2024 and my systems break due to this issue.
> +---
> + ifupdown2/ifupdown/main.py | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/ifupdown2/ifupdown/main.py b/ifupdown2/ifupdown/main.py
> +index 8e0f13f4..de6579ea 100644
> +--- a/ifupdown2/ifupdown/main.py
> ++++ b/ifupdown2/ifupdown/main.py
> +@@ -138,7 +138,7 @@ def read_config(self):
> + configStr = '[ifupdown2]\n' + config
> + configFP = io.StringIO(configStr)
> + parser = configparser.RawConfigParser()
> +- parser.readfp(configFP)
> ++ parser.read_file(configFP)
> + configmap_g = dict(parser.items('ifupdown2'))
> +
> + # Preprocess config map
--
Jing Luo
About me: https://jing.rocks/about/
GPG Fingerprint: 4E09 8D19 00AA 3F72 1899 2614 09B3 316E 13A1 1EFC
--===============0782358820943063040==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
--===============0782358820943063040==--