bazelbuild/bazel

[bazel.build] Mutliple problems with /install/ubuntu

Open

#26,309 opened on Jun 16, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Java (4,465 forks)batch import
P2help wantedteam-Documentationteam-OSStype: documentation (cleanup)

Repository metrics

Stars
 (25,384 stars)
PR merge metrics
 (Avg merge 22d 20h) (77 merged PRs in 30d)

Description

Page link:

https://bazel.build/install/ubuntu

Problem description (include actual vs expected text, if applicable):

Hi,

the installation instructions for Debian/Ubuntu contain multiple errors:

  • The apt-transtport-https package is a dummy since Debian Stretch, as of which its functionality has been integrated into the main apt package, so its installation is useless
  • The repository keyring should NOT be stored in /usr/share/keyrings unless there's also a package available for managing the keyring going forward. If such a package doesn't exist, the keyring should be stored in /etc/apt/keyrings instead. See here for the details, where it says:

    If future updates to the certificate will be managed by an apt/dpkg package as recommended below, then it SHOULD be downloaded into /usr/share/keyrings using the same filename that will be provided by the package. If it will be managed locally , it SHOULD be downloaded into /etc/apt/keyrings instead.

Please fix.

Where do you see this issue? (include link to specific section of the page, if applicable)

https://bazel.build/install/ubuntu#install-on-ubuntu

Any other information you'd like to share?

No response

Contributor guide

Research direction
Update the Bazel installation documentation for Ubuntu/Debian to remove the apt transport https package and change the keyring location from /usr/share/keyrings to /etc/apt/keyrings, following Debian's third party repository guidelines.
Tech stack
None
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
LinuxAPT package management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85