Bug 848097 - [abrt] bodhi-client-0.8.5-2.fc17: compat.py:146:getboolean:ValueError: Not a boolean: Fasle
[abrt] bodhi-client-0.8.5-2.fc17: compat.py:146:getboolean:ValueError: Not a ...
Product: Fedora
Classification: Fedora
Component: bodhi (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Luke Macken
Fedora Extras Quality Assurance
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2012-08-14 11:19 EDT by Vít Ondruch
Modified: 2016-09-19 22:43 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-01 13:44:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vít Ondruch 2012-08-14 11:19:13 EDT
libreport version: 2.0.10
abrt_version:   2.0.10
cmdline:        /usr/bin/python -tt /usr/bin/bodhi --new --release f17 --file bodhi.template rubygem-actionpack-3.0.11-7.fc17
comment:        Typo. Written Fasle in place of False
executable:     /usr/bin/bodhi
kernel:         3.4.6-2.fc17.x86_64
time:           Út 14. srpen 2012, 17:17:52 CEST
uid:            1000
username:       vondruch

:compat.py:146:getboolean:ValueError: Not a boolean: Fasle
:Traceback (most recent call last):
:  File "/usr/bin/bodhi", line 519, in <module>
:    main()
:  File "/usr/bin/bodhi", line 201, in main
:    updates = bodhi.parse_file(input_file=opts.input_file)
:  File "/usr/lib/python2.7/site-packages/fedora/client/bodhi.py", line 290, in parse_file
:    update['close_bugs'] = config.getboolean(section, 'close_bugs')
:  File "/usr/lib/python2.7/site-packages/iniparse/compat.py", line 146, in getboolean
:    raise ValueError, 'Not a boolean: %s' % v
:ValueError: Not a boolean: Fasle
:Local variables in innermost frame:
:self: <iniparse.compat.ConfigParser object at 0x2804e90>
:section: ' rubygem-actionpack-3.0.11-7.fc17 '
:option: 'close_bugs'
:v: 'Fasle'
Comment 1 Luke Macken 2012-11-13 15:00:45 EST
Looks like this is due to a typo. For the 'close_bugs' field you must put either 'True' or 'False', where as it seems that you put 'Fasle'.
Comment 2 Vít Ondruch 2012-11-14 03:01:26 EST
Yes, I am aware that it was typo, but no matter what I write there, it should not crash with exception and the problem should be user friendly reported.
Comment 3 Fedora End Of Life 2013-07-04 02:14:09 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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.
Comment 4 Fedora End Of Life 2013-08-01 13:44:51 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.