Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Package-Stash CPAN distribution.

Report information
The Basics
Id: 67266
Status: resolved
Priority: 0/
Queue: Package-Stash

People
Owner: Nobody in particular
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.28
Fixed in: (no value)



Subject: Bootstrapping how to?
This is what happens on a fresh bleadperl: % /home/src/perl/repoperls/installed-perls/perl/v5.13.11-379-g801eb08/bin/perl Makefile.PL *** Your toolchain doesn't support configure_requires, so Dist::CheckConflicts hasn't been installed yet. You should check for conflicting modules manually using the 'package-stash-conflicts' script that is installed with this distribution once the installation finishes. *** Writing Makefile for Package::Stash Writing MYMETA.yml A 'make' run succeeds after that. But 'make test' fails: % make test [CPANSHELL] make[1]: Entering directory `/home/sand/.cpan/build/Package-Stash-0.28-bAl8P_' PERL_DL_NONLAZY=1 /home/src/perl/repoperls/installed-perls/perl/v5.13.11-379-g801eb08/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/impl-selection/*.t t/00-compile.t .................. 1/3 # Failed test 'package-stash-conflicts script compiles' # at t/00-compile.t line 45. # 2 - Can't locate Dist/CheckConflicts.pm in @INC (@INC contains: /home/sand/.cpan/build/Package-Stash-0.28-bAl8P_/blib/arch /home/sand/.cpan/build/Package-Stash-0.28-bAl8P_/blib/lib /home/sand/.cpan/build/Package-Stash-0.28-bAl8P_/blib/lib /home/sand/.cpan/build/Package-Stash-0.28-bAl8P_/blib/arch /home/src/perl/repoperls/installed-perls/perl/v5.13.11-379-g801eb08/lib/site_perl/5.14.0/x86_64-linux /home/src/perl/repoperls/installed-perls/perl/v5.13.11-379-g801eb08/lib/site_perl/5.14.0 /home/src/perl/repoperls/installed-perls/perl/v5.13.11-379-g801eb08/lib/5.14.0/x86_64-linux /home/src/perl/repoperls/installed-perls/perl/v5.13.11-379-g801eb08/lib/5.14.0 .) at /home/sand/.cpan/build/Package-Stash-0.28-bAl8P_/blib/lib/Package/Stash/Conflicts.pm line 19. # BEGIN failed--compilation aborted at /home/sand/.cpan/build/Package-Stash-0.28-bAl8P_/blib/lib/Package/Stash/Conflicts.pm line 19. # Compilation failed in require at bin/package-stash-conflicts line 8. # BEGIN failed--compilation aborted at bin/package-stash-conflicts line 8. # Looks like you failed 1 test of 3. t/00-compile.t .................. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/3 subtests t/01-basic.t .................... ok t/02-extension.t ................ ok t/03-io.t ....................... ok t/04-get.t ...................... ok t/05-isa.t ...................... ok t/06-addsub.t ................... ok t/07-edge-cases.t ............... ok t/10-synopsis.t ................. ok t/author-20-leaks.t ............. skipped: these tests are for testing by the author t/author-21-leaks-debug.t ....... skipped: these tests are for testing by the author t/impl-selection/01-choice.t .... ok t/impl-selection/02-env.t ....... ok t/impl-selection/03-var.t ....... ok t/impl-selection/10-basic-pp.t .. ok t/impl-selection/11-basic-xs.t .. ok t/release-eol.t ................. skipped: these tests are for release candidate testing t/release-no-tabs.t ............. skipped: these tests are for release candidate testing t/release-pod-coverage.t ........ skipped: these tests are for release candidate testing t/release-pod-syntax.t .......... skipped: these tests are for release candidate testing Test Summary Report ------------------- t/00-compile.t (Wstat: 256 Tests: 3 Failed: 1) Failed test: 3 Non-zero exit status: 1 Files=20, Tests=472, 0 wallclock secs ( 0.10 usr 0.06 sys + 0.69 cusr 0.09 csys = 0.94 CPU) Result: FAIL Failed 1/20 test programs. 1/472 subtests failed. make[1]: *** [test_dynamic] Error 255 There may be other ways to resolve the bootstrapping. I suspect that adding Dist::CheckConflicts to PREREQ_PM would be called for. But I may be wrong. What's your suggestion?
Fixed in 0.29. (There's no reason to be testing the conflicts stuff at all, as they are all generated files.) I fixed this earlier, but messed up the most recent release.