Package: rclone
Version: 1.60.1+dfsg-4
Followup-For: Bug #1106640
X-Debbugs-Cc: [email protected]

Dear Maintainer,


the issues that block the release of new package versions for rclone can be 
addressed by removing the related backends:

rclone/backend/all/all.go imports the list of backends and the relevant lines 
can be removed to build without the problematic dependencies blocking new 
releases.

The affected backend that need to be removed until the dependencies issues are 
resolved in the other packages seem to be the following:

_ "github.com/rclone/rclone/backend/azureblob"
_ "github.com/rclone/rclone/backend/azurefiles"
_ "github.com/rclone/rclone/backend/googlecloudstorage"
_ "github.com/rclone/rclone/backend/googlephotos"

Removing these backends should allow a new release of rclone 

-- System Information:
Debian Release: 13.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.57+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rclone depends on:
ii  libc6  2.41-12

rclone recommends no packages.

Versions of packages rclone suggests:
ii  ca-certificates  20250419
ii  fuse             3.17.2-3
ii  fuse3 [fuse]     3.17.2-3

-- no debconf information

Reply via email to