Summary: | app-emulation/cloud-init needs separate distro profiles for OpenRC and systemd | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Reuben Martin <reuben.m> |
Component: | Current packages | Assignee: | Matthew Thode ( prometheanfire ) <prometheanfire> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | alunduil, eva, genzilla |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Reuben Martin
2017-02-23 18:39:07 UTC
yes, upstream cloud-init needs a bit of love in that area and in the network config area, we are still using the 'old' netconfig stuff. 3 Years have passed and it seems that the issue remains. I just ran into it today with app-emulation/cloud-init-20.1 shouldn't a patch that's applied based on use-flags suffice to rewrite the rc-update & co lines with systemd specifics? I faced this issue today as well, I hadn't even thought that systemd-networkd wouldn't be supported when a systemd system usually does use it. Is this pretty much waiting on patches to be submitted to upstream cloud-init or should them be done in portage? ya, patches are needed at this point |