Description of problem: "pkgdb-client list --user ..." backtraces for me: Error: argument of type 'NoneType' is not iterable ERROR:root:Generic error catched: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/pkgdb2client/cli.py", line 1002, in main arg.func(arg) File "/usr/lib/python2.7/site-packages/pkgdb2client/cli.py", line 597, in do_list if '/' in args.pattern: TypeError: argument of type 'NoneType' is not iterable Version-Release number of selected component (if applicable): packagedb-cli-2.12-1.fc23 How reproducible: 100% Steps to Reproduce: 1. pkgdb-client list --user petersen Expected results: no backtrace
s/pkgdb-client/pkgdb-cli/
This has been fixed in git upstream and will be part of the next release (to happen soon): https://github.com/fedora-infra/packagedb-cli/pull/83
Okay - can we leave it open the until it is released this?
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Reclosing - assuming it was released by now.
I think your assumption is correct (and confirm that I can no longer reproduce the issue with the current version)