Actions
Feature #47541
closedadd no-systemd argument to zap
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
octopus,nautilus
Description
In some container deployment scenarios, systemd services are not
used, so the no-systemd parameter is useful.
Updated by Jan Fajerski over 3 years ago
- Status changed from New to Fix Under Review
- Backport set to octopus,nautilus
- Pull request ID set to 37221
Updated by Jan Fajerski over 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Jan Fajerski over 3 years ago
- Copied to Backport #47845: octopus: add no-systemd argument to zap added
Updated by Jan Fajerski over 3 years ago
- Copied to Backport #47846: nautilus: add no-systemd argument to zap added
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions