summary refs log tree commit diff
path: root/gnu/packages/patches
diff options
context:
space:
mode:
Diffstat (limited to 'gnu/packages/patches')
-rw-r--r--gnu/packages/patches/icu4c-test-date-format.patch17
1 files changed, 0 insertions, 17 deletions
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 <http://bugs.icu-project.org/trac/ticket/10960>.
-
---- 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));
- }
- 
- // -------------------------------------