We did not face the conflicts between rustc and rustc-web in Apertis v2024 because we first built the source package with a fixed ci-buildpackage in v2026dev1, and when backporting the same version to v2024 ci-package-builder reuses the already built source package thus this issue this not triggered. But for downstreams which doesn't use v2025 or v2026dev1 then they have to build the source package using a docker image of v2024 and therefor this issue needs to be fixed as well.
