Martin-Éric Racine, le dim. 28 sept. 2025 14:32:12 +0300, a ecrit: > > 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. > > > > N: > > E: package-installs-apt-preferences > > N: > > N: Debian packages should not install files under > > /etc/apt/preferences.d/ or install an /etc/apt/preferences file. This > > directory is under the control of the local administrator. > > N: > > N: Package should not override local administrator choices. > > N: > > N: Please refer to the apt_preferences(5) manual page for details. > > N: > > N: Visibility: error > > N: Show-Always: no > > N: Check: apt > > N: Renamed from: package-install-apt-preferences > > N: > > > > There is an obvious need to prefer customized versions over Debian > > versions for packages deployed across a whole company. > > While I can perfectly see why the Debian archive would not want to > introduce packages with a preferences file without any compelling > reason to do so, the above lintian-explain-tags output doesn't tell > what someone trying to build and deploy a company-wide custom package > needs to know to ensure that it will always be preferred to the stock > Debian package.
I don't understand the problem you are facing. Again, lintian is meant for packages meant for the archive. So it'll warn/error about issues for there. If you have a package not meant for the archive, you can just override the lintian warning/error and be done. Where is the remaining problem? Samuel
