seamonkey nightlies broken on linux

[Andrew Schultz]

SeaMonkey nightly builds starting with yesterday's (3/28) ship with
chrome RDF files with overly restrictive permissions (0600). Assuming
your app dir ends up owned by root, you won't be able to run SeaMonkey
as a normal user. You'll need to do

% chmod a+r [SM_DIR]/chrome/*.rdf

until we fix SeaMonkey to ship with files having proper permissions (not
sure how to pull that off just yet other than packaging hacks).

The bustage resulted from the change in
https://bugzilla.mozilla.org/show_bug.cgi?id=375102

--
Andrew Schultz
ajsc...@verizon.net
http://www.sens.buffalo.edu/~ajs42/

[Andrew Schultz]

Andrew Schultz wrote:
> SeaMonkey nightly builds starting with yesterday's (3/28) ship with

*trunk* nightly builds

[Tony Mechelynck]

Andrew Schultz wrote:
> Andrew Schultz wrote:
>> SeaMonkey nightly builds starting with yesterday's (3/28) ship with
>
> *trunk* nightly builds
>

You may want to add a comment to the culprit bug, or it won't get fixed.

Best regards,
Tony.
--
"I haven't lost my mind; I know exactly where I left it."

[Seth Spitzer]

Andrew,

This was my change. Can you elaborate (in the bug) about the problem?

Specifically, how the users profile dir would not be read/write-able by
the user?

-Seth

[Neil]

Seth Spitzer wrote:

> Specifically, how the users profile dir would not be read/write-able
> by the user?

This doesn't affect the user's profile dir. The issue is that when root
(or whomever installed SeaMonkey) registers chrome, the RDF files are
written with 0600 permissions so that nobody else can read them.

--
Warning: May contain traces of nuts.