Yeah, it definitely makes sense to bring up this issue with upstream. They
should indeed either commit to keeping their API stable, or use gopkg.in or
similar.
On Thu, Jul 27, 2017 at 6:49 AM, Shengjing Zhu wrote:
> On Thu, Jul 27, 2017 at 9:23 PM, Martín Ferrari
On Thu, Jul 27, 2017 at 9:23 PM, Martín Ferrari wrote:
> On 27/07/17 14:05, Michael Stapelberg wrote:
>> It does break the API, as evinced by one build failure.
>>
>> I’m not aware of situations in the past where we created a new binary.
>> How would we name them? Is it worth
Source: golang-github-aws-aws-sdk-go
Severity: wishlist
Dear Maintainer,
I'm currently working on update packer[1] to the latest version.
But it need aws-sdk-go >= 1.4.13. And maybe need to < 1.8.0
Upstream bundled 1.7.1. I find it difficult to fix this in packer to
compile with aws-sdk-go