On Wed, 2022-02-02 at 22:26 +0000, 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 site. > > > > ¹ > > https://src.fedoraproject.org/rpms/rclone/blob/045ab834f/f/rclone.spec#_144 > > That's an interesting proposal. I'll have to wait to test it because > of > the 7-day timeout (I don't know a way of speeding that up) but in the > meantime I'll pass this on to the Rclone forum to see if there's a > response. Well, I waited the requisite 7 days using the "official" rclone build and the issue remains exactly the same. From discussion on the Rclone forum it looks like the only ways to get round this are a) use the build's own built-in default credentials, which are rate-limited in some way, or b) set up a "service account" via Google Workspace. I do in fact have a GW account so I may end up doing this, but it's hardly a general-purpose solution. Fedora could presumably also do it as an institution, but I don't expect that to happen. It may be more productive to look into ways of scripting the interactive refresh dialogue to allow it to be hands-off, but I'm not sure how feasible that would be. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
