Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 152926

Summary: FC1 is not yumified
Product: [Retired] Fedora Legacy Reporter: David Lawrence <dkl>
Component: GeneralAssignee: Fedora Legacy Bugs <bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecified   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-12 00:14:41 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 David Lawrence 2005-03-30 23:32:39 UTC
One can not use yum with FC1 while FC1 updates via yum.
These headers have been missing for a while.

------- Additional Comments From 2005-03-25 14:11:03 ---- appears to
contain yum headers. Are you using a mirror which doesn't include these headers?
Have you correctly configured yum according to Can you provide more information
on the error message(s) you have received? I believe that people are
successfully using yum for FC1 at the moment.


------- Additional Comments From 2005-03-28 10:41:23 ----

It seems someone fixed the headers.
They have been unavailable for about a week.

------- Bug moved to this database by 2005-03-30 18:32 -------

This bug previously known as bug 2458 at
Originally filed under the Fedora Legacy product and General component.

Unknown priority P2. Setting to default priority "normal".
Unknown platform PC. Setting to default platform "All".
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here,
   Previous reporter was
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.