From 8c3fc834114306a082d84a83519f870d3c002907 Mon Sep 17 00:00:00 2001 From: Andreas Enge Date: Thu, 20 Nov 2014 14:01:20 +0100 Subject: gnu: icu4c: Update to 54.1. * gnu/packages/icu4c.scm (icu4c): Update to 54.1. * gnu/packages/patches/icu4c-test-date-format.patch: Remove unneeded patch. * gnu-system.am (dist_patch_DATA): Unregister dropped patch. --- gnu/packages/patches/icu4c-test-date-format.patch | 17 ----------------- 1 file changed, 17 deletions(-) delete mode 100644 gnu/packages/patches/icu4c-test-date-format.patch (limited to 'gnu/packages/patches') diff --git a/gnu/packages/patches/icu4c-test-date-format.patch b/gnu/packages/patches/icu4c-test-date-format.patch deleted file mode 100644 index d7f0df98a6..0000000000 --- a/gnu/packages/patches/icu4c-test-date-format.patch +++ /dev/null @@ -1,17 +0,0 @@ -Starting with the switch to GCC 4.8.3, we observed this test failure. -Changing "34" to "134" means that we expect the date to be parsed as -"2034", not "1934", which seems consistent with the line above. - -Reported at . - ---- icu/source/test/intltest/dtfmttst.cpp 2014-06-16 10:35:46.000000000 +0200 -+++ icu/source/test/intltest/dtfmttst.cpp 2014-06-16 10:35:52.000000000 +0200 -@@ -1129,7 +1129,7 @@ DateFormatTest::TestTwoDigitYear() - return; - } - parse2DigitYear(fmt, "5/6/17", date(117, UCAL_JUNE, 5)); -- parse2DigitYear(fmt, "4/6/34", date(34, UCAL_JUNE, 4)); -+ parse2DigitYear(fmt, "4/6/34", date(134, UCAL_JUNE, 4)); - } - - // ------------------------------------- -- cgit v1.2.3