From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Missing perl module Locale.pm
Date: Fri, 17 Jun 2022 17:52:39 +0200 [thread overview]
Message-ID: <7fa62b2f-60b9-cfbc-aef3-e86f2a5cc33f@ipfire.org> (raw)
In-Reply-To: <t7irht$m4v$1@tuscan3.grantura.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]
Hi All,
On 05/06/2022 20:10, Rob Brewer wrote:
> Hi All,
>
> Core-upgrade-165 introduced a new version of
>
> /usr/lib/perl5/site_perl/5.32.1/LWP/UserAgent.pm
>
> This version UserAgent.pm has a dependency on Encode/Locale.pm which isn't
> included in Core Update 167.
>
> Can this module be included in the next upgrade?
>
I am putting together a patch for Encode::Locale. While looking at this I found a list of dependencies for perl-libwww which provides LWP::UserAgent, and only a few of those dependencies are installed on IPFire. It is likely that many are not needed for the use that IPFire makes of perl-libwww but are we just left with waiting to see if things break to figure out that a dependency is now needed for IPFire. I looked in the changes list for perl-libwww and there is no mention of Encode::Locale being needed for LWP::UserAgent.
Here is the list of dependencies and those with an X at the start of the line are not installed on IPFire.
X Digest::MD5
X Encode
X Encode::Locale
X File::Copy
X File::Listing
X File::Temp
X Getopt::Long
X HTML::Entities
X HTML::HeadParser
X HTTP::Cookies
HTTP::Date
X HTTP::Negotiate
X HTTP::Request
X HTTP::Request::Common
X HTTP::Response
X HTTP::Status
X IO::Select
X IO::Socket
X LWP::MediaTypes
MIME::Base64
X Net::FTP
Net::HTTP
X Scalar::Util
Try::Tiny
URI
URI::Escape - included in URI
X WWW::RobotRules
I will just go ahead and only do a patch for Encode::Locale at this point in time.
Regards,
Adolf.
> Regards
>
> Rob
>
next prev parent reply other threads:[~2022-06-17 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 18:10 Rob Brewer
2022-06-17 15:52 ` Adolf Belka [this message]
2022-06-17 21:31 ` Rob Brewer
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=7fa62b2f-60b9-cfbc-aef3-e86f2a5cc33f@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@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