Debian Configuration

OSA Proxy implementation

This page describes the current OSA Proxy implementation. The archived Java/Spring implementation is available in Archived Java/Spring implementation.

debian:
  enabled: true
  repository:
    - name: debian
      registry: https://deb.debian.org/debian
      distro: bookworm
      scan-package: true
      work-mode: strict_wait

Example /etc/apt/sources.list.d/osa-proxy.sources:

Types: deb
URIs: https://osa-proxy.example.com/debian
Suites: bookworm
Components: main
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
apt update
apt install curl

Component identification

With scan-package: true, the name, version (including epoch), and architecture come from the control file inside .deb/.udeb.

Distribution is inferred from the upstream path or version marker. It is omitted when signals are absent or contradictory. An explicit distro field overrides automatic detection.

Upstream 401, 403, 404, 410, 429, and 5xx responses to the header request are returned to the client unchanged; if upstream does not answer, the client receives 502 or 504. In other cases, for example when the header cannot be parsed, codescoring.block-on-codescoring-errors applies.

For upstreams that serve both package formats, use a combined Debian and RPM repository.

Was this page helpful?