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

build: Patch boost install checksum mismatch error #6520

Conversation

wpmobilebot
Copy link
Collaborator

Related PRs

Description

This PR is generated by version-toolkit to downstream the changes for gutenberg submodule.

@fluiddot fluiddot added this to the 1.111.0 (24.1) milestone Jan 9, 2024
Copy link
Contributor

@fluiddot fluiddot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fluiddot
Copy link
Contributor

fluiddot commented Jan 9, 2024

Some of the CI jobs are failing due to not being able to checkout the Gutenberg repository (reference):

fatal: repository '../../WordPress/gutenberg.git' does not exist

The error seems unrelated to these changes. I'll create a different branch to confirm if this can be reproduced in trunk.

@fluiddot
Copy link
Contributor

fluiddot commented Jan 9, 2024

Some of the CI jobs are failing due to not being able to checkout the Gutenberg repository (reference):

fatal: repository '../../WordPress/gutenberg.git' does not exist

The error seems unrelated to these changes. I'll create a different branch to confirm if this can be reproduced in trunk.

I encountered the same error on a different PR (reference), so this looks like an actual issue in CI and Buildkite.

@fluiddot fluiddot merged commit a100078 into trunk Jan 10, 2024
16 of 19 checks passed
@fluiddot fluiddot deleted the version-toolkit/gutenberg/fix/patch-boost-install-checksum-mistmatch-error branch January 10, 2024 10:05
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.

None yet

2 participants