public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Hansen <meh@winfirst.com>
To: cygwin@cygwin.com
Subject: Re: After installing nc (netcat), nc.exe is not found
Date: Wed, 11 Jul 2018 19:46:00 -0000	[thread overview]
Message-ID: <990023c0-3b3f-abff-26d3-f255c5f328a2@winfirst.com> (raw)
Message-ID: <20180711194600.-ZWzFi9Br6VGDmbRuPaS_wBG-8JrFvqAYk0UPsqm07o@z> (raw)
In-Reply-To: <7aa60e78-2d1a-88f6-273a-0294c3e71b12@avenger.ws>

On 7/11/2018 10:34 AM, Heavenly Avenger wrote:
> I have these versions, and nc is here happy and playful.
> 
> It is possible you attempted an upgrade while cygwin programs were
> running? Cygwin services also count. This is due a limitation on windows
> which locks files when they are in use, so cygwin updates can't replace
> the files and end up failing.
> 
> You may ensure everything is closed and services stopped, re-run
> setup-x86_64.exe, selecting the 'nc' package and switching it to
> "Reinstall". Then let the setup do its things.
> 
> If the setup is hanging, or have hung up and you had to force-close it
> the last install attempt you did, this is a strong sign that not just
> nc, but several other packages that have been attempted to upgrade may
> be compromised. To ensure that is not the case, a good
> 
> cygcheck -c
> 
> should help.
> 
> The package nc-1.10-4.tar.bz2 has 'usr/bin/nc.exe', which is the file
> you claim missing.
> 
> Hope this helps! :)
> 

Thanks for your help. I have notes that show what all I need to shut down when doing the
install. I caught all them (Cygwin SSHD, Cygwin cygserver, the X Server, and anything running
cygwin shells, etc.) - I think that's everything.

When I run cygcheck -c, it shows Incomplete on the two packages (nc and nc6) so they definitely
had problems, and appear to be the only ones which did.

I see that the .bz2 file is in my downloads area (I download to local without install, and then
install from local).

I tried running bunzip2 on that file and then extracting it using tar. The bunzip2 completed
quickly but the tar command took a long time (I'm not sure what it was doing during this time).

I'll try shutting everything down and doing a reinstall on the netcat stuff.

Thanks,

> 
> On 7/11/2018 2:10 PM, Mark Hansen wrote:
>> I've just updated to the latest Cygwin 64-bit installation on my 
>> Windows 7 PC. Included
>> in this update was the package for nc (nc: A simple but powerful 
>> network tool) version 1.107-4
>>
>> After downloading and installing, which all seemed to go fine, the man 
>> page for nc is there,
>> but nc.exe is not.
>>
>> I included the following (netcat-related) packages:
>> - nc, 1.107-4
>> - nc6, 1.0-1
>> - nc6-debuginfo, 1.0-1
>>
>> Is there something special I need to do to get nc.exe installed?
>>
>> Thanks,
>>
>>
>> -- 
>> 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
>>
>>
> 
> 



--
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-07-11 19:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 17:10 Mark Hansen
2018-07-11 17:35 ` Heavenly Avenger
2018-07-11 19:34   ` Mark Hansen [this message]
2018-07-11 19:46     ` Mark Hansen
2018-07-11 19:50     ` Mark Hansen
2018-07-11 20:00       ` Mark Hansen
2018-07-12  2:37       ` Heavenly Avenger
2018-07-11 20:10 ` Andrey Repin
2018-07-11 20:10   ` Gary Johnson
2018-07-11 20:35   ` Mark Hansen
2018-07-12  1:30     ` Mark Hansen
2018-07-12  3:36     ` Gary Johnson
2018-07-12  7:46     ` Brian Inglis
2018-07-12 13:38       ` Christian Franke
2018-07-12  9:14     ` Erik Soderquist

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=990023c0-3b3f-abff-26d3-f255c5f328a2@winfirst.com \
    --to=meh@winfirst.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).