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

Final batch of fixes for Noble support. #769

Merged
merged 3 commits into from
Apr 16, 2024

Conversation

clalancette
Copy link
Contributor

@clalancette clalancette commented Apr 8, 2024

With this batch of fixes, we can now successfully build Rolling on Noble. See the individual commits for more information about why we need each of the changes.

@clalancette
Copy link
Contributor Author

clalancette commented Apr 8, 2024

  • Linux Build Status
  • Linux-aarch64 Build Status

@clalancette clalancette force-pushed the clalancette/proposed-arm64 branch 2 times, most recently from 3d21fd3 to decbba6 Compare April 8, 2024 14:41
@clalancette clalancette force-pushed the clalancette/proposed-arm64 branch 4 times, most recently from 7a74a8d to cbb451a Compare April 11, 2024 15:11
@clalancette
Copy link
Contributor Author

clalancette commented Apr 15, 2024

Here's new CI, now that we think flake8 is fixed upstream:

  • Linux Build Status
  • Linux-aarch64 Build Status

Since we now depend on having updated apt packages, make sure
we invalidate before all of the installation.  This ensures
we have up-to-date packages.

Signed-off-by: Chris Lalancette <clalancette@gmail.com>
The flake8 packages we need have finally landed in
the normal noble repositories, so we no longer need
the hack.

Signed-off-by: Chris Lalancette <clalancette@gmail.com>
They will automatically get pulled in by the development
packages.  This works around a potential problem on
Noble aarch64 where the package names are now different
because of the t64 changes.

Signed-off-by: Chris Lalancette <clalancette@gmail.com>
@clalancette clalancette changed the title We need to use "ports" for aarch64. Final batch of fixes for Noble support. Apr 15, 2024
@clalancette clalancette marked this pull request as ready for review April 15, 2024 23:54
@clalancette
Copy link
Contributor Author

Here's a bunch of different CI to validate this change:

Rolling on Noble:

  • Linux Build Status
  • Linux-aarch64 Build Status

Rolling on Jammy:

  • Linux Build Status
  • Linux-aarch64 Build Status

Iron on Jammy:

  • Linux Build Status
  • Linux-aarch64 Build Status

Humble on Jammy:

  • Linux Build Status
  • Linux-aarch64 Build Status

Copy link
Member

@nuclearsandwich nuclearsandwich left a comment

Choose a reason for hiding this comment

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

I would prefer this to be rebase-merged rather than squash-merged to maintain the three independent (and well-written) commit messages.

@clalancette
Copy link
Contributor Author

I'm going to go ahead and merge this one in. Thanks for the review.

@clalancette clalancette merged commit ff985d7 into master Apr 16, 2024
1 check passed
@delete-merged-branch delete-merged-branch bot deleted the clalancette/proposed-arm64 branch April 16, 2024 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants