From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 2/2] doc: lei: add manpages for remaining commands
Date: Sat, 16 Oct 2021 13:21:35 -0400 [thread overview]
Message-ID: <87fst028dc.fsf@kyleam.com> (raw)
In-Reply-To: <20211016170352.GA22949@dcvr>
Eric Wong writes:
> The failure is probably caused by
> 00d5dff2cce9d2c9 (eml: avoid Encode 2.87..3.12 leak, 2021-10-13)
> but I can't reproduce it across CentOS 7.x, FreeBSD 11.x, nor
> Debian 10 & 11.
Hmm, yeah, as mentioned in my other reply, I'm now not having any luck
triggering this either.
> Which versions of Encode and Perl are you using?
Perl v5.32.1 from Debian 11 and...
> At least in Debian, libencode-perl is available as a separate package
> but it's also part of libperl5.xx (possibly w/ a different version);
> only the latter is required for us, but two packages offering
> the same thing gets confusing :/
>
> I use: perl -MEncode -E 'say $Encode::VERSION'
> to determine which gets loaded.
... it looks like I'm using the on that's ships with libperl5:
$ perl -MEncode -E 'say $Encode::VERSION'
3.06
$ apt-cache policy libencode-perl
libencode-perl:
Installed: (none)
Candidate: 3.08-1+deb11u1
Version table:
3.08-1+deb11u1 500
500 http://ftp.us.debian.org/debian bullseye/main amd64 Packages
500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
prev parent reply other threads:[~2021-10-16 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 5:39 [PATCH 0/2] doc: lei manpages for remaining commands Kyle Meyer
2021-10-16 5:39 ` [PATCH 1/2] doc: lei: restore alphabetical order to some listings Kyle Meyer
2021-10-16 5:39 ` [PATCH 2/2] doc: lei: add manpages for remaining commands Kyle Meyer
2021-10-16 7:07 ` Eric Wong
2021-10-16 15:13 ` Kyle Meyer
2021-10-16 16:58 ` Kyle Meyer
2021-10-16 17:03 ` Eric Wong
2021-10-16 17:21 ` Kyle Meyer [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fst028dc.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).