Source: ruby-virtus Version: 1.0.5-3.1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: [email protected] Usertags: ruby3.1
Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-virtus with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > expected NoMethodError with "Expected \"not a hash, really\" to > respond to #to_hash", got #<NoMethodError: Expected "not a hash, really" to > respond to #to_hash > > ::Hash.try_convert(attributes) or raise( > ^^^^^> with backtrace: > # ./lib/virtus/attribute_set.rb:196:in `coerce' > # ./lib/virtus/attribute_set.rb:170:in `set' > # ./lib/virtus/instance_methods.rb:17:in `initialize' > # ./spec/unit/virtus/attributes_writer_spec.rb:33:in `new' > # ./spec/unit/virtus/attributes_writer_spec.rb:33:in `block (4 > levels) in <top (required)>' > # ./spec/unit/virtus/attributes_writer_spec.rb:33:in `block (3 > levels) in <top (required)>' > # ./spec/unit/virtus/attributes_writer_spec.rb:33:in `block (3 levels) > in <top (required)>' > > Finished in 0.4125 seconds (files took 0.26456 seconds to load) > 462 examples, 1 failure, 2 pending > > Failed examples: > > rspec ./spec/unit/virtus/attributes_writer_spec.rb:32 # Virtus#attributes= > with a class raises when attributes is not hash-like object > > Randomized with seed 53745 > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-virtus/ruby-virtus_1.0.5-3.1+rebuild1663008303_amd64-2022-09-12T18:45:04Z.build To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on when you try this, it might mean installing ruby-all-dev from experimental, or if the transition has already started, a normal build on unstable will be enough. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. 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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects
signature.asc
Description: PGP signature
