Control: tags -1 moreinfo Hi David, On Mon, 13 May 2019 15:52:56 -0400 David Gilman <dgilman@gilslotd.com> wrote: > Users who want to use s3ql with Google's cloud storage API need to > obtain an OAuth credential with the appropriate permissions. s3ql > ships a helper binary s3ql_oauth_client that makes the appropriate API > calls to obtain a token with the correct permissions. Google made > breaking changes to the token's structure and s3ql_oauth_client is no > longer able to create these tokens. > > s3ql shipped a fix to s3ql_oauth_client in version 3.1. Please > consider shipping version 3.1 in debian buster so users of s3ql and > Google's cloud storage can obtain valid credentials. If the fix is not > in buster users will be forced to figure out the OAuth flow by > themselves (very painful) or grab a copy of s3ql 3.1 from its upstream > just so they can run s3ql_oauth_client to get a token. A new upstream release is not really what we want at this stage of the release. How much of the package is actually broken right now? There are quite a bit of changes, lots of it in documentation, but also new functionality. How feasible would it be to do a targeted fix of the issue at hand? By the way, you could have mentioned you're not the maintainer. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature