Bug 152926 - FC1 is not yumified
FC1 is not yumified
Product: Fedora Legacy
Classification: Retired
Component: General (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Fedora Legacy Bugs
Depends On:
  Show dependency treegraph
Reported: 2005-03-19 22:20 EST by David Lawrence
Modified: 2007-04-18 13:22 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-11 20:14:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Lawrence 2005-03-30 18:32:39 EST
One can not use yum with FC1 while FC1 updates via yum.
These headers have been missing for a while.

------- Additional Comments From dom@earth.li 2005-03-25 14:11:03 ----

http://download.fedoralegacy.org/fedora/1/updates/i386/headers/ appears to
contain yum headers. Are you using a mirror which doesn't include these headers?
Have you correctly configured yum according to
http://www.fedoralegacy.org/docs/yum-fc1.php? 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 hvdkooij@vanderkooij.org 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 dkl@redhat.com 2005-03-30 18:32 -------

This bug previously known as bug 2458 at https://bugzilla.fedora.us/
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, dkl@redhat.com.
   Previous reporter was hvdkooij@vanderkooij.org.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

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