This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected Fedora versions. For comments that are specific to the vulnerability please use bugs filed against "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When creating a Bodhi update request, please include this bug ID and the bug IDs of this bug's parent bugs filed against the "Security Response" product (the top-level CVE bugs). Please mention the CVE IDs being fixed in the RPM changelog when available. Bodhi update submission link: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=865483 Please note: this issue affects multiple supported versions of Fedora. Only one tracking bug has been filed; please ensure that it is only closed when all affected versions are fixed. [bug automatically created by: add-tracking-bugs]
librdmacm-1.0.17-0.gitc6bfc1c.1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/librdmacm-1.0.17-0.gitc6bfc1c.1.fc18
librdmacm-1.0.17-0.gitc6bfc1c.1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/librdmacm-1.0.17-0.gitc6bfc1c.1.fc17
Package librdmacm-1.0.17-0.gitc6bfc1c.1.fc17: * 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 librdmacm-1.0.17-0.gitc6bfc1c.1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19892/librdmacm-1.0.17-0.gitc6bfc1c.1.fc17 then log in and leave karma (feedback).
librdmacm-1.0.17-0.gitc6bfc1c.1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
librdmacm-1.0.17-0.gitc6bfc1c.1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.