-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modification needed in xcunsign script for macOS Sierra #2
Comments
@kaustubh-kabra thanks for the report. I have not yet had a chance to upgrade to Sierra myself, so this is good to know. Those two lines are intended as a protection so that the script will stop running if any commands fail, which prevents the script from continuing if the system has gotten into an unexpected state. Could you provide any information on at what point the script failed for you? Are there any errors that were logged while it was trying to execute? If you're able to post the output you received that would be a great help. |
It gave no error, simply exited. Hence, debugging became bit difficult. I suggest to modify script (and make it conditional) for macOS Sierra support. |
#2 - Modification needed in xcunsign,xcrestore script for macOS Sierra
Thanks for the PR -- I've gone ahead and merged it. I'm going to keep this ticket open for now as a reminder for me to take a look at the underlying cause as soon as I'm able to get upgraded to Sierra, but hopefully this will help others from being blocked in the meantime. |
Sure, cheers ! |
If it helps anyone, I had to comment first 2 lines of xcunsign script -
set -o errexit # Exit if any statement returns a non-true return value (non-zero).
set -o nounset # Exit on use of an uninitialized variable
xcunsign then ran fine on my macOS Sierra.
The text was updated successfully, but these errors were encountered: