A recent commit in 2.9 triggered a bug in po4a and repeatedly crashed the buildbot.
You can trigger the problem using this process: 1. Start a debian:buster container 2. Check out commit fadb1c28 (current head of 2.9) 3. Install build dependencies like usual 4. Install po4a 0.67 from http://linuxcnc.org/dists/buster/base 5. Configure with --enable-build-documentation 6. Build All versions of po4a that I've tested are affected by this bug, including 0.67 (which we backported to buster and bullseye), 0.69 (in bookworm), and 0.73 (in trixie). I bisected the recent history of 2.9 and determined the commit that introduced the problem is d1414e36. I've reverted that commit in 2.9, and I'm merging to master now. Before reintroducing that commit, please test on the affected platforms as outlined above. -- Sebastian Kuzminsky On July 22, 2024 9:19:37 AM MDT, linux...@rodes.biz wrote: >Hey all. > >The Buildbot2 is broken. Not Seb's fault. Really can't expect him to fix >everyone else's screwups. > >Who ever broke the build, please FIX IT NOW. > >Looks like it was broken around July 8th. That was the last successful >Bookworm Master build. > >Even the Bookworm 2.9 last successful build was July 11. Same with >Bullseye... > >Come on guys. Development is wonderful, but ya gotta clean up when ya mess >up. > >Look back at your changes and figure it out. Please. > > > >Roguish > >Noel. > > >_______________________________________________ >Emc-developers mailing list >Emc-developers@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/emc-developers _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
