public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: DRC <dcommander@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] VirtualGL 2.6.3
Date: Thu, 25 Jun 2020 23:31:54 -0500	[thread overview]
Message-ID: <30033bda-2c7a-d634-08af-fe1de0ea9e1a@users.sourceforge.net> (raw)
In-Reply-To: <33ba7362-dfb3-f88a-39c6-7aa4921d9750@SystematicSw.ab.ca>

For whatever reason, Jon's "Done" message did not reach me, so I
apologize for my confusion.  It works now.  Creating the ~/.cygport.conf
file was the missing piece of the puzzle.

On 6/25/20 10:11 PM, Brian Inglis wrote:
> 
> On 2020-06-25 16:11, Jon Turney wrote:
>> On 25/06/2020 23:07, DRC via Cygwin-apps wrote:
>>> When can I expect to get SSH access in order to deploy my packages?
> 
>> 'Done' means it should be working now.
>> If it's not, you'll need to be a bit more explicit about the problem you are 
>> having.
> 
> Don't forget to first set up the remote host key with:
> 
> 	$ sftp cygwin@cygwin.com
> 
> You can of course first use ssh-agent and ssh-add to preset your private key.
> 
> Using e.g.
> 
> 	$ cygport virtualgl.cygport upload
> 
> is pretty foolproof and reliable if you set ~/.cygport.conf:
> 
> 	SSH_KEY=~/.ssh/id_...
> 
> to your private key file.

      reply	other threads:[~2020-06-26  4:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 20:53 DRC
2020-06-13  7:11 ` Marco Atzeri
2020-06-16  3:11   ` DRC
2020-06-16 14:45     ` Jon Turney
2020-06-16 14:55       ` Jon Turney
2020-06-18  0:05       ` DRC
2020-06-18  5:42         ` Marco Atzeri
2020-06-24  3:40           ` DRC
2020-06-24 21:21             ` Jon Turney
2020-06-25 22:07             ` DRC
2020-06-25 22:11               ` Jon Turney
2020-06-26  3:11                 ` Brian Inglis
2020-06-26  4:31                   ` DRC [this message]

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=30033bda-2c7a-d634-08af-fe1de0ea9e1a@users.sourceforge.net \
    --to=dcommander@users.sourceforge.net \
    --cc=cygwin-apps@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).