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.

Sign up for GitHub

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

Jump to bottom

v3.2.0-arm64 release #8085

Closed
glevand opened this issue Jun 12, 2017 · 2 comments
Closed

v3.2.0-arm64 release #8085

glevand opened this issue Jun 12, 2017 · 2 comments

Comments

@glevand
Copy link
Contributor

glevand commented Jun 12, 2017 •
edited
Loading

There doesn't seem to be any arm64 release of v3.2.0 in either github or quay.io. PR #7714 (add multi-arch support in release binaries) should have made that possible.

rkt's TestFetchAny functional test uses etcd images, so to fix that for arm64 I need arm64 releases of etcd to at least the github downloads. See https://github.com/rkt/rkt/blob/master/tests/rkt_fetch_test.go#L93.
@gyuho
Copy link
Contributor

gyuho commented Jun 13, 2017

@glevand We will include those builds from 3.2.1+.
I should have communicated earlier.
Thanks!

@glevand
Copy link
Contributor Author

glevand commented Jun 13, 2017

@gyuho OK. Just to mention it here, the v3.2.0-rc.1 release was missing the pgp signature file for the arm64 aci image, so please include it in 3.2.1. The rkt tests will fail without that.

Thanks.

@glevand glevand closed this as completed Jun 13, 2017
gyuho added a commit to gyuho/etcd that referenced this issue Jun 20, 2017
@gyuho
Documentation/release: sign *.aci files
ca6d7bd 
Thanks to
etcd-io#8085 (comment).

Signed-off-by: Gyu-Ho Lee <gyuhox@gmail.com>
@gyuho gyuho mentioned this issue Jun 20, 2017
Merged
yudai pushed a commit to yudai/etcd that referenced this issue Oct 5, 2017
@gyuho
Documentation/release: sign *.aci files
95ddcbb 
Thanks to
etcd-io#8085 (comment).

Signed-off-by: Gyu-Ho Lee <gyuhox@gmail.com>
@glevand glevand mentioned this issue Jan 3, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gyuho @glevand