Fix build with aws 0.16. Thanks, aristidb.

This commit is contained in:
Joey Hess 2017-02-07 13:01:57 -04:00
parent 5f873be329
commit 655f707990
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
4 changed files with 5 additions and 2 deletions

View file

@ -27,6 +27,7 @@ git-annex (6.20170102) UNRELEASED; urgency=medium
shipped in a Debian stable release. If that turns out to not be the
case, this change will need to be cherry-picked into the git-annex in
Debian stable, or its wormhole pairing will break.
* Fix build with aws 0.16. Thanks, aristidb.
-- Joey Hess <id@joeyh.name> Fri, 06 Jan 2017 15:22:06 -0400

View file

@ -221,7 +221,7 @@ store _r info h = fileStorer $ \k f p -> do
let popper = handlePopper numchunks defaultChunkSize p' fh
let req = S3.uploadPart (bucket info) object partnum uploadid $
RequestBodyStream (fromIntegral sz) popper
S3.UploadPartResponse _ etag <- sendS3Handle h req
S3.UploadPartResponse { S3.uprETag = etag } <- sendS3Handle h req
sendparts (offsetMeterUpdate meter (toBytesProcessed sz)) (etag:etags) (partnum + 1)
sendparts p [] 1

View file

@ -40,3 +40,5 @@ BuildError: Failed executing: cabal install --jobs=8 --max-backjumps=100000 --pr
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes!
> [[fixed|done]] thanks --[[Joey]]

View file

@ -48,4 +48,4 @@ Not sure, I got this build failure report from ilovezfs who I think uses Max OS
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
> [[fixed|done]], thanks --[[Joey]]