Skip to content

docs: warn about missing noble-updates/backports on Ubuntu 24 installs#6854

Merged
fujitatomoya merged 1 commit into
ros2:kiltedfrom
Supull:fix/ubuntu-noble-apt-sources
May 24, 2026
Merged

docs: warn about missing noble-updates/backports on Ubuntu 24 installs#6854
fujitatomoya merged 1 commit into
ros2:kiltedfrom
Supull:fix/ubuntu-noble-apt-sources

Conversation

@Supull
Copy link
Copy Markdown

@Supull Supull commented May 23, 2026

Closes #6853

On Ubuntu 24.04 installs, the apt sources may only include the base noble suite which causes this error when installing ros-dev-tools:

bzip2 : Depends: libbz2-1.0 (= 1.0.8-5.1) but 1.0.8-5.1build0.1 is to be installed
E: Unable to correct problems, you have held broken packages.

Added a warning block with steps to check and fix the apt sources before proceeding with the installation.

Did you use Generative AI?

No

Copy link
Copy Markdown
Collaborator

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

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

@Supull thanks for creating PR.

should this be applied only to ubuntu noble based distro, means kilted and jazzy? in that case, we could target this PR to kilted and then backport jazzy? so that we do not need to add this note for rolling, lyrical and humble.

@Supull Supull changed the base branch from rolling to kilted May 24, 2026 06:17
@Supull Supull force-pushed the fix/ubuntu-noble-apt-sources branch from 17811e3 to d5dc880 Compare May 24, 2026 06:30
@Supull
Copy link
Copy Markdown
Author

Supull commented May 24, 2026

Sorry for the confusion with the new PR. I've cleaned up the branch and force pushed a single clean commit targeting kilted as suggested, to this.

@Supull
Copy link
Copy Markdown
Author

Supull commented May 24, 2026

Should I create a separate PR to backport this fix to jazzy or would you prefer a different way?

@fujitatomoya
Copy link
Copy Markdown
Collaborator

Should I create a separate PR to backport this fix to jazzy or would you prefer a different way?

No we do not need that. once we merge this into kilted, we can backport with using Mergifyio from this PR.

@fujitatomoya fujitatomoya added the backport-jazzy backport at reviewers discretion; from rolling to jazzy label May 24, 2026
@fujitatomoya fujitatomoya enabled auto-merge (squash) May 24, 2026 08:45
@fujitatomoya fujitatomoya merged commit 36e5fd6 into ros2:kilted May 24, 2026
7 checks passed
@Supull
Copy link
Copy Markdown
Author

Supull commented May 24, 2026

Thanks a lot for the review.

@fujitatomoya
Copy link
Copy Markdown
Collaborator

@Mergifyio backport jazzy

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 24, 2026

backport jazzy

✅ Backports have been created

Details

fujitatomoya pushed a commit that referenced this pull request May 24, 2026
#6854) (#6856)

(cherry picked from commit 36e5fd6)

Co-authored-by: Retroqd <supulbaddegama@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-jazzy backport at reviewers discretion; from rolling to jazzy

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ROS2 Kilted on Ubuntu 24 server, change of ubuntu source, bricks ros-dev-tools

2 participants