[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



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 experimental, I guess it's this version that
you need for rclone?

That's right, the go.mod for rclone 1.47.0 specifies swift v1.0.47.

-> google-api

https://github.com/googleapis/google-api-go-client/commit/de943baf05a022a8f921b544b7827bacaba1aed5
from Oct 21, 2016. Seems fairly old.

Here rclone's 1.47.0 go.mod specifies google.golang.org/api v0.1.0. At the time I was processing it api 0.4.0 was available (0.7.0 is now latest), but I put api 0.1.0 into experimental, the minimum version for rclone, since I wasn't sure if rclone might use deprecated functions that would be dropped in the later versions.

For reference, rclone 1.48.0 specifies google.golang.org/api v0.3.2, and they've already marked api v0.7.0 on the master go.mod.

I see that there was a surge of activity in 2018:
https://github.com/googleapis/google-api-go-client/graphs/code-frequency

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 afterwards" ;)

Drew


Reply to: