Hello,
I have now created an issue in the systemd repository where this can
be tracked further as this seems to be something which would fit into
sd-sysupdate itself: https://github.com/systemd/systemd/issues/30855
Kind regards, Nils
On Di, 02.01.24 14:40, Nils Kattenbeck (nilskem...@gmail.com) wrote:
> > > does sysupdate currently support any way to slowly roll out updates
> > > where the server providing the files can be in control? [...]
> >
> > This is currently not available, no.
> >
> > The idea so far was always that th
> > does sysupdate currently support any way to slowly roll out updates
> > where the server providing the files can be in control? [...]
>
> This is currently not available, no.
>
> The idea so far was always that the server is dumb, and the client
> picks the release it wants.
I feel like it wou
On Di, 02.01.24 13:11, Simon McVittie (s...@collabora.com) wrote:
> Prior art: Debian/Ubuntu apt does slow rollout for packages like
> this, with simple filesystem-based http mirrors combined with "smart"
> clients. It works by adding a Phased-Update-Percentage field to the
> metadata of each pack
On Tue, 02 Jan 2024 at 11:16:15 +0100, Lennart Poettering wrote:
> The idea so far was always that the server is dumb, and the client
> picks the release it wants.
>
> I have thought about this usecase a while back, and my thinking was
> that such a staged update logic should be driven by the mach
On Mi, 20.12.23 19:04, Nils Kattenbeck (nilskem...@gmail.com) wrote:
> Hey everyone,
>
> does sysupdate currently support any way to slowly roll out updates
> where the server providing the files can be in control? This would be
> used to slowly make a new version available and have it at e.g. 1%
Hello and happy New Year,
I tried to solve this by adding percent-specifiers as query parameters to
the Path= property of the sysupdate definition though to my dismay I had to
find out that they are discarded by the sd-import logic. Removing this
restriction could solve this problem as one could e
Hey everyone,
does sysupdate currently support any way to slowly roll out updates
where the server providing the files can be in control? This would be
used to slowly make a new version available and have it at e.g. 1%
adoption for a day to monitor regressions before increasing the
coverage. I was
