Hi,
I'm looking into broken URLs of Fedora packages of (inter
alia) CPAN modules, in the following picking https://src.fedoraproject.org/rpms/perl-Config-IniHash as a
random example.
This Fedora package refers to
https://metacpan.org/release/Config-IniHash which redirects
to https://metacpan.org/dist/Config-IniHash which is 404.
The source URL however, https://cpan.metacpan.org/authors/id/J/JE/JENDA/Config-IniHash-3.01.01.tar.gz,
works nicely, as does some metadata file at https://www.cpan.org/modules/by-authors/id/J/JE/JENDA/Config-IniHash-3.01.01.meta.
Does the module author have to click some button to trigger the
inclusion in the database?
Are all modules available at cpan.org supposed to be listed at
metacpan.org?
Tim Landscheidt <tim@tim-landscheidt.de> writes:*SKIP* [ 14 lines 2 levels deep]
I'm looking into broken URLs of Fedora packages of (inter alia) CPAN
modules, in the following picking
https://src.fedoraproject.org/rpms/perl-Config-IniHash as a random
example.
|The first line of a META.yml file should be a valid YAML document
|header like "--- #YAML:1.0".
Maybe that's the problem? (Just a wild guess as I'm not really
familiar with the old spec's details.)
If an author releases a new module (or new version) on PAUSE, an
indexer analyses the package including the META-spec (and usually
sends a mail to the author that everything went well, what it indexed
etc.). But this process can sometimes fail and the author has to
restart it manually. (I never had any problems though, I just read
about it.)
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 918 |
Nodes: | 10 (1 / 9) |
Uptime: | 26:21:16 |
Calls: | 12,179 |
Calls today: | 2 |
Files: | 186,523 |
Messages: | 2,235,545 |