Resolved ptest failures in python‑tqdm package

[durgajagadeesh]

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?

• Resolved ptest failures in package.
• Upgrade to 4.67.2 to fix pip uninstall error during %check
• CVE-2024-34062 fix is included in this version.

Change Log

• SPECS/python-tqdm/python-tqdm.signatures.json
• SPECS/python-tqdm/python-tqdm.spec
• cgmanifest.json

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

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

Test Methodology

• Pipeline build id: xxxx
• Build Summary

[durgajagadeesh]

1. There are failures in %check section due to incompatibility between python‑tqdm and newer pandas—tqdm is trying to use removed internal APIs (is_builtin_func / _is_builtin_func).
2. hese issues were resolved by upgrading to version 4.67.2.
3. This version also includes the fix for CVE-2024-34062.