From: Steve Bangert <sbangert@mindspring.com>
To: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: make rpm broken in 2.6.8-rc2
Date: Tue, 20 Jul 2004 12:09:34 -0700 [thread overview]
Message-ID: <40FD6DEE.4050208@mindspring.com> (raw)
In-Reply-To: <20040719223148.GA9796@mars.ravnborg.org>
sam@ravnborg.org wrote:
>>>>+ cd /usr/src/redhat/BUILD
>>>>+ rm -rf kernel-2.6.8rc1
>>>>+ /usr/bin/gzip -dc /usr/src/kernel-2.6.8rc1.tar.gz
>>>>+ tar -xf -
>>>>
>>>>gzip: /usr/src/kernel-2.6.8rc1.tar.gz: unexpected end of file
>>>>tar: Unexpected EOF in archive
>>>>tar: Unexpected EOF in archive
>>>>
>>>>
>>>>
>>>>
>>>tar is complaining here, even though it is reading from '-'.
>>>Is it repeatable?
>>>
>>>
>>>
>>>
>>Yes, tried it 3 times, same result. I don,t think the "make spec"
>>script is being executed.
>>
>>
>
>Could you try running
>/bin/gzip -dc /home/sam/bk/kernel-2.6.8rc2.tar.gz | tar -xf -
>in an empty directory.
>
>
Works fine
>If that fails try:
>/bin/gzip -dc /home/sam/bk/kernel-2.6.8rc2.tar.gz
>eventually redirected to /dev/null
>
>
>Also try to check the size of the .tar.gz file.
>My tar.gz file:
> $ ll /home/sam/bk/kernel-2.6.8rc2.tar.gz
> -rw-r--r-- 1 sam users 153725342 Jul 20 00:17 /home/sam/bk/kernel-2.6.8rc2.tar.gz
>
>
It was corrupted and the cause of the error, notice that tar was
complaining about 2.6.8-rc1,
but I was building 2.6.8-rc2, thats because the kernel.spec file didn't
get updated, the " make spec"
script didn't get executed after I built 2.6.8-rc1, It will execute if I
delete the kernel.spec file and I
can successfully build the kernel with "make rpm"
Steve
>
>If the .tar.gz file is broken try uncomenting the rm from the Makefile
>and execute rpmbuild manually.
>
> Sam
>
>
>
prev parent reply other threads:[~2004-07-20 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 10:43 make rpm broken in 2.6.8-rc2 Steve Bangert
2004-07-19 15:22 ` sam
2004-07-19 18:41 ` Steve Bangert
2004-07-19 22:31 ` sam
2004-07-20 19:09 ` Steve Bangert [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=40FD6DEE.4050208@mindspring.com \
--to=sbangert@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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