agama-project / agama / 14334125150
73%

DEFAULT BRANCH: master
Ran
Jobs 0
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
14334125150

push

github

web-flow 
Include the short Git commit hash in the RPM package version (#2251)

## Problem

- To find whether an Agama package contains a certain fix is not easy.
- The package version contains the Git version tag + number of commits
since that tag, so it is possible to find that respective commit but
that is not trivial.
- Moreover if the package comes from a different branch the number of
commits can be the same as in `master` but with different content. The
version number is not unique.

## Solution

- Include the short Git commit hash in the package version.
- Then finding the appropriate Git commit in the history is trivial.
- This makes the version unique even for different branches or forks.

## Testing

- Tested manually in
https://build.opensuse.org/project/show/systemsmanagement:Agama:branches:git_commit_in_version
OBS project
- When listing the installed package versions the Git commit is included
(highlighted with extra `grep`):
  

![image](https://github.com/user-attachments/assets/41e263ff-8055-44be-bca9-675256a42ac4)
- Note: All packages have the save version/Git commit because I updated
all of them in a single commit. Later the versions will be more
different.
- Zypper (libzypp) treats the versions correctly, the number of commits
takes precedence so even if the Git commit uses a lower number the
higher commit count is correctly evaluated as a newer version:
  

![image](https://github.com/user-attachments/assets/82f3edd3-5314-4890-bdb0-3e370691ef71)

- That means updating the packages in the potential self-update will
work correctly.
Source Files on build 14334125150
Detailed source file information is not available for this build.