Aside from bug 2301249 , one of rubygem-curb testsuite fails only on 32bit, not on 64bit: ``` Error: test_download_bad_url_gives_404(TestCurbCurlDownload): Curl::Err::GotNothingError: Server returned nothing (no headers, no data): Empty reply from server /builddir/build/GIT/curb/lib/curl/easy.rb:80:in `perform' /builddir/build/GIT/curb/lib/curl/easy.rb:462:in `download' /builddir/build/GIT/curb/tests/tc_curl_download.rb:68:in `test_download_bad_url_gives_404' 65: dl_url = "http://127.0.0.1:9129/this_file_does_not_exist.html" 66: dl_path = File.join(Dir::tmpdir, "dl_url_test.file") 67: => 68: curb = Curl::Easy.download(dl_url, dl_path) 69: assert_equal Curl::Easy, curb.class 70: assert_equal 404, curb.response_code 71: ensure ``` The upstream bug report (actually I've reported) is: https://github.com/curl/curl/issues/14272 and it is fixed in: https://github.com/curl/curl/commit/fc273027f16df2dd1eb66ffc7df417f605199e35 Could you backport the above fix to Fedora curl? It is needed to fix rubygem-curb FTBFS. Reproducible: Always
Thanks for the report. There is a patch release planned for tomorrow: https://curl.se/mail/lib-2024-07/0040.html I will rebase curl in Rawhide shortly after the release. Do you want a backport to Fedora 40?
> Do you want a backport to Fedora 40? If possible, I would appreciate it, but not necessarily I think.
FEDORA-2024-9b00b19216 (curl-8.6.0-10.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-9b00b19216
FEDORA-2024-9b00b19216 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-9b00b19216` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-9b00b19216 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-9b00b19216 (curl-8.6.0-10.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.