Hello community,

here is the log from the commit of package perl-Devel-Cover for 
openSUSE:Factory checked in at 2013-09-13 14:44:31
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/perl-Devel-Cover (Old)
 and      /work/SRC/openSUSE:Factory/.perl-Devel-Cover.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "perl-Devel-Cover"

Changes:
--------
--- /work/SRC/openSUSE:Factory/perl-Devel-Cover/perl-Devel-Cover.changes        
2013-07-27 15:50:16.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.perl-Devel-Cover.new/perl-Devel-Cover.changes   
2013-09-13 14:44:33.000000000 +0200
@@ -1,0 +2,15 @@
+Thu Sep 12 08:18:04 UTC 2013 - [email protected]
+
+- updated to 1.08
+ - Don't test against 5.17.x development releases.
+ - Don't test against 5.19.2 and 5.19.3 which have a bug which causes tests to
+   fail.
+ - Perl 5.18 is more picky about POD encodings (Gregor Herrmann) (rt 88027).
+ - Numerous typo fixes (David Steinbrunner) (github 67).
+ - Improve -coverage options, fix -ignore_re for .gcov files (Steve Sanbeg)
+   (github 53).
+ - Work around B::CV::GV regression in 5.18.1.
+ - Officially support 5.18.1.
+ - Test against 5.19.1, 5.19.2 and 5.19.3.
+
+-------------------------------------------------------------------

Old:
----
  Devel-Cover-1.06.tar.gz

New:
----
  Devel-Cover-1.08.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ perl-Devel-Cover.spec ++++++
--- /var/tmp/diff_new_pack.F3Alo8/_old  2013-09-13 14:44:33.000000000 +0200
+++ /var/tmp/diff_new_pack.F3Alo8/_new  2013-09-13 14:44:33.000000000 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           perl-Devel-Cover
-Version:        1.06
+Version:        1.08
 Release:        0
 %define cpan_name Devel-Cover
 Summary:        Code coverage metrics for Perl

++++++ Devel-Cover-1.06.tar.gz -> Devel-Cover-1.08.tar.gz ++++++
++++ 1667 lines of diff (skipped)

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to