[Bug 970567] New: perl-5.18: t/op/coreamp.t sometimes fails
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=970567
Bug ID: 970567
Summary: perl-5.18: t/op/coreamp.t sometimes fails
Product: Fedora
Version: rawhide
Component: perl
Severity: unspecified
Priority: unspecified
Assignee: mmaslano(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: cweyl(a)alumni.drew.edu, iarnell(a)gmail.com,
jplesnik(a)redhat.com, kasal(a)ucw.cz, lkundrak(a)v3.sk,
mmaslano(a)redhat.com,
perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com,
psabata(a)redhat.com, rc040203(a)freenet.de,
tcallawa(a)redhat.com
There is a bug in t/op/coreamp.t tests that fails randomly. Fixed with this
upstream patch:
commit fba93b250c0d566f7ef26442312286310b2b9b46
Author: Father Chrysostomos <sprout(a)cpan.org>
Date: Sun Jun 2 00:36:33 2013 -0700
[perl #118237] Fix coreamp.t’s rand test
when rand returns something really small that does not
begin with 0, such as 2.90736361456823e-05.
diff --git a/t/op/coreamp.t b/t/op/coreamp.t
index c1f7181..fe7c741 100644
--- a/t/op/coreamp.t
+++ b/t/op/coreamp.t
@@ -637,7 +637,7 @@ test_proto 'quotemeta', '$', '\$';
test_proto 'rand';
$tests += 3;
-like &CORE::rand, qr/^0[.\d+-e]*\z/, '&rand';
+like &CORE::rand, qr/^[.\d+-e]*\z/, '&rand';
unlike join(" ", &CORE::rand), qr/ /, '&rand in list context';
&cmp_ok(&CORE::rand(78), qw '< 78', '&rand with 1 arg');
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=2cl2QSvo7O&a=cc_unsubscribe
10 years, 8 months
[Bug 978233] New: perl-5.18: Regex \8 and \9 after literals no longer work
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=978233
Bug ID: 978233
Summary: perl-5.18: Regex \8 and \9 after literals no longer
work
Product: Fedora
Version: rawhide
Component: perl
Severity: unspecified
Priority: unspecified
Assignee: mmaslano(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: cweyl(a)alumni.drew.edu, iarnell(a)gmail.com,
jplesnik(a)redhat.com, kasal(a)ucw.cz, lkundrak(a)v3.sk,
mmaslano(a)redhat.com,
perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com,
psabata(a)redhat.com, rc040203(a)freenet.de,
tcallawa(a)redhat.com
There is a regression about \8 and \9 back-references not working since
v5.17.0-543-g726ee55. This has been somewhat fixed with:
commit f1e1b256c5c1773d90e828cca6323c53fa23391b
Author: Yves Orton <demerphq(a)gmail.com>
Date: Tue Jun 25 21:01:27 2013 +0200
Fix rules for parsing numeric escapes in regexes
Commit 726ee55d introduced better handling of things like \87 in a
regex, but as an unfortunate side effect broke latex2html.
The rules for handling backslashes in regexen are a bit arcane.
Anything starting with \0 is octal.
The sequences \1 through \9 are always backrefs.
Any other sequence is interpreted as a decimal, and if there
are that many capture buffers defined in the pattern at that point
then the sequence is a backreference. If however it is larger
than the number of buffers the sequence is treated as an octal digit.
A consequence of this is that \118 could be a backreference to
the 118th capture buffer, or it could be the string "\11" . "8". In
other words depending on the context we might even use a different
number of digits for the escape!
This also left an awkward edge case, of multi digit sequences
starting with 8 or 9 like m/\87/ which would result in us parsing
as though we had seen /87/ (iow a null byte at the start) or worse
like /\x{00}87/ which is clearly wrong.
This patches fixes the cases where the capture buffers are defined,
and causes things like the \87 or \97 to throw the same error that
/\8/ would. One might argue we should complain about an illegal
octal sequence, but this seems more consistent with an error like
/\9/ and IMO will be less surprising in an error message.
This patch includes exhaustive tests of patterns of the form
/(a)\1/, /((a))\2/ etc, so that we dont break this again if we
change the logic more.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=wixX3ZHmwA&a=cc_unsubscribe
10 years, 8 months
[Bug 956264] New: perl scripts do not sent LOG_EMERG log messages (Sys::Syslog)
by Red Hat Bugzilla
Product: Red Hat Software Collections
https://bugzilla.redhat.com/show_bug.cgi?id=956264
Bug ID: 956264
Summary: perl scripts do not sent LOG_EMERG log messages
(Sys::Syslog)
Product: Red Hat Software Collections
Version: RHSCL-1 perl516
Component: perl
Keywords: Regression
Severity: high
Priority: urgent
Assignee: perl-maint-list(a)redhat.com
Reporter: mkyral(a)redhat.com
QA Contact: qe-baseos-apps(a)redhat.com
CC: cweyl(a)alumni.drew.edu, iarnell(a)gmail.com,
jplesnik(a)redhat.com, kasal(a)ucw.cz, lkundrak(a)v3.sk,
mmaslano(a)redhat.com,
perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com,
psabata(a)redhat.com, psplicha(a)redhat.com,
rc040203(a)freenet.de, tao(a)redhat.com,
tbeattie(a)boingo.com, tcallawa(a)redhat.com
Depends On: 956257, 454602
Group: devel
Category: ---
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=1TNGB8dQaE&a=cc_unsubscribe
10 years, 8 months
[Bug 950017] New: Unable to use LOG_EMERG level in Sys::Syslog
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=950017
Bug ID: 950017
Summary: Unable to use LOG_EMERG level in Sys::Syslog
Product: Fedora
Version: 18
Component: perl
Keywords: Regression
Severity: medium
Priority: medium
Assignee: mmaslano(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: cweyl(a)alumni.drew.edu, iarnell(a)gmail.com,
jplesnik(a)redhat.com, kasal(a)ucw.cz, lkundrak(a)v3.sk,
lzachar(a)redhat.com, mmaslano(a)redhat.com,
perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com,
psabata(a)redhat.com, rc040203(a)freenet.de,
tcallawa(a)redhat.com
External Bug ID: CPAN 82368
Category: ---
+++ This bug was initially created as a clone of Bug #949927 +++
Description of problem:
Level LOG_EMERG seems to be not recognized as valid level for syslog calls.
Other levels "LOG_ALERT LOG_CRIT LOG_ERR LOG_WARNING LOG_NOTICE LOG_INFO" were
accepted and produced messages. LOG_DEBUG was accepted as valid level too.
Version-Release number of selected component (if applicable):
perl-5.16.2-[...]
Steps to Reproduce:
1. perl -e 'use Sys::Syslog; syslog(LOG_EMERG, "emergency")'
Actual results:
syslog: level must be given at -e line 1.
Expected results:
"emergency" message written
[...]
--- Additional comment from RHEL Product and Program Management on 2013-04-09
10:02:47 GMT ---
This bugzilla has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases,
it is also being [proposed|marked] as a blocker for this release.
Please resolve ASAP.
--- Additional comment from Petr Pisar on 2013-04-09 13:08:53 GMT ---
Thanks for the report. It has been fixed in Sys-Syslog-0.31
<http://cpansearch.perl.org/src/SAPER/Sys-Syslog-0.31/Changes> which has not
yet been merged into stable perl release.
I will sub-package Sys-Syslog from perl and package latest release from CPAN
which contains the fix.
----
All perl 5.16 releases are affected, F≥18 are affected.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=aqf38LJhX6&a=cc_unsubscribe
10 years, 8 months