[Security Update] 2019-01-30 - Firefox 65.0

I have built and pushed Firefox 65.0 to the following branches:

  • stable
  • testing
  • unstable
     
  • x32-stable
  • x32-testing
  • x32-unstable

As is always the case for a short-turnaround update, this package has had only minimal testing.


Release notes: https://www.mozilla.org/en-US/firefox/65.0/releasenotes/
Security advisory: https://www.mozilla.org/en-US/security/advisories/mfsa2019-01/


Other packages will arrive as they are built.

unstable already has Firefox 65 and Chromium 72.

37 Likes

Thanks!

Can you please do the same for Chrome 72…?!? :wink:

Google solves more than 50 security issues in Chrome 72

Soon. There’s Thunderbird to build too.

7 Likes

Is there a way to receive the rolling release updates as in Arch?

Use Arch?

unstable is synced to Arch stable, every other branch has packages moved batch-by-batch through the various testing phases:

That means various packages have to be rebuilt against the libraries in stable if they need updating faster.

5 Likes

Well, I like the kernel and driver handling of Manajaro, but would like to have the up to date packages

OK, so the obvious solution for your particular requirements (i.e. to always have the most recent version of every package) is to use the unstable branch.

Although - if you want the absolute most recent then you need to switch to Arch testing+staging. But good luck with that.

4 Likes

Thanks!

7 posts were split to a new topic: Why no update?

A post was merged into an existing topic: Why no update?

Excellent :wink:

For firefox-kde users: currently it’s not possible to build with the KDE patchset because they haven’t been updated for FF 65 yet.

EDIT: it’s just the mozilla-nongnome patch that needs to be adapted. I’ll try without it (or fix the patch…)

EDIT 2: errr sorry… no it’s much more than just that single patch :frowning:

4 Likes

Building kde-opensuse now, will post later today.
I’ve been down with the flu and didn’t notice Arch had updated.
Even though I’m still sick, this package I usually build on my home PC so a trip into the office isn’t needed. :wink:

5 Likes

Please report back if you get it working.
Thanks :slight_smile:

Everything is fine, thanx. :slightly_smiling_face:

Update: I’m reworking that patch now.
But then, my patching skills are not so great.

3 Likes

Update, nope it’s more than just that one patch:

patching file toolkit/system/unixproxy/nsUnixSystemProxySettings.cpp
Hunk #1 succeeded at 56 with fuzz 1 (offset 1 line).
patching file modules/libpref/Preferences.cpp
Hunk #2 FAILED at 4909.
Hunk #3 succeeded at 4533 with fuzz 1 (offset -443 lines).
1 out of 3 hunks FAILED -- saving rejects to file modules/libpref/Preferences.cpp.rej
patching file modules/libpref/moz.build
patching file python/mozbuild/mozpack/chrome/flags.py
patching file python/mozbuild/mozpack/chrome/manifest.py
patching file toolkit/components/downloads/moz.build
patching file toolkit/content/jar.mn
Hunk #1 FAILED at 68.
1 out of 1 hunk FAILED -- saving rejects to file toolkit/content/jar.mn.rej
patching file toolkit/content/widgets/dialog-kde.xml
patching file toolkit/mozapps/downloads/nsHelperAppDlg.js
Hunk #1 succeeded at 1030 (offset -1 lines).
patching file toolkit/system/unixproxy/nsUnixSystemProxySettings.cpp
Hunk #1 FAILED at 15.
Hunk #2 FAILED at 39.
Hunk #3 FAILED at 505.
Hunk #4 FAILED at 540.
4 out of 4 hunks FAILED -- saving rejects to file toolkit/system/unixproxy/nsUnixSystemProxySettings.cpp.rej
patching file toolkit/xre/moz.build
Hunk #1 succeeded at 73 (offset 5 lines).
patching file toolkit/xre/nsKDEUtils.cpp
patching file toolkit/xre/nsKDEUtils.h
patching file uriloader/exthandler/HandlerServiceParent.cpp
Hunk #1 FAILED at 1.
Hunk #2 FAILED at 265.
2 out of 2 hunks FAILED -- saving rejects to file uriloader/exthandler/HandlerServiceParent.cpp.rej
patching file uriloader/exthandler/moz.build
patching file uriloader/exthandler/unix/nsCommonRegistry.cpp
patching file uriloader/exthandler/unix/nsCommonRegistry.h
patching file uriloader/exthandler/unix/nsKDERegistry.cpp
patching file uriloader/exthandler/unix/nsKDERegistry.h
patching file uriloader/exthandler/unix/nsMIMEInfoUnix.cpp
Hunk #1 FAILED at 1.
Hunk #2 FAILED at 59.
2 out of 2 hunks FAILED -- saving rejects to file uriloader/exthandler/unix/nsMIMEInfoUnix.cpp.rej
patching file uriloader/exthandler/unix/nsOSHelperAppService.cpp
Hunk #2 FAILED at 1122.
Hunk #3 FAILED at 1140.
Hunk #4 FAILED at 1237.
Hunk #5 FAILED at 1358.
4 out of 5 hunks FAILED -- saving rejects to file uriloader/exthandler/unix/nsOSHelperAppService.cpp.rej
patching file widget/gtk/moz.build
Hunk #1 succeeded at 116 (offset -7 lines).
patching file widget/gtk/nsFilePicker.cpp
Hunk #2 FAILED at 248.
Hunk #3 FAILED at 373.
Hunk #4 FAILED at 602.
3 out of 4 hunks FAILED -- saving rejects to file widget/gtk/nsFilePicker.cpp.rej
patching file widget/gtk/nsFilePicker.h
Hunk #1 FAILED at 69.
1 out of 1 hunk FAILED -- saving rejects to file widget/gtk/nsFilePicker.h.rej
patching file xpcom/components/ManifestParser.cpp
Hunk #1 FAILED at 33.
Hunk #2 succeeded at 392 (offset -29 lines).
Hunk #3 FAILED at 477.
Hunk #4 FAILED at 601.
Hunk #5 FAILED at 664.
4 out of 5 hunks FAILED -- saving rejects to file xpcom/components/ManifestParser.cpp.rej
patching file xpcom/components/moz.build
Hunk #1 FAILED at 43.
1 out of 1 hunk FAILED -- saving rejects to file xpcom/components/moz.build.rej
patching file xpcom/io/nsLocalFileUnix.cpp
Hunk #2 FAILED at 2008.
1 out of 2 hunks FAILED -- saving rejects to file xpcom/io/nsLocalFileUnix.cpp.rej
==> ERROR: A failure occurred in prepare().
   Aborting...

Let me see what I can do with the other patches later.
If not, I’ll just have to wait on Wolfgang to fix them.

3 Likes

Use Arch?

Lol’ed at your response.
Well played good sir.

Updated, no issues to report. Manjaro Deepin edition. Thank you devs!

It looks like in the new version they combined the privacy cookie settings. I had mine previously set to block “all 3rd party cookies” but the new version only has apparently 1 setting and this was set on “3rd party trackers”…but you can set this option to “all 3rd party cookies.” Definitely worth checking out your settings.

3 Likes

Forum kindly sponsored by