Hide Forgot
Description of problem: When I try to create buildroot override, it tracebacks on me. Version-Release number of selected component (if applicable): bodhi-client-0.9.12.2-3.fc23.noarch How reproducible: Easy Steps to Reproduce: 1. $ bodhi -o opencsg-1.4.1-1.fc25 2. Notes: For rebuilding OpenSCAD Actual results: $ bodhi -o opencsg-1.4.1-1.fc25 No handlers could be found for logger "fedora.client.bodhi" Notes: For rebuilding OpenSCAD Traceback (most recent call last): File "/usr/bin/bodhi", line 537, in <module> main() File "/usr/bin/bodhi", line 433, in main }, auth=True) File "/usr/lib/python2.7/site-packages/fedora/client/openidbaseclient.py", line 240, in send_request output = func(method, **kwargs) File "/usr/lib/python2.7/site-packages/fedora/client/openidbaseclient.py", line 78, in _decorator output = func(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/fedora/client/openidbaseclient.py", line 195, in _authed_post response = self._session.post(url, params=params, data=data, **kwargs) File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 518, in post return self.request('POST', url, data=data, json=json, **kwargs) TypeError: request() got an unexpected keyword argument 'req_params' Expected results: $ bodhi -o opencsg-1.4.1-1.fc25 Notes: For rebuilding OpenSCAD Override created (or similar message)
Hello! I have recently become the primary caretaker of Bodhi and I've inherited a number of issues related to bodhi 0.9. I wanted to be forthcoming with you that it will be difficult for me to fix issues with bodhi 0.9 while also pressing forward with bodhi 2, especially since I do not have any familiarity with the bodhi 0.9 codebase. I'm happy to keep this bug open to track the problem, but I would also encourage you to please test the bodhi 2 client (currently available in Rawhide and Copr[0]). Unfortunately, the bodhi 2 client is not backwards compatible with bodhi 0.9, so at this time I only plan for bodhi 2 to be released with Fedora 26 and EPEL 7 (with special permission from the EPEL SC). Here are some options you could pursue for this issue: 0) Write a patch for me that can be applied with the spec file. If you are willing to take the time to learn the bodhi 0.9 code, write a patch, and test it, I am willing to accept patches to be applied during build. 1) Use Rawhide. 2) Install bodhi 2 from my Copr[0]. I apologize as I understand that this is probably disappointing news for you to hear, but I thought it would be better to be forthcoming than to let the bug languish. I appreciate your understanding! [0] https://copr.fedorainfracloud.org/coprs/bowlofeggs/bodhi/
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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.