On Wed, Jul 15, 2026 at 06:58:50AM +0000, Norwid Behrnd wrote: > 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
debian/.debhelper/ is created by debhelper during package build, and this happens with every package using debhelper (almost all packages in Debian), not only Ruby packages. As with any other content generated during the build, this directory should not be committed into version control, and it is removed when you clean the source package (basically at the start of any new build).
signature.asc
Description: PGP signature
