Bug 127363 - samba not updated during FC2 update from FC1
samba not updated during FC2 update from FC1
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-07-07 00:49 EDT by Colin Kuskie
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-07 11:52:41 EDT
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 Colin Kuskie 2004-07-07 00:49:16 EDT
Description of problem:
Last week I updated all RPMs on my FC1 box, which installed the
latest and greatest samba (samba-3.0.4-1.FC1).  Yesterday, I updated
the machine to FC2.  samba was not updated to the version used with
FC2. (3.0.3-5).

Later, when using synaptic to see what updates were available, samba,
samba-common, samba-client and several other RPMs were marked as obsolete,
but trying to manually remove them trashed the system to the point where
metacity would not start up again and I installed over the upgraded
Comment 1 Jeremy Katz 2004-07-07 11:52:41 EDT
anaconda doesn't pull in updates, so it didn't know about the newer
update of samba for FC2.  Since the version number for the FC1 update
was higher than what was shipped in FC2, we had no choice but to leave
the FC1 version installed.

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