Bug 744540

Summary: cppcheck-1.51 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: cppcheckAssignee: Susi Lehtola <susi.lehtola>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: susi.lehtola, ville.skytta
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cppcheck-1.51-1.fc16 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-30 00:29:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2011-10-09 10:07:07 UTC
Latest upstream release: 1.51
Current version in Fedora Rawhide: 1.50
URL: http://sourceforge.net/projects/cppcheck/files/

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-10-09 16:01:55 UTC
cppcheck-1.51-1.el4 has been submitted as an update for Fedora EPEL 4.
https://admin.fedoraproject.org/updates/cppcheck-1.51-1.el4

Comment 2 Fedora Update System 2011-10-09 16:02:04 UTC
cppcheck-1.51-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/cppcheck-1.51-1.fc16

Comment 3 Fedora Update System 2011-10-09 16:02:13 UTC
cppcheck-1.51-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/cppcheck-1.51-1.fc15

Comment 4 Fedora Update System 2011-10-09 16:02:26 UTC
cppcheck-1.51-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/cppcheck-1.51-1.fc14

Comment 5 Fedora Update System 2011-10-09 16:02:35 UTC
cppcheck-1.51-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/cppcheck-1.51-1.el6

Comment 6 Fedora Update System 2011-10-09 16:02:45 UTC
cppcheck-1.51-1.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/cppcheck-1.51-1.el5

Comment 7 Fedora Update System 2011-10-09 19:13:16 UTC
Package cppcheck-1.51-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cppcheck-1.51-1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-14066
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2011-10-30 00:29:39 UTC
cppcheck-1.51-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2011-10-30 00:37:14 UTC
cppcheck-1.51-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2011-10-31 18:58:11 UTC
cppcheck-1.51-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2011-10-31 18:59:01 UTC
cppcheck-1.51-1.el4 has been pushed to the Fedora EPEL 4 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2011-10-31 18:59:18 UTC
cppcheck-1.51-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2011-11-05 01:28:35 UTC
cppcheck-1.51-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.