-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Create Humble Branch from Rolling #32784
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved not to merge, but to use as the basis for the humble migration.
The errors in tests are due to conflicts with requirements from the migration tool and that of the other tests which are run. These conflicts vanish once the distribution has any content.
Signed-off-by: Audrow Nash <audrow@hey.com>
Signed-off-by: Audrow Nash <audrow@hey.com>
Signed-off-by: Audrow Nash <audrow@hey.com>
For this run the primary cause is actually that the release was still missing in Rolling after the Jammy migratio (#32036). rosdep resolution failure for any platform, including RHEL 8 and Debian Bullseye can block the migration script which has no way to know which platforms are "critical" and which aren't. So we can restore a good few of these with a normal manual bloom-release after the migration. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There were similar migration failures as there were with the previous migration on Rolling and some additional (and expected failures) due to patches not migrating fully when the distro name changes and with some changes to templates brought with bloom 0.11.0 used in this migration.
Once this has merged we can begin addressing some of the failures with the regular bloom workflow which needs a human operator.
The first steps in creating a new branch for Humble Hawksbill from Rolling.
Migration command:
31 failed to bloom successfully. This is most frequently caused by missing rosdep dependencies.