[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[Bug 179802] Review Request: seamonkey
- From: bugzilla redhat com
- To: fedora-extras-list redhat com
- Subject: [Bug 179802] Review Request: seamonkey
- Date: Fri, 10 Feb 2006 15:36:23 -0500
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: seamonkey
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179802
------- Additional Comments From kengert redhat com 2006-02-10 15:36 EST -------
> > Ok, done. Motivated by your proposal, I tried to
> > use the same build code as used in the firefox spec file.
> > But that failed, I got errors in install stage,
>
> What specific errors?
During install, the RPM build system tries to access a path that does not match
what is produced in /var/tmp
As it requires so much time to build, I was not motivated to make further
attempts, but decided to go with the code that works.
> Does it work if you Require: seamonkey (it should be Require anyway, and
> please one Require per line.)
You mean RequireS: instead of Prereq: ?
Trying.
> > Or should we use some "find" statements to change the modes before they
> > are copied? Or do you have a better idea?
>
> I think either solution is probably sufficient.
I found the existing spec has
# fix permissions of the chrome directories
/usr/bin/find . -type d -perm 0700 -exec chmod 755 {} \; || :
I will add
# We don't want JS files to be executable
/usr/bin/find . -type f -name \*.js -exec chmod 644 {} \; || :
and see if that works
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]