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
Bleadperl v5.21.0-417-g1f1ec7b breaks DANIEL/Ogg-Vorbis-Header-PurePerl-1.0.tar.gz #13940
Comments
From @andkgit bisect commit 1f1ec7b Fatalize using hash|array as reference An announcement was made in Now also affected DANIEL/Ogg-Vorbis-Header-PurePerl-1.0.tar.gz I've opened https://rt.cpan.org/Ticket/Display.html?id=96578 for it. Opening also a ticket on rt.perl.org because I believe such things perl -V Summary of my perl5 (revision 5 version 21 subversion 1) configuration: Characteristics of this binary (from libperl): |
From @rjbs* "Andreas J. Koenig via RT" <perlbug-followup@perl.org> [2014-06-20T00:09:54]
Thanks, this example shows me how to improve the grep I used. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @jkeenanOn Thu Jun 19 21:09:54 2014, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:
I have supplied the author with a patch in the ticket at rt.cpan.org: Hence, if this ticket is solely concerned with Ogg-Vorbis-Header-PurePerl, it should no longer be considered to be a blocker for the release of perl-5.22. Thank you very much. -- |
From @iabynOn Mon, Apr 06, 2015 at 06:51:53PM -0700, James E Keenan via RT wrote:
I've removed it as 5.22 blocker. -- |
From @jkeenanOn Mon Apr 20 08:42:22 2015, davem wrote:
The author of Ogg-Vorbis-Header-PurePerl hasn't done anything with my patch submission (https://rt.cpan.org/Ticket/Display.html?id=103191https://rt.cpan.org/Ticket/Display.html?id=103191) in 8 months. So I recommend we close this ticket. Thank you very much. |
From @rjbsClosing as per Jim Keenan's comments. -- |
@rjbs - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#122139 (status was 'resolved')
Searchable as RT122139$
The text was updated successfully, but these errors were encountered: