On Wed, 2022-02-02 at 22:26 +, Patrick O'Callaghan wrote:
> > It would be ideal if upstream and downstream packagers could
> > come to some sort of arrangement to improve the situation.
> > That presumes upstream would be interested in having builds
> > which didn't come directly from their
On Wed, 2022-02-02 at 12:22 -0500, Todd Zullinger wrote:
> Patrick O'Callaghan wrote:
> > I would if this were a test version of the RPM, but it
> > isn't. It's the standard version from the base repo. I may
> > file a BZ report.
>
> It looks to me like that upstream doesn't consider anything
>
Patrick O'Callaghan wrote:
> I would if this were a test version of the RPM, but it
> isn't. It's the standard version from the base repo. I may
> file a BZ report.
It looks to me like that upstream doesn't consider anything
but their binaries as official. :(
This might be due in whole or in
On Wed, 2022-02-02 at 08:05 +0800, Ed Greshko wrote:
> On 02/02/2022 07:32, Patrick O'Callaghan wrote:
> > The current version of Rclone from the Fedora repo is 1.57.0. What
> > isn't clear until you look more closely is that this is a
> > development
> > version. It identifies itself as:
> >
> >
On 02/02/2022 07:32, Patrick O'Callaghan wrote:
The current version of Rclone from the Fedora repo is 1.57.0. What
isn't clear until you look more closely is that this is a development
version. It identifies itself as:
rclone: Version "v1.57.0-DEV"
The upshot is that when connecting to Google
The current version of Rclone from the Fedora repo is 1.57.0. What
isn't clear until you look more closely is that this is a development
version. It identifies itself as:
rclone: Version "v1.57.0-DEV"
The upshot is that when connecting to Google Drive the authentication
token expires after 7
