Bug 711038 - libdrm-2.4.26 is available
Summary: libdrm-2.4.26 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libdrm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-06 10:19 UTC by Upstream Release Monitoring
Modified: 2011-06-10 13:28 UTC (History)
1 user (show)

Fixed In Version: libdrm-2.4.26-1.fc15
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-10 13:28:28 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Upstream Release Monitoring 2011-06-06 10:19:06 UTC 
Latest upstream release: 2.4.26
Current version in Fedora Rawhide: 2.4.25
URL: http://dri.freedesktop.org/libdrm/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Comment 1 Fedora Update System 2011-06-06 15:45:20 UTC 
libdrm-2.4.26-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/libdrm-2.4.26-1.fc15
Comment 2 Fedora Update System 2011-06-07 04:41:54 UTC 
Package libdrm-2.4.26-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libdrm-2.4.26-1.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/libdrm-2.4.26-1.fc15
then log in and leave karma (feedback).
Comment 3 Fedora Update System 2011-06-10 13:28:23 UTC 
libdrm-2.4.26-1.fc15 has been pushed to the Fedora 15 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.