GNU bug report logs - #69889
Rclone is 4 years outdated

Previous Next

Package: guix;

Reported by: Adroit <adroit1 <at> proton.me>

Date: Tue, 19 Mar 2024 01:58:02 UTC

Severity: normal

To reply to this bug, email your comments to 69889 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#69889; Package guix. (Tue, 19 Mar 2024 01:58:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Adroit <adroit1 <at> proton.me>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Tue, 19 Mar 2024 01:58:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Adroit <adroit1 <at> proton.me>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: Rclone is 4 years outdated
Date: Tue, 19 Mar 2024 01:35:26 +0000
[Message part 1 (text/plain, inline)]
The package "rclone" has not been updated in a long time. I did not find any open bug reports about it.

I was brave and tried to run the latest myself using:
`guix build rclone --with-source=rclone <at> 1.66.0=./rclone-1.66.0.tar.gz`
With the latest source tarball from the Github release. The recipe (in sync.scm) uses a tar download rather than a git-fetch for some reason, so I wasn't able to reuse the recipe with --with-branch. (Btw --with-version would be nice to have, since the version's download URL is done correctly in the recipe.)

Unfortunately I ran into some obscure build error and don't know how to proceed as this is outside of my familiarity.
[Message part 2 (text/html, inline)]

This bug report was last modified 46 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.