From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4gfldQ4YZdz3076 for ; Tue, 16 Jun 2026 11:49:14 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "YR2" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4gfldM2s00z2xHk for ; Tue, 16 Jun 2026 11:49:11 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4gfldL65Xjz2SW; Tue, 16 Jun 2026 11:49:10 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1781610551; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yKziN2ceMVP6NMt2xCwwpcAKF7apJUV9BLtCbSitYmI=; b=depoExszytaM2FUE2hP8fS1R4lrwK+pQ81CrQcDzJorAEUZkxLrl1a2sAXIMsnfne8TrSW D8l2o6JIjInczICQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1781610551; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yKziN2ceMVP6NMt2xCwwpcAKF7apJUV9BLtCbSitYmI=; b=Ajg3lgljWgO3dpYkhMHNkWkXmOP3w/tbAhzXsygNKiInICR482UQivH3SG2UmoNHGsIBqF ZkOK+Dv0FukfxgSnZTJkCQ6GAynWEokbbCMiR6YiXg9xNXuwwH5zBLVv1XOcT3XeGo/J9B 1QXph6MdF9ZDKftIA76Zd296t8OABgIc1Pjy7b4x2LUxvxlVkwht3OEe+g54U3Sm176tmB EN5iy7mag9th6FTzY9LdAXPEJQX1tE8Tc4w/VHZpO1XEPAoOVMXo39LoatvZhOYvFxRz0H vp7xnWHNVFXDClfU/xc40ChfaZFNNTq3NW62T/85w1i7x8i4J0Cob19nFGOYLw== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Updating perl 5.36.0 => 5.42.2 - some questions From: Michael Tremer In-Reply-To: <5d90be69-e026-477e-96c1-056235b202c2@ipfire.org> Date: Tue, 16 Jun 2026 12:49:10 +0100 Cc: development@lists.ipfire.org, "IPFire: Belka, Adolf" Content-Transfer-Encoding: quoted-printable Message-Id: <0645F905-CBFC-4A53-9AD6-D0B86F43197B@ipfire.org> References: <2dd775e8-e645-43f2-8219-e79198e666e3@ipfire.org> <1D3FCBD1-16E5-450B-88A0-B27B1F337EDB@ipfire.org> <56142892-a026-4f3f-b446-f05153f87490@ipfire.org> <60287726-6a52-4c3d-af92-917f62d52759@ipfire.org> <0B8676F0-27B2-4DE2-BE12-301D2F827E4D@ipfire.org> <5d90be69-e026-477e-96c1-056235b202c2@ipfire.org> To: Matthias Fischer No worries, I wasn=E2=80=99t particularly quick with my response. What you sent looks good to me. I will reply to those emails once I = review them. > On 16 Jun 2026, at 12:47, Matthias Fischer = wrote: >=20 > On 16.06.2026 13:20, Michael Tremer wrote: >> Hello Matthias, >=20 > Hi Michael, >=20 >> Yes, this is a bug update because there are plenty of modules built = after the main package. >>=20 >> The best way would be to update them one by one - i.e. commit them = one by one. But since this is a lot, I would be happy to listen to any = other proposals. >=20 > Ups. Just saw your mail - a few seconds after I pushed the whole = thing, > sorry. >=20 > Take a look and decide - its really huge... ;-) >=20 > Best > Matthias >> Best, >> -Michael >>=20 >>> On 14 Jun 2026, at 22:04, Matthias Fischer = wrote: >>>=20 >>> Hi, >>>=20 >>> On 12.06.2026 13:19, Adolf Belka wrote: >>>> ... >>>> Feel free to do so but maybe you should also look at updating the = perl package itself. >>>> ... >>>=20 >>> I did. But I'm not quite sure what to do next and need a hint. >>>=20 >>> After "a few" rootfile-adjustments I got a build based on 'next' = with >>> 'perl 5.42.2' that is building without any errors. No seen problems. >>>=20 >>> Adjusting the rootfile for the new perl version was a = bit...extensive, >>> but I think I managed it. Build is running without any errors. >>>=20 >>> But there are about 70 rootfiles from 'common' to 'packages' who = thought >>> they were all alone now and wanted to come along. They all contained = the >>> perl version string '5.36.0', which now had to be changed to 5.42.2. >>>=20 >>> I think I need to push these files together with the actual perl = update. >>> This will take some place for an update... Since this is my first = perl >>> update I was a bit surprised how many files were affected. >>>=20 >>> Would this be ok? Updating perl leads to about ~70 files that need = to be >>> updated too and pushed because of changed rootfiles? >>>=20 >>> Best >>> Matthias >>>=20 >>>=20 >>=20 >>=20 >=20