From: Mark H Weaver <mhw@netris.org>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: help-guix@gnu.org
Subject: Re: Recipe for latest release of firefox?
Date: Tue, 01 Oct 2019 06:45:04 -0400 [thread overview]
Message-ID: <87h84srbg4.fsf@netris.org> (raw)
In-Reply-To: <87impa92dr.fsf@dustycloud.org> (Christopher Lemmer Webber's message of "Sun, 29 Sep 2019 18:14:08 -0400")
Hi Christopher,
Christopher Lemmer Webber <cwebber@dustycloud.org> writes:
> Does someone have a recipe, or channel, for the latest release of
> Firefox?
>
> Mark Weaver was doing an amazing job of patching icecat to be up to date
> on security releases. Since nobody is doing that work currently, I'm a
> bit worried about the security of my browsing...
FWIW, I'm still using IceCat 60.9, based on Firefox ESR 60.9, which was
released at the same time as Firefox ESR 68.1. Those are the most
recent upstream ESR releases from Mozilla, so our IceCat package is
currently up to date.
The next IceCat update will be needed when you see a version number
newer than 68.1 on the following page:
https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox-esr/
The next update is currently scheduled for October 22, when Firefox 70
and Firefox 68.2 ESR are due to be released. Unless an especially
urgent issue is discovered, leading to an "out of band" release from
Mozilla, it's likely that no action will be needed until October 22.
Regards,
Mark
next prev parent reply other threads:[~2019-10-01 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 22:14 Recipe for latest release of firefox? Christopher Lemmer Webber
2019-09-30 13:09 ` John Soo
2019-10-01 10:45 ` Mark H Weaver [this message]
2019-10-01 12:13 ` Christopher Lemmer Webber
2019-10-02 0:32 ` Mike Gerwitz
2019-10-02 3:10 ` Amin Bandali
2019-10-03 1:36 ` Mike Gerwitz
2019-10-03 2:58 ` Amin Bandali
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h84srbg4.fsf@netris.org \
--to=mhw@netris.org \
--cc=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).