[aur-general] Fwd: FS#60333: namcap exits 0 when errors found (Task closed)

Doug Newgard scimmia at archlinux.org
Mon Oct 8 06:35:17 UTC 2018

On Mon, 8 Oct 2018 13:23:03 +0700
Tom Hale <tom at hale.ee> wrote:

> I noticed that even when namcap prints out errors, it still exits 0.
> I raised this at:
> https://bugs.archlinux.org/task/60333
> It was closed:
> Reason for closing: Not a bug
> Additional comments about closing: namcap runs fine, so exiting with an 
> error makes no sense
> To me the "reason for closing" is like saying that diff should exit 0 
> when two files are different because diff ran fine.
> If namcap is to be used in any automated packaging tools (or even my 
> dodgy script), then it makes sense to have meaningful exit codes. And 
> possibly an option to also have warnings also exit non-0 for the 
> persnickety amongst us.
> I note that the python source returns 0 and 2, but never 1.
> I'm a newbie here, but I believe my argument has merit, so I raise it 
> here for possible discussion.

namcap's output is informational, nothing more. Taking it as gospel or using it
as any kind of automated checking instead of actually reading the output is not

More information about the aur-general mailing list