[Work Item #19220] Resolved ptests failure in git-lfs package

[SumitJenaHCL]

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?
This is to fix ptests failures in TLS handshake issue due to openssl for package git-lfs

Change Log

• SPECS/git-lfs/git-lfs.spec

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: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1118123&view=results

[SumitJenaHCL]

Buddy build has passed.

[Kanishk-Bansal]

remove CGO_ENABLED=0

[SumitJenaHCL]

remove CGO_ENABLED=0

removed.

[Kanishk-Bansal]

similar changes already merged in 70e4aa0

[kgodara912]

We may need to make change in build section as well. Because in build section, if the module is compiled with different crypto backend, then it can't run check section with different backend. Please check once and put the change in build section which will ensure consistent crypto backend for both build and test.

[SumitJenaHCL]

We may need to make change in build section as well. Because in build section, if the module is compiled with different crypto backend, then it can't run check section with different backend. Please check once and put the change in build section which will ensure consistent crypto backend for both build and test.

Added requested changes. Buddy build has passed after necessary changes.