Hi, I tried installing chromium-l10n again on a freshly updated Bullseye machine (with the bullseye-security and bullseye-updates repositories enabled, of course) and this time the operation succeeded with no conflicts.
Unless there are new reports about this problem persisting, I think this bug can be closed. Best regards.
