From: Michael Tremer <michael.tremer@ipfire.org>
To: Matthias Fischer <matthias.fischer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: perl-Net-DNS: Not updated
Date: Fri, 12 Jun 2026 11:40:37 +0100 [thread overview]
Message-ID: <1D3FCBD1-16E5-450B-88A0-B27B1F337EDB@ipfire.org> (raw)
In-Reply-To: <2dd775e8-e645-43f2-8219-e79198e666e3@ipfire.org>
Hello Matthias,
No, no specific reason as far as I am concerned. Maybe Adolf knows more.
If he doesn’t object either, feel free to send a patch to update it.
Best,
-Michael
> On 12 Jun 2026, at 11:39, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>
> Hi all,
>
> since it just came my way:
>
> Is there a specific reason why “perl-Net-DNS” hasn't been updated in
> five years? The ‘next’ branch is at v1.30, but the current version is
> v1.55. One of my Devels is running...
>
> Best
> Matthias
>
>
next prev parent reply other threads:[~2026-06-12 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 10:39 Matthias Fischer
2026-06-12 10:40 ` Michael Tremer [this message]
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
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=1D3FCBD1-16E5-450B-88A0-B27B1F337EDB@ipfire.org \
--to=michael.tremer@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