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
New copy-on-write breaks CPAN #12617
Comments
From @cpansproutI haven’t merged it yet, but I intend to shortly. This is what it will break: Algorithm-FEC-1.0 File::BOM is actually broken due to an existing Encode bug. There is a patch in rt.cpan.org #80608 that needs to be applied and merged into blead before 5.18. Flags: Site configuration information for perl 5.17.7: Configured by sprout at Fri Nov 23 12:46:02 PST 2012. Summary of my perl5 (revision 5 version 17 subversion 7) configuration: Locally applied patches: @INC for perl 5.17.7: Environment for perl 5.17.7: |
From @LeontOn Sun, Nov 25, 2012 at 10:37 PM, Father Chrysostomos
That's not an XS module, not does it depend on a non-core XS module. Leon |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Mon Nov 26 06:33:25 2012, LeonT wrote:
Don’t know yet. :-) The smokers have found two bugs I need to fix. I am working on that -- Father Chrysostomos |
From [Unknown Contact. See original ticket]On Mon Nov 26 06:33:25 2012, LeonT wrote:
Don’t know yet. :-) The smokers have found two bugs I need to fix. I am working on that -- Father Chrysostomos |
From @cpansproutOn Mon Nov 26 09:52:18 2012, sprout wrote:
It was actually a bug I introduced in e3918bb, which back then -- Father Chrysostomos |
From [Unknown Contact. See original ticket]On Mon Nov 26 09:52:18 2012, sprout wrote:
It was actually a bug I introduced in e3918bb, which back then -- Father Chrysostomos |
From @cpansproutOn Sun Nov 25 13:37:30 2012, sprout wrote:
It has been merged as cd298ce. -- Father Chrysostomos |
From [Unknown Contact. See original ticket]On Sun Nov 25 13:37:30 2012, sprout wrote:
It has been merged as cd298ce. -- Father Chrysostomos |
From @andkFather Chrysostomos (via RT) <perlbug-followup@perl.org> writes:
Are you intending to write individual tickets for each? In any case, I have three more: File-Map-0.53 All three start failing at v5.17.6-87-g07d01d6 -- |
From @cpansproutOn Thu Dec 06 12:17:00 2012, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:
I was planning to do so as I write patches.
Thank you. -- Father Chrysostomos |
From [Unknown Contact. See original ticket]On Thu Dec 06 12:17:00 2012, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:
I was planning to do so as I write patches.
Thank you. -- Father Chrysostomos |
From @LeontOn Thu, Dec 6, 2012 at 9:16 PM, Andreas Koenig
Interesting. Both SV_CHECK_THINKFIRST(var) before initializing the Leon |
From @andkAndreas Koenig <andreas.koenig.7os6VVqR@franz.ak.mind.de> writes:
Scratch that, it belongs into a different category. Smoker still -- |
From @LeontOn Thu, Dec 6, 2012 at 11:37 PM, Leon Timmermans <fawaka@gmail.com> wrote:
I think I've fixed it in the latest version of File::Map, but I Leon |
From @andkLeon Timmermans <fawaka@gmail.com> writes:
In my bisecting runs it survives up to v5.17.6-87-g07d01d6 and then 1a904fc is the first bad commit Disable PL_sawampersand -- |
From @LeontOn Mon, Dec 17, 2012 at 10:25 PM, Andreas Koenig
That isn't making any sense. I'd say either the bisect is wrong or the Leon |
From @andkLeon Timmermans <fawaka@gmail.com> writes:
http://www.cpantesters.org/cpan/report/26634729 -- |
From @LeontOn Wed, Dec 19, 2012 at 7:19 AM, Andreas Koenig
Thank you, that clarifies everything. I'm somewhat horrified I didn't My module makes the assumption that s/a/b/g does not reallocate the Leon |
From @cpansproutOn Wed Dec 19 05:13:09 2012, LeonT wrote:
That logic probably needs to be revisited then. Is the s/// target a -- Father Chrysostomos |
From [Unknown Contact. See original ticket]On Wed Dec 19 05:13:09 2012, LeonT wrote:
That logic probably needs to be revisited then. Is the s/// target a -- Father Chrysostomos |
From @LeontOn Wed, Dec 19, 2012 at 2:55 PM, Father Chrysostomos via RT
No, it's a SvLEN == 0 string, with set magic as fallback to ensure the Leon |
From @andkgit bisect commit 07d01d6 Enable PERL_NEW_COPY_ON_WRITE by default sample fail report http://www.cpantesters.org/cpan/report/482522f4-4462-11e2-b569-bf2ea8c9b5a1 also affected SISYPHUS/Math-GMPf-0.35.tar.gz perl -V Summary of my perl5 (revision 5 version 17 subversion 7) configuration: Characteristics of this binary (from libperl): -- |
From @nwc10On Wed, Dec 19, 2012 at 10:06:04PM +0100, Leon Timmermans wrote:
SvLEN == 0 has a historical established meaning of "the core doesn't own Nicholas Clark |
From @LeontOn Thu, Dec 20, 2012 at 1:12 PM, Nicholas Clark <nick@ccl4.org> wrote:
I assume it does, but I'm not certain on the implications for $& and Leon |
From @doyOn Sun, Nov 25, 2012 at 01:37:30PM -0800, Father Chrysostomos wrote:
[perl #116158] seems related, looks like Inline::C may be affected as -doy |
From @jkeenanOn Thu Dec 20 16:40:39 2012, doy@tozt.net wrote:
Now that Perl 5.18.0 is out, it would be good if someone could summarize * Opening tickets for any issues that have appeared with 5.18.0. Thank you very much. |
From @LeontOn Thu, Dec 20, 2012 at 1:12 PM, Nicholas Clark <nick@ccl4.org> wrote:
That is already taken into account in sv_setsv, so I guess something Leon |
From @cpansproutOn Sun May 19 17:33:08 2013, jkeenan wrote:
Before we close this ticket, we ought to find out why these are failing ILYAZ/modules/Audio-FindChunks-2.00.tar.gz Those are distributions that either fail on bleadperl or require C And I need to look into this one: POSIX-pselect-0.03 - tests pass anyway; probably still broken -- Father Chrysostomos |
From @LeontOn Thu, Aug 22, 2013 at 5:40 PM, Father Chrysostomos via RT <
It uses code highly similar to File::Map, so if that is fixed I'd assume Leon |
From @rjbsThis ticket is no longer useful. Specific problems can get specific new tickets. -- |
@rjbs - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#115910 (status was 'resolved')
Searchable as RT115910$
The text was updated successfully, but these errors were encountered: