particle-os/debian-koji
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

more grammar changes

Browse source
This commit is contained in:
Mike McLean 2020-04-01 17:03:53 -04:00 • committed by Tomas Kopecek
parent 21b461ec25
commit 067d30080e
2 changed files with 12 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

12
cli/koji_cli/commands.py
View file

@ -463,7 +463,7 @@ def handle_build(options, session, args):
tag (where the build eventually lands) or build tag (where the buildroot
contents are pulled from).
You can list all available build targets using the 'koji list-targets' command.
You can list all available build targets using the '%prog list-targets' command.
More detail can be found in the documentation.
https://docs.pagure.org/koji/HOWTO/#package-organization""")
@ -2351,9 +2351,13 @@ def anon_handle_latest_build(goptions, session, args):
usage = _("""\
usage: %prog latest-build [options] <tag> <package> [<package> ...]
Note, that <tag> needn't be same as build target. If you've wanted to
see what was the latest build in given buildroot, check '%prog
list-targets --name=<target>' to find name of the buildroot's tag""")
The first option should be the name of a tag, not the name of a build target.
If you want to know the latest build in buildroots for a given build target,
then you should use the name of the build tag for that target. You can find
this value by running '%prog list-targets --name=<target>'
More information on tags and build targets can be found in the documentation.
https://docs.pagure.org/koji/HOWTO/#package-organization""")
usage = textwrap.dedent(usage)
parser = OptionParser(usage=get_usage_str(usage))

8
tests/test_cli/test_build.py
View file

@ -25,13 +25,13 @@ The first option is the build target, not to be confused with the destination
tag (where the build eventually lands) or build tag (where the buildroot
contents are pulled from).
You can list all available build targets using the 'koji list-targets' command.
You can list all available build targets using the '%s list-targets' command.
More detail can be found in the documentation.
https://docs.pagure.org/koji/HOWTO/#package-organization
(Specify the --help global option for a list of other help options)
%s: error: {message}
""" % (self.progname, self.progname)
""" % (self.progname, self.progname, self.progname)
@mock.patch('sys.stdout', new_callable=six.StringIO)
@mock.patch('koji_cli.commands.activate_session')
@ -204,7 +204,7 @@ The first option is the build target, not to be confused with the destination
tag (where the build eventually lands) or build tag (where the buildroot
contents are pulled from).
You can list all available build targets using the 'koji list-targets' command.
You can list all available build targets using the '%s list-targets' command.
More detail can be found in the documentation.
https://docs.pagure.org/koji/HOWTO/#package-organization
(Specify the --help global option for a list of other help options)
@ -227,7 +227,7 @@ Options:
--repo-id=REPO_ID Use a specific repo
--noprogress Do not display progress of the upload
--background Run the build at a lower priority
""" % progname
""" % (progname, progname)
expected_stderr = ''
self.assertMultiLineEqual(actual_stdout, expected_stdout)
self.assertMultiLineEqual(actual_stderr, expected_stderr)