Several months ago I installed GO via Yast. The “GO PROGRAMMING LANGUAGE” book required at least GO version 1.9. So I ticked go1.9 and go1.9-race in Yast. The result was that go, go1.4, go1.6, go1.7, go1.8 as well as go1.9 and the corresponding go-race versions were installed. When I subsequently ran GO, the version was 1.4.3-21.1 - the lowest version. I found no way to change that. That version worked Ok for the early chapters of the GO book, although I would like to run GO version 1.9 eventually. Subsequently problems started with updates. For weeks now there was an automatic update “opensuse-2018-218(1) security update for go”, which always fails with “Update Error: Subprocess failed. Error: RPM failed”. I then tried to do an update with Yast. The “opensuse-2018-218(1) security update for go” failed there also with a slightly longer error message - same as above + “error package go-1.9.2-30.1.x87_64 is nor installed 1.9.4-33.1”.
In desperation I tried to uninstall all the versions of GO by putting a X on each package in Yast. Unfortunately that failed as well. There were similar RPM errors after the attempted rm commands. Now GO no longer works - it is completely broken and cannot be uninstalled or updated.
Can anyone help me how to solve this problem.
Hardware 2 x Intel Pentium CPU 8940 @ 2.0 GHz, 3.7 GiB Ram, 500 GB SSD disk
id like a clear explanation of this too. opensuse go installation appears a mess.
as a sticky-tape work-around perhaps setting GOROOT in the working shell to temporarily point to 1.9 might work? or perhaps set up your own named executable in /bin?
It’s possible to install only Go 1.9.
But, if you do install multiple versions of “go” then you can switch between them easily (see below)
The following is how I did this…
Although probably not a critical option, because I intend to develop using the Go language and not just run pre-built Go applications, I recommend adding the Go language repository. You can do this using the YaST Software Repository management module or possibly zypper. Oddly, in this case my attempt using zypper failed for unknown reasons so I did this using YaST. The URL for the 42.3 Go repo is the following
I then used YaST Software Manager, and did a search for go, found “Go 1.9” and checked the box for installation Side note:
As long as I was using YaST Software Manager (I usually don’t), I also checked Patterns (nothing go-related existed), Packages (no results), and RPM groups (Only Go 1.4 listed). So, these other “views” don’t really fully work.
After Checking “Go 1.9” I also noted packages for Go 1.8 and Go 1.7 were selected.
I unchecked those boxes, deselecting those unwanted Go versions.
Now, after clicking the “Accept” button to install the selected packages, the following Summary displayed
So,
It’s possible to install a specific version of Go without the other undesirable versions.
But,
If you do install multiple versions of Go on your system, it looks like you can use update-alternatives to switch between each installed version. To switch between go versions, run the following command and select what you want
update-alternatives --config go
Now,
To your current situation…
From your description, I wonder if you installed the complete selection of Go packages… note in the first screenshot above that “Go 1.9” is the actual Go package you should install (the others are then selected automatically) but “Go 1.9-race” is the complete package… It’s only a collection of add-on functions to address race conditions.
See if the following command runs, and post the result to see what packages are supposedly installed on your system
# zypper se -i 'go'
BTW -
Your situation might have been the result of a self-inflicted mistake but is not that uncommon when developing…
It’s a major reason why whenever possible I do all my development in virtual machines so that when the system is borked, I just disgard and fire up a new virtual machine (a copy of my development install and project so I don’t have to re-install everything all over again).
My physical machine is then left pristine and unaffected by any misfortune.
I have just tried removing with zypper with similar errors to removing with Yast.
The following list of packages was obtained via the command “zypper info package:go*” with some editing:Name Version Repository
go 1.9.4-33.1 openSUSE-Leap-42.3-Update
go-race 1.9.4-33.1 openSUSE-Leap-42.3-Update
go1.4 1.4.3-21.1 @System
go1.4-doc 1.4.3-21.1 @System
go1.4-race 1.4.3-21.1 @System
go1.6-doc 1.6.4-20.1 @System
go1.6-race 1.6.4-20.1 @System
go1.7-doc 1.7.5-31.1 @System
go1.7-race 1.7.5-31.1 @System
go1.8-doc 1.8.5-11.1 @System
go1.8-race 1.8.5-11.1 @System
go1.9 1.9.4-6.1 @System
go1.9-race 1.9.4-5.1 openSUSE-Leap-42.3-Update
The following 14 packages are going to be REMOVED:
go go go-race go1.4 go1.4-doc go1.4-race go1.6-doc go1.6-race go1.7-doc go1.7-race go1.8-doc go1.8-race go1.9
go1.9-race
14 packages to remove.
After the operation, 388.8 MiB will be freed.
Continue? [y/n/…? shows all options] (y): y
( 1/14) Removing go-1.9.2-30.1.x86_64 …[error]
Removal of (341)go-1.9.2-30.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go-1.9.2-30.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 2/14) Removing go-race-1.9.4-33.1.x86_64 …[done]
( 3/14) Removing go1.4-doc-1.4.3-21.1.x86_64 …[error]
Removal of (345)go1.4-doc-1.4.3-21.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.4-doc-1.4.3-21.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 4/14) Removing go1.4-race-1.4.3-21.1.x86_64 …[error]
Removal of (346)go1.4-race-1.4.3-21.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.4-race-1.4.3-21.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 5/14) Removing go1.6-doc-1.6.4-20.1.x86_64 …[error]
Removal of (347)go1.6-doc-1.6.4-20.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.6-doc-1.6.4-20.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 6/14) Removing go1.6-race-1.6.4-20.1.x86_64 …[error]
Removal of (348)go1.6-race-1.6.4-20.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.6-race-1.6.4-20.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 7/14) Removing go1.7-doc-1.7.5-31.1.x86_64 …[error]
Removal of (349)go1.7-doc-1.7.5-31.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.7-doc-1.7.5-31.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 8/14) Removing go1.7-race-1.7.5-31.1.x86_64 …[error]
Removal of (350)go1.7-race-1.7.5-31.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.7-race-1.7.5-31.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 9/14) Removing go1.8-doc-1.8.5-11.1.x86_64 …[error]
Removal of (351)go1.8-doc-1.8.5-11.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.8-doc-1.8.5-11.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
(10/14) Removing go1.8-race-1.8.5-11.1.x86_64 …[error]
Removal of (352)go1.8-race-1.8.5-11.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.8-race-1.8.5-11.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
(11/14) Removing go1.9-race-1.9.4-5.1.x86_64 …[done]
(12/14) Removing go-1.9.4-33.1.x86_64 …[done]
(13/14) Removing go1.4-1.4.3-21.1.x86_64 …[error]
Removal of (344)go1.4-1.4.3-21.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.4-1.4.3-21.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
(14/14) Removing go1.9-1.9.4-6.1.x86_64 …[error]
Removal of (353)go1.9-1.9.4-6.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.9-1.9.4-6.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
Problem occurred during or after installation or removal of packages:
Failed to cache rpm database (1).
Please see the above error message for a hint.
Three packages have actually been removed but Yast still shows “go 1.9.4-33.1” as installed.
All the packages with the “RPM failed error” show the revision number in Yast either as RED or BLUE ??
Zypper does not work any better - sorry I need more help.
Thank you for your detailed Go installation instructions. I guessed I should have only selected ‘go1.9’ etc. Not knowing what to expect I selected ‘go’ and got all the early revisions which I cannot get rid of.
zypper se -i 'go’i+ | go | A compiled, garbage-collected, concurrent programming langu-> | package
i+ | go1.4 | A compiled, garbage-collected, concurrent programming langu-> | package
i+ | go1.4-doc | Go documentation | package
i+ | go1.4-race | Go runtime race detector | package
i+ | go1.6-doc | Go documentation | package
i+ | go1.6-race | Go runtime race detector | package
i+ | go1.7-doc | Go documentation | package
i+ | go1.7-race | Go runtime race detector | package
i+ | go1.8-doc | Go documentation | package
i+ | go1.8-race | Go runtime race detector | package
i+ | go1.9 | A compiled, garbage-collected, concurrent programming langu-> | package
This is what is left after “zypper remove …” in answer to nde33. The run-time for GO has been broken since my initial attempt to clean up and remove GO packages with Yast.
The following 11 packages are going to be REMOVED:
go go1.4 go1.4-doc go1.4-race go1.6-doc go1.6-race go1.7-doc go1.7-race go1.8-doc go1.8-race go1.9
11 packages to remove.
After the operation, 388.5 MiB will be freed.
Continue? [y/n/…? shows all options] (y): y
( 1/11) Removing go-1.9.2-30.1.x86_64 …[error]
Removal of (341)go-1.9.2-30.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go-1.9.2-30.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 2/11) Removing go1.4-doc-1.4.3-21.1.x86_64 …[error]
Removal of (343)go1.4-doc-1.4.3-21.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.4-doc-1.4.3-21.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 3/11) Removing go1.4-race-1.4.3-21.1.x86_64 …[error]
Removal of (344)go1.4-race-1.4.3-21.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.4-race-1.4.3-21.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 4/11) Removing go1.6-doc-1.6.4-20.1.x86_64 …[error]
Removal of (345)go1.6-doc-1.6.4-20.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.6-doc-1.6.4-20.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 5/11) Removing go1.6-race-1.6.4-20.1.x86_64 …[error]
Removal of (346)go1.6-race-1.6.4-20.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.6-race-1.6.4-20.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 6/11) Removing go1.7-doc-1.7.5-31.1.x86_64 …[error]
Removal of (347)go1.7-doc-1.7.5-31.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.7-doc-1.7.5-31.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 7/11) Removing go1.7-race-1.7.5-31.1.x86_64 …[error]
Removal of (348)go1.7-race-1.7.5-31.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.7-race-1.7.5-31.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 8/11) Removing go1.8-doc-1.8.5-11.1.x86_64 …[error]
Removal of (349)go1.8-doc-1.8.5-11.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.8-doc-1.8.5-11.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
( 9/11) Removing go1.8-race-1.8.5-11.1.x86_64 …[error]
Removal of (350)go1.8-race-1.8.5-11.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.8-race-1.8.5-11.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
(10/11) Removing go1.9-1.9.4-6.1.x86_64 …[error]
Removal of (351)go1.9-1.9.4-6.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.9-1.9.4-6.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
(11/11) Removing go1.4-1.4.3-21.1.x86_64 …[error]
Removal of (342)go1.4-1.4.3-21.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package go1.4-1.4.3-21.1.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
There are some running programs that might use files deleted by recent upgrade. You may wish to check and restart some of them. Run ‘zypper ps -s’ to list these programs.
Same errors as with previous attempts after zypper clean and zypper refresh
The 11 RPM packages are obviously not installed. All I really want to do is to remove the names of these packages from the data-base which makes Yast/zypper assume they are installed. Is there any way of doing that. Clean and Refresh seem to ignore this inconsistency.
In any case whether you resolve this or not,
IMO you can set up a working Go environment in a virtual machine, in fact I’d highly recommend not just for possibly avoiding any problems in your HostOS but to easily address this type of situation in the future.
I don’t know if there is a response in the mailing list, but the described GOROOT problem is likely only an update-alternatives lack of full configuration issue.
Highly recommend you submit your problem as a bug to https://bugzilla.opensuse.org.
Maybe even submit a bug relating to your mailing list reference(I don’t see an existing bug in the bugzilla)
and
Install something like Virtualbox with an openSUSE Guest and install Go as I described.
That way,
You will have a fully working environment immediately so you won’t be slowed down and whenever your problem might be fixed, that fix can be applied in the future.
i dont understand why all packages are given as @system
are you using a root shell for remove (i see no sudo)?
you dont need to formally specify doc files etc, they would be removed automatically (or can be certain with -u flag i.e. zypper rm -u <>)
to make things clearer could you give results of ‘zypper info go1.9’ and clarify if /usr/lib64/go/ contains the go versions 1.6 to 1.9?
Thank you TSU for your 2 replies and NDC33. I will follow up the threads on orphaned packages. I will also follow up with a bug report to https://bugzilla.opensuse.org.
The idea of a Virtualbox is sensible and I will do it. Unfortunately I have never had the need for it. I have been using SUSE Linux since 1995 and have always found it stable for my needs. I mostly do development with C and C++, Bison and Flex as well as Perl and a lot of Shell scripts.
I have no idea how to install a Virtualbox and get my current environment into it. If you could point me to a tutorial describing exactly what I should do, that would be a great help. My current 500 GB SSD disc has plenty of spare space. It has 2 partitions:root 42 GB 62% used
home 435 GB 12% used
I am doing all the activities with zypper in a root shell. I do not understand why some of the repositories for packages are given as @system. It could be that in the early stages of this clean-up I followed the advice of another forum entry and removed all repositories from Yast except:
zypper reposRepository priorities are without effect. All enabled repositories share the same priority.
Repository : @System
Name : go1.9
Version : 1.9.4-6.1
Arch : x86_64
Vendor : obs://build.opensuse.org/devel:languages:go
Installed Size : 237.7 MiB
Installed : Yes
Status : up-to-date
Source package : go1.9-1.9.4-6.1.src
Summary : A compiled, garbage-collected, concurrent programming language
Description :
Go is an expressive, concurrent, garbage collected systems programming language
that is type safe and memory safe. It has pointers but no pointer arithmetic.
Go has fast builds, clean syntax, garbage collection, methods for any type, and
run-time reflection. It feels like a dynamic language but has the speed and
safety of a static language.
callala:/usr/lib64/go # ls -l . 1.9.:
total 0
drwxr-xr-x 1 root root 38 Mar 1 02:14 1.9
drwxr-xr-x 1 root root 32 Feb 5 11:23 bin
drwxr-xr-x 1 root root 34 Feb 5 11:23 contrib
drwxr-xr-x 1 root root 0 Jul 14 2017 lib
drwxr-xr-x 1 root root 120 Feb 5 11:23 pkg
drwxr-xr-x 1 root root 460 Feb 5 11:23 src
1.9:
total 0
drwxr-xr-x 1 root root 50 Mar 2 18:14 bin
drwxr-xr-x 1 root root 34 Mar 2 18:14 contrib
drwxr-xr-x 1 root root 8 Mar 1 02:14 lib
drwxr-xr-x 1 root root 120 Mar 1 02:14 pkg
drwxr-xr-x 1 root root 472 Mar 2 18:14 src
callala:/usr/lib64/go # bin/go versiongo version go1.7.5 linux/amd64
callala:/usr/lib64/go # 1.9/bin/go versiongo version go1.9.4 linux/amd64
as shown above there are 2 versions of GO actually present:
go version go1.7.5 linux/amd64 @ /usr/lib64/go/bin
go version go1.9.4 linux/amd64 @ /usr/lib64/go/1.9/bin
Neither is in a directory on $PATH, which you would expect after a proper install.
My $PATH is:
In addition to my answer to ndc33 it might be interesting for you to see the following:
zypper info goLoading repository data…
Reading installed packages…
Information for package go:
Repository : openSUSE-Leap-42.3-Update
Name : go
Version : 1.9.4-33.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 82 B
Installed : Yes
Status : out-of-date (version 1.9.2-30.1 installed)
Source package : go-1.9.4-33.1.src
Summary : A compiled, garbage-collected, concurrent programming language
Description :
Go is an expressive, concurrent, garbage collected systems programming language
that is type safe and memory safe. It has pointers but no pointer arithmetic.
Go has fast builds, clean syntax, garbage collection, methods for any type, and
run-time reflection. It feels like a dynamic language but has the speed and
safety of a static language.
Of particular interest are the lines:Version : 1.9.4-33.1
Status : out-of-date (version 1.9.2-30.1 installed)
neither version are the ones actually present in /usr/lib64/go/bin and /usr/lib64/go/1.9/bin
Regarding the above post #13 (I won’t quote the whole post)
“zypper info packagename” will only work on installed packages.
So, if for instance you thought you uninstalled go1.9, it’s still installed on your system.
When a package source is “@system” I’ve found that references the install DVD.
You’ll find that anything managed by update-alternatives isn’t necessarily in $PATH, what happens is that a generic binary needs to be in the system path, and then update-alternatives symlinks that generic binary and a substitute binary elsewhere… So that your system reads that substitute binary instead of the generic.
So, if you run the following command, from what you posted you should see both go 1.7.5 and 1.9.4 displayed, and you can select one or the other as you wish… but from what you’ve also posted in this Forum, a Slave link that describes the GOPATH for each selection is missing so needs to be configured manually.
That command suggested installing amongst others go1.7, which I accepted with the idea that if it was installed again correctly I could afterwards remove it. Unfortunately the attempted installation produced 1000’s of errors (overflowed the konsole buffer). The errors were all similar. Here are the last of them:error: db4 error(-30974) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting “sum_arm.go” records from Basenames index
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting “sum_arm.s” records from Basenames index
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting “sum_ref.go” records from Basenames index
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting “net” records from Basenames index
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30974) getting “http2” records from Basenames index
error: rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30974) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
[truncated]
This confirms my suspicion that the Yast/zypper database is seriously broken. I am hoping that I can fix this or find a workaround without having to do a complete new installation. So far I have been ignoring the automatic update messages which all immediately fail. Not a good look for openSUSE.
I would still appreciate a link to a Virtualbox (virtual machine) tutorial.
I ran the following commands from the ancient Forum thread you suggested without error:
callala:~ # rpmdb --rebuilddb
callala:~ # zypper refRepository ‘openSUSE-Leap-42.3-Non-Oss’ is up to date.
Repository ‘openSUSE-Leap-42.3-Update’ is up to date.
Repository ‘openSUSE-Leap-42.3-Update-Non-Oss’ is up to date.
Repository ‘openSUSE-Leap42.3-Oss’ is up to date.
All repositories have been refreshed.
The following 3 package updates will NOT be installed:
go1.8 go1.8-doc go1.8-race
The following 4 NEW packages are going to be installed:
go-race go1.9-doc go1.9-race libtxc_dxtn
The following package is going to be REMOVED:
s2tc
The following 31 packages are going to be upgraded:
MozillaFirefox MozillaFirefox-translations-common chromium go java-1_8_0-openjdk java-1_8_0-openjdk-headless
kernel-firmware libatomic1 libgcc_s1 libgcc_s1-32bit libgomp1 libitm1 libquadmath0 libstdc++6 libstdc++6-32bit
libsystemd0 libsystemd0-32bit libtsan0 libudev1 libudev1-32bit messagelib messagelib-lang systemd systemd-32bit
systemd-bash-completion systemd-logger systemd-sysvinit ucode-amd ucode-intel udev wireless-regdb
31 packages to upgrade, 4 new, 1 to remove.
Overall download size: 222.6 MiB. Already cached: 0 B. After the operation, additional 7.5 MiB will be used.
Continue? [y/n/…? shows all options] (y): y
Retrieving package go1.9-doc-1.9.4-5.1.x86_64 (1/35), 2.4 MiB ( 3.8 MiB unpacked)
Retrieving: go1.9-doc-1.9.4-5.1.x86_64.rpm …[done (400.7 KiB/s)]
Retrieving package go1.9-race-1.9.4-5.1.x86_64 (2/35), 136.1 KiB (367.9 KiB unpacked)
Retrieving: go1.9-race-1.9.4-5.1.x86_64.rpm …[done (333.0 KiB/s)]
…
Retrieving package go-1.9.4-33.1.x86_64 (19/35), 52.0 KiB ( 82 B unpacked)
Retrieving: go-1.9.4-33.1.x86_64.rpm …[done (20.3 KiB/s)]
…
Retrieving package go-race-1.9.4-33.1.x86_64 (24/35), 51.8 KiB ( 82 B unpacked)
Retrieving: go-race-1.9.4-33.1.x86_64.rpm …[done]
…
Checking for file conflicts: …[done]
( 1/35) Installing: go1.9-doc-1.9.4-5.1.x86_64 …[done]
( 2/35) Installing: go1.9-race-1.9.4-5.1.x86_64 …[done]
…
19/35) Installing: go-1.9.4-33.1.x86_64 …[done]
…
(24/35) Installing: go-race-1.9.4-33.1.x86_64 …[done]
…
I have left out references to non-GO packages which were also updated.
Inspection in Yast showed that there was no change in the GO packages (still red go1.4 - go1.7, blue go1.8)
The system still showed that I have 11 software updates. When I click the [Update] button I get an immediate error message that the rpm cache could not be updated (??) Unfortunately it does not stay up long enough to copy the full message. After 3 update attempts, which resulted in the same error message, further update attempts changed to 1 update only:openSUSE-2018 235 (1) Security update for go1.8.
The resulting Update error message was:patch openSUSE-2018-235-1.noarch conflicts with go1.8-doc.x86_64
This is now much the same as when I started 2 days ago and how it has been for several months previously when I first installed GO (incorrectly I admit). Ho hum