From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: libfreetype CVE FYI
Date: Wed, 21 Oct 2020 17:20:24 -0400 [thread overview]
Message-ID: <5a53014f-1c97-0081-7b8f-e5a8d927912a@cornell.edu> (raw)
In-Reply-To: <87mu0fmryr.fsf@Rainer.invalid>
On 10/21/2020 1:03 PM, Achim Gratz wrote:
> Ken Brown via Cygwin-apps writes:
>>> https://sourceforge.net/projects/freetype/files/freetype2/2.10.4/
>>
>> Thanks, Brian. I'll update it.
>
> Did you intend to release this security / minor version update as a test
> release? It would seem more prudent to just update the package or do
> you expect problems?
I did that because Fedora is still on 2.10.2, and I generally try to avoid
getting ahead of Fedora on package releases. That's because (a) the Fedora
maintainers are more knowledgeable than I am about many of the packages that I
maintain, and (b) the update will get much more testing once Fedora releases it.
That said, I agree that a security update should get high priority. So I'll
wait a few more days for Fedora, and then I'll go ahead and promote the test
release to "current", regardless of what Fedora does.
Ken
prev parent reply other threads:[~2020-10-21 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 16:50 [ITA from Yaakov] freeport2 Ken Brown
2020-05-12 16:53 ` Ken Brown
2020-05-12 18:08 ` Marco Atzeri
2020-05-12 18:34 ` Ken Brown
2020-05-12 19:00 ` Marco Atzeri
2020-05-12 18:02 ` [ITA from Yaakov] freetype2 Yaakov Selkowitz
2020-05-12 18:46 ` Ken Brown
2020-10-20 14:46 ` libfreetype CVE FYI Brian Inglis
2020-10-20 18:00 ` Ken Brown
2020-10-21 17:03 ` Achim Gratz
2020-10-21 21:20 ` Ken Brown [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a53014f-1c97-0081-7b8f-e5a8d927912a@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/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).