-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
firefox: 68.0.2 -> 69.0 #67924
firefox: 68.0.2 -> 69.0 #67924
Conversation
I did a build and it's been running well for the last half hour of active browsing 👍 Thanks! |
Let's try to do some rebuilds in advance of Firefox release.
Thanks @vcunat I was just about to do that as well :-) |
I forgot to push it yesterday, but hopefully this staging-next iteration won't take too long. We'll see about regressions from other changes. |
The Security Advisory for this update can be found here: |
@vcunat From my point of view this is good to go in. The staging-next build seems to be rather extensive. Do we want to wait for that to finish? I did a rebuild of the nixos release set and it looks fine. |
🤔 Borg claims about 23k rebuilds for this PR, and there's 55k remaining for staging-next on Hydra (including the NSS bump). The other CVEs fixed in current master..staging-next seem less important at a quick look, though. It's not clear to me which way to go. |
Yeah, that number is surprisingly high. The 19.03 PR only had: 7k https://gist.github.com/GrahamcOfBorg/d6630ad59e271a709ed6f4d21832b4fd Looking back at the previous PR to master it was in the same ballpark: https://gist.github.com/GrahamcOfBorg/3248abcdc9f3f98ac51b03a7ab13409a |
…owngrades While Firefox 68 started messing with our profiles and required new profiles on binary location changes Firefox 69 now verifies that we aren't downgrading to an older Firefox even of the same version. If you switch between two channel versions and/or between nixpkgs releases Firefox will refuse to start and demand a fresh profile. Disabling the downgrade protection works around that issue.
The mass rebuilds were in master for several hours now. |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/why-does-the-following-setup-reset-firefox/4129/3 |
Motivation for this change
Firefox 69 is scheduled to be released tomorrow. To be able to build that we will have to bump NSS on master and add yet a bit more of logic to the build expression.
Changelog: https://www.mozilla.org/en-US/firefox/69.0/releasenotes/
Security Fixes: https://www.mozilla.org/en-US/security/advisories/mfsa2019-25/
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @