[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#928949: marked as done (unblock: s3ql/3.1+dfsg-2)

Your message dated Tue, 11 Jun 2019 21:44:20 +0200
with message-id <a4c0303c-5819-4b42-c320-515c2b84f5a2@debian.org>
and subject line Re: unblock: s3ql/3.1+dfsg-2
has caused the Debian Bug report #928949,
regarding unblock: s3ql/3.1+dfsg-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
928949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928949
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Dear release managers:

s3ql is a FUSE front end for cloud storage providers such as Amazon's
s3, Google Cloud's knockoff of s3 and OpenStack's knockoff of s3.

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.

unblock s3ql/3.1+dfsg-2

--- End Message ---
--- Begin Message --- 
Hi,

On 28-05-2019 21:08, Paul Gevers wrote:
> On 27-05-2019 22:58, Nikolaus Rath wrote:
>> IIRC the necessary changes are isolated and easy to backport.
>> However, the new release is already in testing which IIRC makes
>> things more complicated.
> If your interested to provide these fixes, then please revert the new
> upstream release in unstable and only pick the relevant changes (e.g.
> with +really upstream versioning). If you're not interested in doing
> that, please close this bug.

We're nearing the moment we can release buster. s3ql hasn't seen an
upload, so I take it this isn't going to happen.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: