Neither the yellow indicator "absence of d/watch", nor "missing watchfile standard" is a reason to worry here.
The checks on the mentors page are not yet updated to the current Debian Policy (which would be 4.7.4.1, released on 2026-03-31). While not a new observation (I think there already was a request to close this gap however did not retain the bug number) your adoption of `Version: 5` instead of `version=4` is not a hinderance for an eventual upload to `testing`. While preparing an update of `ruby-mdl`, I equally noticed this a couple of days ago, too. On the other hand, there is a green check mark next to the abbreviated commit hash on https://salsa.debian.org/debian/luit. Thus, the repository uses some quality control _including_ a probe of `d/watch` called `test-uscan`. I wonder how this was launched in your case - because https://salsa.debian.org/ruby-team/ruby-mdl/ includes an auxilliary file `d/salsa-ci.yml` to ease such a CI. Here, it seems absent. If the auxilliary file is to be used, it is activated on salsa via Settings -> CI/CD -> General pipelines by addition of the full address of the configuration (i.e., `debian/salsa-ci.yml`). A sponsor may see this and the logs. Side note: Inspired by other Ruby relevant packages, I use a badge `Pipeline passed` as additional opt-in. On GitLab, this is activated via Settings -> General -> Badges, in a pattern of - Name: `Pipeline status` - Link: in pattern of `https://salsa.debian.org/<namespace>/<project>`, for instance https://salsa.debian.org/nbehrnd/ruby-mdl - Badge image URL: in the pattern of `https://salsa.debian.org/<namespace>/<project>/badges/debian/<branch>/pipeline.svg`, for instance https://salsa.debian.org/nbehrnd/ruby-uri/badges/debian/latest/pipeline.svg The badge is gray if there is no CI to refer to, and probably red if any individual check defined by the CI pipeline failed. When `ruby-mdl` became a team maintained package, the previously used namespace `nbehrnd` was substituted by `ruby-team`. Best regards, Norwid Behrnd
