Hello community,

here is the log from the commit of package systemd for openSUSE:Factory checked 
in at 2014-08-03 15:36:33
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/systemd (Old)
 and      /work/SRC/openSUSE:Factory/.systemd.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "systemd"

Changes:
--------
--- /work/SRC/openSUSE:Factory/systemd/systemd-mini.changes     2014-07-31 
21:49:16.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.systemd.new/systemd-mini.changes        
2014-08-03 15:36:35.000000000 +0200
@@ -1,0 +2,7 @@
+Fri Aug  1 09:53:30 UTC 2014 - [email protected]
+
+- Add upstream patches
+  0007-hwdb-update.patch
+  1061-rules-allow-systemd-to-manage-loop-device-partitions.patch
+
+-------------------------------------------------------------------
systemd.changes: same change

New:
----
  0007-hwdb-update.patch
  1061-rules-allow-systemd-to-manage-loop-device-partitions.patch

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

Other differences:
------------------
++++++ systemd-mini.spec ++++++
--- /var/tmp/diff_new_pack.EhPsUs/_old  2014-08-03 15:36:40.000000000 +0200
+++ /var/tmp/diff_new_pack.EhPsUs/_new  2014-08-03 15:36:40.000000000 +0200
@@ -759,6 +759,8 @@
 Patch365:       0003-keymap-Annotate-all-micmute-workarounds.patch
 # PATCH-FIX-SUSE Provide the /var/lock/subsys at start (bnc#889357)
 Patch366:       tomcat6-var-lock-subsys-legacy.patch
+# PATCH-FIX-UPSTREAM added at 2014/08/01
+Patch367:       0007-hwdb-update.patch
 
 # UDEV PATCHES
 # ============
@@ -886,6 +888,8 @@
 Patch1059:      1059-udev-fixup-commit-dd5eddd28a74a49607a8fffcaf960040db.patch
 # PATCH-FIX-SUSE 
1060-udev-use-device-mapper-target-name-for-btrfs-device-ready.patch
 Patch1060:      
1060-udev-use-device-mapper-target-name-for-btrfs-device-ready.patch
+# PATCH-FIX-UPSTREAM 
1061-rules-allow-systemd-to-manage-loop-device-partitions.patch
+Patch1061:      1061-rules-allow-systemd-to-manage-loop-device-partitions.patch
 
 %description
 Systemd is a system and service manager, compatible with SysV and LSB
@@ -1411,6 +1415,7 @@
 %patch364 -p0
 %patch365 -p0
 %patch366 -p1
+%patch367 -p0
 
 # udev patches
 %patch1001 -p1
@@ -1494,6 +1499,7 @@
 %endif
 %patch1059 -p0
 %patch1060 -p1
+%patch1061 -p0
 
 # ensure generate files are removed
 rm -f units/emergency.service

++++++ systemd.spec ++++++
--- /var/tmp/diff_new_pack.EhPsUs/_old  2014-08-03 15:36:40.000000000 +0200
+++ /var/tmp/diff_new_pack.EhPsUs/_new  2014-08-03 15:36:40.000000000 +0200
@@ -754,6 +754,8 @@
 Patch365:       0003-keymap-Annotate-all-micmute-workarounds.patch
 # PATCH-FIX-SUSE Provide the /var/lock/subsys at start (bnc#889357)
 Patch366:       tomcat6-var-lock-subsys-legacy.patch
+# PATCH-FIX-UPSTREAM added at 2014/08/01
+Patch367:       0007-hwdb-update.patch
 
 # UDEV PATCHES
 # ============
@@ -881,6 +883,8 @@
 Patch1059:      1059-udev-fixup-commit-dd5eddd28a74a49607a8fffcaf960040db.patch
 # PATCH-FIX-SUSE 
1060-udev-use-device-mapper-target-name-for-btrfs-device-ready.patch
 Patch1060:      
1060-udev-use-device-mapper-target-name-for-btrfs-device-ready.patch
+# PATCH-FIX-UPSTREAM 
1061-rules-allow-systemd-to-manage-loop-device-partitions.patch
+Patch1061:      1061-rules-allow-systemd-to-manage-loop-device-partitions.patch
 
 %description
 Systemd is a system and service manager, compatible with SysV and LSB
@@ -1406,6 +1410,7 @@
 %patch364 -p0
 %patch365 -p0
 %patch366 -p1
+%patch367 -p0
 
 # udev patches
 %patch1001 -p1
@@ -1489,6 +1494,7 @@
 %endif
 %patch1059 -p0
 %patch1060 -p1
+%patch1061 -p0
 
 # ensure generate files are removed
 rm -f units/emergency.service

++++++ 0007-hwdb-update.patch ++++++
++++ 1910 lines (skipped)

++++++ 1061-rules-allow-systemd-to-manage-loop-device-partitions.patch ++++++
>From b5df2eabf3fdd3e1663bc4c948812472084f3e96 Mon Sep 17 00:00:00 2001
From: Kevin Wells <[email protected]>
Date: Thu, 31 Jul 2014 17:38:21 +0200
Subject: [PATCH] rules: allow systemd to manage loop device partitions

SYSTEMD_READY is currently set to 0 for all loop devices (loop[0-9]*)
that do not have a backing_file. Partitioned loop devices (ex. loop0p1),
however, are matched by this rule and excluded by systemd even though
they are active devices.

This change adds an additional check to the rule, ensuring that only
top level loop devices (loop[0-9]+$) are excluded from systemd.
---
 rules/99-systemd.rules.in |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git rules/99-systemd.rules.in rules/99-systemd.rules.in
index c3ef81b..aa435c4 100644
--- rules/99-systemd.rules.in
+++ rules/99-systemd.rules.in
@@ -23,7 +23,7 @@ SUBSYSTEM=="block", ENV{DEVTYPE}=="disk", KERNEL=="md*", 
TEST!="md/array_state",
 SUBSYSTEM=="block", ENV{DEVTYPE}=="disk", KERNEL=="md*", 
ATTR{md/array_state}=="|clear|inactive", ENV{SYSTEMD_READY}="0"
 
 # Ignore loop devices that don't have any file attached
-SUBSYSTEM=="block", KERNEL=="loop[0-9]*", TEST!="loop/backing_file", 
ENV{SYSTEMD_READY}="0"
+SUBSYSTEM=="block", KERNEL=="loop[0-9]*", ENV{DEVTYPE}=="disk", 
TEST!="loop/backing_file", ENV{SYSTEMD_READY}="0"
 
 # Ignore nbd devices in the "add" event, with "change" the nbd is ready
 ACTION=="add", SUBSYSTEM=="block", KERNEL=="nbd*", ENV{SYSTEMD_READY}="0"
-- 
1.7.9.2

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

Reply via email to