Re: [PATCH 2/3] tests/lcitool: Update openSUSE to version 16

["Daniel P. Berrangé" <berrange@redhat.com>]

On Tue, Mar 17, 2026 at 03:18:36PM +0000, Alex Bennée wrote:
> Thomas Huth <thuth@redhat.com> writes:
> 
> > On 16/03/2026 15.43, Alex Bennée wrote:
> >> Thomas Huth <thuth@redhat.com> writes:
> >> 
> >>> From: Thomas Huth <thuth@redhat.com>
> >>>
> >>> The first version of openSUSE 15 has been released in 2018, and
> >>> according to our support policy, we "support the most recent major
> >>> version at all times for up to five years after its initial release."
> >>>
> >>> Since openSUSE 16 has been released a while ago, and openSUSE is
> >>> clearly older than 5 years already, it's time to update to version 16
> >>> now.
> >>>
> >>> Signed-off-by: Thomas Huth <thuth@redhat.com>
> >>> ---
> >>>   configure                  |  1 -
> >>>   tests/lcitool/mappings.yml | 58 --------------------------------------
> >>>   tests/lcitool/refresh      |  2 +-
> >>>   3 files changed, 1 insertion(+), 60 deletions(-)
> >>>
> >>> diff --git a/configure b/configure
> >>> index cd1dadd8bb2..f3603fd9160 100755
> >>> --- a/configure
> >>> +++ b/configure
> >>> @@ -929,7 +929,6 @@ if ! check_py_version "$python"; then
> >>>     error_exit "Cannot use '$python', Python >= 3.9 is required." \
> >>>                "Use --python=/path/to/python to specify a supported Python." \
> >>>                "Maybe try:" \
> >>> -             "  openSUSE Leap 15.3+: zypper install python39" \
> >>>                "  CentOS: dnf install python3.12"
> >>>   fi
> >>>   diff --git a/tests/lcitool/mappings.yml
> >>> b/tests/lcitool/mappings.yml
> >>> index 60618971584..62fe60d047f 100644
> >>> --- a/tests/lcitool/mappings.yml
> >>> +++ b/tests/lcitool/mappings.yml
> >>> @@ -3,70 +3,17 @@ mappings:
> >>>     bindgen:
> >>>       Ubuntu2204:
> >>>   -  flake8:
> >>> -    OpenSUSELeap15:
> >>> -
> >>>     meson:
> >>> -    OpenSUSELeap15:
> >>>       # Use Meson from PyPI wherever Rust is enabled
> >>>       Debian:
> >>>       Fedora:
> >>>       Ubuntu:
> >>>   -  python3:
> >>> -    OpenSUSELeap15: python311-base
> >>> -
> >>> -  python3-PyYAML:
> >>> -    OpenSUSELeap15:
> >>> -
> >>> -  python3-devel:
> >>> -    OpenSUSELeap15: python311-devel
> >>> -
> >>> -  python3-docutils:
> >>> -    OpenSUSELeap15:
> >>> -
> >>> -  python3-numpy:
> >>> -    OpenSUSELeap15:
> >>> -
> >>> -  python3-opencv:
> >>> -    OpenSUSELeap15:
> >>> -
> >>> -  python3-pillow:
> >>> -    OpenSUSELeap15:
> >>> -
> >>> -  python3-pip:
> >>> -    OpenSUSELeap15: python311-pip
> >>> -
> >>> -  python3-pillow:
> >>> -    OpenSUSELeap15:
> >>> -
> >>> -  python3-selinux:
> >>> -    OpenSUSELeap15:
> >>> -
> >>> -  python3-setuptools:
> >>> -    OpenSUSELeap15: python311-setuptools
> >>> -
> >>> -  python3-sphinx:
> >>> -    OpenSUSELeap15:
> >>> -
> >>> -  python3-sphinx-rtd-theme:
> >>> -    OpenSUSELeap15:
> >>> -
> >>> -  python3-sqlite3:
> >>> -    OpenSUSELeap15: python311
> >>> -
> >>>     python3-tomli:
> >>>       # test using tomllib
> >>>       apk:
> >>>       Fedora:
> >>>       Debian12:
> >>> -    OpenSUSELeap15:
> >>> -
> >>> -  python3-venv:
> >>> -    OpenSUSELeap15: python311-base
> >>> -
> >>> -  python3-wheel:
> >>> -    OpenSUSELeap15: python311-wheel
> >>>       rust:
> >>>       Debian12: rustc-web
> >>> @@ -79,12 +26,7 @@ pypi_mappings:
> >>>       default: meson==1.8.1
> >>>       # Drop packages that need devel headers
> >>> -  python3-numpy:
> >>> -    OpenSUSELeap15:
> >>> -
> >>> -  # see above
> >>>     python3-tomli:
> >>>       apk:
> >>>       Fedora:
> >>>       Debian12:
> >>> -    OpenSUSELeap15:
> >> I'm unsure about the mappings stuff just because I'm not sure what
> >> it is
> >> for. Does it supplement the mappings in libvirt-ci itself?
> >
> > Yes, that's how I understood it. Since this is just an extension to
> > the mappings from libvirt-ci, I think we can safely remove those
> > mappings on the QEMU side now.
> 
> Ahh ok - I've always been waiting for the libvirt-ci MRs to go through.

That's the right approach in general. This qemu local mappings.yml
file was just for some QEMU specific overrides that are not appropriate
for upstream libvirt-ci.git  mappings. Ideally we should rarely, or even
never, use the local mappings as that tends to defeat the benefit of
sharing the info across many projects.

With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|