Package: src:ruby-vcr Version: 4.0.0-1 Severity: serious Tags: ftbfs Dear maintainer:
I tried to build this package in buster but it failed: -------------------------------------------------------------------------------- [...] debian/rules binary-indep dh binary-indep --buildsystem=ruby --with ruby dh_update_autotools_config -i -O--buildsystem=ruby dh_autoreconf -i -O--buildsystem=ruby dh_auto_configure -i -O--buildsystem=ruby dh_ruby --configure dh_auto_build -i -O--buildsystem=ruby dh_ruby --build dh_ruby --build dh_auto_test -i -O--buildsystem=ruby dh_ruby --test create-stamp debian/debhelper-build-stamp dh_testroot -i -O--buildsystem=ruby dh_prep -i -O--buildsystem=ruby [... snipped ...] # An HTTP request has been made that VCR does not know how to handle: # GET http://localhost:34979/search?q=thread # # VCR are currently using the following cassettes: # - /<<PKGBUILDDIR>>/tmp/cassette_library_dir/search.yml # - :record => :once # - :match_requests_on => [:method, :uri] # - /<<PKGBUILDDIR>>/tmp/cassette_library_dir/foo.yml # - :record => :once # - :match_requests_on => [:method, :uri] # # Under the current configuration VCR can not find a suitable HTTP interaction # to replay and is prevented from recording new requests. There are a few ways # you can deal with this: # # * If you're surprised VCR is raising this error # and want insight about how VCR attempted to handle the request, # you can use the debug_logger configuration option to log more details [1]. # * You can use the :new_episodes record mode to allow VCR to # record this new request to the existing cassette [2]. # * If you want VCR to ignore this request (and others like it), you can # set an `ignore_request` callback [3]. # * The current record mode (:once) does not allow new requests to be recorded # to a previously recorded cassette. You can delete the cassette file and re-run # your tests to allow the cassette to be recorded with this request [4]. # # [1] https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/configuration/debug-logging # [2] https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/record-modes/new-episodes # [3] https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/configuration/ignore-request # [4] https://www.relishapp.com/vcr/vcr/v/4-0-0/docs/record-modes/once # ================================================================================ # ./lib/vcr/request_handler.rb:97:in `on_unhandled_request' Finished in 26.5 seconds (files took 2.79 seconds to load) 1725 examples, 1 failure Failed examples: rspec ./spec/acceptance/concurrency_spec.rb:15 # VCR when used in a multithreaded environment with an around_http_request can use a cassette in an #around_http_request hook /usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed ERROR: Test "ruby2.5" failed. Exiting. dh_auto_install: dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-vcr returned exit code 1 make: *** [debian/rules:6: binary-indep] Error 1 dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit status 2 -------------------------------------------------------------------------------- (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here at least in the arm64 architecture: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-vcr.html where you can get a full build log if you need it. 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.