Wednesday 17 August 2022

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

> > 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.

I can work on adding a new package and update the MR. But it needs to
be removed for the next release, with the appropriate
conflicts+replaces that Ubuntu will need to carry as delta (I am not
going to add them in Debian). It's really a lot of work for nothing,
given the risk is really zero - it's a new command line program that is
inhert and doesn't do anything until it's called manually...

--
Kind regards,
Luca Boccassi