Martin-Éric Racine:
la 27.9.2025 klo 11.48 Samuel Thibault (sthibault@debian.org) kirjoitti:[...]Agreed. In fairness, in that particular case, the error is explained by a requirement due to Apache code change. Here are two less obvious ones: [...] This is a fairly common case for commercial non-free commercial packages and for local packages deployed across a whole company. The package includes a sources.list.d file to enable fetching updates, and it definitely won't pull in a separate company-apt-source package just to quiet down Lintian. [...] There is an obvious need to prefer customized versions over Debian versions for packages deployed across a whole company. Martin-Éric
Hi Martin-Éric,Sounds like you may want to create a Lintian profile that better match the need of your use-case if it is for a package not targeting a Debian upload.
Lintian has support for creating arbitrary rule sets for which hints to be emitted and under what severity via its profile system. Then once you have a valid profile, it is a matter of running `lintian --profile <foo>` to use your defined rule set and get the policy you desire for your use-case, while Debian retains its default under the `debian/main` profile that is Lintian's current default.
Best regards, Niels
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature