public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Apache Fork Errors - Found on Windows Server 2019
Date: Tue, 19 Oct 2021 16:07:38 -0400	[thread overview]
Message-ID: <202040f2-1adf-eb9d-30c0-4d99f9ed25d9@cornell.edu> (raw)
In-Reply-To: <CAK0ZC5VyCiz1kq=4UQ_KPrq-AWiwur6dd1WtO-sUOpynGhd3Sg@mail.gmail.com>

On 10/18/2021 9:43 PM, OwN-3m-All via Cygwin wrote:
> I upgraded both libharfbuzz0 and libfreetype6 to the latest version again,
> and the issues are back.
> 
> I tested these previous versions for both, and they work:
> 
> libharfbuzz0 2.7.4-1 and 2.8.1-1 work
> libfreetype6 2.10.4-1 and 2.10.4-2 work
> 
> The latest versions of these libs need to be reverted or properly fixed.

The new packages (using the previous build method, with no circular dependency) 
are now available.  Please test.

Ken

  reply	other threads:[~2021-10-19 20:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15  3:38 OwN-3m-All
2021-10-15  5:05 ` Mark Geisert
2021-10-15 17:25   ` OwN-3m-All
2021-10-15 18:55 ` Achim Gratz
2021-10-15 19:12   ` OwN-3m-All
2021-10-15 19:35     ` OwN-3m-All
2021-10-15 20:04       ` OwN-3m-All
2021-10-15 20:25         ` Ken Brown
2021-10-17  1:49           ` OwN-3m-All
2021-10-17 15:54             ` Ken Brown
2021-10-17 16:40               ` Brian Inglis
2021-10-18 20:43               ` OwN-3m-All
2021-10-18 21:25                 ` Ken Brown
2021-10-19  1:43                   ` OwN-3m-All
2021-10-19 20:07                     ` Ken Brown [this message]
2021-10-20  3:22                       ` OwN-3m-All
2021-10-17  9:40 ` Andrey Repin

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=202040f2-1adf-eb9d-30c0-4d99f9ed25d9@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@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).