June 2016 - openSUSE Go - openSUSE Mailing Lists

[opensuse-go] revert some changes to support SLE11
by Marguerite Su 30 Jun '16

30 Jun '16

Hi, I'm afraid I'll have to revert some of my previous "simplify rpmsysinfo.rb" work to support SLE11 again. The problem is not "RbConfig" this time, it's 'ENV["RPM_BUILD_ROOT"]". The environment variable is not avaiable at Provides/Requires finding stage. Here's my test: Add "ruby /usr/lib/rpm/golang.prov" right after "%goinstall", it generates: buildroot: /var/tmp/golang-github-shurcool-sanitized_anchor_name-0.0.0+git20151027.10ef21a-build contribdir: /usr/lib64/go/contrib/pkg/linux_amd64 So "buildroot + contribdir + '/'" should have valid value. But in the Provides/Requires finding stage of SLE_11_SP3, it still complains: /usr/lib/rpm/golang.prov:9:in `+': can't convert nil into String (TypeError) Which means "buildroot" doesn't have any value at that stage. So I have to say the previous "guess buildroot" process still have to remain there although it may look redudant. That is, any environment variable directly from SYSTEM or Ruby is safe, while those depends on RPM is not, at least in SLE_11_SP3. Keep that in mind. Marguerite -- To unsubscribe, e-mail: opensuse-go+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-go+owner(a)opensuse.org

1 0

[opensuse-go] Added new macro to disable binary stripping within golang packages
by Thomas Boerger 28 Jun '16

28 Jun '16

Hi, I just want to inform you that I have created a new macro named go_nostrip at https://github.com/openSUSE/golang-packaging/pull/3. This macro should be used within the packages which use golang-packaging to disable the stripping of golang binaries to avoid issues related to that. Beside that it disables also useless debug sub-packages. So if you create a package for some golang related tool please use this macro. Under the hood it just calls one undefine and one define: %undefine _build_create_debug %define __arch_install_post export NO_BRP_STRIP_DEBUG=true If you want to know more about those options read https://en.opensuse.org/openSUSE:Packaging_guidelines#Debuginfo and https://github.com/golang/go/issues/1242. Best, Thomas Boerger -- Thomas Boerger <tboerger(a)suse.de> Docker Developer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

3 2

[opensuse-go] Remove runtime dependency for golang(API)?
by Marguerite Su 22 Jun '16

22 Jun '16

Hi, I've been AFKed for a while so didn't catch up with the fork and recent commits. I'm ok with the fork, it gives me access to openSUSE organization. But actually I'm a little mad with the package updates...someone has brought this kind of behavior on ML once...while I am the author of a project and the only maintainer for a package, suddenly I see my release schedule, versioning scheme and control over my package was totally altered by just leaving a note, from upstream to downstream. 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 didn't see any respect and open discussion here actually. Newbies for go still have their rights to go, gentlemen. Complaint is over. Bad things just happen everyday. Let's go back to the codes to carry on. While I think I knew golang libraries are statically built when I introduced those runtime requirements. (The commit message makes me feel I didn't write main function in a 10-line C program) It was not to bring go itself in (although there was such side effect) but for ABI consistency. Back when I updated golang from 1.3 to 1.4, I noticed those: OBS will not rebuilt all golang stuff after the main go's version bumps. >From time to time there're failed states in openSUSE:Factory for 3rd-party golang libraries. If A depends on B, when B is updated, A will not get rebuilt, not like the standard behavior for C/C++. So I have to update A too to fix the failure which can be resolved by an automatical rebuild. So this is it: if golang updates to 1.7, all 3rd-party golang libraries will still explicitly require golang 1.6 in my design. Then when you build another golang programs depend on one of those libraries. 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. 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. Marguerite -- To unsubscribe, e-mail: opensuse-go+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-go+owner(a)opensuse.org

6 22

[opensuse-go] golang_packaging and nodebuginfo
by Aleksa Sarai 07 Jun '16

07 Jun '16

Hi all, After quite a bit of experimentation, we managed to figure out what incantations are necessary to build a binary in OBS without stripping the debug information from it (this is necessary for Go binaries because of known issues with the Go runtime). You just have to add the following lines to before %pre: %undefine _build_create_debug %define __arch_install_post export NO_BRP_STRIP_DEBUG=true So, the question is how we should go about adding these incantations to golang_packaging (so all Go packages can avoid this problem). It might be as simple as adding a %go_init macro that does this for us (or even have an automatically inserted macro). Thanks. -- Aleksa Sarai Software Engineer (Containers) SUSE Linux GmbH https://www.cyphar.com/ -- To unsubscribe, e-mail: opensuse-go+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-go+owner(a)opensuse.org

1 0

[opensuse-go] simplify rpmsysinfo.rb
by Marcus Rückert 07 Jun '16

07 Jun '16

1. why not hook onto RbConfig::CONFIG['libdir']? it has the value for us already :) then only the goarch stuff would need to be in the conditional 2. we could get the BUILDROOT and stuff from the environment ... no need to guess it. or am I missing something? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-go+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-go+owner(a)opensuse.org

4 6