Blame SOURCES/0533-units-order-cryptsetup-pre.target-before-cryptsetup..patch

17b0f1
From acf59b657e23e3b5b0f038823fe57dcfb4f914a4 Mon Sep 17 00:00:00 2001
17b0f1
From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= <zbyszek@in.waw.pl>
17b0f1
Date: Tue, 5 Sep 2017 09:14:51 +0200
17b0f1
Subject: [PATCH] units: order cryptsetup-pre.target before cryptsetup.target
17b0f1
17b0f1
Normally this happens automatically, but if it happened that both targets were
17b0f1
pulled in, even though there were no cryptsetup units, they could be started
17b0f1
in reverse order, which would be somewhat confusing. Add an explicit ordering
17b0f1
to avoid this potential issue.
17b0f1
17b0f1
Cherry-picked from: 947d21171bdd8375db6482bc7d758d74b27f7dd4
17b0f1
Resolves: #1384014
17b0f1
---
17b0f1
 units/cryptsetup-pre.target | 1 +
17b0f1
 1 file changed, 1 insertion(+)
17b0f1
17b0f1
diff --git a/units/cryptsetup-pre.target b/units/cryptsetup-pre.target
17b0f1
index 65353419fc..42e35dd4e4 100644
17b0f1
--- a/units/cryptsetup-pre.target
17b0f1
+++ b/units/cryptsetup-pre.target
17b0f1
@@ -9,3 +9,4 @@
17b0f1
 Description=Encrypted Volumes (Pre)
17b0f1
 Documentation=man:systemd.special(7)
17b0f1
 RefuseManualStart=yes
17b0f1
+Before=cryptsetup.target