On Mon, Jan 08, 2024 at 10:48:58AM +0100, Peter Krempa wrote: > On Mon, Jan 08, 2024 at 10:35:53 +0100, Peter Krempa wrote: > > I've approved and merged > > > > https://gitlab.com/libvirt/libvirt-perl/-/merge_requests/109 > > > > and posted > > > > https://gitlab.com/libvirt/libvirt-python/-/merge_requests/130 > > > > which will need to be approved. > > > > This should fix the following integration test failure: > > > > https://gitlab.com/libvirt/libvirt/-/jobs/5880074910 > > 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. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ Devel mailing list -- devel@xxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxx
