Bug 819093 - fedora-release needs update for final
fedora-release needs update for final
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: fedora-release (Show other bugs)
17
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Dennis Gilmore
Fedora Extras Quality Assurance
:
Depends On:
Blocks: F17Blocker/F17FinalBlocker
  Show dependency treegraph
 
Reported: 2012-05-04 15:58 EDT by Dennis Gilmore
Modified: 2012-05-07 00:18 EDT (History)
3 users (show)

See Also:
Fixed In Version: fedora-release-17-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-05-07 00:18:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Dennis Gilmore 2012-05-04 15:58:13 EDT
Description of problem:

need to enable metadata caching of fedora repo and disable updates-testing

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Fedora Update System 2012-05-04 16:00:38 EDT
fedora-release-17-1 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/fedora-release-17-1
Comment 2 Fedora Update System 2012-05-04 18:18:47 EDT
Package fedora-release-17-1:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fedora-release-17-1'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-7335/fedora-release-17-1
then log in and leave karma (feedback).
Comment 3 Fedora Update System 2012-05-07 00:18:34 EDT
fedora-release-17-1 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

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