OCO / CI / candidate channel

Testing repository

Packages built for testing are published separately from the production repository. Use this channel to try a CI build without switching your system to a different repository by default.

Repository pathhttps://repo.osowoso.org/testing/<architecture>/

Browse testing packages

Choose the architecture matching your Void installation. Package availability depends on which CI builds have completed.

Publication flow

Where builds go

Normal pushes to the OCO branch publish to production. Non-OCO branch builds and repository dispatches use the isolated /testing/ path. A manually dispatched build has a destination choice; production routing applies only on the OCO ref.

Testing packages do not replace or publish over the production package index.

One-command install

Try a package

Install the OCO signing key first if you have not already; the setup instructions are on the home page. Then add the testing repository only for the install command:

sudo xbps-install -S \
  -R https://repo.osowoso.org/testing/x86_64 \
  package-name

Replace x86_64 with your architecture and package-name with the package you want to test. This command does not add the testing repository to your permanent XBPS configuration.