X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Dick Subject: Re: rpm-build-4.1-1 incompatible with tar-1.16.1-1 Date: Thu, 4 Jan 2007 17:39:32 +0000 (UTC) Lines: 37 Message-ID: References: <20061229172741 DOT GA21211 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Christopher Faylor cygwin.com> writes: > I'm struggling to understand what "tar" has to do with rpm. I think > you probably need to do more debugging of this situation. Please take a look at the -t parameter of rpmbuild: The argument used is -b if a spec file is being used to build the package and -t if rpmbuild should look inside of a (possibly compressed) tar file for the spec file to use. rpmbuild does this by calling tar xzf tarname.tar.gz *.spec -O > tmp/1234.spec but *.spec needs --wildcards. Dave Korn artimi.com> writes: > That's not what it looks like to me. Look at that stray ": m" at the end of > the line. It looks to me like you have a stray CR-LF line-ending somewhere, > and the error message is partially self-overwriting. I think this comes from all the pipes and so, the output is corrupted. Whenever I manually extract the specfile from the tar.gz (see above command) and build it it seems to work. You can reproduce the effect by creating a tar (test.tar.gz) containing the following file: test.spec Name: test Version: 0 Release: 0 Summary: test Group: test/test License: GPL %description And then calling: rpmbuild -ta test.tar.gz Thanks in advance, Dick -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/