Dear list I'm not sure if the following observation merits either filing a bug to `gem2deb`, or to the documentation about how to package from scratch with gem2deb (either [1], or [2], or both).
Recently,[3] using the CI ``` salsa-ci.yml --- include: - https://salsa.debian.org/ruby-team/meta/raw/master/salsa-ci.yml ``` I faced difficulties to pass the remote check with lintian. This was resolved by removal of the directory of `d./debhelper/` I had in the project for a couple of years (without using the CI). For testing purposes, I locally build `ruby-mdl` from scratch, and `gem2deb` (version 2.2.8) creates (again) this directory, i.e. this would face the same issue again and the quality check run on salsa.debian.org would fail anew. Which of the two options were preferable, - edit of the wikipages to inform «prior to upload to salsa, if using the CI remove this directory», or - filing a bug to `gem2deb` to eventually write a project without this directory Maybe there is a third approach I did not recognize yet, too. Best regards, Norwid [1] https://wiki.debian.org/Teams/Ruby/Packaging#Packaging_new_gems_from_scratch [2] https://wiki.debian.org/Teams/Ruby/Packaging/gem2deb [3] https://lists.debian.org/debian-ruby/2026/07/msg00003.html
