Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

2017-07-27 Thread Michael Stapelberg
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

Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

2017-07-27 Thread Shengjing Zhu
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

Bug#869800: [pkg-go] Bug#869800: Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

2017-07-27 Thread Michael Stapelberg
On Thu, Jul 27, 2017 at 6:23 AM, 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

Bug#869800: [pkg-go] Bug#869800: Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

2017-07-27 Thread Martín Ferrari
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 the trouble? We had to do it once, for golang-github-dgrijalva-jwt-go-v3-dev

Bug#869800: [pkg-go] Bug#869800: Bug#869800: Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

2017-07-27 Thread Daniel Stender
On 27.07.2017 15: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 the trouble? > > Personally, I would just update the new version + the fixed

Bug#869800: [pkg-go] Bug#869800: Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

2017-07-27 Thread Michael Stapelberg
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 the trouble? Personally, I would just update the new version + the fixed affected packages in one go, to reduce the breakage to a

Bug#869800: [pkg-go] Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

2017-07-27 Thread Martín Ferrari
On 26/07/17 15:46, Shengjing Zhu wrote: > I have tested aws-sdk-go 1.4.22 in my local env and also tested it with > ratt. (I pick 1.4.22 since I hope we don't break too many things.) We need to know if this will introduce further regressions, or if it is API incompatible.. If it is, we would

Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

2017-07-26 Thread Shengjing Zhu
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