Source: ruby-vcr Version: 6.0.0+really5.0.0-6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20250128 ftbfs-trixie
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cannot load such file -- rack/handler/webrick > # > /build/reproducible-path/ruby-vcr-6.0.0+really5.0.0/spec/support/vcr_localhost_server.rb:2:in > `<top (required)>' > # > /build/reproducible-path/ruby-vcr-6.0.0+really5.0.0/spec/spec_helper.rb:14:in > `require_relative' > # > /build/reproducible-path/ruby-vcr-6.0.0+really5.0.0/spec/spec_helper.rb:14:in > `<top (required)>' > # > /build/reproducible-path/ruby-vcr-6.0.0+really5.0.0/spec/lib/vcr_spec.rb:1:in > `<top (required)>' > > Finished in 0.00006 seconds (files took 0.57648 seconds to load) > 0 examples, 0 failures, 22 errors occurred outside of examples > > /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 --format documentation failed > ERROR: Test "ruby3.3" failed: The full build log is available from: http://qa-logs.debian.net/2025/01/28/ruby-vcr_6.0.0+really5.0.0-6_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250128;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250128&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
