The only problem is that sudo is missing from the sh -x call but I found the problem anyway (the cvsd-buginfo output showed how far it got). The problem is that bash 4 handles the this statement:
false || ( false && false )
differently from bash 3 when set -e is used (bash 4 terminates the script and 3 doesn't). Btw, dash behaves the same as bash 3.
Anyway, I will change the cvsd-buildroot script to use less && and || magic (which is a good thing anyway) and create a new release shortly (the upload will be to Debian but I guess Ubuntu will pick it up soon enough).
As a workaround you can edit the cvsd-buildroot script and comment out the set -e statement at the beginning. Attached is a minimal patch which also fixes the issue. Note that this is not the patch that will go into 1.0.18, for that see http://arthurdejong.org/viewvc/cvsd/cvsd-buildroot.in?r1=1.49&r2=1.50
The cvsd-buginfo also pointed me to a bug in that script (was there since 2006 apparently) (the wrong uname call). That will also be fixed in the next release.
The only problem is that sudo is missing from the sh -x call but I found the problem anyway (the cvsd-buginfo output showed how far it got). The problem is that bash 4 handles the this statement:
false || ( false && false )
differently from bash 3 when set -e is used (bash 4 terminates the script and 3 doesn't). Btw, dash behaves the same as bash 3.
Anyway, I will change the cvsd-buildroot script to use less && and || magic (which is a good thing anyway) and create a new release shortly (the upload will be to Debian but I guess Ubuntu will pick it up soon enough).
As a workaround you can edit the cvsd-buildroot script and comment out the set -e statement at the beginning. Attached is a minimal patch which also fixes the issue. Note that this is not the patch that will go into 1.0.18, for that see http:// arthurdejong. org/viewvc/ cvsd/cvsd- buildroot. in?r1=1. 49&r2=1. 50
The cvsd-buginfo also pointed me to a bug in that script (was there since 2006 apparently) (the wrong uname call). That will also be fixed in the next release.