Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upModule::CoreList version problems #14060
Comments
This comment has been minimized.
This comment has been minimized.
From @eserteCreated by @eserte5.20.1-RC1 ships with Module::CoreList 5.020001, while the newest on I have the feeling that the current versioning scheme Perl Info
|
This comment has been minimized.
This comment has been minimized.
From @eserteDana Ned 31. Kol 2014, 11:43:40, slaven@rezic.de reče:
Maybe I should outline the possible problems here: a user who installs perl 5.20.1 and then upgrades his modules (e.g. by using CPAN.pm's "upgrade" command) would get an *unusable* Module::CoreList. This will break all modules depending on correct Module::CoreList information, for example Test::Prereq (https://rt.cpan.org/Public/Bug/Display.html?id=98445 ), modules depending on Test::Prereq (e.g. CPAN::Mini::Tested, Netscape::Bookmarks, Distribution::Cooker...), or Pinto (thaljef/Pinto#167 ). IMHO this should be fixed before the perl 5.20.1 release, either within perl 5.20.1, or using a CPAN release of Module::CoreList. |
This comment has been minimized.
This comment has been minimized.
From [Unknown Contact. See original ticket]Dana Ned 31. Kol 2014, 11:43:40, slaven@rezic.de reče:
Maybe I should outline the possible problems here: a user who installs perl 5.20.1 and then upgrades his modules (e.g. by using CPAN.pm's "upgrade" command) would get an *unusable* Module::CoreList. This will break all modules depending on correct Module::CoreList information, for example Test::Prereq (https://rt.cpan.org/Public/Bug/Display.html?id=98445 ), modules depending on Test::Prereq (e.g. CPAN::Mini::Tested, Netscape::Bookmarks, Distribution::Cooker...), or Pinto (thaljef/Pinto#167 ). IMHO this should be fixed before the perl 5.20.1 release, either within perl 5.20.1, or using a CPAN release of Module::CoreList. |
This comment has been minimized.
This comment has been minimized.
From @cpansproutOn Mon Sep 08 11:26:16 2014, slaven@rezic.de wrote:
One solution would be for maint release to include a completely up-to-date corelist, instead of one that has just been updated for that particular maint release. (Not only would it solve this problem; it would also reduce the hassle required to make a release, I imagine.) -- Father Chrysostomos |
This comment has been minimized.
This comment has been minimized.
The RT System itself - Status changed from 'new' to 'open' |
This comment has been minimized.
This comment has been minimized.
From @eserteDana Pon 08. Ruj 2014, 12:41:33, sprout reče:
The corelist in the 5.20.1 release is already the most up-to-date one. It has unfortunately a lower version than the latest on CPAN. |
This comment has been minimized.
This comment has been minimized.
From @steve-m-hayOn 8 Sep 2014 21:16, "slaven@rezic.de via RT" <perlbug-followup@perl.org>
The intention is to switch to a date-based version scheme in the future to However, I'm now not so sure if this has happened before, at least So maybe a fix for this release would be wise after all. A new CPAN release New Module::CoreList releases are always made immediately after a perl That seems acceptable to me, but I'm willing to make an RC3 if the |
This comment has been minimized.
This comment has been minimized.
From @rjbs* Steve Hay <steve.m.hay@googlemail.com> [2014-09-08T19:59:54]
That seems okay to me, too, but taking a moment to see whether there are -- |
This comment has been minimized.
This comment has been minimized.
From @steve-m-hayWith the release of Module-CoreList-5.20140914 onto CPAN following the release of perl-5.20.1, am I correct in thinking that this ticket can now be closed? |
This comment has been minimized.
This comment has been minimized.
From [Unknown Contact. See original ticket]With the release of Module-CoreList-5.20140914 onto CPAN following the release of perl-5.20.1, am I correct in thinking that this ticket can now be closed? |
This comment has been minimized.
This comment has been minimized.
From @eserteDana Uto 16. Ruj 2014, 13:19:43, shay reče:
Very likely. |
This comment has been minimized.
This comment has been minimized.
From @eserteDana Uto 16. Ruj 2014, 13:41:17, slaven@rezic.de reče:
Wait, 5.18.3-RC1 has the same problem. |
This comment has been minimized.
This comment has been minimized.
From @karenetheridgeOn Wed, Sep 17, 2014 at 10:57:45PM -0700, slaven@rezic.de via RT wrote:
It needs a new Module::CoreList release that contains dates for 5.18.3-RC1. However, this release of MCL is not released to the cpan but is only |
This comment has been minimized.
This comment has been minimized.
From @steve-m-hayOn 18 September 2014 07:17, Karen Etheridge <perl@froods.org> wrote:
The MCL in 5.18.3-RC1 already has the release date for 5.18.3 filled Yes, the problem has occurred again with 5.18.3-RC1 because it's I think the only question remaining is whether maint releases of 5.18 |
This comment has been minimized.
This comment has been minimized.
From @AbigailOn Thu, Sep 18, 2014 at 08:26:01AM +0100, Steve Hay wrote:
Will a 5.YYYYMMDD scheme prevent us from doing a maint and a dev release Abigail |
This comment has been minimized.
This comment has been minimized.
From @steve-m-hayOn 18 September 2014 09:56, Abigail <abigail@abigail.be> wrote:
No, but I think other logistical / will-power factors will ;-) |
This comment has been minimized.
This comment has been minimized.
From @rjbs* Steve Hay <steve.m.hay@googlemail.com> [2014-09-18T03:26:01]
My plan was that upon the release of 5.18.3, the release data for 5.18.3 I encountered some uninteresting problems doing other things with maint-5.18, I expect this to be the last release of 5.18.3, but even if it isn't, we should -- |
This comment has been minimized.
This comment has been minimized.
From @bingosOn Thu, Sep 18, 2014 at 09:31:44AM -0400, Ricardo Signes wrote:
Sounds good to me. --
|
This comment has been minimized.
This comment has been minimized.
From zefram@fysh.orgModule::CoreList is now using the date-based version number scheme, -zefram |
This comment has been minimized.
This comment has been minimized.
From @eserteDana Fri, 15 Dec 2017 23:47:39 -0800, zefram@fysh.org reče:
The current situation is much better, though it's still not perfect. But the remaining problems are already addressed in https://rt-archive.perl.org/perl5/Ticket/Display.html?id=127914 So I agree: this ticket may be closed. |
This comment has been minimized.
This comment has been minimized.
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#122670 (status was 'resolved')
Searchable as RT122670$