I recently talked to bluca on IRC about the enablement of "systemd-repart" [2] in Jammy.
It is already enabled in Kinetic. The rational being that they (upstream systemd) want to make use of it for their mkosi image builder running on GitHub Actions Jammy images. See [0] for a detailed explanation.
I explained, that we cannot enable new features after feature freeze much less after final release, usually.
But we agreed it should be brought up for discussion in this case. bluca already provided a full SRU bug [0] and merge proposal [1].
It seems to be a low-risk change bringing value to our users, as they could opt-in to using it.
I already suggested, that one option to get such an exception (by further reducing the risk involved) could be to ship systemd-repart in a separate binary package in universe, not installed by default.
And not as part of the primary "systemd" package in main, as currently suggested.
We would like to get more opinions on that, especially from release/SRU team members.
Cheers,
Lukas
[0] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932
[1] https://code.launchpad.net/~bluca/ubuntu/+source/systemd/+git/systemd/+merge/427557
[2] https://www.freedesktop.org/software/systemd/man/systemd-repart.service.html
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
