public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Robert Cohen <cohen@merl.com>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: setup 2.891release candidate - please test
Date: Thu, 22 Mar 2018 21:26:00 -0000	[thread overview]
Message-ID: <4c2cd12b-7678-dcfb-839f-22a6afc4b3da@dronecode.org.uk> (raw)
In-Reply-To: <6e7f1576c33d41d89b3a5689a5d57ca4@merl.com>

On 16/03/2018 21:52, Robert Cohen wrote:
> -----------------
> 
> Hi Jon,
> 
>   I tested setup-2.891.x86_64 with an install from local directory, and I got the same
> result as setup-2.889-12-g1cf567.x86_64.exe, where it installed the additional packages
> that I selected, but at the end it gave this message:
> 
> Package: _/libfontconfig-common
> 	fontconfig_dtd.sh exit code 2
> 
>   Do you think this may be because I'm installing from an already-downloaded directory and
> It may work ok if I repeat the download and install process using the new setup executable, or
> would another solution be needed for this, as alluded to in your earlier reply to this same error
> message?

Thanks for testing.

Yes, as I wrote in [1], this isn't more a missing feature and/or missing 
dependency information, than a bug in setup.

[1] https://cygwin.com/ml/cygwin/2018-03/msg00108.html

--
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

  reply	other threads:[~2018-03-22 21:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 23:41 Jon Turney
2018-03-16 22:13 ` Robert Cohen
2018-03-22 21:26   ` Jon Turney [this message]
2018-03-23  0:15     ` Robert Cohen
2018-03-17 17:14 ` Steven Penny
2018-03-18 19:36 ` Houder
2018-03-22 21:48   ` Jon Turney

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=4c2cd12b-7678-dcfb-839f-22a6afc4b3da@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cohen@merl.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).