Build fix for python-fixtures.

[AkarshHCL]

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

Build fix for failing python-fixtures. Dependency packages-python-colorama , python-testtools, python-toml , python-tox

Change Log

• SPECS-EXTENDED/python-fixtures/python-fixtures.spec

Does this affect the toolchain?

NO

Test Methodology

-Screenshot of successful build-

[sandeepkarambelkar]

BB - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1008008&view=results

[sandeepkarambelkar]

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1011007&view=results

[sandeepkarambelkar]

Buddy Build to verify the build of dependent packages - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1011913&view=results

[sandeepkarambelkar]

Buddy Build successful.
Changes LGTM.

[kgodara912]

As such changes look fine but check once python-fixtures changes if they are needed or not in regular build path. Also, the dependent packages' buddy build is still failing, are we investigating those failures or those are expected?

[sandeepkarambelkar]

@kgodara912 , dependent packages failures if any will be addressed as separate PR