Autoupdate of 2 submodules
*external/icu updated to 010f0eefca7ec7da20b53d2edfc0bbce449b62c9
DO NOT MERGE Update Android ICU data from 2025b to 2025c. [S]
Changes here are identical to https://github.com/unicode-org/icu/commit/83fd74f69966e275e3c64fbf1dbd392cf528f510
Bug: 476047084
Test: see system/timezone
Change-Id: Ie44460560b0c394b6a5355e662b574cfe0711f6e
Merged-In: Ie44460560b0c394b6a5355e662b574cfe0711f6e
*system/timezone updated to da428c1fc3828adc22a3eaf2a7d71ffd3394a5b3
DO NOT MERGE Update Android TZDB from 2025b to 2025c [S]
Notes for Android time zone maintainers:
Like all tzdb updates, the binary files in this commit should not be
patched to other release branches: they are not guaranteed to work.
Also note that there are associated changes in external/icu and often
others that should also be applied. tzdb updates are incremental
changes: all previous tzdb updates should be applied. Look for
aosp/<release>-dev changes for backports. If you have a local branch
with ICU changes the ICU .dat file in external/icu will not apply
cleanly. Instead, make equivalent changes to text files and run
system/timezone/update-tzdata.py.
---------------
IANA release 2025c notes:
Changes to past timestamps
Baja California agreed with California’s DST rules in 1953 and in
1961 through 1975, instead of observing standard time all year.
Bug: 476047084
Test: run cts --include-filter CtsLibcoreTestCases
Test: run cts --include-filter CtsLibcoreOjTestCases
Test: run cts --include-filter CtsIcuTestCases
Test: run cts --include-filter CtsBionicTestCases
Test: run cts --include-filter CtsTextTestCases
Test: atest MtsTimeZoneDataTestCases
Test: "adb shell dumpsys runtime" reports 2025c
Change-Id: I1d84b71951a9cdad854f0e49ba6a838351022247
Merged-In: I1d84b71951a9cdad854f0e49ba6a838351022247
2 files changed
