Pyinstaller ships two executables in /usr/lib/python3/dist-packages/. There is an experimental tag that suggests these should be moved to /usr/libexec/.
X: python3-pyinstaller: executable-in-usr-lib [usr/lib/python3/dist-packages/ PyInstaller/bootloader/Linux-64bit-intel/run] N: N: The package ships an executable file in /usr/lib. N: N: Please move the file to /usr/libexec. N: N: With policy revision 4.1.5, Debian adopted the Filesystem Hierarchy Specification (FHS) version 3.0. N: N: The FHS 3.0 describes /usr/libexec. Please use that location for executables. N: N: Please refer to File System Structure (Section 9.1.1) in the Debian Policy Manual, filesystem-hierarchy, https://refspecs.linuxfoundation.org/ FHS_3.0/fhs/ch04s07.html, and Bug#954149 for details. N: N: Visibility: pedantic N: Show-Always: no N: Check: files/permissions/usr-lib N: This tag is experimental. N: N: Screen: emacs/elpa/scripts N: Advocates: "David Bremner" <[email protected]> N: Reason: The emacsen-common package places installation and removal scripts, which for ELPA packages are executable, in the folder /usr/lib/ emacsen-common/packages. N: N: About four hundred installation packages are affected. All of them declare emacsen-common as an installation prerequisite. N: N: Read more in Bug#974175 and Bug#954149. N: N: Screen: web/cgi/scripts N: Advocates: "Andrius Merkys" <[email protected]> N: Reason: The folder /usr/lib/cgi-bin/ is designated for scripts in the Common Gateway Interface (CGI). They require the executable bit so the server can run them. N: N: Read more in https://en.wikipedia.org/wiki/ Common_Gateway_Interface, https://datatracker.ietf.org/doc/html/rfc3875.html, and Bug#1003941. N: N: X: python3-pyinstaller: executable-in-usr-lib [usr/lib/python3/dist-packages/ PyInstaller/bootloader/Linux-64bit-intel/run_d] I do not know how easy it would be to relocate these files. Before reaching out to the Pyinstaller upstream to see of what it would take to relocate these files, I wanted to ask the Debian Python Team how this is generally handled with Python packages. Are executables typically relocated to /usr/libexec/? If so, does this require much modification of the upstream code to locate them? Or is it generally considered wiser to just leave the executables in / usr/lib/ and ignore these lintian tags? -- Soren Stoutner [email protected]
signature.asc
Description: This is a digitally signed message part.
