Bug#1019628: ruby-hashie: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "The property 'middle_name' is not defined for DashTest.", got #

Control: reassign -1 ruby-rspec-expectations Control: retitle -1 ruby-rspec-expectations: raise_error() matcher does not work with ruby3.1 Control: forwarded -1 https://github.com/rspec/rspec-expectations/issues/1338 Control: affects -1 src:ruby-hashie On Sat, Nov 19, 2022 at 03:29:31PM +0200,

Bug#1019628: ruby-hashie: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "The property 'middle_name' is not defined for DashTest.", got #

Control: tags -1 fixed-upstream On Mon, Sep 12, 2022 at 09:47:14PM -0300, Antonio Terceiro wrote: > Source: ruby-hashie > Version: 3.5.5-4 > Severity: important > Justification: FTBFS > Tags: bookworm sid ftbfs > User: debian-r...@lists.debian.org > Usertags: ruby3.1 > > Hi, > > We are about to

Bug#1019628: ruby-hashie: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "The property 'middle_name' is not defined for DashTest.", got #

Source: ruby-hashie Version: 3.5.5-4 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-hashie with ruby3.1 enabled, the build failed.