Closed Bug 28486 Opened 25 years ago Closed 25 years ago

Need to take new NSPR tag for SSL fixes

Categories

(SeaMonkey :: Build Config, defect, P3)

PowerPC
Mac System 8.5

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mw, Assigned: jj.enser)

Details

(Whiteboard: [PDT+])

The changes I checked into mozilla/nsprpub via wtc@netscape.com landed in the
version tagged "NSPRPUB_RELEASE_4_0". SSL will not work at all (in fact, the
machine will freeze when attempting to load pages over SSL) unless the build
team moves over to using that tag. Bug 19119 depends on this bug.
Attaching to M14 / requesting beta1 evaluation by PDT
Blocks: 19119
Keywords: beta1
Target Milestone: M14
Actually, there will probably be another NSPR fix coming in conjunction with
this one, relating to missing pictures on an SSL connection. How we determine
where to put that fix is unclear to me. (I'll file a bug against myself for the
other fix.)
Waiting for approval to switch the Mac Release Build script from 
"NSPRPUB_20000208" to "NSPRPUB_RELEASE_4_0".

This doesn't look like a Mac-only change... please advise whether Win/Unix should 
also pull from this tag.
Status: NEW → ASSIGNED
Note that wtc has approval to move to the new NSPR tag.  Please coordinate as 
needed.
Thanks,
Jim
PDT+added
Whiteboard: [PDT+]
As of today, SeaMonkey is pulling NSPRPUB_RELEASE_4_0_20000218.
Can you add a completion date for this bug? It seems like it should be RSN 
(since wtc has landed his tag).  Please add it to the whiteboard.
as of this morning, unix verification builds are now pulling the new NSPR 4 
release tag.  I believe the win32 builds are as well, but I'll leave it to leaf 
to give final confirmation of that.
Yes, windows builds are using the NSPRPUB_RELEASE_4_0_20000218 release tag.
same for Mac. Marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Marking Verified.
Status: RESOLVED → VERIFIED
No longer blocks: 19119
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.