Thank you for a second opinion on this because I would prefer if `ruby-uri` were not necessary.
It is prompted by an earlier discussion upstream[1] and by the observation a pristine rebuild by ```bash gem2deb mdl ``` yields a d/control file with an entry for `ruby-uri` though there is not an explicit extra package outside Ruby's standard library. The two lead me to think an update of `ruby-mdl` now should include the tests present on GitHub, but not in the rubygem[2,3] to have strong evidence here. At present, d/control does not call for `ruby-uri`[4] which both locally and remotely on salsa is at best is "acceptable" because the test suite is not used. So far, my attempts to get the tests running failed - which one reason why I did not push the edits to the team maintained salsa repository of `ruby-mdl`. I'm aware the Debian Ruby Team compiled hints; so far, the website's examples escape me because I'm not yet used to Ruby's automated testing. Best regards, Norwid [1] https://github.com/markdownlint/markdownlint/issues/605 [2] https://rubygems.org/gems/mdl [3] https://github.com/markdownlint/markdownlint/blob/main/CHANGELOG.md#v080-2019-11-08 [4] https://salsa.debian.org/nbehrnd/ruby_mdl_test05a
