On Tue, Jan 09, 2024 at 12:14:38PM +0000, Daniel P. Berrangé wrote:
On Tue, Jan 09, 2024 at 01:12:35PM +0100, Peter Krempa wrote:
On Tue, Jan 09, 2024 at 11:41:17 +0000, Daniel P. Berrangé wrote:
On Mon, Jan 08, 2024 at 10:48:58AM +0100, Peter Krempa wrote:
Grrr, this broke because debian-10 was dropped from lcitool and libvirt-python doesn't build trivially neither in debian-11 nor in debian-12.
I might check it later, but honestly got demotivated ...
Yes, it is very frustrating when updating CI with lcitool when youj want to update the version of one particlar distro, and lcitool forces you to also replace a different distro, and the latter cause breakage for some reason. This has hit me time and time and time again.
IMHO it is time to change the policy for lcitool, such that we do NOT remove old distro versions for *at least* 1 year.
This will give us flexibility to update individual distros without having to do every distro in lockstep. It will let us debug problems with certain new distros, without blocking updates of the rest of the world.
Considering that we have stopped aggressively deleting mappings, this feels like a natural next step. Let's just make sure that we don't end up keeping everything around forever.
I'd suggest to flag the older distros which would be deleted with a flag which will produce a warning, when regenerating the CI stuff.
It might be nice to notify that the distro is out of our support policy but without forcing update.
Yep, that's a good idea, as its nice if 'lcitool manifest' warns us about outdated stuff.
Agreed. -- Andrea Bolognani / Red Hat / Virtualization