Fix "Conda init bash" issue.

[rikenm1]

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?
=> add missing shell files.
=> also add sudo, ca-certificates and libsolv-devel packages as runtime deps

Change Log

• Change: Fix conda init bash

Does this affect the toolchain?

YES/NO
NO

Test Methodology

• Pipeline build id: 893035

[CBL-Mariner-Bot]

✅ PR Check Passed

No critical issues detected in spec file changes.

🤖 AI Analysis Summary:

Brief Analysis:
The changes in the spec file bump the release version, add installation of a missing conda.xsh script, update the destination for conda.fish, and include additional runtime dependencies. There are no CVE-specific patch references in this update.

Critical Issues Found:
• No CVE patches are referenced so no CVE-related files or changelog entries require matching.
• All patched files (using numeric names) are present in the directory.

Recommended Actions:
• Confirm that the new runtime dependencies (sudo, ca-certificates, libsolv-devel) align with security guidelines.
• Verify that the additional file installations (conda.xsh and fish configuration move) meet deployment policies.
• Document any future security patches using the correct CVE-YYYY-XXXXX.patch naming if applicable.

---

📋 For detailed analysis and recommendations, check the Azure DevOps pipeline logs.