Bug 725299

Summary: Strange extension library spec
Product: [Fedora] Fedora Reporter: Alec Leamas <leamas.alec>
Component: nautilus-pythonAssignee: Patrick Dignan <dignan.patrick>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: dignan.patrick, mads
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-11 19:50:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Alec Leamas 2011-07-25 02:45:27 UTC
Description of problem:

Packaging a nautilus-python extension will either produce serious rpmlint warnings or break on some platforms.

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

How reproducible: always

Steps to Reproduce:
1. Write a nautilus-python extension
2. Try to package it using the same extension library as
   nautilus-python i. e.,  %{_libdir}/nautilus/extensions-2.0/python/
3. Watch rpmlint warnings about noarch extension referring to %{_libdir}
4. Realize that not using %{_libdir} will break extension on some platforms
  
Actual results: see above

Expected results: rpmlint should be silent, extension should work on all architectures.

Additional info:

IMHO, the extension path should be hardcoded to /usr/lib/nautilus/extensions-2.0/python

Comment 1 Mads Kiilerich 2011-08-11 19:50:05 UTC

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