YES, I didn't reply in time. But in that hurry? better not. it's not urgent security updates, but some cleaning work (I doubt).
I appreciate the work you did for packaging Go programs, and AFAIK you're still the maintainer for that project. The reason for the fork was because *every Go package in OBS was broken*. The issue was that the golang(API) generation script accidentally generated the wrong version (I think it generated 1.6 when it should've been 1.6.1, or something like that). Since we didn't have go=1.6 packaged (but we did have go=1.6.1), things broke badly.
I didn't see any respect and open discussion here actually. Newbies for go still have their rights to go, gentlemen.
We didn't mean to disrespect you, we just wanted to fix the fact that the entire build system for Go-based packages was temporarily broken (and this was all happening near the release of a few Go-based packages for openSUSE). IIRC @flavio made you a maintainer of the new project anyway -- if not, I'm sure they would be happy to make you one.
It will get an "unresolvable" error. Very Clear. Instead of processing the build and failing somewhere random because of using go 1.7 and some go libraries built against go 1.6.
Can you explain what you mean by "go libraries"? Since everything is statically compiled or vendored by the project itself (in most cases), what libraries are you referring to? AFAIK proper shared library support is still an RFC for the Go project (I can't find the link at the moment, but I remember reading an RFC for it a while ago).
Unless we can get a solution, either to fix from OBS side or prevent those situations better, we can not just omit the codes I wrote.
I actually am not against the original code written (and thought that the ABI locking was a good idea), we just had to hotfix it because we couldn't build or release any Go-based packages for a few days. A better fix would be to figure out why the golang(API) macro generation produced the wrong version value, and fix _that_. Or maybe just check that the major-minor versions are the same for the compiler? The version checks are too strict given that it seems that Go doesn't bump their API version with each patchlevel release. -- Aleksa Sarai Software Engineer (Containers) SUSE Linux GmbH https://www.cyphar.com/ -- To unsubscribe, e-mail: opensuse-go+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-go+owner@opensuse.org