On Mon, 2018-02-26 at 11:26 +0100, Matthias Brugger wrote:
$ sudo zypper in go
Loading repository data... Reading installed packages... Resolving package dependencies...
The following 17 NEW packages are going to be installed: go go1.4 go1.4-doc go1.4-race go1.6 go1.6-doc go1.6-race go1.7 go1.7-doc go1.7-race go1.8 go1.8-doc go1.8-race go1.9 go1.9-doc go1.9-race go-race
The following recommended package was automatically selected: go1.9-doc
17 new packages to install. Overall download size: 199,3 MiB. Already cached: 0 B. After the operation, additional 1,1 GiB will be used.
I hit the same problem. Due to space constraints on my hard disk I uninstalled all older go versions, but they get all pulled in again when I do a zypper dup to get the newest tumbleweed snapshot.
That's a bug - and actually a pretty simple one in plus: from go1.4.spec: Supplements: go So, whenever 'go' is installed, go1.4 supplements it (which is a reverse recommends). Installing go obviously triggers this. Installing go1.9 directly still triggers it, as go1.9 requires go - which go1.4 then again supplements. If there is no bug report yet, plese file one so this can be fixed (the Supplements can simply be dropped - this is useless, as go requires go<version>; so go<versionX> needs not supplement it) Cheers Dominique