Skip to content
Snippets Groups Projects
Verified Commit 525b5a98 authored by Karel Koci's avatar Karel Koci :metal:
Browse files

helpers/new_release.sh: use packages hash as authoritative

The reason is that this is more appropriate if for example we modify
patches on commit not yet build but released older version. Such state
would not compile so instead we have to choose packages version. The
changes in updater's lists should not have such effect.
parent dcb2bc6e
Branches
Tags
1 merge request!74helpers/new_release.sh: use packages hash as authoritative
......@@ -95,9 +95,9 @@ tb_hash() {
for board in "${BOARDS[@]}"; do
l_hash="$(cat "$GIT_HASH_LISTS-$board")"
b_hash="$(git_hash "$board" "turris-build")"
[ -n "$p_hash" ] || p_hash="$l_hash" # First board is considered primary and lists are authoritative
[ "$p_hash" = "$l_hash" ] || {
error "Turris build used to generate lists is not same as for ${BOARDS[0]} board: $board ($l_hash / $p_hash)"
[ -n "$p_hash" ] || p_hash="$b_hash" # First board is considered primary and packages are authoritative
[ "$p_hash" = "$b_hash" ] || {
error "Turris build used to generate packages is not same as for ${BOARDS[0]} board: $board ($b_hash / $p_hash)"
ec=1
}
[ "$b_hash" = "$l_hash" ] || {
......@@ -105,7 +105,7 @@ tb_hash() {
ec=1
}
done
echo "$l_hash"
echo "$p_hash"
return $ec
}
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment