On 12/12/2022 6:44 AM, Sam Hartman wrote:
>> From my quick read: Michael Biebl proposes dropping >> network-pre.target Ross> from cloud-init's After=, and replacing it with each of the Ross> config backends that cloud-init supports. This sounds pretty Ross> reasonable, but also like something that upstream should Ross> address first.Why wait for upstream? It's a bug affecting Debian users, our systemd maintainer has a solution that you (and I) think is reasonable. The symptom is quite serious. We often make changes before upstream in situations like that, especially when the alternative is: Ross> Should we consider adding "Conflicts: firewalld" to cloud-init Ross> before the freeze? That's not optimal of course, but it'd Ross> prevent a user from ending up in this situation for now. I'd much rather see Debian local changes than conflicts.
We should simply move this discussion to an upstream pull request rather than wait passively for their response. I agree that diverging from upstream is preferable to unnecessary conflicts, but it shouldn't be done without first consulting with upstream on our proposed solution.
noah
