dw-0
commented
1 month ago Please provide more information to the Linux Distribution / Operating System you encounter this observation.
The rollback of Klipper or Moonraker rolls back the git history, which is persisted. This is not a temporary thing that gets reverted during a system reboot.
The system must do a full rollback, to have a system, that was before the updates, and fully save the configuration
I don't understand this. Can you elaborate what you mean by a full rollback? What are you referring to as "system"? What are you referring to as "configuration"?
Your information is not sufficient to begin to analyze the problem.
Linux Distribution
There was some problems with connecting of Mainsail to the Moonraker after reinstalling of klipper and mainsail. And after making the Klipper and Moonraker repository rollback to 1-4 commits, system works, but after reboot of the Host there is the same story. It is not saving the working configuration, and the procedure of rolling back must be done every time you restarting the host.
What happened
There was some problems with connecting of Mainsail to the Moonraker after reinstalling of klipper and mainsail. And after making the Klipper and Moonraker repository rollback to 1-4 commits, system works, but after reboot of the Host there is the same story. It is not saving the working configuration, and the procedure of rolling back must be done every time you restarting the host.
What did you expect to happen
The system must do a full rollback, to have a system, that was before the updates, and fully save the configuration
How to reproduce
Just having system, that cannot connect to moonracker via mainsail, and worked before.
Additional information