Bug 180014

Summary: anaconda produces syntax error in anaconda.repo
Product: [Fedora] Fedora Reporter: Roy-Magne Mo <rmo>
Component: anacondaAssignee: Paul Nasrat <nobody+pnasrat>
Status: CLOSED RAWHIDE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: dwmw2
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-27 22:31:32 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:
Bug Depends On:    
Bug Blocks: 150222    
Attachments:
Description Flags
anaconda.repo created by anaconda on install none

Description Roy-Magne Mo 2006-02-04 18:12:29 UTC 
Description of problem:
Installing todays rawhide as a xen guest, fedora produces a anaconda.repo that
halts yum

Version-Release number of selected component (if applicable):
10.91.14-1 (not 100% sure of this)
yum-2.5.1-4

How reproducible:
every time yum runs, havent't tried reinstalling yet 

Steps to Reproduce:
1. install rawhide as of today
2. yum upgrade or yum update
3.
  
Actual results:
# yum upgrade
Options Error: Error parsing 'gpgkey': URL must be http, ftp, file or https not ""

[..]

Expected results:
yum should pull in upgrades

Additional info:
--disablerepo=anaconda does not work, have to move the file out of it's way.
When commenting out gpgkey, it complains about mirrorlist that has 'None' as a
value - and then goes on complaining about the others with 'None'

I'm attaching the anaconda.repo
Comment 1 Roy-Magne Mo 2006-02-04 18:12:29 UTC 
Created attachment 124175 [details]
anaconda.repo created by anaconda on install
Comment 2 Paul Nasrat 2006-02-06 16:22:37 UTC 
Thanks for the bug report. I think we need to make repo.dump smarter.
Comment 3 Jeremy Katz 2006-02-07 16:17:07 UTC 
*** Bug 180365 has been marked as a duplicate of this bug. ***
Comment 4 Jeremy Katz 2006-02-27 22:31:32 UTC 
We're not writing them out for now