Bug 541063

Summary:	nautilus-python needs python-devel package
Product:	[Fedora] Fedora	Reporter:	Luit van Drongelen <luitvd>
Component:	nautilus-python	Assignee:	Orphan Owner <extras-orphan>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12	CC:	a.badger, extras-orphan
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	466841	Environment:
Last Closed:	2010-01-27 20:28:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Luit van Drongelen 2009-11-24 21:18:54 UTC

Description of problem:
When I installed nautilus-python as a dependency of tortoisehg-nautilus and restarted nautilus it started throwing all sorts of python errors (not being able to find symbols in libraries). Removing the tortoisehg plugin from my ~/.nautilus/python-extensions directory revealed the culprit: /usr/lib/libpython2.6.so could not be found. 

Steps to Reproduce:
1. Select nautilus-python package in gpk-application and let it install
2. Restart nautilus and look in ~/.xsession-errors
3. Select python-devel package in gpk-application and let it install
4. Watch as restarting nautilus won't throw these errors anymore

Fix:
My guess is that nautilus-python should depend on the python-devel package

Comment 1 Toshio Ernie Kuratomi 2010-01-27 17:16:41 UTC

Note: This is supposed to be fixed with the 0.6.1 release (released on the 19th of January).

trondd, are you still around?  It would be great if you are or we can orphan this package and let someone else work on it if you have no time anymore.

Comment 2 Toshio Ernie Kuratomi 2010-01-27 20:28:04 UTC

This bug has been fixed upstream as part of the work on bz #474428  However nautilus-python is currently an orphaned package and we need a new maintainer to step in and perform the updates that pull in those fixes.

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