Add epoch to libdwarf spec to fix versioning order

[sindhu-karri]

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 (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/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?
The PR adds an epoch version to the package.
The versioning of the package has changed from date versioning to normal versioning in the last upgrade.
version before upgrade: 20200114
version after upgrade: 0.9.0
Since the version after upgrade is numerically lower, package manager treats it as an older version and the CVEs on the earlier versions are being detected on the current version even though they're not applicable.

Change Log

• Add Epoch to fix version ordering as date versioning had changed to normal versioning

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• https://dev.azure.com/mariner-org/mariner/_build/results?buildId=486988&view=results

[mfrw]

LGTM :)

An idea I would like to bounce across, we have moved libdwarf recently to SPECS from SPECS-EXTENDED, how about, we remove the libdwarf rpms from the extended repo ? That way we need not add the Epoch tag.
/cc @jslobodzian @PawelWMS @anphel31

[sindhu-karri]

LGTM :)

An idea I would like to bounce across, we have moved libdwarf recently to SPECS from SPECS-EXTENDED, how about, we remove the libdwarf rpms from the extended repo ? That way we need not add the Epoch tag. /cc @jslobodzian @PawelWMS @anphel31

Hi @mfrw, The package is published to core repos now, with the 20240117 release

[CBL-Mariner-Bot]

Auto cherry-pick results:

• main ✅ -> [AUTO-CHERRYPICK] Add epoch to libdwarf spec to fix versioning order - branch main #7341

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=487195&view=results