2023-09-11 13:28:23 +02:00
|
|
|
This command downloads the latest release of rclone and replaces the
|
|
|
|
|
currently running binary. The download is verified with a hashsum and
|
|
|
|
|
cryptographically signed signature; see [the release signing
|
|
|
|
|
docs](/release_signing/) for details.
|
2021-03-11 20:39:30 +01:00
|
|
|
|
2023-10-05 16:32:50 +02:00
|
|
|
If used without flags (or with implied `--stable` flag), this command
|
2021-03-18 21:11:16 +01:00
|
|
|
will install the latest stable release. However, some issues may be fixed
|
|
|
|
|
(or features added) only in the latest beta release. In such cases you should
|
2023-10-05 16:32:50 +02:00
|
|
|
run the command with the `--beta` flag, i.e. `rclone selfupdate --beta`.
|
2021-03-18 21:11:16 +01:00
|
|
|
You can check in advance what version would be installed by adding the
|
2023-10-05 16:32:50 +02:00
|
|
|
`--check` flag, then repeat the command without it when you are satisfied.
|
2021-03-18 21:11:16 +01:00
|
|
|
|
|
|
|
|
Sometimes the rclone team may recommend you a concrete beta or stable
|
|
|
|
|
rclone release to troubleshoot your issue or add a bleeding edge feature.
|
2023-10-05 16:32:50 +02:00
|
|
|
The `--version VER` flag, if given, will update to the concrete version
|
|
|
|
|
instead of the latest one. If you omit micro version from `VER` (for
|
|
|
|
|
example `1.53`), the latest matching micro version will be used.
|
2021-03-11 20:39:30 +01:00
|
|
|
|
2021-03-18 21:11:16 +01:00
|
|
|
Upon successful update rclone will print a message that contains a previous
|
|
|
|
|
version number. You will need it if you later decide to revert your update
|
|
|
|
|
for some reason. Then you'll have to note the previous version and run the
|
2023-10-05 16:32:50 +02:00
|
|
|
following command: `rclone selfupdate [--beta] OLDVER`.
|
|
|
|
|
If the old version contains only dots and digits (for example `v1.54.0`)
|
|
|
|
|
then it's a stable release so you won't need the `--beta` flag. Beta releases
|
|
|
|
|
have an additional information similar to `v1.54.0-beta.5111.06f1c0c61`.
|
2021-03-18 21:11:16 +01:00
|
|
|
(if you are a developer and use a locally built rclone, the version number
|
2023-10-05 16:32:50 +02:00
|
|
|
will end with `-DEV`, you will have to rebuild it as it obviously can't
|
2021-03-18 21:11:16 +01:00
|
|
|
be distributed).
|
|
|
|
|
|
2021-03-11 20:39:30 +01:00
|
|
|
If you previously installed rclone via a package manager, the package may
|
|
|
|
|
include local documentation or configure services. You may wish to update
|
2023-10-05 16:32:50 +02:00
|
|
|
with the flag `--package deb` or `--package rpm` (whichever is correct for
|
|
|
|
|
your OS) to update these too. This command with the default `--package zip`
|
2021-03-11 20:39:30 +01:00
|
|
|
will update only the rclone executable so the local manual may become
|
|
|
|
|
inaccurate after it.
|
|
|
|
|
|
2023-09-11 13:28:23 +02:00
|
|
|
The [rclone mount](/commands/rclone_mount/) command may
|
2021-03-21 13:14:10 +01:00
|
|
|
or may not support extended FUSE options depending on the build and OS.
|
2023-10-05 16:32:50 +02:00
|
|
|
`selfupdate` will refuse to update if the capability would be discarded.
|
2021-03-21 13:14:10 +01:00
|
|
|
|
2021-03-11 20:39:30 +01:00
|
|
|
Note: Windows forbids deletion of a currently running executable so this
|
|
|
|
|
command will rename the old executable to 'rclone.old.exe' upon success.
|
2021-03-18 21:11:16 +01:00
|
|
|
|
|
|
|
|
Please note that this command was not available before rclone version 1.55.
|
2023-10-05 16:32:50 +02:00
|
|
|
If it fails for you with the message `unknown command "selfupdate"` then
|
2021-03-18 21:11:16 +01:00
|
|
|
you will need to update manually following the install instructions located
|
|
|
|
|
at https://rclone.org/install/
|
