Description of problem: PCPIntro(1) says: -a archive[,archive,...] An alternate form of -a for applications that are able to handle multiple archives. This indeed works just fine with e.g. pmval(1). However, when passing an archive list to any Python client over Python PMAPI: No such file or directory ['/tmp/20150910.10.41,/tmp/20150911.13.14'] Traceback (most recent call last): File "/tmp/test.py", line 125, in <module> T.connect() File "/tmp/test.py", line 114, in connect self.context = pmapi.pmContext.fromOptions(self.opts, sys.argv) File "/usr/lib64/python2.7/site-packages/pcp/pmapi.py", line 1085, in fromOptions context = builder(typed, source) File "/usr/lib64/python2.7/site-packages/pcp/pmapi.py", line 1044, in __init__ raise pmErr(self._ctx, [target]) pmErr: No such file or directory ['/tmp/20150813.10.41,/tmp/20150911.23.14'] pmSetLongOptionArchiveList() and pmSetLongOptionHostList() experience similar issue as well. Version-Release number of selected component (if applicable): python-pcp-3.10.6
This issue is very closely related to https://bugzilla.redhat.com/show_bug.cgi?id=1270176
Marko, can you pull from upstream to pick up the latest multi-archive changes and retest?
Hi Dave, I retested latest upstream with pmrep(1) and it works now all, both of these: $ pmrep -a arch1,arch2 mem.util.free $ pmrep -a . mem.util.free Extended header information looks also good (shows what was passed for -a). I see that pmrep(1) and many other man pages still refer the archive part of "-a archive" as a single file, will you be updating the man pages in one go later? Thanks.
Yes -- man page updates are forthcoming.
pcp-3.11.1-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-90112fb9ca
pcp-3.11.1-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e687eabad0
pcp-3.11.1-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-4969de37e5
pcp-3.11.1-1.el5 has been submitted as an update to Fedora EPEL 5. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5b519318e0
pcp-3.11.1-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-90112fb9ca
pcp-3.11.1-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5b519318e0
pcp-3.11.1-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-4969de37e5
pcp-3.11.1-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e687eabad0
pcp-3.11.1-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.1-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.1-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.1-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.