Bug 85437 - Upgrade from 8.0 to 8.0.94 doesn't remove bdflush
Upgrade from 8.0 to 8.0.94 doesn't remove bdflush
Status: CLOSED WONTFIX
Product: Red Hat Public Beta
Classification: Retired
Component: bdflush (Show other bugs)
phoebe
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Florian La Roche
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-02 14:31 EST by Blair Zajac
Modified: 2015-01-07 19:04 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-03-03 15:35:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Blair Zajac 2003-03-02 14:31:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461; YComp 
5.0.0.0; .NET CLR 1.0.3705)

Description of problem:
I did a series of up2date commands to manually update my 8.0 box to
run 8.0.94.

After the upgrade, I compared the list of RPMs on the system with the
list of RPMs supplied in 8.0.94 and bdflush is not in 8.0.94.

Shouldn't the up2date list have up2date remove bdflush, as it does
other RPMs?


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


How reproducible:
Always

Steps to Reproduce:
1. Install RedHat 8.0
2. Upgrade to 8.0.94
3.
    

Actual Results:  bdflush is still on the system

Expected Results:  I would think that bdflush should be removed

Additional info:
Comment 1 Florian La Roche 2003-03-03 14:47:38 EST
What todo about this? Absorb by kernel or by anaconda or just leave this
installed on the system?

greetings,

Florian La Roche
Comment 3 Florian La Roche 2003-03-03 15:35:39 EST
Ok, closing this entry. bdflush should not harm your system and we
normally keep such rpms installed instead of forcing a removal.

Thanks for this notice,

Florian La Roche

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