Bug 141427

Summary: system-config-date test update conflicts with firstboot
Product: [Fedora] Fedora Reporter: Jef Spaleta <jspaleta>
Component: firstbootAssignee: Adrian Likins <alikins>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 2CC: mattdm, nphilipp
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: 2005-05-02 07:43:25 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 Jef Spaleta 2004-12-01 01:33:08 UTC
Description of problem:
yum update system-config-date
fails with a conflict with firstboot.

rpm -Uvh system-config-date-1.7.13-0.fc2.1.noarch.rpm
error: Failed dependencies:
       firstboot <= 1.3.26 conflicts with
system-config-date-1.7.13-0.fc2.1

rpm -q firstboot
firstboot-1.3.14-1

Comment 1 Nils Philippsen 2004-12-01 13:12:42 UTC
Bah, should have thought of that one before. Adrian, I'll leave it to
you whether firstboot should be updated in FC2, if not bump it back to
me and I'll withdraw the update.

Comment 2 Adrian Likins 2004-12-02 22:17:30 UTC
hmm, at the moment, I'd rather not do a update for fc2.

maybe once the rhel stuff is squared away a bit.

Comment 3 Nils Philippsen 2004-12-03 09:50:27 UTC
OK, then I'll retract the system-config-date update for now.

Comment 4 Matthew Miller 2005-04-26 16:26:10 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Comment 5 Jef Spaleta 2005-05-01 01:35:07 UTC
I'm pretty sure this bug can be closed since the offending update was retracted
as per comment #3.