Bug 524730

Summary: djvulibre: use standard scriptlets (not homebrew/xdg-utils)
Product: [Fedora] Fedora Reporter: Rex Dieter <rdieter>
Component: djvulibreAssignee: Rakesh Pandit <rpandit>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: orion, pertusus, rdieter, rpandit
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 524724 Environment:
Last Closed: 2010-12-04 07:40:22 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:
Bug Depends On: 524724    
Bug Blocks:    

Description Rex Dieter 2009-09-21 23:07:02 UTC
+++ This bug was initially created as a clone of Bug #524724 +++

Description of problem:

Fresh rawhide install:

Installing djvulibre-3.5.21-3.fc12.x86_64
/usr/bin/xdg-desktop-menu: line 1145: kde-config: command not found
/usr/bin/xdg-desktop-menu: line 1146: kde-config: command not found

I think just a judicious 2>/dev/null is needed assuming kde-config is optional.  Or perhaps a conditional test for kde-config's existence.

Version-Release number of selected component (if applicable):
xdg-utils-1.0.2-11.20090913cvs.fc12.noarch

--- Additional comment from rdieter.edu on 2009-09-21 19:03:01 EDT ---

djvulibre probably shouldn't be using xdg-desktop-menu in scriptlets. 

There are better documented ways of doing this in the Packaging guidelines.

In the meantime, I'll fix the erroneous output. (normally, these tools are run in a user context, not a system/root one).

Comment 2 Rex Dieter 2009-09-22 00:06:03 UTC
For example, existing scriptlets result in unowned files, including (but not necessarily limited to):

rpm -q -f /usr/share/applications/djvulibre-djview3.desktop
file /usr/share/applications/djvulibre-djview3.desktop is not owned by any package

Comment 3 Bug Zapper 2009-11-16 12:44:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2010-11-04 09:53:17 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 WONTFIX if it remains open with a Fedora 
'version' of '12'.

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 prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2010-12-04 07:40:22 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.

Thank you for reporting this bug and we are sorry it could not be fixed.