Exit build script on failures

[ashthespy]

Especially multistrap!
After quite some head scratching as to why my images weren't booting, scrutinised the build process in more detail to discover multistrap was failing.
This would make errors like #348 easier to catch.

[gkkpch]

Agree, but checking the log is still strongly adviced.
I have seen other errors, like Debian repo's not responding, leading to similar errors.
As for the multistrap issue, this is known from Ubuntu and Stretch OS hosts.
Meanwhile the multistrap issue has been resolved, but an issue with building our initramfs is still being debugged, unfortunately on hold because of other priorities.

Only Debian jessie is guaranteed to work as a host OS at the moment.

[ashthespy]

Agree, but checking the log is still strongly adviced.
I have seen other errors, like Debian repo's not responding, leading to similar errors.
Only Debian jessie is guaranteed to work as a host OS at the moment.

That explains a lot - I tried first with stretch, and then buster. Will try again with Jessie.

[gkkpch]

Thought so, another stretch/ buster or Ubuntu user....
And we already have a number of users preferring Ubuntu for their build environment.
Seems this slowly needs more attention.... moved #348 to 3rd on my todo list.

[ashthespy]

@gkkpch Don't mean to clutter this PR, but I am having quite the hard time even with jessie now.
Build fails here with:

Adding os-release infos
chroot: failed to run command '/bin/bash': Exec format error

Is there documentation somewhere for the ideal build environment? I don't recall it being so hard to build this about a year ago! :=D

[gkkpch]

just email directly

…

On 02/04/19 17:15, Ash wrote: @gkkpch <https://github.com/gkkpch> Don't mean to clutter this PR, I am having quite the hard time even with |jessie| now. Something about the wrong binary format of |/bin/bash| Is there documentation somewhere for the ideal build environment? I don't recall it being so hard to build this about a year ago! :=D — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#369 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMfAG7jFwl-ICveUtlioGwjuVEVfUhOKks5vc3QsgaJpZM4cYDqk>.

[gkkpch]

use volumio(at)bluewin.ch

…

On 02/04/19 17:15, Ash wrote: @gkkpch <https://github.com/gkkpch> Don't mean to clutter this PR, I am having quite the hard time even with |jessie| now. Something about the wrong binary format of |/bin/bash| Is there documentation somewhere for the ideal build environment? I don't recall it being so hard to build this about a year ago! :=D — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#369 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMfAG7jFwl-ICveUtlioGwjuVEVfUhOKks5vc3QsgaJpZM4cYDqk>.

[ashthespy]

@volumio fe83e03 has introduced conflicts via a reference to a motivo device. Seems like a mistake as
scripts/motivoimage.sh wasn't added to the repo?