[DRE-maint] Bug#1091505: ruby3.3: will FTBFS during trixie support period

Sebastian Andrzej Siewior sebastian at breakpoint.cc
Fri Jan 10 17:07:37 GMT 2025


On 2024-12-27 18:52:20 [+0000], Santiago Vila wrote:
>   1) Failure:
> TestGemBundledCA#test_accessing_rubygems [/<<PKGBUILDDIR>>/test/rubygems/test_bundled_ca.rb:47]:
> rubygems.org is not verifiable using the included certificates. Error was: SSL_connect returned=1 errno=0 peeraddr=[2a04:4e42:400::483]:443 state=error: certificate verify failed (certificate has expired)
> 
>   2) Failure:
> TestGemBundledCA#test_accessing_www_rubygems [/<<PKGBUILDDIR>>/test/rubygems/test_bundled_ca.rb:51]:
> www.rubygems.org is not verifiable using the included certificates. Error was: SSL_connect returned=1 errno=0 peeraddr=[2a04:4e42:200::483]:443 state=error: certificate verify failed (certificate has expired)
> 
>   3) Failure:
> TestGemBundledCA#test_accessing_new_index [/<<PKGBUILDDIR>>/test/rubygems/test_bundled_ca.rb:59]:
> index.rubygems.org is not verifiable using the included certificates. Error was: SSL_connect returned=1 errno=0 peeraddr=[2a04:4e42:200::483]:443 state=error: certificate verify failed (certificate has expired)
> 
>   4) Failure:
> TestGemBundledCA#test_accessing_staging [/<<PKGBUILDDIR>>/test/rubygems/test_bundled_ca.rb:55]:
> staging.rubygems.org is not verifiable using the included certificates. Error was: SSL_connect returned=1 errno=0 peeraddr=[2a04:4e42::483]:443 state=error: certificate verify failed (certificate has expired)
> 
> Finished tests in 617.171218s, 43.0464 tests/s, 10265.7493 assertions/s.
> 26567 tests, 6335725 assertions, 4 failures, 0 errors, 179 skips
…
> About the archive rebuild: This is an effort to keep trixie free from FTBFS bugs
> during its lifetime as a supported distribution, as explained here:

I as looking at this as part of the NMU I just prepared and did not act
on this because it is not a bug as described.
The build fails because it connect at build time to the hosts
- rubygems.org
- www.rubygems.org
- staging.rubygems.org
- index.rubygems.org

and if you push the date too far into the future then the certificates
expire. However if the future date really kicks in then I would expect
the admins to renew the certificates before they expire. The test is
skipped if network connection can not be established.

It would be nice if you could confirm this and close the bug.

> Thanks.

Sebastian



More information about the Pkg-ruby-extras-maintainers mailing list