[DRE-maint] Bug#996238: ruby-hamster FTBFS caused by ruby-rbtree and ruby-sorted-set

[Daniel Leidert]

Source: ruby-sorted-set
Version: 1.0.3-2
Severity: serious
User: debian-ruby at lists.debian.org
Usertags: ruby3.0
Tags: help


After doing some debugging on the ruby-hamster FTBFS, the problem seems to be
ruby-btree and ruby-sorted-set breaking the tests. In a pure Ruby 2.7
environment, this is true:

SortedSet.new([1,3,2]).eql?(SortedSet.new([1,2,3])) => true

Installing ruby-rbtree, and the same matcher becomes false:

SortedSet.new([1,3,2]).eql?(SortedSet.new([1,2,3])) => false

Now adding ruby-sorted-set in the mix for the Ruby3.0 transition, which depends
on ruby-rbtree, more tests fail. This is causing ruby-hamster's tests to fail.

This bug report is to indicate that this blocks the ruby-hamster fix.

Regards, Daniel
-- 
Regards,
Daniel Leidert <dleidert at debian.org> | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20211128/7c6274f6/attachment-0001.sig>