Bug 807899 - [abrt] yum-3.4.3-7.fc16: cli.py:177:_parseSetOpts:ValueError: need more than 1 value to unpack
[abrt] yum-3.4.3-7.fc16: cli.py:177:_parseSetOpts:ValueError: need more than ...
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Fedora Packaging Toolset Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-03-29 01:22 EDT by Mukundan Ragavan
Modified: 2014-01-21 18:21 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 15:49:31 EST
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 Mukundan Ragavan 2012-03-29 01:22:23 EDT
libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:        /usr/bin/python /usr/bin/yum -d 0 -C list updates --setopt=prote*
executable:     /usr/bin/yum
kernel:         3.3.0-4.fc16.x86_64
reason:         cli.py:177:_parseSetOpts:ValueError: need more than 1 value to unpack
time:           Thu 29 Mar 2012 12:21:52 AM CDT
uid:            1000
username:       mukundan

:cli.py:177:_parseSetOpts:ValueError: need more than 1 value to unpack
:Traceback (most recent call last):
:  File "/usr/bin/yum", line 29, in <module>
:    yummain.user_main(sys.argv[1:], exit_code=True)
:  File "/usr/share/yum-cli/yummain.py", line 309, in user_main
:    errcode = main(args)
:  File "/usr/share/yum-cli/yummain.py", line 98, in main
:    base.getOptionsConfig(args)
:  File "/usr/share/yum-cli/cli.py", line 213, in getOptionsConfig
:    self._parseSetOpts(opts.setopts)
:  File "/usr/share/yum-cli/cli.py", line 177, in _parseSetOpts
:    k,v = item.split('=')
:ValueError: need more than 1 value to unpack
:Local variables in innermost frame:
:item: 'prote*'
:self: <cli.YumBaseCli object at 0x1b81c50>
:setopts: ['prote*']
:repoopts: {}
:mainopts: <yum.misc.GenericHolder instance at 0x1b8f5f0>
Comment 1 Zdeněk Pavlas 2012-03-29 03:22:34 EDT
Has been fixed by ce610cac3b0afcab326cf23ebe293f530489f413
Comment 2 Fedora Admin XMLRPC Client 2012-04-27 11:27:32 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Fedora End Of Life 2013-01-16 11:48:24 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
Comment 4 Fedora End Of Life 2013-02-13 15:49:35 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.