public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Upload fails with "connection closed"
Date: Fri, 27 Feb 2015 08:47:00 -0000	[thread overview]
Message-ID: <20150227084724.GA24860@calimero.vinschen.de> (raw)
In-Reply-To: <20150226103810.GB1911@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]

Hi Federico,

On Feb 26 11:38, Corinna Vinschen wrote:
> On Feb 26 00:44, Federico Hernandez wrote:
> > Here it comes...
> > 
> > put task-2.4.1-1.tar.xz
> > Uploading task-2.4.1-1.tar.xz to /x86_64/release/task-2.4.1-1.tar.xz
> > task-2.4.1-1.tar.xz
> >                                                      0%    0
> > 0.0KB/s   --:-- ETAdebug1: client_input_channel_req: channel 0 rtype
> > exit-status reply 0
> > debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
> > debug2: channel 0: rcvd eow
>                      ^^^^^^^^
> 		     Means: Write Failed
> 
> I can reproduce this.  I tried to upload to my staging dir as well as to
> your staging dir.  I can't upload normally either.  Given the latest
> uploads, it was no problem two days ago at least.
> 
> This only affects the Cygwin package upload, which uses a perl module
> NET::SFTP::SftpServer.  If I use a "normal" sftp server, uploading
> works.
> 
> The directory permissions are looking perfectly normal, too.  I can
> upload short files but nothing bigger than about 12K.
> 
> In the meantime I set up the same perl stuff on my local machine and
> even there I can reproduce this problem.  I'm trying to debug this, but
> I'm not a perl wizard at all.
> 
> Is somebody available for help?  Via IRC, perhaps (freenode
> #cygwin-developers)?

I haven't fond a solution to this problem yet.  Given that most people
don't seem to be affected, it might have something to do with a setting
on the client side, bot for the life of me I can figure out what the
difference might be.

For the time being, can you just provide URLs to the 32 and 64 bit
packages and we'll upload them using other means.


Sorry,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-02-27  8:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 21:58 Federico Hernandez
2015-02-25  8:41 ` Corinna Vinschen
2015-02-25 23:44   ` Federico Hernandez
2015-02-26 10:38     ` Corinna Vinschen
2015-02-27  8:47       ` Corinna Vinschen [this message]
2015-02-27 11:59         ` Federico Hernandez
2015-02-28  7:26           ` Marco Atzeri
2015-02-28 13:40             ` Federico Hernandez
2015-02-28 14:04               ` Corinna Vinschen
2015-02-28 14:55                 ` Corinna Vinschen

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=20150227084724.GA24860@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).