GNU bug report logs - #64278
29.0.92; tramp-rclone.el seems to be in a defunct state

Previous Next

Full log

View this message in rfc822 format

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Sebastian Miele <iota <at> whxvd.name>
Cc: 64278 <at> debbugs.gnu.org
Subject: bug#64278: 29.0.92; tramp-rclone.el seems to be in a defunct state
Date: Sun, 25 Jun 2023 14:55:59 +0200

[Message part 1 (text/plain, inline)]

Sebastian Miele <iota <at> whxvd.name> writes:

Hi Sebastian,

Thanks for the report.

I've never tried the memory type of rclone. I have two test entries in
~/.config/rclone/rclone.conf:

--8<---------------cut here---------------start------------->8---
[local_drive]
type = local
nounc = true

[gdrive]
type = drive
scope = drive
...
--8<---------------cut here---------------end--------------->8---

Both work, and they are tested regularly in my regression tests. So I
wouldn't say that tramp-rclone.el is in a defunct state.

> I am using the Tramp built into the most recent emacs-29 from the Emacs
> repository.  Steps to reproduce the first problem:
>
> Augment ~/.config/rclone/rclone.conf with:
>
>   [memory]
>   type = memory
>
> I tried to debug the issue for myself for a while.  The first issue I
> encountered, is that ‘tramp-rclone’ contains a call to
> ‘tramp-call-process’ with a DESTINATION of 0.  ‘tramp-call-process’
> contains
>
>   (tramp-get-buffer-string destination)
>
> which in that case yields an error.  I tried changing "destination" in
> that line into:
>
>   (unless (eq destination 0) destination)

Reproduced here. I've pushed a fix to the emacs-29 branch in git.

Furthermore, there is indeed a problem detecting a mount point for
rclone memory type. The appended patch should fix this.

However, calling "emacs /rclone:memory:" with the rclone.conf entry
given by you.conf results in in an empty directory. No file visible
there, even if I copy something.

I've tried the rclone memory type manually in a shell

--8<---------------cut here---------------start------------->8---
# mount -t fuse.rclone
local_drive:/ on /tmp/tramp.rclone.local_drive type fuse.rclone (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
memory: on /tmp/tramp.rclone.memory type fuse.rclone (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

# ls -al /tmp/tramp.rclone.memory
total 0
drwxr-xr-x.  1 albinus albinus    0 Jun 25 14:49 .
drwxrwxrwt. 99 root    root    7800 Jun 25 14:49 ..

# rclone copyto ~/tmp memory:

# ls -al /tmp/tramp.rclone.memory
total 0
drwxr-xr-x.  1 albinus albinus    0 Jun 25 14:49 .
drwxrwxrwt. 99 root    root    7800 Jun 25 14:51 ..
--8<---------------cut here---------------end--------------->8---

So I'm a little bit undecided what the memory type of rclone is good
for, and how it works. Do I miss something?

Best regards, Michael.

[Message part 2 (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.