Hello community,

here is the log from the commit of package rear for openSUSE:Factory checked in 
at 2017-12-21 11:29:54
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rear (Old)
 and      /work/SRC/openSUSE:Factory/.rear.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rear"

Thu Dec 21 11:29:54 2017 rev:33 rq:558882 version:2.3

Changes:
--------
--- /work/SRC/openSUSE:Factory/rear/rear.changes        2017-08-24 
18:42:27.137459518 +0200
+++ /work/SRC/openSUSE:Factory/.rear.new/rear.changes   2017-12-21 
11:30:00.697594957 +0100
@@ -1,0 +2,30 @@
+Wed Dec 20 16:56:11 CET 2017 - [email protected]
+
+- Version upgrade to 2.3
+  (fate#323930 fate#323931 fate#323932)
+  New features and bigger enhancements:
+  * First steps towards running ReaR unattended in general
+  * SSH support in the recovery system is now secure by default
+  * Improved verification of the recovery system contents
+  * ReaR is now more safe against recreating on a wrong disk
+  Possibly backward incompatible changes:
+  * In addition to STDERR now also STDOUT is redirected into the
+    log file so that when programs prompt via STDOUT to get input
+    the program's prompt could be no longer visible to the user
+  * There are no longer private SSH keys in the recovery system by
+    default and a RSA key is generated from scratch when starting
+    sshd during recovery system startup so that it does no longer
+    work by default to use SSH in the recovery system via the
+    SSH keys that exist on the original system
+  * By default it is now fatal when 'ldd' reports a 'not found'
+    library for any file in a /bin/ or /sbin/ directory in the
+    recovery system so that now 'rear mkrescue/mkbackup'
+    may fail where it had (blindly) worked before
+  * Improved autodetection when the disk layout looks ambiguous.
+    Now 'rear recover' switches by default more often into the
+    MIGRATION_MODE where manual disk layout configuration happens
+    via several user dialogs so that by default 'rear recover'
+    shows more often user dialogs
+  A detailed list can be found in the rear-release-notes.txt file
+
+-------------------------------------------------------------------

Old:
----
  rear-2.2.tar.gz

New:
----
  rear-2.3.tar.gz

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

Other differences:
------------------
++++++ rear.spec ++++++
--- /var/tmp/diff_new_pack.aKuX4X/_old  2017-12-21 11:30:01.341563557 +0100
+++ /var/tmp/diff_new_pack.aKuX4X/_new  2017-12-21 11:30:01.345563362 +0100
@@ -22,9 +22,9 @@
 # When there are SUSE specific patches, add a trailing letter 'a' 'b' 'c' ...
 # to the rear upstrea, version (e.g. "Version: 1.18.a"
 # see https://github.com/rear/rear/issues/666
-Version:        2.2
+Version:        2.3
 Release:        0
-%define upstream_version 2.2
+%define upstream_version 2.3
 # Automatic version upgrades are not possible in practice.
 # The user must explicitly specify his intended version.
 # When users have a working disaster recovery procedure, they should not 
upgrade
@@ -61,8 +61,9 @@
 # Of course the rear bash scripts can be installed on any architecture just as 
any binaries can be installed on any architecture.
 # But the meaning of architecture dependent packages should be on what 
architectures they will work.
 # Therefore only those architectures that are actually supported are 
explicitly listed.
-# This avoids that rear can be "just installed" on architectures that are 
actually not supported (e.g. ARM or IBM z Systems):
-ExclusiveArch:  %ix86 x86_64 ppc ppc64 ppc64le
+# This avoids that rear can be "just installed" on architectures that are 
actually not supported (e.g. ARM or IBM z Systems).
+# ReaR does not support the 'ppc' architecture, cf. 
https://github.com/rear/rear/issues/1596#issuecomment-351698817
+ExclusiveArch:  %ix86 x86_64 ppc64 ppc64le
 # Furthermore for some architectures it requires architecture dependent 
packages (like syslinux for x86 and x86_64)
 # so that rear must be architecture dependent because ifarch conditions never 
match in case of "BuildArch: noarch"
 # see the GitHub issue https://github.com/rear/rear/issues/629
@@ -324,7 +325,7 @@
 
 %files
 %defattr(-,root,root,-)
-%doc AUTHORS COPYING README.adoc doc/*.txt doc/*.adoc doc/user-guide/*.adoc 
doc/mappings/
+%doc MAINTAINERS COPYING README.adoc doc/*.txt doc/*.adoc 
doc/user-guide/*.adoc doc/mappings/
 %{_mandir}/man8/rear.8*
 %config(noreplace) %{_sysconfdir}/rear/
 %config(noreplace) %{_datadir}/rear/

++++++ rear-2.2.tar.gz -> rear-2.3.tar.gz ++++++
++++ 15777 lines of diff (skipped)


Reply via email to