Bug 233806 – fedora 7 problem in update repro online

Bug 233806 - fedora 7 problem in update repro online

Summary:	fedora 7 problem in update repro online

Status:	CLOSED CURRENTRELEASE

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Seth Vidal
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-03-25 03:31 EDT by wilfred morrow
Modified:	2008-01-22 11:29 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	3.2.0-1.fc7
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-01-22 11:29:10 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)
bug report (2.94 KB, text/plain) 2007-03-25 03:31 EDT, wilfred morrow	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description wilfred morrow 2007-03-25 03:31:19 EDT

Description of problem:

problem occurred in installing updates packages
Version-Release number of selected component (if applicable):
fedora 7

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 wilfred morrow 2007-03-25 03:31:19 EDT

Created attachment 150844 [details]
bug report

Comment 2 Matthew Miller 2007-04-10 11:53:13 EDT

Bulk message: Fedora 7 test bugs should be filed against "devel", not against
test1/2/3. This isn't obvious, I know. Moving this report so it isn't lost.

Comment 3 Michael Schwendt 2008-01-22 11:29:10 EST

Wrong component. Misfiled ages ago. As can easily be seen in
the traceback, it was a problem in Yum and not in bug-buddy.
Assuming it was fixed for Fedora 7 (or later). It's highly
unlikely that it wasn't fixed.

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