The packaging-rpm Evergreen task (variant packaging) has been failing since late August 2026.

Findings

• The build image no longer ships the fedora-40-aarch64 mock config that .evergreen/scripts/build_snapshot_rpm.sh used. Fedora 43's EPEL does not ship a new-enough mongo-c-driver, and its resolver-library detection fails under its glibc (ENABLE_SRV build error), so fedora-43-aarch64 is not a viable replacement.
• Switching to the centos-stream+epel-10-aarch64 mock config works: EPEL 10 now ships mongo-c-driver-devel 2.5.4 and libmongocrypt (it shipped 2.5.2 on 2026-09-26; cmake would then FetchContent-download the C driver, which requires --enable-network on the mock --rebuild invocation).
• With the working chroot, the RPM spec itself fails in three places because it predates the 4.x driver changes:
  • %build hardcoded -DBUILD_VERSION=4.1.0 (via spec.patch), so the cmake install directories (lib64/cmake/mongocxx-4.1.0) no longer matched the %install globs using {{% {version}

    }} (4.7.0).

  • %files globbed for the old libmongocxx.so / libbsoncxx.so naming; the 4.x driver installs libmongocxx1.so. / libbsoncxx1.so. and libmongocxx1.pc / libbsoncxx1.pc.
  • The post-install example verification compiled with -lmongocxx -lbsoncxx; it must use -lmongocxx1 -lbsoncxx1.

Fix

The mock -rebuild call now passes -enable-network, spec.patch is removed (corrections baked into .evergreen/mongo-cxx-driver.spec), and the example link flags use the 4.x names. Validated green in patch build 6abeec368d5e580007cca49c. Draft PR to follow.