In one week, 2025-03-18, or slightly later, in collaboration with Scott
Logan (FAS: cottsay), I plan to update spatialindex from 1.9.3 to 2.1.0
in F43/Rawhide[1].
Upstream reports that “There are no significant major enhancements or
refactorings that should change any behaviors. It had been a long time
(almost 5 years!) since a release and 2.0.0 was the next version
number...”[2][3]
Nevertheless, the SONAME version has changed, and therefore I plan to
use provenpackager privilege to rebuild the following packages in the
same side tag:
- minetest
- qgis
Testing in COPR[4] revealed no incompatibilities. This impact check also
covered the python-Rtree package, which will not need to be rebuilt
because it does not link the library, instead loading it at runtime
using Python’s ctypes module.
A similar update for Fedora 42 appears technically feasible, but isn’t
planned because it doesn’t seem justified at this point in the release
cycle.
– Ben Beasley (FAS: music)
[1] https://src.fedoraproject.org/rpms/spatialindex/pull-request/3
[2] https://github.com/libspatialindex/libspatialindex/releases/tag/2.0.0
[3] https://github.com/libspatialindex/libspatialindex/releases/tag/2.1.0
[4] https://copr.fedorainfracloud.org/coprs/music/spatialindex/packages/
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
