Hi,
In January I sent the below email to your cpan address. I have not heard back. I ended up just bumping Git.pm's version number to .40 to leapfrog your .130270 version mentioned below.
I think you might be able to just delete the $git::VERSION line and everything should still work? You have a VERSION for Git::Sub and I don't think you're using $git::VERSION anywhere. However, I'm not a big PAUSE expert so let me know if there's something else that we need to do to coordinate.
ack VERSION
./lib/Git/Sub.pm: $Git::Sub::VERSION = '0.130270';
./lib/Git/Sub.pm: $git::VERSION = '0.130270';
./lib/Git/Sub.pm:=head1 VERSION
./Makefile.PL: "VERSION" => "0.130270",
./Makefile.PL:unless ( eval { ExtUtils::MakeMaker->VERSION(6.56) } ) {
./Makefile.PL: unless eval { ExtUtils::MakeMaker->VERSION(6.52) };
Hi Olivier,
I received the following notice when I tried to upload the latest version of Git.pm from the git distribution:
Status: Decreasing version number
=================================
module: Git
version: 0.03
in file: Git-0.03/lib/Git.pm
status: Not indexed because Git-Sub-0.130270/lib/Git/Sub.pm in
D/DO/DOLMEN/Git-Sub-0.130270.tar.gz has a higher version
number (0.130270)
My purpose in putting Git.pm on CPAN is to make it so that people using things like a perlbrewed perl can get Git from CPAN to satisfy the dependency chain when using things like Git::Hooks.
I believe/guess that this section of code in your module:
package git;
{
$git::VERSION = '0.130270';
}
is confusing the CPAN indexer into thinking your module is a more recent version of Git.pm than the one I am trying to upload.
I don't know why, since the cases don't match. Perhaps it's a bug in the indexer.
Does your code need that bit for something? Is there a way to do it that doesn't make it look to the PAUSE system as if you're setting $Git::VERSION?
Thanks for any help you might be able to give with this.
mike