-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Linux aarch64 - ros_core, ros_base, perception, simulation, desktop, desktop_full #209
Conversation
Thanks for this, @sonelu! What's the plan of attack in general? Do you want to try to rebuild all packages that are currently selected? |
If you don't have any other strategy you can just let the PRs build. I've created them separately by platform, and I will come with additional PRs for OSX and WIN as I am able to test them locally to reduce the impact on CI. After this we can add the additional packages as needed. I was thinking to get a python script that pulls the download numbers from Anaconda for packages in robostack-staging and we can tackle them in order of interest. |
All of the packages that are selected currently have been requested by users, so I'd like to keep them all if possible. The ideal PR would basically just increase the build numbers and update / create new patches if needed :) |
See #229 |
All tested locally and ready to go.