From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: Mark H Weaver <mhw@netris.org>, Nikita <nikita@n0.is>,
Adrian Malacoda <malacoda@monarch-pass.net>,
Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Icedove package needs update, following IceCat 68.9.0 update.
Date: Wed, 3 Jun 2020 10:44:23 +0200 [thread overview]
Message-ID: <7405effd-e355-2da7-9947-6134362516c7@web.de> (raw)
In-Reply-To: <87d06hc51v.fsf@netris.org>
On 03.06.20 03:26, Mark H Weaver wrote:
> Earlier, I wrote:
>
>> I just pushed the IceCat-68.9.0 security update to the master branch of
>> Guix, along with a graft for NSS.
>>
>> However, I just noticed that we now have Icedove in Guix, and that it's
>> based on 'icecat-source'. This is all good and proper (kudos to all who
>> worked on it!), but unfortunately I didn't know about it until now, and
>> my IceCat update may have left Icedove in a bad state.
>
> Upon further thought, I think it's unlikely that Icedove was adversely
> affected by the IceCat update. Updates to the ESR branch are generally
> limited to bug fixes and blocklist updates. Also, I see that
> Thunderbird 68.9.0 has not yet been released, so maybe there's nothing
> to do at present.
There is a Thunderbird 68.8.1 with only 3 patches. None of them seems to
be security relevant. I'm working on the update. My laptop just needs
some time to built that stuff...
next prev parent reply other threads:[~2020-06-03 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 18:19 Icedove package needs update, following IceCat 68.9.0 update Mark H Weaver
2020-06-03 1:26 ` Mark H Weaver
2020-06-03 8:44 ` Jonathan Brielmaier [this message]
2020-06-04 7:08 ` Jonathan Brielmaier
2020-06-06 9:53 ` Jonathan Brielmaier
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=7405effd-e355-2da7-9947-6134362516c7@web.de \
--to=jonathan.brielmaier@web.de \
--cc=guix-devel@gnu.org \
--cc=malacoda@monarch-pass.net \
--cc=mhw@netris.org \
--cc=nikita@n0.is \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).