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