[pkg-go] Bug#869800: Bug#869800: Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13
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 worth the trouble? > > We had to do it once, for golang-github-dgrijalva-jwt-go-v3-dev > > Worth the trouble or not: depends on who gets to fix all the breakage > left behind :) > Yes, I think this makes for a good rule of thumb: if fixes for the affected packages are readily available, there’s little harm in uploading all packages at once, and it means less work for ftp-master and less bloat in the archive :). If, however, fixes are more involved/not easily coordinated, we should go the route of a new package. > > > Personally, I would just update the new version + the fixed affected > > packages in one go, to reduce the breakage to a minimum. > > I would be OK with that. > > -- > Martín Ferrari (Tincho) > -- Best regards, Michael ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#869800: Bug#869800: Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13
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 Worth the trouble or not: depends on who gets to fix all the breakage left behind :) > Personally, I would just update the new version + the fixed affected > packages in one go, to reduce the breakage to a minimum. I would be OK with that. -- Martín Ferrari (Tincho) ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#869800: Bug#869800: Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13
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 minimum. On Thu, Jul 27, 2017 at 5:55 AM, Martín Ferrari wrote: > 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 need a new binary package for the > new API > > -- > Martín Ferrari (Tincho) > > ___ > Pkg-go-maintainers mailing list > Pkg-go-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers > -- Best regards, Michael ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers