From: Fernando Nasser <fnasser@cygnus.com>
To: Mário Videira <mvideira@av.it.pt>
Cc: insight@sourceware.cygnus.com
Subject: Re: Help!!!!!!!!!!!!!!!!!!!!
Date: Wed, 22 Nov 2000 09:44:00 -0000 [thread overview]
Message-ID: <3A1C05DF.953966C6@cygnus.com> (raw)
In-Reply-To: <005e01c054a6$a207d320$c35c88c1@av.it.pt>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]
Mario,
Either your file transfer has ended prematurely or you were using ftp and
forgot to change the type to binary.
If you are doing this transfer on a Cygwin system you should also make your
mounts binary. I believe I once had a problem with this.
Anyway, your tar ball got corrupted in transit. You need to get another one.
Fernando
Mário Videira wrote:
>
> Hi, Everybody!
>
> I'm trying to build insight tool, but i'm unable to extract the file
> insght-5.0 that i have downloaded. After some extracted file, i got some
> error. The last extracted file was: insight-5.0/etc/standards.info .
>
> What i do is this:
> $bunzip2 < insight-5.0.tar.bz2 | tar xvf -
>
> This is the results:
> .
> .
> .
> insight-5.0 /etc/make-stds.kxi
> insight-5.0 /etc/standards.info
>
> bunzip2: compressed file ends unexpectedly
> perhaps it is corrupted? *possible *reason follows.
>
> bunzip2: error 0
> input file = <stdin>, out file = <stdout>
> It is possible that the compressed file(s) have become corrupted. You can
> use the -trv option to test integrity of such file.
>
> You can use the 'bzip2recover' program to *attempt* to recover data from
> undamaged sections of corrupted file.
>
> tar: Archive - EOF not on block boundary
> tar: Error is not recoverable : exiting now
>
> Please,
> can anybody help me to solve this problem.
>
> Best Regards
> Mário Videira
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
prev parent reply other threads:[~2000-11-22 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 9:10 Help!!!!!!!!!!!!!!!!!!!! Mário Videira
2000-11-22 9:44 ` Fernando Nasser [this message]
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=3A1C05DF.953966C6@cygnus.com \
--to=fnasser@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=mvideira@av.it.pt \
/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).