From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 2/2] doc: lei: add manpages for remaining commands
Date: Sat, 16 Oct 2021 17:03:52 +0000 [thread overview]
Message-ID: <20211016170352.GA22949@dcvr> (raw)
In-Reply-To: <87lf2t0zq2.fsf@kyleam.com>
Kyle Meyer <kyle@kyleam.com> wrote:
> Thanks, sorry about the mix up.
No worries, will push a regen.
> [*] I did run `make check' before sending, and it looks like that also
> checks MANIFEST _after_ running the test suite. That didn't help me
> catch the MANIFEST sorting issue in this case because the test suite
> is failing on my end.
>
> I believe these failures are recent and was planning on looking into
> them today, either sending a patch or just reporting, depending on
> whether I could figure out a fix. Anyway, here they are:
>
> t/psgi_multipart_not.t .......
> ok 1 - use HTTP::Request::Common;
> ok 2 - use Plack::Test;
> ok 3 - use PublicInbox::WWW;
> not ok 4 - /v2test/?q=%22ain't what it used to be%22&x=t
> not ok 5 - /v2test/?q=%22ain't what it used to be%22&x=t warns
> Failed 2/5 subtests
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.
Which versions of Encode and Perl are you using?
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.
next prev parent reply other threads:[~2021-10-16 17:03 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 [this message]
2021-10-16 17:21 ` Kyle Meyer
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: http://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=20211016170352.GA22949@dcvr \
--to=e@80x24.org \
--cc=kyle@kyleam.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).