Le Vendredi 29 Novembre 2002 11:26, Fran�ois Pons a �crit :
> Le ven 29/11/2002 � 11:03, daniel beck a �crit :
> > oh, and an other nice feature for urpmi that would be
> > (rember the libpng2 to libpng3 transition) . Every
> > time i install a new rpm, all the files which are
> > overwritten are stored in /var/cache/urpmi/temp or
> > something like that. so I could do so :
> >
> > there is already A2.0
> > urpmi --safe A2.1.rpm
> >
> > urpmi overwrites some files from A2.0 but store them
> > in /var/cache/urpmi/temp
> >
> > the programm A2.1 brings everyting so I want to have
> > my old configuration again. so I do :
> >
> > urpmi --recover
> >
> > and everything is just like befor the update of A2.0.
> > That would give really a safe impression to the user !
>
> You can do urpmi A2.0 (if it still exists of course) and you get back
> the package...
>
> Fran�ois.
Yes but on cooker often the old package has been erased... :)
The really bad problem is when urpmi or worse rpm get corrupted by an update
:~{
IBM on AIX uses the notion of APPLY and COMMIT. An APPLIED package has his old
version files saved. You can have several level of applied version. You can
REJECT a version to recover the old one, or you can COMMIT the newer to get
rid of old saved files. This is really powerfull. We use to APPLY only each
maintenance level (hundred of fixes with dependencies), let it run for a week
or too or even until the newt maintenance realease where we first COMMIT the
software applied previouly.
Pascal
