Am 21.03.2014 23:41, schrieb Raphaël Jadot:
+1 for me
the recoverthing it's really highest quite good,
because some Experience Users/ And Admins and some have now
the possible for resetting the System to original-state like it was on
well working.
Vorallem bei Provider kann es wichtig sein, for setting up recoverypoints !
An questions, it is possible for create different recovery points with
date and User-entry ?
as exemple :
urpmi.recover --checkpoint
urpmi.recover --checkpoint --Date --userentry "this was the stabiles and nice
working thing"
urpmi.recover --ls / urpmi.recover --list
Urpmi Recover Listing for recovery :
1. 01/03/2014 | Root-Saving / Provider saveing / Install System
2. 23/03/2014 | this was the stabiles and nice working thing
3. 04/04/2014 | Testingphase with new rpm's
4. 10/04/2014 | works all well - savepoint
5.
and so on
~
therewith whant it is possible easy listing the restorepoints
and have an easy way for restore, :
urpmi.recover --rollback 5
maby an possible for say the chekcpoint and
the checkpoint behind it's moving one back like :
urpmi.recover --ls
Urpmi Recover Listing for recovery :
1. 01/03/2014 | Root-Saving / Provider saveing / Install System
2. 23/03/2014 | this was the stabiles and nice working thing
3. 04/04/2014 | Testingphase with new rpm's
4. 10/04/2014 | works all well - savepoint
urpmi.recover --checkpoint --Date --userentry "this is an better checkpoint"
--Nr 3
urpmi.recover --ls
Urpmi Recover Listing for recovery :
1. 01/03/2014 | Root-Saving / Provider saveing / Install System
2. 23/03/2014 | this was the stabiles and nice working thing
3. 01/05/2014 | this is an better checkpoint
4. 04/04/2014 | Testingphase with new rpm's
5. 10/04/2014 | works all well - savepoint
urpmi.recover --delcheckpoint 4
urpmi.recover --delcheckpoint 5
urpmi.recover --ls
Urpmi Recover Listing for recovery :
1. 01/03/2014 | Root-Saving / Provider saveing / Install System
2. 23/03/2014 | this was the stabiles and nice working thing
3. 01/05/2014 | this is an better checkpoint
(or
urpmi.recover --delcheckpoint 4 5 )
urpmi.recover --delcheckpoint 4,5
urpmi.recover --delcheckpoint 4;5 )
maybe it is therewith possible for creating also an Guy
like rpmdrake for have an rollback in graphical also :)
with delbuttons or create buttons and something ..
maybe with locking the Input devices and grafical feedback,
during the recovery ...
best regards
Blacky
2014-03-21 13:27 GMT+01:00 Denis Silakov <[email protected]
<mailto:[email protected]>>:
FYI - do we want this for cooker?
-------- Original Message --------
Subject: Re: [rosa-devel] urpmi.recover
Date: Fri, 21 Mar 2014 15:28:48 +0400
From: Denis Silakov <[email protected]>
<mailto:[email protected]>
Reply-To: Maillist for ROSA development community
<[email protected]> <mailto:[email protected]>
To: [email protected] <mailto:[email protected]>
Well, urpmi.recover will be brought to you system with next urpmi
update. You may find useful corresponding notes in our blog:
(en)
http://wiki.rosalab.ru/en/index.php/Blog:ROSA_Planet/Urpmi.recover_-_%22Back_In_Time%22_For_The_Package_Base
(ru)
http://wiki.rosalab.ru/ru/index.php/????:?????_????/Urpmi.recover_-_??????_???????_???_????????_????
<http://wiki.rosalab.ru/ru/index.php/%3F%3F%3F%3F:%3F%3F%3F%3F%3F_%3F%3F%3F%3F/Urpmi.recover_-_%3F%3F%3F%3F%3F%3F_%3F%3F%3F%3F%3F%3F%3F_%3F%3F%3F_%3F%3F%3F%3F%3F%3F%3F%3F_%3F%3F%3F%3F>
Feel free to test.
On 03/17/2014 04:35 PM, Denis Silakov wrote:
> Hi all,
>
> as some of you likely know, we have a tool named 'urpmi.recover' which
> is aimed to revert state of the packages in the system to particular
> date.
>
> This tool is actually a wrapper for "rpm --rollback" functionality
> which doesn't work currently, unfortunately. Until we identify root of
> problems with "real rpm rollback", I have implemented a very
> straightforward way of work for urpmi.recover - it will simply invoke
> rpm to install old versions of packages and remove the new one (which
> were absent in the system at the specified time).
>
> New urpmi is available in testing repositories of ROSA Desktop Fresh.
>
> To test urpmi.recover, you should first enable repackaging it by typing
>
> # urpmi.recover --checkpoint
>
> After this, when some package is updated, its old version will be
> saved to /var/spool/repackage folder, to a subfolder corresponding to
> update date.
>
> At some moment when you decide that it is time to revert your packages
> (at least to try to do it:)), simply say something like:
>
> # urpmi.recover --rollback <timestamp>
> or
> # urpmi.recover --rollback <number_of_transactions>
>
> Ideally, you should specify timestamp in "seconds since the Unix
> Epoch", but you should be also able to use human-readable formats, e.g.
> # urpmi.recover --rollback "2014-03-07 13:20:47"
>
> or even
> # urpmi.recover --rollback "1 hour ago"
>
> If you just updated a package a want to rollback this update, you can
> tell urpmi.recover to revert a single transaction:
> # urpmi.recover --rollback 1
>
> Finally, to completely disable repackaging and to clean
> /var/spool/repackage folder, just type:
>
> # urpmi.recover --disable
>
>
> Feel free to test this new feature. But use it on your own risk;
> currently I wouldn't recommend to use it on real machines, since it is
> possible that the tool will erase some crucial packages or will fail
> during rollback.
>
--
Denis Silakov, ROSA Laboratory.
www.rosalab.ru <http://www.rosalab.ru>
_______________________________________________
rosa-devel mailing list
[email protected] <mailto:[email protected]>
http://lists.rosalab.ru/mailman/listinfo/rosa-devel
