Upgraded xapian-core to version 1.4.26

[aninda-al]

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

Upgrades xapian-core to version 1.4.26

Build/Dependency Information

The PR is a leaf PR which builds alone successfully

Change Log

• modified: SPECS-EXTENDED/xapian-core/xapian-core.signatures.json
• modified: SPECS-EXTENDED/xapian-core/xapian-core.spec
• modified: cgmanifest.json

Does this affect the toolchain?

NO

Associated issues

• NA

Links to CVEs

• NA

Test Methodology

• local build

[mfrw]

can we please address the failing github pr checks

[aninda-al]

can we please address the failing github pr checks

@mfrw I could be wrong here, the only issue I noticed on manual inspection was missing newline at the end of the spec and signature file. I fixed them and pushed my changes. Please let me know if I am missing anything else.

[mfrw]

Interim approval to upload to blobstore