Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DO NOT MERGE: Go142 test #91

Closed
wants to merge 4 commits into from
Closed

Conversation

mtrmac
Copy link
Collaborator

@mtrmac mtrmac commented Jun 2, 2016

Only to test #46 with #89 fixed.

@mtrmac mtrmac force-pushed the go142-test branch 2 times, most recently from 1f8e1de to d30b23c Compare June 3, 2016 21:27
@mtrmac mtrmac force-pushed the go142-test branch 6 times, most recently from ca25d07 to ec2a6aa Compare June 14, 2016 14:09
@mtrmac mtrmac force-pushed the go142-test branch 5 times, most recently from 8cf6b03 to 266d0fc Compare June 27, 2016 19:05
mtrmac added a commit to mtrmac/skopeo that referenced this pull request Jul 1, 2016
This fixes --version integration test on CentOS, as noticed by
containers#91 .  The underlying cause
is:
- Makefile builds with -ldflags "-X var=value", while go 1.4.2 only
  supports "-X var value".  This causes centOS builds to be built
  without the specific commit information
- The --version integration test assumes that commit information will
  always follow the version number.

Changing either one of these would fix the build, changing the
integration test has the advantage that we don't have to use the
obsolete -X syntax and suffer warnings on newer Go versions.
mtrmac added a commit to mtrmac/skopeo that referenced this pull request Jul 1, 2016
This fixes --version integration test on CentOS, as noticed by
containers#91 .  The underlying cause
is:
- Makefile builds with -ldflags "-X var=value", while go 1.4.2 only
  supports "-X var value".  This causes CentOS builds to be built
  without the specific commit information
- The --version integration test assumes that commit information will
  always follow the version number.

Changing either one of these would fix the build, changing the
integration test has the advantage that we don't have to use the
obsolete -X syntax and suffer warnings on newer Go versions.
@mtrmac mtrmac force-pushed the go142-test branch 2 times, most recently from 68c9ab4 to 710bbd7 Compare July 18, 2016 18:00
@mtrmac mtrmac force-pushed the go142-test branch 2 times, most recently from 6b9820f to 4c26a4d Compare July 30, 2016 15:29
@mtrmac mtrmac force-pushed the go142-test branch 3 times, most recently from 9f48bc6 to c44991a Compare August 5, 2016 17:14
This is intended for use in Travis (or perhaps also locally).  The
default behavior remains the same, uses the fedora image.

Adds various workarounds for Go 1.4; we should drop them ASAP.

(Note that the (yum install) does not fail when one of the packages
is missing.  This is not a dealbreaker, but it will make diagnosing
future bugs more difficult.)
This is currently known to fail due to
containers#89
@mtrmac
Copy link
Collaborator Author

mtrmac commented Aug 17, 2016

As of https://rhn.redhat.com/errata/RHSA-2016-1538.html / https://lists.centos.org/pipermail/centos-announce/2016-August/022005.html , CentOS has golang 1.6.3. so this is no longer relevant.

@mtrmac mtrmac closed this Aug 17, 2016
@mtrmac mtrmac deleted the go142-test branch August 17, 2016 23:23
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant