Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 2219564 - perl-Mail-Box-3.009-8.fc39 FTBFS: t/501parser-head.t fails with perl-Mail-Message-3.013
Summary: perl-Mail-Box-3.009-8.fc39 FTBFS: t/501parser-head.t fails with perl-Mail-Mes...
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Mail-Box
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
Depends On: 2224548
Blocks: F39FTBFS
TreeView+ depends on / blocked
Reported: 2023-07-04 10:50 UTC by Petr Pisar
Modified: 2023-07-24 07:21 UTC (History)
4 users (show)

Fixed In Version: perl-Mail-Box-3.010-1.fc39
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-07-24 07:21:57 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
CPAN 148902 0 None None None 2023-07-04 10:53:34 UTC

Description Petr Pisar 2023-07-04 10:50:15 UTC
perl-Mail-Box-3.009-8.fc39 fails to build from sources in Fedora 39 because a tests fails:

$ perl -Ilib t/501parser-head.t 
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
not ok 14
#   Failed test at t/501parser-head.t line 47.
#          got: '(from majordomo@localhost)     by (8.9.3/8.9.3) id PAA29389       for magick-outgoing'
#     expected: '(from majordomo@localhost) by (8.9.3/8.9.3) id PAA29389 for magick-outgoing'
ok 15
ok 16 - X-foo ok
# Looks like you failed 1 test of 16.

This is triggered by upgrading perl-Mail-Message from 0:3.012-5.fc39 to 0:3.013-1.fc39:

version 3.013: Sat 24 Jun 17:25:11 CEST 2023

    - In header lines, leave the actual white-space related to FWS
      intact.  You may want to add s/\t/ / before you print a header.
      GitHub#7 [Jacob Balazer]

Note You need to log in before you can comment on or make changes to this bug.