-
Notifications
You must be signed in to change notification settings - Fork 13
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
3.7.0 update on macOS, blocked by SIP? #135
Comments
Hi @clwgh Thanks for reporting this. We have been working on an update of ThinkingRock, including compatibility with newer JRE and Netbeans versions. We are still in an early state and don't have an official release yet. Personally, I am running the current state of the main branch in this repo producitvely, albeit on linux, not macOs. Let me know if you'd be willing to try out the current develpement version of ThinkingRock to see if it already improves the situation you are facing on macOS (or Windows/Linux). Cheers, Urs |
Sounds interesting @ursjoss I'm happy to do some testing for the project. I used to do this for Jeremy and Claire 12 or more years ago back in the blue logo 3.3 days. |
Can you contact me via email (to thinkingrock at gmx dot net)? We can discuss there how you will get an update to the current beta version. |
Done. In respect of this issue, though, is there a way to apply these updates, and is the problem caused by SIP on macOS? |
Hello, I'm still using ThinkingRock 3.7.0 and it works great. I use it on an old XP VM with host-only networking. I recently tried it on macOS (Catalina 10.15.7) and it installs and works fine. However module updates from the previously downloaded updates.zip fail to install.
ThinkingRock goes through the motions of staging the nbm files and prompts to restart. On a restart there is some NetBeans activity. TR returns and the updates have not been applied, and the application shortly re-prompts that the same updates are available.
I suspect this has something to do with macOS System Integrity Protection, and this old version of NetBeans has no awareness of the need to go through the updated mechanisms for app updates, nor any concept of checking for success, since it did everything it was supposed and was blocked out of band by SIP.
Do you think this is indeed caused by SIP and the analysis is correct? Other than disabling SIP temporarily, which I prefer to not do, is there a way to manually apply, or force apply the module updates?
The text was updated successfully, but these errors were encountered: