Hello, We probably don't care about such old versions, but you get broken links in the CSS of old versions of the bitbake manual by scanning the YP documentation: URL `figures/yocto-project-bw.png' Parent URL https://docs.yoctoproject.org/1.6/bitbake-user-manual/bitbake-user-manual-style.css, line 692, col 24 Real URL https://docs.yoctoproject.org/1.6/bitbake-user-manual/figures/yocto-project-bw.png Check time 0.615 seconds Size 178B Result Error: 404 Not Found URL `figures/yocto-project-bw.png' Parent URL https://docs.yoctoproject.org/1.6.1/bitbake-user-manual/bitbake-user-manual-style.css, line 692, col 24 Real URL https://docs.yoctoproject.org/1.6.1/bitbake-user-manual/figures/yocto-project-bw.png Check time 0.708 seconds Size 178B Result Error: 404 Not Found URL `figures/yocto-project-bw.png' Parent URL https://docs.yoctoproject.org/1.6.2/bitbake-user-manual/bitbake-user-manual-style.css, line 692, col 24 Real URL https://docs.yoctoproject.org/1.6.2/bitbake-user-manual/figures/yocto-project-bw.png Check time 0.637 seconds Size 178B Result Error: 404 Not Found URL `figures/yocto-project-bw.png' Parent URL https://docs.yoctoproject.org/1.6.3/bitbake-user-manual/bitbake-user-manual-style.css, line 692, col 24 Real URL https://docs.yoctoproject.org/1.6.3/bitbake-user-manual/figures/yocto-project-bw.png Check time 0.618 seconds Size 178B Result Error: 404 Not Found A quick fix would be to remove the below line from bitbake-user-manual-style.css: background-image: url("figures/yocto-project-bw.png"); If there's a way to manually fix this on the website, that wouldn't change anybody's life, but at least this would eliminate the 404 errors in my broken link checker runs... Don't hesitate to close this bug if we don't care...
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