• Bug#1091505: ruby3.3: will FTBFS during trixie support period

    From Santiago Vila@21:1/5 to All on Fri Dec 27 20:00:02 2024
    Package: src:ruby3.3
    Version: 3.3.5-2
    Tags: ftbfs trixie sid
    User: debian-qa@lists.debian.org
    Usertags: ftbfs-during-trixie-support-period

    Dear maintainer:

    During a rebuild of all packages in unstable in the year 2028, your package failed to build:

    --------------------------------------------------------------------------------
    [...]
    [26565/26632] Bug::Time::Test_New#test_nano_new = 0.00 s
    [26566/26632] Bug::Time::Test_New#test_timespec_new = 0.00 s
    [26567/26632] Bug::Time::Test_New#test_timespec_now = 0.00 s

    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

    ruby -v: ruby 3.3.5 (2024-09-03 revision ef084cc8f4) [x86_64-linux-gnu] make[2]: *** [uncommon.mk:945: yes-test-all] Error 4
    make[2]: Leaving directory '/<<PKGBUILDDIR>>'
    make[1]: *** [debian/rules:137: override_dh_auto_test-arch] Error 2
    make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    make: *** [debian/rules:102: binary] Error 2
    dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --------------------------------------------------------------------------------

    The above is just how the build ends and not necessarily the most relevant part.
    If required, the full build log is available here:

    https://people.debian.org/~sanvila/build-logs/ftbfs-future/

    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:

    https://lists.debian.org/debian-devel/2024/05/msg00414.html

    (While they are not yet, please note that the bugs will be RC for trixie)

    The build was made using sbuild and a reduced chroot with only
    build-essential packages.

    If you could not reproduce the bug please contact me privately, as I
    am willing to provide ssh access to a virtual machine where the bug is
    fully reproducible.

    If this is really a bug in one of the build-depends, please use
    reassign and affects, so that this is still visible in the BTS web
    page for this package.

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)