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 4gjCK32hWkz32YF for ; Sat, 20 Jun 2026 11:43:35 +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 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 4gjCJz3qL5z2xHP for ; Sat, 20 Jun 2026 11:43:31 +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 4gjCJy2KQlz2v; Sat, 20 Jun 2026 11:43:30 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1781955810; 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=1SA+xFCaiKOGAcoFSdiCFEGKaD7Wa8S5XBVvkrd42O4=; b=hOFDE7L/5jggsJ13I7FilhU/LCT8v4qtOWQdsmwMQQlXyKZKLfI/VcIP5Cp7fnluPaY8tK DThEfJL3QLUcuQAg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1781955810; 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=1SA+xFCaiKOGAcoFSdiCFEGKaD7Wa8S5XBVvkrd42O4=; b=SaI6mTt/Mi+0Im+EBNpjdpR4W8cWVY/9uTCbO2AFc7OSVFQAwBGaWX8KzetENcUUNgyvlz BtRvN+zjI1OskemUtBMeweVEGcJBZej5XcWPtjvjtBOh4EOv5446iFY+sw3R7+H8bKAllT hstRf+3E6Rat9XHsXL3JkypYWo54AInGufxLdCDVxil1Vitq9IYne4cEmHYK9r9CWRvixz 6U9cx9eIthG6Svtx0U3m3EJISZjRDzVCNI7DHhV8/aQ8OryMzging28lQtsuH2pxS3fn36 +jpUuMud4nz4ADMeIj4KNEw5y0BQxLQR1c0WcB9y1Ok3+HT94T6yMspEnSIaRg== Message-ID: <9b768727-3a1c-47d5-b915-c882e7e543d7@ipfire.org> Date: Sat, 20 Jun 2026 13:43: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 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> From: Adolf Belka Content-Language: en-GB In-Reply-To: <6001b1cd-b5c7-4878-9d0e-cc8e43ea2346@ipfire.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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. 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 >>>>> >>>>> >>>> >>>> >>> >> > -- Sent from my laptop