Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1260813

Summary: libebur128-v1.1.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: libebur128Assignee: Simone Caronni <negativo17>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: i
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libebur128-1.2.0-1.el7 libebur128-1.2.0-1.fc25 libebur128-1.2.0-1.fc24 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-03 17:52:00 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 2015-09-08 00:13:13 UTC
Latest upstream release: v1.0.3
Current version/release in rawhide: 1.0.2-1.fc24
URL: https://github.com/jiixyj/libebur128

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

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Comment 1 Upstream Release Monitoring 2015-09-08 00:13:18 UTC
Failed to kick off scratch build.

cmd:  spectool -g /var/tmp/thn-sSDwMt/libebur128.spec
return code:  22
stdout:
Getting https://github.com/jiixyj/libebur128/archive/vv1.0.3.tar.gz#/libebur128-v1.0.3.tar.gz to ./libebur128-v1.0.3.tar.gz

stderr:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   126    0   126    0     0    247      0 --:--:-- --:--:-- --:--:--   247

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found

Comment 2 Upstream Release Monitoring 2016-02-16 00:13:41 UTC
Latest upstream release: v1.1.0
Current version/release in rawhide: 1.0.3-2.fc24
URL: https://github.com/jiixyj/libebur128

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

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Comment 3 Upstream Release Monitoring 2016-02-16 00:13:48 UTC
Failed to kick off scratch build.

cmd:  spectool -g /var/tmp/thn-hmbjS7/libebur128.spec
return code:  22
stdout:
Getting https://github.com/jiixyj/libebur128/archive/vv1.1.0.tar.gz#/libebur128-v1.1.0.tar.gz to ./libebur128-v1.1.0.tar.gz
Getting https://tech.ebu.ch/files/live/sites/tech/files/shared/testmaterial/ebu-loudness-test-setv03.zip to ./ebu-loudness-test-setv03.zip
Getting https://github.com/jiixyj/libebur128/commit/0bf8339ba08859531cdb5b8736a101302a51a2e7.patch to ./0bf8339ba08859531cdb5b8736a101302a51a2e7.patch

stderr:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   126    0   126    0     0    362      0 --:--:-- --:--:-- --:--:--   363

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
./ebu-loudness-test-setv03.zip already exists, skipping download
./0bf8339ba08859531cdb5b8736a101302a51a2e7.patch already exists, skipping download

Comment 4 Fedora Admin XMLRPC Client 2016-02-26 17:38:20 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Fedora Admin XMLRPC Client 2016-12-16 13:39:03 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Fedora Update System 2016-12-17 08:52:33 UTC
libebur128-1.2.0-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-d0f65ace4a

Comment 7 Fedora Update System 2016-12-17 08:52:44 UTC
libebur128-1.2.0-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-cd3140798e

Comment 8 Fedora Update System 2016-12-17 08:52:52 UTC
libebur128-1.2.0-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-08ea08d4d3

Comment 9 Fedora Update System 2016-12-17 08:53:00 UTC
libebur128-1.2.0-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-d5468b814d

Comment 10 Fedora Update System 2016-12-19 01:51:44 UTC
libebur128-1.2.0-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-d5468b814d

Comment 11 Fedora Update System 2016-12-19 02:28:26 UTC
libebur128-1.2.0-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-08ea08d4d3

Comment 12 Fedora Update System 2016-12-19 02:30:57 UTC
libebur128-1.2.0-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-cd3140798e

Comment 13 Fedora Update System 2016-12-20 00:57:57 UTC
libebur128-1.2.0-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-d0f65ace4a

Comment 14 Fedora Update System 2017-01-03 17:52:00 UTC
libebur128-1.2.0-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.

Comment 15 Fedora Update System 2017-01-03 20:22:18 UTC
libebur128-1.2.0-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 16 Fedora Update System 2017-01-03 21:24:26 UTC
libebur128-1.2.0-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.