Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package transactional-update for
openSUSE:Factory checked in at 2023-02-09 16:21:58
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/transactional-update (Old)
and /work/SRC/openSUSE:Factory/.transactional-update.new.4462 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "transactional-update"
Thu Feb 9 16:21:58 2023 rev:96 rq:1063863 version:4.1.3
Changes:
--------
---
/work/SRC/openSUSE:Factory/transactional-update/transactional-update.changes
2023-01-24 20:36:05.561550354 +0100
+++
/work/SRC/openSUSE:Factory/.transactional-update.new.4462/transactional-update.changes
2023-02-09 16:22:11.566399476 +0100
@@ -1,0 +2,7 @@
+Wed Feb 8 15:14:26 UTC 2023 - Ignaz Forster <[email protected]>
+
+- Version 4.1.3
+ - Suppress SELinux relabelling output in quiet mode
+ - Documentation readability improvements
+
+-------------------------------------------------------------------
Old:
----
transactional-update-4.1.2.tar.gz
New:
----
transactional-update-4.1.3.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ transactional-update.spec ++++++
--- /var/tmp/diff_new_pack.6s6hjT/_old 2023-02-09 16:22:12.030401866 +0100
+++ /var/tmp/diff_new_pack.6s6hjT/_new 2023-02-09 16:22:12.034401887 +0100
@@ -26,7 +26,7 @@
%{!?_distconfdir: %global _distconfdir %{_prefix}%{_sysconfdir}}
Name: transactional-update
-Version: 4.1.2
+Version: 4.1.3
Release: 0
Summary: Transactional Updates with btrfs and snapshots
License: GPL-2.0-or-later AND LGPL-2.1-or-later
++++++ transactional-update-4.1.2.tar.gz -> transactional-update-4.1.3.tar.gz
++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/transactional-update-4.1.2/NEWS
new/transactional-update-4.1.3/NEWS
--- old/transactional-update-4.1.2/NEWS 2023-01-23 14:31:20.000000000 +0100
+++ new/transactional-update-4.1.3/NEWS 2023-02-08 16:06:30.000000000 +0100
@@ -2,6 +2,10 @@
Copyright (C) 2016-2022 Thorsten Kukuk, Ignaz Forster et al.
+Version 4.1.3
+* Suppress SELinux relabelling output in quiet mode
+* Documentation readability improvements
+
Version 4.1.2
* Don't try to mount user mounts if they don't exist [boo#1207366]
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/transactional-update-4.1.2/configure.ac
new/transactional-update-4.1.3/configure.ac
--- old/transactional-update-4.1.2/configure.ac 2023-01-23 14:31:20.000000000
+0100
+++ new/transactional-update-4.1.3/configure.ac 2023-02-08 16:06:30.000000000
+0100
@@ -1,11 +1,11 @@
dnl Process this file with autoconf to produce a configure script.
-AC_INIT(transactional-update, 4.1.2)
+AC_INIT(transactional-update, 4.1.3)
# Increase on any interface change and reset revision
LIBTOOL_CURRENT=4
# On interface change increase if backwards compatible, reset otherwise
LIBTOOL_AGE=0
# Increase on *any* C/C++ library code change, reset at interface change
-LIBTOOL_REVISION=2
+LIBTOOL_REVISION=3
AC_CANONICAL_SYSTEM
AM_INIT_AUTOMAKE([foreign])
AC_CONFIG_FILES([tukit.pc])
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/transactional-update-4.1.2/doc/transactional-update.xml
new/transactional-update-4.1.3/doc/transactional-update.xml
--- old/transactional-update-4.1.2/doc/transactional-update.xml 2023-01-23
14:31:20.000000000 +0100
+++ new/transactional-update-4.1.3/doc/transactional-update.xml 2023-02-08
16:06:30.000000000 +0100
@@ -45,8 +45,8 @@
is an application that allows to update a Linux system and its
applications in an <emphasis>atomic</emphasis> way: The update will
be performed in the background, not influencing the currently
- running system. The update will be activated by a reboot instead,
- similar to
+ running system. The update will be activated by a reboot. This concept
+ is similar to
<ulink
url="https://rpm-ostree.readthedocs.io/en/latest/";>rpm-ostree</ulink>
or CoreOS' previous Container OS. However
<emphasis remap='B'>transactional-update</emphasis> is not another
@@ -100,7 +100,8 @@
<para>
The machine can be powered off at any time. When powered on
again either the unmodified old state or the new state is
- active, but no state in between.
+ active. It is not possible to have a running system in an
+ intermediate state.
</para>
</listitem>
</itemizedlist>
@@ -125,10 +126,10 @@
<section id="tu-introduction-reason">
<title>Use Cases</title>
<para>
- As Linux distributions are evolving over the years, new concepts are
- appearing such rolling releases, containers, embedded systems or long
+ As Linux distributions are evolving, new concepts are
+ emerging, such rolling releases, containers, embedded systems or long
time support releases. While the classical update mechanisms are
- probably perfectly fine for a regular desktop user or a conventional
+ probably perfectly fine for a regular desktop users or a conventional
server system, the following example use cases may give an indication
why an even more error-proof system may be desirable:
</para>
@@ -163,8 +164,8 @@
For these systems transactional-updates provides automatic
updates; snapshots with failed updates will be automatically removed.
Automatic reboots can be triggered using a variety of different reboot
- methods (e.g. rebootmgr, notify, kured or systemd), making the
appliance of
- the updates cluster aware.
+ methods (e.g. rebootmgr, notify, kured or systemd), making the
+ application of the updates cluster aware.
</para>
<para>
To summarize: The update should only be applied if there were no
@@ -523,7 +524,7 @@
<para>
Let's have another look from the perspective while an update is
running. <replaceable>x</replaceable> is the id of the new snapshot
- where the update is currently be performed in,
+ where the update is currently being performed.
<replaceable>x-1</replaceable> is the id of the currently running
snapshot, and <replaceable>x-2</replaceable> is the id of the
snapshot before the currently running one.
@@ -545,7 +546,7 @@
</para>
<para>
<filename>file4</filename> was only added in the new snapshot
- and will be only available there. The currently running system doesn't
+ and will only be available there. The currently running system doesn't
know anything about it.
</para>
<para>
@@ -583,7 +584,8 @@
</para>
</warning>
<para>
- If the <option>--continue</option> is used multiple times to extend a
+ If the <option>--continue</option> option is used multiple times to
+ extend a
new snapshot while the system has not been rebooted, and if that
snapshot is based on the currently active system, then the
merge will only run for the first snapshot; the additional
@@ -598,7 +600,8 @@
indicates the snapshot which was used as a base. As the
<option>lowerdir</option> contains a second entry with number
<emphasis>81</emphasis> it means that the <option>--continue</option>
- has been used before the system was rebooted. Gaps in the number such
+ option has been used before the system was rebooted. Gaps in the
+ numbers such
as seen here may indicate that those snapshots were discarded or a
rollback to snapshot 76 was performed. The lowest snapshot is always
<filename class='directory'>/sysroot/etc</filename>, containing the
@@ -608,7 +611,7 @@
As <filename class='directory'>/etc</filename> is mounted by
<application>dracut</application> during early boot the options have to
be prefixed with <emphasis>/sysroot</emphasis>. The
- <command>x-systemd.</command> options are setting up the volume's
+ <command>x-systemd</command> options are setting up the volume's
<application>systemd</application> dependencies correctly.
</para>
<para>
@@ -669,7 +672,8 @@
<title>Porting to other systems</title>
<para>
Currently <emphasis>snapper</emphasis> is the only supported snapshot
- implementation, however it is prepared to support other (file) systems
+ implementation, however the code base is prepared to support other
+ (file) systems
as long as they provide snapshot functionality and the ability to boot
from specific snapshots.
</para>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/transactional-update-4.1.2/lib/Transaction.cpp
new/transactional-update-4.1.3/lib/Transaction.cpp
--- old/transactional-update-4.1.2/lib/Transaction.cpp 2023-01-23
14:31:20.000000000 +0100
+++ new/transactional-update-4.1.3/lib/Transaction.cpp 2023-02-08
16:06:30.000000000 +0100
@@ -143,7 +143,10 @@
tulog.error("Chrooting to " + bindDir + " for SELinux
relabelling failed: " + std::string(strerror(errno)));
_exit(errno);
}
- if (selinux_restorecon("/var", SELINUX_RESTORECON_RECURSE |
SELINUX_RESTORECON_VERBOSE | SELINUX_RESTORECON_IGNORE_DIGEST) < 0) {
+ unsigned int restoreconOptions = SELINUX_RESTORECON_RECURSE |
SELINUX_RESTORECON_IGNORE_DIGEST;
+ if (tulog.level >= TULogLevel::Info)
+ restoreconOptions |= SELINUX_RESTORECON_VERBOSE;
+ if (selinux_restorecon("/var", restoreconOptions) < 0) {
tulog.error("Relabelling of snapshot /var failed: " +
std::string(strerror(errno)));
_exit(errno);
}
