public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Cc: "IPFire: Belka, Adolf" <adolf.belka@ipfire.org>,
	"IPFire: Tremer, Michael" <michael.tremer@ipfire.org>
Subject: Re: Updating perl 5.36.0 => 5.42.2 - some questions
Date: Sat, 20 Jun 2026 13:59:31 +0200	[thread overview]
Message-ID: <9aacfcb3-28bd-4e9c-81be-87d5df2db2ca@ipfire.org> (raw)
In-Reply-To: <9b768727-3a1c-47d5-b915-c882e7e543d7@ipfire.org>

On 20.06.2026 13:43, Adolf Belka wrote:
> Hallo Matthias,

Hi Adolf,

> 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.
> ...
No problem, take your time...its too warm for anything anyway... ;-)

In the meantime I did a few tests with my - offline - testmachine, which
included restoring my firewall rules from Core 202 on a fresh built Core
204. Installation showed no errors and no seen problems on console or in
the logs. Only green [OK]s... ;-)

E.g., running 'rules.pl' in '/usr/lib/firewall' produced no errors.

Best
Matthias



      reply	other threads:[~2026-06-20 11:59 UTC|newest]

Thread overview: 14+ 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
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 [this message]

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=9aacfcb3-28bd-4e9c-81be-87d5df2db2ca@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=michael.tremer@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