From: Steffen Sledz <sledz@zone42.org>
To: cygwin-apps@cygwin.com
Subject: Re: cygport/rsync problem
Date: Wed, 29 Oct 2008 13:55:00 -0000 [thread overview]
Message-ID: <49086B40.10608@zone42.org> (raw)
In-Reply-To: <4904659A.4060800@zone42.org>
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. :(
next prev parent reply other threads:[~2008-10-29 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 12:43 Steffen Sledz
2008-10-29 13:55 ` Steffen Sledz [this message]
2008-12-19 23:48 ` Christopher Faylor
2008-12-21 0:35 ` Yaakov (Cygwin/X)
2009-01-18 18:11 ` Steffen Sledz
2009-01-18 18:25 ` Yaakov (Cygwin/X)
2009-01-18 18:39 ` Ken Brown
2009-01-19 9:46 ` Steffen Sledz
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=49086B40.10608@zone42.org \
--to=sledz@zone42.org \
--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).