Closed
Bug 151671
Opened 23 years ago
Closed 23 years ago
Mozilla 1.0.1 should use NSPR 4.2.1
Categories
(SeaMonkey :: General, defect, P2)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.0.1
People
(Reporter: wtc, Assigned: wtc)
Details
(Whiteboard: [adt3 RTM])
Attachments
(2 files, 1 obsolete file)
|
1.24 KB,
patch
|
Details | Diff | Splinter Review | |
|
3.59 KB,
patch
|
Details | Diff | Splinter Review |
MOZILLA_1_0_BRANCH is now using a version of NSPR
marked as "4.2 Beta". It is almost the same as
NSPR 4.2 RTM, plus a few fixes from NSPR 4.2.1.
I would like to check in the remaining NSPR 4.2
and 4.2.1 fixes on the MOZILLA_1_0_BRANCH so that
Mozilla 1.0.1 will be using NSPR 4.2.1.
| Assignee | ||
Comment 1•23 years ago
|
||
Note that for ease of code review, I omitted the
changes to the NSPR files that are not used by
Mozilla.
I would like to check in all the fixes, but am
open to excluding the ones that you consider high
risk.
| Assignee | ||
Updated•23 years ago
|
Is it bad to have the config.guess and config.sub changes out of sync with the
other copies in the Mozilla tree? I recall seawood saying something like that.
I also recall seawood getting approval to land that patch anyway...
Comment 3•23 years ago
|
||
a=blizzard on behalf of drivers for the 1.0 branch. Please make sure that you
work with cls to get the config.* files figured out, as dbaron says.
Keywords: mozilla1.0.1 → mozilla1.0.1+
| Assignee | ||
Comment 4•23 years ago
|
||
I can exclude the config.guess and config.sub changes
from this bug and handle them separately.
Status: NEW → ASSIGNED
Comment 5•23 years ago
|
||
No visible user benefit = adt1.0.1-.
| Assignee | ||
Comment 6•23 years ago
|
||
The resolution should not be FIXED. Reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Updated•23 years ago
|
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Comment 7•23 years ago
|
||
Marked WONTFIX.
Comment 8•23 years ago
|
||
Yay, my users are going to be impacted by a beta nspr release.
| Assignee | ||
Comment 9•23 years ago
|
||
I have a different patch. The new patch is much
smaller and easier to assess its risk.
I am going to present the patch in two parts. This
is Part I, which consists of the changes that affect
Mozilla.
1. A fix for bug 135008.
2. New NSPR version number "4.2.1 Beta".
Attachment #87595 -
Attachment is obsolete: true
| Assignee | ||
Comment 10•23 years ago
|
||
Part II of the new patch consists of the changes that
do not affect Mozilla.
1. Update the NSPR binary distribution packaging script
for NSPR 4.2.1. This script is not used by Mozilla.
2. Remove a blank line from a header file that is not
included by NSPR.
3. Fix incorrect assertions in PR_SendFile. Mozilla
does not use the PR_SendFile function.
4. Update a test program for NSPR 4.2.1. The test
program is not shipped with Mozilla.
Attachment #88516 -
Attachment is obsolete: true
| Assignee | ||
Updated•23 years ago
|
Attachment #88516 -
Attachment description: Patch Part 1: changes that affect Mozilla → Patch Part I: changes that affect Mozilla
Attachment #88516 -
Attachment is obsolete: false
| Assignee | ||
Comment 11•23 years ago
|
||
Reopened the bug and requesting mozilla1.0.1 and adt1.0.1
approvals for the new patch.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 12•23 years ago
|
||
Adding adt1.0.1+ on behalf of the adt for checkin to the 1.0 branch. Please get
drivers approval before checking in. When you check this into the branch, please
change the mozilla1.0.1+ keyword to fixed1.0.1
Comment 13•23 years ago
|
||
a=blizzard on behalf of drivers for the 1.0 branch.
Updated•23 years ago
|
Keywords: mozilla1.0.1 → mozilla1.0.1+
| Assignee | ||
Comment 14•23 years ago
|
||
The new patch has been checked into the MOZILLA_1_0_BRANCH.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Keywords: mozilla1.0.1+ → fixed1.0.1
Resolution: --- → FIXED
Comment 15•23 years ago
|
||
stephen - do you know how to verify this fix for branch?
I'm not 100% sure, exactly:
C:\branch>cvs co -r MOZILLA_1_0_BRANCH mozilla/client.mk
U mozilla/client.mk
C:\branch>cd mozilla
C:\branch\mozilla>make -f client.mk
make: c:/branch/mozilla/build/unix/abs2rel.pl: Command not found
checkout start: Sat Aug 24 21:30:41 2002
cvs -q -z 3 co -r MOZILLA_1_0_BRANCH -P mozilla/client.mk
mozilla/build/unix/modules.mk
make[1]: c:/branch/mozilla/build/unix/abs2rel.pl: Command not found
make[1]: Entering directory `/cygdrive/c/branch'
cvs -q -z 3 co -P -r MOZILLA_1_0_BRANCH mozilla/nsprpub
I thought I could check the NSPR module under LXR, but it appears to be one
entity, that is: not having a separate MOZILLA_1_0_BRANCH entry like /mozilla
does under http://lxr.mozilla.org by which to query for changes.
| Assignee | ||
Comment 17•23 years ago
|
||
You can verify as follows:
cvs co -r MOZILLA_1_0_BRANCH mozilla/nsprpub/pr/include/prinit.h
Open prinit.h and verify that the value of PR_VERSION is "4.2.1".
#define PR_VERSION "4.2.1"
#define PR_VMAJOR 4
#define PR_VMINOR 2
#define PR_VPATCH 1
#define PR_BETA PR_FALSE
Verified FIXED for the MOZILLA_1_0_BRANCH.
Keywords: fixed1.0.1 → verified1.0.1
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•