Bug 127363 - samba not updated during FC2 update from FC1
Summary: samba not updated during FC2 update from FC1
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-07 04:49 UTC by Colin Kuskie
Modified: 2007-11-30 22:10 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2004-07-07 15:52:41 UTC


Attachments (Terms of Use)

Description Colin Kuskie 2004-07-07 04:49:16 UTC
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
system.

Comment 1 Jeremy Katz 2004-07-07 15:52:41 UTC
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.