Bug#1025618: cloud-init and firewalld systemd unit files have ordering cycles
Hi Ross,
> Should we consider adding "Conflicts: firewalld" to cloud-init before
> the freeze? That's not optimal of course, but it'd prevent a user from
> ending up in this situation for now.
Is there a way to bypass "Conflicts" and install such packages anyway,
in case the user finds a way to customize the configuration in a way that
fits their needs?
For example, on one of my systems I kept cloud-init installed for now, but
I disabled and masked cloud-init.service.
Cheers!
Guillaume
Reply to: