From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 4920d477a2cc9524d0a293d658c14981cc786672
Date: Sat, 08 Aug 2026 16:45:11 +0000 (UTC) [thread overview]
Message-ID: <4hHRhR3cwDz2xg0@people01.haj.ipfire.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via 4920d477a2cc9524d0a293d658c14981cc786672 (commit)
from 99d43bf7b21528911d5f5825415fc3a16c86d098 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 4920d477a2cc9524d0a293d658c14981cc786672
Author: Adolf Belka <adolf.belka@ipfire.org>
Date: Thu Aug 6 11:26:45 2026 +0200
perl: Update rootfile
- The rootfile had Getopt/Long/Parser.pm commented out. A forum user tried the Testing
branch already and found a message in the logs that was looking for that perl file
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/perl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/common/perl b/config/rootfiles/common/perl
index 61a0a2ddc..1e617269e 100644
--- a/config/rootfiles/common/perl
+++ b/config/rootfiles/common/perl
@@ -264,7 +264,7 @@ usr/lib/perl5/5.42.2/FindBin.pm
#usr/lib/perl5/5.42.2/Getopt
#usr/lib/perl5/5.42.2/Getopt/Long
usr/lib/perl5/5.42.2/Getopt/Long.pm
-#usr/lib/perl5/5.42.2/Getopt/Long/Parser.pm
+usr/lib/perl5/5.42.2/Getopt/Long/Parser.pm
usr/lib/perl5/5.42.2/Getopt/Std.pm
#usr/lib/perl5/5.42.2/HTTP
usr/lib/perl5/5.42.2/HTTP/Tiny.pm
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-08-08 16:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4hHRhR3cwDz2xg0@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.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