user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: "Uwe Kleine-König" <>
To: Eric Wong <>
Cc: Lucas Nussbaum <>,,,
	Debian Perl Group <>
Subject: Re: [PATCH] t/eml.t: ignore newer Email::MIME behavior
Date: Sun, 2 Jan 2022 15:14:26 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20211230191742.M703794@dcvr>

[-- Attachment #1.1: Type: text/plain, Size: 2491 bytes --]

Hello Eric,

On 12/30/21 20:17, Eric Wong wrote:
> Uwe Kleine-König <> wrote:
>> Hello,
>> adding the Debian Perl Group to Cc, maybe they can help here.
>> (for context look at
>> On 12/30/21 10:12, Uwe Kleine-König wrote:
>>> I got a bug report against the public-inbox 1.6.1 package about a
>>> failing test, see below for the whole output. I didn't have time yet to
>>> look into it, so this is just a heads up to make you aware. If someone
>>> has a hint what to do, this would be greatly appreciated. Maybe just
>>> updating to 1.7 will help?
>>> Best regards
>>> Uwe
>>> On 12/21/21 17:34, Lucas Nussbaum wrote:
>>>>> #   Failed test 'filename decoded'
>>>>> #   at t/eml.t line 407.
>>>>> #          got: '=?utf-8?q?vtpm-makefile.patch?='
>>>>> #     expected: 'vtpm-makefile.patch'
>>>>> # Looks like you failed 1 test of 146.
>>>>> t/eml.t ......................
>> I can reproduce this problem with 1.6.1 checked out. I played a bit around
>> (suffering from my weak perl foo) and found that when I downgrade
>> libemail-mime-perl from 1.952-1 (i.e. Debian unstable's version) to 1.949-1
>> (i.e. Debian stable's version), this works.
>> The reproducer is:
>> $ perl -e 'use Email::MIME; print Email::MIME->new("Content-Type:
>> text/x-patch; name=\"=?utf-8?q?vtpm-fakefile.patch?=\"\nContent-Disposition:
>> attachment; filename=\"=?utf-8?q?vtpm-makefile.patch?=\"\n\n")->filename;'
>> which emits "vtpm-makefile.patch" with 1.949-1 (as public-inbox expects),.
>> but =?utf-8?q?vtpm-makefile.patch?= with 1.952-1.
>> So the key question is: Is the test correct and his is a regression in
>> libemail-mime-perl, or is the test wrong and we need to fix the test (and
>> PublicInbox::Eml)?
> I thought I sent a fix to this; but I nuked the root FS on one of
> my workstations on accident :<  Still recovering...

Oh, good luck in restoring your precious data.

Thanks for your patch. I just uploaded public-inbox with this change to 
fix the bug.

I still wonder if this is a regression in Email::MIME, or just a wrong 
expectation. In the first case I'd open a bug against libemail-mime-perl.

Bisecting in yields 
as breaking commit. So this looks like an intended change.

Best regards

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2022-01-02 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-12-30  9:12 ` Bug#1002219: public-inbox: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Uwe Kleine-König
2021-12-30 18:49   ` Uwe Kleine-König
2021-12-30 19:17     ` [PATCH] t/eml.t: ignore newer Email::MIME behavior Eric Wong
2022-01-02 14:14       ` Uwe Kleine-König [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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] t/eml.t: ignore newer Email::MIME behavior' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

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).