cygport/rsync problem

cygport/rsync problem

[Steffen Sledz]

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

Regards,
Steffen

Re: cygport/rsync problem

[Steffen Sledz]

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.  :(

Re: cygport/rsync problem

[Christopher Faylor]

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

Re: cygport/rsync problem

[Yaakov (Cygwin/X)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
> Why is cygport running rsync and why isn't anyone else seeing this
> problem?

Starting with 0.3.13 (released August '08), cygport uses rsync during
the prep stage to copy the sources from origsrc/ to src/.  I switched to
rsync to workaround a number of issues that cropped up with using cp.
I've built hundreds of packages since then without problems, and AFAIK
nobody else has had any problems with this either.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAklNjysACgkQpiWmPGlmQSPNEwCg/fCXpgHbTPKQOqEPMGfk/ddk
uqQAoJgZnDSAkqaHehkwn+/Epg0/S/48
=0QhM
-----END PGP SIGNATURE-----

Re: cygport/rsync problem

[Steffen Sledz]

The problem is still existing:

$ 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: Good signature from "Chong Yidong <cyd@stupidchicken.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: AF1A 0574 841E 0F2D EDE2  829A 764D A716 BC40 251C
>>> 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]

$ cygcheck -c cygport
Cygwin Package Information
Package              Version        Status
cygport              0.9.4-1        OK

$ cygcheck -c rsync  
Cygwin Package Information
Package              Version        Status
rsync                3.0.4-1        OK

Is there anything i can do to help finding the problem? Does cygport have some debugging support?

Steffen

Re: cygport/rsync problem

[Yaakov (Cygwin/X)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Steffen Sledz wrote:
> The problem is still existing:
> 
> $ 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: Good signature from "Chong Yidong
> <cyd-iS+aIwYd2teDXAOJFZ9NEwC/G2K4zDHf@public.gmane.org>"
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:          There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: AF1A 0574 841E 0F2D EDE2  829A 764D A716 BC40 251C
>>>> 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]
> 
> $ cygcheck -c cygport
> Cygwin Package Information
> Package              Version        Status
> cygport              0.9.4-1        OK
> 
> $ cygcheck -c rsync  Cygwin Package Information
> Package              Version        Status
> rsync                3.0.4-1        OK
> 
> Is there anything i can do to help finding the problem? Does cygport
> have some debugging support?

1) This is not the correct list for this issue.
2) If you're having a problem with rsync, it has nothing to do with cygport.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAklzdCAACgkQpiWmPGlmQSN3VgCfd5FHYcVB2I5Y6MVSzl7k8Jlf
m24AnAqGjV2ykPlH9nHRQxDch1YeU/mY
=8Z8X
-----END PGP SIGNATURE-----

Re: cygport/rsync problem

[Ken Brown]

On 1/18/2009 1:11 PM, Steffen Sledz wrote:
> The problem is still existing:

You received a reply on the main cygwin mailing list to your first 
message about this problem:

    http://cygwin.com/ml/cygwin/2008-10/msg00524.html

By the way, do you subscribe to that list?  There was quite a bit of 
emacs discussion in December.

Ken

Re: cygport/rsync problem

[Steffen Sledz]

Ken Brown schrieb:
> You received a reply on the main cygwin mailing list to your first
> message about this problem:
> 
>    http://cygwin.com/ml/cygwin/2008-10/msg00524.html
> 
> By the way, do you subscribe to that list?  There was quite a bit of
> emacs discussion in December.

Sorry, i didn't subscribe to that list. But i'll have a look into the archive. Thanx for the hint.

Steffen