Bug 204139

Summary: mozilla-rebuild-databases.pl script called in %post has incorrect path
Product: Red Hat Enterprise Linux 4 Reporter: wingc
Component: seamonkeyAssignee: Martin Stransky <stransky>
Status: CLOSED CURRENTRELEASE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: caillon, rdieter
Target Milestone: ---Keywords: EasyFix, Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: seamonkey-1.0.8-0.1.el4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-03-06 09:20:57 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:
Attachments:
Description Flags
[PATCH] seamonkey.spec: fix path name in mozilla-rebuild-databases.pl
none
proposed patch none

Description wingc 2006-08-25 20:17:12 UTC
Description of problem:

The 'mozilla-rebuild-databases.pl' script, which is called in %post for the
'seamonkey' RPM, has an incorrect path.

The script uses a path such as (on x86_64):

        /usr/lib64/mozilla-1.0.3

but the actual path containing the files in the seamonkey RPM is:

        /usr/lib64/mozilla-seamonkey-1.0.3/

As a result, the 'mozilla-rebuild-databases.pl' script has no effect.  It is
unclear whether or not this is a bad thing.  Previous releases of the 'mozilla'
package from Red Hat always ran this script after installation.


Note also that some of the files which this script regenerates such as:

        /usr/lib64/mozilla-1.0.3/chrome/overlayinfo
        /usr/lib64/mozilla-1.0.3/chrome/*.rdf
        /usr/lib64/mozilla-1.0.3/component.reg
        /usr/lib64/mozilla-1.0.3/components/compreg.dat
        /usr/lib64/mozilla-1.0.3/components/xpti.dat
        /usr/lib64/mozilla-1.0.3/chrome/lang/installed-chrome.txt

are also packaged in the RPM.  As a result, after the script is run (on previous
versions of the 'mozilla' RPM), the contents of these files are modified and/or
deleted.  Therefore, attempting to do a RPM verify will show errors and missing
files.

Perhaps the RPM package should be changed to either not include these files
(those which are automatically regenerated by mozilla-rebuild-databases.pl), or
else they should be marked as %config or the like.  I will defer this question
to mozilla experts.

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

seamonkey-1.0.3-0.el4.1

How reproducible:

always

Steps to Reproduce:
1. install 'seamonkey' package from RHEL4-U4
2. note that 'mozilla-rebuild-databases.pl' script run in %post has no effect,
because it is using an incorrect path name.
  
Actual results:

The mozilla databases in, e.g.:

        /usr/lib/mozilla-seamonkey-1.0.3

are not regenerated.  (which is what I would expect based on previous 'mozilla'
RPMs from Red Hat, prior to the mozilla -> seamonkey upgrade in RHEL4-U4)

Expected results:

I assume that the mozilla-rebuild-databases.pl script should have regenerated
these files.  (Red Hat mozilla experts please answer)

Additional info:

Comment 1 wingc 2006-08-25 20:25:22 UTC
Created attachment 134960 [details]
[PATCH] seamonkey.spec: fix path name in mozilla-rebuild-databases.pl

Here is a patch against seamonkey.spec that should fix the path name in
mozilla-resbuild-databases.pl

Please confirm that this will restore the desired behavior as Red Hat sees it.

Comment 2 Rex Dieter 2006-10-25 17:51:22 UTC
This breaks seamonkey-mail (and pretty much any other seamonkey-* addon that
runs mozilla-rebuild-databases.pl in %post scriptlets).  Thanks wingc for the
detective-work, I can vouge that running:

sed -i -e "s|/usr/lib/mozilla-1.0.5|/usr/lib/mozilla-seamonkey-1.0.5|g" \
  /usr/lib/mozilla-seamonkey-1.0.5/mozilla-rebuild-databases.pl

/usr/lib/mozilla-seamonkey-1.0.5/mozilla-rebuild-databases.pl

makes things work again.


Comment 3 Rex Dieter 2006-11-16 19:55:13 UTC
FYI, bug still present in seamonkey-1.0.6 update/release.  Patch is provided,
should be a no-brainer.


Comment 4 Martin Stransky 2006-11-27 16:51:53 UTC
Created attachment 142184 [details]
proposed patch

Comment 5 Rex Dieter 2007-01-05 14:30:45 UTC
Confirmed problem still present in seamonkey-1.0.7-0.1.el4

Comment 6 Dmitry Butskoy 2007-01-09 15:13:33 UTC
The same in Fedora Core now :(

Comment 7 RHEL Program Management 2007-01-09 15:27:46 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 9 Martin Stransky 2007-03-06 09:20:57 UTC
fixed in seamonkey-1.0.8-0.1.el4