diff options
| author | Mingli Yu <mingli.yu@windriver.com> | 2024-01-10 14:42:37 +0800 |
|---|---|---|
| committer | Khem Raj <raj.khem@gmail.com> | 2024-01-09 22:48:25 -0800 |
| commit | df2e4cff8e908226b0b0c61f4b5ea5c5f73be1bd (patch) | |
| tree | e7e4bf7c81f885708717a7cdc7fbfc21e31c6f24 /meta-python/recipes-devtools/python/python3-pybluez/py-3.11.patch | |
| parent | 11056735e8c2ced778ec308f9a9f52964ceefa12 (diff) | |
| download | meta-openembedded-df2e4cff8e908226b0b0c61f4b5ea5c5f73be1bd.tar.gz | |
ipmitool: Make the version consistent
The git revison info is added [1] to make the version more descriptive
to produce an incremental revision number like 1.8.18.13 or 1.8.18.14
and etc and more clear in terms of "what codebase was used" like
`1.8.18.13.gee01aa5`. But it also introduces the version inconsistence.
Note as stated in [1]
For cases when .git directory is missing (Release compilation?) the suffix
part will be omitted completely yielding a version like `1.8.18`.
Considering the version we acutally used in oe is a release version,
the git revision info as [1] is meaningness. So drop the git revsion
info to make the version consistent.
Before the patch:
root@qemux86-64:~# ipmitool -V
ipmitool version 1.8.19.19.gab5ce5b
root@qemux86-64:~# rpm -qa | grep ipmitool
ipmitool-1.8.19-r0.core2_64
After the patch:
root@qemux86-64:~# ipmitool -V
ipmitool version 1.8.19
root@qemux86-64:~# rpm -qa | grep ipmitool
ipmitool-1.8.19-r0.core2_64
[1] https://github.com/ipmitool/ipmitool/commit/ba01dc84b4e225c86eac3f562e629662d752040f
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-pybluez/py-3.11.patch')
0 files changed, 0 insertions, 0 deletions
