Overview
Request 852338 accepted
Due to a gdal bug in GeoTiff handling, some packages do require gdal >=3.1. So I would like
to ask for an upgrade of gdal to version 3.2.0 for Leap 15.3.
See https://github.com/qgis/QGIS/issues/36699#issuecomment-633539864 .
The background is, that I would love to see qgis in Leap 15.3, and this is a prerequisite.
- Created by manfred999
- In state accepted
Request History
manfred999 created request
Due to a gdal bug in GeoTiff handling, some packages do require gdal >=3.1. So I would like
to ask for an upgrade of gdal to version 3.2.0 for Leap 15.3.
See https://github.com/qgis/QGIS/issues/36699#issuecomment-633539864 .
The background is, that I would love to see qgis in Leap 15.3, and this is a prerequisite.
tzotsos accepted review
Looks good, thank you
bigironman accepted review
LGTM
bigironman approved review
LGTM
bigironman accepted request
LGTM
Submitting to Backport is not a 100% target to see gdal upgrade for 15.3. The real target is SLE. And the first step for that is opening a bug against 15.2 to request upgrade of gdal. Especially if sle binaries become leap one.
In this case submitting to openSUSE:Backports:SLE-15-SP3 is correct since gdal isn't in SLE and Leap 15.3 inherits binaries from SLE and openSUSE:Backports:SLE-15-SP3.
But to make it more easy for you, just submit updates or new packages to openSUSE:Leap:15.3 and the request will be automatically routed to the correct project (SLE or Backports).
I naively opened a request for openSUSE:Leap:15.3, and this got re-routed to openSUSE:Backports:SLE-15-SP3. Doing it against Leap 15.2 did not feel correct, as Leap 15.2 is already released. And updates for a released distro would have to be done with a maintenance request? As my intention was to do legwork for new packages, I went for 15.3.
You still can submit updates to openSUSE:Leap:15.2:Update if needed.
The process for Leap 15.3 has changed since Leap 15.3 now inherits binaries from SLE-15-SP3 and openSUSE:Backports:SLE-15-SP3. So submits to openSUSE:Leap:15.3 are ending up in openSUSE:Backports:SLE-15-SP3. So just keep submitting to openSUSE:Leap:15.3 :) Therefore it is also helpful to add build target openSUSE:Backports:SLE-15-SP3 to see if package builds successfully. Since the build target is missing in this request I checked build of gdal for openSUSE:Backports:SLE-15-SP3 and it builds successfully, so I'm going to accept the request. Thank you for the updated package.
I did a request to 15.3 some days ago and it went to SUSE:SLE-15-SP2:Update :-)
https://build.opensuse.org/request/show/848621
I don't understand Leap anymore and don't find this situation helpful, but probably we simply have to wait and see what happens?
Indeed, the current situation is about Leap 15.3 is confusing since it inherits the binaries from SLE-15-SP3 and openSUSE:Backports:SLE-15-SP3.
But submitting just to openSUSE:Leap:15.2 should automatically re-direct the request to the correct project (SLE or Backports). In your case unfortunately the setup of this automation was wrong during that point in time so it got redirected to SUSE:SLE-15-SP2:Update instead of SUSE:SLE-15-SP3.
If a package is already in SLE-15-SP3, like in your case with ImageMagick, submitting updates to openSUSE:Leap:15.3 will be redirected to SUSE:SLE-15-SP3 (and after release of SLE-15-SP3 and Leap 15.3 redirected to SLE-15-SP3:Update).
So should I redo this submit to SUSE:SLE-15-SP3 when I want it in 15.3?