Skip to content

Commit 5df5e9c

Browse files
skill-based updates
1 parent 1aa05c1 commit 5df5e9c

1 file changed

Lines changed: 29 additions & 29 deletions

File tree

content/install-guides/arm-toolchains-repository.md

Lines changed: 29 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ test_images:
1717
- ubuntu:latest
1818

1919
official_docs: https://developer.arm.com/tools-and-software
20-
description: Configure the Arm Toolchains repository for Linux package archive on supported Linux AArch64 distributions to enable installing Arm Toolchains products using the system package manager.
20+
description: Configure the Arm Toolchains repository on supported Linux aarch64 distributions to install Arm Toolchain for Linux and Arm Performance Libraries using the system package manager.
2121
author: Gary Carroll
2222

2323
weight: 1 # Defines page ordering. Must be 1 for first (or only) page.
@@ -66,11 +66,11 @@ Use the native package manager for your distribution:
6666
- `dnf` or `yum` for RHEL 8 or later and Amazon Linux 2023
6767
- `zypper` for SLES 15 or 16
6868

69-
## About the signing key
69+
## About the signing key
7070

7171
Linux package managers use cryptographic signing keys to verify that repository metadata and packages are authentic and come directly from Arm.
7272

73-
In July 2026, Arm reviewed and strengthened the repository management and publication processes used for the Arm Toolchains repository. As part of the continuing evolution of this release channel, Arm has revoked and replaced the signing key.
73+
In July 2026, Arm reviewed and strengthened the repository management and publication processes used for the Arm Toolchains repository. As part of the continuing evolution of this release channel, Arm revoked and replaced the signing key.
7474

7575
If you're setting up a new system after July 2026, installing the `arm-toolchains-repository` package automatically configures the current repository signing key for you. You don't need to install the key manually or verify fingerprints.
7676

@@ -95,7 +95,7 @@ Current fingerprint:
9595
A406 5BCE 9386 DD1E 62FD E03B 8144 CA16 11A0 BD71
9696
```
9797

98-
### (Optional) Manually verifying the signing key
98+
### (Optional) Manually verify the signing key
9999

100100
If you want to manually verify the signing key, ensure the `gpg` utility (part of GnuPG) is installed on your system, then download the key file and display its fingerprint:
101101

@@ -112,7 +112,7 @@ A406 5BCE 9386 DD1E 62FD E03B 8144 CA16 11A0 BD71
112112

113113
## Previous repository locations
114114

115-
The current Arm Toolchains Linux Repository at [https://developer.arm.com/packages/arm-toolchains/](https://developer.arm.com/packages/arm-toolchains/) replaces the earlier repository structure that was based on repositories built using the SUSE Open Build Service.
115+
The current Arm Toolchains repository at [https://developer.arm.com/packages/arm-toolchains/](https://developer.arm.com/packages/arm-toolchains/) replaces the earlier repository structure that was based on repositories built using the SUSE Open Build Service.
116116

117117
Earlier repositories were published under the top-level package URL [https://developer.arm.com/packages/](https://developer.arm.com/packages/) and used repository prefixes such as:
118118

@@ -127,30 +127,6 @@ Don't configure new systems to use the deprecated `ACfL:` or `arm-toolchains:` r
127127

128128
The deprecated repositories will be removed in a future update.
129129

130-
## Expected package manager errors
131-
132-
If your system still trusts only the previous Arm Toolchains Repository signing key, package manager operations might fail when you refresh metadata, install packages, or upgrade packages.
133-
134-
Ubuntu hosts might experience errors running the `apt update` command, for example:
135-
136-
```output
137-
Err:1 https://developer.arm.com/packages/arm-toolchains/ubuntu noble InRelease
138-
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY <key-id>
139-
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: <error>
140-
W: Some index files failed to download. They have been ignored, or old ones used instead.
141-
```
142-
143-
RPM based hosts might download the new signing key but refuse to use it:
144-
145-
```output
146-
The GPG keys listed for the "Arm Toolchains" repository are already installed but they are not correct for this package.
147-
Check that the correct key URLs are configured for this repository..
148-
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-arm-toolchains
149-
Error: GPG check FAILED
150-
```
151-
152-
To resolve these errors, install the updated repository package and accept the new signing key.
153-
154130
## Install the repository package directly
155131

156132
Use one of the following commands to install the repository package [directly](https://developer.arm.com/packages/arm-toolchains/). This allows you to update the repository configuration even if your package manager can't currently refresh the Arm Toolchains repository metadata.
@@ -319,6 +295,30 @@ rpm -q arm-toolchains-repository
319295

320296
The installed version should be `2-2` or later.
321297

298+
## Troubleshoot package manager errors
299+
300+
If your system still trusts only the previous Arm Toolchains Repository signing key, package manager operations might fail when you refresh metadata, install packages, or upgrade packages.
301+
302+
Ubuntu hosts might experience errors running the `apt update` command, for example:
303+
304+
```output
305+
Err:1 https://developer.arm.com/packages/arm-toolchains/ubuntu noble InRelease
306+
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY <key-id>
307+
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: <error>
308+
W: Some index files failed to download. They have been ignored, or old ones used instead.
309+
```
310+
311+
RPM-based hosts might download the new signing key but refuse to use it:
312+
313+
```output
314+
The GPG keys listed for the "Arm Toolchains" repository are already installed but they are not correct for this package.
315+
Check that the correct key URLs are configured for this repository..
316+
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-arm-toolchains
317+
Error: GPG check FAILED
318+
```
319+
320+
To resolve these errors, install the updated repository package and accept the new signing key.
321+
322322
## Next steps
323323

324324
After installing the repository package, you're ready to install the Arm Toolchain for Linux and the Arm Performance Libraries.

0 commit comments

Comments
 (0)