Dist::Zilla release archive disappears before release plugins consume it
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 58/100
Research direction
Start by running prove -v t/plugins/testrelease.t t/plugins/uploadtocpan.t t/tester.t under PerlOnJava and compare the archive lifecycle with standard Perl. Trace the release entry point and the consumers named in those tests, especially the tester's source archive path. Done means the archive remains available through TestRelease and UploadToCPAN, and all three focused tests pass.
Written by the indexing model from the issue text.
Description
Summary
PerlOnJava loses a Dist::Zilla release archive before release plugins can consume it. The same missing archive causes three otherwise independent upstream tests to fail:
t/plugins/testrelease.tcannot extractDZT-Sample-0.001.tar.gzduringTestRelease.t/plugins/uploadtocpan.tnever reportsUploading ... DZT-Sample, because its fake uploader sees that the archive path is not a file.t/tester.tdies before producing a TAP plan whenArchive::Tar->newis given the absent archive.
The error from TestRelease is Could not open ... DZT-Sample-0.001.tar.gz for reading: No such file or directory.
Oracle and impact
CPAN random run 20260924-115230-59978 tested Dist::Zilla 6.039. The unmodified upstream suite passes under isolated standard Perl 5.42.2: 57 files and 504 tests, Result: PASS.
Under the PerlOnJava JVM backend, the acceptance run fails 38 of 531 subtests across 5 files. This archive-lifecycle cluster accounts for the failures in the three files above. Dist::Zilla is pure Perl, so native/XS support is not involved.
Focused reproducer
With Dist::Zilla's normal test prerequisites installed, run the upstream focused tests without modification:
prove -v t/plugins/testrelease.t t/plugins/uploadtocpan.t t/tester.t
Standard Perl passes all three. PerlOnJava fails them after release because the archive expected at the tester's source path is gone.
The essence of the upstream t/tester.t reproducer is:
use Test::DZil;
use Archive::Tar;
my $tzil = Builder->from_config(
{ dist_root => 'corpus/dist/DZT' },
{ add_files => {
'source/zero' => '',
'source/dist.ini' => simple_ini({ name => 'DZT' }, 'GatherDir', 'MakeMaker', 'FakeRelease'),
} },
);
$tzil->release;
my $archive = $tzil->built_in->parent->child('source')->child($tzil->archive_filename);
die "archive missing: $archive\n" unless -f $archive;
Archive::Tar->new("$archive");
Expected behavior
The archive produced by release must remain present until the TestRelease and UploadToCPAN consumers have processed it, matching standard Perl and Dist::Zilla's upstream lifecycle.
Duplicate search
No existing issue matched Dist::Zilla archive handling, DZT-Sample, TestRelease, or UploadToCPAN at filing time. Issue #1508 concerns the already-fixed TrialVersionComment plugin and is unrelated.
- Dominant language
- Perl
- Stars
- 64
- Forks
- 6
- Avg merge
- 5h
- Merged PRs (30d)
- 161
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fglock/PerlOnJava
-
area:cpan-port area:unicode bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
fglock/PerlOnJava#1341 ·
Maintainers usually reply within 2 days
-
area:backend area:cpan-port bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
fglock/PerlOnJava#1548 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 5/5 Over a week Newbie friendliness 35/100
fglock/PerlOnJava#1541 ·
Maintainers usually reply within 2 days
-
area:backend area:cpan-port area:parser area:runtime bug
Difficulty 3/5 1-2 days Newbie friendliness 78/100
fglock/PerlOnJava#1528 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
fglock/PerlOnJava#1524 ·
Maintainers usually reply within 2 days
All issues in fglock/PerlOnJava
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
openfoodfacts/openfoodfacts-server#14724 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rubocop/ruby-style-guide#982 ·
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100