Bug 1939424 - perl-Crypt-PWSafe3-1.22-17.fc35 FTBFS: Failed test 'open a pwsafe3 database ('blocksize' is not a recognized argument at /usr/share/perl5/vendor_perl/Crypt/CBC.pm line 309.
Summary: perl-Crypt-PWSafe3-1.22-17.fc35 FTBFS: Failed test 'open a pwsafe3 database (...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Crypt-PWSafe3
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Charles R. Anderson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F35FTBFS 1964646 F36FTBFS F37FTBFS
TreeView+ depends on / blocked
 
Reported: 2021-03-16 11:51 UTC by Petr Pisar
Modified: 2022-03-26 15:06 UTC (History)
4 users (show)

Fixed In Version: perl-Crypt-PWSafe3-1.23~20220227git002b0f0-1.fc37 perl-Crypt-PWSafe3-1.23~20220227git002b0f0-1.fc34 perl-Crypt-PWSafe3-1.23~20220227git002b0f0-1.fc35 perl-Crypt-PWSafe3-1.23~20220227git002b0f0-1.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-02 03:54:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github TLINDEN Crypt--PWSafe3 issues 12 0 None open t/run.t started to fail 2021-05-11 07:22:11 UTC

Description Petr Pisar 2021-03-16 11:51:21 UTC
perl-Crypt-PWSafe3-1.22-17.fc35 fails to build in Fedora 35 because a test fails:

+ make test
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
#   Failed test 'open a pwsafe3 database ('blocksize' is not a recognized argument at /usr/share/perl5/vendor_perl/Crypt/CBC.pm line 309.
#  at /builddir/build/BUILD/Crypt-PWSafe3-1.22/blib/lib/Crypt/PWSafe3.pm line 259.
# )'
#   at t/run.t line 71.
#   Failed test 'create a new pwsafe3 database ('blocksize' is not a recognized argument at /usr/share/perl5/vendor_perl/Crypt/CBC.pm line 309.
#  at /builddir/build/BUILD/Crypt-PWSafe3-1.22/blib/lib/Crypt/PWSafe3.pm line 197.
# )'
#   at t/run.t line 86.
#   Failed test 'read created new pwsafe3 database (PWSafe3 file /tmp/.myvaultEHk0P2sE does not exist or is not readable at t/run.t line 33.
# )'
#   at t/run.t line 95.
#   Failed test 'Write record to a new pwsafe3 database'
#   at t/run.t line 96.
#     Structures begin differing at:
#          $got->{user} = 'u3'
#     $expected->{user} = Does not exist
#   Failed test 'read a pwsafe3 database and change a record, traditional method ('blocksize' is not a recognized argument at /usr/share/perl5/vendor_perl/Crypt/CBC.pm line 309.
#  at /builddir/build/BUILD/Crypt-PWSafe3-1.22/blib/lib/Crypt/PWSafe3.pm line 259.
# )'
#   at t/run.t line 121.
#   Failed test 'Change a record an check if changes persist after saving, traditional method'
#   at t/run.t line 122.
#     Structures begin differing at:
#          $got->{user} = 'u3'
#     $expected->{user} = Does not exist
# 3 done
#   Failed test 'read a pwsafe3 database and change a record, new method ('blocksize' is not a recognized argument at /usr/share/perl5/vendor_perl/Crypt/CBC.pm line 309.
#  at /builddir/build/BUILD/Crypt-PWSafe3-1.22/blib/lib/Crypt/PWSafe3.pm line 259.
# )'
#   at t/run.t line 143.
Can't call method "notes" on an undefined value at t/run.t line 144.
# Looks like your test exited with 255 just after 9.
t/run.t .. 
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 11/13 subtests 

A difference between passing and failing build root is at <https://koschei.fedoraproject.org/build/9825735>. An upgrade of perl-Crypt-CBC from 2.33-30.fc34 to 3.01-1.fc34 looks suspicious.

Comment 1 Charles R. Anderson 2021-06-11 12:25:53 UTC
FTBFS due to the change in perl-Crypt-CBC from version 2.33 (fc33) to 3.01 (fc34) or 3.04 (fc35).

Comment 2 Ben Cotton 2021-08-10 12:54:39 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 3 Paul Howarth 2022-02-28 08:43:37 UTC
This is now fixed in upstream git. Author wants to do some more testing with the android app before issuing a new release but hopefully it won't be long now.

Comment 4 Fedora Update System 2022-03-02 03:53:41 UTC
FEDORA-2022-e0421d0f66 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e0421d0f66

Comment 5 Fedora Update System 2022-03-02 03:54:13 UTC
FEDORA-2022-e0421d0f66 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2022-03-02 04:33:01 UTC
FEDORA-2022-e541fc8d0d has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e541fc8d0d

Comment 7 Fedora Update System 2022-03-02 04:33:54 UTC
FEDORA-2022-9af00d105b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9af00d105b

Comment 8 Fedora Update System 2022-03-02 04:34:40 UTC
FEDORA-2022-2fa03c4f5d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-2fa03c4f5d

Comment 9 Fedora Update System 2022-03-02 15:56:33 UTC
FEDORA-2022-2fa03c4f5d has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-2fa03c4f5d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-2fa03c4f5d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2022-03-02 16:15:49 UTC
FEDORA-2022-9af00d105b has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-9af00d105b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9af00d105b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2022-03-02 19:43:17 UTC
FEDORA-2022-e541fc8d0d has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-e541fc8d0d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e541fc8d0d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2022-03-09 19:15:45 UTC
FEDORA-2022-2fa03c4f5d has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2022-03-09 19:43:15 UTC
FEDORA-2022-9af00d105b has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2022-03-26 15:06:34 UTC
FEDORA-2022-e541fc8d0d has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


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