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: > > On Thu, Dec 14, 2023 at 09:28:15 +0100, Michal Privoznik wrote: > > > Green pipeline: > > > > > > https://gitlab.com/MichalPrivoznik/libvirt/-/pipelines/1106643445 > > > > > > Michal Prívozník (2): > > > ci: integration: Switch upstream integration tests to Fedora 39 > > > > For future reference, please note that the integration test suite makes > > use of artifacts from libvirt/libvirt-perl and libvirt/libvirt-python > > projects, which thus must be bumped to new Fedora prior to bumping the > > main project. Right. We keep forgetting that. I've just posted patches[1] that add notes to the file, so hopefully that doesn't happen again. > > 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. >From a quick look, the problem seems to be related to the somewhat recent change in Debian (and other distros? Or was it Python itself?) where 'pip install' is disabled outside of venvs. IIRC lcitool has been patched to work around it already. > I might check it later, but honestly got demotivated ... No, that's fair. I'll take a better look later today. [1] https://lists.libvirt.org/archives/list/devel@xxxxxxxxxxxxxxxxx/thread/CKXFH6PIV2YXROYNJLA2OILTT6VN4V6U/ -- Andrea Bolognani / Red Hat / Virtualization _______________________________________________ Devel mailing list -- devel@xxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxx
