Project

General

Profile

Actions
Copy link

Bug #5125

closed

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

Added by Sean Riddle over 14 years ago. Updated about 14 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
David Welker
Category:
build system
Target version:
2.2.0
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.

Actions
Copy link

Also available in: Atom PDF