Bug 331051 - yum / pup unable to run. Cannot find path for repository for gs-0.10-apps
Summary: yum / pup unable to run. Cannot find path for repository for gs-0.10-apps
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pirut
Version: 7
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-14 00:36 UTC by Jeffrey Doshna
Modified: 2008-08-02 23:40 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2007-12-31 14:49:27 UTC


Attachments (Terms of Use)
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 (2.19 KB, application/octet-stream)
2007-10-14 00:36 UTC, Jeffrey Doshna
no flags Details

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.  


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