Bug 458801 - pirut crash when nonexisting repo is not modified
pirut crash when nonexisting repo is not modified
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pirut (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: James Antill
Vladimir Benes
: Desktop
Depends On:
  Show dependency treegraph
Reported: 2008-08-12 08:15 EDT by Vladimir Benes
Modified: 2013-03-12 16:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-03-12 16:17:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vladimir Benes 2008-08-12 08:15:38 EDT
Description of problem:
when bad mirror or location url filed and after warning and reopening repo manager Close button clicked.. pirut crashes 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.run pirut
2.open repomanager and add repository with nonexisting mirror (or location)
3.click close
4.when warning shows click repository manager
5.click close without any change 
Actual results:

Expected results:
go back to warning

Additional info:
maybe also when network is down
Comment 1 James Antill 2013-03-12 16:17:08 EDT
This request was evaluated by Red Hat Engineering for inclusion in a Red 
Hat Enterprise Linux maintenance release.

Red Hat does not currently plan to provide this change in a Red Hat 
Enterprise Linux update release for currently deployed products.

With the goal of minimizing risk of change for deployed systems, and in 
response to customer and partner requirements, Red Hat takes a 
conservative approach when evaluating enhancements for inclusion in 
maintenance updates for currently deployed products. The primary 
objectives of update releases are to enable new hardware platform 
support and to resolve critical defects.

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