Upgrade: python-debtcollector version to 3.0.0

[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

Upgrade: python-debtcollector version to 3.0.0
This package have the following dependencies list
python-colorama python-testtools python-toml python-tox python-fixtures

Change Log

• Bump up the version.
• License verified

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

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

Test Methodology

• Local VM build log file:
  python-debtcollector-3.0.0-5.azl3.src.rpm.log

[kgodara912]

If possible, please keep the key files into local folder only, both this and below txt file. They are not big and will avoid multiple files for same package.

[durgajagadeesh]

Hi @kgodara, I’ve uploaded the key files as per your suggestions.
Thank you!

[kgodara912]

I am not sure will this work or not. Was this verified and did it correctly generate dependencies for our spec files? If possible, we can directly keep any other build requires. We already have many at the top.

[kgodara912]

Please check the names of build requirements. Our extended repo names are without 3, means python-fixtures and not python3-fixtures, similarly check others. Please verify local build once.

[durgajagadeesh]

Hi, I have tested the build in local VM with the following packages.

-Thank you!