Red Hat Bugzilla – Bug 207281
bad anaconda-base-200609190431.i386.repo repo
Last modified: 2014-01-21 17:55:24 EST
Description of problem:
Yum fails due to corrupt repo
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum -y update
Deprecated constant TYPE_INTERFACE during plugin initialization.
Please use TYPE_INTERACTIVE instead.
Loading "installonlyn" plugin
Repository 'anaconda-base-200609190431.i386' is missing name in configuration,
Setting up Update Process
Setting up repositories
file:///mnt/source/./repodata/repomd.xml: [Errno 5] OSError: [Errno 2] No such
file or directory: '/mnt/source/./repodata/repomd.xml'
Trying other mirror.
Error: Cannot open/read repomd.xml file for repository:
Fresh install of today's (Sept 20, 06) Rawhide
Created attachment 136734 [details]
the corrupted repo
The repo conf is written out by anaconda but it should be disabled. I'll look into.
User email@example.com's account has been closed
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.
If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
I can do a yum update from a freshly installed rawhide with no error that
resembles the one described in the original comment. Please reopen the issue if
you still see the same behavior.