#2341 CLI copr monitor: The --dirname option does nothing
Closed: MIGRATED 2 years ago by nikromen. Opened 2 years ago by churchyard.

In https://copr.fedorainfracloud.org/coprs/g/python/python-without-distutils/builds/ I have most of the builds in a custom directory.

When I run copr monitor without --dirname, I only get the one build that was done in the default directory:

$ copr monitor @python/python-without-distutils --output-format text-row --fields name,state 
python3.11  succeeded

According to the --help message, I should be able to pass --dirname to see results from a different directory:

$ copr monitor --help
usage: copr monitor [-h] [--dirname DIRNAME] [--output-format {text,json,text-row}] [--fields FIELDS] project
...
  --dirname DIRNAME     project (sub)directory name, e.g. 'foo:pr:125', by default just 'foo' is used
...

Unfortunately, it does not work:

$ copr monitor @python/python-without-distutils --dirname python-without-distutils:custom:isolated --output-format text-row --fields name,state 
python3.11  succeeded

No matter what I try:

$ copr monitor @python/python-without-distutils --dirname custom:isolated --output-format text-row --fields name,state 
python3.11  succeeded

Even nonexistent directory still only shows that one build form the default one:

$ copr monitor @python/python-without-distutils --dirname xxx --output-format text-row --fields name,state 
python3.11  succeeded

Am I doing it wrong, or is it broken?


copr-distgit-client-0.61-1.fc35.x86_64
copr-cli-1.103-1.fc35.noarch
python3-copr-1.123-1.fc35.noarch

Thank you for the report. This seems broken, indeed.

Metadata Update from @praiskup:
- Issue tagged with: bug

2 years ago

Metadata Update from @nikromen:
- Issue close_status updated to: MIGRATED
- Issue status updated to: Closed (was: Open)

2 years ago

Log in to comment on this ticket.

Metadata