S3 AWS package incompatibility about tusd

[Acconut]

I was able to reproduce this issue and the only solution I was able to find is the same deletion approach as you mentioned. For now, I removed the aws-go-sdk package (and another one for which the same problem would have occurred). I hope it will work for you now.

[Acconut]

Once the tests pass again (which fail now due to missing dependencies), I will publish a new release with the corresponding tag.

[Acconut]

The new release has been tagged as 0.5.2

[kvz]

I like you commithash 😋

Sent from mobile, pardon the brevity.

On 26 aug. 2016, at 16:21, Marius [email protected] wrote:

Closed #59 via beef245.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[Acconut]

Thank you for reporting, there is definitely something fishy going on. It seems to be related to how we manage our dependencies but I need to dive more into before I can tell you more specific facts.

Which Go version are you using and did you explicitly enable or disable the Go vendor experiment (using the GO15VENDOREXPERIMENT environment variable)?

[maxpert]

I am using Go 1.7, I will look into disabling the vendor experiment. I got it to work by removing the aws directory from vendor folder (right now I have written a bash script, which is of course not good). I can get code to compile afterwards.

[maxpert]

Will this fix one have a tag? I can just modify my dependency version file to point to the new version.