The Wire · Showcase
GEOSPATIAL STACK GETS BATCH REBUILD ACROSS EXTRA-STAGING
By RepoJournal · Filed · About Arch Linux
Five core mapping and graphics libraries are rolling through staging simultaneously—watch for dependency ripples when these hit stable.
The geospatial desk is pushing a coordinated update wave: GDAL 3.12.4-2 [3], PDAL 2.9.3-2 [5], and OpenSceneGraph 3.6.5-32 [4] are all moving through extra-staging-x86_64, with Scribus 1.6.6-3 [1] and QMapShack 1.20.1-2 [2] following in their wake. These aren't minor point bumps—GDAL and PDAL handle the heavy lifting for geospatial processing pipelines, and any downstream breakage will cascade fast. OpenSceneGraph's rebuild suggests a compiler or dependency chain fix rather than a feature release, which usually means something upstream forced the hand. Watch QMapShack and Scribus closely; both depend on the lower-level libraries and will be the first to fail if the staging builds don't validate. This is the kind of batch that looks routine until it hits stable and you discover a subtle ABI incompatibility in production.
Action items
- → Monitor extra-staging builds for GDAL [ref:3] and PDAL [ref:5] test results before promotion archlinux/svntogit-packages [monitor]
- → Plan rebuild of any in-house geospatial tools once stable promotion completes archlinux/svntogit-packages [plan]
- → Test QMapShack [ref:2] and Scribus [ref:1] workflows immediately after promotion to catch regressions archlinux/svntogit-packages [plan]
References
- [1] Scribus 1.6.6-3 update to extra-staging
- [2] QMapShack 1.20.1-2 update to extra-staging
- [3] GDAL 3.12.4-2 update to extra-staging
- [4] OpenSceneGraph 3.6.5-32 update to extra-staging
- [5] PDAL 2.9.3-2 update to extra-staging
FAQ
- What changed in Arch Linux on May 1, 2026?
- Five core mapping and graphics libraries are rolling through staging simultaneously—watch for dependency ripples when these hit stable.
- What should Arch Linux teams do about it?
- Monitor extra-staging builds for GDAL [ref:3] and PDAL [ref:5] test results before promotion • Plan rebuild of any in-house geospatial tools once stable promotion completes • Test QMapShack [ref:2] and Scribus [ref:1] workflows immediately after promotion to catch regressions