Mario Fetka
32 lines
1.0 KiB
Markdown
32 lines
1.0 KiB
Markdown
# Installing the Debian Trixie bundle
|
|
|
|
The release ZIP contains packages built together from the recorded source
|
|
inputs. On a fresh Debian Trixie host, inspect the package list and run:
|
|
|
|
```sh
|
|
sudo ./install.sh
|
|
sudo bongo-setup
|
|
sudo systemctl enable --now bongo.service
|
|
```
|
|
|
|
The installer verifies `SHA256SUMS`, refuses a non-Trixie system, checks that
|
|
all patched libraries carry a `+bongo` version, installs the required runtime
|
|
libraries before Bongo, and verifies the installed versions. It then holds
|
|
only these patched dependency packages:
|
|
|
|
- `libmailutils9t64`, `libmu-dbm9t64`, and their version-coupled
|
|
`mailutils-common` data
|
|
- `libspf2-2t64`
|
|
- `libsrs2-0`
|
|
|
|
Bongo itself is not held and can be upgraded normally. Before deliberately
|
|
replacing the patched libraries, run:
|
|
|
|
```sh
|
|
sudo ./install.sh --unhold
|
|
```
|
|
|
|
Review the next Bongo bundle's manifest and installer before upgrading and
|
|
let that bundle establish its new library holds. Do not use `dpkg --force-*`
|
|
to bypass an MTA conflict: remove or migrate the old MTA deliberately.
|