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

Change defaulting of TARGETARCH #13

Merged
merged 1 commit into from
Oct 8, 2021
Merged

Change defaulting of TARGETARCH #13

merged 1 commit into from
Oct 8, 2021

Conversation

ciaranmcnulty
Copy link
Collaborator

This doesn't actually work - it prevents the TARGETARCH being populated. I suspect buildkit implements it as a default, then this overrides the default

@asgrim asgrim added the bug Something isn't working label Oct 8, 2021
@asgrim asgrim added this to the 1.1.1 milestone Oct 8, 2021
@asgrim asgrim changed the base branch from 1.2.x to 1.1.x October 8, 2021 13:10
@asgrim
Copy link
Member

asgrim commented Oct 8, 2021

changed base to 1.1.x since I'd class this as a bugfix to 1.1.0 :)

@asgrim
Copy link
Member

asgrim commented Oct 8, 2021

@Ocramius does Laminas/AutomaticReleases automatically create a PR to forward-port fixes to the default branch?

@Ocramius
Copy link
Member

Ocramius commented Oct 8, 2021

@asgrim it should, yes

The default argument doesn't actually work - it prevents the TARGETARCH being populated. I suspect buildkit implements it as a default, then this overrides the default
@ciaranmcnulty ciaranmcnulty changed the title Remove default TARGETARCH Change defaulting of TARGETARCH Oct 8, 2021
@asgrim asgrim merged commit fb0c0e3 into Roave:1.1.x Oct 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants