[rjd15372]

Why

Release PR #148's QA failed three PG 17 component lanes the same way:

make: /usr/bin/clang: No such file or directory
make: *** [/usr/pgsql-17/lib/pgxs/src/makefiles/../../src/Makefile.global:1085: credcheck.bc] Error 127

• credcheck 17 and PostGIS 17 on rocky9, pg_stat_monitor 17 on EL10.

The PG 17 server is built --with-llvm, so its Makefile.global sets CLANG=/usr/bin/clang and PGXS compiles every extension's .bc bitcode with it. percona-postgresql17-devel did not require clang, so extension builds on a host without it fail. The PG 18 lanes on the same hosts passed because PG 18's -devel already requires clang.

What

Both PG 17 server specs (root/ppg/staging/17 and root/ppg/staging/17/extras) get, in %package devel:

%if %llvm
Requires:       llvm-devel >= 19.0 clang-devel >= 19.0
%endif

Same block as the PG 14, 15 and 16 specs; 19 matches PG 17's own llvmjit (Requires: llvm >= 19).

Audit of the other majors (rpmspec -P per EL): 14, 15, 16, 16:extras and 16:tde build --with-llvm and require llvm-devel >= 19.0 clang-devel >= 19.0 on EL8/9/10; 18 and 19 require clang too. PG 17 was the only gap.

Verification

• rpmspec -P expands the new Requires on EL8, EL9 and EL10 for both specs.
• project verify --offline passes for ppg:staging:17 and ppg:staging:17:extras.
• Real proof is the OBS build plus the credcheck / pg_stat_monitor / PostGIS 17 QA lanes.

Rebuilds the PG 17 server and everything depending on it (extensions, images, tarballs).