Bug 1192716 - go alternatives should prefer golang
Summary: go alternatives should prefer golang
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 26
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-14 16:18 UTC by Jan Kratochvil
Modified: 2018-05-29 12:02 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:02:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Kratochvil 2015-02-14 16:18:29 UTC
Description of problem:
Unrelated to personal preferences current Fedora Go developers develop with golang.  Installing gcc-go will unexpectedly replace /usr/bin/go with gcc-go which may take some time before one finds out.

Version-Release number of selected component (if applicable):
gcc-go-5.0.0-0.11.fc22.x86_64
golang-1.4.1-1.fc22.x86_64

How reproducible:
Always

Steps to Reproduce:
yum install golang gcc-go
alternatives --display go

Actual results:
go - status is auto.
 link currently points to /usr/bin/go.gcc
/usr/bin/go.gcc - priority 92
 slave gofmt: /usr/bin/gofmt.gcc
/usr/lib/golang/bin/linux_amd64/go - priority 90
 slave gofmt: /usr/lib/golang/bin/linux_amd64/gofmt
Current `best' version is /usr/bin/go.gcc.

Expected results:
 link currently points to /usr/lib/golang/bin/linux_amd64/go

Additional info:
Decrease the priority: 92-> 80 or so

Comment 1 Jan Kratochvil 2015-02-14 16:19:34 UTC
The workaround is:
alternatives --set go /usr/lib/golang/bin/linux_amd64/go

Comment 2 Vincent Batts 2015-06-19 19:17:21 UTC
bump. I've been hitting this a lot more lately.

Comment 3 Jan Kurik 2015-07-15 14:32:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 4 Vasiliy Glazov 2016-06-02 11:42:49 UTC
I can confirm this bug. Please fix it.

Comment 5 Fedora End Of Life 2016-11-24 11:27:05 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2016-12-20 13:14:57 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 7 Jan Kratochvil 2017-01-04 20:15:13 UTC
gcc-go-6.3.1-1.fc26.x86_64
golang-1.7.4-1.fc26.x86_64

Comment 8 Fedora End Of Life 2017-02-28 09:40:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 9 Fedora End Of Life 2018-05-03 08:52:46 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 10 Fedora End Of Life 2018-05-29 12:02:33 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.