Pinning non-lead modules with MetaCPAN resolver can fail comparison

[thibaultduponchelle]

Hi @miyagawa 👋🏼

When using MetaCPAN resolver and pinning a module version which is not the "lead module" of the distribution, comparison to know if it satisfies can fail.

$ cpanm --metacpan Pod::Simple::[email protected] --force
Found Pod::Simple::HTMLLegacy 3.45 which doesn't satisfy == 5.01

$ cpanm Pod::Simple::[email protected] --force
...
1 distribution installed

Pod::Simple::HTMLLegacy is not the lead package.

But the distribution Pod::Simple version 3.45 contains well the package Pod::Simple::HTMLLegacy version 5.01 - fastapi

{
   "date" : "2023-05-15T23:28:35",
   "download_url" : "https://cpan.metacpan.org/authors/id/K/KH/KHW/Pod-Simple-3.45.tar.gz",
   "version" : "3.45",
   "release" : "Pod-Simple-3.45",
   "checksum_sha256" : "8483bb95cd3e4307d66def092a3779f843af772482bfdc024e3e00d0c4db0cfa",
   "status" : "latest",
   "checksum_md5" : "18b2176f025f8b2213d9c31946f75cb8"
}

See also MetaCPAN Pod-Simple-3.45

[miyagawa]

This is likely an issue with metacpan API not returning the version of the specified package, and cpanm is assuming the distribution version to be the same.