[bazel.build] Problem with /install/ubuntu
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 72
Description
### Page link:
https://bazel.build/install/ubuntu
### Problem description (include actual vs expected text, if applicable):
Mainly this step here could lead to incorrect permission when generating the GPG key to be used by apt
```
sudo apt install apt-transport-https curl gnupg -y
curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
echo "deb [arch=amd64 signed-by=/usr/share/keyrings/bazel-archive-keyring.gpg] https://storage.googleapis.com/bazel-apt stable jdk1.8" | sudo tee /etc/apt/sources.list.d/bazel.list
```
For my case it will create a file like that
`-rw-rw---- 1 jose-vilarouca-filho jose-vilarouca-filho 3421 Jul 9 16:48 bazel-archive-keyring.gpg`
With these permission I got the following error when running `apt update`
```
W: GPG error: https://storage.googleapis.com/bazel-apt stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3D5919B448457EE0
E: The repository 'https://storage.googleapis.com/bazel-apt stable InRelease' is not signed.
```
So I changed the permissions to match the permission from files inside `/usr/share/keyrings`
```
-rw-r--r-- 1 root root 3421 Jul 9 16:48 bazel-archive-keyring.gpg
-rw-r--r-- 1 root root 641 Jan 29 09:15 microsoft.gpg
-rw-r--r-- 1 root root 7399 Sep 18 2018 ubuntu-archive-keyring.gpg
-rw-r--r-- 1 root root 6713 Okt 27 2016 ubuntu-archive-removed-keys.gpg
-rw-r--r-- 1 root root 3023 Mär 27 2021 ubuntu-cloudimage-keyring.gpg
-rw-r--r-- 1 root root 0 Jan 17 2018 ubuntu-cloudimage-removed-keys.gpg
-rw-r--r-- 1 root root 1227 Mai 27 2010 ubuntu-master-keyring.gpg
-rw-r--r-- 1 root root 1846 Apr 9 2020 ubuntu-oem-keyring.gpg
-rw-r--r-- 1 root root 0 Feb 11 2020 ubuntu-oem-removed-keys.gpg
-rw-r--r-- 1 root root 1150 Apr 30 22:35 ubuntu-pro-anbox-cloud.gpg
-rw-r--r-- 1 root root 2247 Apr 30 22:35 ubuntu-pro-cc-eal.gpg
-rw-r--r-- 1 root root 2274 Apr 30 22:35 ubuntu-pro-cis.gpg
-rw-r--r-- 1 root root 2236 Apr 30 22:35 ubuntu-pro-esm-apps.gpg
-rw-r--r-- 1 root root 2264 Apr 30 22:35 ubuntu-pro-esm-infra.gpg
-rw-r--r-- 1 root root 2275 Apr 30 22:35 ubuntu-pro-fips.gpg
-rw-r--r-- 1 root root 2275 Apr 30 22:35 ubuntu-pro-fips-preview.gpg
-rw-r--r-- 1 root root 2250 Apr 30 22:35 ubuntu-pro-realtime-kernel.gpg
-rw-r--r-- 1 root root 2235 Apr 30 22:35 ubuntu-pro-ros.gpg
```
This solve the issue. The error message is no easy to lead to the problem so maybe it`d be great to point this out in the documentation.
### Where do you see this issue? (include link to specific section of the page, if applicable)
https://bazel.build/install/ubuntu#add-dis-uri
### Any other information you'd like to share?
```
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
```
Contributor guide
Research direction
Start at the Ubuntu installation page's “Add the distribution” section and review the GPG key-generation and repository setup commands described in the issue. Confirm the documented steps account for the keyring permissions, then verify that the resulting instructions allow apt update to recognize the Bazel repository without the reported NO_PUBKEY error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ubuntu
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100