Debian's rclone package is missing the storj backend. I assume that is due to this patch: https://sources.debian.org/src/rclone/1.60.1+dfsg-3/debian/patches/ignore_tardigrade_backend.patch/ What is the reason for this? Does it have to do with unpackaged dependencies? Is this documented somewhere? I assume that this is related to this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983445 In any event, if Debian is going to be disabling significant parts of upstream functionality, this should be documented somewhere. Thanks for your work on rclone!
Hi, https://sources.debian.org/src/rclone/1.60.1+dfsg-3/debian/patches/ignore_tardigrade_backend.patch/ This is because the storj.io/uplink dependency is not available in Debian, as well as its dependencies: - github.com/jtolio/eventkit - storj.io/eventkit - github.com/elek/bubbles - github.com/spacemonkeygo/monkit - storj.io/picobuf - storj.io/common - storj.io/drpc - github.com/twitchtv/twirp - storj.io/infectious Usually the patch should be enough. (IMO this should warrant a NEWS entry.) Several backends have been disabled in rclone due to their dependencies not being available in Debian. FYI, unless someone backports rclone (or somehow gets it into a Bookworm point release), then you'll have to wait until the next release of Debian for any backends to be reenabled. Kind regards, Maytham
Hi, https://sources.debian.org/src/rclone/1.60.1+dfsg-3/debian/patches/ignore_tardigrade_backend.patch/ This is because the storj.io/uplink dependency is not available in Debian, as well as its dependencies: - github.com/jtolio/eventkit - storj.io/eventkit - github.com/elek/bubbles - github.com/spacemonkeygo/monkit - storj.io/picobuf - storj.io/common - storj.io/drpc - github.com/twitchtv/twirp - storj.io/infectious Usually the patch should be enough. (IMO this should warrant a NEWS entry.) Several backends have been disabled in rclone due to their dependencies not being available in Debian. FYI, unless someone backports rclone (or somehow gets it into a Bookworm point release), then you'll have to wait until the next release of Debian for any backends to be reenabled. Kind regards, Maytham
... This is pretty much what I assumed. I do think that this needs to be properly documented in a file included in the package itself.