Bug 366721 – software update dosn't work goes into debug mode.

Bug 366721 - software update dosn't work goes into debug mode.

Summary:	software update dosn't work goes into debug mode.

Status:	CLOSED INSUFFICIENT_DATA

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	pirut (Show other bugs)
Sub Component:
Version:	7
Hardware:	x86_64 Linux

Priority	low Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-11-05 08:10 EST by kevin petway
Modified:	2008-08-02 19:40 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-12-31 09:49:42 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 system. (2.15 KB, application/octet-stream) 2007-11-05 08:10 EST, kevin petway	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description kevin petway 2007-11-05 08:10:30 EST

Description of problem:

software update goes to bug report
Version-Release number of selected component (if applicable):

2.6.23.1-10.fc7 #1 SMP Fri Oct 19 14:35:28 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:


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


Expected results:


Additional info:

Comment 1 kevin petway 2007-11-05 08:10:30 EST

Created attachment 247941 [details]
debug file from system.

Comment 2 Jeremy Katz 2007-11-05 10:46:08 EST

Can you try installing the updated pirut from the updates-testing repo with
  yum --enablerepo=updates-testing update pirut

and see if that resolves your problem?

Comment 3 Jeremy Katz 2007-12-31 09:49:42 EST

Closing due to inactivity.  If you have further information to add to this
report, please either reopen the bug or file a new one.

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