4 files changed, 2 insertions, 190 deletions
diff --git a/pod/8/urpme.pod b/pod/8/urpme.pod
index c61a8827..e7e0c7c6 100644
--- a/pod/8/urpme.pod
+++ b/pod/8/urpme.pod
@@ -133,4 +133,4 @@ Francois Pons, Rafael Garcia-Suarez
 =head1 SEE ALSO
 
 urpmi.addmedia(8), urpmi.update(8), urpmi.removemedia(8), urpmf(8),
-urpmi(8), urpmq(8), urpmi.files(5), urpmi.recover(8).
+urpmi(8), urpmq(8), urpmi.files(5).
diff --git a/pod/8/urpmi.pod b/pod/8/urpmi.pod
index d1776c7d..508a5ed2 100644
--- a/pod/8/urpmi.pod
+++ b/pod/8/urpmi.pod
@@ -546,7 +546,7 @@ FranE<ccedil>ois Pons, Rafael Garcia-Suarez
 =head1 SEE ALSO
 
 urpmi.addmedia(8), urpmi.update(8), urpmi.removemedia(8), urpme(8),
-urpmf(8), urpmq(8), urpmi.cfg(5), urpmi.files(5), urpmi.recover(8).
+urpmf(8), urpmq(8), urpmi.cfg(5), urpmi.files(5).
 
 =cut
 
diff --git a/pod/8/urpmi.recover.pod b/pod/8/urpmi.recover.pod
deleted file mode 100644
index 2866798a..00000000
--- a/pod/8/urpmi.recover.pod
+++ /dev/null
@@ -1,110 +0,0 @@
-=head1 NAME
-
-urpmi.recover - manages repackaging of old RPMs and rollbacks
-
-=head1 SYNOPSIS
-
-    urpmi.recover --checkpoint [--noclean]
-    urpmi.recover --list '1 week ago'
-    urpmi.recover --rollback '1 hour ago'
-    urpmi.recover --disable [--noclean]
-
-=head1 DESCRIPTION
-
-B<urpmi.recover> is a tool to help management of RPM rollbacks. It has
-three main functions:
-
-C<urpmi.recover --checkpoint> is used to define a point in your system
-that you consider stable, and to start storing info that will enable you
-to rollback installations and upgrades to this state.
-
-C<urpmi.recover --list> is used to list chronologically all installations
-and upgrades on your system. (It has two variants, C<--list-all> and
-C<--list-safe>.)
-
-C<urpmi.recover --rollback> is used to roll back installations and
-upgrades to a previous point in the past (at most until your checkpoint.)
-
-=head1 OPTIONS
-
-=over 4
-
-=item --checkpoint
-
-Define the repackaging checkpoint. From now on, using rpm and/or
-urpmi/urpme to install, upgrade or remove packages, the older packages
-will be stored in F</var/spool/repackage>, or whatever directory you set
-the C<%_repackage_dir> rpm macro to. This way one can use them for
-rollbacks.
-
-Technically, using this option writes a file
-F</etc/rpm/macros.d/urpmi.recover.macros> that overrides the rpm macros
-used to set up the repackaging functionalities of rpm. You can change
-C<%_repackage_dir> there if you want to. Note that you'll probably need
-plenty of space to store repackaged rpms for a long timeframe.
-
-You can also choose to turn off repackaging by setting
-C<%_repackage_all_erasures> to 0 in this file. (Of course if you do so
-rollbacks won't be possible anymore.)
-
-=item --noclean
-
-C<--checkpoint> defines a new checkpoint and removes everything in the
-repackage directory. To prevent this cleaning, use the C<--noclean>
-option.
-
-=item --list <date>
-
-Lists all installations and upgrades from now since the provided date,
-grouped by installation transactions. The date parser is quite elaborated,
-so you can give a date in ISO format or close to it (C<YYYY-MM-DD
-hh:mm:ss>) or a duration (e.g. "1 day ago").
-
-=item --list-all
-
-Lists all installations and upgrades known to the RPM database.
-
-=item --list-safe
-
-Lists all installations and upgrades up to the date of the checkpoint.
-
-=item --rollback <date>
-
-=item --rollback <number of transactions>
-
-Roll back the system to the given date (see C<--list> for accepted date
-formats), or rolls back the given number of transactions.
-
-=item B<--urpmi-root> I<directory>
-
-Use the file system tree rooted for urpmi database and rpm install. Contrary
-to B<--root>, the urpmi configuration comes from the rooted tree.
-
-=item --disable
-
-Turn off repackaging. Unless C<--noclean> was also specified, this cleans
-up the repackage directory as well. To turn it on again, use
-C<--checkpoint>.
-
-=back
-
-=head1 BUGS
-
-When enabled, you can't install and repackage delta rpms (rpms generated
-with the C<makedeltarpm> tool.) Also, if you install a delta rpm, you
-won't be able to rollback past this point. A sound advice would be to
-completely avoid delta rpms if you're planning to use urpmi.recover.
-
-=head1 FILES
-
-    /etc/rpm/macros.d/urpmi.recover.macros
-
-=head1 AUTHOR
-
-Rafael Garcia-Suarez, 
-
-Copyright (C) 2006 Mandriva SA
-
-=head1 SEE ALSO
-
-urpmi(8), urpme(8)
diff --git a/pod/8/urpmihowto.pod b/pod/8/urpmihowto.pod
index 1eb525d1..e1e3edf5 100644
--- a/pod/8/urpmihowto.pod
+++ b/pod/8/urpmihowto.pod
@@ -303,84 +303,6 @@ Run the urpmi command : for example, to install "package_name" :
 
 =back
 
-=head1 urpmi.recover
-
-urpmi.recover is a tool to help management of RPM rollbacks. One rarely
-used feature of RPM is that it can "repackage" the RPMs it deinstalls
-(either because they are upgraded to a newer version, or because they are
-plainly erased), and then reinstall the repackaged RPMs, thereby restoring
-the system to a previous (hopefully more stable) state.
-
-urpmi.recover has three main functions:
-
-=over 4
-
-=item define a checkpoint
-
-C<urpmi.recover --checkpoint> is used to define a point in your system
-that you consider stable, and to start storing info that will enable you
-to rollback to this state (or to any later state).
-
-=item list installations you've done
-
-C<urpmi.recover --list date> is used to list chronologically all
-installations and upgrades on your system up to the specified date. The
-output format gives them grouped by installation transactions. (This
-option has two variants, C<--list-all> and C<--list-safe>.) Here are some
-examples :
-
-List all installations made during the last day :
-
-    urpmi.recover --list '1 day ago'
-
-List all installations since 7th february 2006 :
-
-    urpmi.recover --list 2006-02-07
-
-List all installations since the checkpoint :
-
-    urpmi.recover --list-safe
-
-Lists all installations and upgrades known to the RPM database :
-
-    urpmi.recover --list-all
-
-=item perform rollbacks
-
-C<urpmi.recover --rollback> is used to roll back installations and
-upgrades to a previous point in the past (at most until your checkpoint.)
-It has two variants :
-
-To roll back until a specified date :
-
-    urpmi.recover --rollback <date>
-
-The date can be a duration (for example "2 hours ago") or a date given
-in YYYY-MM-SS hh:mm format.
-
-To roll back a specified number of transactions :
-
-    urpmi.recover --rollback <number of transactions>
-
-In both cases, be careful not to rollback beyond the checkpoint!
-
-=back
-
-Once you've defined a checkpoint, when you use urpmi, urpme or directly
-rpm to install or remove packages, the older packages will be stored in
-/var/spool/repackage. You thus must make sure you have enough space on
-this partition to store all repackaged RPMs.
-
-Technically, defining a checkpoint is equivalent to writing a file
-/etc/rpm/macros.d/urpmi.recover.macros that overrides the rpm macros
-used to set up the repackaging functionalities of rpm. You can change
-C<%_repackage_dir> there if you want to, if you don't want to store
-repackaged RPMs in /var/spool/repackage.
-
-If you want to disable the repackaging functionality and clean up the
-repackage spool, use C<urpmi.recover --disable>. Warning: rollbacks won't
-be possible anymore.
-
 =head1 Restricted urpmi
 
 urpmi has a "restricted" counterpart: rurpmi. It is similar to urpmi, but