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

Search Discussions

  • Hassan Schroeder at Oct 31, 2009 at 10:06 pm

    On Sat, Oct 31, 2009 at 2:44 PM, Don Fox 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@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@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@ceylon:/tmp>

    --
    Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
    twitter: @hassan
  • Don Fox at Oct 31, 2009 at 10:22 pm
    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 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@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@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@ceylon:/tmp>

    --
    Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
    twitter: @hassan

    --
    Sent via pgsql-novice mailing list (pgsql-novice@postgresql.org)
    To make changes to your subscription:
    http://www.postgresql.org/mailpref/pgsql-novice
  • Hassan Schroeder at Oct 31, 2009 at 10:38 pm

    On Sat, Oct 31, 2009 at 3:22 PM, Don Fox 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@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@ceylon:/tmp> md5sum postgresql-8.4.1.tar.gz
    3546300baee928ce0f254aafdfa6a1dc postgresql-8.4.1.tar.gz
    hassan@ceylon:/tmp>

    Seems like something's not right there :-)
    --
    Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
    twitter: @hassan
  • Don Fox at Oct 31, 2009 at 10:42 pm
    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 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@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@ceylon:/tmp> md5sum postgresql-8.4.1.tar.gz
    3546300baee928ce0f254aafdfa6a1dc postgresql-8.4.1.tar.gz
    hassan@ceylon:/tmp>

    Seems like something's not right there :-)
    --
    Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
    twitter: @hassan
  • Hassan Schroeder at Oct 31, 2009 at 10:53 pm

    On Sat, Oct 31, 2009 at 3:42 PM, Don Fox 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.schroeder@gmail.com
    twitter: @hassan
  • Tom Lane at Nov 1, 2009 at 2:58 pm

    Hassan Schroeder writes:
    hassan@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
  • Tom Lane at Nov 1, 2009 at 3:37 pm

    Hassan Schroeder 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
  • Michael Wood at Nov 2, 2009 at 8:26 am

    2009/11/1 Tom Lane <tgl@sss.pgh.pa.us>:
    Hassan Schroeder <hassan.schroeder@gmail.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@gmail.com>

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppgsql-novice @
categoriespostgresql
postedOct 31, '09 at 9:45p
activeNov 2, '09 at 8:26a
posts9
users4
websitepostgresql.org
irc#postgresql

People

Translate

site design / logo © 2022 Grokbase