conary-0.16.1-1.fc44.x86_64.rpmbase="https://github.com/ConaryLabs/Conary/releases/download/v0.16.1" $curl -fLO "$base/SHA256SUMS" $curl -fLO "$base/conary-0.16.1-1.fc44.x86_64.rpm" $sha256sum -c SHA256SUMS --ignore-missingTester loop paused
v0.16.1 is published and artifact-verified, but the external tester pin remains paused until the #110 ordinary-package corpus gate passes.
The installer endpoint is inspectable now. It fails closed until the latest
immutable release contains the signed conary-bootstrap-v1.manifest and its detached signature. Preview is the default; installation requires the
explicit --apply --yes pair.
$curl --proto '=https' --tlsv1.2 -fLO https://conary.io/install-conary-preview.sh $less install-conary-preview.sh $bash ./install-conary-preview.sh $bash ./install-conary-preview.sh --apply --yesThe basic package loop uses a stock distribution kernel. Composefs, UEFI, and special boot support are only needed for generation work outside this runbook.
$cat /etc/os-release $uname -m $uname -r $sudo -vx86_64;
a stock kernel; and working sudo.Create a clean directory, choose only the package for this host, and verify it against the release checksum before installation.
$mkdir -p "$HOME/conary-preview-v0.16.1" $cd "$HOME/conary-preview-v0.16.1"conary-0.16.1-1.fc44.x86_64.rpmbase="https://github.com/ConaryLabs/Conary/releases/download/v0.16.1" $curl -fLO "$base/SHA256SUMS" $curl -fLO "$base/conary-0.16.1-1.fc44.x86_64.rpm" $sha256sum -c SHA256SUMS --ignore-missingconary_0.16.1-1_amd64.debbase="https://github.com/ConaryLabs/Conary/releases/download/v0.16.1" $curl -fLO "$base/SHA256SUMS" $curl -fLO "$base/conary_0.16.1-1_amd64.deb" $sha256sum -c SHA256SUMS --ignore-missingconary-0.16.1-1-x86_64.pkg.tar.zstbase="https://github.com/ConaryLabs/Conary/releases/download/v0.16.1" $curl -fLO "$base/SHA256SUMS" $curl -fLO "$base/conary-0.16.1-1-x86_64.pkg.tar.zst" $sha256sum -c SHA256SUMS --ignore-missingThe downloaded package must print OK. Stop on any missing or failed checksum.
Choose the command that matches the verified package. This changes the host, so review the command and ask for approval before running it.
sudo dnf install ./conary-0.16.1-1.fc44.x86_64.rpmsudo apt install ./conary_0.16.1-1_amd64.debsudo pacman -U ./conary-0.16.1-1-x86_64.pkg.tar.zstRelease packages initialize one source-independent database and configure Remi plus all built-in RPM, Debian, and Arch source feeds. Inspect the configured sources before the package loop.
$conary --version $conary --help | sed -n '1,80p' $sudo conary repo list $sudo conary repo sync remirepo sync remi. Packaged testers should not initialize
the system again or add a second Remi repository.Choose a source that differs from the host's native package format. Review
every dry-run first and ask before each command with --yes.
choosesource=ubuntu-26.04 # Fedora/Arch; use fedora-44 on Ubuntu inspect$sudo conary install htop --from "$source" --dry-run live$sudo conary install htop --from "$source" --yes read$sudo conary list htop --info read$sudo conary query depends htop inspect$sudo conary update htop --dry-run live$sudo conary remove htop --yeshtop's exact package declaration against the target
before mutation and rejects unsupported requirements without a bypass flag.An exact capability error, lifecycle defect, or slow first conversion is useful evidence. Keep the public report concise and include only the output needed to explain the result.
/etc/conary/trust and unreviewed support bundles.Contributor path
Use this path for development, not as a substitute for the packaged tester lane. It requires Rust 1.97.1+, Git, and Linux; Conary does not currently build on macOS or Windows.
$git clone https://github.com/ConaryLabs/Conary.git $cd Conary $cargo build -p conary $sudo install -m 755 target/debug/conary /usr/local/bin/ $sudo conary system initThe example is for Fedora 44. Use --profile ubuntu-26.04 or --profile arch only on the matching host.