Bug 180014 - anaconda produces syntax error in anaconda.repo
Summary: anaconda produces syntax error in anaconda.repo
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Paul Nasrat
QA Contact: Mike McLean
: 180365 (view as bug list)
Depends On:
Blocks: FC5Blocker
TreeView+ depends on / blocked
Reported: 2006-02-04 18:12 UTC by Roy-Magne Mo
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-27 22:31:32 UTC
Type: ---

Attachments (Terms of Use)
anaconda.repo created by anaconda on install (491 bytes, text/plain)
2006-02-04 18:12 UTC, Roy-Magne Mo
no flags Details

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)

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

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