Bug 195269 – Yumex fails to run after recent yum upgrade

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 195269 - Yumex fails to run after recent yum upgrade

Summary:	Yumex fails to run after recent yum upgrade

Status:	CLOSED DUPLICATE of bug 195770

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	yumex (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Tim Lauridsen
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2006-06-14 13:10 EDT by Kevin DeKorte
Modified:	2007-11-30 17:11 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-06-18 03:33:25 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Kevin DeKorte 2006-06-14 13:10:54 EDT

Description of problem:


Version-Release number of selected component (if applicable):

yumex-1.0.1-1.0.fc6

How reproducible:

100%

Steps to Reproduce:
1. Upgrade to rawhide as of 6/14/2006
2. Install yumex
3. Run yumex
  
Actual results:

yumex
Traceback (most recent call last):
  File "/usr/share/yumex/yumexmain.py", line 36, in ?
    from yumex.yum24XBase import *
  File "/usr/lib/python2.4/site-packages/yumex/yum24XBase.py", line 26, in ?
    from repomd import mdUtils, mdErrors
ImportError: No module named repomd


Expected results:

Yumex GUI should appear

Additional info:

Worked fine prior to yum-2.9.0-4 being installed

Comment 1 Tim Lauridsen 2006-06-18 03:33:25 EDT


*** This bug has been marked as a duplicate of 195770 ***

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