Steps to reproduce Try to import dummy name package:
importRPM('.', non_exist_rpm)
Current output
Traceback (most recent call last): File "/home/mfilip/opt/virtualenv/mfilip-koji-biweekly/lib64/python3.7/site-packages/koji/__init__.py", line 2578, in _callMethod return self._sendCall(handler, headers, request) File "/home/mfilip/opt/virtualenv/mfilip-koji-biweekly/lib64/python3.7/site-packages/koji/__init__.py", line 2500, in _sendCall return self._sendOneCall(handler, headers, request) File "/home/mfilip/opt/virtualenv/mfilip-koji-biweekly/lib64/python3.7/site-packages/koji/__init__.py", line 2542, in _sendOneCall ret = self._read_xmlrpc_response(r) File "/home/mfilip/opt/virtualenv/mfilip-koji-biweekly/lib64/python3.7/site-packages/koji/__init__.py", line 2554, in _read_xmlrpc_response result = u.close() File "/usr/lib64/python3.7/xmlrpc/client.py", line 656, in close raise Fault(**self._stack[0]) xmlrpc.client.Fault: <Fault 1000: 'No such file: /mnt/brew/work/./package-pfxjy.rpm'> During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/mfilip/opt/brew-testing/src/kojitest/kojitest/api/test_signatures.py", line 150, in test_import_rpm_non_exist_rpm env.session.importRPM('.', non_exist_rpm) File "/home/mfilip/opt/virtualenv/mfilip-koji-biweekly/lib64/python3.7/site-packages/koji/__init__.py", line 2093, in __call__ return self.__func(self.__name, args, opts) File "/home/mfilip/opt/virtualenv/mfilip-koji-biweekly/lib64/python3.7/site-packages/koji/__init__.py", line 2597, in _callMethod raise err koji.GenericError: No such file: /mnt/brew/work/./package-pfxjy.rpm
Expected output Only koji.GenericError should be shown
Opened by mistake. This is expected behavior. Sorry
Metadata Update from @mfilip: - Custom field Size adjusted to None
Metadata Update from @mfilip: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/1647
Please continue any further discussion there.