Hide Forgot
Latest upstream release: 7.66.0 Current version/release in rawhide: 7.65.3-4.fc32 URL: https://curl.haxx.se/ 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. Based on the information from anitya: https://release-monitoring.org/project/381/
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!
There is a regression in the new release that breaks the upstream test-suite and consequently %check. I have submitted a fix for review: https://github.com/curl/curl/pull/4326
(In reply to Kamil Dudka from comment #2) > There is a regression in the new release that breaks the upstream test-suite > and consequently %check. I have submitted a fix for review: > > https://github.com/curl/curl/pull/4326 upstream commit: https://github.com/curl/curl/commit/1ca91bcd
dist-git commits: https://src.fedoraproject.org/rpms/curl/c/da9af162 https://src.fedoraproject.org/rpms/curl/c/e0bf66ef
FEDORA-2019-6d7f6fa2c8 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-6d7f6fa2c8
curl-7.66.0-1.fc31 has been pushed to the Fedora 31 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-2019-6d7f6fa2c8
curl-7.66.0-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.