Version: 1.63.1, 1.64.2 Reproducible: Always Steps to Reproduce: 1. Update to rclone-1.63.1 2. Attempt to use storj backends 3. Actual Results: rclone command fails with error "...didn't find backend called "storj" Expected Results: Expect it to work. Works fine with native rclone.org provided rpm. Based on the URL above and the fact that the native rpm works, it seems evident that the exclusion of storj is a Fedora build issue, not an upstream one.
See https://koji.fedoraproject.org/koji/buildinfo?buildID=2269758
I disabled it some months ago as storj stack was difficult to maintain: https://src.fedoraproject.org/rpms/rclone/c/abfcb63258b53b15df3f3854d4f094981482ffb4?branch=rawhide Help to re-enable it is welcome.
I'm not being critical, just trying to understand. But can you help me understand how such a decision is made, notwithstanding the maintenance challenge? Is it common/acceptable to remove core "features" from an upstream product when challenging to maintain by fedora?
I didn't want to sound rude, sorry if I did. Packaging go packages require, per Fedora recommendation, to have all required dependencies first available in Fedora. This can be quite a challenge if a dependency adds new extra dependencies like the storj stack did in the past. If those dependencies are not available then package can't be updated and that was the case for rclone. The update from 1.60 to 1.61 and newers was delayed because of storj dependencies and I decided that it was better to ship an updated rclone without storj backend than keep 1.60 forever. The other option is to use bundled package as upstream would do, that wouldn't require dependencies to be available for Fedora, but as rclone has been an unbundled package I try to keep that way. Storj can be enabled, but requires someone to work on the required packages and I don't have time at the moment, that's why I say help is welcomed.
Sorry I'm unable to help with the packaging. :( Although rclone/storj may be uncommon among Fedora users (as I'm only just now reporting this), loss of this feature is quite impactful to those of us who do. I was forced to install the rclone.org standalone rpm. As such, I wonder if the bundled package option isn't worth considering.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle. Changing version to 40.
What issue did you encounter when dealing with the Storj backend support, Mikel? I'd be happy to examine it and see if I can help. Thanks for maintaining this package!
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This will be fixed during F43 cycle.