commit kdevelop4-plugin-python.2179 for openSUSE:13.1:Update
Hello community,
here is the log from the commit of package kdevelop4-plugin-python.2179 for
openSUSE:13.1:Update checked in at 2013-11-15 10:43:35
Comparing /work/SRC/openSUSE:13.1:Update/kdevelop4-plugin-python.2179 (Old)
and /work/SRC/openSUSE:13.1:Update/.kdevelop4-plugin-python.2179.new (New)
Package is kdevelop4-plugin-python.2179
Changes:
New Changes file:
--- /dev/null 2013-10-11 12:16:15.204037506 +0200
+++
/work/SRC/openSUSE:13.1:Update/.kdevelop4-plugin-python.2179.new/kdevelop4-plugin-python.changes
2013-11-15 10:43:36.0 +0100
@@ -0,0 +1,70 @@
+---
+Wed Oct 30 10:48:47 UTC 2013 - toddrme2...@gmail.com
+
+- Fix lang target name
+
+---
+Wed Oct 30 01:28:16 UTC 2013 - hrvoje.sen...@gmail.com
+
+- Update to 1.5.2
+ - Fix a bug which led to the PEP8 checker running on non-python
+files in some cases
+ - Properly support unicode docstrings
+ - Fix a crash in code completion which happened in some rare cases
+ - Fix a crash which could happen when a list comprehension was
+used as the default value for a function parameter
+
+---
+Sun Oct 27 23:20:16 UTC 2013 - hrvoje.sen...@gmail.com
+
+- Bump minimal libkdevplatform-devel BuildRequires to 1.4.60 as per
+ CMakeLists
+
+---
+Sun Oct 6 12:09:23 UTC 2013 - cgiboude...@gmx.com
+
+- Remove unneeded dependencies.
+
+---
+Thu Jun 27 15:44:34 UTC 2013 - hrvoje.sen...@gmail.com
+
+- Obsolete doc package
+
+---
+Sat May 18 18:55:50 UTC 2013 - toddrme2...@gmail.com
+
+- Update to 1.5.1
+ - Bugfixes
+
+---
+Tue May 7 12:28:14 UTC 2013 - toddrme2...@gmail.com
+
+- doc package no longer exists so don't require it
+
+---
+Fri May 3 18:00:24 UTC 2013 - dmitr...@opensuse.org
+
+- Move parser documentation back to main package [kde#319284]
+
+---
+Thu May 2 12:08:59 UTC 2013 - toddrme2...@gmail.com
+
+- Uodate to 1.5.0
+ - Compatible with kdevplatform 1.5.0 / kdevelop4 4.5.0
+ - No changelog
+- Split documentation package
+
+---
+Mon Nov 26 09:51:32 UTC 2012 - toddrme2...@gmail.com
+
+- Update to 1.4.1
+ - First stable release
+ - lang package is no longer available
+- Added devel package
+
+---
+Mon Sep 19 14:42:16 UTC 2011 - cgiboude...@gmx.com
+
+- Add kdevelop4-plugin-python
+
+
New:
kdev-python-v1.5.2.tar.xz
kdevelop4-plugin-python.changes
kdevelop4-plugin-python.spec
Other differences:
--
++ kdevelop4-plugin-python.spec ++
#
# spec file for package kdevelop4-plugin-python
#
# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An Open Source License is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
Name: kdevelop4-plugin-python
Version:1.5.2
Release:0
Summary:Python support for KDevelop
License:GPL-2.0+
Group: Development/Tools/IDE
Url:http://www.kdevelop.org
Source0:
http://download.kde.org/stable/kdevelop/kdev-python/%{version}/src/kdev-python-v%{version}.tar.xz
BuildRequires: fdupes
BuildRequires: kdevelop4-devel
BuildRequires: kdevelop4-pg-qt
BuildRequires: libkde4-devel
BuildRequires: libkdevplatform-devel = 1.4.60
BuildRequires: python-kde4-devel
Requires: kdevelop4
Requires: python-kde4
Requires: python-qt4
Recommends: python-pep8
Recommends: %{name}-lang
Provides: %{name}-doc = %{version}
Obsoletes: %{name}-doc %{version}
BuildRoot: %{_tmppath}/%{name}-%{version}-build
%kde4_runtime_requires
%description
A KDevelop plugin which provides Python language support.
%package devel
commit kdevelop4.2179 for openSUSE:13.1:Update
Hello community, here is the log from the commit of package kdevelop4.2179 for openSUSE:13.1:Update checked in at 2013-11-15 10:43:39 Comparing /work/SRC/openSUSE:13.1:Update/kdevelop4.2179 (Old) and /work/SRC/openSUSE:13.1:Update/.kdevelop4.2179.new (New) Package is kdevelop4.2179 Changes: New Changes file: --- /dev/null 2013-10-11 12:16:15.204037506 +0200 +++ /work/SRC/openSUSE:13.1:Update/.kdevelop4.2179.new/kdevelop4.changes 2013-11-15 10:43:40.0 +0100 @@ -0,0 +1,546 @@ +--- +Thu Oct 31 17:00:40 UTC 2013 - dmitr...@opensuse.org + +- Update to version 4.5.2 + * Make qt4.py compatible with Python 3.x + * Backport crash fixes for crash in Cpp TypeBuilder. + * When calling a constructor don't offer deleted ones for completion + * Do not offer explicitely deleted methods for code completion + * Do not insert spaces in function definition after void or type with no argument name + * Fix missing break in the c++ parser + * Fix build on big endian plattforms. + * Fix endless recursion in setSpecializedFrom + * Fix usage of PushValue for recursion counters in TemplateDeclaration. + * Gracefully react to a lack of a working directory + * cpp_header.h: Conditionally add license header + * Don't run an execute process command if the working dir is unknown + * Don't use the items after calling ::removeUrl + * Fix overloaded-virtual of computeCompletions. + * RETURN() also works with find_package() and include() + * Support return statement + * Update global vars when visiting set(..CACHE..FORCE) AST node + * Verify validity of type after deserialization from the storage. + * take() variables when they go out of scope + * Correct Basic C++ Template + * Fix builds for okteta in a separate prefix + +--- +Thu May 30 13:41:52 UTC 2013 - dmitr...@opensuse.org + +- Update to version 4.5.1 + * Fix crash while completing null types + * Do not offer signature assistant for changes in Qt signals. + * Raise kdelibs dependency to 4.7 + * Fix conversion from QByteArray to QString + * Don't crash if we run list(FIND) without a find element + * Fix cmake icon sizes + * Don't store a ProjectBaseItem in the MakeJob + * New implementation for get_filename_component(PATH) + * Remove erroneous double-quotes around %c in Exec line + * Add missing msg extraction + +--- +Tue Apr 30 11:16:07 UTC 2013 - toddrme2...@gmail.com + +- Added missing libqjson-devel buildrequires. + The build was complaining about not being able to find this. + +--- +Fri Apr 26 16:16:27 UTC 2013 - dmitr...@opensuse.org + +- Update to version 4.5.0 + * Unit tests improvements + * New file/project templates support + * C++ support improvements + * User interface polishing + +--- +Mon Dec 3 20:41:08 UTC 2012 - dmitr...@opensuse.org + +- Update to 4.4.1 + * Skip varibles when parsing Makefile for targets. + * Fix code completion: We used to hide const getter functions if they have a Q_PROPERTY of the same name. + * Call ::repaint explicitly on the QSplashScreen after showing it. + * Fix c++ completion bug: don't insert + * Don't crash when calling string(TOLOWER, TOUPPER or LENGTH) with too few arguments + * update splash to say v4.4 + * Put the recent projects in a button+menu instead of a list + * Fix build on PPC. + +--- +Sun Nov 4 12:10:52 UTC 2012 - mailaen...@opensuse.org + +- update to 4.4.0 + * Fix bug in signature assistant. Tested in master. + * Fix auto type-deduction for cases like 'auto foo(bar);'. + * Extend unit test + * Improve properties fetching + +--- +Tue Sep 25 11:07:18 UTC 2012 - co...@suse.com + +- buildrequire explicit version of kdevplatform + +--- +Mon Sep 10 10:56:46 UTC 2012 - wstephen...@suse.com + +- Update to 4.3.90 (4.4RC1) + * kdevelop_attach renamed to kdevelop! + * Fix auto type-deduction for cases like 'auto a(1.1);'. + * Move plain Qt application templates into a Qt category + * Add Thread and Frame Information on Execution + * Improve the way we map to cmake's variables model + * support multiple location breakpoints + * Fix threading problem in the CMakeManager + * add support for padding parenthesis headers + * Improve KDev's Dashboard projects' names + * Properly add the build directory + * Properly initialize CMAKE_INCLUDE_CURRENT_DIR + * Explicitly disable Apply button after
commit varnish for openSUSE:12.3:Update
Hello community, here is the log from the commit of package varnish for openSUSE:12.3:Update checked in at 2013-11-15 10:46:31 Comparing /work/SRC/openSUSE:12.3:Update/varnish (Old) and /work/SRC/openSUSE:12.3:Update/.varnish.new (New) Package is varnish Changes: New Changes file: NO CHANGES FILE!!! Other differences: -- ++ _link ++ --- /var/tmp/diff_new_pack.Mgf8Yl/_old 2013-11-15 10:46:32.0 +0100 +++ /var/tmp/diff_new_pack.Mgf8Yl/_new 2013-11-15 10:46:32.0 +0100 @@ -1 +1 @@ -link package='varnish.2099' cicount='copy' / +link package='varnish.2185' cicount='copy' / -- To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit varnish.2185 for openSUSE:12.2:Update
Hello community, here is the log from the commit of package varnish.2185 for openSUSE:12.2:Update checked in at 2013-11-15 10:46:28 Comparing /work/SRC/openSUSE:12.2:Update/varnish.2185 (Old) and /work/SRC/openSUSE:12.2:Update/.varnish.2185.new (New) Package is varnish.2185 Changes: New Changes file: --- /dev/null 2013-10-11 12:16:15.204037506 +0200 +++ /work/SRC/openSUSE:12.2:Update/.varnish.2185.new/varnish.changes 2013-11-15 10:46:29.0 +0100 @@ -0,0 +1,159 @@ +--- +Fri Nov 1 18:52:49 UTC 2013 - jeng...@inai.de + +- Add 0001-Make-up-our-mind-Any-req.-we-receive-from-the-client.patch + (CVE-2013-4484, bnc#848451) + +--- +Wed Feb 8 23:26:10 UTC 2012 - jeng...@medozas.de + +- Update to new upstream release 3.0.2 +* Add support for ESI and gzip +* Handle objects larger than 2G +* HTTP Range support is now enabled by default +* 307 Temporary redirect is now considered cacheable +* see ChangeLog (packaged) or + http://varnish-cache.org/trac/browser/doc/changes.rst + for details +- Note that the -s file,/var/cache/varnish,524288 argument (check + /etc/sysconfig/varnish) needs at least 1M instead of 524288 + or the daemon will not start anymore. +- Add systemd unit files + +--- +Thu Dec 8 13:51:14 UTC 2011 - co...@suse.com + +- fix license to be in spdx.org format + +--- +Tue May 10 14:01:13 UTC 2011 - crrodrig...@opensuse.org + +- Varnish Requires a C compiler, the vcl scripts are compiled + and loaded as DSO. + +--- +Sat Apr 16 17:26:10 UTC 2011 - crrodrig...@opensuse.org + +- remove configure option --enable-debugging-symbols + it overrides buildsystem optimization levels. + +--- +Sat Apr 16 17:12:11 UTC 2011 - crrodrig...@opensuse.org + +- Update to version 2.1.5 + * Two bugs relating to Content-Length and possible duplication +of Content-Length headers have been resolved. + * Fixed an issue with re-using connections after Chunked-Encoding. + * Use the time of cache-insertion for If-Modified-Since requests + if a Last-Modified header isn't provided by the backend. + * Merge multi-line Vary and Cache-Control headers from clients, + which Google Chromium seem to split up. + +--- +Fri Apr 15 22:36:02 UTC 2011 - mrueck...@suse.de + +- use pkgconfig instead of pkg-config on SLES 9 + +--- +Sun Apr 3 23:38:24 UTC 2011 - jeng...@medozas.de + +- Fix security-problematic ownership of /etc/varnish files + (bnc#678811) +- Run spec-beautifier over it +- Replace default shipped vcl.conf by something working +- Run as varnish user +- Start varnishlog together with varnishd +- Properly use PID files in init script + +--- +Sat Oct 9 04:31:06 UTC 2010 - jeng...@medozas.de + +- Create and package /var/log/varnish + +--- +Thu Aug 5 22:11:24 UTC 2010 - jeng...@medozas.de + +- Update to new upstream release: 2.1.3 +* fixed an off-by-one error in the ESI handling causing includes to + fail a large part of the time. +* Avoid triggering an assert if the other end closes the connection + while we are lingering and waiting for another request from them. +* Make it possible to specify the per-thread stack size. This might + be useful on 32 bit systems with their limited address space. +* Persistent storage is now experimentally supported using the + persistent stevedore. It has the same command line arguments as + the file stevedore. +* The regular expression engine is now PCRE instead of POSIX + regular expressions. +* Add a new hashing method called critbit. This autoscales and + should work better on large object workloads than the classic + hash. Critbit has been made the default hash algorithm. +* Add support for authenticating CLI connections. +* Add hash director that chooses which backend to use depending on + req.hash. +* Add client director that chooses which backend to use depending + on the client's IP address. Note that this ignores the + X-Forwarded-For header. +* Add a timestamp to bans, so you can know how old they are. +* Varnish can now connect its CLI to a remote instance when + starting up, rather than just being connected to. +* It is no longer needed to specify the maximum number of HTTP + headers to allow from
commit amavisd-new for openSUSE:Factory
Hello community,
here is the log from the commit of package amavisd-new for openSUSE:Factory
checked in at 2013-11-15 13:12:12
Comparing /work/SRC/openSUSE:Factory/amavisd-new (Old)
and /work/SRC/openSUSE:Factory/.amavisd-new.new (New)
Package is amavisd-new
Changes:
--- /work/SRC/openSUSE:Factory/amavisd-new/amavisd-new.changes 2013-10-23
13:11:03.0 +0200
+++ /work/SRC/openSUSE:Factory/.amavisd-new.new/amavisd-new.changes
2013-11-15 13:12:14.0 +0100
@@ -1,0 +2,6 @@
+Tue Nov 12 13:40:03 UTC 2013 - w...@rosenauer.org
+
+- Add real systemd support; add required macros in %post/postun sections
+ and drop sysvinit support on openSUSE = 12.3
+
+---
Other differences:
--
++ amavisd-new.spec ++
--- /var/tmp/diff_new_pack.eRFL5M/_old 2013-11-15 13:12:15.0 +0100
+++ /var/tmp/diff_new_pack.eRFL5M/_new 2013-11-15 13:12:15.0 +0100
@@ -79,12 +79,6 @@
%define avuser vscan
%define avgroupvscan
-%if %suse_version 1220
-%define _unitdir /usr/lib/systemd
-%else
-%define _unitdir /lib/systemd
-%endif
-
%description
Amavisd-new is a high-performance interface between mailer (MTA) and
content checkers: virus scanners or SpamAssassin. It talks to the MTA
@@ -135,14 +129,13 @@
# ---
%install
-mkdir -p $RPM_BUILD_ROOT/%{avquarantine}
-mkdir -p $RPM_BUILD_ROOT/%{avspool}/{tmp,var}
-mkdir -p $RPM_BUILD_ROOT/%{avdb}
-mkdir -p $RPM_BUILD_ROOT/etc/init.d
-mkdir -p $RPM_BUILD_ROOT/%{_sbindir}
+mkdir -p $RPM_BUILD_ROOT%{avquarantine}
+mkdir -p $RPM_BUILD_ROOT%{avspool}/{tmp,var}
+mkdir -p $RPM_BUILD_ROOT%{avdb}
+mkdir -p $RPM_BUILD_ROOT%{_sbindir}
mkdir -p $RPM_BUILD_ROOT/var/adm/fillup-templates
mkdir -p $RPM_BUILD_ROOT/etc/openldap/schema
-mkdir -p $RPM_BUILD_ROOT/%{perl_vendorlib}
+mkdir -p $RPM_BUILD_ROOT%{perl_vendorlib}
mkdir -p $RPM_BUILD_ROOT/usr/lib/tmpfiles.d
install -m 644 $RPM_SOURCE_DIR/sysconfig.amavis
$RPM_BUILD_ROOT/var/adm/fillup-templates
install -m 755 amavisd $RPM_BUILD_ROOT/%{_sbindir}/amavisd
@@ -151,13 +144,18 @@
install -m 755 amavisd-release $RPM_BUILD_ROOT/%{_sbindir}/amavisd-release
install -m 755 p0f-analyzer.pl $RPM_BUILD_ROOT/%{_sbindir}/p0f-analyzer.pl
install -m 644 amavisd.conf $RPM_BUILD_ROOT/etc/amavisd.conf
-install -m 755 %{S:2} $RPM_BUILD_ROOT/etc/init.d/amavis
-ln -s ../../etc/init.d/amavis $RPM_BUILD_ROOT/%{_sbindir}/rcamavis
install -m 644 LDAP.schema
$RPM_BUILD_ROOT/etc/openldap/schema/amavisd-new.schema
install -m 644 JpegTester.pm $RPM_BUILD_ROOT/%{perl_vendorlib}/JpegTester.pm
-mkdir -p $RPM_BUILD_ROOT%{_unitdir}/system
%if 0%{?suse_version} 1140
-install -m 644 %{S:5} $RPM_BUILD_ROOT%{_unitdir}/system/
+mkdir -p $RPM_BUILD_ROOT%{_unitdir}
+install -m 644 %{S:5} $RPM_BUILD_ROOT%{_unitdir}
+%endif
+%if 0%{?suse_version} 1230
+mkdir -p $RPM_BUILD_ROOT/etc/init.d
+install -m 755 %{S:2} $RPM_BUILD_ROOT/etc/init.d/amavis
+ln -s ../../etc/init.d/amavis $RPM_BUILD_ROOT/%{_sbindir}/rcamavis
+%else
+ln -s ../../sbin/service $RPM_BUILD_ROOT/%{_sbindir}/rcamavis
%endif
install -m 755 %{S:6} $RPM_BUILD_ROOT/usr/sbin/
cd amavisd-milter
@@ -169,12 +167,27 @@
/usr/sbin/useradd -r -o -g %{avgroup} -u 65 -s /bin/false -c Vscan account
-d %{avspool} %{avuser} 2 /dev/null || :
/usr/sbin/usermod %{avuser} -g %{avgroup} 2 /dev/null || :
%{logmsg} Added user %{avuser} for package %{name}
+%if 0%{?suse_version} 1140
+%service_add_pre amavis.service
+%endif
%preun
+%if 0%{?suse_version} 1230
%stop_on_removal amavis
+%endif
+%if 0%{?suse_version} 1140
+%service_del_preun amavis.service
+%endif
%post
+%if 0%{?suse_version} 1230
%{fillup_and_insserv -n amavis amavis}
+%else
+%fillup_only
+%endif
+%if 0%{?suse_version} 1140
+%service_add_post amavis.service
+%endif
# Update ?
if [ ${1:-0} -gt 1 ]; then
: OK currently nothing to do
@@ -193,8 +206,13 @@
fi
%postun
+%if 0%{?suse_version} 1230
%restart_on_update amavis
%{insserv_cleanup}
+%endif
+%if 0%{?suse_version} 1140
+%service_del_postun amavis.service
+%endif
%files
%defattr(-,root,root)
@@ -203,14 +221,16 @@
%dir /etc/openldap
%dir /etc/openldap/schema
%dir /usr/lib/tmpfiles.d
+%if 0%{?suse_version} 1230
%config /etc/init.d/amavis
+%endif
%config(noreplace) /etc/amavisd.conf
%config(noreplace) /etc/openldap/schema/amavisd-new.schema
/var/adm/fillup-templates/sysconfig.amavis
%{_sbindir}/*
%{perl_vendorlib}/JpegTester.pm
%if 0%{?suse_version} 1140
-%config %{_unitdir}/system/amavis.service
+%{_unitdir}/amavis.service
/usr/sbin/amavisd-milter.sh
%endif
%defattr(0750,%{avuser},%{avgroup}, 0750)
--
To unsubscribe, e-mail:
commit apparmor for openSUSE:Factory
Hello community,
here is the log from the commit of package apparmor for openSUSE:Factory
checked in at 2013-11-15 13:12:17
Comparing /work/SRC/openSUSE:Factory/apparmor (Old)
and /work/SRC/openSUSE:Factory/.apparmor.new (New)
Package is apparmor
Changes:
--- /work/SRC/openSUSE:Factory/apparmor/apparmor.changes2013-11-04
07:04:40.0 +0100
+++ /work/SRC/openSUSE:Factory/.apparmor.new/apparmor.changes 2013-11-15
13:12:18.0 +0100
@@ -1,0 +2,6 @@
+Thu Nov 14 20:54:23 UTC 2013 - opens...@cboltz.de
+
+- add apparmor-profiles-ntpd-r2103.diff with updated driftfile
+ location for ntpd (bnc#850374)
+
+---
New:
apparmor-profiles-ntpd-r2103.diff
Other differences:
--
++ apparmor.spec ++
--- /var/tmp/diff_new_pack.ySLyDn/_old 2013-11-15 13:12:20.0 +0100
+++ /var/tmp/diff_new_pack.ySLyDn/_new 2013-11-15 13:12:20.0 +0100
@@ -118,6 +118,9 @@
# dnsmasq - add missing read permisions for libvirt files - bnc#848215 -
committed upstream trunk r2238, 2.8 branch r2101
Patch13:apparmor-profiles-dnsmasq.diff
+# ntpd - add missing permissions for drift file at yet another location -
bnc#850374 - commited upstream trunk r2252, 2.8 branch r2103
+Patch14:apparmor-profiles-ntpd-r2103.diff
+
# create Immunix::SubDomain perl module - only included for openSUSE = 12.1 -
bnc#720617 #c7
Patch21:apparmor-utils-subdomain-compat
@@ -492,6 +495,7 @@
%patch11
%patch12 -p1
%patch13
+%patch14
# only create Immunix::SubDomain perl module for openSUSE = 12.1
%if 0%{?suse_version}
++ apparmor-profiles-ntpd-r2103.diff ++
=== modified file 'profiles/apparmor.d/usr.sbin.ntpd'
--- profiles/apparmor.d/usr.sbin.ntpd 2013-09-16 22:25:59 +
+++ profiles/apparmor.d/usr.sbin.ntpd 2013-11-14 20:48:41 +
@@ -45,6 +45,8 @@
/usr/sbin/ntpd rmix,
/var/lib/ntp/drift rwl,
/var/lib/ntp/drift.TEMP rwl,
+ /var/lib/ntp/drift/driftfile rw,
+ /var/lib/ntp/drift/driftfile.TEMP rw,
/var/lib/ntp/drift/ntp.drift rw,
/var/lib/ntp/drift/ntp.drift.TEMP rw,
/var/lib/ntp/etc/* r,
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit castor for openSUSE:Factory
Hello community,
here is the log from the commit of package castor for openSUSE:Factory checked
in at 2013-11-15 13:14:13
Comparing /work/SRC/openSUSE:Factory/castor (Old)
and /work/SRC/openSUSE:Factory/.castor.new (New)
Package is castor
Changes:
--- /work/SRC/openSUSE:Factory/castor/castor.changes2013-08-23
11:05:46.0 +0200
+++ /work/SRC/openSUSE:Factory/.castor.new/castor.changes 2013-11-15
13:14:14.0 +0100
@@ -1,0 +2,5 @@
+Thu Nov 14 12:14:37 UTC 2013 - mvysko...@suse.com
+
+- remove test file not compatible with junit 4
+
+---
Other differences:
--
++ castor.spec ++
--- /var/tmp/diff_new_pack.RxNNG1/_old 2013-11-15 13:14:15.0 +0100
+++ /var/tmp/diff_new_pack.RxNNG1/_new 2013-11-15 13:14:15.0 +0100
@@ -129,6 +129,9 @@
find . -name *.java -exec perl -p -i -e 's|assert\(|assertTrue\(|g;' {} \;
find . -name *.java -exec perl -p -i -e
's|_test.name\(\)|_test.getName\(\)|g;' {} \;
+# junit.swingui is missing in junit 4
+rm -rf src/tests/org/exolab/castor/tests/framework/CastorTestSuiteRunner.java
+
%build
if ! grep -q javac.*source= src/build.xml ; then
perl -p -i -e 's|javac |javac source=\1.4\ |' src/build.xml
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit dom2-core-tests for openSUSE:Factory
Hello community,
here is the log from the commit of package dom2-core-tests for openSUSE:Factory
checked in at 2013-11-15 13:14:30
Comparing /work/SRC/openSUSE:Factory/dom2-core-tests (Old)
and /work/SRC/openSUSE:Factory/.dom2-core-tests.new (New)
Package is dom2-core-tests
Changes:
--- /work/SRC/openSUSE:Factory/dom2-core-tests/dom2-core-tests.changes
2013-09-11 13:39:14.0 +0200
+++ /work/SRC/openSUSE:Factory/.dom2-core-tests.new/dom2-core-tests.changes
2013-11-15 13:14:32.0 +0100
@@ -1,0 +2,5 @@
+Thu Nov 14 12:22:56 UTC 2013 - mvysko...@suse.com
+
+- remove org/w3c/domts/JUnitRunner.java not compatible with junit 4
+
+---
Other differences:
--
++ dom2-core-tests.spec ++
--- /var/tmp/diff_new_pack.h4UIxs/_old 2013-11-15 13:14:32.0 +0100
+++ /var/tmp/diff_new_pack.h4UIxs/_new 2013-11-15 13:14:32.0 +0100
@@ -52,6 +52,8 @@
find . -name *.class -exec rm {} \;
%patch0 -b .orig
cp %{SOURCE1} .
+# not compatible with junit 4
+rm -rf org/w3c/domts/JUnitRunner.java
%build
export CLASSPATH=$(build-classpath junit)
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit eric5 for openSUSE:Factory
Hello community, here is the log from the commit of package eric5 for openSUSE:Factory checked in at 2013-11-15 13:14:38 Comparing /work/SRC/openSUSE:Factory/eric5 (Old) and /work/SRC/openSUSE:Factory/.eric5.new (New) Package is eric5 Changes: --- /work/SRC/openSUSE:Factory/eric5/eric5.changes 2013-10-20 10:50:48.0 +0200 +++ /work/SRC/openSUSE:Factory/.eric5.new/eric5.changes 2013-11-15 13:14:39.0 +0100 @@ -1,0 +2,6 @@ +Thu Nov 14 02:03:14 UTC 2013 - ter...@gmail.com + +- Update to version 5.3.8 + * Bugfix release + +--- Old: eric5-5.3.7.tar.gz eric5-i18n-cs-5.3.7.tar.gz eric5-i18n-de-5.3.7.tar.gz eric5-i18n-en-5.3.7.tar.gz eric5-i18n-es-5.3.7.tar.gz eric5-i18n-fr-5.3.7.tar.gz eric5-i18n-it-5.3.7.tar.gz eric5-i18n-ru-5.3.7.tar.gz eric5-i18n-tr-5.3.7.tar.gz eric5-i18n-zh_CN.GB2312-5.3.7.tar.gz New: eric5-5.3.8.tar.gz eric5-i18n-cs-5.3.8.tar.gz eric5-i18n-de-5.3.8.tar.gz eric5-i18n-en-5.3.8.tar.gz eric5-i18n-es-5.3.8.tar.gz eric5-i18n-fr-5.3.8.tar.gz eric5-i18n-it-5.3.8.tar.gz eric5-i18n-ru-5.3.8.tar.gz eric5-i18n-tr-5.3.8.tar.gz eric5-i18n-zh_CN.GB2312-5.3.8.tar.gz Other differences: -- ++ eric5.spec ++ --- /var/tmp/diff_new_pack.w0GBPA/_old 2013-11-15 13:14:40.0 +0100 +++ /var/tmp/diff_new_pack.w0GBPA/_new 2013-11-15 13:14:40.0 +0100 @@ -17,7 +17,7 @@ Name: eric5 -Version:5.3.7 +Version:5.3.8 Release:0 Summary:Python IDE based on Qt4 License:GPL-3.0+ ++ eric5-5.3.7.tar.gz - eric5-5.3.8.tar.gz ++ /work/SRC/openSUSE:Factory/eric5/eric5-5.3.7.tar.gz /work/SRC/openSUSE:Factory/.eric5.new/eric5-5.3.8.tar.gz differ: char 5, line 1 ++ eric5-i18n-cs-5.3.7.tar.gz - eric5-i18n-cs-5.3.8.tar.gz ++ ++ eric5-i18n-de-5.3.7.tar.gz - eric5-i18n-de-5.3.8.tar.gz ++ ++ eric5-i18n-en-5.3.7.tar.gz - eric5-i18n-en-5.3.8.tar.gz ++ ++ eric5-i18n-es-5.3.7.tar.gz - eric5-i18n-es-5.3.8.tar.gz ++ ++ eric5-i18n-fr-5.3.7.tar.gz - eric5-i18n-fr-5.3.8.tar.gz ++ ++ eric5-i18n-it-5.3.7.tar.gz - eric5-i18n-it-5.3.8.tar.gz ++ ++ eric5-i18n-ru-5.3.7.tar.gz - eric5-i18n-ru-5.3.8.tar.gz ++ ++ eric5-i18n-tr-5.3.7.tar.gz - eric5-i18n-tr-5.3.8.tar.gz ++ ++ eric5-i18n-zh_CN.GB2312-5.3.7.tar.gz - eric5-i18n-zh_CN.GB2312-5.3.8.tar.gz ++ -- To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit flash-player for openSUSE:Factory:NonFree
Hello community,
here is the log from the commit of package flash-player for
openSUSE:Factory:NonFree checked in at 2013-11-15 13:16:06
Comparing /work/SRC/openSUSE:Factory:NonFree/flash-player (Old)
and /work/SRC/openSUSE:Factory:NonFree/.flash-player.new (New)
Package is flash-player
Changes:
--- /work/SRC/openSUSE:Factory:NonFree/flash-player/flash-player.changes
2013-09-16 09:35:11.0 +0200
+++ /work/SRC/openSUSE:Factory:NonFree/.flash-player.new/flash-player.changes
2013-11-15 13:16:07.0 +0100
@@ -1,0 +2,9 @@
+Wed Nov 13 19:51:26 UTC 2013 - sbra...@suse.com
+
+- Security update to 11.2.202.327: (bnc#850220)
+ * APSB13-26, CVE-2013-5329, CVE-2013-5330
+- Supplementary script (update.sh) update:
+ * Update to the new web pages layout.
+ * Use original .tar.gz files released by Adobe.
+
+---
Old:
flashplayer_11.2.202.310_sa.i386.tar.bz2
install_flash_player_11.2.202.310_linux.i386.tar.bz2
install_flash_player_11.2.202.310_linux.x86_64.tar.bz2
New:
flashplayer_11.2.202.327_sa.i386.tar.gz
install_flash_player_11.2.202.327_linux.i386.tar.gz
install_flash_player_11.2.202.327_linux.x86_64.tar.gz
Other differences:
--
++ flash-player.spec ++
--- /var/tmp/diff_new_pack.0AgZkO/_old 2013-11-15 13:16:09.0 +0100
+++ /var/tmp/diff_new_pack.0AgZkO/_new 2013-11-15 13:16:09.0 +0100
@@ -19,18 +19,18 @@
%define build_standalone 1
Name: flash-player
-Version:11.2.202.310
+Version:11.2.202.327
Release:0
Summary:Adobe Flash Plugin and Standalone Player
License:SUSE-NonFree
Group: Productivity/Networking/Web/Browsers
Url:http://get.adobe.com/flashplayer/
%ifarch %ix86
-Source0:install_flash_player_%{version}_linux.i386.tar.bz2
-Source1:flashplayer_%{version}_sa.i386.tar.bz2
+Source0:install_flash_player_%{version}_linux.i386.tar.gz
+Source1:flashplayer_%{version}_sa.i386.tar.gz
%endif
%ifarch x86_64
-Source0:install_flash_player_%{version}_linux.x86_64.tar.bz2
+Source0:install_flash_player_%{version}_linux.x86_64.tar.gz
Source1:flashplayer_11.1.102.55_sa.x86_64.tar.bz2
%endif
Source2:LICENSE
++ update.sh ++
--- /var/tmp/diff_new_pack.0AgZkO/_old 2013-11-15 13:16:09.0 +0100
+++ /var/tmp/diff_new_pack.0AgZkO/_new 2013-11-15 13:16:09.0 +0100
@@ -12,7 +12,7 @@
md5sum libflashplayer.so ORIG_FLASH
rm -f libflashplayer.so
# fetch the current download url
-download_url=$(curl -s
'http://get.adobe.com/flashplayer/completion/?installer=Flash_Player_11.2_for_other_Linux_(.tar.gz)_32-bit'
| egrep -o
'http:\/\/fpdownload.macromedia.com\/get\/flashplayer\/pdc\/11.*\/install_flash_player_11_linux.i386.tar.gz')
+download_url=$(curl -s
'http://get.adobe.com/flashplayer/download/?installer=Flash_Player_11.2_for_other_Linux_%28.tar.gz%29_32-bitstandalone=1'
| egrep -o
'http:\/\/fpdownload.macromedia.com\/get\/flashplayer\/pdc\/11.*\/install_flash_player_11_linux.i386.tar.gz')
echo Trying download $download_url;
wget $download_url
tar xf install_flash_player_11_linux.i386.tar.gz libflashplayer.so
@@ -31,8 +31,7 @@
for arch in i386 x86_64; do
wget -q $(echo $download_url | sed -e s,ARCH,$arch,)
mv install_flash_player_11_linux.$arch.tar.gz
install_flash_player_${version}_linux.$arch.tar.gz
-bznew install_flash_player_${version}_linux.$arch.tar.gz
-mv install_flash_player_${version}_linux.$arch.tar.bz2 ..
+mv install_flash_player_${version}_linux.$arch.tar.gz ..
done
sed -i -e s,Version:.*,Version:$version, ../flash-player.spec
( cd ..;
@@ -41,7 +40,7 @@
fi
for arch in i386; do
-tar xf ../flashplayer_*_sa.$arch.tar.bz2
install_flash_player_linux_sa/flashplayer
+tar xf ../flashplayer_*_sa.$arch.tar.gz
install_flash_player_linux_sa/flashplayer
md5sum install_flash_player_linux_sa/flashplayer ORIG_FLASH
rm -rf install_flash_player_linux_sa
wget
http://fpdownload.macromedia.com/pub/flashplayer/updaters/11/flashplayer_11_sa.$arch.tar.gz
@@ -57,8 +56,7 @@
version=$(strings install_flash_player_linux_sa/flashplayer | grep
LNX 11, |cut -d' ' -f2 | sed -e 's#,#.#g')
echo new version is $version
mv flashplayer_11_sa.$arch.tar.gz
flashplayer_${version}_sa.$arch.tar.gz
-bznew flashplayer_${version}_sa.$arch.tar.gz
-mv flashplayer_${version}_sa.$arch.tar.bz2 ..
+mv flashplayer_${version}_sa.$arch.tar.gz ..
commit git for openSUSE:Factory
Hello community, here is the log from the commit of package git for openSUSE:Factory checked in at 2013-11-15 13:19:43 Comparing /work/SRC/openSUSE:Factory/git (Old) and /work/SRC/openSUSE:Factory/.git.new (New) Package is git Changes: --- /work/SRC/openSUSE:Factory/git/git.changes 2013-10-30 15:32:10.0 +0100 +++ /work/SRC/openSUSE:Factory/.git.new/git.changes 2013-11-15 13:19:48.0 +0100 @@ -1,0 +2,7 @@ +Wed Nov 13 07:51:29 UTC 2013 - dougla...@outlook.com + +- updated to version 1.8.4.3 + + https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.4.3.txt + +--- Old: git-1.8.4.2.tar.gz New: git-1.8.4.3.tar.gz Other differences: -- ++ git.spec ++ --- /var/tmp/diff_new_pack.dTuMYN/_old 2013-11-15 13:19:49.0 +0100 +++ /var/tmp/diff_new_pack.dTuMYN/_new 2013-11-15 13:19:49.0 +0100 @@ -20,7 +20,7 @@ %define _fwdefdir /etc/sysconfig/SuSEfirewall2.d/services Name: git -Version:1.8.4.2 +Version:1.8.4.3 Release:0 Summary:Fast, scalable, distributed revision control system License:GPL-2.0 ++ git-1.8.4.2.tar.gz - git-1.8.4.3.tar.gz ++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/git-1.8.4.2/Documentation/RelNotes/1.8.4.3.txt new/git-1.8.4.3/Documentation/RelNotes/1.8.4.3.txt --- old/git-1.8.4.2/Documentation/RelNotes/1.8.4.3.txt 1970-01-01 01:00:00.0 +0100 +++ new/git-1.8.4.3/Documentation/RelNotes/1.8.4.3.txt 2013-11-08 21:21:49.0 +0100 @@ -0,0 +1,54 @@ +Git v1.8.4.3 Release Notes + + +Fixes since v1.8.4.2 + + + * The interaction between use of Perl in our test suite and NO_PERL + has been clarified a bit. + + * A fast-import stream expresses a pathname with funny characters by + quoting them in C style; remote-hg remote helper (in contrib/) + forgot to unquote such a path. + + * One long-standing flaw in the pack transfer protocol used by git + clone was that there was no way to tell the other end which branch + HEAD points at, and the receiving end needed to guess. A new + capability has been defined in the pack protocol to convey this + information so that cloning from a repository with more than one + branches pointing at the same commit where the HEAD is at now + reliably sets the initial branch in the resulting repository. + + * We did not handle cases where http transport gets redirected during + the authorization request (e.g. from http:// to https://). + + * git rev-list --objects ^v1.0^ v1.0 gave v1.0 tag itself in the + output, but git rev-list --objects v1.0^..v1.0 did not. + + * The fall-back parsing of commit objects with broken author or + committer lines were less robust than ideal in picking up the + timestamps. + + * Bash prompting code to deal with an SVN remote as an upstream + were coded in a way not supported by older Bash versions (3.x). + + * git checkout topic, when there is not yet a local topic branch + but there is a unique remote-tracking branch for a remote topic + branch, pretended as if git checkout -t -b topic remote/$r/topic + (for that unique remote $r) was run. This hack however was not + implemented for git checkout topic --. + + * Coloring around octopus merges in log --graph output was screwy. + + * We did not generate HTML version of documentation to git subtree + in contrib/. + + * The synopsis section of git unpack-objects documentation has been + clarified a bit. + + * An ancient How-To on serving Git repositories on an HTTP server + lacked a warning that it has been mostly superseded with more + modern way. + +Also contains a handful of trivial code clean-ups, documentation +updates, updates to the test suite, etc. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/git-1.8.4.2/Documentation/git-unpack-objects.txt new/git-1.8.4.3/Documentation/git-unpack-objects.txt --- old/git-1.8.4.2/Documentation/git-unpack-objects.txt2013-10-28 19:17:38.0 +0100 +++ new/git-1.8.4.3/Documentation/git-unpack-objects.txt2013-11-08 21:21:49.0 +0100 @@ -9,7 +9,7 @@ SYNOPSIS [verse] -'git unpack-objects' [-n] [-q] [-r] [--strict] pack-file +'git unpack-objects' [-n] [-q] [-r] [--strict] pack-file DESCRIPTION diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/git-1.8.4.2/Documentation/git.txt new/git-1.8.4.3/Documentation/git.txt --- old/git-1.8.4.2/Documentation/git.txt 2013-10-28 19:17:38.0 +0100 +++
commit gkrellm for openSUSE:Factory
Hello community,
here is the log from the commit of package gkrellm for openSUSE:Factory checked
in at 2013-11-15 13:21:09
Comparing /work/SRC/openSUSE:Factory/gkrellm (Old)
and /work/SRC/openSUSE:Factory/.gkrellm.new (New)
Package is gkrellm
Changes:
--- /work/SRC/openSUSE:Factory/gkrellm/gkrellm.changes 2013-05-06
09:51:36.0 +0200
+++ /work/SRC/openSUSE:Factory/.gkrellm.new/gkrellm.changes 2013-11-15
13:21:10.0 +0100
@@ -1,0 +2,7 @@
+Thu Oct 24 08:41:54 UTC 2013 - pgaj...@suse.com
+
+- Install /usr/lib{,64}/gkrellm2/plugins directories (bnc#841818).
+- Add gkrellm-lib64-plugins-dir.patch: Look in
+ /usr/lib64/gkrellm2/plugins on 64bit systems.
+
+---
New:
gkrellm-lib64-plugins-dir.patch
Other differences:
--
++ gkrellm.spec ++
--- /var/tmp/diff_new_pack.SvQyyc/_old 2013-11-15 13:21:11.0 +0100
+++ /var/tmp/diff_new_pack.SvQyyc/_new 2013-11-15 13:21:11.0 +0100
@@ -29,8 +29,10 @@
Source3:gkrellm-24.png
Source4:gkrellm-32.png
Source5:gkrellm-48.png
-# PATCH-FIX-OPENSUSE -- detect libsensors correctly -- pgaj...@suse.cz
+# PATCH-FIX-OPENSUSE gkrellm-libsensors.patch pgaj...@suse.cz -- detect
libsensors correctly
Patch0: %{name}-libsensors.patch
+# PATCH-FIX-OPENSUSE gkrellm-lib64-plugins-dir.patch pgaj...@suse.cz -- look
also into /usr/lib64/gkrellm2/plugins
+Patch1: %{name}-lib64-plugins-dir.patch
BuildRequires: gtk2-devel
BuildRequires: libsensors4-devel
BuildRequires: openssl-devel
@@ -90,6 +92,7 @@
%prep
%setup -q
%patch0
+%patch1
%build
cd src
@@ -111,6 +114,11 @@
cp %{SOURCE3} %{buildroot}%{_datadir}/icons/hicolor/24x24/apps/gkrellm.png
cp %{SOURCE4} %{buildroot}%{_datadir}/icons/hicolor/32x32/apps/gkrellm.png
cp %{SOURCE5} %{buildroot}%{_datadir}/icons/hicolor/48x48/apps/gkrellm.png
+# following two directories are searched for plugins and we want to own them
(bnc#841818)
+mkdir -p %{buildroot}/usr/lib/gkrellm2/plugins
+%if x%{_lib} == xlib64
+mkdir -p %{buildroot}/usr/lib64/gkrellm2/plugins
+%endif
%suse_update_desktop_file -i %name
%find_lang %{name} %{?no_lang_C}
@@ -138,6 +146,12 @@
%{_datadir}/icons/hicolor/*/apps/gkrellm.png
%{_datadir}/applications/gkrellm.desktop
%doc %{_mandir}/man1/*
+%dir /usr/lib/gkrellm2
+%dir /usr/lib/gkrellm2/plugins
+%if x%{_lib} == xlib64
+%dir /usr/lib64/gkrellm2
+%dir /usr/lib64/gkrellm2/plugins
+%endif
%files devel
%defattr(-,root,root)
++ gkrellm-lib64-plugins-dir.patch ++
Index: src/gkrellm.h
===
--- src/gkrellm.h.orig 2010-10-02 18:21:01.0 +0200
+++ src/gkrellm.h 2013-11-14 13:33:55.325216840 +0100
@@ -141,6 +141,9 @@
#if !defined(SYSTEM_PLUGINS_DIR)
#defineSYSTEM_PLUGINS_DIR /usr/lib/gkrellm2/plugins
#endif
+#if !defined(SYSTEM64_PLUGINS_DIR)
+#defineSYSTEM64_PLUGINS_DIR/usr/lib64/gkrellm2/plugins
+#endif
#else
Index: src/plugins.c
===
--- src/plugins.c.orig 2010-09-14 18:25:51.0 +0200
+++ src/plugins.c 2013-11-14 13:34:34.349703021 +0100
@@ -1293,6 +1293,10 @@
#if defined(SYSTEM_PLUGINS_DIR)
scan_for_plugins(SYSTEM_PLUGINS_DIR);
#endif
+
+#if defined(SYSTEM64_PLUGINS_DIR)
+ scan_for_plugins(SYSTEM64_PLUGINS_DIR);
+#endif
}
#if 0
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit iputils for openSUSE:Factory
Hello community,
here is the log from the commit of package iputils for openSUSE:Factory checked
in at 2013-11-15 13:22:28
Comparing /work/SRC/openSUSE:Factory/iputils (Old)
and /work/SRC/openSUSE:Factory/.iputils.new (New)
Package is iputils
Changes:
--- /work/SRC/openSUSE:Factory/iputils/iputils.changes 2013-08-01
17:13:50.0 +0200
+++ /work/SRC/openSUSE:Factory/.iputils.new/iputils.changes 2013-11-15
13:22:30.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 14:43:36 UTC 2013 - meiss...@suse.com
+
+- also do the usr move with the permissions handlers bnc#841533
+
+---
Other differences:
--
++ iputils.spec ++
--- /var/tmp/diff_new_pack.SJWTPH/_old 2013-11-15 13:22:30.0 +0100
+++ /var/tmp/diff_new_pack.SJWTPH/_new 2013-11-15 13:22:30.0 +0100
@@ -112,10 +112,10 @@
rm -rf $RPM_BUILD_ROOT
%post
-%set_permissions /bin/ping /bin/ping6
+%set_permissions %{_bindir}/ping %{_bindir}/ping6
%verifyscript
-%verify_permissions /bin/ping /bin/ping6
+%verify_permissions %{_bindir}/ping %{_bindir}/ping6
%files
%defattr(-,root,root)
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit less for openSUSE:Factory
Hello community, here is the log from the commit of package less for openSUSE:Factory checked in at 2013-11-15 13:24:20 Comparing /work/SRC/openSUSE:Factory/less (Old) and /work/SRC/openSUSE:Factory/.less.new (New) Package is less Changes: --- /work/SRC/openSUSE:Factory/less/less.changes2013-07-31 18:31:26.0 +0200 +++ /work/SRC/openSUSE:Factory/.less.new/less.changes 2013-11-15 13:24:22.0 +0100 @@ -1,0 +2,6 @@ +Wed Nov 13 11:23:59 CET 2013 - ti...@suse.de + +- Fix lesspipe.sh for removing properly the leftover tmp files + when viewing patch files without colordiff (bnc#850225) + +--- Other differences: -- ++ lessopen.sh ++ --- /var/tmp/diff_new_pack.bk0Quj/_old 2013-11-15 13:24:24.0 +0100 +++ /var/tmp/diff_new_pack.bk0Quj/_new 2013-11-15 13:24:24.0 +0100 @@ -132,7 +132,7 @@ if [ $R_NOT_SET = false ] \ [ -x `which colordiff 2/dev/null` ]; then colordiff $TMPF_pre | cat $TMPF 2/dev/null - else TMPF=$TMPF_pre; fi + else rm -f $TMPF; TMPF=$TMPF_pre; fi ;; *) if [ $LESS_ADVANCED_PREPROCESSOR = yes ]; then -- To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit libetonyek for openSUSE:Factory
Hello community,
here is the log from the commit of package libetonyek for openSUSE:Factory
checked in at 2013-11-15 13:25:05
Comparing /work/SRC/openSUSE:Factory/libetonyek (Old)
and /work/SRC/openSUSE:Factory/.libetonyek.new (New)
Package is libetonyek
Changes:
New Changes file:
--- /dev/null 2013-10-11 12:16:15.204037506 +0200
+++ /work/SRC/openSUSE:Factory/.libetonyek.new/libetonyek.changes
2013-11-15 13:25:06.0 +0100
@@ -0,0 +1,30 @@
+---
+Tue Nov 12 09:05:02 UTC 2013 - fst...@suse.com
+
+- Modify libetonyek-0.0.0-pi.patch
+ * fixes build of tests with less recent boost versions
+
+---
+Sat Nov 9 09:43:24 UTC 2013 - tchva...@suse.com
+
+- Bump to 0.0.1
+ * Fixes test
+ * Various runtime fixes
+
+---
+Fri Nov 8 15:25:26 UTC 2013 - fridrich.st...@suse.com
+
+- Add libetonyek-0.0.0-pi.patch
+ * fixes build problems with less recent boost versions
+- Don't build noarch docs for SLE11
+
+---
+Fri Nov 1 10:15:49 UTC 2013 - tchva...@suse.com
+
+- Make the package actually build.
+
+---
+Fri Nov 1 10:07:05 UTC 2013 - tchva...@suse.com
+
+- Initial commit, needed by libreo-4.2
+
New:
libetonyek-0.0.0-pi.patch
libetonyek-0.0.1.tar.xz
libetonyek.changes
libetonyek.spec
Other differences:
--
++ libetonyek.spec ++
#
# spec file for package libetonyek
#
# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An Open Source License is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
%define libname libetonyek-0_0-0
Name: libetonyek
Version:0.0.1
Release:0
Summary:Library for Apple Keynote presentations
License:MPL-2.0
Group: Productivity/Publishing/Word
Url:http://www.freedesktop.org/wiki/Software/libetonyek
Source0:http://dev-www.libreoffice.org/src/%{name}-%{version}.tar.xz
Patch0: libetonyek-0.0.0-pi.patch
BuildRequires: boost-devel
BuildRequires: cppunit-devel
BuildRequires: doxygen
BuildRequires: fdupes
BuildRequires: gcc-c++
BuildRequires: gperf
BuildRequires: libwpd-devel = 0.9.0
BuildRequires: libwpg-devel = 0.2.0
BuildRequires: libxml2-devel
BuildRequires: pkgconfig
BuildRequires: xz
BuildRequires: zlib-devel
BuildRoot: %{_tmppath}/%{name}-%{version}-build
%description
Libetonyek is library providing ability to interpret and import Apple Keynote
presentations into various applications.
%package -n %{libname}
Summary:Library for parsing the Apple Keynote presentations
Group: System/Libraries
%description -n %{libname}
Libetonyek is library providing ability to interpret and import Apple Keynote
presentations into various applications.
%package devel
Summary:Files for Developing with libetonyek
Group: Development/Libraries/C and C++
Requires: %{libname} = %{version}
Requires: libwpd-devel
Requires: libwpg-devel
%description devel
Libetonyek is library providing ability to interpret and import Apple Keynote
presentations into various applications.
This package contains the libetonyek development files.
%package devel-doc
Summary:Documentation for the libetonyek API
Group: Documentation/HTML
%if 0%{?suse_version} 1200
BuildArch: noarch
%endif
%description devel-doc
This package contains documentation for the libetonyek API.
%package tools
Summary:Tools to work with Apple Keynote presentations
Group: Productivity/Publishing/Word
%description tools
This package contains tools to work with Apple Keynote presentations
%prep
%setup -q
%patch0 -p1
%build
%configure \
--disable-werror \
--disable-static \
--docdir=%{_docdir}/%{name}-devel/html
make %{?_smp_mflags} V=1
%install
make DESTDIR=%{buildroot} install
rm %{buildroot}%{_libdir}/*.la
cp -p AUTHORS COPYING ChangeLog %{buildroot}%{_docdir}/%{name}-devel/
%fdupes -s
commit libodfgen for openSUSE:Factory
Hello community,
here is the log from the commit of package libodfgen for openSUSE:Factory
checked in at 2013-11-15 13:25:30
Comparing /work/SRC/openSUSE:Factory/libodfgen (Old)
and /work/SRC/openSUSE:Factory/.libodfgen.new (New)
Package is libodfgen
Changes:
--- /work/SRC/openSUSE:Factory/libodfgen/libodfgen.changes 2013-11-04
15:10:10.0 +0100
+++ /work/SRC/openSUSE:Factory/.libodfgen.new/libodfgen.changes 2013-11-15
13:25:31.0 +0100
@@ -1,0 +2,16 @@
+Fri Nov 8 15:43:06 UTC 2013 - fridrich.st...@suse.com
+
+- Build also the documentation
+
+---
+Fri Nov 8 09:11:19 UTC 2013 - tchva...@suse.com
+
+- Version bump to 0.0.3:
+ - handle more table properties
+ - more SVG path commands
+ - allow to define center of rotation for a textbox
+ - make linked text boxes more robust
+ - add support for generating presentations (using libetonyek)
+ - start on API documentation
+
+---
Old:
libodfgen-0.0.2.tar.xz
New:
libodfgen-0.0.3.tar.xz
Other differences:
--
++ libodfgen.spec ++
--- /var/tmp/diff_new_pack.oMj8wQ/_old 2013-11-15 13:25:32.0 +0100
+++ /var/tmp/diff_new_pack.oMj8wQ/_new 2013-11-15 13:25:32.0 +0100
@@ -19,12 +19,15 @@
Name: libodfgen
# note: the main package is empty, it only sets a sane name for the source rpm
BuildRequires: boost-devel
+BuildRequires: doxygen
+BuildRequires: fdupes
BuildRequires: gcc-c++
+BuildRequires: libetonyek-devel
BuildRequires: libwpd-devel
BuildRequires: libwpg-devel
BuildRequires: pkgconfig
BuildRequires: xz
-Version:0.0.2
+Version:0.0.3
Release:0
Summary:Library to generate ODF documents from libwpd's and libwpg's
api calls
License:LGPL-2.1+ and MPL-2.0+
@@ -58,6 +61,16 @@
libodfgen is a general purpose library designed to generate ODF documents
from api calls to libwpd and libwpg libraries.
+%package devel-doc
+Summary:Documentation for the libodfgen API
+Group: Documentation/HTML
+%if 0%{?suse_version} 1200
+BuildArch: noarch
+%endif
+
+%description devel-doc
+This package contains documentation for the libodfgen API.
+
%prep
%setup -q
@@ -65,7 +78,7 @@
%configure \
--disable-werror \
--disable-static \
- --docdir=%_docdir/%name \
+ --docdir=%{_docdir}/%{name}-devel/html \
--with-sharedptr=boost
make %{?_smp_mflags} V=1
@@ -74,6 +87,8 @@
make DESTDIR=%{buildroot} install
rm %{buildroot}%_libdir/*.la
+%fdupes -s %{buildroot}
+
%post -n %libname -p /sbin/ldconfig
%postun -n %libname -p /sbin/ldconfig
@@ -92,4 +107,9 @@
%{_libdir}/pkgconfig/libodfgen*.pc
%{_includedir}/libodfgen*
+%files devel-doc
+%defattr(-,root,root,-)
+%dir %{_docdir}/%{name}-devel
+%doc %{_docdir}/%{name}-devel/html/
+
%changelog
++ libodfgen-0.0.2.tar.xz - libodfgen-0.0.3.tar.xz ++
10678 lines of diff (skipped)
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit libpng16 for openSUSE:Factory
Hello community,
here is the log from the commit of package libpng16 for openSUSE:Factory
checked in at 2013-11-15 13:26:14
Comparing /work/SRC/openSUSE:Factory/libpng16 (Old)
and /work/SRC/openSUSE:Factory/.libpng16.new (New)
Package is libpng16
Changes:
--- /work/SRC/openSUSE:Factory/libpng16/libpng16.changes2013-09-26
19:35:55.0 +0200
+++ /work/SRC/openSUSE:Factory/.libpng16.new/libpng16.changes 2013-11-15
13:26:15.0 +0100
@@ -1,0 +2,15 @@
+Fri Nov 15 07:56:22 UTC 2013 - pgaj...@suse.com
+
+- updated to 1.6.7:
+ * Revised unknown chunk code to correct several bugs in the
+NO_SAVE_/NO_WRITE combination
+ * Check user callback behavior in pngunknown.c. Previous versions
+compiled if SAVE_UNKNOWN was not available but did nothing since the
+callback was never implemented.
+ * Merged pngunknown.c with 1.7 version and back ported 1.7
+improvements/fixes
+ * Revised pngvalid to generate size images with as many filters as
+it can manage, limited by the number of rows.
+ * ARM improvements/fixes
+
+---
Old:
libpng-1.6.6.tar.xz
libpng-1.6.6.tar.xz.asc
New:
libpng-1.6.7.tar.xz
libpng-1.6.7.tar.xz.asc
Other differences:
--
++ libpng16.spec ++
--- /var/tmp/diff_new_pack.jNGO5u/_old 2013-11-15 13:26:15.0 +0100
+++ /var/tmp/diff_new_pack.jNGO5u/_new 2013-11-15 13:26:15.0 +0100
@@ -19,7 +19,7 @@
#
%define major 1
%define minor 6
-%define micro 6
+%define micro 7
%define branch %{major}%{minor}
%define libname libpng%{branch}-%{branch}
++ libpng-1.6.6.tar.xz - libpng-1.6.7.tar.xz ++
3186 lines of diff (skipped)
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit libreoffice for openSUSE:Factory
Hello community, here is the log from the commit of package libreoffice for openSUSE:Factory checked in at 2013-11-15 13:26:53 Comparing /work/SRC/openSUSE:Factory/libreoffice (Old) and /work/SRC/openSUSE:Factory/.libreoffice.new (New) Package is libreoffice Changes: --- /work/SRC/openSUSE:Factory/libreoffice/libreoffice-branding-upstream.changes 2013-10-09 14:42:51.0 +0200 +++ /work/SRC/openSUSE:Factory/.libreoffice.new/libreoffice-branding-upstream.changes 2013-11-15 13:26:57.0 +0100 @@ -1,0 +2,5 @@ +Thu Nov 7 13:52:26 UTC 2013 - tchva...@suse.com + +- Version bump to 4.1.3 bugfix release. News: http://blog.documentfoundation.org/2013/11/01/the-document-foundation-announces-libreoffice-4-1-3/ + +--- --- /work/SRC/openSUSE:Factory/libreoffice/libreoffice-help-en-US.changes 2013-10-09 14:42:51.0 +0200 +++ /work/SRC/openSUSE:Factory/.libreoffice.new/libreoffice-help-en-US.changes 2013-11-15 13:26:57.0 +0100 @@ -1,0 +2,5 @@ +Thu Nov 7 13:52:27 UTC 2013 - tchva...@suse.com + +- Version bump to 4.1.3 bugfix release. News: http://blog.documentfoundation.org/2013/11/01/the-document-foundation-announces-libreoffice-4-1-3/ + +--- libreoffice-help-group1.changes: same change libreoffice-help-group2.changes: same change --- /work/SRC/openSUSE:Factory/libreoffice/libreoffice-help-group3.changes 2013-10-09 14:42:51.0 +0200 +++ /work/SRC/openSUSE:Factory/.libreoffice.new/libreoffice-help-group3.changes 2013-11-15 13:26:57.0 +0100 @@ -1,0 +2,5 @@ +Thu Nov 7 13:52:28 UTC 2013 - tchva...@suse.com + +- Version bump to 4.1.3 bugfix release. News: http://blog.documentfoundation.org/2013/11/01/the-document-foundation-announces-libreoffice-4-1-3/ + +--- libreoffice-help-group4.changes: same change --- /work/SRC/openSUSE:Factory/libreoffice/libreoffice-help-group5.changes 2013-10-09 14:42:52.0 +0200 +++ /work/SRC/openSUSE:Factory/.libreoffice.new/libreoffice-help-group5.changes 2013-11-15 13:26:57.0 +0100 @@ -1,0 +2,5 @@ +Thu Nov 7 13:52:29 UTC 2013 - tchva...@suse.com + +- Version bump to 4.1.3 bugfix release. News: http://blog.documentfoundation.org/2013/11/01/the-document-foundation-announces-libreoffice-4-1-3/ + +--- --- /work/SRC/openSUSE:Factory/libreoffice/libreoffice-icon-themes.changes 2013-10-09 14:42:52.0 +0200 +++ /work/SRC/openSUSE:Factory/.libreoffice.new/libreoffice-icon-themes.changes 2013-11-15 13:26:57.0 +0100 @@ -1,0 +2,5 @@ +Thu Nov 7 13:52:30 UTC 2013 - tchva...@suse.com + +- Version bump to 4.1.3 bugfix release. News: http://blog.documentfoundation.org/2013/11/01/the-document-foundation-announces-libreoffice-4-1-3/ + +--- --- /work/SRC/openSUSE:Factory/libreoffice/libreoffice-l10n.changes 2013-10-09 14:42:52.0 +0200 +++ /work/SRC/openSUSE:Factory/.libreoffice.new/libreoffice-l10n.changes 2013-11-15 13:26:57.0 +0100 @@ -1,0 +2,5 @@ +Thu Nov 7 13:52:35 UTC 2013 - tchva...@suse.com + +- Version bump to 4.1.3 bugfix release. News: http://blog.documentfoundation.org/2013/11/01/the-document-foundation-announces-libreoffice-4-1-3/ + +--- --- /work/SRC/openSUSE:Factory/libreoffice/libreoffice.changes 2013-10-09 14:42:54.0 +0200 +++ /work/SRC/openSUSE:Factory/.libreoffice.new/libreoffice.changes 2013-11-15 13:27:00.0 +0100 @@ -1,0 +2,5 @@ +Thu Nov 7 13:52:29 UTC 2013 - tchva...@suse.com + +- Version bump to 4.1.3 bugfix release. News: http://blog.documentfoundation.org/2013/11/01/the-document-foundation-announces-libreoffice-4-1-3/ + +--- Old: libreoffice-4.1.2.3.tar.xz libreoffice-help-4.1.2.3.tar.xz libreoffice-translations-4.1.2.3.tar.xz New: libreoffice-4.1.3.2.tar.xz libreoffice-help-4.1.3.2.tar.xz libreoffice-translations-4.1.3.2.tar.xz Other differences: -- ++ libreoffice-branding-upstream.spec ++ --- /var/tmp/diff_new_pack.zY9QIT/_old 2013-11-15 13:27:10.0 +0100 +++ /var/tmp/diff_new_pack.zY9QIT/_new 2013-11-15 13:27:10.0 +0100 @@ -17,7 +17,7 @@ Name: libreoffice-branding-upstream -Version:4.1.2.3 +Version:4.1.3.2 Release:0 %define lo_home libreoffice Summary:Original Branding for LibreOffice ++
commit mdds for openSUSE:Factory
Hello community,
here is the log from the commit of package mdds for openSUSE:Factory checked in
at 2013-11-15 13:27:47
Comparing /work/SRC/openSUSE:Factory/mdds (Old)
and /work/SRC/openSUSE:Factory/.mdds.new (New)
Package is mdds
Changes:
--- /work/SRC/openSUSE:Factory/mdds/mdds.changes2013-11-04
15:27:22.0 +0100
+++ /work/SRC/openSUSE:Factory/.mdds.new/mdds.changes 2013-11-15
13:27:48.0 +0100
@@ -1,0 +2,5 @@
+Thu Nov 14 11:19:25 UTC 2013 - tchva...@suse.com
+
+- Depend on pkg-config to have proper provides later on.
+
+---
Other differences:
--
++ mdds.spec ++
--- /var/tmp/diff_new_pack.o3PvNP/_old 2013-11-15 13:27:49.0 +0100
+++ /var/tmp/diff_new_pack.o3PvNP/_new 2013-11-15 13:27:49.0 +0100
@@ -19,19 +19,20 @@
Name: mdds
Version:0.8.1
Release:0
+Summary:A collection of multi-dimensional data structure and indexing
algorithm
+License:MIT
+Group: Development/Libraries/C and C++
Url:http://code.google.com/p/multidimalgorithm/
Source:
https://multidimalgorithm.googlecode.com/files/%{name}_%{version}.tar.bz2
# not upstreamed as it is specifico only for SLE
Patch0: old-gcc-bug.patch
-Summary:A collection of multi-dimensional data structure and indexing
algorithm
-License:MIT
-Group: Development/Libraries/C and C++
-BuildArch: noarch
-BuildRoot: %{_tmppath}/%{name}-%{version}-build
BuildRequires: boost-devel
BuildRequires: gcc-c++
BuildRequires: libstdc++-devel
+BuildRequires: pkg-config
Requires: boost-devel = 1.39
+BuildRoot: %{_tmppath}/%{name}-%{version}-build
+BuildArch: noarch
%description
This library provides a collection of multi-dimensional data structure and
indexing
@@ -50,7 +51,7 @@
%define _docdir %{_defaultdocdir}/%{name}-devel
%prep
-%setup -q -n %{name}_%{version}
+%setup -n %{name}_%{version}
%patch0 -p1
%build
@@ -58,7 +59,7 @@
make %{?_smp_mflags} V=1
%check
-make check
+make check %{?_smp_mflags} V=1
%install
make DESTDIR=%buildroot install
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit mutter for openSUSE:Factory
Hello community, here is the log from the commit of package mutter for openSUSE:Factory checked in at 2013-11-15 13:28:40 Comparing /work/SRC/openSUSE:Factory/mutter (Old) and /work/SRC/openSUSE:Factory/.mutter.new (New) Package is mutter Changes: --- /work/SRC/openSUSE:Factory/mutter/mutter.changes2013-10-17 17:42:30.0 +0200 +++ /work/SRC/openSUSE:Factory/.mutter.new/mutter.changes 2013-11-15 13:28:41.0 +0100 @@ -1,0 +2,7 @@ +Thu Nov 14 17:31:34 UTC 2013 - dims...@opensuse.org + +- Update to version 3.10.2 (bnc#849913): + + Fix resize operations using mouse-button-modifier (bgo#710251). + + Updated translations. + +--- Old: mutter-3.10.1.1.tar.xz New: mutter-3.10.2.tar.xz Other differences: -- ++ mutter.spec ++ --- /var/tmp/diff_new_pack.hxoAYA/_old 2013-11-15 13:28:42.0 +0100 +++ /var/tmp/diff_new_pack.hxoAYA/_new 2013-11-15 13:28:42.0 +0100 @@ -17,7 +17,7 @@ Name: mutter -Version:3.10.1.1 +Version:3.10.2 Release:0 Summary:Window and compositing manager based on Clutter License:GPL-2.0+ ++ mutter-3.10.1.1.tar.xz - mutter-3.10.2.tar.xz ++ 2828 lines of diff (skipped) -- To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit nfs-utils for openSUSE:Factory
Hello community,
here is the log from the commit of package nfs-utils for openSUSE:Factory
checked in at 2013-11-15 13:29:45
Comparing /work/SRC/openSUSE:Factory/nfs-utils (Old)
and /work/SRC/openSUSE:Factory/.nfs-utils.new (New)
Package is nfs-utils
Changes:
--- /work/SRC/openSUSE:Factory/nfs-utils/nfs-utils.changes 2013-10-22
10:20:48.0 +0200
+++ /work/SRC/openSUSE:Factory/.nfs-utils.new/nfs-utils.changes 2013-11-15
13:29:46.0 +0100
@@ -1,0 +2,14 @@
+Wed Nov 6 02:06:45 UTC 2013 - nfbr...@suse.com
+
+- nfs-utils.spec: add various systemd macros to make
+ sure init scripts are registered properly
+ bnc#845475
+- nfs.int, nfsserver.init: run gssd on server as well
+ as on client. This is needed for NFSv4.0 callbacks.
+ bnc#845269
+- exportfs-exit-with-error-code-if-there-was-any-error.patch
+- exportfs-report-failure-if-asked-to-unexport-somethi.patch
+ Return good error code from exportfs.
+ bnc#846064
+
+---
New:
exportfs-exit-with-error-code-if-there-was-any-error.patch
exportfs-report-failure-if-asked-to-unexport-somethi.patch
Other differences:
--
++ nfs-utils.spec ++
--- /var/tmp/diff_new_pack.aeq4u2/_old 2013-11-15 13:29:47.0 +0100
+++ /var/tmp/diff_new_pack.aeq4u2/_new 2013-11-15 13:29:47.0 +0100
@@ -31,6 +31,9 @@
BuildRequires: pkgconfig
BuildRequires: sqlite3-devel
BuildRequires: tcpd-devel
+%if 0%{?suse_version} = 1210
+BuildRequires: systemd
+%endif
Url:http://kernel.org/pub/linux/utils/nfs-utils/
Summary:Support Utilities for Kernel nfsd
License:GPL-2.0+
@@ -39,6 +42,7 @@
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
PreReq: %fillup_prereq %insserv_prereq
+%{?systemd_requires}
BuildRoot: %{_tmppath}/%{name}-%{version}-build
Source0:
http://kernel.org/pub/linux/utils/nfs-utils/%{version}/nfs-utils-%{version}.tar.bz2
# Download does not work:
@@ -73,6 +77,10 @@
Patch7: skip-on-ENOENT.patch
# PATCH-FIX-UPSTREAM
mountd-fix-bug-affecting-exports-of-dirs-with-64bit-.patch nfbr...@suse.de
Patch8: mountd-fix-bug-affecting-exports-of-dirs-with-64bit-.patch
+# PATCH-FIX-UPSTREAM
exportfs-exit-with-error-code-if-there-was-any-error.patch nfbr...@suse.de
+Patch9: exportfs-exit-with-error-code-if-there-was-any-error.patch
+# PATCH-FIX_UPSTREAM
exportfs-report-failure-if-asked-to-unexport-somethi.patch nfbr...@suse.de
+Patch10:exportfs-report-failure-if-asked-to-unexport-somethi.patch
Suggests: python-base
%description
@@ -131,6 +139,8 @@
%patch6 -p1
%patch7 -p1
%patch8 -p1
+%patch9 -p1
+%patch10 -p1
cp %{S:6} .
%build
@@ -194,6 +204,7 @@
%pre -n nfs-client
useradd -r -c 'NFS statd daemon' \
-s /sbin/nologin -d /var/lib/nfs -g nogroup statd /dev/null || :
+%service_add_pre nfs
%post -n nfs-client
chown statd:nogroup /var/lib/nfs
@@ -211,20 +222,27 @@
%{fillup_and_insserv -n nfs nfs}
#
%set_permissions /sbin/mount.nfs
+%service_add_post nfs
%preun -n nfs-client
%stop_on_removal nfs
+%service_del_preun nfs
%postun -n nfs-client
%restart_on_update nfs
[ -x /sbin/mkinitrd_setup ] mkinitrd_setup
%insserv_cleanup
+%service_del_postun nfs
%verifyscript -n nfs-client
%verify_permissions -e /sbin/mount.nfs
+%pre -n nfs-kernel-server
+%service_add_pre nfsserver
+
%preun -n nfs-kernel-server
%stop_on_removal nfsserver
+%service_del_preun nfsserver
%post -n nfs-kernel-server
### migrate from /var/lock/subsys
@@ -237,10 +255,12 @@
fi
###
%{fillup_and_insserv nfsserver}
+%service_add_post nfsserver
%postun -n nfs-kernel-server
%restart_on_update nfsserver
%insserv_cleanup
+%service_del_postun nfsserver
%files -n nfs-client
%defattr(-,root,root)
++ exportfs-exit-with-error-code-if-there-was-any-error.patch ++
From e10ddcb9d913f7938fc37c72568eea4e8287ade4 Mon Sep 17 00:00:00 2001
From: Neil Brown ne...@suse.de
Date: Mon, 21 Oct 2013 17:40:55 +1100
Subject: [PATCH] exportfs: exit with error code if there was any error.
Reference: bnc#846064
exportfs currently exits with a non-zero error for some errors,
but not for others.
It does this by having various support routines set the global
variable export_errno.
Change this to have 'xlog' set export_errno if an ERROR is
reported. That way all errors will be caught.
Note that the exit error code is changed from 22 (EINVAL)
to the more traditional '1'.
Signed-off-by: NeilBrown ne...@suse.de
---
support/include/exportfs.h |3 ---
support/include/xlog.h |1 +
support/nfs/exports.c |6 --
support/nfs/xlog.c |4
utils/exportfs/exportfs.c |2 --
5 files
commit python-swift3 for openSUSE:Factory
Hello community,
here is the log from the commit of package python-swift3 for openSUSE:Factory
checked in at 2013-11-15 13:30:47
Comparing /work/SRC/openSUSE:Factory/python-swift3 (Old)
and /work/SRC/openSUSE:Factory/.python-swift3.new (New)
Package is python-swift3
Changes:
--- /work/SRC/openSUSE:Factory/python-swift3/python-swift3.changes
2013-10-02 17:20:46.0 +0200
+++ /work/SRC/openSUSE:Factory/.python-swift3.new/python-swift3.changes
2013-11-15 13:30:48.0 +0100
@@ -1,0 +2,12 @@
+Wed Nov 13 09:31:55 UTC 2013 - speili...@suse.com
+
+- Update to version 1.7+git.1379116028.c367e2f:
+ + Issue #49 - fixed Date and ExpireDate checking logic Cleaned up PEP8 and
Flake8 formatting errors.canonical_string refactoring + fix typing in
middleware comment
+ + Undo part of patch by Willys
+ + Add a error of EntityTooLarge
+ + fix signature generation
+- Fix set_version service by changing the version from v1.7... to 1.7.
+ Since RPM comparison says numbers are bigger than characters, it's just
+ an ordinary version update
+
+---
Old:
swift3-v1.7+git.1372425725.9e51c35.tar.gz
New:
_servicedata
swift3-1.7+git.1379116028.c367e2f.tar.gz
Other differences:
--
++ python-swift3.spec ++
--- /var/tmp/diff_new_pack.OmfGSb/_old 2013-11-15 13:30:49.0 +0100
+++ /var/tmp/diff_new_pack.OmfGSb/_new 2013-11-15 13:30:49.0 +0100
@@ -17,7 +17,7 @@
Name: python-swift3
-Version:v1.7+git.1372425725.9e51c35
+Version:1.7+git.1379116028.c367e2f
Release:0
Summary:OpenStack Swift - Amazon S3 API Middleware
License:Apache-2.0
++ _service ++
--- /var/tmp/diff_new_pack.OmfGSb/_old 2013-11-15 13:30:49.0 +0100
+++ /var/tmp/diff_new_pack.OmfGSb/_new 2013-11-15 13:30:49.0 +0100
@@ -3,8 +3,10 @@
param name=urlgit://github.com/fujita/swift3.git/param
param name=scmgit/param
param name=exclude.git/param
-param name=versionformat@PARENT_TAG@+git.%ct.%h/param
+param name=versionformat1.7+git.%ct.%h/param
param name=revisionmaster/param
+!--TOOD(saschpe): Reenable changes generation once Adrian merged my pull:
+ param name=changesgenerateenable/param--
/service
service name=recompress mode=disabled
++ _servicedata ++
servicedata
service name=tar_scm
param name=urlgit://github.com/fujita/swift3.git/param
param name=changesrevisionc367e2f891/param/service
/servicedata++ swift3-v1.7+git.1372425725.9e51c35.tar.gz -
swift3-1.7+git.1379116028.c367e2f.tar.gz ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/swift3-v1.7+git.1372425725.9e51c35/swift3/middleware.py
new/swift3-1.7+git.1379116028.c367e2f/swift3/middleware.py
--- old/swift3-v1.7+git.1372425725.9e51c35/swift3/middleware.py 2013-07-02
13:39:42.0 +0200
+++ new/swift3-1.7+git.1379116028.c367e2f/swift3/middleware.py 2013-11-13
10:26:36.0 +0100
@@ -70,7 +70,8 @@
from swift.common.http import HTTP_OK, HTTP_CREATED, HTTP_ACCEPTED, \
HTTP_NO_CONTENT, HTTP_BAD_REQUEST, HTTP_UNAUTHORIZED, HTTP_FORBIDDEN, \
HTTP_NOT_FOUND, HTTP_CONFLICT, HTTP_UNPROCESSABLE_ENTITY, is_success, \
-HTTP_NOT_IMPLEMENTED, HTTP_LENGTH_REQUIRED, HTTP_SERVICE_UNAVAILABLE
+HTTP_NOT_IMPLEMENTED, HTTP_LENGTH_REQUIRED, HTTP_SERVICE_UNAVAILABLE, \
+HTTP_REQUEST_ENTITY_TOO_LARGE
MAX_BUCKET_LISTING = 1000
@@ -108,6 +109,9 @@
(HTTP_BAD_REQUEST, 'The Content-MD5 you specified was invalid'),
'BadDigest':
(HTTP_BAD_REQUEST, 'The Content-Length you specified was invalid'),
+'EntityTooLarge':
+(HTTP_BAD_REQUEST, 'Your proposed upload exceeds the maximum '
+'allowed object size.'),
'NoSuchBucket':
(HTTP_NOT_FOUND, 'The specified bucket does not exist'),
'SignatureDoesNotMatch':
@@ -283,7 +287,8 @@
if '?' in path:
path, args = path.split('?', 1)
params = []
-for key, value in urlparse.parse_qsl(args, keep_blank_values=True):
+for key, value in sorted(urlparse.parse_qsl(args,
+ keep_blank_values=True)):
if key in ALLOWED_SUB_RESOURCES:
params.append('%s=%s' % (key, value) if value else key)
if params:
@@ -798,6 +803,8 @@
return get_err_response('NoSuchBucket')
elif status == HTTP_UNPROCESSABLE_ENTITY:
return get_err_response('InvalidDigest')
+elif status == HTTP_REQUEST_ENTITY_TOO_LARGE:
+return get_err_response('EntityTooLarge')
commit rpm for openSUSE:Factory
Hello community,
here is the log from the commit of package rpm for openSUSE:Factory checked in
at 2013-11-15 13:32:43
Comparing /work/SRC/openSUSE:Factory/rpm (Old)
and /work/SRC/openSUSE:Factory/.rpm.new (New)
Package is rpm
Changes:
rpm-python.changes: same change
--- /work/SRC/openSUSE:Factory/rpm/rpm.changes 2013-10-30 15:51:44.0
+0100
+++ /work/SRC/openSUSE:Factory/.rpm.new/rpm.changes 2013-11-15
13:32:44.0 +0100
@@ -1,0 +2,8 @@
+Wed Nov 6 18:07:49 UTC 2013 - dval...@suse.com
+
+- Add support for ppc64le (ppc64le.diff)
+ those are upstream commits:
+ ef1497b1f81966fed56f008bc8ee8ba42102efd6
+ cf07feda05822377d62b973adc4010c0d7f9eaa0
+
+---
New:
ppc64le.diff
Other differences:
--
rpm-python.spec: same change
++ rpm.spec ++
--- /var/tmp/diff_new_pack.Cnf5CU/_old 2013-11-15 13:32:46.0 +0100
+++ /var/tmp/diff_new_pack.Cnf5CU/_new 2013-11-15 13:32:46.0 +0100
@@ -142,6 +142,9 @@
Patch88:selfconflicts.diff
Patch89:application_provides.diff
Patch90:appdata_provides.diff
+#upstream commit cf07feda05822377d62b973adc4010c0d7f9eaa0
+#upstream commit ef1497b1f81966fed56f008bc8ee8ba42102efd6
+Patch91:ppc64le.diff
Patch6464: auto-config-update-aarch64.diff
Patch68000: m68k.patch
Patch68001: debugedit-m68k.patch
@@ -231,7 +234,8 @@
%patch -P 60 -P 61 -P 62 -P 63 -P 64 -P 65 -P 66 -P 67 -P 68 -P 69
%patch -P 70 -P 71 -P 72 -P 73 -P 74 -P 75 -P 76 -P 77 -P 78 -P 79
%patch -P 80 -P 81 -P 82 -P 83 -P 84 -P 85 -P 86 -P 87 -P 88 -P 89
-%patch -P 90
+%patch -P 90 -P 91
+
%ifarch aarch64
%patch6464
%endif
++ beecrypt-4.1.2.diff ++
--- /var/tmp/diff_new_pack.Cnf5CU/_old 2013-11-15 13:32:46.0 +0100
+++ /var/tmp/diff_new_pack.Cnf5CU/_new 2013-11-15 13:32:46.0 +0100
@@ -1,5 +1,7 @@
beecrypt-4.1.2/Makefile.am.orig2004-12-22 07:06:31.0 +
-+++ beecrypt-4.1.2/Makefile.am 2006-11-24 14:08:27.0 +
+Index: beecrypt-4.1.2/Makefile.am
+===
+--- beecrypt-4.1.2/Makefile.am.orig
beecrypt-4.1.2/Makefile.am
@@ -49,7 +49,7 @@ libaltdir=$(prefix)/lib@LIBALT@
libalt_LTLIBRARIES = libbeecrypt.la
@@ -21,8 +23,10 @@
+
bench:
(cd tests $(MAKE) $(AM_MAKEFLAGS) bench)
beecrypt-4.1.2/base64.c.orig 2004-12-19 20:21:04.0 +
-+++ beecrypt-4.1.2/base64.c2006-11-24 14:08:27.0 +
+Index: beecrypt-4.1.2/base64.c
+===
+--- beecrypt-4.1.2/base64.c.orig
beecrypt-4.1.2/base64.c
@@ -253,7 +253,6 @@ char* b64encode(const void* data, size_t
unsigned c;
@@ -31,8 +35,10 @@
if (ns == 0) ns = strlen((const char*) s);
nt = ((ns + 2) / 3) * 4;
beecrypt-4.1.2/c++/io/DataOutputStream.cxx.orig2004-11-04
12:38:15.0 +
-+++ beecrypt-4.1.2/c++/io/DataOutputStream.cxx 2006-11-24 14:09:35.0
+
+Index: beecrypt-4.1.2/c++/io/DataOutputStream.cxx
+===
+--- beecrypt-4.1.2/c++/io/DataOutputStream.cxx.orig
beecrypt-4.1.2/c++/io/DataOutputStream.cxx
@@ -126,8 +126,8 @@ void DataOutputStream::writeLong(javalon
void DataOutputStream::writeChar(javaint v) throw (IOException)
{
++ ppc64le.diff ++
diff -Nur installplatform.old installplatform
--- installplatform.old 2013-11-06 19:34:36.446381950 +0100
+++ installplatform 2013-11-06 19:38:24.617417000 +0100
@@ -54,12 +54,18 @@
CANONARCH=s390x
CANONCOLOR=3
;;
-ppc64*)
+ppc64|ppc64p7)
ISANAME=ppc
ISABITS=64
CANONARCH=ppc64
CANONCOLOR=3
;;
+ppc64le)
+ ISANAME=ppc
+ ISABITS=64
+ CANONARCH=ppc64le
+ CANONCOLOR=3
+ ;;
ppc*)
ISANAME=ppc
ISABITS=32
diff -Nur lib/rpmrc.c.orig lib/rpmrc.c
--- lib/rpmrc.c.orig2013-11-06 19:34:36.426381894 +0100
+++ lib/rpmrc.c 2013-11-06 19:38:32.713558000 +0100
@@ -1119,6 +1119,7 @@
# endif /* sparc*-linux */
# if defined(__linux__) defined(__powerpc__)
+# if __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__
{
int powerlvl;
if (!rstreq(un.machine, ppc)
@@ -1127,6 +1128,7 @@
strcpy(un.machine, ppc64p7);
}
}
+# endif /* __ORDER_BIG_ENDIAN__ */
# endif /* ppc64*-linux */
# if defined(__GNUC__) defined(__alpha__)
diff -Nurrpmrc.in.orig rpmrc.in
--- rpmrc.in2013-11-06 19:34:36.446381950 +0100
+++ rpmrc.in2013-11-06 19:41:21.698505000 +0100
@@ -48,6 +48,7 @@
commit qscintilla for openSUSE:Factory
Hello community, here is the log from the commit of package qscintilla for openSUSE:Factory checked in at 2013-11-15 13:32:12 Comparing /work/SRC/openSUSE:Factory/qscintilla (Old) and /work/SRC/openSUSE:Factory/.qscintilla.new (New) Package is qscintilla Changes: --- /work/SRC/openSUSE:Factory/qscintilla/python-qscintilla.changes 2013-04-16 06:56:43.0 +0200 +++ /work/SRC/openSUSE:Factory/.qscintilla.new/python-qscintilla.changes 2013-11-15 13:32:13.0 +0100 @@ -1,0 +2,35 @@ +Thu Nov 14 02:15:18 UTC 2013 - ter...@gmail.com + +- +update to v2.8: + - Based on Scintilla v3.3.6. + - Added the SCN_FOCUSIN() and SCN_FOCUSOUT() signals to QsciScintillaBase. + - Added PreProcessorCommentLineDoc and InactivePreProcessorCommentLineDoc to +QsciLexerCPP. + - Added SCLEX_LITERATEHASKELL, SCLEX_KVIRC, SCLEX_RUST and SCLEX_STTXT to +QsciScintillaBase. + - Added ThickCompositionIndicator to QsciScintilla::IndicatorStyle. + - Added INDIC_COMPOSITIONTHICK to QsciScintillaBase. + - Added SC_FOLDACTION_CONTRACT, SC_FOLDACTION_EXPAND and SC_FOLDACTION_TOGGLE +to QsciScintillaBase. + - Added SCI_FOLDLINE, SCI_FOLDCHILDREN, SCI_EXPANDCHILDREN and SCI_FOLDALL to +QsciScintillaBase. + - Added SC_AUTOMATICFOLD_SHOW, SC_AUTOMATICFOLD_CLICK and +SC_AUTOMATICFOLD_CHANGE to QsciScintillaBase. + - Added SCI_SETAUTOMATICFOLD and SCI_GETAUTOMATICFOLD to QsciScintillaBase. + - Added SC_ORDER_PRESORTED, SC_ORDER_PERFORMSORT and SC_ORDER_CUSTOM to +QsciScintillaBase. + - Added SCI_AUTOCSETORDER and SCI_AUTOCGETORDER to QsciScintillaBase. + - Added SCI_POSITIONRELATIVE to QsciScintillaBase. + - Added SCI_RELEASEALLEXTENDEDSTYLES and SCI_ALLOCATEEXTENDEDSTYLES to +QsciScintillaBase. + - Added SCI_SCROLLRANGE to QsciScintillaBase. + - Added SCI_SETCARETLINEVISIBLEALWAYS and SCI_GETCARETLINEVISIBLEALWAYS to +QsciScintillaBase. + - Added SCI_SETMOUSESELECTIONRECTANGULARSWITCH and +SCI_GETMOUSESELECTIONRECTANGULARSWITCH to QsciScintillaBase. + - Added SCI_SETREPRESENTATION, SCI_GETREPRESENTATION and +SCI_CLEARREPRESENTATION to QsciScintillaBase. + - Input methods are now properly supported. + +--- --- /work/SRC/openSUSE:Factory/qscintilla/python3-qscintilla.changes 2013-04-16 06:56:43.0 +0200 +++ /work/SRC/openSUSE:Factory/.qscintilla.new/python3-qscintilla.changes 2013-11-15 13:32:13.0 +0100 @@ -1,0 +2,34 @@ +Thu Nov 14 02:15:52 UTC 2013 - ter...@gmail.com + +- update to v2.8: + - Based on Scintilla v3.3.6. + - Added the SCN_FOCUSIN() and SCN_FOCUSOUT() signals to QsciScintillaBase. + - Added PreProcessorCommentLineDoc and InactivePreProcessorCommentLineDoc to +QsciLexerCPP. + - Added SCLEX_LITERATEHASKELL, SCLEX_KVIRC, SCLEX_RUST and SCLEX_STTXT to +QsciScintillaBase. + - Added ThickCompositionIndicator to QsciScintilla::IndicatorStyle. + - Added INDIC_COMPOSITIONTHICK to QsciScintillaBase. + - Added SC_FOLDACTION_CONTRACT, SC_FOLDACTION_EXPAND and SC_FOLDACTION_TOGGLE +to QsciScintillaBase. + - Added SCI_FOLDLINE, SCI_FOLDCHILDREN, SCI_EXPANDCHILDREN and SCI_FOLDALL to +QsciScintillaBase. + - Added SC_AUTOMATICFOLD_SHOW, SC_AUTOMATICFOLD_CLICK and +SC_AUTOMATICFOLD_CHANGE to QsciScintillaBase. + - Added SCI_SETAUTOMATICFOLD and SCI_GETAUTOMATICFOLD to QsciScintillaBase. + - Added SC_ORDER_PRESORTED, SC_ORDER_PERFORMSORT and SC_ORDER_CUSTOM to +QsciScintillaBase. + - Added SCI_AUTOCSETORDER and SCI_AUTOCGETORDER to QsciScintillaBase. + - Added SCI_POSITIONRELATIVE to QsciScintillaBase. + - Added SCI_RELEASEALLEXTENDEDSTYLES and SCI_ALLOCATEEXTENDEDSTYLES to +QsciScintillaBase. + - Added SCI_SCROLLRANGE to QsciScintillaBase. + - Added SCI_SETCARETLINEVISIBLEALWAYS and SCI_GETCARETLINEVISIBLEALWAYS to +QsciScintillaBase. + - Added SCI_SETMOUSESELECTIONRECTANGULARSWITCH and +SCI_GETMOUSESELECTIONRECTANGULARSWITCH to QsciScintillaBase. + - Added SCI_SETREPRESENTATION, SCI_GETREPRESENTATION and +SCI_CLEARREPRESENTATION to QsciScintillaBase. + - Input methods are now properly supported. + +--- --- /work/SRC/openSUSE:Factory/qscintilla/qscintilla.changes2013-06-28 18:57:06.0 +0200 +++ /work/SRC/openSUSE:Factory/.qscintilla.new/qscintilla.changes 2013-11-15 13:32:13.0 +0100 @@ -1,0 +2,34 @@ +Thu Nov 14 02:13:30 UTC 2013 - ter...@gmail.com + +- update to v2.8: + - Based on Scintilla v3.3.6. + - Added the SCN_FOCUSIN() and SCN_FOCUSOUT() signals to QsciScintillaBase. + - Added PreProcessorCommentLineDoc and InactivePreProcessorCommentLineDoc to +QsciLexerCPP. + - Added SCLEX_LITERATEHASKELL, SCLEX_KVIRC, SCLEX_RUST and SCLEX_STTXT to +QsciScintillaBase. + -
commit rsyslog for openSUSE:Factory
Hello community,
here is the log from the commit of package rsyslog for openSUSE:Factory checked
in at 2013-11-15 13:37:27
Comparing /work/SRC/openSUSE:Factory/rsyslog (Old)
and /work/SRC/openSUSE:Factory/.rsyslog.new (New)
Package is rsyslog
Changes:
--- /work/SRC/openSUSE:Factory/rsyslog/rsyslog.changes 2013-11-06
11:02:20.0 +0100
+++ /work/SRC/openSUSE:Factory/.rsyslog.new/rsyslog.changes 2013-11-15
13:37:28.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 6 09:07:10 UTC 2013 - m...@suse.de
+
+- Fixed to avoid rebuild rscryutil.1 rsgtutil.1 on SLE-11.
+
+---
Other differences:
--
++ rsyslog.spec ++
--- /var/tmp/diff_new_pack.Q09zaA/_old 2013-11-15 13:37:29.0 +0100
+++ /var/tmp/diff_new_pack.Q09zaA/_new 2013-11-15 13:37:29.0 +0100
@@ -580,7 +580,11 @@
%endif
--enable-usertools \
--disable-static
-
+#
+%if ! %{with rst2man}
+ touch tools/{rscryutil.1,rsgtutil.1}
+%endif
+#
make %{?_smp_mflags:%{_smp_mflags}} V=1
%install
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit samba for openSUSE:Factory
Hello community,
here is the log from the commit of package samba for openSUSE:Factory checked
in at 2013-11-15 13:38:48
Comparing /work/SRC/openSUSE:Factory/samba (Old)
and /work/SRC/openSUSE:Factory/.samba.new (New)
Package is samba
Changes:
--- /work/SRC/openSUSE:Factory/samba/samba.changes 2013-10-17
17:47:39.0 +0200
+++ /work/SRC/openSUSE:Factory/.samba.new/samba.changes 2013-11-15
13:38:50.0 +0100
@@ -1,0 +2,19 @@
+Wed Nov 13 15:16:03 UTC 2013 - lmue...@suse.com
+
+- Update to 4.1.1.
+ + ACLs are not checked on opening an alternate data stream on a file or
+directory; CVE-2013-4475; (bso#10229); (bnc#848101).
+ + Private key in key.pem world readable; CVE-2013-4476; (bnc#848103).
+
+---
+Sun Nov 10 18:16:56 UTC 2013 - lmue...@suse.com
+
+- Private key in key.pem world readable; CVE-2013-4476; (bnc#848103).
+
+---
+Wed Oct 30 14:11:42 UTC 2013 - lmue...@suse.com
+
+- ACLs are not checked on opening an alternate data stream on a file or
+ directory; CVE-2013-4475; (bso#10229); (bnc#848101).
+
+---
Old:
samba-4.1.0.tar.asc
samba-4.1.0.tar.gz
New:
samba-4.1.1.tar.asc
samba-4.1.1.tar.gz
Other differences:
--
++ samba.spec ++
--- /var/tmp/diff_new_pack.v8ROwh/_old 2013-11-15 13:38:51.0 +0100
+++ /var/tmp/diff_new_pack.v8ROwh/_new 2013-11-15 13:38:51.0 +0100
@@ -108,7 +108,7 @@
%if %suse_version 1220
BuildRequires: gpg-offline
%endif
-%definesamba_ver 4.1.0
+%definesamba_ver 4.1.1
%definesamba_ver_suffix %nil
%if %{samba_ver_suffix} ==
%define samba_source_location
http://ftp.samba.org/pub/samba/stable/samba-%{version}.tar.gz
@@ -135,12 +135,12 @@
%else
%definebuild_make_smp_mflags %{?jobs:-j%jobs}
%endif
-%define SOURCE_TIMESTAMP 3087
+%define SOURCE_TIMESTAMP 3109
%define BRANCH %{version}
%global with_mitkrb5 1
%global with_dc 0
%global with_get_printing_ticket 0
-Version:4.1.0
+Version:4.1.1
Release:0
License:GPL-3.0+
Url:http://www.samba.org/
++ patches.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/patches/suse/passdb_backend_defaults_smbpasswd.diff
new/patches/suse/passdb_backend_defaults_smbpasswd.diff
--- old/patches/suse/passdb_backend_defaults_smbpasswd.diff 2013-07-17
19:13:46.0 +0200
+++ new/patches/suse/passdb_backend_defaults_smbpasswd.diff 2013-11-10
19:19:51.0 +0100
@@ -8,7 +8,7 @@
===
--- source3/param/loadparm.c
+++ source3/param/loadparm.c
-@@ -898,7 +898,7 @@ static void init_globals(bool reinit_glo
+@@ -901,7 +901,7 @@ static void init_globals(bool reinit_glo
a large number of sites (tridge) */
Globals.bHostnameLookups = false;
++ samba-4.1.0.tar.gz - samba-4.1.1.tar.gz ++
/work/SRC/openSUSE:Factory/samba/samba-4.1.0.tar.gz
/work/SRC/openSUSE:Factory/.samba.new/samba-4.1.1.tar.gz differ: char 5, line 1
++ vendor-files.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/vendor-files/tools/package-data
new/vendor-files/tools/package-data
--- old/vendor-files/tools/package-data 2013-10-11 11:13:45.0 +0200
+++ new/vendor-files/tools/package-data 2013-11-13 16:24:34.0 +0100
@@ -1,2 +1,2 @@
# This is an autogenrated file.
-SAMBA_PACKAGE_SVN_VERSION=3087
+SAMBA_PACKAGE_SVN_VERSION=3109
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit vim for openSUSE:Factory
Hello community,
here is the log from the commit of package vim for openSUSE:Factory checked in
at 2013-11-15 13:39:31
Comparing /work/SRC/openSUSE:Factory/vim (Old)
and /work/SRC/openSUSE:Factory/.vim.new (New)
Package is vim
Changes:
--- /work/SRC/openSUSE:Factory/vim/vim.changes 2013-10-31 10:12:23.0
+0100
+++ /work/SRC/openSUSE:Factory/.vim.new/vim.changes 2013-11-15
13:39:32.0 +0100
@@ -1,0 +2,31 @@
+Thu Nov 14 09:27:18 UTC 2013 - idon...@suse.com
+
+- Updated to revision 092, fixes the following problems
+ * Reading past end of the 'stl' string.
+ * byteidx() does not work for composing characters.
+ * set_last_cursor() may encounter w_buffer being NULL. (Matt Mkaniaris)
+ * Declaration has wrong return type for PyObject_SetAttrString().
+ * Crash when using invalid key in Python dictionary.
+ * When replacing a character in Visual block mode, entering a CR does not
cause a repeated line break.
+ * When recording, the character typed at the hit-enter prompt is recorded
twice. (Urtica Dioica)
+ * After inserting comment leader, CTRL-\ CTRL-O does move the cursor.
(Wiktor Ruben)
+ * Cannot right shift lines starting with #.
+ * Passing limits around too often.
+ * Crash when using Insert mode completion.
+ * Setting undolevels for one buffer changes undo in another.
+ * When undo'ing all changes and creating a new change the undo structure is
incorrect. (Christian Brabandt)
+ * Locally setting 'undolevels' is not tested.
+ * cgn does not wrap around the end of the file. (Dimitrov Dimitrov)
+ * A script cannot detect whether 'hlsearch' highlighting is actually
displayed.
+ * Missing documentation for v:hlsearch.
+ * Wrong logic when ANALYZE is yes.
+ * Using gf in a changed buffer suggests adding !, which is not possible.
(Tim Chase)
+ * It's hard to avoid adding a used pattern to the search history.
+ * Python: interrupt not being properly discarded. (Yggdroot Chen)
+ * When inserting text in Visual block mode and moving the cursor the wrong
text gets repeated in other lines.
+ * Skipping over an expression when not evaluating it does not work properly
for dict members.
+ * When spell checking is enabled Asian characters are always marked as error.
+ * When editing a file in a directory mounted through sshfs Vim doesn't set
the security context on a renamed file.
+- Drop vim-7.4-python-decl.patch, patch upstream now.
+
+---
Old:
vim-7.4-python-decl.patch
Other differences:
--
++ vim.spec ++
--- /var/tmp/diff_new_pack.69cAyx/_old 2013-11-15 13:39:33.0 +0100
+++ /var/tmp/diff_new_pack.69cAyx/_new 2013-11-15 13:39:33.0 +0100
@@ -17,7 +17,7 @@
%define pkg_version 7.4
-%define official_ptchlvl 052
+%define official_ptchlvl 092
%define VIM_SUBDIR vim74
%define site_runtimepath /usr/share/vim/site
%define make make VIMRCLOC=/etc VIMRUNTIMEDIR=/usr/share/vim/current
MAKE=make -e %{?_smp_mflags}
@@ -102,7 +102,6 @@
Patch19:%{name}-7.3-diff_check.patch
Patch21:%{name}-7.3-filetype_changes.patch
Patch22:%{name}-7.4-filetype_mine.patch
-Patch23:%{name}-7.4-python-decl.patch
Patch100: vim-7.1.314-CVE-2009-0316-debian.patch
Patch101: vim73-no-static-libpython.patch
%{perl_requires}
@@ -191,7 +190,6 @@
%patch19 -p1
%patch21 -p1
%patch22 -p1
-%patch23 -p1
%patch100 -p1
%patch101
cp %{SOURCE3} %{SOURCE4} %{SOURCE5} %{SOURCE8} %{SOURCE10} .
++ vim-7.4-patches.tar.bz2 ++
9583 lines of diff (skipped)
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit tomcat for openSUSE:Factory
Hello community,
here is the log from the commit of package tomcat for openSUSE:Factory checked
in at 2013-11-15 13:39:07
Comparing /work/SRC/openSUSE:Factory/tomcat (Old)
and /work/SRC/openSUSE:Factory/.tomcat.new (New)
Package is tomcat
Changes:
--- /work/SRC/openSUSE:Factory/tomcat/tomcat.changes2013-09-11
17:11:47.0 +0200
+++ /work/SRC/openSUSE:Factory/.tomcat.new/tomcat.changes 2013-11-15
13:39:09.0 +0100
@@ -1,0 +2,14 @@
+Mon Nov 4 14:12:40 UTC 2013 - mvysko...@suse.com
+
+- Update to 4.0.47
+ * bugfix release
+ * backport of JSR-356 Java WebSocket 1.0
+ * package tomcat now requires java7 at lease
+- Updated tomcat.keyring to reflect the fact new release is signed by
+ Violeta Georgieva / D63011C7
+ see http://osdir.com/ml/dev-tomcat.apache.org/2013-10/msg00849.html
+- Add tomcat-dbcp.jar (bnc#847505) back into tomcat lib dir
+- Install tomcat-coyote.jar as well
+- Remove pointless scriplets
+
+---
Old:
apache-tomcat-7.0.42-src.tar.gz
apache-tomcat-7.0.42-src.tar.gz.asc
New:
apache-tomcat-7.0.47-src.tar.gz
apache-tomcat-7.0.47-src.tar.gz.asc
collections-tomcat-build.xml
dbcp-tomcat-build.xml
Other differences:
--
++ tomcat.spec ++
--- /var/tmp/diff_new_pack.zIiDJS/_old 2013-11-15 13:39:10.0 +0100
+++ /var/tmp/diff_new_pack.zIiDJS/_new 2013-11-15 13:39:10.0 +0100
@@ -26,7 +26,7 @@
%define major_version 7
%define minor_version 0
-%define micro_version 42
+%define micro_version 47
%define packdname apache-tomcat-%{version}-src
%define tcuid 91
@@ -70,6 +70,7 @@
Source16: tomcat-juli-OSGi-MANIFEST.MF
Source17: tomcat-7.0-tomcat-sysd
Source20: tomcat-7.0-jsvc.service
+Source30: dbcp-tomcat-build.xml
Source1000: tomcat-rpmlintrc
Source1001:
http://www.apache.org/dist/tomcat/tomcat-%{major_version}/v%{version}/src/%{packdname}.tar.gz.asc
Source1002: %{name}.keyring
@@ -95,9 +96,11 @@
BuildRequires: jakarta-commons-collections
BuildRequires: jakarta-commons-daemon
BuildRequires: jakarta-commons-dbcp
+BuildRequires: jakarta-commons-dbcp-src
BuildRequires: jakarta-commons-pool
+BuildRequires: jakarta-commons-pool-tomcat5
BuildRequires: jakarta-taglibs-standard = 1.1
-BuildRequires: java-devel = 1.6.0
+BuildRequires: java-devel = 1.7.0
BuildRequires: javapackages-tools
BuildRequires: javapackages-tools
BuildRequires: junit
@@ -217,10 +220,11 @@
Requires: %{name}-jsp-%{jspspec}-api = %{version}-%{release}
Requires: %{name}-servlet-%{servletspec}-api = %{version}-%{release}
Requires(post): ecj = 4.2.1
-#Requires(post): jakarta-commons-collections-tomcat5
-#$Requires(post): jakarta-commons-dbcp-tomcat5
-#Requires(post): jakarta-commons-pool-tomcat5
+#Requires(post): jakarta-commons-dbcp-tomcat5
+Requires(post): jakarta-commons-pool-tomcat5
Requires(preun):%{__rm}
+Provides: jakarta-commons-dbcp-tomcat5 = 1.4
+Obsoletes: jakarta-commons-dbcp-tomcat5 1.4
%description lib
Libraries needed to run the Tomcat Web container
@@ -251,8 +255,6 @@
%description webapps
The ROOT and examples web applications for Apache Tomcat
-
-
%prep
%if 0%{?suse_version} 1220
@@ -268,6 +270,18 @@
%patch2 -p1
%build
+#bnc847505: build all commons-dbcp-tomcat jars before tomcat
+# so we broke the build cycle between commons-dbcp and tomcat
+
+mkdir -p commons/dbcp
+pushd commons/dbcp
+cp %{SOURCE30} .
+mkdir src
+cp -r %{_usrsrc}/commons-dbcp/java src/
+export CLASSPATH=$(build-classpath commons-pool-tomcat5)
+ant -f dbcp-tomcat-build.xml
+popd
+
%{__ln_s} $(build-classpath jakarta-taglibs-core)
webapps/examples/WEB-INF/lib/jstl.jar
%{__ln_s} $(build-classpath jakarta-taglibs-standard)
webapps/examples/WEB-INF/lib/standard.jar
@@ -283,6 +297,7 @@
touch HACKDIR/build.xml
%{ant} -Dbase.path=. \
+-Djava.7.home=%{java_home} \
-Dbuild.compiler=modern \
-Dcommons-collections.jar=$(build-classpath commons-collections) \
-Dcommons-daemon.jar=$(build-classpath commons-daemon) \
@@ -301,12 +316,12 @@
-Dno.build.dbcp=true \
-Dversion=%{version} \
-Dversion.build=%{micro_version} \
-deploy dist-prepare dist-source javadoc
+deploy dist-prepare dist-source javadoc package-java7
# remove some jars that we'll replace with symlinks later
%{__rm} output/build/bin/commons-daemon.jar \
output/build/lib/ecj.jar \
-output/build/lib/commons-dbcp.jar
+output/build/lib/*commons-dbcp.jar
# remove the cruft we created
%{__rm} output/build/bin/tomcat-native.tar.gz
@@ -378,6 +393,8 @@
%{__cp} -a lib/*.jar %{buildroot}%{libdir}
%{__cp} -a webapps/*
commit tslib for openSUSE:Factory
Hello community,
here is the log from the commit of package tslib for openSUSE:Factory checked
in at 2013-11-15 13:39:21
Comparing /work/SRC/openSUSE:Factory/tslib (Old)
and /work/SRC/openSUSE:Factory/.tslib.new (New)
Package is tslib
Changes:
--- /work/SRC/openSUSE:Factory/tslib/tslib.changes 2013-08-12
14:28:27.0 +0200
+++ /work/SRC/openSUSE:Factory/.tslib.new/tslib.changes 2013-11-15
13:39:22.0 +0100
@@ -1,0 +2,8 @@
+Wed Nov 13 01:09:42 UTC 2013 - jeng...@inai.de
+
+- Fix insufficient description for libts-1_0-0
+- Set RPM groups; simpler make install line; remove redundant
+ %clean section
+- Own all created directories
+
+---
Other differences:
--
++ tslib.spec ++
--- /var/tmp/diff_new_pack.iseXMK/_old 2013-11-15 13:39:22.0 +0100
+++ /var/tmp/diff_new_pack.iseXMK/_new 2013-11-15 13:39:22.0 +0100
@@ -24,6 +24,8 @@
License:LGPL-2.0+ and GPL-2.0+
Group: Hardware/Other
Url:https://github.com/kergoth/tslib.git
+
+#Git-Clone:git://github.com/kergoth/tslib
Source: tslib-e2e03ef719.tar.gz
Source2:baselibs.conf
Patch0: use-module-raw-input-for-ts-conf.patch
@@ -35,30 +37,40 @@
%description
Tslib is an abstraction layer for touchscreen panel events.
+The idea of tslib is to have a core library and a set of plugins to
+manage the conversion and filtering as needed.
+
%package -n libts-1_0-0
-Summary:Tslib library itself
-Group: Development/Libraries/Other
+Summary:Abstraction layer for touchscreens
+Group: System/Libraries
%description -n libts-1_0-0
-Library package for Tslib.
+Tslib is an abstraction layer for touchscreen panel events.
+
+The idea of tslib is to have a core library and a set of plugins to
+manage the conversion and filtering as needed.
%package plugins
-Summary:Driver plugins for Tslib
-Group: Development/Libraries/Other
+Summary:Driver plugins for tslib, an abstraction layer for touchscreens
+Group: Hardware/Other
%description plugins
-Hardware driver plugins for Tslib.
+Tslib is an abstraction layer for touchscreen panel events.
+
+The idea of tslib is to have a core library and a set of plugins to
+manage the conversion and filtering as needed.
+
+This subpackage contains the hardware driver plugins for tslib.
%package devel
-Summary:Devel package for tslib
-Group: Development/Libraries/Other
+Summary:Development files for tslib, a touchscreen panel event layer
+Group: Development/Libraries/C and C++
Requires: %name = %version
Requires: %name-plugins = %version
%description devel
Devel package for tslib. Tslib is an abstraction layer for touchscreen panel
events.
-
%prep
%setup -q -n tslib-e2e03ef719
%patch0 -p0
@@ -69,7 +81,7 @@
make
%install
-%{?make_install} %{!?make_install:make install DESTDIR=$RPM_BUILD_ROOT}
+make install DESTDIR=%buildroot
rm %{buildroot}%{_libdir}/pkgconfig/tslib-1.0.pc
ln -s tslib.pc %{buildroot}%{_libdir}/pkgconfig/tslib-1.0.pc
@@ -77,16 +89,14 @@
%postun -n libts-1_0-0 -p /sbin/ldconfig
-%clean
-rm -rf %buildroot
-
%files devel
%defattr(-,root,root)
%dir %{_libdir}/ts
-/usr/include/tslib.h
+%_includedir/tslib.h
%{_libdir}/libts.la
%{_libdir}/pkgconfig/tslib-1.0.pc
%{_libdir}/pkgconfig/tslib.pc
+%dir %_libdir/ts
%{_libdir}/ts/*.la
%{_libdir}/libts.so
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit yast2-firewall for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-firewall for openSUSE:Factory
checked in at 2013-11-15 13:39:48
Comparing /work/SRC/openSUSE:Factory/yast2-firewall (Old)
and /work/SRC/openSUSE:Factory/.yast2-firewall.new (New)
Package is yast2-firewall
Changes:
--- /work/SRC/openSUSE:Factory/yast2-firewall/yast2-firewall.changes
2013-10-11 11:06:39.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-firewall.new/yast2-firewall.changes
2013-11-15 13:39:49.0 +0100
@@ -1,0 +2,8 @@
+Thu Nov 7 21:01:38 UTC 2013 - mfi...@suse.com
+
+- bnc#843646
+ - fixed second stage proposal to reflect changes done during
+first stage
+- 3.1.1
+
+---
Old:
yast2-firewall-3.1.0.tar.bz2
New:
yast2-firewall-3.1.1.tar.bz2
Other differences:
--
++ yast2-firewall.spec ++
--- /var/tmp/diff_new_pack.SBsllb/_old 2013-11-15 13:39:50.0 +0100
+++ /var/tmp/diff_new_pack.SBsllb/_new 2013-11-15 13:39:50.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-firewall
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-firewall-3.1.0.tar.bz2 - yast2-firewall-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-firewall-3.1.0/CONTRIBUTING.md
new/yast2-firewall-3.1.1/CONTRIBUTING.md
--- old/yast2-firewall-3.1.0/CONTRIBUTING.md1970-01-01 01:00:00.0
+0100
+++ new/yast2-firewall-3.1.1/CONTRIBUTING.md2013-11-15 09:21:40.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
commit yast2-lxc for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-lxc for openSUSE:Factory
checked in at 2013-11-15 13:40:16
Comparing /work/SRC/openSUSE:Factory/yast2-lxc (Old)
and /work/SRC/openSUSE:Factory/.yast2-lxc.new (New)
Package is yast2-lxc
Changes:
--- /work/SRC/openSUSE:Factory/yast2-lxc/yast2-lxc.changes 2013-10-11
11:07:45.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-lxc.new/yast2-lxc.changes 2013-11-15
13:40:16.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-lxc-3.1.0.tar.bz2
New:
yast2-lxc-3.1.1.tar.bz2
Other differences:
--
++ yast2-lxc.spec ++
--- /var/tmp/diff_new_pack.MeOQr1/_old 2013-11-15 13:40:18.0 +0100
+++ /var/tmp/diff_new_pack.MeOQr1/_new 2013-11-15 13:40:18.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-lxc
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-lxc-3.1.0.tar.bz2 - yast2-lxc-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-lxc-3.1.0/CONTRIBUTING.md
new/yast2-lxc-3.1.1/CONTRIBUTING.md
--- old/yast2-lxc-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0 +0100
+++ new/yast2-lxc-3.1.1/CONTRIBUTING.md 2013-11-15 09:08:38.0 +0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
+autolinking](https://help.github.com/articles/github-flavored-markdown#references)
+and [openSUSE abbreviation
commit yast2-network for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-network for openSUSE:Factory
checked in at 2013-11-15 13:42:08
Comparing /work/SRC/openSUSE:Factory/yast2-network (Old)
and /work/SRC/openSUSE:Factory/.yast2-network.new (New)
Package is yast2-network
Changes:
--- /work/SRC/openSUSE:Factory/yast2-network/yast2-network.changes
2013-11-07 09:15:28.0 +0100
+++ /work/SRC/openSUSE:Factory/.yast2-network.new/yast2-network.changes
2013-11-15 13:42:09.0 +0100
@@ -1,0 +2,7 @@
+Thu Nov 7 20:53:56 UTC 2013 - mfi...@suse.com
+
+- bnc#843646
+ - firewall can be enabled/disabled during installation
+- 3.1.5
+
+---
Old:
yast2-network-3.1.4.tar.bz2
New:
yast2-network-3.1.5.tar.bz2
Other differences:
--
++ yast2-network.spec ++
--- /var/tmp/diff_new_pack.nsorUX/_old 2013-11-15 13:42:10.0 +0100
+++ /var/tmp/diff_new_pack.nsorUX/_new 2013-11-15 13:42:10.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-network
-Version:3.1.4
+Version:3.1.5
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-network-3.1.4.tar.bz2 - yast2-network-3.1.5.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-network-3.1.4/VERSION
new/yast2-network-3.1.5/VERSION
--- old/yast2-network-3.1.4/VERSION 2013-11-04 16:42:19.0 +0100
+++ new/yast2-network-3.1.5/VERSION 2013-11-15 09:19:29.0 +0100
@@ -1 +1 @@
-3.1.4
+3.1.5
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-network-3.1.4/package/yast2-network.changes
new/yast2-network-3.1.5/package/yast2-network.changes
--- old/yast2-network-3.1.4/package/yast2-network.changes 2013-11-04
16:42:19.0 +0100
+++ new/yast2-network-3.1.5/package/yast2-network.changes 2013-11-15
09:19:29.0 +0100
@@ -1,9 +1,16 @@
---
+Thu Nov 7 20:53:56 UTC 2013 - mfi...@suse.com
+
+- bnc#843646
+ - firewall can be enabled/disabled during installation
+- 3.1.5
+
+---
Wed Oct 30 21:43:14 UTC 2013 - mfi...@suse.com
- bnc#847783
- do not offer ifplugd devices as bridge port candidate
-- 3.1.4
+- 3.1.4
---
Tue Oct 22 12:28:17 UTC 2013 - mfi...@suse.com
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-network-3.1.4/src/clients/firewall_stage1_finish.rb
new/yast2-network-3.1.5/src/clients/firewall_stage1_finish.rb
--- old/yast2-network-3.1.4/src/clients/firewall_stage1_finish.rb
2013-11-04 16:42:19.0 +0100
+++ new/yast2-network-3.1.5/src/clients/firewall_stage1_finish.rb
2013-11-15 09:19:29.0 +0100
@@ -66,9 +66,7 @@
title = _(
Writing Firewall Configuration...
),
- when = SuSEFirewallProposal.GetChangedByUser || @ssh_enabled ||
@vnc_enabled ?
-[:installation, :autoinst] :
-[]
+ when = [:installation, :autoinst]
}
elsif @func == Write
Builtins.y2milestone(
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-network-3.1.4/testsuite/tests/runtime.rb
new/yast2-network-3.1.5/testsuite/tests/runtime.rb
--- old/yast2-network-3.1.4/testsuite/tests/runtime.rb 2013-11-04
16:42:19.0 +0100
+++ new/yast2-network-3.1.5/testsuite/tests/runtime.rb 2013-11-15
09:19:29.0 +0100
@@ -82,7 +82,7 @@
TEST(lambda { RunSuSEconfig() }, [{}, {}, @EXEC1], nil)
Yast.import NetworkInterfaces
- NetworkInterfaces.Devices = { dsl = { 0 = {} } }
+ NetworkInterfaces.instance_variable_set(:@Devices, { dsl = { 0 =
{} } })
DUMP(SetupSMPPPD)
TEST(lambda { SetupSMPPPD(true) }, [@READ, {}, @EXEC0], nil)
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit yast2-ycp-ui-bindings for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-ycp-ui-bindings for
openSUSE:Factory checked in at 2013-11-15 13:43:57
Comparing /work/SRC/openSUSE:Factory/yast2-ycp-ui-bindings (Old)
and /work/SRC/openSUSE:Factory/.yast2-ycp-ui-bindings.new (New)
Package is yast2-ycp-ui-bindings
Changes:
---
/work/SRC/openSUSE:Factory/yast2-ycp-ui-bindings/yast2-ycp-ui-bindings.changes
2013-11-10 20:37:54.0 +0100
+++
/work/SRC/openSUSE:Factory/.yast2-ycp-ui-bindings.new/yast2-ycp-ui-bindings.changes
2013-11-15 13:43:58.0 +0100
@@ -1,0 +2,7 @@
+Thu Nov 14 13:21:26 CET 2013 - loci...@suse.com
+
+- Removed warning if checking for TextMode. It became a standard
+ check so no warning is necessary anymore.
+- 3.1.2
+
+---
Old:
yast2-ycp-ui-bindings-3.1.1.tar.bz2
New:
yast2-ycp-ui-bindings-3.1.2.tar.bz2
Other differences:
--
++ yast2-ycp-ui-bindings.spec ++
--- /var/tmp/diff_new_pack.evKe13/_old 2013-11-15 13:43:58.0 +0100
+++ /var/tmp/diff_new_pack.evKe13/_new 2013-11-15 13:43:58.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-ycp-ui-bindings
-Version:3.1.1
+Version:3.1.2
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-ycp-ui-bindings-3.1.1.tar.bz2 -
yast2-ycp-ui-bindings-3.1.2.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-ycp-ui-bindings-3.1.1/VERSION
new/yast2-ycp-ui-bindings-3.1.2/VERSION
--- old/yast2-ycp-ui-bindings-3.1.1/VERSION 2013-11-08 11:32:47.0
+0100
+++ new/yast2-ycp-ui-bindings-3.1.2/VERSION 2013-11-15 09:15:41.0
+0100
@@ -1 +1 @@
-3.1.1
+3.1.2
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-ycp-ui-bindings-3.1.1/package/yast2-ycp-ui-bindings.changes
new/yast2-ycp-ui-bindings-3.1.2/package/yast2-ycp-ui-bindings.changes
--- old/yast2-ycp-ui-bindings-3.1.1/package/yast2-ycp-ui-bindings.changes
2013-11-08 11:32:47.0 +0100
+++ new/yast2-ycp-ui-bindings-3.1.2/package/yast2-ycp-ui-bindings.changes
2013-11-15 09:15:41.0 +0100
@@ -1,4 +1,11 @@
---
+Thu Nov 14 13:21:26 CET 2013 - loci...@suse.com
+
+- Removed warning if checking for TextMode. It became a standard
+ check so no warning is necessary anymore.
+- 3.1.2
+
+---
Mon Oct 14 14:47:09 UTC 2013 - jreidin...@suse.com
- Fix query for special widget DateField and TimeField resulting
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-ycp-ui-bindings-3.1.1/package/yast2-ycp-ui-bindings.spec
new/yast2-ycp-ui-bindings-3.1.2/package/yast2-ycp-ui-bindings.spec
--- old/yast2-ycp-ui-bindings-3.1.1/package/yast2-ycp-ui-bindings.spec
2013-11-08 11:32:47.0 +0100
+++ new/yast2-ycp-ui-bindings-3.1.2/package/yast2-ycp-ui-bindings.spec
2013-11-15 09:15:41.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-ycp-ui-bindings
-Version:3.1.1
+Version:3.1.2
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-ycp-ui-bindings-3.1.1/source/YCP_UI.cc
new/yast2-ycp-ui-bindings-3.1.2/source/YCP_UI.cc
--- old/yast2-ycp-ui-bindings-3.1.1/source/YCP_UI.cc2013-11-08
11:32:47.0 +0100
+++ new/yast2-ycp-ui-bindings-3.1.2/source/YCP_UI.cc2013-11-15
09:15:41.0 +0100
@@ -1016,8 +1016,6 @@
YCPBoolean YCP_UI::TextMode()
{
-ycpwarning( UI::TextMode(): Please check if this is really necessary! );
-
return YCPBoolean( YUI::app()-isTextMode() );
}
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit yast2-control-center-gnome for openSUSE:Factory
Hello community, here is the log from the commit of package yast2-control-center-gnome for openSUSE:Factory checked in at 2013-11-15 14:23:59 Comparing /work/SRC/openSUSE:Factory/yast2-control-center-gnome (Old) and /work/SRC/openSUSE:Factory/.yast2-control-center-gnome.new (New) Package is yast2-control-center-gnome Changes: --- /work/SRC/openSUSE:Factory/yast2-control-center-gnome/yast2-control-center-gnome.changes 2013-10-11 09:05:31.0 +0200 +++ /work/SRC/openSUSE:Factory/.yast2-control-center-gnome.new/yast2-control-center-gnome.changes 2013-11-15 14:24:01.0 +0100 @@ -1,0 +2,5 @@ +Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com + +- Add explicit COPYING file + +--- Old: yast2-control-center-gnome-3.1.0.tar.bz2 New: yast2-control-center-gnome-3.1.1.tar.bz2 Other differences: -- ++ yast2-control-center-gnome.spec ++ --- /var/tmp/diff_new_pack.G4aIQD/_old 2013-11-15 14:24:02.0 +0100 +++ /var/tmp/diff_new_pack.G4aIQD/_new 2013-11-15 14:24:02.0 +0100 @@ -17,7 +17,7 @@ Name: yast2-control-center-gnome -Version:3.1.0 +Version:3.1.1 Release:0 Summary:YaST2 - Control Center (GNOME version) ++ yast2-control-center-gnome-3.1.0.tar.bz2 - yast2-control-center-gnome-3.1.1.tar.bz2 ++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-control-center-gnome-3.1.0/CONTRIBUTING.md new/yast2-control-center-gnome-3.1.1/CONTRIBUTING.md --- old/yast2-control-center-gnome-3.1.0/CONTRIBUTING.md1970-01-01 01:00:00.0 +0100 +++ new/yast2-control-center-gnome-3.1.1/CONTRIBUTING.md2013-11-04 16:29:52.0 +0100 @@ -0,0 +1,87 @@ +YaST Contribution Guidelines + + +YaST is an open source project and as such it welcomes all kinds of +contributions. If you decide to contribute, please follow these guidelines to +ensure the process is effective and pleasant both for you and YaST maintainers. + +There are two main forms of contribution: reporting bugs and performing code +changes. + +Bug Reports +--- + +If you find a problem, please report it either using +[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2) +or [GitHub issues](../../issues). (For Bugzilla, use the [simplified +registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp) +if you don't have an account yet.) + +If you find a problem, please report it either using +[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee +that every bug will be fixed, but we'll try. + +When creating a bug report, please follow our [bug reporting +guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug). + +Code Changes + + +We welcome all kinds of code contributions, from simple bug fixes to significant +refactorings and implementation of new features. However, before making any +non-trivial contribution, get in touch with us first — this can prevent wasted +effort on both sides. Also, have a look at our [development +documentation](http://en.opensuse.org/openSUSE:YaST_development). + +To send us your code change, use GitHub pull requests. The workflow is as +follows: + + 1. Fork the project. + + 2. Create a topic branch based on `master`. + + 3. Implement your change, including tests (if possible). Make sure you adhere + to the [Ruby style + guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md). + + 4. Make sure your change didn't break anything by building the RPM package + (`rake osc:build`). The build process includes running the full testsuite. + + 5. Publish the branch and create a pull request. + + 6. YaST developers will review your change and possibly point out issues. + Adapt the code under their guidance until they are all resolved. + + 7. Finally, the pull request will get merged or rejected. + +See also [GitHub's guide on +contributing](https://help.github.com/articles/fork-a-repo). + +If you want to do multiple unrelated changes, use separate branches and pull +requests. + +Do not change the `VERSION` and `*.changes` files as this could lead to +conflicts. + +### Commits + +Each commit in the pull request should do only one thing, which is clearly +described by its commit message. Especially avoid mixing formatting changes and +functional changes into one commit. When writing commit messages, adhere to +[widely used +conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). + +If your commit is related to a bug in Buzgilla or an issue on GitHub,
commit yast2-add-on for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-add-on for openSUSE:Factory
checked in at 2013-11-15 14:23:54
Comparing /work/SRC/openSUSE:Factory/yast2-add-on (Old)
and /work/SRC/openSUSE:Factory/.yast2-add-on.new (New)
Package is yast2-add-on
Changes:
--- /work/SRC/openSUSE:Factory/yast2-add-on/yast2-add-on.changes
2013-10-06 19:37:31.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-add-on.new/yast2-add-on.changes
2013-11-15 14:23:54.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-add-on-3.1.0.tar.bz2
New:
yast2-add-on-3.1.1.tar.bz2
Other differences:
--
++ yast2-add-on.spec ++
--- /var/tmp/diff_new_pack.fSCcI1/_old 2013-11-15 14:23:55.0 +0100
+++ /var/tmp/diff_new_pack.fSCcI1/_new 2013-11-15 14:23:55.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-add-on
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
@@ -89,7 +89,6 @@
%{yast_desktopdir}/*.desktop
%{yast_schemadir}/autoyast/rnc/add-on.rnc
%dir %{yast_docdir}
-%doc %{yast_docdir}/README
%doc %{yast_docdir}/COPYING
%files devel-doc
++ yast2-add-on-3.1.0.tar.bz2 - yast2-add-on-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-add-on-3.1.0/CONTRIBUTING.md
new/yast2-add-on-3.1.1/CONTRIBUTING.md
--- old/yast2-add-on-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-add-on-3.1.1/CONTRIBUTING.md 2013-11-04 16:29:29.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use
commit yast2-ca-management for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-ca-management for
openSUSE:Factory checked in at 2013-11-15 14:23:57
Comparing /work/SRC/openSUSE:Factory/yast2-ca-management (Old)
and /work/SRC/openSUSE:Factory/.yast2-ca-management.new (New)
Package is yast2-ca-management
Changes:
--- /work/SRC/openSUSE:Factory/yast2-ca-management/yast2-ca-management.changes
2013-10-11 11:06:04.0 +0200
+++
/work/SRC/openSUSE:Factory/.yast2-ca-management.new/yast2-ca-management.changes
2013-11-15 14:23:58.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-ca-management-3.1.0.tar.bz2
New:
yast2-ca-management-3.1.1.tar.bz2
Other differences:
--
++ yast2-ca-management.spec ++
--- /var/tmp/diff_new_pack.6AbqPI/_old 2013-11-15 14:23:59.0 +0100
+++ /var/tmp/diff_new_pack.6AbqPI/_new 2013-11-15 14:23:59.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-ca-management
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-ca-management-3.1.0.tar.bz2 - yast2-ca-management-3.1.1.tar.bz2
++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-ca-management-3.1.0/CONTRIBUTING.md
new/yast2-ca-management-3.1.1/CONTRIBUTING.md
--- old/yast2-ca-management-3.1.0/CONTRIBUTING.md 1970-01-01
01:00:00.0 +0100
+++ new/yast2-ca-management-3.1.1/CONTRIBUTING.md 2013-11-15
12:55:36.0 +0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also
commit yast2-dns-server for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-dns-server for
openSUSE:Factory checked in at 2013-11-15 14:24:11
Comparing /work/SRC/openSUSE:Factory/yast2-dns-server (Old)
and /work/SRC/openSUSE:Factory/.yast2-dns-server.new (New)
Package is yast2-dns-server
Changes:
--- /work/SRC/openSUSE:Factory/yast2-dns-server/yast2-dns-server.changes
2013-10-11 11:06:34.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-dns-server.new/yast2-dns-server.changes
2013-11-15 14:24:12.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-dns-server-3.1.0.tar.bz2
New:
yast2-dns-server-3.1.1.tar.bz2
Other differences:
--
++ yast2-dns-server.spec ++
--- /var/tmp/diff_new_pack.sqhPP9/_old 2013-11-15 14:24:13.0 +0100
+++ /var/tmp/diff_new_pack.sqhPP9/_new 2013-11-15 14:24:13.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-dns-server
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-dns-server-3.1.0.tar.bz2 - yast2-dns-server-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-dns-server-3.1.0/CONTRIBUTING.md
new/yast2-dns-server-3.1.1/CONTRIBUTING.md
--- old/yast2-dns-server-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-dns-server-3.1.1/CONTRIBUTING.md 2013-11-15 12:57:39.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
commit yast2-dbus-server for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-dbus-server for
openSUSE:Factory checked in at 2013-11-15 14:24:05
Comparing /work/SRC/openSUSE:Factory/yast2-dbus-server (Old)
and /work/SRC/openSUSE:Factory/.yast2-dbus-server.new (New)
Package is yast2-dbus-server
Changes:
--- /work/SRC/openSUSE:Factory/yast2-dbus-server/yast2-dbus-server.changes
2013-10-11 11:06:26.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-dbus-server.new/yast2-dbus-server.changes
2013-11-15 14:24:07.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-dbus-server-3.1.0.tar.bz2
New:
yast2-dbus-server-3.1.1.tar.bz2
Other differences:
--
++ yast2-dbus-server.spec ++
--- /var/tmp/diff_new_pack.7gFlK1/_old 2013-11-15 14:24:07.0 +0100
+++ /var/tmp/diff_new_pack.7gFlK1/_new 2013-11-15 14:24:07.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-dbus-server
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-dbus-server-3.1.0.tar.bz2 - yast2-dbus-server-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-dbus-server-3.1.0/CONTRIBUTING.md
new/yast2-dbus-server-3.1.1/CONTRIBUTING.md
--- old/yast2-dbus-server-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-dbus-server-3.1.1/CONTRIBUTING.md 2013-11-04 16:08:01.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
commit yast2-ftp-server for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-ftp-server for
openSUSE:Factory checked in at 2013-11-15 14:24:14
Comparing /work/SRC/openSUSE:Factory/yast2-ftp-server (Old)
and /work/SRC/openSUSE:Factory/.yast2-ftp-server.new (New)
Package is yast2-ftp-server
Changes:
--- /work/SRC/openSUSE:Factory/yast2-ftp-server/yast2-ftp-server.changes
2013-10-11 11:06:43.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-ftp-server.new/yast2-ftp-server.changes
2013-11-15 14:24:16.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-ftp-server-3.1.0.tar.bz2
New:
yast2-ftp-server-3.1.1.tar.bz2
Other differences:
--
++ yast2-ftp-server.spec ++
--- /var/tmp/diff_new_pack.AfeCCY/_old 2013-11-15 14:24:16.0 +0100
+++ /var/tmp/diff_new_pack.AfeCCY/_new 2013-11-15 14:24:16.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-ftp-server
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-ftp-server-3.1.0.tar.bz2 - yast2-ftp-server-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-ftp-server-3.1.0/CONTRIBUTING.md
new/yast2-ftp-server-3.1.1/CONTRIBUTING.md
--- old/yast2-ftp-server-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-ftp-server-3.1.1/CONTRIBUTING.md 2013-11-04 16:13:57.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
commit yast2-nfs-server for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-nfs-server for
openSUSE:Factory checked in at 2013-11-15 14:24:41
Comparing /work/SRC/openSUSE:Factory/yast2-nfs-server (Old)
and /work/SRC/openSUSE:Factory/.yast2-nfs-server.new (New)
Package is yast2-nfs-server
Changes:
--- /work/SRC/openSUSE:Factory/yast2-nfs-server/yast2-nfs-server.changes
2013-10-11 11:07:59.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-nfs-server.new/yast2-nfs-server.changes
2013-11-15 14:24:42.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-nfs-server-3.1.0.tar.bz2
New:
yast2-nfs-server-3.1.1.tar.bz2
Other differences:
--
++ yast2-nfs-server.spec ++
--- /var/tmp/diff_new_pack.SYaeON/_old 2013-11-15 14:24:43.0 +0100
+++ /var/tmp/diff_new_pack.SYaeON/_new 2013-11-15 14:24:43.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-nfs-server
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-nfs-server-3.1.0.tar.bz2 - yast2-nfs-server-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-nfs-server-3.1.0/CONTRIBUTING.md
new/yast2-nfs-server-3.1.1/CONTRIBUTING.md
--- old/yast2-nfs-server-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-nfs-server-3.1.1/CONTRIBUTING.md 2013-11-15 13:12:10.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
commit yast2-inetd for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-inetd for openSUSE:Factory
checked in at 2013-11-15 14:24:17
Comparing /work/SRC/openSUSE:Factory/yast2-inetd (Old)
and /work/SRC/openSUSE:Factory/.yast2-inetd.new (New)
Package is yast2-inetd
Changes:
--- /work/SRC/openSUSE:Factory/yast2-inetd/yast2-inetd.changes 2013-10-11
11:06:51.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-inetd.new/yast2-inetd.changes
2013-11-15 14:24:18.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-inetd-3.1.0.tar.bz2
New:
yast2-inetd-3.1.1.tar.bz2
Other differences:
--
++ yast2-inetd.spec ++
--- /var/tmp/diff_new_pack.PlgL20/_old 2013-11-15 14:24:19.0 +0100
+++ /var/tmp/diff_new_pack.PlgL20/_new 2013-11-15 14:24:19.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-inetd
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
@@ -76,7 +76,6 @@
%{yast_schemadir}/autoyast/rnc/inetd.rnc
%doc %dir %{yast_docdir}
%doc %{yast_docdir}/COPYING
-%readme %{yast_docdir}/README
%package doc
@@ -94,6 +93,5 @@
%defattr(-,root,root)
%doc %{yast_docdir}
%exclude %{yast_docdir}/COPYING
-%exclude %{yast_docdir}/README
%changelog
++ yast2-inetd-3.1.0.tar.bz2 - yast2-inetd-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-inetd-3.1.0/CONTRIBUTING.md
new/yast2-inetd-3.1.1/CONTRIBUTING.md
--- old/yast2-inetd-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-inetd-3.1.1/CONTRIBUTING.md 2013-11-15 12:59:46.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla
commit yast2-dhcp-server for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-dhcp-server for
openSUSE:Factory checked in at 2013-11-15 14:24:08
Comparing /work/SRC/openSUSE:Factory/yast2-dhcp-server (Old)
and /work/SRC/openSUSE:Factory/.yast2-dhcp-server.new (New)
Package is yast2-dhcp-server
Changes:
--- /work/SRC/openSUSE:Factory/yast2-dhcp-server/yast2-dhcp-server.changes
2013-10-11 11:06:31.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-dhcp-server.new/yast2-dhcp-server.changes
2013-11-15 14:24:10.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-dhcp-server-3.1.0.tar.bz2
New:
yast2-dhcp-server-3.1.1.tar.bz2
Other differences:
--
++ yast2-dhcp-server.spec ++
--- /var/tmp/diff_new_pack.AywjDq/_old 2013-11-15 14:24:11.0 +0100
+++ /var/tmp/diff_new_pack.AywjDq/_new 2013-11-15 14:24:11.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-dhcp-server
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-dhcp-server-3.1.0.tar.bz2 - yast2-dhcp-server-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-dhcp-server-3.1.0/CONTRIBUTING.md
new/yast2-dhcp-server-3.1.1/CONTRIBUTING.md
--- old/yast2-dhcp-server-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-dhcp-server-3.1.1/CONTRIBUTING.md 2013-11-15 12:54:37.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
commit yast2-online-update-configuration for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-online-update-configuration
for openSUSE:Factory checked in at 2013-11-15 14:25:02
Comparing /work/SRC/openSUSE:Factory/yast2-online-update-configuration (Old)
and /work/SRC/openSUSE:Factory/.yast2-online-update-configuration.new
(New)
Package is yast2-online-update-configuration
Changes:
---
/work/SRC/openSUSE:Factory/yast2-online-update-configuration/yast2-online-update-configuration.changes
2013-10-11 11:08:23.0 +0200
+++
/work/SRC/openSUSE:Factory/.yast2-online-update-configuration.new/yast2-online-update-configuration.changes
2013-11-15 14:25:03.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-online-update-configuration-3.1.0.tar.bz2
New:
yast2-online-update-configuration-3.1.1.tar.bz2
Other differences:
--
++ yast2-online-update-configuration.spec ++
--- /var/tmp/diff_new_pack.JWqJyw/_old 2013-11-15 14:25:04.0 +0100
+++ /var/tmp/diff_new_pack.JWqJyw/_new 2013-11-15 14:25:04.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-online-update-configuration
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-online-update-configuration-3.1.0.tar.bz2 -
yast2-online-update-configuration-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/yast2-online-update-configuration-3.1.0/CONTRIBUTING.md
new/yast2-online-update-configuration-3.1.1/CONTRIBUTING.md
--- old/yast2-online-update-configuration-3.1.0/CONTRIBUTING.md 1970-01-01
01:00:00.0 +0100
+++ new/yast2-online-update-configuration-3.1.1/CONTRIBUTING.md 2013-11-15
13:11:43.0 +0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
commit yast2-isns for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-isns for openSUSE:Factory
checked in at 2013-11-15 14:24:33
Comparing /work/SRC/openSUSE:Factory/yast2-isns (Old)
and /work/SRC/openSUSE:Factory/.yast2-isns.new (New)
Package is yast2-isns
Changes:
--- /work/SRC/openSUSE:Factory/yast2-isns/yast2-isns.changes2013-10-11
11:07:18.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-isns.new/yast2-isns.changes
2013-11-15 14:24:34.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-isns-3.1.0.tar.bz2
New:
yast2-isns-3.1.1.tar.bz2
Other differences:
--
++ yast2-isns.spec ++
--- /var/tmp/diff_new_pack.bcDXPd/_old 2013-11-15 14:24:35.0 +0100
+++ /var/tmp/diff_new_pack.bcDXPd/_new 2013-11-15 14:24:35.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-isns
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-isns-3.1.0.tar.bz2 - yast2-isns-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-isns-3.1.0/CONTRIBUTING.md
new/yast2-isns-3.1.1/CONTRIBUTING.md
--- old/yast2-isns-3.1.0/CONTRIBUTING.md1970-01-01 01:00:00.0
+0100
+++ new/yast2-isns-3.1.1/CONTRIBUTING.md2013-11-04 16:38:52.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
+autolinking](https://help.github.com/articles/github-flavored-markdown#references)
+and [openSUSE abbreviation
commit yast2-iscsi-server for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-iscsi-server for
openSUSE:Factory checked in at 2013-11-15 14:24:29
Comparing /work/SRC/openSUSE:Factory/yast2-iscsi-server (Old)
and /work/SRC/openSUSE:Factory/.yast2-iscsi-server.new (New)
Package is yast2-iscsi-server
Changes:
--- /work/SRC/openSUSE:Factory/yast2-iscsi-server/yast2-iscsi-server.changes
2013-10-11 11:07:02.0 +0200
+++
/work/SRC/openSUSE:Factory/.yast2-iscsi-server.new/yast2-iscsi-server.changes
2013-11-15 14:24:30.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-iscsi-server-3.1.0.tar.bz2
New:
yast2-iscsi-server-3.1.1.tar.bz2
Other differences:
--
++ yast2-iscsi-server.spec ++
--- /var/tmp/diff_new_pack.qdcgls/_old 2013-11-15 14:24:31.0 +0100
+++ /var/tmp/diff_new_pack.qdcgls/_new 2013-11-15 14:24:31.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-iscsi-server
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-iscsi-server-3.1.0.tar.bz2 - yast2-iscsi-server-3.1.1.tar.bz2
++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-iscsi-server-3.1.0/CONTRIBUTING.md
new/yast2-iscsi-server-3.1.1/CONTRIBUTING.md
--- old/yast2-iscsi-server-3.1.0/CONTRIBUTING.md1970-01-01
01:00:00.0 +0100
+++ new/yast2-iscsi-server-3.1.1/CONTRIBUTING.md2013-11-04
16:13:19.0 +0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
commit yast2-proxy for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-proxy for openSUSE:Factory
checked in at 2013-11-15 14:25:08
Comparing /work/SRC/openSUSE:Factory/yast2-proxy (Old)
and /work/SRC/openSUSE:Factory/.yast2-proxy.new (New)
Package is yast2-proxy
Changes:
--- /work/SRC/openSUSE:Factory/yast2-proxy/yast2-proxy.changes 2013-10-19
11:20:59.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-proxy.new/yast2-proxy.changes
2013-11-15 14:25:09.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-proxy-3.1.0.tar.bz2
New:
yast2-proxy-3.1.1.tar.bz2
Other differences:
--
++ yast2-proxy.spec ++
--- /var/tmp/diff_new_pack.FgqarN/_old 2013-11-15 14:25:09.0 +0100
+++ /var/tmp/diff_new_pack.FgqarN/_new 2013-11-15 14:25:09.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-proxy
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-proxy-3.1.0.tar.bz2 - yast2-proxy-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-proxy-3.1.0/CONTRIBUTING.md
new/yast2-proxy-3.1.1/CONTRIBUTING.md
--- old/yast2-proxy-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-proxy-3.1.1/CONTRIBUTING.md 2013-11-04 16:37:30.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
+autolinking](https://help.github.com/articles/github-flavored-markdown#references)
+and [openSUSE abbreviation
commit yast2-online-update for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-online-update for
openSUSE:Factory checked in at 2013-11-15 14:24:51
Comparing /work/SRC/openSUSE:Factory/yast2-online-update (Old)
and /work/SRC/openSUSE:Factory/.yast2-online-update.new (New)
Package is yast2-online-update
Changes:
--- /work/SRC/openSUSE:Factory/yast2-online-update/yast2-online-update.changes
2013-10-11 11:08:16.0 +0200
+++
/work/SRC/openSUSE:Factory/.yast2-online-update.new/yast2-online-update.changes
2013-11-15 14:24:52.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-online-update-3.1.0.tar.bz2
New:
yast2-online-update-3.1.1.tar.bz2
Other differences:
--
++ yast2-online-update.spec ++
--- /var/tmp/diff_new_pack.N8Apo8/_old 2013-11-15 14:24:53.0 +0100
+++ /var/tmp/diff_new_pack.N8Apo8/_new 2013-11-15 14:24:53.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-online-update
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-online-update-3.1.0.tar.bz2 - yast2-online-update-3.1.1.tar.bz2
++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-online-update-3.1.0/CONTRIBUTING.md
new/yast2-online-update-3.1.1/CONTRIBUTING.md
--- old/yast2-online-update-3.1.0/CONTRIBUTING.md 1970-01-01
01:00:00.0 +0100
+++ new/yast2-online-update-3.1.1/CONTRIBUTING.md 2013-11-15
13:10:25.0 +0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also
commit yast2-instserver for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-instserver for
openSUSE:Factory checked in at 2013-11-15 14:24:24
Comparing /work/SRC/openSUSE:Factory/yast2-instserver (Old)
and /work/SRC/openSUSE:Factory/.yast2-instserver.new (New)
Package is yast2-instserver
Changes:
--- /work/SRC/openSUSE:Factory/yast2-instserver/yast2-instserver.changes
2013-10-11 11:06:56.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-instserver.new/yast2-instserver.changes
2013-11-15 14:24:25.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-instserver-3.1.0.tar.bz2
New:
yast2-instserver-3.1.1.tar.bz2
Other differences:
--
++ yast2-instserver.spec ++
--- /var/tmp/diff_new_pack.nuuLIc/_old 2013-11-15 14:24:26.0 +0100
+++ /var/tmp/diff_new_pack.nuuLIc/_new 2013-11-15 14:24:26.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-instserver
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
@@ -77,7 +77,6 @@
%dir /etc/apache2
%dir /etc/apache2/conf.d
%dir %{yast_docdir}
-%doc %{yast_docdir}/README
%doc %{yast_docdir}/COPYING
%files devel-doc
++ yast2-instserver-3.1.0.tar.bz2 - yast2-instserver-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-instserver-3.1.0/CONTRIBUTING.md
new/yast2-instserver-3.1.1/CONTRIBUTING.md
--- old/yast2-instserver-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-instserver-3.1.1/CONTRIBUTING.md 2013-11-15 12:57:11.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the
commit yast2-live-installer for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-live-installer for
openSUSE:Factory checked in at 2013-11-15 14:24:38
Comparing /work/SRC/openSUSE:Factory/yast2-live-installer (Old)
and /work/SRC/openSUSE:Factory/.yast2-live-installer.new (New)
Package is yast2-live-installer
Changes:
---
/work/SRC/openSUSE:Factory/yast2-live-installer/yast2-live-installer.changes
2013-10-11 11:07:40.0 +0200
+++
/work/SRC/openSUSE:Factory/.yast2-live-installer.new/yast2-live-installer.changes
2013-11-15 14:24:40.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-live-installer-3.1.0.tar.bz2
New:
yast2-live-installer-3.1.1.tar.bz2
Other differences:
--
++ yast2-live-installer.spec ++
--- /var/tmp/diff_new_pack.J0mRMC/_old 2013-11-15 14:24:40.0 +0100
+++ /var/tmp/diff_new_pack.J0mRMC/_new 2013-11-15 14:24:40.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-live-installer
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-live-installer-3.1.0.tar.bz2 - yast2-live-installer-3.1.1.tar.bz2
++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-live-installer-3.1.0/CONTRIBUTING.md
new/yast2-live-installer-3.1.1/CONTRIBUTING.md
--- old/yast2-live-installer-3.1.0/CONTRIBUTING.md 1970-01-01
01:00:00.0 +0100
+++ new/yast2-live-installer-3.1.1/CONTRIBUTING.md 2013-11-15
13:07:57.0 +0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or
commit yast2-pam for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-pam for openSUSE:Factory
checked in at 2013-11-15 14:25:05
Comparing /work/SRC/openSUSE:Factory/yast2-pam (Old)
and /work/SRC/openSUSE:Factory/.yast2-pam.new (New)
Package is yast2-pam
Changes:
--- /work/SRC/openSUSE:Factory/yast2-pam/yast2-pam.changes 2013-10-11
11:08:37.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-pam.new/yast2-pam.changes 2013-11-15
14:25:07.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-pam-3.1.0.tar.bz2
New:
yast2-pam-3.1.1.tar.bz2
Other differences:
--
++ yast2-pam.spec ++
--- /var/tmp/diff_new_pack.Ot6iE1/_old 2013-11-15 14:25:07.0 +0100
+++ /var/tmp/diff_new_pack.Ot6iE1/_new 2013-11-15 14:25:07.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-pam
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-pam-3.1.0.tar.bz2 - yast2-pam-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-pam-3.1.0/CONTRIBUTING.md
new/yast2-pam-3.1.1/CONTRIBUTING.md
--- old/yast2-pam-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0 +0100
+++ new/yast2-pam-3.1.1/CONTRIBUTING.md 2013-11-04 16:38:30.0 +0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
+autolinking](https://help.github.com/articles/github-flavored-markdown#references)
+and [openSUSE abbreviation
commit yast2-tune for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-tune for openSUSE:Factory
checked in at 2013-11-15 14:25:41
Comparing /work/SRC/openSUSE:Factory/yast2-tune (Old)
and /work/SRC/openSUSE:Factory/.yast2-tune.new (New)
Package is yast2-tune
Changes:
--- /work/SRC/openSUSE:Factory/yast2-tune/yast2-tune.changes2013-10-19
11:21:07.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-tune.new/yast2-tune.changes
2013-11-15 14:25:41.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-tune-3.0.3.tar.bz2
New:
yast2-tune-3.0.4.tar.bz2
Other differences:
--
++ yast2-tune.spec ++
--- /var/tmp/diff_new_pack.73nd83/_old 2013-11-15 14:25:42.0 +0100
+++ /var/tmp/diff_new_pack.73nd83/_new 2013-11-15 14:25:42.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-tune
-Version:3.0.3
+Version:3.0.4
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-tune-3.0.3.tar.bz2 - yast2-tune-3.0.4.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-tune-3.0.3/CONTRIBUTING.md
new/yast2-tune-3.0.4/CONTRIBUTING.md
--- old/yast2-tune-3.0.3/CONTRIBUTING.md1970-01-01 01:00:00.0
+0100
+++ new/yast2-tune-3.0.4/CONTRIBUTING.md2013-11-04 16:54:45.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
+autolinking](https://help.github.com/articles/github-flavored-markdown#references)
+and [openSUSE abbreviation
commit yast2-slp-server for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-slp-server for
openSUSE:Factory checked in at 2013-11-15 14:25:32
Comparing /work/SRC/openSUSE:Factory/yast2-slp-server (Old)
and /work/SRC/openSUSE:Factory/.yast2-slp-server.new (New)
Package is yast2-slp-server
Changes:
--- /work/SRC/openSUSE:Factory/yast2-slp-server/yast2-slp-server.changes
2013-10-11 11:11:33.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-slp-server.new/yast2-slp-server.changes
2013-11-15 14:25:33.0 +0100
@@ -1,0 +2,6 @@
+Thu Nov 14 12:16:15 UTC 2013 - vmora...@suse.com
+
+- fix incorrect firewall service bnc#825505
+- 3.1.1
+
+---
Old:
yast2-slp-server-3.1.0.tar.bz2
New:
yast2-slp-server-3.1.1.tar.bz2
Other differences:
--
++ yast2-slp-server.spec ++
--- /var/tmp/diff_new_pack.FbmS8f/_old 2013-11-15 14:25:34.0 +0100
+++ /var/tmp/diff_new_pack.FbmS8f/_new 2013-11-15 14:25:34.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-slp-server
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-slp-server-3.1.0.tar.bz2 - yast2-slp-server-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-slp-server-3.1.0/CONTRIBUTING.md
new/yast2-slp-server-3.1.1/CONTRIBUTING.md
--- old/yast2-slp-server-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-slp-server-3.1.1/CONTRIBUTING.md 2013-11-15 13:37:33.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
commit yast2-testsuite for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-testsuite for openSUSE:Factory
checked in at 2013-11-15 14:25:34
Comparing /work/SRC/openSUSE:Factory/yast2-testsuite (Old)
and /work/SRC/openSUSE:Factory/.yast2-testsuite.new (New)
Package is yast2-testsuite
Changes:
--- /work/SRC/openSUSE:Factory/yast2-testsuite/yast2-testsuite.changes
2013-10-11 11:11:54.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-testsuite.new/yast2-testsuite.changes
2013-11-15 14:25:35.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-testsuite-3.1.0.tar.bz2
New:
yast2-testsuite-3.1.1.tar.bz2
Other differences:
--
++ yast2-testsuite.spec ++
--- /var/tmp/diff_new_pack.U0g7BX/_old 2013-11-15 14:25:36.0 +0100
+++ /var/tmp/diff_new_pack.U0g7BX/_new 2013-11-15 14:25:36.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-testsuite
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-testsuite-3.1.0.tar.bz2 - yast2-testsuite-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-testsuite-3.1.0/CONTRIBUTING.md
new/yast2-testsuite-3.1.1/CONTRIBUTING.md
--- old/yast2-testsuite-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-testsuite-3.1.1/CONTRIBUTING.md 2013-11-15 13:20:59.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
commit yast2-runlevel for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-runlevel for openSUSE:Factory
checked in at 2013-11-15 14:25:14
Comparing /work/SRC/openSUSE:Factory/yast2-runlevel (Old)
and /work/SRC/openSUSE:Factory/.yast2-runlevel.new (New)
Package is yast2-runlevel
Changes:
--- /work/SRC/openSUSE:Factory/yast2-runlevel/yast2-runlevel.changes
2013-10-11 11:10:22.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-runlevel.new/yast2-runlevel.changes
2013-11-15 14:25:15.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-runlevel-3.1.0.tar.bz2
New:
yast2-runlevel-3.1.1.tar.bz2
Other differences:
--
++ yast2-runlevel.spec ++
--- /var/tmp/diff_new_pack.pcrOAX/_old 2013-11-15 14:25:15.0 +0100
+++ /var/tmp/diff_new_pack.pcrOAX/_new 2013-11-15 14:25:15.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-runlevel
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-runlevel-3.1.0.tar.bz2 - yast2-runlevel-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-runlevel-3.1.0/CONTRIBUTING.md
new/yast2-runlevel-3.1.1/CONTRIBUTING.md
--- old/yast2-runlevel-3.1.0/CONTRIBUTING.md1970-01-01 01:00:00.0
+0100
+++ new/yast2-runlevel-3.1.1/CONTRIBUTING.md2013-11-15 13:13:55.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
+autolinking](https://help.github.com/articles/github-flavored-markdown#references)
+and
commit yast2-python-bindings for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-python-bindings for
openSUSE:Factory checked in at 2013-11-15 14:25:11
Comparing /work/SRC/openSUSE:Factory/yast2-python-bindings (Old)
and /work/SRC/openSUSE:Factory/.yast2-python-bindings.new (New)
Package is yast2-python-bindings
Changes:
---
/work/SRC/openSUSE:Factory/yast2-python-bindings/yast2-python-bindings.changes
2013-10-11 11:08:50.0 +0200
+++
/work/SRC/openSUSE:Factory/.yast2-python-bindings.new/yast2-python-bindings.changes
2013-11-15 14:25:12.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-python-bindings-3.1.0.tar.bz2
New:
yast2-python-bindings-3.1.1.tar.bz2
Other differences:
--
++ yast2-python-bindings.spec ++
--- /var/tmp/diff_new_pack.J2GO3S/_old 2013-11-15 14:25:12.0 +0100
+++ /var/tmp/diff_new_pack.J2GO3S/_new 2013-11-15 14:25:12.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-python-bindings
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-python-bindings-3.1.0.tar.bz2 -
yast2-python-bindings-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-python-bindings-3.1.0/CONTRIBUTING.md
new/yast2-python-bindings-3.1.1/CONTRIBUTING.md
--- old/yast2-python-bindings-3.1.0/CONTRIBUTING.md 1970-01-01
01:00:00.0 +0100
+++ new/yast2-python-bindings-3.1.1/CONTRIBUTING.md 2013-11-04
17:16:50.0 +0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or
commit yast2-x11 for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-x11 for openSUSE:Factory
checked in at 2013-11-15 14:25:43
Comparing /work/SRC/openSUSE:Factory/yast2-x11 (Old)
and /work/SRC/openSUSE:Factory/.yast2-x11.new (New)
Package is yast2-x11
Changes:
--- /work/SRC/openSUSE:Factory/yast2-x11/yast2-x11.changes 2013-10-11
09:06:23.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-x11.new/yast2-x11.changes 2013-11-15
14:25:44.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-x11-3.1.0.tar.bz2
New:
yast2-x11-3.1.1.tar.bz2
Other differences:
--
++ yast2-x11.spec ++
--- /var/tmp/diff_new_pack.DqSnwQ/_old 2013-11-15 14:25:45.0 +0100
+++ /var/tmp/diff_new_pack.DqSnwQ/_new 2013-11-15 14:25:45.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-x11
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
@@ -57,7 +57,6 @@
/etc/icewm
%doc %dir %{yast_docdir}
-%doc %{yast_docdir}/README*
%doc %{yast_docdir}/COPY*
%doc %{_mandir}/*/*
++ yast2-x11-3.1.0.tar.bz2 - yast2-x11-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-x11-3.1.0/CONTRIBUTING.md
new/yast2-x11-3.1.1/CONTRIBUTING.md
--- old/yast2-x11-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0 +0100
+++ new/yast2-x11-3.1.1/CONTRIBUTING.md 2013-11-04 17:31:41.0 +0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
commit yast2-security for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-security for openSUSE:Factory
checked in at 2013-11-15 14:25:29
Comparing /work/SRC/openSUSE:Factory/yast2-security (Old)
and /work/SRC/openSUSE:Factory/.yast2-security.new (New)
Package is yast2-security
Changes:
--- /work/SRC/openSUSE:Factory/yast2-security/yast2-security.changes
2013-10-11 11:11:12.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-security.new/yast2-security.changes
2013-11-15 14:25:30.0 +0100
@@ -1,0 +2,5 @@
+Wed Nov 13 15:56:18 UTC 2013 - jreidin...@suse.com
+
+- Add explicit COPYING file
+
+---
Old:
yast2-security-3.1.0.tar.bz2
New:
yast2-security-3.1.1.tar.bz2
Other differences:
--
++ yast2-security.spec ++
--- /var/tmp/diff_new_pack.bYegZ8/_old 2013-11-15 14:25:31.0 +0100
+++ /var/tmp/diff_new_pack.bYegZ8/_new 2013-11-15 14:25:31.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-security
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++ yast2-security-3.1.0.tar.bz2 - yast2-security-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-security-3.1.0/CONTRIBUTING.md
new/yast2-security-3.1.1/CONTRIBUTING.md
--- old/yast2-security-3.1.0/CONTRIBUTING.md1970-01-01 01:00:00.0
+0100
+++ new/yast2-security-3.1.1/CONTRIBUTING.md2013-11-15 13:20:27.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on GitHub, make sure
+you mention it in the commit message for cross-reference. Use format like
+bnc#775814 or gh#yast/yast-foo#42. See also [GitHub
+autolinking](https://help.github.com/articles/github-flavored-markdown#references)
+and
commit yast2-snapper for openSUSE:Factory
Hello community, here is the log from the commit of package yast2-snapper for openSUSE:Factory checked in at 2013-11-15 14:28:04 Comparing /work/SRC/openSUSE:Factory/yast2-snapper (Old) and /work/SRC/openSUSE:Factory/.yast2-snapper.new (New) Package is yast2-snapper Changes: --- /work/SRC/openSUSE:Factory/yast2-snapper/yast2-snapper.changes 2013-10-20 10:56:21.0 +0200 +++ /work/SRC/openSUSE:Factory/.yast2-snapper.new/yast2-snapper.changes 2013-11-15 14:28:05.0 +0100 @@ -1,0 +2,5 @@ +Wed Nov 06 09:54:33 CET 2013 - aschn...@suse.de + +- added supplements snapper and yast2 (fate#314695) + +--- Other differences: -- ++ yast2-snapper.spec ++ --- /var/tmp/diff_new_pack.uCWvzZ/_old 2013-11-15 14:28:06.0 +0100 +++ /var/tmp/diff_new_pack.uCWvzZ/_new 2013-11-15 14:28:06.0 +0100 @@ -26,9 +26,8 @@ BuildRequires: doxygen BuildRequires: gcc-c++ BuildRequires: libbtrfs-devel -BuildRequires: libsnapper-devel = 0.0.11 +BuildRequires: libsnapper-devel = 0.0.17 BuildRequires: libtool -BuildRequires: perl-XML-Writer BuildRequires: update-desktop-files BuildRequires: yast2 BuildRequires: yast2-core-devel = 2.23.1 @@ -37,6 +36,7 @@ Requires: yast2 = 2.21.22 Requires: yast2-ruby-bindings = 1.0.0 +Supplements:packageand(snapper:yast2) # require the version of libsnapper used during build (bnc#845618) %requires_eq libsnapper2 ++ yast2-snapper-3.1.1.tar.bz2 ++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/yast2-snapper-3.1.1/CONTRIBUTING.md new/yast2-snapper-3.1.1/CONTRIBUTING.md --- old/yast2-snapper-3.1.1/CONTRIBUTING.md 1970-01-01 01:00:00.0 +0100 +++ new/yast2-snapper-3.1.1/CONTRIBUTING.md 2013-11-06 09:56:09.0 +0100 @@ -0,0 +1,87 @@ +YaST Contribution Guidelines + + +YaST is an open source project and as such it welcomes all kinds of +contributions. If you decide to contribute, please follow these guidelines to +ensure the process is effective and pleasant both for you and YaST maintainers. + +There are two main forms of contribution: reporting bugs and performing code +changes. + +Bug Reports +--- + +If you find a problem, please report it either using +[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2) +or [GitHub issues](../../issues). (For Bugzilla, use the [simplified +registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp) +if you don't have an account yet.) + +If you find a problem, please report it either using +[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee +that every bug will be fixed, but we'll try. + +When creating a bug report, please follow our [bug reporting +guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug). + +Code Changes + + +We welcome all kinds of code contributions, from simple bug fixes to significant +refactorings and implementation of new features. However, before making any +non-trivial contribution, get in touch with us first — this can prevent wasted +effort on both sides. Also, have a look at our [development +documentation](http://en.opensuse.org/openSUSE:YaST_development). + +To send us your code change, use GitHub pull requests. The workflow is as +follows: + + 1. Fork the project. + + 2. Create a topic branch based on `master`. + + 3. Implement your change, including tests (if possible). Make sure you adhere + to the [Ruby style + guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md). + + 4. Make sure your change didn't break anything by building the RPM package + (`rake osc:build`). The build process includes running the full testsuite. + + 5. Publish the branch and create a pull request. + + 6. YaST developers will review your change and possibly point out issues. + Adapt the code under their guidance until they are all resolved. + + 7. Finally, the pull request will get merged or rejected. + +See also [GitHub's guide on +contributing](https://help.github.com/articles/fork-a-repo). + +If you want to do multiple unrelated changes, use separate branches and pull +requests. + +Do not change the `VERSION` and `*.changes` files as this could lead to +conflicts. + +### Commits + +Each commit in the pull request should do only one thing, which is clearly +described by its commit message. Especially avoid mixing formatting changes and +functional changes into one commit. When writing commit messages, adhere to +[widely used +conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). +
commit yast2-storage for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-storage for openSUSE:Factory
checked in at 2013-11-15 14:28:33
Comparing /work/SRC/openSUSE:Factory/yast2-storage (Old)
and /work/SRC/openSUSE:Factory/.yast2-storage.new (New)
Package is yast2-storage
Changes:
--- /work/SRC/openSUSE:Factory/yast2-storage/yast2-storage.changes
2013-10-20 10:56:29.0 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-storage.new/yast2-storage.changes
2013-11-15 14:28:35.0 +0100
@@ -1,0 +2,23 @@
+Wed Nov 13 15:38:35 CET 2013 - aschn...@suse.de
+
+- use correct binary prefix (bnc#849276)
+- version 3.1.2
+
+---
+Wed Nov 06 09:49:39 CET 2013 - aschn...@suse.de
+
+- do not install yast2-snapper if root is on btrfs (fate#314695)
+
+---
+Mon Nov 04 16:42:35 CET 2013 - aschn...@suse.de
+
+- changed technique to ensure UTF-8 string in ruby (bnc#848812)
+
+---
+Wed Oct 30 17:44:29 CET 2013 - aschn...@suse.de
+
+- handle device name change during update due to switch from
+ dmraid to mdadm (fate#316007)
+- version 3.1.1
+
+---
@@ -6537 +6560 @@
-- allow arbitrary number of pathes for md raid
+- allow arbitrary number of paths for md raid
Old:
yast2-storage-3.1.0.tar.bz2
New:
yast2-storage-3.1.2.tar.bz2
Other differences:
--
++ yast2-storage.spec ++
--- /var/tmp/diff_new_pack.lJjr6u/_old 2013-11-15 14:28:36.0 +0100
+++ /var/tmp/diff_new_pack.lJjr6u/_new 2013-11-15 14:28:36.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-storage
-Version:3.1.0
+Version:3.1.2
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
@@ -26,8 +26,8 @@
BuildRequires: docbook-xsl-stylesheets
BuildRequires: doxygen
BuildRequires: gcc-c++
-BuildRequires: libstorage-devel = 2.24.0
-BuildRequires: libstorage-ruby = 2.25.0
+BuildRequires: libstorage-devel = 2.25.3
+BuildRequires: libstorage-ruby = 2.25.2
BuildRequires: libtool
BuildRequires: libxslt
BuildRequires: perl-XML-Writer
@@ -38,8 +38,8 @@
BuildRequires: yast2-core-devel = 2.23.1
BuildRequires: yast2-devtools = 3.0.6
BuildRequires: yast2-testsuite = 2.19.0
-Requires: libstorage-ruby = 2.25.0
-Requires: libstorage4 = 2.24.5
+Requires: libstorage-ruby = 2.25.2
+Requires: libstorage4 = 2.25.2
Requires: rubygem-ruby-dbus
Requires: yast2 = 2.19.4
Requires: yast2-core = 2.18.3
++ yast2-storage-3.1.0.tar.bz2 - yast2-storage-3.1.2.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-storage-3.1.0/CONTRIBUTING.md
new/yast2-storage-3.1.2/CONTRIBUTING.md
--- old/yast2-storage-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0
+0100
+++ new/yast2-storage-3.1.2/CONTRIBUTING.md 2013-11-15 10:46:48.0
+0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change,
commit atftp for openSUSE:Factory
Hello community,
here is the log from the commit of package atftp for openSUSE:Factory checked
in at 2013-11-15 16:55:54
Comparing /work/SRC/openSUSE:Factory/atftp (Old)
and /work/SRC/openSUSE:Factory/.atftp.new (New)
Package is atftp
Changes:
--- /work/SRC/openSUSE:Factory/atftp/atftp.changes 2013-02-14
20:33:20.0 +0100
+++ /work/SRC/openSUSE:Factory/.atftp.new/atftp.changes 2013-11-15
16:55:56.0 +0100
@@ -1,0 +2,8 @@
+Tue Nov 12 20:41:45 UTC 2013 - ch...@computersalat.de
+
+- rebase patches (p0)
+- rename atftpd.init.d to atftpd.init
+- fix spec
+ * remove ghost /var/run/atftp (created by init)
+
+---
Old:
atftpd.init.d
New:
atftpd.init
Other differences:
--
++ atftp.spec ++
--- /var/tmp/diff_new_pack.HPMZIW/_old 2013-11-15 16:55:57.0 +0100
+++ /var/tmp/diff_new_pack.HPMZIW/_new 2013-11-15 16:55:57.0 +0100
@@ -28,7 +28,7 @@
Release:0
Url:ftp://ftp.mamalinux.com/pub/atftp/
Source: %{name}-%{pkg_version}.tar.bz2
-Source1:atftpd.init.d
+Source1:atftpd.init
Source2:atftpd.sysconfig
Source3:atftpd.logrotate
Source4:atftp.fw
@@ -81,11 +81,11 @@
%patch6
%patch7
%patch8
-%patch9 -p1
-%patch10 -p0
-%patch12 -p1
-%patch13 -p1
-%patch14 -p1
+%patch9
+%patch10
+%patch12
+%patch13
+%patch14
%build
autoreconf -fi
@@ -144,6 +144,6 @@
%config %{_fwdefdir}/atftp
%dir %attr(0750,tftp,tftp) /srv/tftpboot
%dir %attr(0750,tftp,tftp) /var/log/atftpd/
-%ghost %dir /var/run/atftpd
+#ghost %dir /var/run/atftpd
%changelog
++ atftp-0.7-ack_heuristic.patch ++
--- /var/tmp/diff_new_pack.HPMZIW/_old 2013-11-15 16:55:57.0 +0100
+++ /var/tmp/diff_new_pack.HPMZIW/_new 2013-11-15 16:55:57.0 +0100
@@ -1,7 +1,7 @@
-Index: atftp-0.7/tftpd_file.c
+Index: tftpd_file.c
===
atftp-0.7.orig/tftpd_file.c2013-02-06 16:15:50.178332917 +0100
-+++ atftp-0.7/tftpd_file.c 2013-02-06 16:16:49.608140471 +0100
+--- tftpd_file.c.orig
tftpd_file.c
@@ -402,7 +402,6 @@ int tftpd_send_file(struct thread_data *
int timeout_state = state;
int result;
++ atftp-0.7-default_dir_man.patch ++
--- /var/tmp/diff_new_pack.HPMZIW/_old 2013-11-15 16:55:57.0 +0100
+++ /var/tmp/diff_new_pack.HPMZIW/_new 2013-11-15 16:55:57.0 +0100
@@ -1,7 +1,7 @@
-Index: atftp-0.7/atftpd.8
+Index: atftpd.8
===
atftp-0.7.orig/atftpd.82012-11-16 11:50:17.618281568 +0100
-+++ atftp-0.7/atftpd.8 2013-01-03 14:27:00.913280412 +0100
+--- atftpd.8.orig
atftpd.8
@@ -210,7 +210,7 @@ Show summary of options.
.B path
This is the root directory used by the TFTP server. All requested
++ atftp-0.7-default_user_man.patch ++
--- /var/tmp/diff_new_pack.HPMZIW/_old 2013-11-15 16:55:57.0 +0100
+++ /var/tmp/diff_new_pack.HPMZIW/_new 2013-11-15 16:55:57.0 +0100
@@ -1,7 +1,7 @@
-Index: atftp-0.7/atftpd.8
+Index: atftpd.8
===
atftp-0.7.orig/atftpd.82012-11-16 11:46:18.798067178 +0100
-+++ atftp-0.7/atftpd.8 2012-11-16 11:50:17.618281568 +0100
+--- atftpd.8.orig
atftpd.8
@@ -80,10 +80,10 @@ acknowledging the 'multicast' request by
.TP
++ atftp-0.7-server_receive_race.patch ++
--- /var/tmp/diff_new_pack.HPMZIW/_old 2013-11-15 16:55:57.0 +0100
+++ /var/tmp/diff_new_pack.HPMZIW/_new 2013-11-15 16:55:57.0 +0100
@@ -1,8 +1,8 @@
Index: tftpd_file.c
===
tftpd_file.c.orig 2012-08-06 10:26:36.356745154 +0200
-+++ tftpd_file.c 2012-08-06 11:27:59.265571512 +0200
-@@ -113,7 +113,7 @@ int tftpd_receive_file(struct thread_dat
+--- tftpd_file.c.orig
tftpd_file.c
+@@ -114,7 +114,7 @@ int tftpd_receive_file(struct thread_dat
struct sockaddr_in *sa = data-client_info-client;
struct sockaddr_in from;
struct tftphdr *tftphdr = (struct tftphdr *)data-data_buffer;
@@ -11,7 +11,7 @@
char filename[MAXLEN];
char string[MAXLEN];
int timeout = data-timeout;
-@@ -143,18 +143,6 @@ int tftpd_receive_file(struct thread_dat
+@@ -144,18 +144,6 @@ int tftpd_receive_file(struct thread_dat
return ERR;
}
@@ -30,7 +30,7 @@
/* tsize option */
if (((result = opt_get_tsize(data-tftp_options)) -1) !convert)
{
-@@ -171,7 +159,6 @@ int tftpd_receive_file(struct thread_dat
+@@ -172,7 +160,6 @@ int tftpd_receive_file(struct thread_dat
if
commit autoyast2 for openSUSE:Factory
Hello community,
here is the log from the commit of package autoyast2 for openSUSE:Factory
checked in at 2013-11-15 16:56:01
Comparing /work/SRC/openSUSE:Factory/autoyast2 (Old)
and /work/SRC/openSUSE:Factory/.autoyast2.new (New)
Package is autoyast2
Changes:
--- /work/SRC/openSUSE:Factory/autoyast2/autoyast2.changes 2013-10-20
10:49:44.0 +0200
+++ /work/SRC/openSUSE:Factory/.autoyast2.new/autoyast2.changes 2013-11-15
16:56:02.0 +0100
@@ -1,0 +2,6 @@
+Fri Nov 8 15:14:37 UTC 2013 - vmora...@suse.com
+
+- replace yast2-runlevel dependency with yast2-services-manager
+ FATE#312568
+
+---
Old:
autoyast2-3.1.0.tar.bz2
New:
autoyast2-3.1.1.tar.bz2
Other differences:
--
++ autoyast2.spec ++
--- /var/tmp/diff_new_pack.nQOqId/_old 2013-11-15 16:56:03.0 +0100
+++ /var/tmp/diff_new_pack.nQOqId/_new 2013-11-15 16:56:03.0 +0100
@@ -17,7 +17,7 @@
Name: autoyast2
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
@@ -83,7 +83,7 @@
Requires: yast2-country
Requires: yast2-ncurses
Requires: yast2-packager
-Requires: yast2-runlevel
+Requires: yast2-services-manager
Requires: yast2-slp
Requires: yast2-storage
Requires: yast2-transfer = 2.21.0
++ autoyast2-3.1.0.tar.bz2 - autoyast2-3.1.1.tar.bz2 ++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/autoyast2-3.1.0/CONTRIBUTING.md
new/autoyast2-3.1.1/CONTRIBUTING.md
--- old/autoyast2-3.1.0/CONTRIBUTING.md 1970-01-01 01:00:00.0 +0100
+++ new/autoyast2-3.1.1/CONTRIBUTING.md 2013-11-13 13:49:56.0 +0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make sure your change didn't break anything by building the RPM package
+ (`rake osc:build`). The build process includes running the full testsuite.
+
+ 5. Publish the branch and create a pull request.
+
+ 6. YaST developers will review your change and possibly point out issues.
+ Adapt the code under their guidance until they are all resolved.
+
+ 7. Finally, the pull request will get merged or rejected.
+
+See also [GitHub's guide on
+contributing](https://help.github.com/articles/fork-a-repo).
+
+If you want to do multiple unrelated changes, use separate branches and pull
+requests.
+
+Do not change the `VERSION` and `*.changes` files as this could lead to
+conflicts.
+
+### Commits
+
+Each commit in the pull request should do only one thing, which is clearly
+described by its commit message. Especially avoid mixing formatting changes and
+functional changes into one commit. When writing commit messages, adhere to
+[widely used
+conventions](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+If your commit is related to a bug in Buzgilla or an issue on
commit openstack-utils for openSUSE:Factory
Hello community, here is the log from the commit of package openstack-utils for openSUSE:Factory checked in at 2013-11-15 16:56:23 Comparing /work/SRC/openSUSE:Factory/openstack-utils (Old) and /work/SRC/openSUSE:Factory/.openstack-utils.new (New) Package is openstack-utils Changes: --- /work/SRC/openSUSE:Factory/openstack-utils/openstack-utils.changes 2013-10-30 15:48:13.0 +0100 +++ /work/SRC/openSUSE:Factory/.openstack-utils.new/openstack-utils.changes 2013-11-15 16:56:24.0 +0100 @@ -1,0 +2,6 @@ +Wed Nov 13 09:37:07 UTC 2013 - speili...@suse.com + +- Drop changesrevision from service file, the implementation in tar_scm + changed + +--- Other differences: -- ++ _service ++ --- /var/tmp/diff_new_pack.n9vqyH/_old 2013-11-15 16:56:24.0 +0100 +++ /var/tmp/diff_new_pack.n9vqyH/_new 2013-11-15 16:56:24.0 +0100 @@ -5,7 +5,7 @@ param name=exclude.git/param param name=versionformat@PARENT_TAG@+git.%ct.%h/param param name=revisionmaster/param - param name=changesrevisionb17bebedea/param/service + /service service mode=disabled name=recompress param name=fileopenstack-utils-*.tar/param @@ -15,4 +15,4 @@ service mode=disabled name=set_version param name=basenameopenstack-utils/param /service -/services \ No newline at end of file +/services -- To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit kiwi for openSUSE:Factory
Hello community, here is the log from the commit of package kiwi for openSUSE:Factory checked in at 2013-11-15 16:56:10 Comparing /work/SRC/openSUSE:Factory/kiwi (Old) and /work/SRC/openSUSE:Factory/.kiwi.new (New) Package is kiwi Changes: --- /work/SRC/openSUSE:Factory/kiwi/kiwi.changes2013-11-12 15:09:10.0 +0100 +++ /work/SRC/openSUSE:Factory/.kiwi.new/kiwi.changes 2013-11-15 16:56:13.0 +0100 @@ -1,0 +2,104 @@ +Fri Nov 15 15:48:34 CET 2013 - m...@suse.de + +- v5.06.06 released + +--- +Thu Nov 14 11:48:12 CET 2013 - m...@suse.de + +- enhance pxeSetupDownloadServer + * if the image download server ip is not configured by $kiwiserver +the function now also checks for the contents of the $ip variable +which exists if pxelinux booted the kernel with 'IPAPPEND 1' +only if we did not get information from $ip the default name +tftp.$DOMAIN applies as it was before + +--- +Wed Nov 13 18:22:15 CET 2013 - m...@suse.de + +- fixed broken symlink due to move of results from intermediate + build directory to final result directory + +--- +Wed Nov 13 17:52:44 CET 2013 - m...@suse.de + +- use ovftool to create an ova format/archive + * unfortunately only ovftool supports the full featureset +e.g streamOptimized images + * added a runtime check to search for ovftool if the +format=ova is requested + +--- +Wed Nov 13 17:36:23 CET 2013 - m...@suse.de + +- removed support for controller=scsi in KIWIImageFormat + and adapted the runtime checker as well as the unit test + +--- +Wed Nov 13 17:32:08 CET 2013 - m...@suse.de + +- update all image descriptions to schema version 5.9 + +--- +Wed Nov 13 17:30:57 CET 2013 - m...@suse.de + +- update kiwi schema to version 5.9 + * removed scsi as allowed value from vmdisk controller attribute + +--- +Wed Nov 13 17:27:46 CET 2013 - m...@suse.de + +- added new xsl stylesheet 5.8 - 5.9 + * the controller type 'scsi' does not exist for VMware. +lsilogic and buslogic define scsi controllers. Thus this +attribute value is moved back to the default 'ide' value +Using new controller types requires a specific version of +qemu-img which means the only safe translation is back to +ide + +--- +Wed Nov 13 16:17:16 CET 2013 - m...@suse.de + +- fixed OVF file diskname: file has to be the .vmdk + in reference and not the .ovf + +--- +Tue Nov 12 00:22:25 CET 2013 - cshor...@suse.de + +- make sure etc/sysconfig directory exists before temporary + copying the proxy configuration into the chroot + +--- +Mon Nov 11 23:31:07 CET 2013 - cshor...@suse.de + +- fixed nested File::Find method fixupLinks in cloneImage + * entities found in $File::Find::name always exists, thus it's +not needed to check their existence + * moved the code searching for links with relative pointer +into a perl closure method named findLinksRelative + * moved the code fixing broken relative links into its +own code block + +--- +Mon Nov 11 22:52:45 CET 2013 - m...@suse.de + +- fixed creation of rpmsort cache data in KIWIAnalyseManagedSoftware + * the data was stored as reference but the reference +was changed during the process + +--- +Mon Nov 11 22:03:15 CET 2013 - m...@suse.de + +- don't remove the satsolver cache when running kiwi --describe + +--- +Mon Nov 11 22:02:28 CET 2013 - m...@suse.de + +- open custom directory tree browser in a new tab + +--- +Mon Nov 11 21:54:54 CET 2013 - m...@suse.de + +- fixed creation of toplevel menu in kiwi analyse + * the menu should only contain items found by the analyser + +--- @@ -34,0 +139,7 @@ +Mon Nov 11 05:12:35 CET 2013 - kanstantsin_shaut...@suse.de + +- if format is set to ovf or ova it makes sense to create the + standard VMware machine config file (.vmx) too +- rename log message from Starting
commit webalizer for openSUSE:Factory
Hello community,
here is the log from the commit of package webalizer for openSUSE:Factory
checked in at 2013-11-15 16:57:01
Comparing /work/SRC/openSUSE:Factory/webalizer (Old)
and /work/SRC/openSUSE:Factory/.webalizer.new (New)
Package is webalizer
Changes:
--- /work/SRC/openSUSE:Factory/webalizer/webalizer.changes 2012-06-26
17:41:05.0 +0200
+++ /work/SRC/openSUSE:Factory/.webalizer.new/webalizer.changes 2013-11-15
16:57:02.0 +0100
@@ -1,0 +2,12 @@
+Thu Nov 14 22:31:51 UTC 2013 - ch...@computersalat.de
+
+- update to update to 2.23-08
+ * Fix sporadic eol problem with some IIS/W3C logs
+ * Fix compiler directive syntax error (broke some 64 bit systems)
+ - Changes/Additions:
+ * Modest speed improvements in hash table code
+- rebase patches
+- fix spec
+ * package flags too, not only the DIR
+
+---
Old:
webalizer-2.23-05-src.tar.bz2
New:
webalizer-2.23-08-src.tar.bz2
Other differences:
--
++ webalizer.spec ++
--- /var/tmp/diff_new_pack.YugiMF/_old 2013-11-15 16:57:03.0 +0100
+++ /var/tmp/diff_new_pack.YugiMF/_new 2013-11-15 16:57:03.0 +0100
@@ -1,7 +1,7 @@
#
# spec file for package webalizer
#
-# Copyright (c) 2012 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2013 SUSE LINUX Products 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,7 +17,7 @@
%define apache_serverroot %(/usr/sbin/apxs2 -q datadir 2/dev/null || apxs -q
PREFIX)
-%define editlvl 05
+%define editlvl 08
Name: webalizer
Summary:A Web Server Log File Analysis Program
@@ -26,7 +26,7 @@
Version:2.23
Release:0
Url:http://www.mrunix.net/webalizer/
-Source0:%{name}-%{version}-%{editlvl}-src.tar.bz2
+Source0:
ftp://ftp.mrunix.net/pub/webalizer/%{name}-%{version}-%{editlvl}-src.tar.bz2
Source1:flags.tar.bz2
Source2:flags.license.html
# PATCH-MISSING-TAG -- See http://en.opensuse.org/Packaging/Patches
@@ -90,9 +90,9 @@
%patch0
%patch1
%patch3
-%patch4 -p1
+%patch4
%patch5
-%patch6 -p1
+%patch6
%{__cp} -a %{S:2} .
%build
@@ -140,5 +140,6 @@
%defattr(-,root,root)
%doc flags.license.html
%dir %{apache_serverroot}/htdocs/%{name}/flags
+%{apache_serverroot}/htdocs/%{name}/flags/*
%changelog
++ webalizer-2.21-02-fclose.diff ++
--- /var/tmp/diff_new_pack.YugiMF/_old 2013-11-15 16:57:03.0 +0100
+++ /var/tmp/diff_new_pack.YugiMF/_new 2013-11-15 16:57:03.0 +0100
@@ -1,6 +1,8 @@
wcmgr.c
+Index: wcmgr.c
+===
+--- wcmgr.c.orig
+++ wcmgr.c
-@@ -839,6 +839,7 @@
+@@ -848,6 +848,7 @@ void import_cache()
exit(1);
}
}
++ webalizer-2.21-02-ia64.diff ++
--- /var/tmp/diff_new_pack.YugiMF/_old 2013-11-15 16:57:03.0 +0100
+++ /var/tmp/diff_new_pack.YugiMF/_new 2013-11-15 16:57:03.0 +0100
@@ -1,6 +1,8 @@
output.c
+Index: output.c
+===
+--- output.c.orig
+++ output.c
-@@ -835,7 +835,7 @@
+@@ -835,7 +835,7 @@ void top_sites_table(int flag)
while(cnt--)
{
/* calculate totals */
@@ -9,7 +11,7 @@
{
case OBJ_REG: h_reg++; break;
case OBJ_GRP: h_grp++; break;
-@@ -1025,7 +1025,7 @@
+@@ -1025,7 +1025,7 @@ void top_urls_table(int flag)
while (cnt--)
{
/* calculate totals */
@@ -18,7 +20,7 @@
{
case OBJ_REG: u_reg++; break;
case OBJ_GRP: u_grp++; break;
-@@ -1228,12 +1228,12 @@
+@@ -1228,12 +1228,12 @@ void top_entry_table(int flag)
cnt=a_ctr; pointer=u_array;
while (cnt--)
{
@@ -36,7 +38,7 @@
}
pointer++;
}
-@@ -1332,7 +1332,7 @@
+@@ -1332,7 +1332,7 @@ void top_refs_table()
while(cnt--)
{
/* calculate totals */
@@ -45,7 +47,7 @@
{
case OBJ_REG: r_reg++; break;
case OBJ_HIDE: r_hid++; break;
-@@ -1497,7 +1497,7 @@
+@@ -1497,7 +1497,7 @@ void top_agents_table()
while(cnt--)
{
/* calculate totals */
@@ -54,7 +56,7 @@
{
case OBJ_REG: a_reg++; break;
case OBJ_GRP: a_grp++; break;
-@@ -1650,7 +1650,7 @@
+@@ -1650,7 +1650,7 @@ void top_search_table()
cnt=tot_num=a_ctr; pointer=s_array;
while(cnt--)
{
@@ -63,7 +65,7 @@
pointer++;
}
-@@ -1764,7 +1764,7 @@
+@@ -1764,7 +1764,7 @@ void top_users_table()
while(cnt--)
{
/* calculate totals
commit yast2-control-center for openSUSE:Factory
Hello community,
here is the log from the commit of package yast2-control-center for
openSUSE:Factory checked in at 2013-11-15 16:57:12
Comparing /work/SRC/openSUSE:Factory/yast2-control-center (Old)
and /work/SRC/openSUSE:Factory/.yast2-control-center.new (New)
Package is yast2-control-center
Changes:
---
/work/SRC/openSUSE:Factory/yast2-control-center/yast2-control-center.changes
2013-10-20 10:54:08.0 +0200
+++
/work/SRC/openSUSE:Factory/.yast2-control-center.new/yast2-control-center.changes
2013-11-15 16:57:13.0 +0100
@@ -1,0 +2,6 @@
+Thu Nov 14 13:11:28 UTC 2013 - mvid...@suse.com
+
+- ported to Qt5
+- 3.1.1
+
+---
Old:
yast2-control-center-3.1.0.tar.bz2
New:
yast2-control-center-3.1.1.tar.bz2
Other differences:
--
++ yast2-control-center.spec ++
--- /var/tmp/diff_new_pack.5VMqdb/_old 2013-11-15 16:57:13.0 +0100
+++ /var/tmp/diff_new_pack.5VMqdb/_new 2013-11-15 16:57:13.0 +0100
@@ -17,7 +17,7 @@
Name: yast2-control-center
-Version:3.1.0
+Version:3.1.1
Release:0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
@@ -25,7 +25,7 @@
BuildRequires: cmake
BuildRequires: libdrm-devel
BuildRequires: libjpeg-devel
-BuildRequires: libqt4-devel
+BuildRequires: libqt5-qtbase-devel
BuildRequires: pkgconfig
BuildRequires: update-desktop-files
BuildRequires: yast2-devtools
@@ -44,12 +44,6 @@
Group: System/YaST
Requires: yast2
Requires: yast2-control-center-binary
-Provides: y2c_menu
-Provides: y2m_menu
-Provides: yast2-menu
-Obsoletes: y2c_menu
-Obsoletes: y2m_menu
-Obsoletes: yast2-menu
%description
This package contains the menu selection component for YaST2.
++ yast2-control-center-3.1.0.tar.bz2 - yast2-control-center-3.1.1.tar.bz2
++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-control-center-3.1.0/CMakeLists.txt
new/yast2-control-center-3.1.1/CMakeLists.txt
--- old/yast2-control-center-3.1.0/CMakeLists.txt 2013-10-14
18:35:55.0 +0200
+++ new/yast2-control-center-3.1.1/CMakeLists.txt 2013-11-15
13:41:10.0 +0100
@@ -1,6 +1,6 @@
PROJECT( yast2-control-center )
-CMAKE_MINIMUM_REQUIRED( VERSION 2.6.0 )
-FIND_PACKAGE( Qt4 REQUIRED )
+CMAKE_MINIMUM_REQUIRED( VERSION 2.8.9 )
+FIND_PACKAGE( Qt5Core REQUIRED )
SET( RPMNAME yast2-control-center )
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-control-center-3.1.0/CONTRIBUTING.md
new/yast2-control-center-3.1.1/CONTRIBUTING.md
--- old/yast2-control-center-3.1.0/CONTRIBUTING.md 1970-01-01
01:00:00.0 +0100
+++ new/yast2-control-center-3.1.1/CONTRIBUTING.md 2013-11-15
13:41:10.0 +0100
@@ -0,0 +1,87 @@
+YaST Contribution Guidelines
+
+
+YaST is an open source project and as such it welcomes all kinds of
+contributions. If you decide to contribute, please follow these guidelines to
+ensure the process is effective and pleasant both for you and YaST maintainers.
+
+There are two main forms of contribution: reporting bugs and performing code
+changes.
+
+Bug Reports
+---
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/enter_bug.cgi?format=guidedproduct=openSUSE+Factorycomponent=YaST2)
+or [GitHub issues](../../issues). (For Bugzilla, use the [simplified
+registration](https://secure-www.novell.com/selfreg/jsp/createSimpleAccount.jsp)
+if you don't have an account yet.)
+
+If you find a problem, please report it either using
+[Bugzilla](https://bugzilla.novell.com/) or GitHub issues. We can't guarantee
+that every bug will be fixed, but we'll try.
+
+When creating a bug report, please follow our [bug reporting
+guidelines](http://en.opensuse.org/openSUSE:Report_a_YaST_bug).
+
+Code Changes
+
+
+We welcome all kinds of code contributions, from simple bug fixes to
significant
+refactorings and implementation of new features. However, before making any
+non-trivial contribution, get in touch with us first — this can prevent wasted
+effort on both sides. Also, have a look at our [development
+documentation](http://en.opensuse.org/openSUSE:YaST_development).
+
+To send us your code change, use GitHub pull requests. The workflow is as
+follows:
+
+ 1. Fork the project.
+
+ 2. Create a topic branch based on `master`.
+
+ 3. Implement your change, including tests (if possible). Make sure you adhere
+ to the [Ruby style
+ guide](https://github.com/SUSE/style-guides/blob/master/Ruby.md).
+
+ 4. Make
commit python-jsonpatch for openSUSE:Factory
Hello community,
here is the log from the commit of package python-jsonpatch for
openSUSE:Factory checked in at 2013-11-15 16:56:50
Comparing /work/SRC/openSUSE:Factory/python-jsonpatch (Old)
and /work/SRC/openSUSE:Factory/.python-jsonpatch.new (New)
Package is python-jsonpatch
Changes:
--- /work/SRC/openSUSE:Factory/python-jsonpatch/python-jsonpatch.changes
2013-11-04 13:26:28.0 +0100
+++ /work/SRC/openSUSE:Factory/.python-jsonpatch.new/python-jsonpatch.changes
2013-11-15 16:56:51.0 +0100
@@ -1,0 +2,5 @@
+Thu Nov 14 09:46:03 UTC 2013 - speili...@suse.com
+
+- Fix update-alternatives (SLE_11_SP3)
+
+---
Other differences:
--
++ python-jsonpatch.spec ++
--- /var/tmp/diff_new_pack.mLsdMW/_old 2013-11-15 16:56:53.0 +0100
+++ /var/tmp/diff_new_pack.mLsdMW/_new 2013-11-15 16:56:53.0 +0100
@@ -41,6 +41,7 @@
%prep
%setup -q -n jsonpatch-%{version}
+sed -i s|entry_poimts|entry_points| setup.py # Typo fix already in upstream
git..
%build
python setup.py build
@@ -49,6 +50,7 @@
python setup.py install --prefix=%{_prefix} --root=%{buildroot}
for i in patch diff; do
mv %{buildroot}%{_bindir}/json$i %{buildroot}%{_bindir}/json$i-%{py_ver}
+ln -s %{_bindir}/json$i-%{py_ver} %{buildroot}%{_bindir}/json$i
done
%pre
@@ -68,9 +70,11 @@
%files
%defattr(-,root,root,-)
%ghost %{_bindir}/jsonpatch
+%ghost %{_sysconfdir}/alternatives/jsonpatch
%{_bindir}/jsonpatch-%{py_ver}
%ghost %{_bindir}/jsondiff
+%ghost %{_sysconfdir}/alternatives/jsondiff
%{_bindir}/jsondiff-%{py_ver}
-%{python_sitelib}/*
+%{python_sitelib}/jsonpatch*
%changelog
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
commit python-d2to1 for openSUSE:Factory
Hello community, here is the log from the commit of package python-d2to1 for openSUSE:Factory checked in at 2013-11-15 16:56:44 Comparing /work/SRC/openSUSE:Factory/python-d2to1 (Old) and /work/SRC/openSUSE:Factory/.python-d2to1.new (New) Package is python-d2to1 Changes: --- /work/SRC/openSUSE:Factory/python-d2to1/python-d2to1.changes 2013-09-27 18:00:39.0 +0200 +++ /work/SRC/openSUSE:Factory/.python-d2to1.new/python-d2to1.changes 2013-11-15 16:56:44.0 +0100 @@ -1,0 +2,5 @@ +Thu Nov 7 12:38:56 UTC 2013 - speili...@suse.com + +- Fix changes format of first entry from local timezone (UTC+4) to UTC + +--- @@ -43 +48 @@ -Thu Nov 03 11:49:53 +0400 2011 - matwey.korni...@gmail.com +Thu Nov 03 07:49:53 UTC 2011 - matwey.korni...@gmail.com Other differences: -- -- To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-commit+h...@opensuse.org
