| Project | bookworm (stable) | bookworm-dev | trixie (stable) | trixie-dev |
|---|---|---|---|---|
| qtpyvcp | ||||
| probe_basic | ||||
| turbonc | ||||
| monokrom |
Each badge is live (auto-updates) and links straight to that workflow's run history.
Debian package repository for qtpyvcp,
probe_basic,
turbonc, and
monokrom, served via GitHub Pages at
repository.qtpyvcp.com.
curl -fsSL https://raw.githubusercontent.com/kcjengr/apt/main/install.sh | sudo shDetects your machine's actual Debian release (bookworm or trixie) from
/etc/os-release and adds the matching suite automatically — this avoids
manually adding the wrong suite by hand (e.g. a bookworm source on a
trixie machine, which apt won't stop you from doing and can pull in
ABI-incompatible packages). Add -- --dev for the continuous dev suite
instead of the latest stable release:
curl -fsSL https://raw.githubusercontent.com/kcjengr/apt/main/install.sh | sudo sh -s -- --devThen install packages as usual, e.g. apt-get install python3-qtpyvcp python3-probe-basic.
The served apt tree lives under apt/ (apt/dists/, apt/pool/) — not
the repo root — because every existing install's sources.list points at
https://repository.qtpyvcp.com/apt, so apt fetches
.../apt/dists/<suite>/.... It's updated automatically by the
release-stable-{bookworm,trixie}.yml/release-dev.yml workflows in the source repos, which
build .deb packages and push the results here.
Suites:
| dists suite | pool dir | codename | notes |
|---|---|---|---|
bookworm |
bookworm |
bookworm | pyqt5, stable releases |
stable |
bookworm |
bookworm | alias, kept for older docs/installs |
bookworm-dev |
bookworm-dev |
bookworm | pyqt5, continuous dev builds |
develop |
bookworm-dev |
bookworm | alias, kept for older docs/installs |
trixie |
trixie |
trixie | pyside6, stable releases |
trixie-dev |
trixie-dev |
trixie | pyside6, continuous dev builds |
Release file Origin/Label/Suite/Codename are all set to match the
suite name exactly (Origin/Label prefixed apt ), mirroring what the
live repo's aptly-generated Release files currently use -- this avoids
apt's "repository changed its Origin/Label value" prompt on existing
users' first update after cutover.
scripts/publish-suite.sh <dists-suite> <pool-suite> <arch...> scans a pool
directory and (re)generates the signed Packages/Release/InRelease for
one suite. Requires GPG_KEY_ID set in the environment and the corresponding
private key imported into the local GPG keyring.
Some runtime dependencies declared by qtpyvcp/probe_basic aren't packaged for
bookworm in Debian proper (only trixie has them) — these are backported here
from Debian's own trixie source packages, unmodified, and published in the
bookworm/bookworm-dev pool alongside qtpyvcp/probe_basic:
python3-hiyapyco(0.7.0-2) — built from Debian trixie'spython-hiyapycosource package against bookworm; builds unmodified, archall.