Article 4ZQ70 My Opensuse give wrong package info for golang.

My Opensuse give wrong package info for golang.

by
hottdogg
from LinuxQuestions.org on (#4ZQ70)
I am running OpenSuse Leap 15.1.
I want to update my go programming language pacage from 1.11 to the latest what the repo have.
But the system said it's already updated the go package where in fact it's not.

Code:# zypper refresh; zypper update go
Repository 'Visual Studio Code' is up to date.
Repository 'dbserver' is up to date.
Repository 'libdvdcss' is up to date.
Repository 'openSUSE-Leap-15.1-1' is up to date.
Repository 'packman' is up to date.
Repository 'Non-OSS Repository' is up to date.
Repository 'Main Repository' is up to date.
Repository 'Main Update Repository' is up to date.
Repository 'Update Repository (Non-Oss)' is up to date.
Repository 'Databases (openSUSE_Leap_15.1)' is up to date.
Repository 'snappy' is up to date.
All repositories have been refreshed.
Loading repository data...
Reading installed packages...
No update candidate for 'go-1.12-lp151.2.3.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...

Nothing to do.Code:#zypper info go
Loading repository data...
Reading installed packages...

Information for package go:
---------------------------
Repository : Main Update Repository
Name : go
Version : 1.12-lp151.2.3.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 82 B
Installed : Yes
Status : up-to-date
Source package : go-1.12-lp151.2.3.1.src
Summary : A compiled, garbage-collected, concurrent programming language
Description : ...Code:# go version
go version go1.11.13 linux/amd64Anyone knows what's the best solution for this?
Thank youlatest?d=yIl2AUoC8zA latest?i=qT-F42yg2t0:nkRfP1bexGI:F7zBnMy latest?i=qT-F42yg2t0:nkRfP1bexGI:V_sGLiP latest?d=qj6IDK7rITs latest?i=qT-F42yg2t0:nkRfP1bexGI:gIN9vFwqT-F42yg2t0
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments