From: "Václav Haisman" <vhaisman@gmail.com>
To: cygwin@cygwin.com
Subject: Re: zp_fontconfig_cache_1.sh exit code 2
Date: Fri, 01 Jul 2016 08:24:00 -0000 [thread overview]
Message-ID: <CAKw7uVhdfBVWjja5TL7vUNAjLN2y=qTqavcn79pBSDEHgnyaOQ@mail.gmail.com> (raw)
In-Reply-To: <a547e565-440c-efc2-68ce-293cd31c75e6@cornell.edu>
On 13 June 2016 at 01:35, Ken Brown <kbrown@cornell.edu> wrote:
> On 6/12/2016 7:26 PM, Mark McGregor wrote:
>>
>> ----Ken wrote:
>>>
>>> I obtained the output in the attachment, which looks good. Are you saying
>>> that the message is bogus and no action is needed?
>>
>>
>> Yes.
>> ----
>>
>> Ok, thanks! It is nice to know than nothing is broken in this respect. But
>> it would be also nice to get less bogus messages.
>
>
> Agreed. I took a brief look at the fontconfig code at one point to see if I
> could figure out why this was happening, but I didn't succeed and didn't
> feel like spending a lot of time on it.
>
> Ken
I have recently experienced this as well. Some sources
(https://bugs.archlinux.org/task/6024 and
http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg266900.html)
suggest that it is some sort of time stamp related issue?
--
VH
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-07-01 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 23:36 Mark McGregor
2016-06-12 23:42 ` Ken Brown
2016-07-01 8:24 ` Václav Haisman [this message]
[not found] <1465768502.22005.ezmlm@cygwin.com>
2016-06-12 23:26 ` Mark McGregor
2016-06-12 23:35 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2016-06-12 22:32 Mark McGregor
2016-06-12 23:15 ` Ken Brown
2016-06-12 21:32 Mark McGregor
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='CAKw7uVhdfBVWjja5TL7vUNAjLN2y=qTqavcn79pBSDEHgnyaOQ@mail.gmail.com' \
--to=vhaisman@gmail.com \
--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).