Bug 1394575

Summary: unicode/precis is now secure/precis
Product: [Fedora] Fedora Reporter: Athos Ribeiro <athoscribeiro>
Component: golang-googlecode-textAssignee: Fridolín Pokorný <fpokorny>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: athoscribeiro, fpokorny, golang-updates, jchaloup, lsm5, vbatts
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-27 17:41:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Athos Ribeiro 2016-11-13 19:39:03 UTC 
unicode/precis was moved to secure/precis. See [1] and [2]

Meaning that packages requiring golang(golang.org/x/text/secure/precis) would need this package to be updated.

packages requiring golang(golang.org/x/text/unicode/precis) would need to have upstream updated.

[1] https://github.com/golang/text/commit/2b0166c3d4caae7d9b27290da81e3c3c680088a2 
[2] https://go-review.googlesource.com/#/c/19157/

Since this is not in golang core, how is this being tracked upstream, since the package does not have versions?
Comment 1 Jan Chaloupka 2017-02-27 11:28:54 UTC 
These days I lack reviewers and go package maintainers. So most of the packages are in a state of flux.

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?
Comment 2 Athos Ribeiro 2017-02-27 17:41:07 UTC 
(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!
Comment 3 Jan Chaloupka 2017-02-28 11:06:13 UTC 
> 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? 

We already hit the problem from time to time. Yeah, either update the upstream dependency or try to patch the current one.