WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@cemeceme
Copy link
Contributor

@cemeceme cemeceme commented Sep 8, 2025

Fixes #3346

The forArch function would not take into account that its parentStates are actually the correct architecture as well. Therefore, it could occur that a parentState for the wrong architecture would be used, depending on the order things were parsed. This meant it could use the wrong settings from the parent config files, by not using the correct architecture overrides.

This fix simply makes sure that the parentState is of the same architecture as requested for the subrepo, and to create it if it didn't exist.

@chrisnovakovic
Copy link
Contributor

Thanks for the PR - this looks sensible to me, but is it possible to write an e2e test to prevent future regressions?

This took me too long to notice, but also lead me to find that parsing errors get swallowed for subrepo configs.
@toastwaffle
Copy link
Contributor

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.

Cross compiling doesn't always use the correct settings for subrepos.

3 participants