From: Michael Tremer <michael.tremer@ipfire.org>
To: Matthias Fischer <matthias.fischer@ipfire.org>
Cc: development@lists.ipfire.org, "IPFire: Belka,
Adolf" <adolf.belka@ipfire.org>
Subject: Re: Updating perl 5.36.0 => 5.42.2 - some questions
Date: Tue, 16 Jun 2026 12:49:10 +0100 [thread overview]
Message-ID: <0645F905-CBFC-4A53-9AD6-D0B86F43197B@ipfire.org> (raw)
In-Reply-To: <5d90be69-e026-477e-96c1-056235b202c2@ipfire.org>
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.
> On 16 Jun 2026, at 12:47, Matthias Fischer <matthias.fischer@ipfire.org> 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 <matthias.fischer@ipfire.org> 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
>>>
>>>
>>
>>
>
next prev parent reply other threads:[~2026-06-16 11:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 10:39 perl-Net-DNS: Not updated Matthias Fischer
2026-06-12 10:40 ` Michael Tremer
2026-06-12 10:46 ` Matthias Fischer
2026-06-12 10:48 ` Adolf Belka
2026-06-12 11:03 ` Matthias Fischer
2026-06-12 11:19 ` Adolf Belka
2026-06-14 21:04 ` Updating perl 5.36.0 => 5.42.2 - some questions (was: Re: perl-Net-DNS: Not updated) Matthias Fischer
2026-06-16 11:20 ` Michael Tremer
2026-06-16 11:47 ` Updating perl 5.36.0 => 5.42.2 - some questions Matthias Fischer
2026-06-16 11:49 ` Michael Tremer [this message]
2026-06-16 12:12 ` Matthias Fischer
2026-06-18 11:56 ` Matthias Fischer
2026-06-20 11:43 ` Adolf Belka
2026-06-20 11:59 ` Matthias Fischer
2026-07-06 10:22 ` Adolf Belka
2026-07-06 10:27 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0645F905-CBFC-4A53-9AD6-D0B86F43197B@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=matthias.fischer@ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox