Kodachi Repository Manager
Browse signed Kodachi packages, compare Stable, Beta, and authenticated Dev channels, inspect hashes and repository trust, manage every APT source, apply system updates, and install additional Debian applications.
Open it from Cairo Dock
Choose More -> Kodachi Repository Manager. The application opens as a normal user. It reads package and source state without privilege, then delegates only approved mutations to kodachi-repo-apt through PolicyKit.
Four destinations on one rail

The left rail groups its rows under four headings. CHANNELS picks Stable, Beta or Dev and narrows the package table to one component (All components, main, thirdparty, apps). THIS MACHINE narrows the same table by state (Installed, Upgradable, Pinned, Channel diff). SYSTEM opens System sources and System updates, and ADDITIONAL APPS opens the Debian applications page. The rail's 14 rows, which the CONTROL SURFACE box at its foot counts as destinations, open four pages: the first two headings both open Packages, then System sources, System updates and Additional apps.
Packages
Search, filter, sort, inspect, install, upgrade, remove, and switch signed Kodachi packages between channels.
System sources
Read every Debian, security, backports, Whonix, Kodachi, and custom APT source. Enable, disable, add, or remove supported entries.
System updates
Simulate what APT would upgrade, show origin details, then apply all reviewed updates.
Additional apps
Install or remove applications Debian ships, from your configured Debian repositories rather than Kodachi's, without hunting for downloads.
The command log stays visible across all four destinations. If you switch pages during an operation, progress and recovery output remain available.
Browse the package storefront
- Choose Stable, Beta, or Dev in the compact channel selector.
- Search by package name, summary, or SHA256, or select a rail filter.
- Read each card's state dot and legend. Select a card to open its slide-over datasheet.
- Review version, channel, size, state, and action label before pressing Install, Upgrade, Downgrade, Reinstall, Switch to beta (or Switch to stable), or Remove in the datasheet.
Filters
These are the rail rows. The line above the cards names the same filter in plain words: All packages, Core suite for main, Transports for thirdparty, Applications for apps, Updates for Upgradable and Channel differs for Channel diff, followed by how many packages are shown.
Sort controls
| Control | Forward order | Second press |
|---|---|---|
| A to Z | Component, then package name | Z to A |
| Newest | Fetched package Last-Modified date | Oldest |
| Largest | Selected channel download size | Smallest |
| State | Update, downgrade, installed, available, absent | Reverse state order |
Newest is honest about partial data
Upload dates come from package HTTP Last-Modified headers already fetched by this window. Packages whose date has not been fetched are grouped at the far end in name order instead of receiving an invented date.
Card state words
UPDATE means the selected channel is newer. DOWNGRADE means it is older. INSTALLED means current for that channel. AVAILABLE means not installed. NOT IN CHANNEL means that channel does not publish the package.
Read the four tabs before changing a package
About
What the package is for and whether the description came from the signed index or a local fallback.
Version & dates
Installed and candidate versions, Stable and Beta cards, optional Dev record, index sync time, build date, and fetched upload time.
Integrity
SHA256, package pool location, download source, byte equality across channels, and the observed repository-key result.
Dependencies
The package relationships APT would resolve. A long list scrolls without hiding the fixed action area.
What the action buttons mean
| Button | Result |
|---|---|
| Install | Installs the selected package from the selected channel. |
| Upgrade | Moves the installed package to a newer candidate in the selected channel. |
| Downgrade | Explicitly installs the older build the selected channel carries, after confirmation. |
| Reinstall | Rewrites the current build of an installed package from the selected channel. |
| Switch to beta / Switch to stable | Selects the other channel's build and pins later upgrades to that channel. |
| Hold updates | Keeps the selected package at its installed version, or resumes updates when it is already held. It reads Resume updates while the package is held. It acts at once, with no confirmation, because it is reversible by pressing it again. |
| Remove | Runs APT remove for the package while retaining package configuration files. |
| Maintenance | A menu of eight whole-machine actions rather than per-package ones, then Dev credentials: Repair packages (dpkg --configure -a then apt-get -f install), Full upgrade, Remove unused packages, Clear download cache, Clear system channel, List snapshots, Snapshot now and Undo the last update. Five ask first, each for its own reason: Repair and Full upgrade because APT may remove a package to carry them out (it lists what it will remove in the output pane before acting), Remove unused packages because APT is occasionally wrong about something you installed by hand, Clear system channel because every Kodachi package stops tracking the channel you moved the system to, and Undo the last update because it rolls the whole system back to the newest snapshot, loses anything changed since, and needs a reboot. Clear download cache, List snapshots and Snapshot now run at once. |
Read every Repository Manager confirmation
The manager confirms downgrades, Kodachi package removals, package or whole-system channel moves, repository add or remove, source enable or disable, installing all updates, and the five Maintenance actions that ask first (see the table above). The dialog names the exact scope. Additional-app install and remove run from their row without that confirmation, so review the listed package set before pressing either button.
The fixed command area is headed either WHAT THE BUTTON RUNS or WHY THERE IS NOTHING TO RUN. Read it when a card action is grey.
Stable, Beta, and Dev
| Channel | Use | Important behavior |
|---|---|---|
| Stable | Default production packages | A version can differ from Beta. Compare the datasheet rather than assuming either one is newer. |
| Beta | Published test channel | Switching can upgrade or downgrade depending on the exact package versions. |
| Dev | Internal authenticated packages | Package actions stay disabled until a non-empty authentication file exists and the source is configured. |
Repository trust is observed, not assumed
The Integrity tab first reads the live official source and requires its Signed-By field to resolve to the pinned Kodachi archive keyring. A missing, alternate, or additional binding is reported as a source-binding mismatch before the key file is judged. With the expected binding, the installed keyring has one of seven exact states: absent, unreadable, unparseable, no keys, mismatch, extra keys, or pinned. Only pinned means exactly one matching key. Unparseable remains unknown until GPG verifies a real InRelease; no keys fails closed. A package hash and a repository signature answer different questions, so both are shown.
Do not embed credentials in a source URL
The manager rejects APT URIs containing user information. Dev credentials are collected separately and stored in APT's protected authentication configuration through the privileged helper.
Move the system versus switch one package
Switch to beta (or Switch to stable) acts on the selected package and pins it. Move system acts on every Kodachi package. Review the confirmation carefully because moving to Beta can be a downgrade when Stable currently carries a newer build.
System sources

Each row represents an APT source file or stanza the machine actually reads. Select a row and the line under the table shows its file, format, state, signing key, and why Enable, Disable or Remove file is unavailable when one is. A source in /etc/apt/sources.list can be displayed but is not removed as though it were a standalone file.
- Enable or Disable changes whether APT reads a supported source.
- Add repository offers Kodachi Stable, Kodachi Beta and Kodachi Dev as ready-made entries. Choosing one fills the fields with exactly what will be written, keeps them readable but not editable, and writes the source through the same privileged helper the Channels page uses, so the Kodachi archive key is installed and checked against a pinned fingerprint first. Dev additionally needs the login and password you were issued: this dialog never asks for a password and never stores one, and refuses until the credentials are entered under Channels. For a custom repository, Add validates the file name, URI, release name and components, and the keyring is chosen from those already installed rather than typed.
- Remove file deletes the chosen standalone source definition after confirmation. It does not uninstall packages obtained from it.
- An unreadable or invalid source remains visible with mutation controls disabled and the reason stated.
System updates

- Open System updates and press Check for updates.
- Review package, installed version, candidate version, and origin.
- If the read failed, correct the displayed APT error first.
- Use Recount only for a fresh read without applying changes.
- Press Install all updates, review the total and security-update count, authenticate through PolicyKit, and keep the window open while the command log runs.
The same page carries an ISO IMAGES card. Its numbers come from the published release file rather than from APT, because APT does not know which image this machine was installed from. The stable image line and the beta image line are compared separately, since a machine running a beta image is ahead of stable by design. Each line reads as available, matching this machine, older than this machine, or not compared when either side is missing.
Additional apps

The eight rows cover VLC, Audacity, GIMP, Inkscape, Bluefish, Docker with Compose, a QEMU plus Virt Manager bundle, and Dropbox. A row reads installed, partly installed, not installed, or not offered by apt. Install adds its package set; Remove removes only the installed subset; Recheck refreshes the reading. This is separate from Kodachi package channels and does not download arbitrary installers from websites.
Whole-system strip and console
The fixed strip at the foot of the window exposes six operations: Refresh, Update all, the selected channel's own button (Add channel, Remove channel, or Configured externally when that channel's source lives in a file this window did not write), Dev credentials (Clear dev credentials once a login is stored), Move system and Export, which saves the catalog as JSON. The command console provides Follow, Expand, Stop, Wrap, Copy and Clear. Stop (announced to screen readers as Stop waiting) returns the interface to you, but a root-owned APT child may still be finishing, so inspect the log before starting another mutation.
Recover without making package state worse
| Symptom | Next step |
|---|---|
| Button is grey | Read the reason line above the fixed command area. Configure the selected channel, add Dev credentials, select a published package, or wait for the catalog read. |
| Channel not configured | Use Add channel on the selected channel. The manager writes the supported source through its helper. |
| Catalog or source read failed | Read the command log. Invalid source syntax, unreachable repositories, or an APT lock can prevent a trustworthy catalog. |
| Operation is silent | The window has an idle timeout and a wall timeout. Keep it open until it reports completion or abandonment. |
| Stop was pressed | The GUI stops reading and gives control back, but it cannot promise that a root-owned APT child stopped immediately. Read the final log before starting another operation. |
| dpkg was interrupted | Run the exact recovery instruction shown by the window, commonly sudo dpkg --configure -a, before another install or update. |
| Closing while busy | Prefer Keep waiting. Close anyway can cut APT off mid-operation and leave dpkg requiring recovery. |
One package manager owns Kodachi files
On Kodachi Desktop, use Repository Manager or APT for packaged binaries. Do not run the portable tarball installer over the same files because two installation systems would then compete for ownership.
Return to Cairo Dock or Desktop Controls.