mock: upgrade and port from extended to core (including dependencies)
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
- [X] The toolchain has been rebuilt successfully (or no changes were made to it)
- [X] The toolchain/worker package manifests are up-to-date
- [X] Any updated packages successfully build (or no packages were changed)
- [X] Packages depending on static components modified in this PR (Golang,
*-staticsubpackages, etc.) have had theirReleasetag incremented. - [X] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
- [X] All package sources are available
- [X] cgmanifest files are up-to-date and sorted (
./cgmanifest.json,./toolkit/scripts/toolchain/cgmanifest.json,.github/workflows/cgmanifest.json) - [X] 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) - [X] All source files have up-to-date hashes in the
*.signatures.jsonfiles - [X]
sudo make go-tidy-allandsudo make go-test-coveragepass - [X] Documentation has been updated to match any changes to the build system
- [ ] Ready to merge
Summary
Upgrades mock to a usable version that will run on Azure Linux 3.0 and upgrades it and its required dependencies to core from extended. Since the 2.0 -> 3.0 upgrade, the version of mock present in extended hasn't been able to run correctly.
Change Log
- Upgrade
mockand move to core - Upgrade
mock-core-configsand move to core (part ofmock) - Upgrade
distribution-gpg-keysand move to core (required bymock) - Upgrade
libuserand move to core (required bymock) - Add
python-backoff(required bymock) - Upgrade
python-pyroute2and move to core (required bymock) - Add
python-rpmautospec-core(required bymock) - Upgrade
python-templated-dictionaryand move to core (required bymock) - Upgrade
usermodeand move to core (required bymock)
Does this affect the toolchain?
No.
Test Methodology
Local build + buddy build.
@PawelWMS thanks for all the feedback on this PR--definitely some good learning for me along the way.
When you get a chance, would you please look at the updates I made to see if they address your questions and concerns? I know there's a conflict with the license map right now, but I'm inclined to hold off on (re-)resolving that / (re-)sync'ing until getting a general thumbs up from you on the meaningful changes herein.
(As a side note, is there something we could do to decrease conflicts on LICENSES-MAP.md? Even splitting up the giant table cells into multiple rows on multiple textual lines would likely decrease conflicts and enable auto-merging without sacrificing the actual contents. Would there be support for doing that?)