Bug 475950 - --file HOSTNAME:F doesn't work because rsh is not required when tar is built
Summary: --file HOSTNAME:F doesn't work because rsh is not required when tar is built
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: tar
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 475981
TreeView+ depends on / blocked
 
Reported: 2008-12-11 09:01 UTC by Masatake YAMATO
Modified: 2008-12-11 12:35 UTC (History)
2 users (show)

Fixed In Version: tar-1.20-6.fc11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-11 12:32:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
A patch, for spec file of tar, fixing the issue. (593 bytes, patch)
2008-12-11 09:02 UTC, Masatake YAMATO
no flags Details | Diff

Description Masatake YAMATO 2008-12-11 09:01:16 UTC
Description of problem:

Remote archiving with --file HOSTNAME:F option doesn't work.
The function needs the path for rsh command.
The configure script for tar detects the path.
However, the spec file of tar doesn't require rsh package
in BuildRequire field.

Version-Release number of selected component (if applicable):
1.20-5.fc11 raw hide. But tar shipped with EL4 has the same problem.

How reproducible:

 $ tar -c -f localhost:/tmp/x.tar /boot
 tar: localhost\:/tmp/x.tar: Cannot open: Input/output error
 tar: Error is not recoverable: exiting now

Steps to Reproduce:
1. Just invoke tar with --file HOSTNAME:F argument
2.
3.
  
Actual results:
Reporting an error.

Expected results:
The archive is created at the remote host.

Additional info:

See the patch.

Comment 1 Masatake YAMATO 2008-12-11 09:02:46 UTC
Created attachment 326595 [details]
A patch, for spec file of tar, fixing the issue.

Comment 2 Ondrej Vasik 2008-12-11 12:32:59 UTC
Thanks for info and patch (although patch not needed in such cases). Fixed in Rawhide, built as tar-1.20-6.fc11, closing RAWHIDE, will clone bugzilla for RHEL to fix it at least in EL5.


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