Front page | perl.perl5.porters |
Postings from May 2012
RC2 status
Thread Next
From:
Ricardo Signes
Date:
May 15, 2012 15:54
Subject:
RC2 status
Message ID:
20120515225441.GA12646@cancer.codesimply.com
Here's where we stand.
* Win32 is still in the same shape it was yesterday.
* Jim Keenan reported "Unrecognized character \xCB;" during a
terminated-and-restarted build that we could not reproduce. He's going to
try again. I do not consider this a blocker.
* [perl #112946] - The user is building as root with umask 0700 (or so).
Config_heavy.pl is written out o-w,g-w and then the filetest.t test
drops to uid 1 and tries to do work, which tries to load Config_heavy.pl,
which can no longer be read.
My take: we fix the test... later. This goes into known problems as
"t/op/filetest.t will fail if you are building as root with umask 0x00"
* "Configure misdetects strlcpy et. al. with gcc -flto"
I think this, too, is "known problem" material. As Nicholas mentioned,
touching the code that sorts this out has been known to be twitchy. I think
Lukas presented something new and quite possibly better, but I'd rather see
it more thoroughly tested.
* "IO::Socket fails to propagate socket type information"
I would have liked to leave this applied, but I think we're going to provide
a better build success rate without it for now. The *really important* thing
is that IO is dual-lifed, and we can release a fix as soon as we're happy
with it, and it can be installed atop 5.16.0 even before 5.16.1, if that's
how things pan out.
* 5.16.0-RC1: mro/package_aliases_utf8.t failing with PERL_UNICODE=A
I have yet to try to reproduce this, but I imagine I'll be able to, and that
Lukas's suggested fix will be right for now... but probably PERL_UNICODE
belongs in @bad_env_vars in t/TEST, no?
------
If I have not listed your bug or concern, I promise I am not slyly trying to
put one over on you. I just forgot.
I am on a bus right now, and so I can't do all the build testing I'd like, but
I will do so tonight. If I hear no strong objections, I will also issue RC2.
After all, we can always have RC3, right?
Finally, I remember how many of Jesse Vincent's emails during the 5.14 release
period were sent from airports. Mine all all to come from the bus. I wonder
whether the next pumpking will be sending a lot of RC-related mail from a
bicycle...
--
rjbs
Thread Next
-
RC2 status
by Ricardo Signes