| Summary: | Broken image in bitbake manual CSS for versions 1.6.x | ||
|---|---|---|---|
| Product: | [Documentation] BitBake User Manual | Reporter: | Michael Opdenacker <michael.opdenacker> |
| Component: | bitbake-manual | Assignee: | Michael Opdenacker <michael.opdenacker> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | Medium | CC: | mhalstead, michael.opdenacker, ndec13, randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 4.1 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Michael Opdenacker
2021-03-19 14:13:47 UTC
How was the documentation for versions 1.6.x generated? If such documentation was just generated once, then all we have to do is modify the 4 instances of bitbake-user-manual-style.css manual. If there's a script to rebuild such docs, like in the case we suddenly have a significant number of broken links that could hurt our SEO ranking, I'd be happy to add a postprocessing step! There's nothing I can do about this bug. Reassigning it to Michael Halstead. Feel free to assign it to somebody else if needed. Richard says that Michael O. can patch the tarball in the build scripts. Now I understand what I could do to fix this. However, I don't want to add complexity to the run-docs-build script for a tiny issue in documents we don't maintain any more. Closing this bug. Thanks for the guidelines anyway. Closing this bug |