Skip to content

Preserve CPAN fixes during perl5 sync - #947

Merged
fglock merged 1 commit into
masterfrom
fix/cpan-sync-case-collision-20260813
Aug 13, 2026
Merged

Preserve CPAN fixes during perl5 sync#947
fglock merged 1 commit into
masterfrom
fix/cpan-sync-case-collision-20260813

Conversation

@fglock

@fglock fglock commented Aug 13, 2026

Copy link
Copy Markdown
Owner

Summary

  • refresh the CPAN-adjacent I18N and Pod sources produced by dev/import-perl5/sync.pl
  • preserve PerlOnJava's CPAN dependency script-path and bundled jar: version parsing behavior in reproducible import patches
  • remove the byte-identical dev/modules/Memoize.md duplicate, keeping lowercase dev/modules/memoize.md as the canonical path

Review findings addressed

The raw sync had overwritten two recent PerlOnJava-specific CPAN fixes. This PR restores those behaviors and regenerates the import patches from the upstream snapshot, so focused sync replays remain byte-for-byte idempotent.

Validation

  • perl -c src/main/perl/lib/CPAN.pm
  • perl -c src/main/perl/lib/CPAN/Module.pm
  • focused sync.pl --only replay for both CPAN files, with identical hashes before and after
  • verified no case-insensitive duplicate remains in the tracked file list
  • make — BUILD SUCCESSFUL (4m35s)

Generated with Codex

Refresh the upstream I18N and Pod sources while retaining PerlOnJava's CPAN
environment and bundled-version handling in reproducible import patches.

Remove the byte-identical uppercase Memoize report duplicate so clones on
case-insensitive filesystems no longer encounter a path collision.

Generated with [Codex](https://openai.com/codex)

Co-Authored-By: Codex <223018245+openai-codex[bot]@users.noreply.github.com>
@fglock
fglock merged commit 13c8504 into master Aug 13, 2026
2 checks passed
@fglock
fglock deleted the fix/cpan-sync-case-collision-20260813 branch August 13, 2026 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant