Bug 230847 – Update of Fedora 7 install failed

Bug 230847 - Update of Fedora 7 install failed

Summary:	Update of Fedora 7 install failed

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	yum (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-03-03 11:39 EST by Burton C. Wise
Modified:	2014-01-21 17:57 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-03-05 15:08:28 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Debug file from crash (3.78 KB, text/plain) 2007-03-03 11:39 EST, Burton C. Wise	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Burton C. Wise 2007-03-03 11:39:30 EST

Description of problem:
Update of Post Fedora 7 install failed to 

Version-Release number of selected component (if applicable):
Fedora 7 Test 2

How reproducible:
Attempt to update all.

Steps to Reproduce:
1. Install Fedora 7 Test 2
2. Login and select to update all
3.
  
Actual results:
Update failed to resolve certain depenedencies relates to Libgcj even though all
libgcj packages were installed. Afterwards update crashed.

Expected results:
All packages updated successfully

Additional info:
See attached debug file

Comment 1 Burton C. Wise 2007-03-03 11:39:30 EST

Created attachment 149181 [details]
Debug file from crash

Comment 2 Burton C. Wise 2007-03-03 11:42:06 EST

In order to get system to update I had to remove all updated packages that
depended on libgcj such as cairo-java,libvte-java-libglade-java, etc.

Comment 3 Jeremy Katz 2007-03-05 15:08:28 EST

This is fixed in yum 3.1.3

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