public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Can't open x86/release/cvs/cvs-1.11.23-2.tar.gz for reading: Unknown filename
Date: Mon, 30 Apr 2018 20:15:00 -0000	[thread overview]
Message-ID: <13950cea-ffd4-6125-b1e0-05fed06760a8@cornell.edu> (raw)
In-Reply-To: <CAFWoy7FWzfLhVfjmyToyQcO43Bvi4_EaSrqkjFbjU-W+Ecc1-Q@mail.gmail.com>

On 4/30/2018 11:16 AM, Keith Christian wrote:
> More information:
> 
> Why is setup mentioning a .gz extension?
> 
> -rw-r--r-- 1 kchristian Domain Users 686572 Feb  9 06:52
> /cygdrive/c/Users/kchristian/Downloads/http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/release/cvs/cvs-1.11.23-2.tar.xz
> 
> Here are the relevant lines in setup.ini:
> 
> @ cvs
> sdesc: "Version control system"
> ldesc: "CVS is a version control system, an important component of Source
> Configuration Management (SCM). Using it, you can record the history of sources
> files, and documents."
> category: Devel
> requires: bash cygwin libcrypt0 libgssapi_krb5_2 libkrb5_3 perl_base zlib0
> replace-versions: 1.12.13-10
> version: 1.11.23-2
> install: x86/release/cvs/cvs-1.11.23-2.tar.xz 686572

Could you make /var/log/setup.log.full available somewhere?  It might 
contain some clues.

Ken


--
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-04-30 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 15:10 Keith Christian
2018-04-30 15:17 ` Keith Christian
2018-04-30 20:15   ` Ken Brown [this message]
2018-04-30 16:05 ` Marco Atzeri

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=13950cea-ffd4-6125-b1e0-05fed06760a8@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).