#3 Go back to 0.10.2 and fix the boot service configuration

defaults/main.yml

-fail2ban_version: '0.9.6'
+fail2ban_version: '0.10.2'

handlers/main.yml

 ---
 # file: roles/fail2ban/handlers/main.yml
 
-- name: "Include Fail2Ban to Boot-List"
-  command: update-rc.d fail2ban defaults
-
 - name: "Restart Fail2Ban"
   service:
     name: 'fail2ban'

tasks/install.yml

@@ -24,18 +24,9 @@
   args:
     chdir: '/tmp/fail2ban-{{ fail2ban_version }}'
 
-- name: "Copy Startup Script"
-  copy:
-    src: '/tmp/fail2ban-{{ fail2ban_version }}/files/debian-initd'
-    dest: '/etc/init.d/fail2ban'
-    mode: '755'
-    remote_src: yes
-  notify:
-    - "Include Fail2Ban to Boot-List"
-
 - name: "Copy Service Script"
   copy:
-    src: '/tmp/fail2ban-{{ fail2ban_version }}/files/fail2ban.service'
+    src: '/tmp/fail2ban-{{ fail2ban_version }}/build/fail2ban.service'
     dest: '/lib/systemd/system/fail2ban.service'
     mode: '644'
     remote_src: yes
@@ -60,3 +51,8 @@
     - 'fail2ban-server'
     - 'fail2ban-testcases'
   ignore_errors: true
+
+- name: "Enable Fail2Ban as a Boot Service"
+  service:
+    name: 'fail2ban'
+    enabled: 'yes'