If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Aurora 28 branch still uses NSPR beta, please upgrade to NSPR 4.10.3 RTM tag

RESOLVED FIXED in Firefox 28

Status

()

Core
Build Config
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: kaie, Assigned: keeler)

Tracking

28 Branch
mozilla28
Points:
---

Firefox Tracking Flags

(firefox28+ fixed, firefox29+ fixed, firefox30 fixed)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Can you please import NSPR 4.10.3 into the aurora 28 branch?

python client.py update_nspr NSPR_4_10_3_RTM
(Reporter)

Updated

4 years ago
status-firefox28: --- → affected
tracking-firefox28: --- → ?
This is the same as updating NSS, except use "update_nspr" instead of "update_nss". I think the tag should be NSPR_4_10_3_RTM.
Assignee: nobody → dkeeler
(Reporter)

Comment 2

4 years ago
Created attachment 8366196 [details] [diff] [review]
p-964437

This upgrade is necessary, because Mozilla never ships NSPR-BETA versions in releases, only RTM-versions, and aurora currently uses a beta.
Attachment #8366196 - Flags: approval-mozilla-aurora?
Comment on attachment 8366196 [details] [diff] [review]
p-964437

Review of attachment 8366196 [details] [diff] [review]:
-----------------------------------------------------------------

(In reply to Brian Smith (:briansmith, :bsmith; NEEDINFO? for response) from comment #1)
> This is the same as updating NSS, except use "update_nspr" instead of
> "update_nss". I think the tag should be NSPR_4_10_3_RTM.

FWIW, I ran `./client.py update_nspr NSPR_4_10_3_RTM && hg addremove`... and got the same patch as this.

Comment 4

4 years ago
Comment on attachment 8366196 [details] [diff] [review]
p-964437

Review of attachment 8366196 [details] [diff] [review]:
-----------------------------------------------------------------

r=wtc.
Attachment #8366196 - Flags: review+
tracking-firefox28: ? → +
Attachment #8366196 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
(Reporter)

Comment 5

4 years ago
Thank you for the approval.
https://hg.mozilla.org/releases/mozilla-aurora/rev/0386e163f0f7
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
status-firefox28: affected → fixed
status-firefox29: --- → unaffected
Target Milestone: --- → mozilla28
(Reporter)

Comment 6

4 years ago
We must do the same thing for Aurora 29.

(I had forgotten to land the update into mozilla-central prior to the most recent merge.)
(Reporter)

Comment 7

4 years ago
May we reuse the approval-aurora?
(Reporter)

Updated

4 years ago
Flags: needinfo?(lsblakk)
Yes - will this need to happen again for future versions or am I correct in marking it 'fixed' on 30?
status-firefox29: unaffected → affected
status-firefox30: --- → fixed
tracking-firefox29: --- → +
Flags: needinfo?(lsblakk)
(Reporter)

Comment 9

4 years ago
(In reply to Lukas Blakk [:lsblakk] from comment #8)
> Yes 

thank you!


> will this need to happen again for future versions or am I correct in
> marking it 'fixed' on 30?

Yes, 30 already won't need an update to 4.10.3 RTM, because 30 already uses 4.10.4 beta
(Reporter)

Comment 10

4 years ago
fixed on 29.
https://hg.mozilla.org/releases/mozilla-aurora/rev/6c70ddf78844
status-firefox29: affected → fixed
You need to log in before you can comment on or make changes to this bug.