Re: upgrading golang packages (swift, google-api)

2019-07-24 Thread Arnaud Rebillout
On 7/25/19 9:23 AM, Drew Parsons wrote: > On 2019-07-25 08:11, Shengjing Zhu wrote: >> >> Haven't used apt-rdepends before, but there's build-rdeps(1) from >> devscripts, which should have same result of ratt. Because they both >> use dose-ceve(1) from dose-extra. > > Ah, too many of these damn l

Re: upgrading golang packages (swift, google-api)

2019-07-24 Thread Drew Parsons
On 2019-07-25 08:11, Shengjing Zhu wrote: On Wed, Jul 24, 2019 at 2:48 AM Drew Parsons wrote: ratt is useful: it picked some some extra dependencies that apt-rdepends missed (Build-Dependencies I guess, since apt-rdepends -rb is not supported). Haven't used apt-rdepends before, but there's

Re: upgrading golang packages (swift, google-api)

2019-07-24 Thread Shengjing Zhu
On Wed, Jul 24, 2019 at 2:48 AM Drew Parsons wrote: > ratt is useful: it picked some some extra dependencies that apt-rdepends > missed (Build-Dependencies I guess, since apt-rdepends -rb is not > supported). > Haven't used apt-rdepends before, but there's build-rdeps(1) from devscripts, which sh

Re: upgrading golang packages (swift, google-api)

2019-07-23 Thread Drew Parsons
On 2019-07-23 15:55, Arnaud Rebillout wrote: In my experience with Go packaging, it works best to bump libraries to the minimum version required, rather than to the latest version available. Because we can have only one version of a library at a time, and the latest bleeding edge might work for

Re: upgrading golang packages (swift, google-api)

2019-07-23 Thread Shengjing Zhu
On Tue, Jul 23, 2019 at 2:03 PM Drew Parsons wrote: > > A handful of go packages need to be upgraded in order to upgrade rclone: >golang-github-ncw-swift >golang-google-api > > Since these packages are build dependencies for other packages (docker > and others), I wanted to ask first if it

Re: upgrading golang packages (swift, google-api)

2019-07-23 Thread Arnaud Rebillout
On 7/23/19 2:46 PM, Drew Parsons wrote: > On 2019-07-23 15:14, Arnaud Rebillout wrote: >> >> As usual, I have no clue what that REALLY means until I try to build >> docker against those versions and see what breaks :) > > That sounds to me like "just do the upgrades and sort out the breakage > af

Re: upgrading golang packages (swift, google-api)

2019-07-23 Thread Drew Parsons
On 2019-07-23 15:14, Arnaud Rebillout wrote: I just had a quick look at what docker master (upstream) uses at the moment. -> ncw-swift https://github.com/ncw/swift/commit/a0320860b16212c2b59b4912bb6508cda1d7cee6 from Aug 25, 2018, v1.0.40 onward. Seems fairly recent. I see that 1.0.47-1 is in

Re: upgrading golang packages (swift, google-api)

2019-07-23 Thread Arnaud Rebillout
I just had a quick look at what docker master (upstream) uses at the moment. -> ncw-swift https://github.com/ncw/swift/commit/a0320860b16212c2b59b4912bb6508cda1d7cee6 from Aug 25, 2018, v1.0.40 onward. Seems fairly recent. I see that 1.0.47-1 is in experimental, I guess it's this version that yo

upgrading golang packages (swift, google-api)

2019-07-22 Thread Drew Parsons
A handful of go packages need to be upgraded in order to upgrade rclone: golang-github-ncw-swift golang-google-api Since these packages are build dependencies for other packages (docker and others), I wanted to ask first if it's safe to begin the upgrades. golang-google-api 0.1.0 is ready