GuillaumeHemmen/winesapOS
1
0
Fork 0
mirror of https://github.com/winesapOS/winesapOS.git synced 2025-11-21 03:10:44 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions8

[contributing] Add better hints

Browse source 
for what to look for in the 'winesapos-install.log' file.
This commit is contained in:
Luke Short 2025-02-22 21:31:26 -07:00
commit 419db5217e
1 changed files with 5 additions and 2 deletions

7
CONTRIBUTING.md
View file

@ -733,14 +733,17 @@ These are tasks that need to happen before publishing a stable release.
- Before building an alpha or beta build, enable the `[winesapos-testing]` repository with `export WINESAPOS_ENABLE_TESTING_REPO=true`.
- Create a "minimal" and "performance" release image (not "secure") using a [container build](#automated-container-build).
- Due to the "secure" image having a common LUKS container encryption key that would be shared, users are encouraged to do their own custom build of winesapOS to generate a unique key instead.
- Make sure that no tests failed by checking the exit/return code of the installation script. It should be zero. If not, that is how many tests have failed. Review the installation log for more details.
- Make sure that no tests failed by checking the exit/return code of the installation script. It should be zero. If not, that is how many tests have failed.
```
$ cat ./output/winesapos-install-rc.txt
0
$ less ./output/winesapos-install.log
```
- Review the installation log for more details: `$ less ./output/winesapos-install.log`. Keywords to look for:
- `err` = Error messages.
- `fail` = General failures. `FAIL` in all capital letters is a winesapOS test failure. If the build used the environment variable `WINESAPOS_DEBUG_TESTS=true`, search for `echo FAIL`.
- `Performing snapper pre snapshots` = A Snapper snapshot was created. This is undesirable in the build.
- Sanitize the image.
```