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

Use latest versions of config.guess and config.sub #10

Closed

Conversation

lag-linaro
Copy link

They have the most up-to-date features and support a greater number of devices.

Signed-off-by: Lee Jones lee.jones@linaro.org

They have the most up-to-date features and support a
greater number of devices.

Signed-off-by: Lee Jones <lee.jones@linaro.org>
@lag-linaro lag-linaro mentioned this pull request Jul 12, 2018
@lag-linaro
Copy link
Author

These files have been updated in the upstream repo now.

Once updated/rebased, this can be closed.

Signed-off-by: Lee Jones <lee.jones@linaro.org>
@vanosg
Copy link
Member

vanosg commented Sep 27, 2018

Support added via upstream, and the official-images repo- thanks again for pointing this out!

@vanosg vanosg closed this Sep 27, 2018
@vanosg vanosg reopened this Sep 27, 2018
@vanosg
Copy link
Member

vanosg commented Sep 27, 2018

Jumped the gun on this- the alt keyservers component is very important, thanks

@tianon
Copy link

tianon commented Oct 1, 2018

Regarding alternate keyservers, see docker-library/official-images#4252, especially docker-library/official-images#4252 (comment) (docker-library/php#666).

@vanosg
Copy link
Member

vanosg commented Oct 2, 2018

Thanks for that pointer, @tianon!

@vanosg vanosg closed this Oct 2, 2018
@vanosg
Copy link
Member

vanosg commented Oct 2, 2018

@lag-linaro just to update you (and anyone else interested) - the develop branch has this support added in the core upstream code, and will eventually merge to the 1.8 branch line as part of 1.8.4. Once 1.8.4 is released, we'll enable arm64 support to that image as well, but for now only the develop branch will have it. For configuration control purposes, we're interested in keeping the codebase the same between docker and source code. If you can make a strong case as why we need to break this now versus in a month or so when .4 releases, I'm happy to entertain your comments! Thanks again for being such a driving force in getting us to integrate this much-needed feature into the codebase.

@lag-linaro
Copy link
Author

One month will be fine. No need to break your workflow.

You are more than welcome. Thank you for being so receptive and responsive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants