Skip to content

package-repositories

Repositories to use to install packages from

This provides a list of repositories to install packages from. It includes dedicated OS installation repositories and more general ones.

An example:

YAML
- tag: "rocky-10-install" # Every repository needs a unique tag.
  # A repository can be used by multiple operating systems.
  # The usual example of this is the EPEL repository, which
  # can be used by all of the RHEL variants of a given generation.
  os:
    - "rocky-10"
  # We also need to know what system architecture this repo is for.
  # If this repo is valid for all arches (like a Debian or Ubuntu
  # mirror), this can be set to "any", although it cannot be
  # an installSource if that is the case
  arch: x86_64
  # If installSource is true, then the URL points directly
  # to the location we should use for all OS install purposes
  # save for fetching kernel/initrd pairs from (for now, we will
  # still assume that they will live on the DRP server).
  # When installSounrce is true, the os field must contain a single
  # entry that is an exact match for the bootenv's OS.Name field.
  installSource: true
  # For redhat-ish distros when installSource is true,
  # this URL must contain distro, component, and arch components,
  # and as such they do not need to be further specified.
  url: "https://dl.rockylinux.org/pub/rocky/10/BaseOS/x86_64/os/"
- tag: "rocky-10-everything"
  # Since installSource is not true here,
  # we can define several package sources at once by
  # providing a distribution and a components section,
  # and having the URL point at the top-level directory
  # where everything is housed.
  # DRP knows how to expand repo definitions for RHEL-clone
  # distros (Rocky, AlmaLinux, etc.) provided that they follow
  # the standard mirror directory layout for each distro.
  os:
    - rocky-10
  arch: any
  url: "https://dl.rockylinux.org/pub/rocky/"
  distribution: "10"
  components:
    - AppStream
    - BaseOS
    - CRB
    - HighAvailability
    - RT
    - devel
    - plus
    - extras
- tag: "debian-13-install"
  os:
    - "debian-13"
  arch: amd64
  installSource: true
  # Debian URLs always follow the same rules, no matter
  # whether the OS install flag is set.  As such,
  # you must always also specify the distribution and
  # at least the main component, although you can also
  # specify other components.
  url: "http://deb.debian.org/debian/"
  distribution: trixie
  components:
    - main
    - contrib
    - non-free
    - non-free-firmware
- tag: "debian-13-updates"
  os:
    - "debian-13"
  arch: any
  url: "http://deb.debian.org/debian/"
  distribution: trixie-updates
  components:
    - main
    - contrib
    - non-free
    - non-free-firmware
- tag: "debian-13-security"
  os:
    - "debian-13"
  arch: any
  url: "http://security.debian.org/debian-security/"
  securitySource: true
  distribution: trixie-security
  components:
    - contrib
    - main
    - non-free
    - non-free-firmware

Objects that Reference package-repositories

Not used in current content packs

Objects used by package-repositories

Not used in current content packs