public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/pkgcore/pkgcheck:master commit in: src/pkgcheck/scripts/
Date: Thu, 29 Jun 2023 15:41:05 +0000 (UTC)	[thread overview]
Message-ID: <1688053088.5f1dc5c1d7e2c26cb7ce3353782d472e65a287c3.arthurzam@gentoo> (raw)

commit:     5f1dc5c1d7e2c26cb7ce3353782d472e65a287c3
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 29 15:38:08 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Thu Jun 29 15:38:08 2023 +0000
URL:        https://gitweb.gentoo.org/proj/pkgcore/pkgcheck.git/commit/?id=5f1dc5c1

scan: fix unknown exit checkset during initial config load

Similar to previous fix, `--exit`` also can accept checksets which come
from args, so we also need to "escape" failures of ExitArgs.

Follows: a2358d60680611d7cbe07068440031c3c6e68f31
Resolves: https://github.com/pkgcore/pkgcheck/issues/594
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 src/pkgcheck/scripts/pkgcheck_scan.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/pkgcheck/scripts/pkgcheck_scan.py b/src/pkgcheck/scripts/pkgcheck_scan.py
index b83f569f..c04ff329 100644
--- a/src/pkgcheck/scripts/pkgcheck_scan.py
+++ b/src/pkgcheck/scripts/pkgcheck_scan.py
@@ -371,7 +371,9 @@ def _setup_scan(parser, namespace, args):
     # have to be parsed twice, will probably require a custom snakeoil
     # arghparse method.
     # parse command line args to override config defaults
-    with patch("pkgcheck.scripts.argparse_actions.ChecksetArgs.__call__", lambda *a, **k: None):
+    with patch(
+        "pkgcheck.scripts.argparse_actions.ChecksetArgs.__call__", lambda *a, **k: None
+    ), patch("pkgcheck.scripts.argparse_actions.ExitArgs.__call__", lambda *a, **k: None):
         namespace, _ = parser._parse_known_args(args, namespace)
 
     # Get the current working directory for repo detection and restriction


             reply	other threads:[~2023-06-29 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 15:41 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-04 19:20 [gentoo-commits] proj/pkgcore/pkgcheck:master commit in: src/pkgcheck/scripts/ Michał Górny
2023-05-11 18:08 Arthur Zamarin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1688053088.5f1dc5c1d7e2c26cb7ce3353782d472e65a287c3.arthurzam@gentoo \
    --to=arthurzam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox