Hi all,

I’ve gone through the starlingx repos to look for remaining packages that are using hardcoded TIS_PATCH_VER values in their build_srpm.data files, replacing them with PKG_GITREVCOUNT. I compared a build with the updated versioning against the hardcoded versions, adding offsets to the PKG_GITREVCOUNT where necessary, to ensure that all updated packages have an incremented version.

There are updates in most of our repos, so I’d appreciate it if cores have a few minutes for reviews in their areas:

https://review.opendev.org/q/topic:%22auto-versioning%22+(status:open%20OR%20status:merged)

Going forward, we should try to ensure new packages use one of the auto-versioning mechanisms. Descriptions of the options (PKG_GITREVCOUNT, SRC_GITREVCOUNT, OTHER_GITREVCOUNT, GITREVCOUNT) can be found in the StarlingX docs here:

https://docs.starlingx.io/developer_resources/packaging_ref.html#details-for-build-srpm-data

Thanks,

Don.