Hide Forgot
Description of problem: simply executed: bodhi --testable Version-Release number of selected component: bodhi-client-0.9.12.2-4.fc24 Additional info: reporter: libreport-2.7.2 cmdline: /usr/bin/python2 -tt /usr/bin/bodhi --testable executable: /usr/bin/bodhi kernel: 4.7.2-201.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: Python uid: 1000 Truncated backtrace: compat.py:125:get:NoOptionError: No option 'ca' in section: 'koji' Traceback (most recent call last): File "/usr/bin/bodhi", line 537, in <module> main() File "/usr/bin/bodhi", line 356, in main for update in bodhi.testable(): File "/usr/lib/python2.7/site-packages/fedora/client/bodhi.py", line 385, in testable login=False).listTagged(tag, latest=True) File "/usr/lib/python2.7/site-packages/fedora/client/bodhi.py", line 504, in get_koji_session ca = os.path.expanduser(config.get('koji', 'ca')) File "/usr/lib/python2.7/site-packages/iniparse/compat.py", line 222, in get value = RawConfigParser.get(self, section, option, vars) File "/usr/lib/python2.7/site-packages/iniparse/compat.py", line 125, in get raise NoOptionError(option, section) NoOptionError: No option 'ca' in section: 'koji' Local variables in innermost frame: section: 'koji' sec: <iniparse.ini.INISection object at 0x7f81dbb19a10> option: 'ca' vars: None self: <iniparse.compat.ConfigParser object at 0x7f81dbb19790>
Created attachment 1199234 [details] File: backtrace
Created attachment 1199235 [details] File: dso_list
Created attachment 1199236 [details] File: environ
Thanks for the bug report! I expect that this issue will not occur in the upcoming Bodhi 2.2.0 release. However, we are not currently planning to release 2.2.0 to Fedora 24 since it has already branched, and Bodhi 2 is not backwards compatible. Therefore, I will keep this bug open against Fedora 24 in case I can find the time to fix the 0.9 client for Fedora 23-25.
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 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.