According to the installation instructions at https://github.com/mattn/go-colorable the correct import path for go-colorable is: github.com/mattn/go-colorable But, the spec for the Fedora package only provides gopkg.in/mattn/go-colorable.v1 This doesn't appear to be a valid import path at all (only v0 actually works, because of the available tags on the repository; try to "go get" that URL, and you'll see what I mean), and isn't referenced anywhere in the documentation. It looks like this was added during package review, but the external expectation for the import path seems to be the github URL; see https://github.com/mgutz/ansi/blob/master/print.go as an example of this in the wild.
golang-github-mattn-go-colorable-0-0.4.20170816gitad5389d.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-bf5e7f8700
I'm very sorry about this, it seems it slipped through. I've pushed fixes for all fedora releases
golang-github-mattn-go-colorable-0-0.4.20170816gitad5389d.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-bf5e7f8700
golang-github-mattn-go-colorable-0-0.5.20170816gitad5389d.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-1767a27810
golang-github-mattn-go-colorable-0-0.5.20170816gitad5389d.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-1767a27810
golang-github-mattn-go-colorable-0-0.5.20170816gitad5389d.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.