Bug 331051

Summary: yum / pup unable to run. Cannot find path for repository for gs-0.10-apps
Product: [Fedora] Fedora Reporter: Jeffrey Doshna <doshna>
Component: pirutAssignee: Jeremy Katz <katzj>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 7CC: james.antill
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-12-31 14:49:27 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:
Attachments:
Description Flags
Summary: TB8f5a3431 yumRepo.py:749:_getRepoXML:RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: gst-0.10-apps. Please verify its path and try again none

Description Jeffrey Doshna 2007-10-14 00:36:05 UTC 
Description of problem:


ATTACHED REPORT

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


How reproducible:


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


Expected results:


Additional info:
Comment 1 Jeffrey Doshna 2007-10-14 00:36:05 UTC 
Created attachment 226561 [details]
Summary: TB8f5a3431 yumRepo.py:749:_getRepoXML:RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: gst-0.10-apps. Please verify its path and try again
Comment 2 Jeremy Katz 2007-10-16 18:03:32 UTC 
Does this still occur with the pirut in f7-updates-testing?
Comment 3 Jeffrey Doshna 2007-10-18 04:39:21 UTC 
Sorry -- this is a bug under f7.  Typo on my part.
Comment 4 Jeremy Katz 2007-10-22 17:58:05 UTC 
Can you please try the pirut packages available from the f7-updates-testing
repository adn see if the problem continues to occur?
Comment 5 Jeremy Katz 2007-12-31 14:49:27 UTC 
Closing due to inactivity.  If you have further information to add to this
report, please either reopen the bug or file a new one.