Hello community,
here is the log from the commit of package perl-PPIx-Regexp for openSUSE:Factory checked in at 2015-10-19 22:49:29
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/perl-PPIx-Regexp (Old)
and /work/SRC/openSUSE:Factory/.perl-PPIx-Regexp.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "perl-PPIx-Regexp"
Changes:
--------
--- /work/SRC/openSUSE:Factory/perl-PPIx-Regexp/perl-PPIx-Regexp.changes 2015-07-08 06:59:40.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.perl-PPIx-Regexp.new/perl-PPIx-Regexp.changes 2015-10-19 22:49:48.000000000 +0200
@@ -1,0 +2,38 @@
+Sat Oct 10 09:15:52 UTC 2015 - coolo@suse.com
+
+- updated to 0.042
+ see /usr/share/doc/packages/perl-PPIx-Regexp/Changes
+
+ 0.042 2015-10-09 T. R. Wyant
+ No changes since 0.041_03.
+
+ 0.041_03 2015-10-01 T. R. Wyant
+ Report error rather than failing when parsing a string consisting
+ wholly of white space.
+
+ 0.041_02 2015-09-29 T. R. Wyant
+ Group types were not being recognized if they contained the delimiter
+ character for the regexp (e.g. in qr<(?\ the look-behind
+ assertion was not recognized as such).
+ Correct mis-parse of ' s///'. Leading white space is supposed to be
+ acceptable, but the leading whitespace token caused
+ PPIx::Regexp::Lexer not to recognize the substitution as such.
+ Tokenizer was failing when the string to be parsed was so bad it was
+ trying to return the whole thing as a single
+ PPIx::Regexp::Token::Unknown.
+ PPIx::Regexp::Dumper now displays a message if a structure is missing
+ its end delimiter.
+
+ 0.041_01 2015-09-28 T. R. Wyant
+ RT 107331 Produce parse error in the presence of trailing cruft.
+ Thanks to Klaus Rindfrey for catching this.
+ The tokenizer now does a preliminary scan for delimiting brackets
+ and modifiers. Anything after the modifiers except for white space
+ is now made into a PPIx::Regexp::Token::Unknown, resulting in a
+ parse failure being reported. The previous implementation simply
+ assumed a valid expression, and in the case of the expression in the
+ ticket blithely mismatched the delimiters and returned a parse
+ without failures, but which was manifestly bogus.
+ Tweak documentation in PPIx::Regexp.
+
+-------------------------------------------------------------------
Old:
----
PPIx-Regexp-0.041.tar.gz
New:
----
PPIx-Regexp-0.042.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ perl-PPIx-Regexp.spec ++++++
--- /var/tmp/diff_new_pack.cQ95qh/_old 2015-10-19 22:49:49.000000000 +0200
+++ /var/tmp/diff_new_pack.cQ95qh/_new 2015-10-19 22:49:49.000000000 +0200
@@ -17,7 +17,7 @@
Name: perl-PPIx-Regexp
-Version: 0.041
+Version: 0.042
Release: 0
%define cpan_name PPIx-Regexp
Summary: Represent a regular expression of some sort
++++++ PPIx-Regexp-0.041.tar.gz -> PPIx-Regexp-0.042.tar.gz ++++++
++++ 2066 lines of diff (skipped)