Bug 755678

Summary: bad baseurl for rawhide
Product: [Fedora] Fedora Reporter: John Reiser <jreiser>
Component: fedora-releaseAssignee: Dennis Gilmore <dennis>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dennis
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-15 07:57:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description John Reiser 2011-11-21 18:18:55 UTC 
Description of problem: /etc/yum.repos.d/fedora-rawhide.repo contains a bad baseurl for rawhide.


Version-Release number of selected component (if applicable):
fedora-release-rawhide-17-0.2.noarch


How reproducible:
Every time

Steps to Reproduce:
1. yum install fedora-release-rawhide
2. grep baseurl /etc/yum.repos.d/fedora-rawhide.repo
3.
  
Actual results:
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/$basearch/os/
and corresponding lines for up rawhide-debuginfo and rawhide-source.
Notice absence of "/rawhide" in that url.

Expected results:
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/rawhide/$basearch/os/
and corresponding lines for up rawhide-debuginfo and rawhide-source.
Notice presence of "/rawhide" in that url.

Additional info: The fedora mirror system often has an unpredictable lag of several hours between the posting of "rawhide report" to devel.org and the availability of new builds on any particular mirror.  This delay impedes daily following of rawhide.  For faster turn-around, one can bypass the mirror system by using:
baseurl=http://download.fedora.redhat.com/pub/fedora/linux/development/rawhide/$basearch/os/
Comment 1 Jens Petersen 2013-03-15 07:57:57 UTC 

*** This bug has been marked as a duplicate of bug 676966 ***