Red Hat Bugzilla – Bug 487764
.desktop menu entry has wrong/missing categories
Last modified: 2009-07-16 03:10:39 EDT
Description of problem:
the desktop entry generated has obsolete and missing categorys. patch to the specfile attached to report.
wouldnt it be better to get those changes upstream too instead of using desktop-file-install to add the appropriate categorys?
Version-Release number of selected component (if applicable):
Created attachment 333525 [details]
patch against seamonkey.spec in cvs
patch against seamonkey.spec in cvs to fix menu categorisation
Upstream doesn't ship a desktop file. Probably better to just fix those outright. They should be available as Source files in the SRPM.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
I've started a build.
I'll submit it to fedora testing if it works right.
seamonkey-1.1.16-1.11.1.fc11 has been submitted as an update for Fedora 11.
Not sure if this deserves getting pushed to stable, but please give feedback whether it works right. It'll then get included on the next seamonkey update.
I mean, whether it deserves the hassle of a big update package for this minor fix.
seamonkey-1.1.16-1.11.1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update seamonkey'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-6694
seamonkey-1.1.17-1.fc10 has been submitted as an update for Fedora 10.
seamonkey-1.1.17-1.fc11 has been submitted as an update for Fedora 11.
seamonkey-1.1.17-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
seamonkey-1.1.17-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.