Bug 127363

Summary:	samba not updated during FC2 update from FC1
Product:	[Fedora] Fedora	Reporter:	Colin Kuskie <colink>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED NOTABUG	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-07-07 15:52:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.