Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#26536 - [namcap] static library permission check should be done on regular files only

Attached to Project: Arch Linux
Opened by Eric Belanger (Snowman) - Thursday, 20 October 2011, 09:11 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Thursday, 20 October 2011, 19:56 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Rémy Oudompheng (remyoudompheng)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When running namcap on bigloo, I get these warnings:

bigloo W: Library (usr/lib/bigloo/3.7a/libbigloomultimedia_u-3.7a.a) does not have permission set to 644 or 444
bigloo W: Library (usr/lib/bigloo/3.7a/libbigloobdl_u-3.7a.a) does not have permission set to 644 or 444
bigloo W: Library (usr/lib/bigloo/3.7a/libbigloopkgcomp_u-3.7a.a) does not have permission set to 644 or 444
bigloo W: Library (usr/lib/bigloo/3.7a/libbigloopackrat_u-3.7a.a) does not have permission set to 644 or 444
bigloo W: Library (usr/lib/bigloo/3.7a/libbigloosqlite_u-3.7a.a) does not have permission set to 644 or 444
bigloo W: Library (usr/lib/bigloo/3.7a/libbigloossl_u-3.7a.a) does not have permission set to 644 or 444
bigloo W: Library (usr/lib/bigloo/3.7a/libbigloosrfi1_u-3.7a.a) does not have permission set to 644 or 444
bigloo W: Library (usr/lib/bigloo/3.7a/libbigloophone_u-3.7a.a) does not have permission set to 644 or 444
bigloo W: Library (usr/lib/bigloo/3.7a/libbigloopkglib_u-3.7a.a) does not have permission set to 644 or 444

All these files are symlinks to static libraries with the correct permissions. Instead of doing the permission check on all *.a files, we should only do it on regular files. This will eliminate false warning like these.
This task depends upon

Closed by  Rémy Oudompheng (remyoudompheng)
Thursday, 20 October 2011, 19:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed for namcap 3.2.1

Loading...