gnupg2: Upgrade gnupg2 to 2.4.7

[KavyaSree2610]

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

What does the PR accomplish, why was it needed?

• While attempting to verify a digital signature using gpg --verify with gnupg version 2.4.4, an "invalid radix64" error was encountered. Upgrading to gnupg version 2.4.7 will resolve this issue.

With 2.4.4:

• During the upgrade of GnuPG to version 2.4.7, a build issue was encountered due to the yat2m tool, which is used for doc generation. The 2.4.7 version of gnupg requires yat2m to support the --gnupgorg argument. However, this argument is not recognized in the version of yat2m provided by libgpg-error 1.47.

• To resolve this, the libgpg-error package was upgraded to version 1.48, which includes support for the --gnupgorg option. This allows the gnupg 2.4.7 package to build successfully

Change Log

• Upgrade libgpg-error to 1.48 to support gnupg2
• Upgrade gnupg2 to 2.4.7

Does this affect the toolchain?

YES

Associated issues

• https://microsoft.visualstudio.com/OS/_workitems/edit/57956075

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• With 2.4.7:

• Buddy build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=845586&view=results
• Full Build id: 846772

[mfrw]

LGTM - we should just to double check, once try a full build (if possible) and boot :)

[Copilot]

Pull Request Overview

Upgrade GnuPG (gnupg2) from 2.4.4 to 2.4.7 and libgpg-error from 1.47 to 1.48 to resolve an “invalid radix64” error and support the new --gnupgorg argument in the yat2m tool.

• Bump package versions in toolchain and pkggen_core manifests for both x86_64 and aarch64
• Update cgmanifest.json download URLs and versions
• Update spec files (.spec and .signatures.json) for libgpg-error and gnupg2, including changelog and symlink additions

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
toolkit/resources/manifests/package/toolchain_x86_64.txt	Bump gnupg2 to 2.4.7 and libgpg-error to 1.48
toolkit/resources/manifests/package/toolchain_aarch64.txt	Same bumps for aarch64
toolkit/resources/manifests/package/pkggen_core_x86_64.txt	Update gnupg2 and libgpg-error versions
toolkit/resources/manifests/package/pkggen_core_aarch64.txt	Same for aarch64
cgmanifest.json	Update download URLs and versions for both libs
SPECS/libgpg-error/libgpg-error.spec	Version bump to 1.48, update changelog
SPECS/libgpg-error/libgpg-error.signatures.json	Update tarball signature
SPECS/gnupg2/gnupg2.spec	Version bump to 2.4.7, update dependencies & symlinks
SPECS/gnupg2/gnupg2.signatures.json	Update tarball signature

[Kanishk-Bansal]

LGTM! The changes look good. Notably, the symlinks for the man pages are now created before the make install step, which ensures they are properly available. Thanks for handling this!

[Kanishk-Bansal]

Buddy Build ✅

Initiated a full build here :
Full Build

[KavyaSree2610]

Buddy Build ✅

Initiated a full build here : Full Build

Full build successful