I request help to identify and remove the cause for a failing lintian test when running the check remotely on salsa.debian.org; for a local build, the local call on `lintian` does not report an error.
Previously, `ruby-mdl`[1] used constrain the versions of its dependencies. I'm on the way to correct this and use the `salsa-ci.yml` used by the Debian Ruby Team maintained `ruby-mixlib-shellout`[2] successfully updated by Simon Quigley (passing pipeline) and admitted to Debian testing. Contrasting to my anticipation, the remote check with lintian on `ruby-mdl` failed, while a local run (v2.137.1) passed. As a third check, I uploaded the tentative version 0.17.0-2 to the mentors page.[3] Checks there did not report an error. I then compared file `debian/rules` of `ruby-mdl` with the one currently used by the successfully passing `ruby-mixlib-shellout`, however do not recognize a difference. In light of the recent discussion «Don't run Salsa CI in vain ...»,[4] I seek assistance to resolve the issue. My intent was (and still is) to eventually bring `ruby-mdl` under the umbrella of the Debian Ruby Team of which I'm not yet a member. Best regards, Norwid [1] https://tracker.debian.org/pkg/ruby-mdl [2] https://salsa.debian.org/ruby-team/ruby-mixlib-shellout [3] https://mentors.debian.net/package/ruby-mdl/#upload-1 [4] https://lists.debian.org/debian-devel/2026/06/msg00310.html
