Update rules to serve Widevine version 4.10.1440.19
Categories
(Release Engineering :: Release Requests, task)
Tracking
(Not tracked)
People
(Reporter: bryce, Unassigned)
References
(Blocks 1 open bug)
Details
Bug 1558924 means that Widevine 4.10.1440.18 is not working on MacOS 10.15 beta 1. Investigation suggests that this is due to new library loading restrictions. To mitigate this we wish to use a new Widevine lib that is signed (4.10.1440.19).
As we would prefer to keep all Widevine versions matching, we should also update the Linux and Windows cases. It appears that outside of the MacOS CDM the files for 4.10.1440.18 and 4.10.1440.19 are the same. The MacOS CDM appears largely similar, but with extra signing. As such, I don't expect any major difference between these versions.
Could we stage a set of test rules on the nightlytest channel to smoke test these new CDMs in preparation for a wider roll out? CDM details follow:
Linux32:
Got https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1440.19-linux-ia32.zip
SHA512: f5f48f2a138da6e11fd655ce3bedd4c71eac50a40ac32c61bfaf4daa0c3a1e9eace5c8b3beecb7461b1c4e3da2c4562db0d92206408a9f3eecc778aa3baf54f3
file size: 3855473 bytes
Linux64:
Got https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1440.19-linux-x64.zip
SHA512: 6028d480c763abd4c888d042b05c96e01487316395d425df0de6123b8113f94b8d3424b22056d0cb1f6f7786ee08b318febffb72df25a84b8ce135969130301a
file size: 3540154 bytes
MacOS:
Got https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1440.19-mac-x64.zip
SHA512: 3134e46e3d08debc1cf1dc025532cb55e3038b61d39e30c4509cf06376513063885cfb715a09fe2956ef7ca402d13d0cfa53bb560211189c8f31e8b68724377a
file size: 3829468 bytes
Windows32:
Got https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1440.19-win-ia32.zip
SHA512: 01a6e29b750ab0014b13391c1a6d7a2a2f36341a3f07d62c494c2f8f3f3f18812352b01c2a6797418c91c9fd136bd03e7d12d272029be1b992c5eb6376227a72
file size: 4980571 bytes
Windows64:
Got https://redirector.gvt1.com/edgedl/widevine-cdm/4.10.1440.19-win-x64.zip
SHA512: 44b59c028140f735df125a3765417f0a0491d3369d2f83a5317488be9285b911910b30afa5ad44651bc39ed7221b9a5d0ba991df1cea609f52eaa058ed702e58
file size: 4753555 bytes
|
||
Comment 1•5 years ago
|
||
Ok, so I have now created a rule for .19...
I should note that we (releng) likely will want to shuffle these rules a bit to be clearer, I spent a longer time trying to understand the rule state than I would have liked.
|
Reporter | |
Comment 2•5 years ago
|
||
(In reply to Justin Wood (:Callek) from comment #1)
Ok, so I have now created a rule for .19...
I should note that we (releng) likely will want to shuffle these rules a bit to be clearer, I spent a longer time trying to understand the rule state than I would have liked.
Thanks. A reshuffle of existing rules is fine by me. A broader rework of rules has been on my mind for awhile now. I've created bug 1566524 to track that.
|
|
Reporter | |
Comment 3•5 years ago
|
||
The other blockers for bug 1558924 have landed and we're seeing Widevine work on the Catalina beta when using the test channel. Could we roll the rules we have for the test channel out to nightly?
|
||
Comment 4•5 years ago
|
||
I'm covering for Mitch's releaseduty today. Scheduled: https://aus4-admin.mozilla.org/scheduled_changes/rules/1828
|
||
Comment 5•5 years ago
|
||
Hey Guys, any update on this? When can we expect the release of an updated Widevine version?
|
|
Reporter | |
Comment 6•5 years ago
|
||
(In reply to manthansharma from comment #5)
Hey Guys, any update on this? When can we expect the release of an updated Widevine version?
This is in nightly now. We're likely to roll it out to further versions soon -- I'm looking to start that process today. Are you asking as you're seeing MacOS Catalina issues?
|
|
Reporter | |
Comment 7•5 years ago
|
||
This has been in nightly for a couple of weeks and I haven't heard any issues reported. I think we should consider rolling this out to a wider release. I'm looking to target beta (69) and both ESRs.
I think it would make our rules a lot simpler if we bumped all ESRs from 60.8+ to the new release, but it would mean shipping already released ESRs. Any thoughts from release management regarding this? Specifically, will cooking rules to ship the update instead to ESR 60.9+ and ESR 68.1+ be painful? It looks that way to me -- having a rule for 60.9+ at 4.10.1440.10 while keeping 68.0 at 4.10.1440.19 seems like it would introduce non-trivial complexity.
Making sure there's no ambiguity above: I am not asking for a rule change yet, but want feedback. From my perspective there is a low risk of 4.10.1440.18 -> 4.10.1440.19 causing issues, and I would prefer simpler rules, so I think doing the above is worthwhile. However, I'm not the one managing the rules.
|
|
Reporter | |
Comment 8•5 years ago
|
||
NI :Callek when you have a moment free. Please let me know if comment 7 could use any clarification.
|
|
||
Comment 9•5 years ago
|
||
(In reply to Bryce Seager van Dyk (:bryce) from comment #6)
(In reply to manthansharma from comment #5)
Hey Guys, any update on this? When can we expect the release of an updated Widevine version?
This is in nightly now. We're likely to roll it out to further versions soon -- I'm looking to start that process today. Are you asking as you're seeing MacOS Catalina issues?
Yeah, I am facing the bug https://bugzilla.mozilla.org/show_bug.cgi?id=1558924 in MacOS Catalina Public Beta 3.
|
|
Reporter | |
Comment 10•5 years ago
|
||
(In reply to manthansharma from comment #9)
(In reply to Bryce Seager van Dyk (:bryce) from comment #6)
(In reply to manthansharma from comment #5)
Hey Guys, any update on this? When can we expect the release of an updated Widevine version?
This is in nightly now. We're likely to roll it out to further versions soon -- I'm looking to start that process today. Are you asking as you're seeing MacOS Catalina issues?
Yeah, I am facing the bug https://bugzilla.mozilla.org/show_bug.cgi?id=1558924 in MacOS Catalina Public Beta 3.
If you're willing to use the nigthly release the issue is already mitigated there. Beyond that I'm hoping that we get the changes for the fix into beta (69) and the ESRs in the near future. Please be aware we're not planning to put the changes into Firefox 68 at this point.
|
|
||
Comment 11•5 years ago
|
||
No concerns or clarification needed from the Release Engineering side, I'm going to toss the n-i over to :ritu from Release Management since c#7 reads more like its best for them to comment.
Feel free to send me/releng a new n-i once this is ready to be actioned
Hi Bryce, I'd recommend shipping a rule to update Widevine version to *.19 on Beta69 first. If that goes well and there are no regression for 3 days, we can create another rule for ESR68.1 and ESR60.9. Are you ok with this plan? If yes, please send an email to r-d about this plan if you haven't already done so.
|
|
Reporter | |
Comment 13•5 years ago
|
||
Sounds reasonable. I will get that email sorted shortly.
|
|
Reporter | |
Comment 14•5 years ago
|
||
Could we please prepare rules to roll 4.10.1440.19 out to Beta69? Per comment 12, we can let that back and if we see no issues, look at rolling out to the ESRs.
|
|
||
Comment 15•5 years ago
|
||
This is now live on beta and should be live on aurora (deved) soon...
|
|
Reporter | |
Comment 16•5 years ago
|
||
This has been in beta without issue for just under a week. Could we roll out to both ESRs please? We would like to target ESR 60.9+ and ESR 68.1+.
|
|
||
Comment 17•5 years ago
|
||
(In reply to Bryce Seager van Dyk (:bryce) from comment #16)
This has been in beta without issue for just under a week. Could we roll out to both ESRs please? We would like to target ESR 60.9+ and ESR 68.1+.
This should now all be live. (including 69+ on -release)
Description
•