gmane.comp.lang.perl.perl5.porters

blead is now thawed

Ricardo Signes — 2013-05-20T13:29:32

With the release of perl v5.19.0, having the shortest perldelta I can recall
editing, blead is now open for business as usual.  I'll try to start reviving
topics that I know were held off until now, soon.

Thanks, everyone, for your hard work on perl and your patience with the freeze!

Re: perl v5.19.0 is now available

Ricardo Signes — 2013-05-20T13:28:17

* Renee B <p5p.list< at >perl-services.de> [2013-05-20T09:20:01]

It should!

Re: perl v5.19.0 is now available

Renee B — 2013-05-20T13:20:01

thanks for all your work...

On 20.05.2013 15:13, Ricardo Signes wrote:

Shouldn't it be 5.19.1?

- Renée

Perl5 Bug Summary

Perl5 Bug Summary — 2013-05-20T13:15:08

Perl5 Bug Summary

http://rt.perl.org/rt3/NoAuth/perl5/Overview.html
Generated at Mon May 20 13:15:01 2013 GMT
-------------------------------------------------------------------------------

  * Numbers
  * New Issues
  * Overview of Open Issues
  * Ticket Status By Version
  * Requestors with most open tickets

-------------------------------------------------------------------------------

Numbers

Ticket Counts: 199 new + 1141 open = 1340
Created this week: 15
Closed this week: 15
Changed this week: 43 - created - closed = 13

-------------------------------------------------------------------------------

New Issues

New issues that have not been responded to yet

1 - 2 weeks old
117941 CopSTASH is not reference counted, and hence can become corrupt
2 - 3 weeks old
117887 generic byteorder code in my_htonl and my_ntohl is incorrect
117855 Excessive memory waste from duplicate CvCOPFILE in threaded perl
117823 <glob*> under 'use threads;' segfaults
3 - 4 weeks old
4 - 5 weeks old
117623 [PATCH] Improve p

perl v5.19.0 is now available

Ricardo Signes — 2013-05-20T13:13:01

  From the beginning, I knew…
  …that there was nothing wrong with you…
  …that I can't fix…
  …with my hands…

  -- Batman, of the Joker, in The Dark Knight Returns

We are ready to announce perl v5.19.0 the first development release of
version 19 of Perl 5.

You will soon be able to download Perl v5.19.0 from your favorite CPAN
mirror or find it at:

https://metacpan.org/release/RJBS/perl-5.19.0/

SHA1 digests for this release are:

 1672b54b715c6058060c8ce8d31bd57563d65c99 perl-5.19.0.tar.bz2
 e2a73a07629267f28ec537b01ad847164e2d07df perl-5.19.0.tar.gz

You can find a full list of changes in the file "perldelta.pod" located in
the "pod" directory inside the release and on the web.

Perl v5.19.0 represents approximately 0.2857142857 weeks of development
since Perl v5.18.0 and contains approximately 52,000 lines of changes
across 310 files from 6 authors.

Perl continues to flourish into its third decade thanks to a vibrant
community of users and developers. The following people are known to

Re: [perl #116851] Test failures on DragonflyBSD

Chris 'BinGOs' Williams — 2013-05-20T12:01:23

I dealt with these in what was blead and became v5.18.0

33821f2f1514a9813696be8d26217081cabbf062 lib/File/Copy.t
d04589db35f09d1a2397c7ca43216163acba7a2d lib/filetest.t

The sticky bit appears to be extremely sticky.

And the dflybsd filetests don't appear to honour chflags.

Skipped those applicable tests on DragonflyBSD.

Cheers,

DAVEM TPF bug-grant report #167

Dave Mitchell — 2013-05-20T10:57:55

In the latter part of this week I started work on finally eliminating
global state from the regex engine (i.e. the various fields within
PL_reg_state). In a private branch on my desktop, I have reduced the
number of fields from 17 to 7 so far.

(Note that the ticket I'm accounting this against is technically already
fixed, but this work provides a more general fix).

Report for period 2013/05/13 to 2013/05/19 inclusive

SUMMARY
-------

    Effort (HH::MM):

        0:00 diagnosing bugs
        9:29 fixing bugs
        0:00 reviewing other people's bug fixes
        0:00 reviewing ticket histories
        0:00 review the ticket queue (triage)
       -----
        9:29 TOTAL

    Numbers of tickets closed:

           0 tickets closed that have been worked on
           0 tickets closed related to bugs that have been fixed
           0 tickets closed that were reviewed but not worked on (triage)
       -----
           0 TOTAL


DETAIL
------

[perl #114878] Regular Expression matching in signal handler

Re: [perl #116569] Re: 5.17.7 breaks rules of assignment

Dave Mitchell — 2013-05-20T10:24:27

The plan (or at least my plan) is to re-enable COW by default shortly
after 5.19.0 is released (thus giving us a year to iron out issues and
allow CPAN authors to fix things up). Thus this ticket should be left
open.

[perl #118059] race condition+fail in dist\IO\t\cachepropagate-tcp.t

Tony Cook via RT — 2013-05-20T09:10:14

___________________________________________________________________________

I see this failure maybe 1 in 20 runs (Windows 7 x64, Core i7).

I suspect the problem is that winsock is invalidating the accept socket 
once the child socket goes out of scope, causing a race in the accept()
implementation.

I changes the code so the child reads a line from the socket, and 
the parent closes the socket.  With that I had 2700 successful runs
before I stopped testing.

I'll try a smoke-me to see if it breaks anywhere else.

Tony

---
via perlbug:  queue: perl5 status: new
https://rt.perl.org:443/rt3/Ticket/Display.html?id=118059

Re: [perl #118055] miniperl fails with SIGBUS on sparc (usethreads+use64bitint)

Nicholas Clark — 2013-05-20T07:19:42


Agree. Been caught out by these before.


I think it needs to be to the alignment of the largest thing in an OP.
Which on a 32 bit sparc with 64 bit IVs is (currently) 64 bits:


struct pmop {
    BASEOP
    OP *op_first;
    OP *op_last;
#ifdef USE_ITHREADS
    IV          op_pmoffset;
#else
    REGEXP *    op_pmregexp;            /* compiled expression */
#endif


But really, that "IV" should be something else. "STRLEN", I think, or even
just size_t, because it's being used as an array index, and arrays can't
be 64 bits large on a 32 bit system.

We can't change that for 5.18.x. But as well as the alignment thing, we
should fix it for the future.

Nicholas Clark

[perl #118059] race condition+fail in dist\IO\t\cachepropagate-tcp.t

bulk88 — 2013-05-20T03:24:50

# New Ticket Created by  bulk88 
# Please include the string:  [perl #118059]
# in the subject line of all future correspondence about this issue. 
# <URL: https://rt.perl.org:443/rt3/Ticket/Display.html?id=118059 >


This is a bug report for perl from bulk88< at >hotmail.com,
generated with the help of perlbug 1.39 running under perl 5.19.0.


-----------------------------------------------------------------
[Please describe your issue here]

There is a race condition in cachepropagate-tcp.t between the parent 
proc's accept() and the child proc's connection since the child proc has 
a "sleep(1);" delay. On my Win32 32 bit, Server 2003 x64, 8 core, VC 
2008 Perl, the ->accept() times out, does not return an obj, and then 
fatally errors when ->sockdomain() is called on an undefined scalar. Example

___________________________________________________________________________
C:\p519\src\t>..\perl.exe -I..\lib harness ../dist/IO/t/cachepropagate-tcp.t
../dist/IO/t/cachepropagate-tcp.t .. 1/8 Can't call method "sock

Re: [perl #118055] miniperl fails with SIGBUS on sparc (usethreads+use64bitint)

Leon Timmermans — 2013-05-20T03:11:38

This smells like an alignment issue.


That makes perfect sense with my theory. Probably that allocator
should do some padding to 64-bit boundaries.

Leon

[perl #64126] ./Configure -de -Dusevendorprefix doesn't default

James E Keenan via RT — 2013-05-20T02:40:31

Let's try again!  Configure experts, can you take a look?

Thank you very much.
Jim Keenan

---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=64126

[perl #116851] Test failures on DragonflyBSD

James E Keenan via RT — 2013-05-20T02:37:33

Are these failures still appearing with 5.18.0?

And, assuming they are, do we have an idea how to fix them for this OS

[perl #116158] 5.17.7 breaks rules of assignment

James E Keenan via RT — 2013-05-20T02:34:03

Slight correction:  Sisyphus recommended that ticket be closed, and I
took it in anticipation of closing it within 7 days.



---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=116158

[perl #116158] 5.17.7 breaks rules of assignment

James E Keenan via RT — 2013-05-20T02:32:46

It appears that we had *two* tickets in RT titled "5.17* breaks rules of
assignment".  We closed
https://rt.perl.org/rt3/Ticket/Display.html?id=116569 just now.

Could those who participated in the discussion in *this* RT re-evaluate
the discussion and make a recommendation as to whether this ticket
should be kept open; which issues should have new tickets of their own
opened; etc.

Thank you very much.
Jim Keenan

---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=116158

[perl #116098] Error in Getopt::Std documentation examples

James E Keenan via RT — 2013-05-20T02:26:33

Applied in commit 0c0a84c65e572a92388387363562ff4da91a9380.

Thank you very much.  Closing ticket.


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=116098

[perl #116569] Re: 5.17.7 breaks rules of assignment

James E Keenan via RT — 2013-05-20T02:10:44

Thanks for getting back so quickly, Rob.

I'll take this ticket for the purpose of closing it in 7 days.  If
anyone wants to keep it open, they can provide a reason and Take it from me.

Thank you very much.
Jim Keenan


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=116569

[perl #117313] Modules broken by hash iterator randomization

Ricardo SIGNES via RT — 2013-05-20T01:24:33

I believe we no longer need to keep track of these.

[perl #117473] [PATCH] perl5180delta Fixes

Ricardo SIGNES via RT — 2013-05-20T01:23:41

These largely got applied, thanks.

Re: [perl #116569] Re: 5.17.7 breaks rules of assignment

2013-05-20T00:54:07


-----Original Message----- 
From: James E Keenan via RT


This ticket was created (by me) when COW was enabled by default in 5.17.
Shortly after, COW was disabled by default in 5.17 (and 5.18) - so the 
ticket then became irrelevant wrt default builds of both 5.17 and 5.18. 
However, perl 5.18 *can* be built COW-enabled if the build process is 
configured accordingly.

I have no objection to the closing of this ticket ... and I think that would 
be a reasonable thing to do (though I'm not entirely sure :-)

Cheers,
Rob