diff options
author | Bruce Ashfield <bruce.ashfield@gmail.com> | 2024-11-01 23:00:58 -0400 |
---|---|---|
committer | Bruce Ashfield <bruce.ashfield@gmail.com> | 2024-11-01 23:59:13 -0400 |
commit | d5bda44c064d56db98f203f6285bf3b6b9016870 (patch) | |
tree | ec8761c77618d389d085fa10649be4fc762cdd08 /recipes-networking/openvswitch/openvswitch-git | |
parent | 72ea52031c045bb6b4e13856f324b3ec28e333df (diff) | |
download | meta-virtualization-d5bda44c064d56db98f203f6285bf3b6b9016870.tar.gz |
upx: update to -tip and return to indivdual fetches
Bumping upx to version v4.2.4-62-g44e4bd0b, which comprises the following commits:
44e4bd0b CI updates
1427b813 CI updates
a9cb3542 CI and cmake updates
b4db17ab cmake update
ba969fb9 CI updates
87ac252c CI updates
ada9081e CI updates
d6a29e58 CI updates
03c41840 all: misc cleanups
The upx repository has invalid git commits for SRCREVs
greater than 4.2.4 (and for commits that used to work).
This was reported on the mailing list by Javier Tia <javier.tia@linaro.org>
Older commits seem to work, but we'd have issues updating
the recipe to newer values (tip fo the tree is also broken
for gitsm fetching).
So for now, we switch back to individual fetches that we
can use to control the SRCREVs precisely.
SRCREVs are from:
git submodule status | awk '{ commit_hash = $1; sub(/vendor\//, "", $2); gsub("-", "_", $2); printf "SRCREV_vendor_%s = \"%s\"\n", $2, commit_hash }'
with two substitions for invalid SRCREVs (hence why the gitsm fetcher
has issues)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Diffstat (limited to 'recipes-networking/openvswitch/openvswitch-git')
0 files changed, 0 insertions, 0 deletions