Update deps, fix build on main

[tigarmo]

• Have you signed the CLA?

---

[lengau]

Re: Spread test failures: I'm not sure why they're failing, but they appear to be reaching the right point. We're matching on "No suitable Python interpreter found, giving up." which we do get to, but for some reason doesn't get included in the output:

:: ++ find /root/parts/my-part/install/usr/bin /root/stage/usr/bin -type f -executable -name python3.10 -print -quit
:: + payload_python=
:: + '[' -n '' ']'
:: + echo 'Python interpreter not found in payload.'
:: + symlink_target=
:: Python interpreter not found in payload.
:: + '[' -z '' ']'
Failed to run the build script for part 'my-part'.
Detailed information: 
:: + '[' -z '' ']'
Recommended resolution: Check the build output and verify the project can work with the 'python' plugin.
For more information, check out: https://documentation.ubuntu.com/rockcraft/en/latest/reference/plugins.html
Failed to execute rockcraft in instance.
Full execution log: '/root/.local/state/rockcraft/log/rockcraft-20250129-165952.401190.log'

I don't think these are reversions - they look more like flaky tests to me. Under that presumption I'm approving

[tigarmo]

Re: Spread test failures: I'm not sure why they're failing, but they appear to be reaching the right point. We're matching on "No suitable Python interpreter found, giving up." which we do get to, but for some reason doesn't get included in the output:

:: ++ find /root/parts/my-part/install/usr/bin /root/stage/usr/bin -type f -executable -name python3.10 -print -quit
:: + payload_python=
:: + '[' -n '' ']'
:: + echo 'Python interpreter not found in payload.'
:: + symlink_target=
:: Python interpreter not found in payload.
:: + '[' -z '' ']'
Failed to run the build script for part 'my-part'.
Detailed information: 
:: + '[' -z '' ']'
Recommended resolution: Check the build output and verify the project can work with the 'python' plugin.
For more information, check out: https://documentation.ubuntu.com/rockcraft/en/latest/reference/plugins.html
Failed to execute rockcraft in instance.
Full execution log: '/root/.local/state/rockcraft/log/rockcraft-20250129-165952.401190.log'

I don't think these are reversions - they look more like flaky tests to me. Under that presumption I'm approving

I'm 90% sure that the new error-output-handling is flaky in this special case. That expected line is the very last line of error output, and sometimes the test passes.

[lengau]

@tigarmo makes sense to me. I can't replicate the issue on my own machine.