Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ We will also setup a 100 GB large RAM disc to use as storage for temporary files
- If you use KVM as hypervisor (ProxmoxVE, virt-manager, vserver) install the qemu guest tools:
`apt install qemu-guest-agent`
- Install the dependencies and the build toolchain
`apt install pkg-config liblzma-dev libsqlite3-dev libzstd-dev cargo make scdoc sqlite3 devscripts sbuild mmdebstrap uidmap diffoscope-minimal`
`apt install pkg-config liblzma-dev libsqlite3-dev libzstd-dev cargo make scdoc sqlite3 devscripts sbuild mmdebstrap uidmap diffoscope-minimal libstring-shellquote-perl equivs`
- Create system user for the rebuilderd services:
```
# Create rebuilderd system user and group
Expand Down Expand Up @@ -258,7 +258,7 @@ sudo cp -rv * /var/www/html/

Trixie ships rebuilderd, so if you just want to test rebuilding Trixie you actually don't need to build from source.
The Trixie package uses /var/lib/ instead of /srv as data directory though, so not all parts of this tutorial are directly applicable.
For testing or unstable it's propably still the best way to go to use the [upstream repository](https://github.com/kpcyrd/rebuilderd) by [kpycrd](https://github.com/kpcyrd).
For testing or unstable it's propably still the best way to go to use the [upstream repository](https://github.com/kpcyrd/rebuilderd) by [kpcyrd](https://github.com/kpcyrd).
I myself used the upstream repo to setup my Trixie rebuilderd main and worker nodes. It was simply less work to build and setup from scratch instead
of figuring out where I would have to change Debians default configuration.

Expand Down