Bug 221761 - Error when updated MKINITRD
Summary: Error when updated MKINITRD
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: 6
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Peter Jones
QA Contact: David Lawrence
URL:
Whiteboard: bzcl34nup
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-01-07 16:57 UTC by Mark A
Modified: 2008-05-06 17:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-06 17:19:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mark A 2007-01-07 16:57:15 UTC
Description of problem:
I use the Software Updater package to automatically notify me of package
updates.  All updates work correctly except the update to MKINITRD.  The
software indicates the MKINITRD package needs to be updated (below is the
package information):

          ID  FEDORA-2006-1398
        Type  bugfix
      Status  final
      Issued  2006-12-14 11:29:09.16
     Updated  2006-12-14 11:29:09.16
 Description  This update is needed for kernel-2.6.19 .

When running the update, I get an error (see below):

('file /sbin/mkinitrd from install of mkinitrd-5.1.19.0.2-1 conflicts with file
from package mkinitrd-5.1.19-1', (7, '/sbin/mkinitrd', 0L))

All other packages have updated successfully.  I just completed a reinstall of
Fedora Core 6 and installed all updates that were available to get to the most
current version.  I have installed one other package - Turboprint - and
installed that package via the RPM file that was available.  

Version-Release number of selected component (if applicable):
See comments in above description.

How reproducible: 
This occurs every time I try to update - regardless of the tool that I try to
use (Software Updater or YUM Externder - both of which are listed as in the
Applications option under System Tools).

Steps to Reproduce:
1. Run Software Updater
2. Select the MKINITRD package updates
3. Apply the updates.
  
Actual results:
Listed in description above.

Expected results:
I expected to get a message that the software was updated successfully.

Additional info:

Comment 1 Bug Zapper 2008-04-04 05:31:20 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 2 Bug Zapper 2008-05-06 17:19:08 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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