Project

General

Profile

Bug #5125

Add feature to do a one-step revert of a botched update from outside of Kepler

Added by Sean Riddle about 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
build system
Target version:
Start date:
08/04/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5125

Description

If a patch does not work correctly, it is possible that Kepler will fail to restart after the patch's installation. The way to handle this (which will be made simpler in the future) is to run the module manager standalone and use it to restore to a working configuration.

The module manager should have an easy way to rollback the last patch that was applied, returning the user to the working configuration they were just in.

This should probably also disable automatic updates.

History

#1 Updated by David Welker almost 9 years ago

This sounds interesting. That there are two different bugs that might be solved by a "rollback" feature makes me wonder whether this feature actually SHOULD be in 2.2. Or should it be in a later version?

#2 Updated by David Welker almost 9 years ago

Rollback functionality has now been implemented.

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5125

Also available in: Atom PDF