mock: backport upstream change for disabling ca-trust copying

[reubeno]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Backports to AZL3.0 an upstream mock change to fix runtime errors we've seen using mock to build Azure Linux 3.0 RPMs that have a build-time requirement on ca-certificates. The change allows us to disable mock from copying ca-trust dirs from the host system into the build root; this let us work around problems on an Azure Linux 3.0 host due to symlinks under /etc/pki/ca-trust causing conflicts within the build root.

More details can be found on the upstream change: rpm-software-management/mock#1573.

Change Log

Ports the linked PR to the version of mock in Azure Linux 3.0.

Does this affect the toolchain?

No

Test Methodology

Local build + buddy build