Description of problem: rpmbuild -tb --force ignores that the tar ball is gzip'ed Version-Release number of selected component (if applicable): rpm-build-4.2-0.69 How reproducible: Always Steps to Reproduce: rpmbuild -tb --force ipv6calc-0.46.tar.gz Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.5837 + umask 022 + cd /mnt/rpmbuild/BUILD + cd /mnt/rpmbuild/BUILD + rm -rf ipv6calc-0.46 + tar -xf /home/rootadm/ipv6calc-0.46.tar.gz tar: This does not look like a tar archive tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: Error exit delayed from previous errors error: Bad exit status from /var/tmp/rpm-tmp.5837 (%prep) Actual Results: See above Expected Results: option "--force" should not disable gzip... $ rpmbuild -tb ipv6calc-0.46.tar.gz Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.46154 + umask 022 + cd /mnt/rpmbuild/BUILD + cd /mnt/rpmbuild/BUILD + rm -rf ipv6calc-0.46 + /usr/bin/gzip -dc /home/rootadm/ipv6calc-0.46.tar.gz + tar -xf - Additional info: This originally happens during "rpmbuild -tb /nfs/path/to/file.tar.gz", where local build host has no entry in passwd for the uid of the file on NFS server: Uid: ( 1001/ UNKNOWN) Gid: ( 100/ users) Therefore I tried option "--force"
BTW, The --force option has murky and ill-defined meaning, I refuse to continue tying all possible workarounds into --force. The real problem is that --tarbuild uses popen(3) to extract the spec file, and popen(3) plats error messages into the current directory. The eventual fix will to be to rip out --tarbuild modes from rpm. Since removing --tarbuild is controversial, DEFERRED into the indefinite future.