Re: Apple switched to BSDtar from GNUtar with Leopard

A little research shows that Apple modified tGNUtar o be resource fork
aware and, I guess, did the same with BSDtar! Maybe this points to the
problem. Certainly there is nothing wrong with the tar files on the
site!

curl http://www.postgresql.org/ftp/source/v8.4.1/
postgresql-8.4.1.tar.gz -O
% Total % Received % Xferd Average Speed Time Time
Time Current
Dload Upload Total Spent
Left Speed
119 239 119 239 0 0 716 0 --:--:-- --:--:--
--:--:-- 1448

gnutar -zvxf postgresql-8.4.1.tar.gz
gzip: stdin: not in gzip format
gnutar: Child returned status 1
gnutar: Error exit delayed from previous errors

bsdtar -zvxf postgresql-8.4.1.tar.gz
bsdtar: Unrecognized archive format: Inappropriate file type or format
bsdtar: Error exit delayed from previous errors.

I'm not sure what to do if I need a fresh copy of the src. ?
Fortunatly I did get an tar file from SourceForge, about a week ago,
that seems to behave normally.

Don

On Sat, Oct 31, 2009 at 2:44 PM, Don Fox <donfox1(at)mac(dot)com> wrote:
>
> A little research shows that Apple modified tGNUtar o be resource fork aware
> and, I guess, did the same with BSDtar! Maybe this points to the problem.
> Certainly there is nothing wrong with the tar files on the site!

You sure? FWIW, I get the same thing on my Linux dev box:

hassan(at)ceylon:/tmp> tar tvfz postgresql-8.4.1.tar.gz

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error exit delayed from previous errors
hassan(at)ceylon:/tmp> uname -a
Linux ceylon 2.6.13-15.15-smp #1 SMP Mon Feb 26 14:11:33 UTC 2007
x86_64 x86_64 x86_64 GNU/Linux
hassan(at)ceylon:/tmp>

--
Hassan Schroeder ------------------------ hassan(dot)schroeder(at)gmail(dot)com
twitter: @hassan

I was able to un-tar readline without any hitch.

tar -xf readline-6.0.tar
c-76-123-226-197:src donfox1$ ls
postgresql-8.4.1.tar.bz2 readline-6.0 readline-6.0.tar

On Oct 31, 2009, at 6:06 PM, Hassan Schroeder wrote:

> On Sat, Oct 31, 2009 at 2:44 PM, Don Fox <donfox1(at)mac(dot)com> wrote:
>>
>> A little research shows that Apple modified tGNUtar o be resource
>> fork aware
>> and, I guess, did the same with BSDtar! Maybe this points to the
>> problem.
>> Certainly there is nothing wrong with the tar files on the site!
>
> You sure? FWIW, I get the same thing on my Linux dev box:
>
> hassan(at)ceylon:/tmp> tar tvfz postgresql-8.4.1.tar.gz
>
> gzip: stdin: not in gzip format
> tar: Child returned status 1
> tar: Error exit delayed from previous errors
> hassan(at)ceylon:/tmp> uname -a
> Linux ceylon 2.6.13-15.15-smp #1 SMP Mon Feb 26 14:11:33 UTC 2007
> x86_64 x86_64 x86_64 GNU/Linux
> hassan(at)ceylon:/tmp>
>
> --
> Hassan Schroeder ------------------------ hassan(dot)schroeder(at)gmail(dot)com
> twitter: @hassan
>
> --
> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-novice

On Sat, Oct 31, 2009 at 3:22 PM, Don Fox <donfox1(at)mac(dot)com> wrote:
> I was able to un-tar readline without any hitch.
> tar -xf readline-6.0.tar

Not sure what readline has to do with the original question
, but

> hassan(at)ceylon:/tmp> tar tvfz postgresql-8.4.1.tar.gz

for that file at least, the md5 checksum is not what's listed:

MD5 (postgresql-8.4.1.tar.gz) = efb12995609aaba2ee5d43b03be161c6
(pulled from a US mirror)

hassan(at)ceylon:/tmp> md5sum postgresql-8.4.1.tar.gz
3546300baee928ce0f254aafdfa6a1dc postgresql-8.4.1.tar.gz
hassan(at)ceylon:/tmp>

Seems like something's not right there :-)
--
Hassan Schroeder ------------------------ hassan(dot)schroeder(at)gmail(dot)com
twitter: @hassan

Just that I was able to use my tar on a 'normal' tared up set of
files, i.e. maybe something is odd about the postgresql-8.4.1.tar.gz

Don

On Oct 31, 2009, at 6:37 PM, Hassan Schroeder wrote:

> On Sat, Oct 31, 2009 at 3:22 PM, Don Fox <donfox1(at)mac(dot)com> wrote:
>> I was able to un-tar readline without any hitch.
>> tar -xf readline-6.0.tar
>
> Not sure what readline has to do with the original question
> , but
>
>> hassan(at)ceylon:/tmp> tar tvfz postgresql-8.4.1.tar.gz
>
> for that file at least, the md5 checksum is not what's listed:
>
> MD5 (postgresql-8.4.1.tar.gz) = efb12995609aaba2ee5d43b03be161c6
> (pulled from a US mirror)
>
> hassan(at)ceylon:/tmp> md5sum postgresql-8.4.1.tar.gz
> 3546300baee928ce0f254aafdfa6a1dc postgresql-8.4.1.tar.gz
> hassan(at)ceylon:/tmp>
>
> Seems like something's not right there :-)
> --
> Hassan Schroeder ------------------------ hassan(dot)schroeder(at)gmail(dot)com
> twitter: @hassan

On Sat, Oct 31, 2009 at 3:42 PM, Don Fox <donfox1(at)mac(dot)com> wrote:
> Just that I was able to use my tar on a 'normal'  tared up set of files,
> i.e. maybe something is odd about the postgresql-8.4.1.tar.gz

I'd say no "maybe" about it, if the checksum doesn't match -- after
all, that's why one's provided: to confirm the file is uncorrupted :-)

--
Hassan Schroeder ------------------------ hassan(dot)schroeder(at)gmail(dot)com
twitter: @hassan

Hassan Schroeder <hassan(dot)schroeder(at)gmail(dot)com> writes:
>> hassan(at)ceylon:/tmp> tar tvfz postgresql-8.4.1.tar.gz
> for that file at least, the md5 checksum is not what's listed:
> MD5 (postgresql-8.4.1.tar.gz) = efb12995609aaba2ee5d43b03be161c6
> (pulled from a US mirror)

So, which mirror has got the bad copy? I tried pulling it down
yesterday, and got a good copy, but that only proves there's at
least one US mirror with a good copy ...

regards, tom lane

Hassan Schroeder <hassan(dot)schroeder(at)gmail(dot)com> writes:
> However, retrieving it from several different mirrors gives me the
> same checksum, which doesn't match the file retrieved from this
> <http://www.postgresql.org/ftp/source/v8.4.1/postgresql-8.4.1.tar.gz>
> location.

There is no such location... if you look closer you'll see what you
have is a 404 Not Found response, which Safari has helpfully wrapped
up into a .gz file :-(

regards, tom lane

2009/11/1 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Hassan Schroeder <hassan(dot)schroeder(at)gmail(dot)com> writes:
>> However, retrieving it from several different mirrors gives me the
>> same checksum, which doesn't match the file retrieved from this
>> <http://www.postgresql.org/ftp/source/v8.4.1/postgresql-8.4.1.tar.gz>
>> location.
>
> There is no such location... if you look closer you'll see what you
> have is a 404 Not Found response, which Safari has helpfully wrapped
> up into a .gz file :-(

Run "file postgresql-8.4.1.tar.gz" and it will likely say it is an HTML file.

$ curl -O http://www.postgresql.org/ftp/source/v8.4.1/postgresql-8.4.1.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 239 100 239 0 0 306 0 --:--:-- --:--:-- --:--:-- 0
$ file postgresql-8.4.1.tar.gz
postgresql-8.4.1.tar.gz: HTML document text

If you use curl's -f option, it makes more sense, though:

$ curl -f -O http://www.postgresql.org/ftp/source/v8.4.1/postgresql-8.4.1.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404

--
Michael Wood <esiotrot(at)gmail(dot)com>