update to lxc-5.0.2

[lxc.git] / debian / patches / pve / 0001-PVE-Config-lxc.service-start-after-a-potential-syslo.patch

diff --git a/debian/patches/pve/0001-PVE-Config-lxc.service-start-after-a-potential-syslo.patch b/debian/patches/pve/0001-PVE-Config-lxc.service-start-after-a-potential-syslo.patch
index 09e74ffe60e828cd383f084959c23d5a989e185a..ca7d598825de1c57d293ce8b439022ee4146a042 100644 (file)
--- a/debian/patches/pve/0001-PVE-Config-lxc.service-start-after-a-potential-syslo.patch
+++ b/debian/patches/pve/0001-PVE-Config-lxc.service-start-after-a-potential-syslo.patch
@@ -1,7 +1,7 @@
 From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
 From: Wolfgang Bumiller <w.bumiller@proxmox.com>
 Date: Fri, 10 Feb 2017 09:13:40 +0100
-Subject: [PATCH lxc] PVE: [Config] lxc.service: start after a potential
+Subject: [PATCH 1/3] PVE: [Config] lxc.service: start after a potential
  syslog.service
 
 We could add this as a snippet from pve-container instead.
@@ -23,3 +23,6 @@ index 397a6c4d0..6924374d9 100644
  Wants=lxc-net.service
  Documentation=man:lxc-autostart man:lxc
  
+-- 
+2.30.2
+