la 27.9.2025 klo 12.43 Johannes Schauer Marin Rodrigues ([email protected]) kirjoitti: > > Quoting Martin-Éric Racine (2025-09-27 11:01:58) > > 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. > > I think it would've helped if you stated in your initial mail that your > problem is using lintian for packages outside of Debian.
You're missing the point. Those were just 2 examples. Here's another one straight from the archive: X: dhcpcd-base: executable-in-usr-lib [usr/lib/dhcpcd/dhcpcd-run-hooks] (this one probably should be a Warning, since there should be a compelling reason to disregard FHS paths) While I _could_ --configure /usr/libexec instead, I then run into another problem: debian/dhcpcd-base/usr/libexec/ ├── dhcpcd-hooks │ ├── 01-test │ ├── 20-resolv.conf │ ├── 30-hostname │ └── 50-timesyncd.conf └── dhcpcd-run-hooks This results in dhcpcd-run-hooks passing the Lintian test, but Lintian then complains about the script fragments in dhcpcd-hooks missing a shebang they don't really need since they are merely getting sourced by dhcpcd-run-hooks. While I could quiet this second one down with a Lintian override, a smarter approach would be for Lintian to ignore anything within a libexec subdirectory. Martin-Éric
