Re: cygport/rsync problem

[Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>]

On Wed, Oct 29, 2008 at 02:55:12PM +0100, Steffen Sledz wrote:
>Steffen Sledz wrote:
>> Now that gcc4 is available in release-2 i wanted to make a new try in
>> building emacs there, but i failed in the first step. :(
>> 
>> $ cygport emacs-22.3-1.cygport prep
>>>>> Preparing emacs-22.3-1
>> *** Info: SOURCE 1 signature follows:
>> gpg: WARNING: using insecure memory!
>> gpg: please see http://www.gnupg.org/faq.html for more information
>> gpg: Signature made Fri Sep  5 18:34:56 2008 WEST using DSA key ID BC40251C
>> gpg: Can't check signature: public key not found
>>>>> Unpacking source emacs-22.3.tar.gz
>>>>> Preparing working source directory
>> rsync: Failed to dup/close: Socket operation on non-socket (108)
>> rsync error: error in IPC code (code 14) at /home/lapo/packaging/rsync-3.0.4-1/src/rsync-3.0.4/pipe.c(147) [receiver=3.0.4]
>> rsync: read error: Connection reset by peer (104)
>> rsync error: error in IPC code (code 14) at /home/lapo/packaging/rsync-3.0.4-1/src/rsync-3.0.4/io.c(791) [sender=3.0.4]
>> 
>> Any idea what went wrong here?
>> 
>> $ cygcheck -c cygport
>> Cygwin Package Information
>> Package              Version        Status
>> cygport              0.9.2-1        OK
>> $ cygcheck -c rsync  Cygwin Package Information
>> Package              Version        Status
>> rsync                3.0.4-1        OK
>
>
>The problem still remains with cygport-0.9.3.  :(

Since no one else is apparently having this type of problem, I'm not
sure how to proceed.

We have people in the cygwin list who are complaining about emacs
now and we need to start moving on getting support.

Why is cygport running rsync and why isn't anyone else seeing this
problem?

cgf