public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: SSH key for John Zaitseff
Date: Wed, 04 Dec 2019 04:50:00 -0000	[thread overview]
Message-ID: <3bd3f95b-462f-c810-091a-0b7324d311f4@SystematicSw.ab.ca> (raw)
In-Reply-To: <8ca2c35b-eada-c3c9-0b39-afafaf8b56e4@dronecode.org.uk>

On 2019-12-03 16:52, Jon Turney wrote:
> On 03/12/2019 21:14, John Zaitseff wrote:
>>>> Name: John Zaitseff
>>>> Package: trader

>> Thank you.  When I use sftp to connect to
>> cygwin-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org (as per
>> the instructions at https://cygwin.com/package-upload.html), I do
>> not see the file "!packages".  Consequently, when I try to upload my
>> trader package, as soon as I try to copy across any tar file, the
>> connection is closed.  Is the missing "!packages" file an oversight,
>> or am I simply being too eager and the file will be created in due
>> course? :-)

> Furthermore, the restriction is not applied to the filenames you can upload, but
> to the processing we do on them after the sftp session has closed, so I think
> something else must be the cause of your connection being closed.

I also had problems with sftp, but none with lftp, or cygport <pkg> upload:
the last should be considered preferred nowadays, as it handles ssh auth, lftp
transfer, and setting flag files, and may be updated to accommodate any calm
requirements change.

Make life easier with appropriate settings in ~/.cygport.conf:

	SSH_KEY=...	# for upload
	DISTDIR=...	# for download
	SMTP_...=...	# for announce

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

  reply	other threads:[~2019-12-04  4:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-01 20:52 John Zaitseff
2019-12-03 20:49 ` Jon Turney
2019-12-03 21:14   ` John Zaitseff
2019-12-03 23:52     ` Jon Turney
2019-12-04  4:50       ` Brian Inglis [this message]
2019-12-04  5:49         ` John Zaitseff

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=3bd3f95b-462f-c810-091a-0b7324d311f4@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).