I do not know how to downgrade, so I’ll look into that since yes, I’m not stuck where software updater makes it seem like it can’t connect to the server. So I will need to find out how to downgrade.
I hope you don’t take offense by my rebuttals to your suggestions about prebuilt VM or Haiku in the cloud. Perhaps some will like those decisions, but I think this only skirts around the issue. What really needs to be done is:
Ensure that there are clear documented steps (not confusing and not ambiguous)
Ensure that those steps, if followed, work
Ensure that there is appropriate error information when something goes wrong (i.e. actionable error messages)
Ensure there is resilience in the process so that it is possible and easy to understand how to recover from errors and resume work
I have done software development for 25+ years and know that more people will get involved when the process works, is understandable and when they can start seeing how “easy” it is to make changes and see their changes work. Right now, the process is unclear, a bit like magic, doesn’t work too much of the time, and discourages participation because it requires too much mental, temporal and technical involvement.
Now I have to figure out how to downgrade my system, and then figure out how I can break-down the steps and find out what is failing. Does this mean that the logs I uploaded do not provide enough information to understand the issue that is occurring?