Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Update mozilla-central + mozilla-aurora +mozilla-beta to NSS 3.13.2 final release (requires NSPR 4.9 final release)

RESOLVED FIXED in Firefox 11



Security: PSM
6 years ago
6 years ago


(Reporter: briansmith, Assigned: briansmith)


Dependency tree / graph

Firefox Tracking Flags

(firefox9 unaffected, firefox10 unaffected, firefox11+ fixed, firefox12+ fixed)


(Whiteboard: [qa-])

+++ This bug was initially created as a clone of Bug #698552 +++

mozilla-central and mozilla-aurora hold a private patch to NSS that implements an API currently needed by Gecko's SSL implementation. We can never ship a version of Firefox that *requires* private patches to NSS like this because it will break Linux vendor releases that use system NSS.

See the blocking bugs to see the work that needs to be done
status-firefox10: --- → unaffected
status-firefox11: --- → affected
status-firefox12: --- → affected
status-firefox9: --- → unaffected
tracking-firefox11: --- → ?
tracking-firefox12: --- → ?
Severity: enhancement → normal


6 years ago
tracking-firefox11: ? → +
tracking-firefox12: ? → +
Depends on: 718554


6 years ago
Summary: Update mozilla-central and mozilla-aurora to NSS 3.13.2 final release → Update mozilla-central + mozilla-aurora +mozilla-beta to NSS 3.13.2 final release

Comment 1

6 years ago
We should get this done soon.

I tried to help by applying NSS patches in bug 542832.
Now waiting for Brian's feedback whether it looks good.

should this stay open?
Target Milestone: --- → mozilla13


6 years ago
Depends on: 699567
Fx 11.0b1 was released depending on an unreleased nss version. Where's the tracking bug for 3.13.2 final release ?

Comment 4

6 years ago
(In reply to Marco Bonardo [:mak] from comment #2)
> should this stay open?

Yes, because the landing was a release candidate (RC0), not a release.
However, we expect no other NSS changes.
If all went well with the landing of this NSS tag, I will create a final release (RTM) tag soon.

Unfortunately, I was informed about the necessity of a last minute change to NSPR.

mozilla is currently using NSPR 4.9 BETA.

Shipping mozilla releases with a NSPR or NSS beta releases is not allowed by policy.

I wasn't aware that changes of NSPR would be necessary. However, I was informed today there is. In bug 699567 people are working to agree on the final change.
Summary: Update mozilla-central + mozilla-aurora +mozilla-beta to NSS 3.13.2 final release → Update mozilla-central + mozilla-aurora +mozilla-beta to NSS 3.13.2 final release (requires NSPR 4.9 final release)

Comment 5

6 years ago
(In reply to Landry Breuil from comment #3)
> Where's the
> tracking bug for 3.13.2 final release ?

This bug

Comment 6

6 years ago
I've pushed NSPR_4_9_BETA7 for final NSPR release testing.

(Bug must be kept open until NSS_3_13_2 and NSPR_4_9_RTM have been created.)

Comment 8

6 years ago
We have created the final release tags:

- NSPR_4_9_RTM

- NSS_3_13_2_RTM

Brian, could you please update all 3 mozilla branches to these new tags?

Note that mozilla-central already has functional equivalent code snapshots, the only difference are in comments, version numbers and one enum symbol got renamed.

Because of this, after landing into mozilla-central, you don't need to wait, it's fine to immediately land into mozilla-aurora and mozilla-beta.


6 years ago
Target Milestone: mozilla13 → mozilla11
Yes, I will do the landings.

BTW, I guess the convention is for target milestone to stay at the version in which the code landed in mozilla-central; tracking-firefox11 and tracking-firefox12 flags (etc.) are used to track the backporting. (I agree it is confusing, but this is the process we are supposed to follow.)
Target Milestone: mozilla11 → mozilla13
Depends on: 727873
No longer depends on: 727873

This is the landing of NSS 3.13.2 RTM into mozilla-central.

One of the above try runs is for mozilla-aurora and the other is for mozilla-beta. They include all of the PSM and NSS patches approved for beta-11 and aurora-12. Once they complete successfully, I will land all those patches on the branches.
Last Resolved: 6 years ago
Resolution: --- → FIXED


6 years ago
No longer depends on: 699567
status-firefox11: affected → fixed
status-firefox12: affected → fixed

Comment 12

6 years ago
Brian, I see you just landed NSS 3.13.2, thanks for that.

However, you didn't land NSPR 4.9, see comment 8, this still needs to be done.

Would you be able to land that, too, or want me to help?
I missed the deletion of one of the private patches in security/patches and I didn't realize this bug was the one tracking the NSPR 4.9 RTM landing until Kai told me so. Thus:
Duplicate of this bug: 728420

Comment 15

6 years ago
Thank you Brian!
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.