Hi Matthias, Matthias Klose: > debian/rules has lots of
> set -e && <stuff> > starting the set in one shell and <stuff> in the next one. Please fix all > those. > Seen while trying to build for multiple python3 versions. > set -e; <stuff> > is the right thing to do. I confess I was not able to reproduce the problem myself: I've tried inserting "false" in various places where I would naively expect "set -e" to fail the build, and I did not manage to find a case when "set -e" did not fail the build. Still, I'm not good Makefile and I'm very much inclined to trust your expertise on this front, so I've applied your suggestion (locally for now). I would greatly appreciate a practical example in which "set -e && <stuff>" does not behave as I thought it would :) Thanks! Cheers, -- intrigeri