New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module::CoreList 5.20160410 not on CPAN #15278
Comments
From @eserteThis is a bug report for perl from slaven@rezic.de, See subject. Flags: Site configuration information for perl 5.22.2: Configured by eserte at Tue Apr 12 07:39:08 CEST 2016. Summary of my perl5 (revision 5 version 22 subversion 2) configuration: Locally applied patches: @INC for perl 5.22.2: Environment for perl 5.22.2: |
From @rjbsI'm confused. Did Module::CoreList 5.20160410 ever exist? The version currently in blead is 5.20160420, but there was no April 20th release, so there has been no subsequent CPAN release of it. I believe this ticket should be rejected. Am I mistaken? -- |
The RT System itself - Status changed from 'new' to 'open' |
From @andk
> I'm confused. Did Module::CoreList 5.20160410 ever exist? All my perl-5.22.2-RC1 report 5.20160410 like this one: : % /home/sand/src/perl/repoperls/installed-perls/perl/v5.22.2-RC1/de40/bin/perl -MV=Module::CoreList > The version currently in blead is 5.20160420, but there was no April commit 0d84e96 in branch maint-5.22 > I believe this ticket should be rejected. Am I mistaken? -- |
From @steve-m-hayOn 18 April 2016 at 02:45, Andreas Koenig
Yes, 20164010 was the release date of 5.22.2 RC1, but as per the =head3 Module::CoreList nagging I<You MUST SKIP this step for RC> Remind the current maintainer of C<Module::CoreList> to push a new release
I agree, unless there is some problem with the instructions in the RMG |
From @eserteDana Pon 18. Tra 2016, 00:12:00, shay reče:
Maybe I should explain why this is a problem. My smoker's selection schema for CPAN distributions is to select everything which is indexed. This means that in situations like these an older Module::CoreList version than required for correct functioning for this perl may slip in, causing distribution depending on M::C to fail. Actually this is happening (e.g. for Mojolicious-Command-listdeps-0.08) and is causing unnecessary fail reports for the module author and unnecessary entries on the beforemaintrelease page. I see two solutions here: Regards, |
Migrated from rt.perl.org#127914 (status was 'open')
Searchable as RT127914$
The text was updated successfully, but these errors were encountered: