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: Mon, 19 Jul 2004 11:41:19 -0700 [thread overview]
Message-ID: <40FC15CF.9090001@mindspring.com> (raw)
In-Reply-To: <20040719152215.GA23344@mars.ravnborg.org>
sam@ravnborg.org wrote:
>Works for me..
>
>On Mon, Jul 19, 2004 at 03:43:30AM -0700, Steve Bangert wrote:
>
>
>>[root@localhost linux-2.6]# make rpm
>>make clean
>>set -e; cd ..; ln -sf /usr/src/linux-2.6 kernel-2.6.8rc2
>>set -e; cd ..; tar -cz -f kernel-2.6.8rc2.tar.gz kernel-2.6.8rc2/.
>>set -e; cd ..; rm kernel-2.6.8rc2
>>set -e; \
>>/bin/sh /usr/src/linux-2.6/scripts/mkversion >
>>/usr/src/linux-2.6/.tmp_version
>>set -e; \
>>mv -f /usr/src/linux-2.6/.tmp_version /usr/src/linux-2.6/.version
>>rpmbuild --target i386 -ta ../kernel-2.6.8rc2.tar.gz
>>Building target platforms: i386
>>Building for target i386
>>Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.72624
>>+ umask 022
>>+ cd /usr/src/redhat/BUILD
>>+ LANG=C
>>+ export LANG
>>
>>
>These two lines are not present here. Maybe that have impact?
>
>
>
>>+ 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.
Steve
> Sam
>
>
>
next prev parent reply other threads:[~2004-07-19 18:41 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 [this message]
2004-07-19 22:31 ` sam
2004-07-20 19:09 ` Steve Bangert
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=40FC15CF.9090001@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