[mscasso-scanoss]

Problem

Release binaries are built on ubuntu-22.04 (glibc 2.35), so ldb and libldb.so require GLIBC_2.33/GLIBC_2.34:

• the .rpm can't be installed on RHEL/Rocky/Alma 8 (glibc 2.28): nothing provides libc.so.6(GLIBC_2.34)(64bit) needed by ldb-4.1.11-1.x86_64;
• the .deb can't run on Debian 11 (glibc 2.31), and also declares libgcrypt20 (>= 1.9.0) while Debian 11 ships 1.8.x.

Changes

• Build in a rockylinux:8 container (glibc 2.28 baseline). The same binaries, .tar.gz, .deb and .rpm then work on every supported distro. Packaging still runs on the Ubuntu runner.
• Check the glibc baseline: the release fails if ldb or libldb.so requires glibc > 2.28.
• Package with package.sh directly: make prepare_*_package depends on all and would rebuild on the runner, undoing the EL8 build.
• .deb depends on libgcrypt20 (>= 1.8.0): built on EL8 (libgcrypt 1.8.5) the binaries only need 1.8 symbols (GCRYPT_1.6).
• Manual runs (workflow_dispatch) upload the packages as workflow artifacts instead of creating a release, and the tarball name is file-safe for branch names.

Package file names are unchanged, so nothing changes for consumers (e.g. the on-premise installer).

Testing

• Workflow run on this branch: https://github.com/scanoss/ldb/actions/runs/40908436133 (build, glibc check: ldb/libldb.so require glibc 2.14).
• The packages produced by that run, together with the engine built the same way (Build release binaries on EL8 so packages run on every supported distro engine#128), installed in clean containers; ldb -v and scanoss -v run and ldd resolves everything:

Distro	glibc	Result
debian:11	2.31	✅
debian:12	2.36	✅
debian:13	2.41	✅
ubuntu:22.04	2.35	✅
ubuntu:24.04	2.39	✅
rockylinux:8	2.28	✅ (fails today: requires GLIBC_2.33/2.34)
rockylinux:9	2.34	✅
almalinux:10	2.39	✅
fedora:latest	2.43	✅

Related: scanoss/on-premise#31.

🤖 Generated with Claude Code