• Bug#1102288: ruby-integration: FTBFS: Expected pending 'GSL not availab

    From Santiago Vila@21:1/5 to All on Mon Apr 7 11:50:01 2025
    Package: src:ruby-integration
    Version: 0.1.0-1.1
    Severity: serious
    Tags: ftbfs trixie sid

    Dear maintainer:

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

    --------------------------------------------------------------------------------
    [...]
    debian/rules clean
    dh clean --buildsystem=ruby --with ruby
    dh: warning: Compatibility levels before 10 are deprecated (level 7 in use)
    dh_auto_clean -O--buildsystem=ruby
    dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 7 in use)
    dh_ruby --clean
    W: XS-Ruby-Versions is deprecated, and will be ignored
    dh_clean -O--buildsystem=ruby
    dh_clean: warning: Compatibility levels before 10 are deprecated (level 7 in use)
    debian/rules binary
    dh binary --buildsystem=ruby --with ruby
    dh: warning: Compatibility levels before 10 are deprecated (level 7 in use)
    dh_update_autotools_config -O--buildsystem=ruby
    dh_auto_configure -O--buildsystem=ruby
    dh_auto_configure: warning: Compatibility levels before 10 are deprecated (level 7 in use)
    dh_ruby --configure
    dh_auto_build -O--buildsystem=ruby
    dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 7 in use)
    dh_ruby --build
    dh_auto_test -O--buildsystem=ruby
    dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 7 in use)
    dh_ruby --test
    dh_testroot -O--buildsystem=ruby
    dh_prep -O--buildsystem=ruby
    dh_auto_install --destdir=debian/ruby-integration/ -O--buildsystem=ruby dh_auto_install: warning: Compatibility levels before 10 are deprecated (level 7 in use)
    dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-integration

    ┌──────────────────────────────────────────────────────────────────────────────┐
    │ ruby-integration: Install files │
    └──────────────────────────────────────────────────────────────────────────────┘

    install -d /<<PKGBUILDDIR>>/debian/ruby-integration/usr/lib/ruby/vendor_ruby install -D -m644 /<<PKGBUILDDIR>>/lib/integration.rb /<<PKGBUILDDIR>>/debian/ruby-integration/usr/lib/ruby/vendor_ruby/integration.rb

    ┌──────────────────────────────────────────────────────────────────────────────┐
    │ ruby-integration: Install Rubygems integration metadata │
    └──────────────────────────────────────────────────────────────────────────────┘

    generating gemspec at /<<PKGBUILDDIR>>/debian/ruby-integration/usr/share/rubygems-integration/all/specifications/integration-0.1.0.gemspec
    /usr/bin/ruby3.3 /usr/bin/gem2deb-test-runner

    ┌──────────────────────────────────────────────────────────────────────────────┐
    │ Run tests for ruby3.3 from debian/ruby-tests.rake │
    └──────────────────────────────────────────────────────────────────────────────┘

    RUBYLIB=/<<PKGBUILDDIR>>/debian/ruby-integration/usr/lib/ruby/vendor_ruby:. GEM_PATH=/<<PKGBUILDDIR>>/debian/ruby-integration/usr/share/rubygems-integration/all:/var/lib/gems/3.3.0:/usr/local/lib/ruby/gems/3.3.0:/usr/lib/ruby/gems/3.3.0:/usr/lib/x86_64-
    linux-gnu/ruby/gems/3.3.0:/usr/share/rubygems-integration/3.3.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.3.0 ruby3.3 -S rake --rakelibdir /gem2deb-nonexistent -f debian/ruby-tests.rake
    /usr/bin/ruby3.3 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.13.1/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/exe/rspec --pattern ./spec/\*\*/\*_spec.rb
    ..FFFFWARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to
    pass without even executing the method you are intending to call. Actual error raised was #<RuntimeError: Ruby methods doesn't support infinity bounds>. Instead consider providing a specific error class or message. This message can be suppressed by
    setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. Called from /<<PKGBUILDDIR>>/spec/integration_spec.rb:61:in `block (2 levels) in <top (required)>'.
    .

    Failures:

    1) Integration should return a correct value for a complex integration with gsl methods FIXED
    Expected pending 'GSL not available' to fail. No error was raised.
    # ./spec/integration_spec.rb:19

    2) Integration should return correct integration for infinity bounds FIXED
    Expected pending 'GSL not available' to fail. No error was raised.
    # ./spec/integration_spec.rb:30

    3) Integration should return correct integration for infinity lower bound FIXED
    Expected pending 'GSL not available' to fail. No error was raised.
    # ./spec/integration_spec.rb:39

    4) Integration should return correct integration for infinity upper bound FIXED
    Expected pending 'GSL not available' to fail. No error was raised.
    # ./spec/integration_spec.rb:49

    Deprecation Warnings:

    Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` instead. Called
    from /<<PKGBUILDDIR>>/spec/integration_spec.rb:9:in `block (3 levels) in <top (required)>'.


    If you need more of the backtrace for any of these deprecations to
    identify where to make the necessary changes, you can configure `config.raise_errors_for_deprecations!`, and it will turn the
    deprecation warnings into errors, giving you the full backtrace.

    1 deprecation warning total

    Finished in 0.00697 seconds (files took 0.06454 seconds to load)
    7 examples, 4 failures

    Failed examples:

    rspec ./spec/integration_spec.rb:19 # Integration should return a correct value for a complex integration with gsl methods
    rspec ./spec/integration_spec.rb:30 # Integration should return correct integration for infinity bounds
    rspec ./spec/integration_spec.rb:39 # Integration should return correct integration for infinity lower bound
    rspec ./spec/integration_spec.rb:49 # Integration should return correct integration for infinity upper bound

    /usr/bin/ruby3.3 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.13.1/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/exe/rspec --pattern ./spec/\*\*/\*_spec.rb
    failed
    ERROR: Test "ruby3.3" failed. Exiting.
    dh_auto_install: error: dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-integration returned exit code 1
    make: *** [debian/rules:16: binary] Error 255
    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/202504/

    About the archive rebuild: The build was made on virtual machines from AWS, 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 add an affects on src:ruby-integration, 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)