Bug 2320191 - rclone is no longer just recommended
Summary: rclone is no longer just recommended
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: deja-dup
Version: 40
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-21 12:49 UTC by Jonathan Billings
Modified: 2024-10-30 03:23 UTC (History)
4 users (show)

Fixed In Version: deja-dup-46.1-3.fc41 deja-dup-46.1-3.fc40
Clone Of:
Environment:
Last Closed: 2024-10-30 02:36:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jonathan Billings 2024-10-21 12:49:55 UTC
Deja Dup, when set up to back up to Google Drive, fails to backup files with the message "rclone not found: please install rclone".  This error is coming from duplicity. ( https://gitlab.com/duplicity/duplicity/-/blob/dev/duplicity/backends/rclonebackend.py?ref_type=heads#L41 )



The Recommend: rclone needs to be changed to Requires: rclone.

Reproducible: Always

Steps to Reproduce:
1. Install deja dup, set to back up to Google Drive
2. Attempt to back up home directory

Actual Results:  
You get an error, "rclone not found: please install rclone"

Expected Results:  
Back up operates fine

It looks like in version 46.0, rclone is used by the Google Drive backend in Duplicity.  (https://gitlab.gnome.org/World/deja-dup/-/blob/main/NEWS.md).  This change appears to occur even if you've backed up using the older Python based code before.

It looks like the Deja Dup flatpak switched to using rclone backend for duplicity cloud storage back in January: https://gitlab.gnome.org/World/deja-dup/-/commit/163d063d9f6233114795c74bdf23a9c363051ad5

Comment 1 Fedora Update System 2024-10-21 16:23:02 UTC
FEDORA-2024-045b5f4a5e (deja-dup-46.1-3.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-045b5f4a5e

Comment 2 Fedora Update System 2024-10-21 16:23:03 UTC
FEDORA-2024-3e47144591 (deja-dup-46.1-3.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-3e47144591

Comment 3 Fedora Update System 2024-10-22 02:03:43 UTC
FEDORA-2024-045b5f4a5e has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-045b5f4a5e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-045b5f4a5e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2024-10-22 02:34:52 UTC
FEDORA-2024-3e47144591 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-3e47144591`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-3e47144591

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2024-10-30 02:36:49 UTC
FEDORA-2024-3e47144591 (deja-dup-46.1-3.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2024-10-30 03:23:24 UTC
FEDORA-2024-045b5f4a5e (deja-dup-46.1-3.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.