all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jeronimo Pellegrini <j_p@aleph0.info>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 35639@debbugs.gnu.org, Jeronimo Pellegrini <j_p@aleph0.info>
Subject: bug#35639: 27.0.50; tramp fails to use ssh on LibreCMC (no base64 encoder available, and not mentioned in tramp manual)
Date: Wed, 8 May 2019 20:01:45 -0300	[thread overview]
Message-ID: <20190508230145.GA1697@socrates.lan> (raw)
In-Reply-To: <87k1f03im0.fsf@gmx.de>

Michael Albinus <michael.albinus@gmx.de> writes:

Hi,

> Jeronimo Pellegrini <j_p@aleph0.info> writes:
>
> Hi Jeronimo,
>
>> The rem-enc function should use a base64 encoding program on the
>> router (but LibreCMC and OpenWRT do not have it!).
>
> Tramp is busy to detect base64 or any other method which can be used for
> encoding/decoding. Pls set tramp-verbose to 6, and rerun the test (w/o
> an installed base64 on the remote machine). There will be a Tramp debug
> buffer.

Yes. That's where I first saw the ""Wrong method specification" message.
The buffer contents are here:

http://aleph0.info/jp/tramp-debug/tramp-debug-buffer.txt

>> reading  lisp/net/tramp-sh.el  I get the impression that tramp
>> actually *should* be able to encode/decode using busybox/awk,
>> which *is* available in LibreCMC (or did I get it wrong?).
>
> See variable tramp-remote-coding-commands, it contains all the different
> encoding/decoding commands Tramp tries to apply. awk is among them.

Before using tramp it has no content; after trying to connect,
tramp-remote-coding-commands is:

((b64 "base64" "base64 -d -i")
 (b64 "base64" "base64 -d")
 (b64 "openssl enc -base64" "openssl enc -d -base64")
 (b64 "mimencode -b" "mimencode -u -b")
 (b64 "mmencode -b" "mmencode -u -b")
 (b64 "recode data..base64" "recode base64..data")
 (b64 tramp-perl-encode-with-module tramp-perl-decode-with-module)
 (b64 tramp-perl-encode tramp-perl-decode)
 (b64 tramp-awk-encode tramp-awk-decode "test -c /dev/zero && od -v -t x1 -A n </dev/null && busybox awk '{}' </dev/null")
 (uu "uuencode xxx" "uudecode -o /dev/stdout" "test -c /dev/stdout")
 (uu "uuencode xxx" "uudecode -o -")
 (uu "uuencode xxx" "uudecode -p")
 (uu "uuencode xxx" tramp-uudecode)
 (pack tramp-perl-pack tramp-perl-unpack))

Funny -- it lists awk as one method:

 (b64 tramp-awk-encode tramp-awk-decode "test -c /dev/zero && od -v -t x1 -A n </dev/null && busybox awk '{}' </dev/null")

But awk was not used, because 'od' is also not available.
And none of the other binaries exist in LibreCMC or OpenWRT (not after a simple install, at least).

> The debug buffer you'll send shall show us, why it doesn't work.

Yes, it is here:

19:41:26.088945 tramp-sh-handle-file-local-copy (1) # File error: Wrong method specification for ‘ssh’

(this is the only occurrence of the string "error").

As I had mentioned in the first message, this is because line 3174 of
tramp.el was reached. It is the default case of a COND expression that has other two cases:
- (or (tramp-local-host-p v)
      (tramp-method-out-of-band-p v size))
- (rem-enc ...)

What happened is that (rem-enc ...) failed (because tramp could not use
any encoding command), and fell through into the default action, which
is this error.

>> So, I'm not sure if this is a tramp bug (can't use awk to encode/decode
>> files in base64 format) or bug in its manual (doesn't mention that
>> a base64 binary is needed on the remote side).
>
> Tramp shall describe in its manual, what does it need for
> encoding/decoding. Agreed.

Right...
I will later in the week propose a patch to the manual, if that is OK.

J.






  reply	other threads:[~2019-05-08 23:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08 16:25 bug#35639: 27.0.50; tramp fails to use ssh on LibreCMC (no base64 encoder available, and not mentioned in tramp manual) Jeronimo Pellegrini
2019-05-08 18:29 ` Michael Albinus
2019-05-08 23:01   ` Jeronimo Pellegrini [this message]
2019-05-09  7:35     ` Michael Albinus
2019-05-09 10:19       ` Jeronimo Pellegrini
2019-05-09 12:05         ` Michael Albinus
2019-05-09 12:37           ` Jeronimo Pellegrini
2019-05-09 12:45             ` Michael Albinus
2019-05-09 19:52               ` Jeronimo Pellegrini
2019-05-09 20:02                 ` Michael Albinus
2019-05-09 20:11                   ` Jeronimo Pellegrini
2019-05-10  8:40                     ` Michael Albinus
2019-05-10  9:07                       ` Robert Pluim
2019-05-10  9:17                         ` Michael Albinus
2019-05-10  9:49                       ` Jeronimo Pellegrini
2019-05-10 10:18                         ` Michael Albinus
2019-05-10 14:45                           ` Jeronimo Pellegrini
2019-05-11  1:57                             ` Jeronimo Pellegrini
2019-05-12  8:43                               ` Michael Albinus
2019-05-17 19:00                                 ` Jeronimo Pellegrini
2019-05-18  7:46                                   ` Michael Albinus
2019-10-11 13:14                   ` Michael Albinus
2019-10-14  1:50                     ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-10-14  7:59                       ` Michael Albinus
2019-12-27 17:26                         ` Michael Albinus
2019-12-27 18:42                           ` Eli Zaretskii
2019-12-30 13:12                           ` Jeronimo Pellegrini
2020-01-01  9:28                             ` Michael Albinus
2020-01-01 15:39                               ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-09 12:58                                 ` Michael Albinus
2020-01-11 13:07                                   ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-11 13:23                                     ` Michael Albinus
2020-01-16 20:09                                       ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-16 20:23                                         ` Michael Albinus
2019-10-15  2:38                       ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190508230145.GA1697@socrates.lan \
    --to=j_p@aleph0.info \
    --cc=35639@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.