Enablement of systemd-repart in Jammy LTS (post-release)

[Robie Basak]

On Wed, Aug 17, 2022 at 02:02:57PM +0100, Luca Boccassi wrote:
> > > 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?
> 
> This is needed by users too. Forcing users to install all systemd
> packages from an unsupported, random third party PPA that doesn't
> provide security updates would not be a good idea for production
> workstations, I think.

This justification applies equally to all software that any user might
want backported to jammy-updates, though. What makes this request
special enough that it should be granted an exception?

To be clear, this isn't a -1 from me. It's a "Needs Information". Maybe
accepting this in a Jammy SRU is justified. But if so, I don't think the
case has been made yet, and that's why I'm asking further questions.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20220817/ac21036b/attachment.sig>