On Jul 29 18:32, David Rothenberger wrote:
wget -x -nH --cut-dirs=2 \
http://mysite.verizon.net/res00a7j/cygwin/libao/libao-0.8.8-1-src.tar.bz2 \
http://mysite.verizon.net/res00a7j/cygwin/libao/libao-0.8.8-1.tar.bz2 \
http://mysite.verizon.net/res00a7j/cygwin/libao/setup.hint \
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Steffen Sledz on 7/29/2007 11:21 AM:
Cygport README mentioned GPG .sig files for all the files used to build
up a package. As I could see, the prep stage checks these. But they are
not made part to the final source package in package
Kovarththanan Rajaratnam wrote:
Hello Bill,
Bill Hoffman wrote:
Bill Hoffman wrote:
I had some trouble myself when I tested the install. I had to
unpack the tar file by hand. I must have messed something up. Any
ideas what? Once unpacked by hand the cmake install was fine. -Bill
I
On Mon, 30 Jul 2007, Corinna Vinschen wrote:
On Jul 29 18:32, David Rothenberger wrote:
wget -x -nH --cut-dirs=2 \
http://mysite.verizon.net/res00a7j/cygwin/libao/libao-0.8.8-1-src.tar.bz2
\
http://mysite.verizon.net/res00a7j/cygwin/libao/libao-0.8.8-1.tar.bz2 \
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Christopher Faylor
Sent: Friday, July 27, 2007 6:29 PM
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH] - setup.exe --mirror-list option (nudge, nudge)
On Fri, Jul 27, 2007 at 11:49:39AM -0400, Hicks,
Bill Hoffman wrote:
OK, I am lost here. Apparently my recent CMake 2.4.7 files are broken
for cygwin setup for some reason. Has anything changed in cygwin setup
recently in the untar section? Is there a more verbose mode that setup
can be run in?
No, nothing's changed in the untar code
Brian Dessent wrote:
Bill Hoffman wrote:
OK, I am lost here. Apparently my recent CMake 2.4.7 files are broken
for cygwin setup for some reason. Has anything changed in cygwin setup
recently in the untar section? Is there a more verbose mode that setup
can be run in?
No,
Brian Dessent wrote:
No, nothing's changed in the untar code in forever. I debugged it and
the problem is that setup does not recognise the file as a valid tar
archive. What version of tar did you use to create it?
The problem is the 'magic' field of the tar header (offset 257). Setup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The new flac packages are ready.
Upstream incorporated the libOggFLAC and libOggFLAC++ libraries
into the main libFLAC and libFLAC++ libraries, so there are no new
libOggFLAC and libOggFLAC++ packages.
wget -x -nH --cut-dirs=2 \
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The new libogg package is ready.
wget -x -nH --cut-dirs=2 \
http://mysite.verizon.net/res00a7j/cygwin/libogg/libogg-1.1.3-1-src.tar.bz2 \
http://mysite.verizon.net/res00a7j/cygwin/libogg/libogg-1.1.3-1.tar.bz2 \
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The new vorbis-tools package is ready.
wget -x -nH --cut-dirs=2 \
http://mysite.verizon.net/res00a7j/cygwin/vorbis-tools/vorbis-tools-1.1.1-6-src.tar.bz2
\
http://mysite.verizon.net/res00a7j/cygwin/vorbis-tools/vorbis-tools-1.1.1-6.tar.bz2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The new speex packages are ready.
wget -x -nH --cut-dirs=2 \
http://mysite.verizon.net/res00a7j/cygwin/speex/speex-1.1.12-1-src.tar.bz2 \
http://mysite.verizon.net/res00a7j/cygwin/speex/speex-1.1.12-1.tar.bz2 \
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The new libvorbis packages are ready.
wget -x -nH --cut-dirs=2 \
http://mysite.verizon.net/res00a7j/cygwin/libvorbis/libvorbis-1.2.0-1-src.tar.bz2
\
http://mysite.verizon.net/res00a7j/cygwin/libvorbis/libvorbis-1.2.0-1.tar.bz2
\
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake schrieb:
If you set SIG in your environment (to anything, although 'export SIG=1'
seems simplest), then cygport will automatically prompt for creation of,
and distribute, .sig files as part of the package phase...
OK, I'll try that.
OK, I have figured out what happened. CMake 2.4.7-1 was the first release
of cmake done with cpack for cygwin. It was not generating gnu style
tar files.
I have changed that, so it should work with setup now.
Corinna, can you please upload:
Bill Hoffman wrote:
So, that explains why the tar file works, it is just not a gnu tar file.
Something must have changed in my code because the 2.4.6 version
has the gnu style header and the 2.4.7 version has the other header.
I will try and figure out what changed and create a new release.
Brian Dessent wrote:
Bill Hoffman wrote:
So, that explains why the tar file works, it is just not a gnu tar file.
Something must have changed in my code because the 2.4.6 version
has the gnu style header and the 2.4.7 version has the other header.
I will try and figure out what changed and
Bill Hoffman wrote:
Of course this won't take effect until the next setup release (unless
you use a snapshot) so bumping the cmake packages is still a good idea.
( http://cygwin.com/setup/snapshots/setup-2.577.exe )
Sounds good, thanks again for the help. I never would have figured
this
18 matches
Mail list logo