lvm2/systemd is resolved

diff --git a/728486_systemd_and_lvm_incompatibility/draft-dla b/728486_systemd_and_lvm_incompatibility/draft-dla
deleted file mode 100644 (file)
index 2c78183..0000000
--- a/728486_systemd_and_lvm_incompatibility/draft-dla
+++ /dev/null
@@ -1,26 +0,0 @@
-When systemd is in operation in conjunction with lvm and lvmetad is
-not in use, lvchange -aay must be called after udevadm --settle which
-is provided by systemd-udev-settle.service, and before (and after)
-encrypted devices are configured (cryptsetup.target).
-
-==COMMENT==
-Is there any case where udevadm --settle would be required after the
-encrypted devices are configured? Does cryptsetup.target ensure that
-udev has triggered the appropriate rules for the newly configured
-encrypted devices?
-==END COMMENT==
-
-The patch prepared by Michael Stapelberg <stapelberg@debian.org> in
-http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728486#163 installs
-the two systemd unit files necessary to properly configure lvm devices
-when systemd is running, and additionally configures systemd-tmpfiles.d to
-create the lockfile directories required by systemd.
-
-Therefore, the CTTE:
-
-A. Overides the objection of the maintainer of lvm (Bastian Blank
-<waldi@debian.org>) to this patch, and directs the maintainer to
-accept this patch or alternatively, authorizes an NMU to implement
-this patch.
-
-B. Further discussion

diff --git a/meetings/agenda.txt b/meetings/agenda.txt
index 54ce652c7f4d28f901315b9140ff402e985b53f0..c9cc84f6445b0e94c19feecf24dc4674f25e4a1f 100644 (file)
--- a/meetings/agenda.txt
+++ b/meetings/agenda.txt
@@ -10,8 +10,6 @@
 
 #topic #681419 Depends: foo | foo-nonfree
 
-#topic #719738 lvm2 - Add systemd support
-
 #topic #727708 Decide which init system to pick
 
 #topic Additional Business

diff --git a/resolved_issues/728486_systemd_and_lvm_incompatibility/draft-dla b/resolved_issues/728486_systemd_and_lvm_incompatibility/draft-dla
new file mode 100644 (file)
index 0000000..2c78183
--- /dev/null
+++ b/resolved_issues/728486_systemd_and_lvm_incompatibility/draft-dla
@@ -0,0 +1,26 @@
+When systemd is in operation in conjunction with lvm and lvmetad is
+not in use, lvchange -aay must be called after udevadm --settle which
+is provided by systemd-udev-settle.service, and before (and after)
+encrypted devices are configured (cryptsetup.target).
+
+==COMMENT==
+Is there any case where udevadm --settle would be required after the
+encrypted devices are configured? Does cryptsetup.target ensure that
+udev has triggered the appropriate rules for the newly configured
+encrypted devices?
+==END COMMENT==
+
+The patch prepared by Michael Stapelberg <stapelberg@debian.org> in
+http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728486#163 installs
+the two systemd unit files necessary to properly configure lvm devices
+when systemd is running, and additionally configures systemd-tmpfiles.d to
+create the lockfile directories required by systemd.
+
+Therefore, the CTTE:
+
+A. Overides the objection of the maintainer of lvm (Bastian Blank
+<waldi@debian.org>) to this patch, and directs the maintainer to
+accept this patch or alternatively, authorizes an NMU to implement
+this patch.
+
+B. Further discussion