View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0033016 | mantisbt | tools | public | 2023-10-14 14:58 | 2023-10-24 14:09 |
| Reporter | dregad | Assigned To | dregad | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0033016: Docbook builds failing on MacOS running publican via Docker | ||||
| Description | When running the buildrelease-repo.py script as documented in our Release Process, the Manuals fail to build | ||||
| Tags | No tags attached. | ||||
|
The build should fail after such error. This should have been fixed by MantisBT master 58ae0d42 but that was committed to master branch (2.26.0-dev), and now that the build scripts are included in the MantisBT repository, if building an older release (like 2.25.8) then the fix is not taken into consideration as the older version of the docbook-manual.py build script is executed... Anyway, the root cause of the problem is that the temporary directory generated by Python's mkdtemp() function is not actually mounted into the docker image, so the repository used to build the release (with the --fresh option) is not available to publican. As a workaround, the repo should be cloned in the given release_path. |
|
|
MantisBT: master dd44ea55 2023-10-14 15:08 Details Diff |
Fix DocBook builds when running Publican via Docker on Mac Clone the temporary repository into the release_path directory instead of using a system temp directory that is not accessible to the Docker image. Fixes 0033016 |
Affected Issues 0033016 |
|
| mod - build/buildrelease-repo.py | Diff File | ||