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 4gv0m916nmz2xfM for ; Mon, 06 Jul 2026 10:22:33 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "YR2" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4gv0m52PNcz2xHd for ; Mon, 06 Jul 2026 10:22:29 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (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 mail01.ipfire.org (Postfix) with ESMTPSA id 4gv0m41vk3z3F; Mon, 06 Jul 2026 10:22:28 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1783333348; 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=YWU6nNOfz38oXywWEsCsLofcItPGIeVuUV72WYwYV1s=; b=B3rsp9bNO1cs7DuDVvqvrnIPWjm6pWOkW5OOrksAxiYw85aplqGiA6I3euYufivU9sj7kA xCjgNm53L5+XdNBQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1783333348; 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=YWU6nNOfz38oXywWEsCsLofcItPGIeVuUV72WYwYV1s=; b=pA5ykXm3Dnlq1cXz5j6CcqXzgMuGsHLYayyH24cKLaRIWQXhIY8505RW9u6pI6aaJgcVT6 +N4cxJA1roQjToDJxVuu5ggmB08foSHqNHIpuZlb8ZyKnHXvHN3vOXW37yoFQcNOe1aRX1 uteD5GZaPauzUJELrv8lEOx6tlhDtajuhp4H82s24fXE+8mUYqpjnsY2mFjPFV+PoOnqyX 7lK6sqiq54FUkLoRHTIeSK9LEemUbDHXmk7LvQINdwncVEhWad6VAT3S+m2hsTbXquiRls iW9n6AAKaY2S4VAZ+a3kaMaa+aW7edm/HmfqLr/wf1d1H/MZ38GQwvWJIde/9g== Message-ID: <1f832fae-129b-4600-bca5-1f48eed8ecac@ipfire.org> Date: Mon, 6 Jul 2026 12:22:25 +0200 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: Adolf Belka To: Matthias Fischer , development@lists.ipfire.org Cc: Michael Tremer 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> <0645F905-CBFC-4A53-9AD6-D0B86F43197B@ipfire.org> <6001b1cd-b5c7-4878-9d0e-cc8e43ea2346@ipfire.org> <9b768727-3a1c-47d5-b915-c882e7e543d7@ipfire.org> Content-Language: en-GB In-Reply-To: <9b768727-3a1c-47d5-b915-c882e7e543d7@ipfire.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Matthias, On 20/06/2026 13:43, Adolf Belka wrote: > Hallo Matthias, > > Sorry for late reply. I am a bit tied up with other things that are keeping me busy at the moment. > > On 18/06/2026 13:56, Matthias Fischer wrote: >> Hi all, >> >> On 16.06.2026 13:49, Michael Tremer wrote: >>> No worries, I wasn’t particularly quick with my response. >>> >>> What you sent looks good to me. I will reply to those emails once I review them. >> >> No problem, take your time. But since I was warned that building could >> be ok, but starting the firewall (e.g.) could run into errors, I set up >> my - offline - testmachine and couldn't find any (starting) errors. >> >> But: could 'someone' (Adolf(!?) ;-) ), install this build with this perl >> update and test it *online*? I don't know if this makes a really *big* >> difference, but I would feel better... > > Yes, I will have a go at this but it might not be till the week after next. I got some time to be able to have a go at this. I took your update patches and applied them to a latest CU204 build set. That went fine with just a couple of issues due to newer changes in CU204. perl-netsnmpd has been updated so the patch for the PAK-VER update failed to work and there is a new module perl-Encode-Locale. So I manually did the changes for those two modules. The build then worked without any issues. I then installed the iso created from that build. Everything looked fine so I restored a CU202 backup. I then checked all the WUI pages with special focus on all then ones that I am actively using. Everything worked as expected. It all looks to be working fine to me. Congratulations, Matthias, on a successful perl update. I think this should be able to be put into CU204. Regards, Adolf. > > Regards, > > Adolf. > >> >> Best >> Matthias >>>> On 16 Jun 2026, at 12:47, Matthias Fischer wrote: >>>> >>>> On 16.06.2026 13:20, Michael Tremer wrote: >>>>> Hello Matthias, >>>> >>>> Hi Michael, >>>> >>>>> Yes, this is a bug update because there are plenty of modules built after the main package. >>>>> >>>>> 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. >>>> >>>> Ups. Just saw your mail - a few seconds after I pushed the whole thing, >>>> sorry. >>>> >>>> Take a look and decide - its really huge... ;-) >>>> >>>> Best >>>> Matthias >>>>> Best, >>>>> -Michael >>>>> >>>>>> On 14 Jun 2026, at 22:04, Matthias Fischer wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> 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. >>>>>>> ... >>>>>> >>>>>> I did. But I'm not quite sure what to do next and need a hint. >>>>>> >>>>>> 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. >>>>>> >>>>>> Adjusting the rootfile for the new perl version was a bit...extensive, >>>>>> but I think I managed it. Build is running without any errors. >>>>>> >>>>>> 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. >>>>>> >>>>>> 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. >>>>>> >>>>>> Would this be ok? Updating perl leads to about ~70 files that need to be >>>>>> updated too and pushed because of changed rootfiles? >>>>>> >>>>>> Best >>>>>> Matthias >>>>>> >>>>>> >>>>> >>>>> >>>> >>> >> >