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 4gdm3W2vTXz3020 for ; Sun, 14 Jun 2026 21:04:55 +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 4gdm3S0PlWz2xYX for ; Sun, 14 Jun 2026 21:04:52 +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 4gdm3R1TLHz1GT; Sun, 14 Jun 2026 21:04:51 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1781471091; 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=stfRMA3xISvacjVt2xb8PeFTgcNZbryIMulQcsHLH9w=; b=MKuujv32zFmOpsvVUiTwbkF+/ORbm2w3exzUrzwoRGCd3j0qDgGcKSzgS24PpgilR5uOhJ 6DpboAkjkqnZOqBw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1781471091; 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=stfRMA3xISvacjVt2xb8PeFTgcNZbryIMulQcsHLH9w=; b=v+ErICFEFXFj9dPhtj8cOi7kHFuiKouKtfOpqgdBNz+Bgg7dU//ATlyyJL36koKmvof90w v81Qe4ASSxzjfrb54kStbBKKSYHm6TVmeTrnUO8JHLdRJ+X3LAhcxI/ZFoKi4tSqIxukZt hLTA3UKZEWqKJCJZi211qkuuBtfGFo2YdyLD17RccTioGsoGygdxpFTjookDkUQCyOSF/D UkNhgNbnxB8+cDtLnHXWEkBdCx/ESPMWz+PPUSAmmv9RuUDBWLbTsaniIdABYCCW2MAwc2 Fl0TexJVGNV/A7mFqe4L9DCVyKxwS4HqRqa6UFUouASxClRHwTV0azqXqXpP8g== Message-ID: <60287726-6a52-4c3d-af92-917f62d52759@ipfire.org> Date: Sun, 14 Jun 2026 23:04:42 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Updating perl 5.36.0 => 5.42.2 - some questions (was: Re: perl-Net-DNS: Not updated) Content-Language: en-US To: development@lists.ipfire.org References: <2dd775e8-e645-43f2-8219-e79198e666e3@ipfire.org> <1D3FCBD1-16E5-450B-88A0-B27B1F337EDB@ipfire.org> <56142892-a026-4f3f-b446-f05153f87490@ipfire.org> Cc: "IPFire: Belka, Adolf" From: Matthias Fischer In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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