Description of problem:
OK, so rpm has the --repackage option for erase or install. However, there is
documentation lacking concerning (re) installation of repackaged packages.
Case in point: today's up2date (4.1.11-3) is "bad" (hangs running). Since I
had another box which I had not updated yet, I turned repackage on and then ran
up2date for up2date only. I got the repackaged up2date and up2date-gnome
(4.1.10-1) in /var/spool/rollbacks as expected but when I copied them to the
other system and attempted to install them they would not.
The only "documentation" I could find was in a "limited visibility" bugzilla
While I admit that there should be extra protections on using these rollbacks,
documentation on re-installing them is needed or why bother having the option at
*** Bug 174630 has been marked as a duplicate of this bug. ***
[This is a mass update sent to many bugs that missed earlier such messages due
to having their version set to a test version.]
This bug was originally filed against a version of Fedora Core which is no
longer supported, even for security updates. Many changes have occured since
then. Please retest this bug against a still supported version. Note that FC3
and FC4 are supported by Fedora Legacy for security fixes only. If
it still occurs on FC5 or FC6, please assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.
This bug will be closed after a few weeks if no information is given indicating
that the bug is still present in a supported release.
The situation has not changed. Either correct documentation should be provided
or delete this capability.
User firstname.lastname@example.org's account has been closed
Reassigning to owner after bugzilla made a mess, sorry about the noise...
Both the install section and the erase section in rpm's man page describe the
--repackage option as:
Re-package the files before erasing. The previously installed package will be
named according to the macro %_repackage_name_fmt and will be created in the
directory named by the macro %_repack-age_dir (default value is
Does this resolve this bug?
this is on Fedora 8. rpm-18.104.22.168-7.fc8
The repackage + rollback feature has been removed from next upstream version, so
you can consider the feature "fixed" ;)