https://bugzilla.redhat.com/show_bug.cgi?id=1394575
Athos Ribeiro <athoscribeiro(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |NOTABUG
Flags|needinfo?(athoscribeiro@gma |
|il.com) |
Last Closed| |2017-02-27 12:41:07
--- Comment #2 from Athos Ribeiro <athoscribeiro(a)gmail.com> ---
(In reply to Jan Chaloupka from comment #1)
These days I lack reviewers and go package maintainers. So most of
the
packages are in a state of flux.
I see. the commit driven dependency might be a problem at some point, whenever
two packages require different commits of a project. In this case, the action
would be to update the upstream depending on the older commit, right?
To your question. As most of go projects refer to dependency commit
and not
its version, all the dependency updates are commit driven. So it is enough
to provide particular commit. Which one are you interested in?
2b0166c3d4caae7d9b27290da81e3c3c680088a2 or newer?
I believe it is already in rawhide though, I am closing this now. Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.