Re: 23.0.60; TRAMP fails to copy a gzip'ed file

[Michael Albinus <michael.albinus@gmx.de>]

Peter Dyballa <Peter_Dyballa@freenet.de> writes:

>> For further analysis I would need the debug buffer of Tramp. Before
>> you start, please perform "(setq tramp-verbose 9)". Make sure that
>> there are no sensitive data in the copied file; I'll read it.

> 17:00:11 tramp-send-command (6) # mimencode -b < /var/log/messages-20080221.gz 2>/dev/null; echo tramp_exit_status $? 

[...]

> 17:00:22 tramp-wait-for-regexp (6) # 
> H4sICEv+vEcAA21lc3NhZ2VzLTIwMDgwMjIxAMz9bXMkuZHlj76/n4L3nWQ2XR0AAoFA2d1r
> pqfZ0cxI6u2Wdu78ZTJZksyqShXJ5GQmu7v06W9EZkZ1MdwP4ER4srG7MyP1rM5xevwSgXAA
> 
> 17:00:22 tramp-handle-insert-file-contents (4) # Inserting local temp file `/tmp/tramp.29438M8o.gz'...done

That looks very strange. Just 2 lines as the result of mimencode.

Could you, please, apply the following commands on the remote machine:

  mimencode -b </var/log/messages-20080221.gz | mimencode -u -b >/tmp/123.gz
  cksum /var/log/messages-20080221.gz
  cksum /tmp/123.gz

/tmp/123.gz shall be identical to /var/log/messages-20080221.gz. If yes,
I would like to see another trace, but with "(setq tramp-verbose 10)".
You might send it to me off the list; it will be huge.

Best regards, Michael.