Latest upstream release: 1.97.7 Current version in Fedora Rawhide: 1.97.5 URL: http://ispras.linuxbase.org/index.php/ABI_compliance_checker_Downloads 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
Latest upstream release: 1.97.8 Current version in Fedora Rawhide: 1.97.7 URL: http://ispras.linuxbase.org/index.php/ABI_compliance_checker_Downloads 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
abi-compliance-checker-1.97.8-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/abi-compliance-checker-1.97.8-1.fc16
abi-compliance-checker-1.97.8-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abi-compliance-checker-1.97.8-1.fc15
abi-compliance-checker-1.97.8-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abi-compliance-checker-1.97.8-1.fc17
Package abi-compliance-checker-1.97.8-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 abi-compliance-checker-1.97.8-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-9288/abi-compliance-checker-1.97.8-1.fc17 then log in and leave karma (feedback).
abi-compliance-checker-1.97.8-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
abi-compliance-checker-1.97.8-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.