I was re-verifying some of the major decision points to make sure this goes the right paths (after all this crossed three digits of builds overall) and as my gut feeling told me, something is even more odd.
I went back and ended up no more being able to reproduce the good case. Not even with the PPA non-debugsymbol non-proposed build in: https://launchpad.net/~paelzer/+archive/ubuntu/lp-2089779-libsdl-rebuild-2.30.9/+build/29314882 That obviously resets a lot of assumptions and efforts. Resetting tets environments from scratch: 1. autopkgtest of wesnoth on plucky with --apt-pocket=proposed=src:libsdl2 2. autopkgtest of wesnoth on plucky Trying against last weeks good/bad no change rebuilds A. default build dep, no debug symbols built: https://launchpad.net/~paelzer/+archive/ubuntu/lp-2089779-libsdl-rebuild-2.30.9/+build/29314882 B. A. proposed build dep, debug symbols built: https://launchpad.net/~paelzer/+archive/ubuntu/lp-2089779-libsdl-rebuild-2.30.9/+build/29317135 C. check if it is infectionous in any way, after A/B force installing the former good via sudo apt install libsdl2-2.0-0=2.30.6+dfsg-1 1: fails 2: works 1A: fails 2A: fails 1B: fails 2B: fails 1C: works 2C: works So indeed the former was a fluke and no change rebuild to fix was therefore a bad try. Back to the drawing board, maybe also double check if the local git build was really working ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2089779 Title: Buffer overflow in autopkgtest of wesnoth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost1.83/+bug/2089779/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
