Bug 189034 - Unable to start gnochm
Summary: Unable to start gnochm
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnochm
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Patrice Dumas
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-14 23:10 UTC by Paul F. Johnson
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version: 0.9.7-5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-04-15 08:41:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Paul F. Johnson 2006-04-14 23:10:24 UTC
Description of problem:
This is probably something wrong in the spec file. When I attempt to start
gnochm, it reports back that it is missing a python module (gconf)

Version-Release number of selected component (if applicable):
0.9.7-4.fc6

How reproducible:
Always

Steps to Reproduce:
1. Install via yum
2. open terminal
3. type gnochm
  
Actual results:
Reports that Python module (gconf) is missing

Expected results:
On install, the missing module should be dragged in as dependancy

Additional info:

Comment 1 MW 2006-04-15 08:05:34 UTC
The same with on x86 hardware with FC5 release - ``gnochm-0.9.7-4.fc5''. There
is no check for gnome-python2-gconf during installation of gnochm via yum . This
package is vital to run gnochm. Other dependencies is resolved successfully (ie.
chmlib, etc). Simply package installs despite gnome-python2-gconf missing.
Resolution: add gnome-python2-gconf to Requires field in spec.

Comment 2 Patrice Dumas 2006-04-15 08:21:24 UTC
I am looking at it. Currently, I think I have found 
gnome-python2-gconf pygtk2-libglade gnome-python2-gtkhtml2
as Requires. But I am investigating a way to find more
systematically the package that provide a python module.

Comment 3 Patrice Dumas 2006-04-15 08:41:27 UTC
I haven't found more packages needed. This is fixed in 0.9.7-5
(building).


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