Bug 1119942 - [abrt] yum-utils: packageSack.py:494:returnPackages:KeyError: 'moka-icon-theme'
Summary: [abrt] yum-utils: packageSack.py:494:returnPackages:KeyError: 'moka-icon-theme'
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils
Version: 20
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:9c5f380df3cc21d5c9069413ee6...
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-15 22:24 UTC by Adrian J
Modified: 2015-06-29 21:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-29 21:36:18 UTC

Attachments (Terms of Use)
File: backtrace (790 bytes, text/plain)
2014-07-15 22:25 UTC, Adrian J
no flags Details
File: environ (3.15 KB, text/plain)
2014-07-15 22:25 UTC, Adrian J
no flags Details

Description Adrian J 2014-07-15 22:24:59 UTC
Version-Release number of selected component:

Additional info:
reporter:       libreport-2.2.2
cmdline:        /usr/bin/python -tt /bin/yum-debug-dump
dso_list:       yum-3.4.3-152.fc20.noarch
executable:     /bin/yum-debug-dump
kernel:         3.15.4-200.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            0

Truncated backtrace:
packageSack.py:494:returnPackages:KeyError: 'moka-icon-theme'

Traceback (most recent call last):
  File "/bin/yum-debug-dump", line 210, in <module>
  File "/bin/yum-debug-dump", line 206, in main
    fn = my.create_debug_file(fn=filename)
  File "/bin/yum-debug-dump", line 182, in create_debug_file
  File "/bin/yum-debug-dump", line 80, in dump_repos
    for po in sorted(self.pkgSack.returnPackages(repo.id)):
  File "/usr/lib/python2.7/site-packages/yum/packageSack.py", line 494, in returnPackages
    return self.sacks[repoid].returnPackages(patterns=patterns,
KeyError: 'moka-icon-theme'

Local variables in innermost frame:
patterns: None
ignore_case: False
repoid: 'moka-icon-theme'
self: <yum.packageSack.MetaSack object at 0x108ec50>

Comment 1 Adrian J 2014-07-15 22:25:03 UTC
Created attachment 918266 [details]
File: backtrace

Comment 2 Adrian J 2014-07-15 22:25:04 UTC
Created attachment 918267 [details]
File: environ

Comment 3 Fedora End Of Life 2015-05-29 12:22:53 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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.

Comment 4 Fedora End Of Life 2015-06-29 21:36:18 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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

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.