ruby-virtus 1.0.5-3.1 is marked for autoremoval from testing on 2022-11-23
It is affected by these RC bugs:
1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
expected NoMethodError with "Expected \"not a hash, really\" to respond to
#to_hash", got
ruby-virtus 1.0.5-3.1 is marked for autoremoval from testing on 2022-11-23
It is affected by these RC bugs:
1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
expected NoMethodError with "Expected \"not a hash, really\" to respond to
#to_hash", got
ruby-virtus 1.0.5-3 is marked for autoremoval from testing on 2022-04-04
It (build-)depends on packages with these RC bugs:
1006026: ruby-axiom-types: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError:
Cannot proxy frozen objects, rspec-mocks relies on proxies for method stubbing
and
ruby-virtus 1.0.5-3 is marked for autoremoval from testing on 2022-04-04
It (build-)depends on packages with these RC bugs:
1006026: ruby-axiom-types: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError:
Cannot proxy frozen objects, rspec-mocks relies on proxies for method stubbing
and
ruby-virtus 1.0.5-3 is marked for autoremoval from testing on 2021-12-21
It (build-)depends on packages with these RC bugs:
996297: ruby-ice-nine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error: expect(subject.end).to be_frozen
https://bugs.debian.org/996297
This mail
ruby-virtus 1.0.5-3 is marked for autoremoval from testing on 2021-11-24
It (build-)depends on packages with these RC bugs:
996140: ruby-bogus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: #
ArgumentError:
https://bugs.debian.org/996140
996297: ruby-ice-nine: FTBFS with ruby3.0:
ruby-virtus 1.0.5-3 is marked for autoremoval from testing on 2021-11-24
It (build-)depends on packages with these RC bugs:
996129: ruby-axiom-types: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
RuntimeError:
https://bugs.debian.org/996129
996140: ruby-bogus: FTBFS with ruby3.0: