Bug 1115808

Summary: blosc-1.5.2 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: bloscAssignee: Thibault North <thibault.north>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: menantea, thibault.north, zbyszek
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: blosc-1.5.2-1.fc20 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-17 05:37:06 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 2014-07-03 07:30:47 UTC
Latest upstream release: 1.3.6
Current version/release in Fedora Rawhide: 1.3.5-2.fc21
URL: https://api.github.com/repos/Blosc/c-blosc/tags

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 Upstream Release Monitoring 2014-07-06 11:51:31 UTC
Latest upstream release: 1.4.0
Current version/release in Fedora Rawhide: 1.3.5-2.fc21
URL: https://api.github.com/repos/Blosc/c-blosc/tags

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 2 Upstream Release Monitoring 2014-07-11 07:08:38 UTC
Latest upstream release: 1.4.1
Current version/release in Fedora Rawhide: 1.3.5-2.fc21
URL: https://api.github.com/repos/Blosc/c-blosc/tags

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 3 Menanteau Guy 2014-07-29 09:25:53 UTC
blosc-1.3.5-2 build failed on ppc64le, http://ppc.koji.fedoraproject.org/koji/buildinfo?buildID=249966

ppc64le build is ok using this new 1.4.1 version.
An update of source package will be appreciated. thanks

Comment 4 Upstream Release Monitoring 2014-11-12 12:11:53 UTC
Latest upstream release: 1.5.0
Current version/release in Fedora Rawhide: 1.3.5-3.fc22
URL: https://api.github.com/repos/Blosc/c-blosc/tags

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 Soon this service will be implemented by a new system: https://github.com/fedora-infra/anitya/
It will require to manage monitored projects via a new web interface. Please make yourself familiar with the new system to ease the transition.

Comment 5 Upstream Release Monitoring 2014-12-23 14:14:04 UTC
Latest upstream release: 1.5.1
Current version/release in Fedora Rawhide: 1.3.5-3.fc22
URL: https://api.github.com/repos/Blosc/c-blosc/tags

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 Soon this service will be implemented by a new system: https://release-monitoring.org/
It will require to manage monitored projects via a new web interface. Please make yourself familiar with the new system to ease the transition.

Comment 6 Upstream Release Monitoring 2015-01-03 22:56:02 UTC
Latest upstream release: 1.5.2
Current version/release in Fedora Rawhide: 1.3.5-3.fc22
URL: https://api.github.com/repos/Blosc/c-blosc/tags

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 Soon this service will be implemented by a new system: https://release-monitoring.org/
It will require to manage monitored projects via a new web interface. Please make yourself familiar with the new system to ease the transition.

Comment 7 Fedora Update System 2015-01-08 15:59:09 UTC
python-blosc-1.2.4-1.fc21,blosc-1.5.2-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/python-blosc-1.2.4-1.fc21,blosc-1.5.2-1.fc21

Comment 8 Fedora Update System 2015-01-08 16:00:53 UTC
blosc-1.5.2-1.fc20,python-blosc-1.2.4-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/blosc-1.5.2-1.fc20,python-blosc-1.2.4-1.fc20

Comment 9 Fedora Update System 2015-01-08 23:29:28 UTC
Package blosc-1.5.2-1.fc20, python-blosc-1.2.4-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing blosc-1.5.2-1.fc20 python-blosc-1.2.4-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-0411/blosc-1.5.2-1.fc20,python-blosc-1.2.4-1.fc20
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2015-01-17 05:37:06 UTC
python-blosc-1.2.4-1.fc21, blosc-1.5.2-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2015-01-17 05:46:17 UTC
blosc-1.5.2-1.fc20, python-blosc-1.2.4-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.