From df90f8ac01101337675a7100e7697f4055db4810 Mon Sep 17 00:00:00 2001
From: Praveen Arimbrathodiyil <praveen@debian.org>
Date: Wed, 15 Feb 2017 11:31:43 +0530
Subject: [PATCH] change gitlab.target to gitlab.service

---
 debian/README.Debian | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/debian/README.Debian b/debian/README.Debian
index bbfa3fa7db..36939a58d9 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -77,7 +77,7 @@ how to fix possible problems. Another one is:
 
 To see service status with systemd, you can use:
 
-    $ systemctl status gitlab.target
+    $ systemctl status gitlab.service -l
     $ systemctl status gitlab-unicorn.service -l
     $ systemctl status gitlab-sidekiq.service -l
     $ systemctl status gitlab-workhorse.service -l
@@ -98,7 +98,7 @@ Migrating from non-Debian gitlab
  2. Install Debian gitlab:
       $ apt-get install gitlab
  3. Stop gitlab services:
-      $ systemctl stop gitlab.target
+      $ systemctl stop gitlab.service
  4. Rename your old database to gitlab_production and set the user gitlab as
     its owner and the owner of all its tables, sequences and views
       $ su - postgres
@@ -125,7 +125,7 @@ Migrating from non-Debian gitlab
       # su gitlab
       $ /usr/share/gitlab-shell/bin/create-hooks
  12. Start gitlab:
-       $ systemctl start gitlab.target
+       $ systemctl start gitlab.service
  13. Check the installation:
       $ runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat /etc/gitlab/gitlab-debian.conf) && rake gitlab:check RAILS_ENV=production'