Arch Linux

Please read this before reporting a bug:

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!

FS#67288 - [namcap] Shouldn't report missing dependencies covered by base

Attached to Project: Arch Linux
Opened by PilzAdam (PilzAdam) - Wednesday, 15 July 2020, 16:26 GMT
Last edited by freswa (frederik) - Wednesday, 15 July 2020, 19:40 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Rémy Oudompheng (remyoudompheng)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


namcap shouldn't report missing dependencies on packages that are required by the `base` package. It can be assumed that every user has the `base` package, and thus all its dependencies, already installed.

Additional info:
* namcap 3.2.10-1

Steps to reproduce:
* build a package with a Bash script (including shebang) without `bash` dependency (e.g.
* run namcap on the created package

Actual behavior:
* namcap reports: "E: Dependency bash detected and not included (programs ['bash'] needed in scripts ['usr/bin/...'])"

Expected behavior:
* namcap detects that `bash` is required by `base` and thus reports no error
This task depends upon

Comment by PilzAdam (PilzAdam) - Wednesday, 15 July 2020, 17:30 GMT
I found a 10-year-old discussion on this issue in  FS#18900 . The decision back then was "wont-fix" with the following reason: "We're not clear about our policy. Re-open if it looks like we have a clear motivation for change."

The mentioned "clear motivation for change" would be the introduction of the `base` package over the old `base` package group. The news post about the `base` package [1] clearly says "Users requesting support are expected to be running a system with the `base` package" and calls it a "mandatory" package. Clearly everybody is expected to have the `base` package installed now. I think this is a good reason to reconsider this issue now.