Bug 839549 - php-pear-PHP-CodeSniffer-1.3.5 is available
php-pear-PHP-CodeSniffer-1.3.5 is available
Product: Fedora
Classification: Fedora
Component: php-pear-PHP-CodeSniffer (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Christof Damian
Fedora Extras Quality Assurance
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2012-07-12 05:30 EDT by Upstream Release Monitoring
Modified: 2012-07-23 16:25 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-07-23 16:25:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Upstream Release Monitoring 2012-07-12 05:30:00 EDT
Latest upstream release: 1.3.5
Current version in Fedora Rawhide: 1.3.4
URL: http://pear.php.net/package/PHP_CodeSniffer/download/

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:
Comment 1 Fedora Update System 2012-07-13 15:55:35 EDT
php-pear-PHP-CodeSniffer-1.3.5-1.fc17 has been submitted as an update for Fedora 17.
Comment 2 Fedora Update System 2012-07-14 17:51:41 EDT
Package php-pear-PHP-CodeSniffer-1.3.5-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 php-pear-PHP-CodeSniffer-1.3.5-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Comment 3 Fedora Update System 2012-07-23 16:25:18 EDT
php-pear-PHP-CodeSniffer-1.3.5-1.fc17 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.