From: Ken Brown <kbrown@cornell.edu>
To: cygwin-announce <cygwin-announce@cygwin.com>
Subject: harfbuzz 2.9.0-2
Date: Tue, 19 Oct 2021 16:04:46 -0400 [thread overview]
Message-ID: <8640328f-cf70-9db5-984f-fe7ce8f4ce3f@cornell.edu> (raw)
The following packages have been uploaded to the Cygwin distribution:
* harfbuzz-2.9.0-2
* libharfbuzz0-2.9.0-2
* libharfbuzz-devel-2.9.0-2
* libharfbuzz-gobject0-2.9.0-2
* libharfbuzz-gobject-devel-2.9.0-2
* libharfbuzz-subset0-2.9.0-2
* libharfbuzz-subset-devel-2.9.0-2
* libharfbuzz-icu0-2.9.0-2
* libharfbuzz-icu-devel-2.9.0-2
* girepository-HarfBuzz0.0-2.9.0-2
HarfBuzz is an OpenType text shaping engine.
This is a rebuild of the 2.9.0-1 packages, without the circular
dependency between harfbuzz and freetype2 that was introduced in
2.9.0-1. That circular dependency apparently caused the fork problems
reported here:
https://cygwin.com/pipermail/cygwin/2021-October/249610.html
Ken Brown
Cygwin's harfbuzz maintainer
reply other threads:[~2021-10-19 20:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8640328f-cf70-9db5-984f-fe7ce8f4ce3f@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-announce@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).