Hello community, here is the log from the commit of package perl-Log-Log4perl for openSUSE:Factory checked in at 2016-03-26 15:20:36 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/perl-Log-Log4perl (Old) and /work/SRC/openSUSE:Factory/.perl-Log-Log4perl.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "perl-Log-Log4perl" Changes: -------- --- /work/SRC/openSUSE:Factory/perl-Log-Log4perl/perl-Log-Log4perl.changes 2012-05-31 17:08:49.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.perl-Log-Log4perl.new/perl-Log-Log4perl.changes 2016-03-26 15:20:38.000000000 +0100 @@ -1,0 +2,28 @@ +Sun Mar 20 10:16:58 UTC 2016 - [email protected] + +- updated to 1.47 + see /usr/share/doc/packages/perl-Log-Log4perl/Changes + + 1.47 (2016/03/17) + * (ms) [rt.cpan.org #102647] Slaven Rezic fixed a test + case for file permissions + * (ms) Fixed synopsis code in Log::Log4perl::Appender::DBI, + reported by Chris Collins. + * (ms) Added suggestion by Dylan Doxey to test for both MSWin32 and + cygwin to detect windows-like systems for which tests need + to be skipped. + * (ms) [rt.cpan.org #110915] Fixed "Redundant argument in sprintf" + warning caused by DateFormat.pm with %d{Z} placeholders, + reported by Alexander Hartmaier. + * (ms) [rt.cpan.org #110512] Felix Ostmann fixed a broken error + message raised when a boolean filter can't be found. + * (ms) All hash traversals in Config.pm now done via "sort keys" + to make sure we can reliably reproduce potential problems. + +------------------------------------------------------------------- +Sun Sep 6 08:46:05 UTC 2015 - [email protected] + +- updated to 1.46 + see /usr/share/doc/packages/perl-Log-Log4perl/Changes + +------------------------------------------------------------------- Old: ---- Log-Log4perl-1.36.tar.gz New: ---- Log-Log4perl-1.47.tar.gz cpanspec.yml ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ perl-Log-Log4perl.spec ++++++ --- /var/tmp/diff_new_pack.llf6ak/_old 2016-03-26 15:20:39.000000000 +0100 +++ /var/tmp/diff_new_pack.llf6ak/_new 2016-03-26 15:20:39.000000000 +0100 @@ -1,7 +1,7 @@ # # spec file for package perl-Log-Log4perl # -# Copyright (c) 2012 SUSE LINUX Products GmbH, Nuernberg, Germany. +# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -17,20 +17,21 @@ Name: perl-Log-Log4perl -Version: 1.36 +Version: 1.47 Release: 0 %define cpan_name Log-Log4perl Summary: Log4j implementation for Perl License: GPL-1.0+ or Artistic-1.0 Group: Development/Libraries/Perl Url: http://search.cpan.org/dist/Log-Log4perl/ -Source: http://www.cpan.org/authors/id/M/MS/MSCHILLI/%{cpan_name}-%{version}.tar.gz +Source0: http://www.cpan.org/authors/id/M/MS/MSCHILLI/%{cpan_name}-%{version}.tar.gz +Source1: cpanspec.yml BuildArch: noarch BuildRoot: %{_tmppath}/%{name}-%{version}-build BuildRequires: perl BuildRequires: perl-macros -# MANUAL -Requires: rrdtool +BuildRequires: perl(File::Path) >= 2.060600 +Requires: perl(File::Path) >= 2.060600 %{perl_requires} %description @@ -40,7 +41,7 @@ *For a detailed tutorial on Log::Log4perl usage, please read* - http://www.perl.com/pub/a/2002/09/11/log4perl.html +http://www.perl.com/pub/a/2002/09/11/log4perl.html Logging beats a debugger if you want to know what's going on in your code during runtime. However, traditional logging packages are too static and @@ -49,23 +50,17 @@ 'Log::Log4perl' is different. It allows you to control the number of logging messages generated at three different levels: -* * - - At a central location in your system (either in a configuration file or - in the startup code) you specify _which components_ (classes, functions) - of your system should generate logs. - -* * - - You specify how detailed the logging of these components should be by - specifying logging _levels_. - -* * - - You also specify which so-called _appenders_ you want to feed your log - messages to ("Print it to the screen and also append it to /tmp/my.log") - and which format ("Write the date first, then the file name and line - number, and then the log message") they should be in. + * At a central location in your system (either in a configuration file or in +the startup code) you specify _which components_ (classes, functions) of +your system should generate logs. + + * You specify how detailed the logging of these components should be by +specifying logging _levels_. + + * You also specify which so-called _appenders_ you want to feed your log +messages to ("Print it to the screen and also append it to /tmp/my.log") +and which format ("Write the date first, then the file name and line +number, and then the log message") they should be in. This is a very powerful and flexible mechanism. You can turn on and off your logs at any time, specify the level of detail and make that dependent @@ -84,7 +79,7 @@ %prep %setup -q -n %{cpan_name}-%{version} -find . -type f -print0 | xargs -0 chmod 644 +find . -type f ! -name \*.pl -print0 | xargs -0 chmod 644 %build %{__perl} Makefile.PL INSTALLDIRS=vendor ++++++ Log-Log4perl-1.36.tar.gz -> Log-Log4perl-1.47.tar.gz ++++++ ++++ 9098 lines of diff (skipped) ++++++ cpanspec.yml ++++++ --- #description_paragraphs: 3 #no_testing: broken upstream #sources: # - source1 # - source2 #patches: # foo.patch: -p1 # bar.patch: #preamble: |- # BuildRequires: gcc-c++ #post_prep: |- # hunspell=`pkg-config --libs hunspell | sed -e 's,-l,,; s, *,,g'` # sed -i -e "s,hunspell-X,$hunspell," t/00-prereq.t Makefile.PL #post_install: |- # sed on %{name}.files #license: SUSE-NonFree #skip_noarch: 1 #custom_build: |- #./Build build flags=%{?_smp_mflags} --myflag #custom_test: |- #startserver && make test #ignore_requires: Bizarre::Module
