Re-allow localisation when SOURCE_DATE_EPOCH is set (follow-up to #10949) #11303
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feature or Bugfix
Purpose
SOURCE_DATE_EPOCH
is set #10949) is likely not a good ideaDetail
SOURCE_DATE_EPOCH
is set #10949 fixed an unusual behaviour around lazy-loading of localised resourcesSOURCE_DATE_EPOCH
is set #10949 also completely disabled localisation during reproducible builds (detected by a non-emptySOURCE_DATE_EPOCH
environment variable)objects.inv
file -- where reproducibility problems were occurring -- was already being requested in a single language (English-only); so localisation of the rest of the package-under-build should be irrelevantRelates
SOURCE_DATE_EPOCH
is set #10949