Two issues with Self-Update

Suspected Bug
1

I was so excited for the rclone update. Both because of the SFTP slowdown (I thought it was in my head) but because I could finally test self-update...Or so I thought.

What is the problem you are having with rclone?

Two Problems:

  • Error message with self-update on macOS
  • FUSE loss message on Linux (despite installing from the website, not a package manager)

What is your rclone version (output from rclone version)

macOS:

rclone v1.55.0
- os/type: darwin
- os/arch: amd64
- go/version: go1.16.2
- go/linking: dynamic
- go/tags: cmount

Linux:

rclone v1.55.0
- os/type: linux
- os/arch: amd64
- go/version: go1.16.2
- go/linking: static
- go/tags: cmount

Which OS you are using and how many bits (eg Windows 7, 64 bit)

macOS and Linux (64 bit)

Which cloud storage system are you using? (eg Google Drive)

N/A

The command you were trying to run (eg rclone copy /tmp remote:tmp)

$ rclone -vv self-update

The rclone config contents with secrets removed.

N/A

A log from the command with the -vv flag

macOS

2021/04/26 17:12:30 DEBUG : Using config file from "/Users/<USER>/.config/rclone/rclone.conf"
2021/04/26 17:12:30 DEBUG : rclone: Version "v1.55.0" starting with parameters ["rclone" "-vv" "self-update"]
2021/04/26 17:12:31 Error: failed to update rclone: failed with 404 Not Found downloading https://downloads.rclone.org/v1.55.1/rclone-v1.55.1-darwin-amd64.zip

Linux

2021/04/26 17:13:07 DEBUG : Using config file from "/home/<USER>/.config/rclone/rclone.conf"
2021/04/26 17:13:07 DEBUG : rclone: Version "v1.55.0" starting with parameters ["rclone" "-vv" "self-update"]
2021/04/26 17:13:07 Error: updating would discard the mount FUSE capability, aborting

The questions

on macOS, I think this is just a bug. Browsing around it should be https://downloads.rclone.org/v1.55.1/rclone-v1.55.1-osx-amd64.zip

On Linux, I am confused. I thought that you didn't get FUSE if you used a package manager. But I installed rclone by downloading the executable from the site and moving it into my $PATH. So shouldn't the one I download also be the same with FUSE, etc? Or am I missing something

2

Okay, I do now see

so I guess I can ignore that one

3

I think this should be fixed with 1.55.1 - you can try updating it to the beta and back to stable if you want to see it working.

4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.