pkgcheck scan of non-existence target doesn't raise errors #721

Activity

1. gentoo-bot

   closed this as completedin 2d91176on Dec 15, 2025
2. ferringb

   reopened this on Dec 15, 2025
3. ferringb commented on Dec 15, 2025

   

   ferringb

   on Dec 15, 2025

   Last edited by ferringb

   Contributor

   More actions

   Re-opening since I think there is something to change here.

   pkgcheck --debug --verbose scan some-random-string

   You're running a scan against any package that matches the pattern; no packages, no scans. I updated the --help to be clearer on this.

   Admittedly it may be surprising if you tell it "scan these non-existant atoms" and it doesn't scan anything. It's doing what was asked.

   @mgorny, @thesamesam what's your thoughts on tweaking pkgcheck scan to give a unique non zero exit code if nothing could possibly be scanned?

   👍React with 👍1Reacted by Alexander Kurakin
4. radhermit commented on Dec 15, 2025

   

   radhermit

   on Dec 15, 2025

   Last edited by radhermit

   Contributor

   More actions

   @mgorny, @thesamesam what's your thoughts on tweaking pkgcheck scan to give a unique non zero exit code if nothing could possibly be scanned?

   If you want to match pkgcruft (or use it for inspiration):

   $ pkgcruft scan nonexistent/pkg
   pkgcruft scan: error: no match: nonexistent/pkg
   $ echo $?
   2

   Note that the error is actually handled generically in the shared CLI support so it's consistent across all tools if they parse arguments using the same underlying functionality.

   👍React with 👍1Reacted by Alexander Kurakin
5. martin-kokos

   added a commit that references this issue on Jan 5, 2026

   clarify pkgcheck scan <targets> in it's --help

   ...

   This issue will close once commit 2d91176 is merged into the 'master' branch.

   2d91176