Skip Menu |

This queue is for tickets about the Data-Serializer CPAN distribution.

Report information
The Basics
Id: 18923
Status: rejected
Worked: 10 min
Priority: 0/
Queue: Data-Serializer

People
Owner: neil [...] neely.cx
Requestors: jrs_1 [...] mac.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.36
Fixed in: (no value)



Subject: make test fails RHEL3
When trying to install v 0.36 on a RHEL3 machine I am unable to get 'make test' to complete successfully. The exact same package installed correctly on a OS-X 10.4.6 machine only moments before. The following external packages were installed in preparation for Data::Serializer (all of which installed successfully): ExtUtils-MakeMaker-6.30 Digest-SHA-5.34 Crypt-Blowfish-2.10 Crypt-CBC-2.12 (was already installed) perl is standard RHEL3 perl (5.8.0 back-patched): % perl -v This is perl, v5.8.0 built for i386-linux-thread-multi %uname -a Linux test1 2.4.21-40.EL #1 Thu Feb 2 22:32:00 EST 2006 i686 i686 i386 GNU/Linux make test output: PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/01-01-Data-Dumper..........ok t/01-02-Data-Denter..........skipped all skipped: Data::Denter not installed t/01-03-Storable.............ok t/01-04-FreezeThaw...........skipped all skipped: FreezeThaw not installed t/01-05-Config-General.......skipped all skipped: Config::General not installed t/01-06-YAML.................skipped all skipped: YAML not installed t/01-07-XML-Dumper...........ok t/01-08-PHP-Serialization....skipped all skipped: PHP::Serialization not installed t/01-09-XML-Simple...........ok t/01-10-Data-Taxi............skipped all skipped: Data::Taxi not installed t/01-11-YAML-Syck............skipped all skipped: YAML::Syck not installed t/01-12-JSON.................skipped all skipped: JSON not installed t/01-13-JSON-Syck............skipped all skipped: JSON::Syck not installed t/02-Raw.....................ok t/03-Non-Portable............ok t/04-Compression.............ok t/05-Encryption..............Warning: Use of "require" without parens is ambiguous at (eval 20) line 1. syntax error at (eval 20) line 1, near "require Digest::SHA-" t/05-Encryption..............dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 1-49 Failed 49/49 tests, 0.00% okay t/06-B64-Encoding............ok t/07-01-MD5-Digest...........ok t/07-02-SHA1-Digest..........Warning: Use of "require" without parens is ambiguous at (eval 21) line 1. syntax error at (eval 21) line 1, near "require Digest::SHA-" t/07-02-SHA1-Digest..........dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 1-49 Failed 49/49 tests, 0.00% okay t/07-03-SHA-256-Digest.......Warning: Use of "require" without parens is ambiguous at (eval 21) line 1. syntax error at (eval 21) line 1, near "require Digest::SHA-" t/07-03-SHA-256-Digest.......dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 1-49 Failed 49/49 tests, 0.00% okay t/08-Store-Retrieve..........ok t/09-Feature-Combos..........Warning: Use of "require" without parens is ambiguous at (eval 22) line 1. syntax error at (eval 22) line 1, near "require Digest::SHA-" t/09-Feature-Combos..........dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 1-343 Failed 343/343 tests, 0.00% okay Failed Test Stat Wstat Total Fail Failed List of Failed ------------------------------------------------------------------------------- t/05-Encryption.t 255 65280 49 49 100.00% 1-49 t/07-02-SHA1-Digest.t 255 65280 49 49 100.00% 1-49 t/07-03-SHA-256-Digest.t 255 65280 49 49 100.00% 1-49 t/09-Feature-Combos.t 255 65280 343 343 100.00% 1-343 9 tests skipped. Failed 4/23 test scripts, 82.61% okay. 490/945 subtests failed, 48.15% okay. make: *** [test_dynamic] Error 2
The particular error is puzzling: "require Digest::SHA-" Nothing in the code of the test suite should try to run that, depending on the test it will call either: require Digest::SHA1; or require Digest::SHA; But it doesn't ever try to require "Digest::SHA-". Can anyone see if this problem still exists on a current RHEL3 port? Only guess I have at this point is that it was a bug introduced in the porting process, as none of the CPAN Testers reported this bug. Any additional information on this bug would be appreciated.