Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 206841 - rpmbuild -ta broken by incompatible change in tar 1.15.91
Summary: rpmbuild -ta broken by incompatible change in tar 1.15.91
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Radek Brich
QA Contact: Fedora Extras Quality Assurance
: 207239 207831 208008 208358 216642 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2006-09-17 06:36 UTC by Kevin Kofler
Modified: 2008-04-08 00:32 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-04-03 18:32:54 UTC

Attachments (Terms of Use)
rpmbuild patch (deleted)
2006-09-29 13:42 UTC, Marcio Oliveira
no flags Details | Diff

Description Kevin Kofler 2006-09-17 06:36:24 UTC
Description of problem:
The -t option of rpmbuild (e.g. rpmbuild -ta mytarball.tar.bz2) doesn't work 
anymore since the latest tar upgrade to FC5. The cause is an incompatible 
change in tar's handling of wildcards passed on the command line. See:
You now have to pass the --wildcards parameter when looking for '*.spec'.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a tarball with a specfile in it.
2. rpmbuild -ta mytarball.tar.bz2

Actual results:
Spurious errors due to the specfile not being found, i.e.:
error: Name field must be present in package: (main package)
error: Version field must be present in package: (main package)
error: Release field must be present in package: (main package)
error: Summary field must be present in package: (main package)
error: Group field must be present in package: (main package)
error: License field must be present in package: (main package)

Expected results:
The package builds.

Additional info:
TAR_OPTIONS=--wildcards rpmbuild -ta mytarball.tar.bz2

Comment 1 Kevin Kofler 2006-09-17 06:38:07 UTC
Adding tar maintainer to CC.

Comment 2 Paul Nasrat 2006-09-20 07:27:29 UTC
*** Bug 207239 has been marked as a duplicate of this bug. ***

Comment 3 Dave Malcolm 2006-09-21 00:10:25 UTC
Me too on Rawhide: I end up with an empty file in rpmbuild/SPECS called:
"tar: Pattern matching characters used in file names. Please," which it tries to
interpret as the specfile, leading to the failure messages above.

Appears to prevent all of the -t options of rpmbuild from working in Rawhide
(ouch); this feels like a blocker to me.

Comment 5 Dave Malcolm 2006-09-21 16:52:15 UTC
I've written a reproducer for this here:*checkout*/testing/trunk/rhts/tests/sandbox/rpm/rpm-build/

fails on one machine with:

passes on another machine with:

Comment 6 John Ata 2006-09-22 17:17:10 UTC
Other -t variants such as -tb are broken as well

Comment 7 Paul Nasrat 2006-09-25 07:35:47 UTC
*** Bug 207831 has been marked as a duplicate of this bug. ***

Comment 8 Nalin Dahyabhai 2006-09-25 12:06:30 UTC
*** Bug 207825 has been marked as a duplicate of this bug. ***

Comment 9 Paul Nasrat 2006-09-25 21:05:59 UTC
*** Bug 208008 has been marked as a duplicate of this bug. ***

Comment 10 Marcio Oliveira 2006-09-29 13:42:03 UTC
Created attachment 137388 [details]
rpmbuild patch

Comment 11 Marcio Oliveira 2006-09-29 13:43:20 UTC

I have a similar problem and after a lot of pain I created a patch and it worked
for me. I hope it helps fix this problem as well.

Check out this link which describes the problem I encountered, and attached its
the patch I created for the rpmbuild package.

Marcio Oliveira

Comment 12 Johan Kok 2006-09-30 08:13:32 UTC
A new tar RPM was released (1.15.1-14) which fixed the problem on my
workstation. Does it work for you too?

Comment 13 Johan Kok 2006-09-30 08:25:58 UTC
*** Bug 208358 has been marked as a duplicate of this bug. ***

Comment 14 Kevin Kofler 2006-09-30 11:04:28 UTC
Tar was reverted to fix Bug 207115, and as a side effect this also fixes this 
bug. However, it will break again when tar is upgraded again, e.g. to 1.16.0 
when it will be out. But using the patch now won't work either because tar 
1.15.1 won't eat the --wildcards option. So we're stuck.

Comment 15 Kevin Kofler 2006-09-30 11:56:03 UTC
Correcting myself: Actually, tar 1.15.1 does eat --wildcards, so it should be 
possible to add the switch now and avoid breakage later. In tar 1.15.1, the 
switch only applies to exclude patterns (and is on by default), the newer 
version also makes it apply to listed files.

Comment 16 Jack Neely 2006-09-30 21:53:56 UTC
I can confirm that building packages with rpmbuild -ta foo.tar.gz does indeed
work on FC5.


Comment 17 John Ata 2006-10-02 13:32:39 UTC
(In reply to comment #12)
> A new tar RPM was released (1.15.1-14) which fixed the problem on my
> workstation. Does it work for you too?

Updated FC5 with 1.15.1-14 - works for me...

Comment 21 Kaz Gofron 2006-11-02 08:45:10 UTC
It is still broken in FC5:

TAR_OPTIONS=--wildcards rpmbuild -ta xx.yy.tar.gz
does not work either (for this tar)

Comment 22 Karel Zak 2006-11-08 15:19:12 UTC
The script from comment #5:

Dummy package
Success - RPM appears to have been built successfully

$ rpm -q tar rpm-build

Comment 23 Peter Vrabec 2006-11-08 15:33:44 UTC
It should be alright in all tar-1.15.1-* releases.

Comment 24 Paul Nasrat 2006-11-21 10:51:30 UTC
*** Bug 216642 has been marked as a duplicate of this bug. ***

Comment 25 Lukas Vrabel 2007-03-20 14:11:51 UTC
opened because of planed tar upgrade

Comment 26 Kevin Kofler 2007-03-20 14:13:54 UTC
All the way down to FC5? FC6? Or only >=F7?

Comment 27 Paul Nasrat 2007-03-20 15:51:41 UTC
I'd hope devel/fc7.  Lukas can you update the Version appropriately.

Comment 28 Paul Nasrat 2007-03-22 10:54:11 UTC
Lukas - what versions of fedora is this required for?

Comment 29 Lukas Vrabel 2007-03-22 13:22:02 UTC
oh im sorry it's planned for FC7

Comment 30 Radek Brich 2007-06-29 13:21:47 UTC
Hi all.

I am packaging version 1.17 for FC8. After reading these comments I figured it
would be best to preserve behavior of version 1.15.1. I already have patch for that.

Wildcards will be used by default and --no-wildcards option will be also
supported to switch them off.

But I think it would be best if rpmbuild and other tools will also be patched.
They should call tar with --wildcards option if they use this feature. It does
not break anything and it works even with tar 1.15.1.

Now (and anytime in future), these tools are unable to work with raw upstream
tar. That isn't very good, imho... It's unlikely that upstream will ever restore
old behavior.

Comment 31 Panu Matilainen 2007-07-03 11:15:24 UTC
rpm will pass --wildcards to tar on build, once it's in rawhide feel
free to drop the wildcards-by-default patch from tar (at least from rpm POV,
dunno if other tools care)

Comment 32 Panu Matilainen 2007-08-09 17:51:50 UTC
Rawhide (and F8-test1) has now and uses --wildcards so from rpm POV the
tar patch can be dropped.

Comment 33 Radek Brich 2007-08-10 10:41:41 UTC
Okay, thanks. I'll probably keep the patch in for a while...

Comment 34 Bug Zapper 2008-04-03 18:14:38 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

Comment 35 Mike Pope 2008-04-08 00:32:47 UTC
Unable to reproduce any more in F8+updates.

Note You need to log in before you can comment on or make changes to this bug.