Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 62800 - Update over an existing rawhide installation causes strange packet installation
Update over an existing rawhide installation causes strange packet installation
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-04-05 13:16 EST by Peter Bieringer
Modified: 2007-04-18 12:41 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-04-05 13:16:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Bieringer 2002-04-05 13:16:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.17-0.18 i686)

Description of problem:
After updating a rawhide installation (which was an update of a 7.2
installation) with skipjack, none of the existing packets were "freshen", they
were installed additionally (looks like using "force"). After booting, "rpm -aq"
shows most packets twice (1x rawhide, 1x skipjack). Some apps won't run until
rawhide libraries were deinstalled with rpm.

Version-Release number of selected component (if applicable):

How reproducible:
Didn't try

Expected Results:  Upgrade from earlier rawhide to skipjack should freshen all
packets instead of additional install

Additional info:
Comment 1 Jeremy Katz 2002-04-05 14:09:19 EST
Rawhide is completely at your own risk and changes significantly over the course
of a development cycle, regularly in ways that prevent upgrades.  If you look in
your upgrade.log, you'll probably see scriptlet failures, thus the duplicate
packages in your rpmdb.

Note You need to log in before you can comment on or make changes to this bug.