p5.12-module-build @0.400.0 fails to upgrade because modules provided by perl5.12 are too old

[geekosaur]

10.6.8 with Xcode 3.2.6

Full log attached; relevant snippet appears to be

DEBUG: Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_perl_p5-module-build/p5.12-module-build/work/Module-Build-0.40" && /opt/local/bin/perl5.12 Build.PL installdirs=vendor 
*** BOOTSTRAPPING version ***
Checking prerequisites...
  requires:
    !  CPAN::Meta is not installed
  build_requires:
    !  Parse::CPAN::Meta (1.40) is installed, but we need version >= 1.4401

ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the versions
of the modules indicated above before proceeding with this installation

Could not create MYMETA files
Copied META.yml to MYMETA.yml for bootstrapping

These additional prerequisites must be installed:
  requires:
    ! version (we need version 0.87)

and, while the former two may not be necessary for an initial build or even an update (as indicated by the bootstrap YAML), the latter prerequisite is confirmed later:

version version 0.87 required--this is only version 0.82 at /opt/local/lib/perl5/vendor_perl/5.12.3/Module/Metadata.pm line 20.

which, as expected for a basic pragma, is provided by perl5.12:

pyanfar:10082 Z$ port provides /opt/local/lib/perl5/5.12.4/version.pm
/opt/local/lib/perl5/5.12.4/version.pm is provided by: perl5.12

[ryandesign (Ryan Carsten Schmidt)]

I of course tested that I was able to install p5.12-module-build @0.400.0_0 before I updated the port to that version.

I do happen to also have p5.12-parse-cpan-meta @1.440.400_0 and p5.12-version @0.970.0_0 installed.

p5.12-version is already an indirect dependency so you should also already have had a sufficient version of that installed.

But perhaps we need to add a p5.12-parse-cpan-meta dependency.

[geekosaur]

*sigh* I appear to have p5.12-version @0.970.0_0 installed already; wonder if it's from a package (hence installed a non-threaded one against a +threads perl5.12); although I thought I forced all perl modules to be reinstalled after I switched to doing only source builds, that being the only way I am aware of to stop packages from installing useless perl modules against a non-default perl variant. If this threads nonsense isn't going to be fixed, can it at least be warned about somehow?

[geekosaur]

And in fact forcing p5.12-version rebuild fixed it, so it apparently evaded my attempt to rebuild all dependents after switching off source builds.

[cmconnelly (Claire Connelly)]

Cc Me!

[jmroot (Joshua Root)]

#34723