support/download: quick fix to avoid breaking on custom toolchains
authorYann E. MORIN <yann.morin.1998@free.fr>
Fri, 3 Apr 2015 12:19:58 +0000 (14:19 +0200)
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Fri, 3 Apr 2015 12:21:47 +0000 (14:21 +0200)
When the user selects a custom toolchain to be downloaded, there's no
hash for that toolchain, so the download fails, now that hashes are
mandatory.

Fix that by simply exiting as if there was no error, until we have a
better fix...

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
support/download/check-hash

index 3483077c55618d38dc6ea19143030d4635e1182d..67c17801127f5b1a0d8a83ce6fd8605ddc56e360 100755 (executable)
@@ -96,5 +96,5 @@ done <"${h_file}"
 
 if [ ${nb_checks} -eq 0 ]; then
     printf "ERROR: No hash found for %s\n" "${base}" >&2
-    exit 3
+    exit 0
 fi