Hello Michel Regarding `SugarJar`: by visit of https://tracker.debian.org/pkg/sugarjar and confirmed by inspection of `d/control` your data appear as `Maintainer:`, the Debian Ruby Team as uploader. Is this intentional? Since my move of `ruby-mdl` into the namespace of the team, I adopted the opposite pattern, i.e.
``` d/control Maintainer: Debian Ruby Team <[email protected]> Uploaders: Norwid Behrnd <[email protected]> ``` A brief check in team maintained packages hosted on salsa (for instance `ruby-thinking-sphinx`, `ruby-js-image-paths`) equally shows this pattern. --- A suggest you might want to opt-in: You already have a quality control beyond a minimum of ``` d/salsa-ci.yml --- include: - https://salsa.debian.org/ruby-team/meta/raw/master/salsa-ci.yml ``` I would recommend - to _activate_ its use. While accessing the salsa repository with a web browser, this is accessed via Settings -> CI/CD -> General pipelines. Here, add the complete path to the file, i.e. `debian/salsa-ci.yml` - to _report_ the results on the landing page of the repository. Go Settings -> General -> Badges, with + Name: `Pipeline status` + Link: `https://salsa.debian.org/<namespace>/<project_name>` + Pipeline Status: `https://salsa.debian.org/<namespace>/<project_name>/badges/debian/latest/pipeline.svg` The badge offers three levels: + gray: (so far) there is no run of the CI defined by `d/salsa-ci.yml` to refer to. If correctly set up, this changes with the next commit and push to salsa. It equally can be launched by an empty commit, for instance ``` bash git commit --allow-empty -m "launch the CI" ``` + red / failed if the CI identified an issue + green /passed if the CI passed Either level `red` or `green`, Build -> Pipelines allows to inspect the runs of the CI in further detail (logs of `build source`, `lintian`, etc.). Based on own experience, it would have been better if I first had moved the repository of `ruby-mdl` into the new namespace `ruby-team`, and then adjusted `d/control`. If there already is a CI badge, moving the repository into the namespace `ruby-team` may yield an additional group badge `Salsa CI`; at this stage, it is safe to remove the private badge previously installed which was based on your private namespace. Running CI based on `d/salsa-ci.yml`, deployment of a pipeline badge, launch of the empty commit equally works well in a private repository on salsa (to test/get familiar and train), too. Best regards, Norwid Behrnd
