git: use openssh-clients instead of full openssh package

[mfrw]

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?
Decouple openssh-server and git. Only take a dependency on openssh-clients

Change Log

• Updatre Requires as openssh-clients instead of openssh which bundles in openssh-server

Does this affect the toolchain?

NO

Associated issues

• Fixes: 52260130
• Closes: openssh shouldn't install both clients and server #9569
• Related: yum install git will install too many packages #10421

Links to CVEs

• NA

Test Methodology

• Pipeline build id: PR-13448

[kgodara912]

Upstream fedora spec also has same openssh-clients dependency only for git. LGTM.

[reubeno]

@mfrw -- this is a righteous change, for sure, but could it be considered a breaking change from the 3.0 LTS's perspective? Is there a risk of an image builder that was unintentionally relying on openssh-server being included and will now no longer have it in their image?

[mfrw]

@mfrw -- this is a righteous change, for sure, but could it be considered a breaking change from the 3.0 LTS's perspective? Is there a risk of an image builder that was unintentionally relying on openssh-server being included and will now no longer have it in their image?

let me verify this