Bug 755678 - bad baseurl for rawhide
Summary: bad baseurl for rawhide
Keywords:
Status: CLOSED DUPLICATE of bug 676966
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-release
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-21 18:18 UTC by John Reiser
Modified: 2013-03-15 07:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-15 07:57:57 UTC
Type: ---


Attachments (Terms of Use)

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 ***


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