FS#59813 - [namcap] /opt/$pkgname is not considered valid location for ELF files
Attached to Project:
Arch Linux
Opened by Alexander Kobel (akobel) - Sunday, 26 August 2018, 12:16 GMT
Last edited by Jelle van der Waa (jelly) - Friday, 11 August 2023, 15:51 GMT
Opened by Alexander Kobel (akobel) - Sunday, 26 August 2018, 12:16 GMT
Last edited by Jelle van der Waa (jelly) - Friday, 11 August 2023, 15:51 GMT
|
Details
According to the Namcap wiki page, the rule
elffile-not-in-allowed-dirs should accept /opt/$pkgname/ as
a valid location for ELF files, in accordance with the Linux
Filesystem Hierarchy Standard. (From
https://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/opt.html: "Generally, all data required to support a package on a
system must be present within /opt/'package', including
files intended to be copied into /etc/opt/'package' and
/var/opt/'package' as well as reserved directories in
/opt.")
But currently namcap reports "ELF files outside of a valid path ('opt/')." and does not seem to check for the $pkgname subdirectory. Additional info: * package version(s): extra/namcap 3.2.8-2 (which reports itself as 3.2.7 with `namcap -v`?) Steps to reproduce: makepkg and namcap *.pkg.tar* for the attached trivial PKGBUILD (which just copies sed from /usr/bin to /opt/$pkgname/bin) |
This task depends upon
Closed by Jelle van der Waa (jelly)
Friday, 11 August 2023, 15:51 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/pacman/namc ap/issues/51
Friday, 11 August 2023, 15:51 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/pacman/namc ap/issues/51
Comment by
Buggy McBugFace (bugbot) - Tuesday,
08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2
years. Please reply if you still experience this bug otherwise
this issue will be closed after 1 month.