On Mon, Aug 08, 2022 at 11:38:35AM +0200, Lukas Märdian wrote:
> 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.
In general, adding new entirely new packages is considered OK from a
regression risk perspective. But note that once it's in, you don't get a
free pass on updating the package any more, since at that point
regression risk exists again.
I haven't looked into the proposal in detail, so I don't know whether I
would prefer the integrated approach over not splitting it out.
However, we generally don't just add new packages to a stable release
updates pocket automatically. A justification is still needed, and then
the SRU team will consider it on a case-by-case basis.
You have provided that already, but I'm not completely clear on the
justification here:
> Unfortunately, they're currently blocked on this because 22.04 doesn't
> ship systemd-repart. The upstream CI uses Github Actions which runs on
> Ubuntu Jammy and will do so until the next Ubuntu LTS is released.
Can Github Actions not install software from any other source? For
example, what if you were to put systemd-repart as a new package into a
PPA, or into jammy-backports? Would Github Actions really be incapable
of using this?
