From 243fb92273de1c8bf5c938a62cb06bd198c97c4c Mon Sep 17 00:00:00 2001 From: Eli Schwartz Date: Thu, 20 Jul 2017 17:51:43 -0400 Subject: Fix setting keywords in the SSH interface This was broken in commit 8914a41db938194efc021f842c89d47ff6b522c9 which refactored the argument parsing. Instead of checking for at least the set-keywords command and a pkgbase name, we were checking for *exactly* the command and pkgbase name, leaving no room for keywords... As a result, while we could clear the keywords, we could not set them. Signed-off-by: Eli Schwartz Signed-off-by: Lukas Fleischer --- aurweb/git/serve.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'aurweb/git') diff --git a/aurweb/git/serve.py b/aurweb/git/serve.py index 3eef26a7..eea0c9c5 100755 --- a/aurweb/git/serve.py +++ b/aurweb/git/serve.py @@ -502,7 +502,7 @@ def serve(action, cmdargv, user, privileged, remote_addr): cmd = action + " '" + repo_path + "'" os.execl(git_shell_cmd, git_shell_cmd, '-c', cmd) elif action == 'set-keywords': - checkarg(cmdargv, 'repository name') + checkarg_atleast(cmdargv, 'repository name') pkgbase_set_keywords(cmdargv[1], cmdargv[2:]) elif action == 'list-repos': checkarg(cmdargv) -- cgit v1.2.3-24-g4f1b