Debian ROCm Team - APT Archive

This is the APT archive of the Debian ROCm Team. In the repository /debian, you will find packages that are either

Instructions for Users

To install packages from this repository, you need to download the archive key, and then add a sources.list entry.

The following command will download the key and save it to /usr/share/keyrings:

sudo wget -O /usr/share/keyrings/rocm-archive-keyring.gpg
# alternatively
sudo curl -o /usr/share/keyrings/rocm-archive-keyring.gpg

Then, either add the following two lines to /etc/apt/sources.list, or add these lines to a new file /etc/apt/sources.list.d/rocm.list:

deb     [signed-by=/usr/share/keyrings/rocm-archive-keyring.gpg] bookworm main
deb-src [signed-by=/usr/share/keyrings/rocm-archive-keyring.gpg] bookworm main

In the above, replace bookworm with whatever release you are targeting.

Having done that, we recommend to install the package rocm-archive-keyring. It will handle key rollovers and similar, in case this key gets updated.

Instructions for Uploaders

Please include binaries in your uploads. We don't operate an autobuilder yet.

Anyone who is (1) at least an occasional contributor to the Debian ROCm Team's packages and (2) who's GPG key is in the Web of Trust may request upload rights to this archive.

If you'd like upload rights, please send a GPG-signed email to either debian-ai AT, or ckk AT (encrypted, if you like), with the following contents:

  1. Your desired account name
  2. An attached authorized_keys file for the account

Upload is currently limited to the SFTP protocol, for the simple reason that it is really easy to lock down with OpenSSH.

To configure dput-ng for upload to this archive, create the file /.dput.d/profiles/rocm.json with the following contents:

    "fqdn": "",
    "incoming": "/incoming",
    "login": "account name you requested",
    "meta": "debian",
    "method": "sftp"

You should then be able to upload with:

dput rocm *.changes

Custom Releases

If you're a developer and you'd like to have your own release as a playground (similar to Ubuntu's ppa), send an email to one of the addresses mentioned above.

The mid-term goal is to get CI coverage for these custom releases as well, so ideally your autopkgtests will have access to broad GPU coverage.