On Mon, 29 Dec 2025 13:39:13 +0200 =?utf-8?q?Martin-=C3=89ric_Racine?= <[email protected]> wrote:
Package: lintian
Version: 2.127.0
Severity: normal
X-Debbugs-Cc: [email protected]

In its current form, bin:dhcpcd-base ships script fragments at this path:

/usr/lib/dhcpcd/dhcpcd-run-hooks
/usr/lib/dhcpcd/dhcpcd-hooks/01-test
/usr/lib/dhcpcd/dhcpcd-hooks/20-resolv.conf
/usr/lib/dhcpcd/dhcpcd-hooks/30-hostname
/usr/lib/dhcpcd/dhcpcd-hooks/50-timesyncd.conf

The file dhcpcd-run-hooks is executable and it sources the content of 
/usr/lib/dhcpcd/dhcpcd-hooks.

Bug #1103429 suggests moving these to /usr/libexec. This would produce the 
following Lintian output:

W: dhcpcd-base: executable-not-elf-or-script [usr/libexec/dhcpcd-hooks/01-test]
W: dhcpcd-base: executable-not-elf-or-script 
[usr/libexec/dhcpcd-hooks/20-resolv.conf]
W: dhcpcd-base: executable-not-elf-or-script 
[usr/libexec/dhcpcd-hooks/30-hostname]
W: dhcpcd-base: executable-not-elf-or-script 
[usr/libexec/dhcpcd-hooks/50-timesyncd.conf]

IMHO, Lintian should only check whether files at the root of /usr/libexec are 
executable. If a package ships any subdirectory, the check should be skipped 
for these files.

Hello,

I have no strong opinions on moving those files to /usr/libexec or not :)

As for the Lintian issue, it feels like what you propose would be too broad of a fix?

This tag seems to exist to prevent people from adding files they shouldn't to /usr/libexec (i.e. non-executables) and ignoring all the files not in the root of /usr/libexec would kind of defeat that purpose.

In this particular case, if you decide to move the files, I would suggest you add Lintian overrides.

Cheers,

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   [email protected] / veronneau.org
  ⠈⠳⣄

Reply via email to