Re: systemd-sysupdate and systemd-sysext images

[Thorsten Kukuk <kukuk@xxxxxxxx>]

On Mon, Nov 4, 2024 at 11:22 AM Thorsten Kukuk <kukuk@xxxxxxxx> wrote:

> Ah, I forgot about that new utility during my vacation...
> But updatectl does not solve my problems, see above.
> It's still centric about this "there is a base OS image and all
> extensions have the same image version", even if it has a nice
> interface.

If you create a list of sysupdate features without a base OS image,
and you have no feature enabled:

# updatectl
Failed to get current version for 'host': No data available

# updatectl check
Failed to call CheckNew for 'host': No such file or directory
No updates available.

# updatectl features
Failed to lookup feature for 'host': No data available

So I cannot even list the available features to enable them.
And if I try to enable a feature since I know them:

# updatectl enable gcc
Failed to call SetFeatureEnabled for 'host': Invalid arguments 'sbt'
to call org.freedesktop.sysupdate1.Target.SetFeatureEnabled(),
expecting 'sit'.

What I don't understand:
The .transfer file can have a list of Features, but since
MatchPattern= is required, you need a single .transfer file for every
.feature file.
In which case can you use more than one "Feature" in a .transfer file,
and what does this look like?

Thanks,
Thorsten

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies
SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461
Nuernberg, Germany
Managing Director: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB
36809, AG Nürnberg)