Package: cloud-init Version: 24.3.1-1 Severity: normal Tags: patch Dear Maintainer,
Initialisation of cloud-init on non-systemd installations is broken. A fresh installation produces Setting up cloud-init (25.3-2)… insserv: FATAL: service cloud-init has to be enabled to use service cloud-config The simple patch below fixes the superficial issue, but I am unsure it addresses the complete situation. Version 24.3.1-1 replaces /etc/init.d/cloud-init with /etc/init.d/cloud-init-main. However, files in /etc/init.d are conffiles and the original /etc/init.d/cloud-init could persist on installations that are being upgraded. I think dpkg-maintscript-helper(1) needs to be used to remove or rename the original, depending on the intention. Also, I notice the new /etc/init.d/cloud-init-main is actually no-op. Wouldn't it be simpler to just remove /etc/init.d/cloud-init, /etc/init.d/cloud-init-main and LSB header references to them? If I have understood that correctly, I am happy to work up a suitable patch. Thanks for your thoughts and insight. Mark diff -u /etc/init.d/cloud-config /etc/init.d/cloud-config.orig --- /etc/init.d/cloud-config.orig 2026-02-03 07:22:48.640835483 +0000 +++ /etc/init.d/cloud-config 2026-02-03 07:23:20.448107273 +0000 @@ -1,7 +1,7 @@ #! /bin/sh ### BEGIN INIT INFO # Provides: cloud-config -# Required-Start: $local_fs $remote_fs cloud-init cloud-init-local +# Required-Start: $local_fs $remote_fs cloud-init-main cloud-init-local # Required-Stop: $remote_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 Diff finished. Tue Feb 3 07:27:35 2026
