Bugzilla Bug 71076

I am trying to use app-arch/tar-1.14.90-r1 to make a tar out of a directory. On
all my other systems, which have tar-1.14, tar c somedir -f somefile.tar works
as expected: the contents of somedir are used to create sometile.tar.

With tar 1.14.90, the same thing results in the output being sent to STDOUT,
and not the file at all. Downgrading to 1.14 solved the problem.


Portage 2.0.51-r3 (default-x86-2004.2, gcc-3.4.3, glibc-2.3.4.20041102-r0,
2.6.9-mm1 i686)
=================================================================
System uname: 2.6.9-mm1 i686 Pentium III (Coppermine)
Gentoo Base System version 1.6.6
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.15.92.0.2-r1
Headers:  sys-kernel/linux-headers-2.4.22
Libtools: sys-devel/libtool-1.5.2-r7
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -mtune=i686 -march=i686 -fomit-frame-pointer -fstack-protector -
pipe"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -mtune=i686 -march=i686 -fomit-frame-pointer -fstack-protector
 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distlocks sandbox"
GENTOO_MIRRORS="ftp://gentoo.mirrors.pair.com/
http://mirror.datapipe.net/gentoo http://open-systems.ufl.edu/mirrors/gentoo
ftp://gentoo.netnitco.net/pub/mirrors/gentoo/source/
ftp://gentoo.ccccom.com"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="apache2 apm arts avi berkdb bitmap-fonts chroot crypt encode f77
foomaticdb fortran gdbm gif gnome gpm gtk gtk2 imlib kde kerberos libg++
libwww mad mikmod mmx motif mpeg mysql ncurses oggvorbis pam pdflib perl
pwdb python qt quicktime readline sdl slang snmp spell ssl tcpd truetype x86
xml2 xv zlib"

Hm. Somewhere along the line, something pulled in the version I had problems
with. Now I can't go back to .90 because it's not in portage anymore, so I'm
left with a broken tar.

I can't be alone here, is this going anywhere?

tar-1.14.90-r1 is still in portage

tar seems to be a little more anal in terms of parameter positions ... `tar c somedir -f somefile.tar` fails while `tar -cf somefile.tar somedir` works fine

-r1 is the version causing me problems. I've seen this on more than one system,
this could really bite a lot of people.

So I'm just simply using it wrong? tar changed?

reported behavior upstream and they provided a quick patch for 1.15.1 which is
now in cvs (but no -r1)