Upgrade Mozilla to NSS 3.12.10

RESOLVED FIXED

Status

()

Core
Security: PSM
RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: kaie, Assigned: kaie)

Tracking

Trunk
x86
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments, 1 obsolete attachment)

(Assignee)

Description

7 years ago
Eventually we'll upgrade Mozilla to NSS 3.12.10

This release is not yet ready, but I'm filing this bug early, for tracking of depdencies.
(Assignee)

Updated

6 years ago
Blocks: 479393
(Assignee)

Comment 1

6 years ago
Created attachment 529949 [details]
Beta upgrade action

We are very close to releasing NSPR 4.8.8 and NSS 3.12.10
We performed QA, both NSS QA and mozilla-central try server builds.

The only remaining issue is NSPR patch bug 645459, which causes a build failure on OSX 64 bit.

I have backed out that patch.

I have verbal agreement (review) from Wan-Teh Chang, Bob Relyea and Brian Smith that we want to land these betas into mozilla-central.

I don't attach a patch. It's large, instead, I'm attaching the tags/commands that are used to land this patch.
Assignee: nobody → kaie
Attachment #529949 - Flags: review+
(Assignee)

Comment 2

6 years ago
I expect that the final releases can be landed within the next couple of days. Most likely, the only change will be the version numbers embedded in the files.

I want to land these nearly-final-betas now, because they are blocking other work (respindola pushes me to get this done).
(Assignee)

Comment 3

6 years ago
landed betas:
http://hg.mozilla.org/mozilla-central/rev/d30b2e9c999a

backout on top:
http://hg.mozilla.org/mozilla-central/rev/c89356582dc9

Because I made that backout on nspr trunk, I didn't add information to the tree about the backout.


Keeping bug open, because we to land the final versions, soon.


Wan-Teh:
Glandium has asked me to upgrade a snapshot newer than nspr-beta3, because he is waiting for another patch to configure. But the latest nspr trunk hasn't been tested with tryserver yet, I didn't want to skip my tested snapshot, and I didn't want to tag an updated beta without having asked you.

Are you going to tag a beta 4?
(Assignee)

Comment 4

6 years ago
sorry, had to back things out, because of confusion around bug 345094
(Assignee)

Comment 5

6 years ago
relanded the beta versions:
http://hg.mozilla.org/mozilla-central/rev/29f3dc7ad5db

This time it appears to stick.

I will keep this bug open.
We will very soon have the final release of NSPR/NSS.
It's expected that only the version names inside the files will change.

I will land the changes to the final version within the next days.

Comment 6

6 years ago
I pushed NSPR_4_8_8_RTM to mozilla-central:
http://hg.mozilla.org/mozilla-central/rev/263ea410a1f9
(Assignee)

Comment 7

6 years ago
Created attachment 534405 [details] [diff] [review]
patch - set version and tag info numbers to final

There were no code changes between the beta version (that has already landed on mozilla-central a while ago) and the final release version.

This patch is necessary to bring the version numbers in synch with the final release, it was produced using

cvs -q rdiff -u -r NSS_3_12_10_BETA1 -r NSS_3_12_10_RTM mozilla/dbm mozilla/security/dbm mozilla/security/coreconf mozilla/security/nss

(plus the TAG-INFO file that we keep in synch).


Given that there are no code changes, r=me
Attachment #534405 - Flags: review+
(Assignee)

Comment 8

6 years ago
Created attachment 534407 [details] [diff] [review]
patch 2 - set version and tag info numbers to final
Attachment #534405 - Attachment is obsolete: true
Attachment #534407 - Flags: review+
(Assignee)

Comment 9

6 years ago
I pushed the missing version number to change to 3.12.10 final.

http://hg.mozilla.org/mozilla-central/rev/b26980e3622a
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED

Updated

6 years ago
Blocks: 651897
You need to log in before you can comment on or make changes to this bug.