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
[META] tickets blocking the release of perl 5.20.2 #14136
Comments
From @cpansproutThis meta-ticket will be used to collect tickets blocking the release of perl 5.20.2. |
From @bulk88On Sun Oct 05 16:43:29 2014, sprout wrote:
Please add https://rt-archive.perl.org/perl5/Ticket/Display.html?id=123483 so it goes up for votes/whatever. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @karenetheridgeIf I recall, the policy is to not upgrade all dual-life modules in between point releases, but due to https://rt.cpan.org/Ticket/Display.html?id=101095, Module::Metadata might need a bump. |
From @bulk88commit http://perl5.git.perl.org/perl.git/commitdiff/237050634b19905cdd9e8e25c2a43d0b24eb59f2 which is listed in http://perl5.git.perl.org/perl.git/blob/refs/heads/maint-5.20-votes:/Porting/cherry-pick-votes-maint-5.20.xml breaks building bleed on HPUX. Ticket for breakage filed as https://rt-archive.perl.org/perl5/Ticket/Display.html?id=123543 . I would guess (I am not a unix person) this means that that commit has to be removed. -- |
From @steve-m-hayOn 5 January 2015 at 00:31, bulk88 via RT <perlbug-followup@perl.org> wrote:
Thanks. I've added a note that if the offending commit is to be |
From @TuxOn Mon, 5 Jan 2015 08:16:57 +0000, Steve Hay
Could you apply 90207ba instead? I tested that in bulk88's configuration, and it completes -- |
From @steve-m-hayOn 5 January 2015 at 11:39, H.Merijn Brand <h.m.brand@xs4all.nl> wrote:
Proposed cherry-pick noted in 5d60892. Thanks. |
From @steve-m-hayPerl 5.20.2 was released and all blockers listed here were fixed. Closing ticket. |
@steve-m-hay - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#122913 (status was 'resolved')
Searchable as RT122913$
The text was updated successfully, but these errors were encountered: