lair/mistralrs-package
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add forced rebuild instructions to readme
All checks were successful
poll-upstream / check (push) Successful in 1s
Details

Browse Source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
rob thijssen
2026-04-27 10:44:50 +03:00
parent 6d3dca17fa
commit 85b78d0c0c
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
readme.md
View File

@@ -108,6 +108,20 @@ EOF
sudo dnf install mistralrs-server-cuda13 sudo dnf install mistralrs-server-cuda13
``` ```
## Forcing a rebuild
To force a rebuild of an already-published RPM (e.g. after a packaging change), remove the RPM from the repo server and update the index:
```bash
ssh oolon "rm /var/www/rpm/fedora/43/x86_64/mistralrs-server-cuda13-<version>-1.fc43.x86_64.rpm \
&& cd /var/www/rpm/fedora/43/x86_64 \
&& createrepo_c --update ."
```
The next poll-upstream cycle (every 15 minutes) will detect the missing package and trigger a full rebuild. You can also trigger poll-upstream manually from the Gitea Actions UI to avoid waiting.
Do not delete the RPM without running `createrepo_c --update` afterwards — this leaves the repo index referencing a missing file, which causes errors for dnf clients.
## CI secrets ## CI secrets
The build-release workflow requires the following secrets: The build-release workflow requires the following secrets: