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

[Robie Basak]

On Wed, Aug 17, 2022 at 03:09:45PM +0100, Luca Boccassi wrote:
> The difference is that here it's the upstream maintainers asking for
> this, not just users. From our point of view, not including repart in
> Jammy was an oversight - there was really no reason to keep it
> disabled, other than we noticed and asked for it too late, and we
> should have asked for it sooner.
> Not being able to rely on repart because it's absent from Jammy means
> we have to accrue significant and expensive technical debt in mkosi,
> that is making everything very fragile, so at some point we might just
> have to cut our losses and leave Jammy unsupported - which would cause
> a lot of friction and grief, given it will be popular and widely used
> for many years among developers, so we are trying hard to avoid that if
> possible.

This doesn't make sense to me.

You're missing a (in fact, your own) binary CLI tool in Jammy. And
presumably you think the tool is mature enough that you will not need to
change the binary CLI tool again, since you're asking for a one-off SRU
for it.

That's all, right? So build it once, put it in a PPA, adjust your
tooling to use it, and you're done. Where's the "significant and
expensive technical debt"?

I still fail to see how situation is any different to any other
developer having dependencies that aren't in the archive.

Robie
-------------- 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/66a3a38a/attachment-0001.sig>