infra: parent_image=ubuntu:24.04 #13018
Conversation
This is not needed, and the package is deprecated anyway.
This requires a workaround for honggfuzz. Also, use the new lib32gcc-s1 package name.
|
This requires an infra build, so that projects that wish to (or require to) use the older image can be pinned to the old image. |
|
The CI failures are expected, because the libssl-dev install is skipped in the GitHub-CI infra-build |
|
@jonathanmetzman is there a chance for a version of this to be merged? What does it take? |
This will be a very long process as we may need to migrate our clusterfuzz images and all users around the same time. I think it will come next quarter. |
|
@jonathanmetzman maybe its a sign that every fuzzing project should be able to say what base image it needs, similar to what GitHub Actions is doing. If that was supported, projects could be updated one by one and there would be no risk of mask-breaking things. PS: As if Github was knewing about our conversation about Ubuntu 20.04, they sent out this mail just today, kill Ubuntu 20.04 support in GitHub Actions for April 1, 2025 altogether: |
I think you are right. We should come up with some kind of system that supports users on diverse OSes and toolchains. |
|
I am wondering how many projects are actually breaking due to this LTS bump. Imagining a future where OSS-Fuzz is shipped not with a docker image, but via some kind of package, I expect most breakage to stem from clang/llvm bumps, or python bumps (or any other OSS-Fuzz supported language). Thus, to prevent breaks due to package changes, each OSS-Fuzz language package would have to be versioned (and some array of versions should be supported)? |
|
Any estimate when this will be finished? Thanks! |
|
I am happy to work on it (this pull request). It just needs a trial build from a maintainer. I do not know if more work is needed on clusterfuzz first, to support this. For reference, google/clusterfuzz#4261 was closed, albeit by a bot. |
…ntu 20.04 When google/oss-fuzz#13018 is merged we can likely switch to ubuntu 24.04 for oss-fuzz Signed-off-by: Stefan Metzmacher <metze@samba.org> Reviewed-by: Andreas Schneider <asn@samba.org>
|
Any update and workaround in the meantime? |
@jonathanmetzman Q2 has already passed in its entirety by now, please do no forget, thank you 🙏 |
|
Sorry, I am on parental leave (!) I'll pass this on to someone |
bitcoin/bitcoin#31802 builds libmultiprocess and enables IPC by default, but my understanding is that this breaks oss-fuzz. One proposed solution is #13018. This PR builds depends with `NO_IPC=1`, which disables the feature, for now while we work on an actual fix.
This updates the parent base image to Ubuntu LTS 24.04.
This is required, because otherwise projects will have to act as a package managers and install recent packages so that their projects keep working.
The last bump was done in commit 7ca0037