Ok, it would be nice for somebody with necessary permissions to merge
this pull request which is pending for several months and just becomes
larger and larger:
https://abf.io/omv_software/urpmi/pull_requests/4
Or just give me permissions to commit to omv_software directly, if omv
community is short in resources. I promise that I will not break
anything (at least intentionally:))
On 03/21/2014 04:27 PM, Denis Silakov wrote:
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]>
Reply-To: Maillist for ROSA development community
<[email protected]>
To: [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_-_??????_???????_???_????????_????
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
_______________________________________________
rosa-devel mailing list
[email protected]
http://lists.rosalab.ru/mailman/listinfo/rosa-devel
--
Denis Silakov, ROSA Laboratory.
www.rosalab.ru
