Bugzilla – Bug 1213470
timezone-java 2023c contains corrupt data for some timezones
Last modified: 2024-05-27 20:30:03 UTC
Created attachment 868314 [details] Small Java program to demonstrate the problem The timezone-java Package from OpenSUSE LEAP 15.5 (and 15.4) in version 2023c (timezone-java-2023c-150000.75.23.1.noarch) seems to contain corrupt data for the time zones "Asia/Gaza" and "Asia/Hebron". Using the toString() method on these timezones throws an IllegalArgumentException. Running the attached example program with a current OpenJDK 17 java gives the following output: andreas@ws1:/work/andreas/devel/tests/src/main/java> java TimeZoneTest.java TimeZone Asia/Gaza failed: java.lang.IllegalArgumentException: Illegal daylight saving value: 0 TimeZone Asia/Hebron failed: java.lang.IllegalArgumentException: Illegal daylight saving value: 0 The exception occurs within the constructor of the SimpleTimeZone class which checks the dstSavings property to be > 0 (and throws the exception if it isn't) As a workaround one can use the Java-internal tzdb as installed in $JAVA_HOME/lib/tzdb.dat by commenting out the sun.zoneinfo.dir property in the config file $JAVA_HOME/conf/tz.properties This problem occurs also on RedHat distributions like Fedora 37 (which also have a separate timezone-java package), but not on Debian-based distributions like Debian 11, Debian 12 or Ubuntu 22.04 (which seem to use the Java-internal tzdb)
Hello Andreas, thank you for the report. Do you know if this issue has already been reported upstream?
I tried to google for it, but haven't found anything. So, I don't know if it was already reported. I decided to report it on the OpenSUSE bugzilla because I first noticed the problem on my OpenSUSE LEAP 15.5 development notebook and I'm not quite sure where a proper place for an upstream bugreport would be.
Can you please report it upstream? The mailing list seems to be tz@iana.org. https://www.iana.org/time-zones
https://www.iana.org/time-zones is not the right place to report this, as the bug is surely in the Java code that is downstream from the TZDB project, and is not in the TZDB project itself. So please report the problem to whatever project or OpenSUSE buildbot is generating and/or parsing Java's tzdb.dat file. For a lengthier analysis of the situation, please see: https://mm.icann.org/pipermail/tz/2023-July/033019.html
Thanks Paul for your reply! But this means we still have to find the exact origin of the problem. So as a next step to narrow down the bug I tried to manually compile the tzdb.dat file from the original tzdb-2023c.tar.lz sources from https://data.iana.org/time-zones/releases/ To do that I installed the tzdb-1.8-3.39.noarch package from the OpenSUSE repository. I also applied the patches from the OpenSUSE timezone-java source RPM to the tzdb-2023c data files to make tzdb happy. As far as I can tell those patches are harmless and do not change anything near the Asia/Gaza timezone data. I then used the following command to compile the tzdb: andreas@ws1:/work/andreas/tmp/tzdb/tzdb-2023c> java -jar /usr/share/java/tzdb.jar -srcdir . -dstfile javazi/tzdb.dat africa antarctica asia australasia europe northamerica southamerica backward etcetera andreas@ws1:/work/andreas/tmp/tzdb/tzdb-2023c> ll javazi insgesamt 100 -rw-rw-r-- 1 andreas outlaws 99560 20. Jul 19:53 tzdb.dat The tzdb.dat file was created without warning or error. I then installed the newly compiled tzdb.dat file under /tmp/javazi/tzdb.dat and let the sun.zoneinfo.dir property point to this directory. And guess what: with this config, the problem still exists! (As a cross-check I let the sun.zoneinfo.dir property point to some non-existing directory and the problem was gone, so I'm quite sure my test program indeed did pick up my newly compiled tzdb.dat from the sun.zoneinfo.dir property) So I conclude: with the tzdb.dat file build from the original tzdb-2023c sources the OpenJDK 17 SimpeTimeZone class throws an exception in its constructor for the "Asia/Gaza" timezone. With the original tzdb.dat file from the OpenJDK 17 distribution it doesn't. (I don't know the exact version of the tzdb.dat file from the OpenJDK 17 distribution, though) I then tried to find the difference between the OpenJDK 17 tzdb.dat and the one derived from the original tzdb-2023c.tar.lz sources. I found that with the OpenJDK 17 tzdb.dat the TimeZone "Asia/Gaza" has (amongst others) the following properties: rawOffset: 7200000 dstSavings: 3600000 useDaylightTime: true observesDaylightTime:true With the tzdb.dat created from the 2023c database, those properties are: rawOffset: 7200000 dstSavings: 0 useDaylightTime: true observesDaylightTime:true I then checked (with the 2023c database) for all time zones with useDaylightTime set to true but with dstSavings set to 0 and found: andreas@ws1:/work/andreas/devel/tests/src/main/java> java TimeZoneTest3.java TimeZone Asia/Gaza has useDaylightTime set to true but dstSavings == 0 TimeZone Asia/Hebron has useDaylightTime set to true but dstSavings == 0 Surprise: only those time zones which produce an IllegalArgumentException in my test program have both dstSavings set to 0 and useDaylightTime set to true! With the OpenJDK 17 tzdb.dat file I haven't found any time zone with this combination. This could mean that the dstSavings value is calculated wrong either by the tzdb program when compiling the 2023c database or by the Java classes which later read the compiled tzdb data at runtime. (And that is essentially the same what Paul stated in comment #4) So how can we proceed now?
I suspect you'll need to look at the source code of the relevant Java programs in order to figure out what is going wrong. That is, the source code of the program that generates tzdb.dat, and the source code of the library code that reads that file. In OpenJDK I think the files are here: openjdk/jdk/make/jdk/src/classes/build/tools/tzdb openjdk/jdk/src/java.base/share/classes/java/time/zone/TzdbZoneRulesProvider.java openjdk/jdk/src/java.base/share/classes/java/time/zone openjdk/jdk/src/java.base/share/classes/java/util/SimpleTimeZone.java Quite possibly you should file a bug report at openjdk.org, though you'll need a way they can reproduce the bug (a bit tricky if the Java code does not generate reproducible results...). You might also try contacting the people who develop this Java code. For example, look who develops and maintains the abovementioned files.
Oracle provides a Java "tzupdater" tool. This seems to be an alternative to the Java "tzdb" tool which is used in the SUSE timezone-java rpm specfile (see https://www.oracle.com/java/technologies/javase/tzupdater-readme.html) Using the tzupdater tool to create a new tzdb.dat file from the original IANA 2023c database I get: ws1:/tmp/tzupdater-2.3.2 # java -jar tzupdater.jar -v -l file:///home/andreas/Downloads/tzdata2023c.tar.gz Using file:///home/andreas/Downloads/tzdata2023c.tar.gz as source for tzdata bundle. java.home: /usr/lib64/jvm/java-17-openjdk-17 java.vendor: N/A java.version: 17.0.7 tzupdater version 2.3.2-b02 JRE tzdata version: tzdata2022g Downloaded file to /tmp/tz.tmp_1/tzdata.tar.gz tzupdater tool would update with tzdata version: tzdata2023c Warning: Source directory does not contain source file: pacificnew Compiling TZDB version 2023c Building rules Building zone Africa/Abidjan Building zone Africa/Accra Building zone Africa/Addis_Ababa Building zone Africa/Algiers [...] Building zone Asia/Famagusta Building zone Asia/Gaza Building zone Asia/Harbin Building zone Asia/Hebron Building zone Asia/Ho_Chi_Minh Building zone Asia/Hong_Kong [...] Linking alias UTC to GMT Linking alias Universal to Etc/UTC Linking alias W-SU to Europe/Moscow Linking alias Zulu to Etc/UTC Outputting tzdb file: /usr/lib64/jvm/java-17-openjdk-17/lib/tzdb.dat.dynamic Renaming /usr/lib64/jvm/java-17-openjdk-17/lib/tzdb.dat to /usr/lib64/jvm/java-17-openjdk-17/lib/tzdb.dat.tzdata2022g Renaming /usr/lib64/jvm/java-17-openjdk-17/lib/tzdb.dat.dynamic to /usr/lib64/jvm/java-17-openjdk-17/lib/tzdb.dat Validating for : tzdata2023c Validation complete JRE updated to version : tzdata2023c So it seems the original OpenJDK tzdb.dat file used the 2022g tzdata and the tzupdater tool did successfully update this file to the 2023c version: ws1:/usr/lib64/jvm/java-17-openjdk-17/lib # ll tz* -rw-r--r-- 1 root root 103785 Jul 21 10:54 tzdb.dat -rw-r--r-- 1 root root 102619 Jun 6 16:44 tzdb.dat.tzdata2022g With this updated tzdb.dat I now have current time zone information *and* the IllegalArgumentException is gone: TimeZone details for TimeZone Asia/Gaza toString: sun.util.calendar.ZoneInfo[id="Asia/Gaza",offset=7200000,dstSavings=3600000,useDaylight=true,transitions=150,lastRule=java.util.SimpleTimeZone[id=Asia/Gaza,offset=7200000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=2,startMonth=2,startDay=-1,startDayOfWeek=7,startTime=7200000,startTimeMode=0,endMode=2,endMonth=9,endDay=-1,endDayOfWeek=7,endTime=7200000,endTimeMode=0]] displayName: Eastern European Standard Time rawOffset: 7200000 dstSavings: 3600000 useDaylightTime: true observesDaylightTime:true zoneID: Asia/Gaza transition: Transition[Overlap at 1900-10-01T00:00+02:17:52 to +02:00] transition: Transition[Gap at 1940-06-01T02:00+02:00 to +03:00] transition: Transition[Overlap at 1940-10-01T03:00+03:00 to +02:00] transition: Transition[Gap at 1940-11-17T02:00+02:00 to +03:00] transition: Transition[Overlap at 1942-11-01T03:00+03:00 to +02:00] transition: Transition[Gap at 1943-04-01T02:00+02:00 to +03:00] transition: Transition[Overlap at 1943-11-01T03:00+03:00 to +02:00] transition: Transition[Gap at 1944-04-01T02:00+02:00 to +03:00] transition: Transition[Overlap at 1944-11-01T03:00+03:00 to +02:00] transition: Transition[Gap at 1945-04-16T02:00+02:00 to +03:00] transition: Transition[Overlap at 1945-11-01T03:00+03:00 to +02:00] transition: Transition[Gap at 1946-04-16T02:00+02:00 to +03:00] transition: Transition[Overlap at 1946-11-01T03:00+03:00 to +02:00] transition: Transition[Gap at 1957-05-10T00:00+02:00 to +03:00] transition: Transition[Overlap at 1957-10-01T00:00+03:00 to +02:00] transition: Transition[Gap at 1958-05-01T00:00+02:00 to +03:00] transition: Transition[Overlap at 1958-10-01T00:00+03:00 to +02:00] transition: Transition[Gap at 1959-05-01T01:00+02:00 to +03:00] transition: Transition[Overlap at 1959-09-30T03:00+03:00 to +02:00] transition: Transition[Gap at 1960-05-01T01:00+02:00 to +03:00] transition: Transition[Overlap at 1960-09-30T03:00+03:00 to +02:00] transition: Transition[Gap at 1961-05-01T01:00+02:00 to +03:00] transition: Transition[Overlap at 1961-09-30T03:00+03:00 to +02:00] transition: Transition[Gap at 1962-05-01T01:00+02:00 to +03:00] transition: Transition[Overlap at 1962-09-30T03:00+03:00 to +02:00] transition: Transition[Gap at 1963-05-01T01:00+02:00 to +03:00] transition: Transition[Overlap at 1963-09-30T03:00+03:00 to +02:00] transition: Transition[Gap at 1964-05-01T01:00+02:00 to +03:00] transition: Transition[Overlap at 1964-09-30T03:00+03:00 to +02:00] transition: Transition[Gap at 1965-05-01T01:00+02:00 to +03:00] transition: Transition[Overlap at 1965-09-30T03:00+03:00 to +02:00] transition: Transition[Gap at 1966-05-01T01:00+02:00 to +03:00] transition: Transition[Overlap at 1966-10-01T03:00+03:00 to +02:00] transition: Transition[Gap at 1967-05-01T01:00+02:00 to +03:00] transition: Transition[Overlap at 1967-06-05T00:00+03:00 to +02:00] transition: Transition[Gap at 1974-07-07T00:00+02:00 to +03:00] transition: Transition[Overlap at 1974-10-13T00:00+03:00 to +02:00] transition: Transition[Gap at 1975-04-20T00:00+02:00 to +03:00] transition: Transition[Overlap at 1975-08-31T00:00+03:00 to +02:00] transition: Transition[Gap at 1980-08-03T00:00+02:00 to +03:00] transition: Transition[Overlap at 1980-09-14T01:00+03:00 to +02:00] transition: Transition[Gap at 1984-05-06T00:00+02:00 to +03:00] transition: Transition[Overlap at 1984-08-26T01:00+03:00 to +02:00] transition: Transition[Gap at 1985-04-14T00:00+02:00 to +03:00] transition: Transition[Overlap at 1985-09-01T00:00+03:00 to +02:00] transition: Transition[Gap at 1986-05-18T00:00+02:00 to +03:00] transition: Transition[Overlap at 1986-09-07T00:00+03:00 to +02:00] transition: Transition[Gap at 1987-04-15T00:00+02:00 to +03:00] transition: Transition[Overlap at 1987-09-13T00:00+03:00 to +02:00] transition: Transition[Gap at 1988-04-10T00:00+02:00 to +03:00] transition: Transition[Overlap at 1988-09-04T00:00+03:00 to +02:00] transition: Transition[Gap at 1989-04-30T00:00+02:00 to +03:00] transition: Transition[Overlap at 1989-09-03T00:00+03:00 to +02:00] transition: Transition[Gap at 1990-03-25T00:00+02:00 to +03:00] transition: Transition[Overlap at 1990-08-26T00:00+03:00 to +02:00] transition: Transition[Gap at 1991-03-24T00:00+02:00 to +03:00] transition: Transition[Overlap at 1991-09-01T00:00+03:00 to +02:00] transition: Transition[Gap at 1992-03-29T00:00+02:00 to +03:00] transition: Transition[Overlap at 1992-09-06T00:00+03:00 to +02:00] transition: Transition[Gap at 1993-04-02T00:00+02:00 to +03:00] transition: Transition[Overlap at 1993-09-05T00:00+03:00 to +02:00] transition: Transition[Gap at 1994-04-01T00:00+02:00 to +03:00] transition: Transition[Overlap at 1994-08-28T00:00+03:00 to +02:00] transition: Transition[Gap at 1995-03-31T00:00+02:00 to +03:00] transition: Transition[Overlap at 1995-09-03T00:00+03:00 to +02:00] transition: Transition[Gap at 1996-04-05T00:00+02:00 to +03:00] transition: Transition[Overlap at 1996-09-20T01:00+03:00 to +02:00] transition: Transition[Gap at 1997-04-04T00:00+02:00 to +03:00] transition: Transition[Overlap at 1997-09-19T01:00+03:00 to +02:00] transition: Transition[Gap at 1998-04-03T00:00+02:00 to +03:00] transition: Transition[Overlap at 1998-09-18T01:00+03:00 to +02:00] transition: Transition[Gap at 1999-04-16T00:00+02:00 to +03:00] transition: Transition[Overlap at 1999-10-15T00:00+03:00 to +02:00] transition: Transition[Gap at 2000-04-21T00:00+02:00 to +03:00] transition: Transition[Overlap at 2000-10-20T00:00+03:00 to +02:00] transition: Transition[Gap at 2001-04-20T00:00+02:00 to +03:00] transition: Transition[Overlap at 2001-10-19T00:00+03:00 to +02:00] transition: Transition[Gap at 2002-04-19T00:00+02:00 to +03:00] transition: Transition[Overlap at 2002-10-18T00:00+03:00 to +02:00] transition: Transition[Gap at 2003-04-18T00:00+02:00 to +03:00] transition: Transition[Overlap at 2003-10-17T00:00+03:00 to +02:00] transition: Transition[Gap at 2004-04-16T00:00+02:00 to +03:00] transition: Transition[Overlap at 2004-10-01T01:00+03:00 to +02:00] transition: Transition[Gap at 2005-04-15T00:00+02:00 to +03:00] transition: Transition[Overlap at 2005-10-04T02:00+03:00 to +02:00] transition: Transition[Gap at 2006-04-01T00:00+02:00 to +03:00] transition: Transition[Overlap at 2006-09-22T00:00+03:00 to +02:00] transition: Transition[Gap at 2007-04-01T00:00+02:00 to +03:00] transition: Transition[Overlap at 2007-09-13T02:00+03:00 to +02:00] transition: Transition[Gap at 2008-03-28T00:00+02:00 to +03:00] transition: Transition[Overlap at 2008-08-29T00:00+03:00 to +02:00] transition: Transition[Gap at 2009-03-27T00:00+02:00 to +03:00] transition: Transition[Overlap at 2009-09-04T01:00+03:00 to +02:00] transition: Transition[Gap at 2010-03-27T00:01+02:00 to +03:00] transition: Transition[Overlap at 2010-08-11T00:00+03:00 to +02:00] transition: Transition[Gap at 2011-04-01T00:01+02:00 to +03:00] transition: Transition[Overlap at 2011-08-01T00:00+03:00 to +02:00] transition: Transition[Gap at 2012-03-30T00:00+02:00 to +03:00] transition: Transition[Overlap at 2012-09-21T01:00+03:00 to +02:00] transition: Transition[Gap at 2013-03-29T00:00+02:00 to +03:00] transition: Transition[Overlap at 2013-09-27T00:00+03:00 to +02:00] transition: Transition[Gap at 2014-03-28T00:00+02:00 to +03:00] transition: Transition[Overlap at 2014-10-24T00:00+03:00 to +02:00] transition: Transition[Gap at 2015-03-28T00:00+02:00 to +03:00] transition: Transition[Overlap at 2015-10-23T01:00+03:00 to +02:00] transition: Transition[Gap at 2016-03-26T01:00+02:00 to +03:00] transition: Transition[Overlap at 2016-10-29T01:00+03:00 to +02:00] transition: Transition[Gap at 2017-03-25T01:00+02:00 to +03:00] transition: Transition[Overlap at 2017-10-28T01:00+03:00 to +02:00] transition: Transition[Gap at 2018-03-24T01:00+02:00 to +03:00] transition: Transition[Overlap at 2018-10-27T01:00+03:00 to +02:00] transition: Transition[Gap at 2019-03-29T00:00+02:00 to +03:00] transition: Transition[Overlap at 2019-10-26T00:00+03:00 to +02:00] transition: Transition[Gap at 2020-03-28T00:00+02:00 to +03:00] transition: Transition[Overlap at 2020-10-24T01:00+03:00 to +02:00] transition: Transition[Gap at 2021-03-27T00:00+02:00 to +03:00] transition: Transition[Overlap at 2021-10-29T01:00+03:00 to +02:00] transition: Transition[Gap at 2022-03-27T00:00+02:00 to +03:00] transition: Transition[Overlap at 2022-10-29T02:00+03:00 to +02:00] transition: Transition[Gap at 2023-04-29T02:00+02:00 to +03:00] transition: Transition[Overlap at 2023-10-28T02:00+03:00 to +02:00] transition: Transition[Gap at 2024-04-13T02:00+02:00 to +03:00] transition: Transition[Overlap at 2024-10-26T02:00+03:00 to +02:00] transition: Transition[Gap at 2025-04-05T02:00+02:00 to +03:00] transition: Transition[Overlap at 2025-10-25T02:00+03:00 to +02:00] transition: Transition[Gap at 2026-03-28T02:00+02:00 to +03:00] transition: Transition[Overlap at 2026-10-24T02:00+03:00 to +02:00] transition: Transition[Gap at 2027-03-27T02:00+02:00 to +03:00] transition: Transition[Overlap at 2027-10-30T02:00+03:00 to +02:00] transition: Transition[Gap at 2028-03-25T02:00+02:00 to +03:00] transition: Transition[Overlap at 2028-10-28T02:00+03:00 to +02:00] transition: Transition[Gap at 2029-03-24T02:00+02:00 to +03:00] transition: Transition[Overlap at 2029-10-27T02:00+03:00 to +02:00] transition: Transition[Gap at 2030-03-30T02:00+02:00 to +03:00] transition: Transition[Overlap at 2030-10-26T02:00+03:00 to +02:00] transition: Transition[Gap at 2031-03-29T02:00+02:00 to +03:00] transition: Transition[Overlap at 2031-10-25T02:00+03:00 to +02:00] transition: Transition[Gap at 2032-03-27T02:00+02:00 to +03:00] transition: Transition[Overlap at 2032-10-30T02:00+03:00 to +02:00] transition: Transition[Gap at 2033-03-26T02:00+02:00 to +03:00] transition: Transition[Overlap at 2033-10-29T02:00+03:00 to +02:00] transition: Transition[Gap at 2034-03-25T02:00+02:00 to +03:00] transition: Transition[Overlap at 2034-10-28T02:00+03:00 to +02:00] transition: Transition[Gap at 2035-03-24T02:00+02:00 to +03:00] transition: Transition[Overlap at 2035-10-27T02:00+03:00 to +02:00] transition: Transition[Gap at 2036-03-29T02:00+02:00 to +03:00] transition: Transition[Overlap at 2036-10-18T02:00+03:00 to +02:00] transition: Transition[Gap at 2037-03-28T02:00+02:00 to +03:00] transition: Transition[Overlap at 2037-10-10T02:00+03:00 to +02:00] transition: Transition[Gap at 2038-03-27T02:00+02:00 to +03:00] transition: Transition[Overlap at 2038-09-25T02:00+03:00 to +02:00] transition: Transition[Gap at 2039-03-26T02:00+02:00 to +03:00] transition: Transition[Overlap at 2039-09-17T02:00+03:00 to +02:00] transition: Transition[Gap at 2039-10-22T02:00+02:00 to +03:00] transition: Transition[Overlap at 2039-10-29T02:00+03:00 to +02:00] transition: Transition[Gap at 2040-03-24T02:00+02:00 to +03:00] transition: Transition[Overlap at 2040-09-01T02:00+03:00 to +02:00] transition: Transition[Gap at 2040-10-13T02:00+02:00 to +03:00] transition: Transition[Overlap at 2040-10-27T02:00+03:00 to +02:00] transition: Transition[Gap at 2041-03-30T02:00+02:00 to +03:00] transition: Transition[Overlap at 2041-08-24T02:00+03:00 to +02:00] transition: Transition[Gap at 2041-09-28T02:00+02:00 to +03:00] transition: Transition[Overlap at 2041-10-26T02:00+03:00 to +02:00] transition: Transition[Gap at 2042-03-29T02:00+02:00 to +03:00] transition: Transition[Overlap at 2042-08-16T02:00+03:00 to +02:00] transition: Transition[Gap at 2042-09-20T02:00+02:00 to +03:00] transition: Transition[Overlap at 2042-10-25T02:00+03:00 to +02:00] transition: Transition[Gap at 2043-03-28T02:00+02:00 to +03:00] transition: Transition[Overlap at 2043-08-01T02:00+03:00 to +02:00] transition: Transition[Gap at 2043-09-12T02:00+02:00 to +03:00] transition: Transition[Overlap at 2043-10-24T02:00+03:00 to +02:00] transition: Transition[Gap at 2044-03-26T02:00+02:00 to +03:00] transition: Transition[Overlap at 2044-07-23T02:00+03:00 to +02:00] transition: Transition[Gap at 2044-08-27T02:00+02:00 to +03:00] transition: Transition[Overlap at 2044-10-29T02:00+03:00 to +02:00] transition: Transition[Gap at 2045-03-25T02:00+02:00 to +03:00] transition: Transition[Overlap at 2045-07-15T02:00+03:00 to +02:00] transition: Transition[Gap at 2045-08-19T02:00+02:00 to +03:00] transition: Transition[Overlap at 2045-10-28T02:00+03:00 to +02:00] transition: Transition[Gap at 2046-03-24T02:00+02:00 to +03:00] transition: Transition[Overlap at 2046-06-30T02:00+03:00 to +02:00] transition: Transition[Gap at 2046-08-11T02:00+02:00 to +03:00] transition: Transition[Overlap at 2046-10-27T02:00+03:00 to +02:00] transition: Transition[Gap at 2047-03-30T02:00+02:00 to +03:00] transition: Transition[Overlap at 2047-06-22T02:00+03:00 to +02:00] transition: Transition[Gap at 2047-07-27T02:00+02:00 to +03:00] transition: Transition[Overlap at 2047-10-26T02:00+03:00 to +02:00] transition: Transition[Gap at 2048-03-28T02:00+02:00 to +03:00] transition: Transition[Overlap at 2048-06-06T02:00+03:00 to +02:00] transition: Transition[Gap at 2048-07-18T02:00+02:00 to +03:00] transition: Transition[Overlap at 2048-10-24T02:00+03:00 to +02:00] transition: Transition[Gap at 2049-03-27T02:00+02:00 to +03:00] transition: Transition[Overlap at 2049-05-29T02:00+03:00 to +02:00] transition: Transition[Gap at 2049-07-03T02:00+02:00 to +03:00] transition: Transition[Overlap at 2049-10-30T02:00+03:00 to +02:00] transition: Transition[Gap at 2050-03-26T02:00+02:00 to +03:00] transition: Transition[Overlap at 2050-05-21T02:00+03:00 to +02:00] transition: Transition[Gap at 2050-06-25T02:00+02:00 to +03:00] transition: Transition[Overlap at 2050-10-29T02:00+03:00 to +02:00] transition: Transition[Gap at 2051-03-25T02:00+02:00 to +03:00] transition: Transition[Overlap at 2051-05-06T02:00+03:00 to +02:00] transition: Transition[Gap at 2051-06-17T02:00+02:00 to +03:00] transition: Transition[Overlap at 2051-10-28T02:00+03:00 to +02:00] transition: Transition[Gap at 2052-03-30T02:00+02:00 to +03:00] transition: Transition[Overlap at 2052-04-27T02:00+03:00 to +02:00] transition: Transition[Gap at 2052-06-01T02:00+02:00 to +03:00] transition: Transition[Overlap at 2052-10-26T02:00+03:00 to +02:00] transition: Transition[Gap at 2053-03-29T02:00+02:00 to +03:00] transition: Transition[Overlap at 2053-04-12T02:00+03:00 to +02:00] transition: Transition[Gap at 2053-05-24T02:00+02:00 to +03:00] transition: Transition[Overlap at 2053-10-25T02:00+03:00 to +02:00] transition: Transition[Gap at 2054-03-28T02:00+02:00 to +03:00] transition: Transition[Overlap at 2054-04-04T02:00+03:00 to +02:00] transition: Transition[Gap at 2054-05-16T02:00+02:00 to +03:00] transition: Transition[Overlap at 2054-10-24T02:00+03:00 to +02:00] transition: Transition[Gap at 2055-05-01T02:00+02:00 to +03:00] transition: Transition[Overlap at 2055-10-30T02:00+03:00 to +02:00] transition: Transition[Gap at 2056-04-22T02:00+02:00 to +03:00] transition: Transition[Overlap at 2056-10-28T02:00+03:00 to +02:00] transition: Transition[Gap at 2057-04-07T02:00+02:00 to +03:00] transition: Transition[Overlap at 2057-10-27T02:00+03:00 to +02:00] transition: Transition[Gap at 2058-03-30T02:00+02:00 to +03:00] transition: Transition[Overlap at 2058-10-26T02:00+03:00 to +02:00] transition: Transition[Gap at 2059-03-29T02:00+02:00 to +03:00] transition: Transition[Overlap at 2059-10-25T02:00+03:00 to +02:00] transition: Transition[Gap at 2060-03-27T02:00+02:00 to +03:00] transition: Transition[Overlap at 2060-10-30T02:00+03:00 to +02:00] transition: Transition[Gap at 2061-03-26T02:00+02:00 to +03:00] transition: Transition[Overlap at 2061-10-29T02:00+03:00 to +02:00] transition: Transition[Gap at 2062-03-25T02:00+02:00 to +03:00] transition: Transition[Overlap at 2062-10-28T02:00+03:00 to +02:00] transition: Transition[Gap at 2063-03-24T02:00+02:00 to +03:00] transition: Transition[Overlap at 2063-10-27T02:00+03:00 to +02:00] transition: Transition[Gap at 2064-03-29T02:00+02:00 to +03:00] transition: Transition[Overlap at 2064-10-25T02:00+03:00 to +02:00] transition: Transition[Gap at 2065-03-28T02:00+02:00 to +03:00] transition: Transition[Overlap at 2065-10-24T02:00+03:00 to +02:00] transition: Transition[Gap at 2066-03-27T02:00+02:00 to +03:00] transition: Transition[Overlap at 2066-10-30T02:00+03:00 to +02:00] transition: Transition[Gap at 2067-03-26T02:00+02:00 to +03:00] transition: Transition[Overlap at 2067-10-29T02:00+03:00 to +02:00] transition: Transition[Gap at 2068-03-24T02:00+02:00 to +03:00] transition: Transition[Overlap at 2068-10-20T02:00+03:00 to +02:00] transition: Transition[Gap at 2069-03-30T02:00+02:00 to +03:00] transition: Transition[Overlap at 2069-10-12T02:00+03:00 to +02:00] transition: Transition[Gap at 2070-03-29T02:00+02:00 to +03:00] transition: Transition[Overlap at 2070-10-04T02:00+03:00 to +02:00] transition: Transition[Gap at 2071-03-28T02:00+02:00 to +03:00] transition: Transition[Overlap at 2071-09-19T02:00+03:00 to +02:00] transition: Transition[Gap at 2072-03-26T02:00+02:00 to +03:00] transition: Transition[Overlap at 2072-09-10T02:00+03:00 to +02:00] transition: Transition[Gap at 2072-10-15T02:00+02:00 to +03:00] transition: Transition[Overlap at 2073-09-02T02:00+03:00 to +02:00] transition: Transition[Gap at 2073-10-07T02:00+02:00 to +03:00] transition: Transition[Overlap at 2074-08-18T02:00+03:00 to +02:00] transition: Transition[Gap at 2074-09-29T02:00+02:00 to +03:00] transition: Transition[Overlap at 2075-08-10T02:00+03:00 to +02:00] transition: Transition[Gap at 2075-09-14T02:00+02:00 to +03:00] transition: Transition[Overlap at 2075-10-26T02:00+03:00 to +02:00] transition: Transition[Gap at 2076-03-28T02:00+02:00 to +03:00] transition: Transition[Overlap at 2076-07-25T02:00+03:00 to +02:00] transition: Transition[Gap at 2076-09-05T02:00+02:00 to +03:00] transition: Transition[Overlap at 2076-10-24T02:00+03:00 to +02:00] transition: Transition[Gap at 2077-03-27T02:00+02:00 to +03:00] transition: Transition[Overlap at 2077-07-17T02:00+03:00 to +02:00] transition: Transition[Gap at 2077-08-28T02:00+02:00 to +03:00] transition: Transition[Overlap at 2077-10-30T02:00+03:00 to +02:00] transition: Transition[Gap at 2078-03-26T02:00+02:00 to +03:00] transition: Transition[Overlap at 2078-07-09T02:00+03:00 to +02:00] transition: Transition[Gap at 2078-08-13T02:00+02:00 to +03:00] transition: Transition[Overlap at 2078-10-29T02:00+03:00 to +02:00] transition: Transition[Gap at 2079-03-25T02:00+02:00 to +03:00] transition: Transition[Overlap at 2079-06-24T02:00+03:00 to +02:00] transition: Transition[Gap at 2079-08-05T02:00+02:00 to +03:00] transition: Transition[Overlap at 2079-10-28T02:00+03:00 to +02:00] transition: Transition[Gap at 2080-03-30T02:00+02:00 to +03:00] transition: Transition[Overlap at 2080-06-15T02:00+03:00 to +02:00] transition: Transition[Gap at 2080-07-20T02:00+02:00 to +03:00] transition: Transition[Overlap at 2080-10-26T02:00+03:00 to +02:00] transition: Transition[Gap at 2081-03-29T02:00+02:00 to +03:00] transition: Transition[Overlap at 2081-06-07T02:00+03:00 to +02:00] transition: Transition[Gap at 2081-07-12T02:00+02:00 to +03:00] transition: Transition[Overlap at 2081-10-25T02:00+03:00 to +02:00] transition: Transition[Gap at 2082-03-28T02:00+02:00 to +03:00] transition: Transition[Overlap at 2082-05-23T02:00+03:00 to +02:00] transition: Transition[Gap at 2082-07-04T02:00+02:00 to +03:00] transition: Transition[Overlap at 2082-10-24T02:00+03:00 to +02:00] transition: Transition[Gap at 2083-03-27T02:00+02:00 to +03:00] transition: Transition[Overlap at 2083-05-15T02:00+03:00 to +02:00] transition: Transition[Gap at 2083-06-19T02:00+02:00 to +03:00] transition: Transition[Overlap at 2083-10-30T02:00+03:00 to +02:00] transition: Transition[Gap at 2084-03-25T02:00+02:00 to +03:00] transition: Transition[Overlap at 2084-04-29T02:00+03:00 to +02:00] transition: Transition[Gap at 2084-06-10T02:00+02:00 to +03:00] transition: Transition[Overlap at 2084-10-28T02:00+03:00 to +02:00] transition: Transition[Gap at 2085-03-24T02:00+02:00 to +03:00] transition: Transition[Overlap at 2085-04-21T02:00+03:00 to +02:00] transition: Transition[Gap at 2085-06-02T02:00+02:00 to +03:00] transition: Transition[Overlap at 2085-10-27T02:00+03:00 to +02:00] transition: Transition[Gap at 2086-03-30T02:00+02:00 to +03:00] transition: Transition[Overlap at 2086-04-13T02:00+03:00 to +02:00] transition: Transition[Gap at 2086-05-18T02:00+02:00 to +03:00] transition: Transition[Overlap at 2086-10-26T02:00+03:00 to +02:00] transition: Transition[Gap at 2087-03-29T02:00+02:00 to +03:00] transition: Transition[Overlap at 2087-10-25T02:00+03:00 to +02:00] transitionrule: TransitionRule[Gap +02:00 to +03:00, SATURDAY on or after MARCH 24 at 02:00 WALL, standard offset +02:00] transitionrule: TransitionRule[Overlap +03:00 to +02:00, SATURDAY on or after OCTOBER 24 at 02:00 WALL, standard offset +02:00] Note that the dstSavings property is now set to 3600000! This very much looks like the tzdb-1.8 utility has a problem compiling the current 2023c time zone database. This utility is quite old and might not be able to deal with some features of the IANA time zone database format: andreas@ws1:~> rpm -qilv tzdb Name : tzdb Version : 1.8 Release : 3.39 Architecture: noarch Install Date: Thu Jul 20 19:31:53 2023 Group : Development/Libraries/Java Size : 103617 License : GPL-2.0-with-classpath-exception Signature : RSA/SHA256, Thu May 31 11:27:52 2018, Key ID 70af9e8139db7c82 Source RPM : tzdb-1.8-3.39.src.rpm Build Date : Thu May 31 11:27:45 2018 Build Host : sheep62 Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : SUSE LLC <https://www.suse.com/> URL : http://icedtea.classpath.org Summary : Time zone rules compiler Java Description : This is a time zone rules compiler for opensource Java Virtual Machine derived from openjdk8 source code. Distribution: SUSE Linux Enterprise 15 -rw-r--r-- 1 root root 38656 May 31 2018 /usr/share/java/tzdb-1.8.jar lrwxrwxrwx 1 root root 12 May 31 2018 /usr/share/java/tzdb.jar -> tzdb-1.8.jar drwxr-xr-x 2 root root 0 May 31 2018 /usr/share/tzdb drwxr-xr-x 2 root root 0 Apr 24 2014 /usr/share/tzdb/tzdata_jdk -rw-r--r-- 1 root root 1251 Apr 24 2014 /usr/share/tzdb/tzdata_jdk/gmt -rw-r--r-- 1 root root 2153 Apr 24 2014 /usr/share/tzdb/tzdata_jdk/jdk11_backward -rw-r--r-- 1 root root 20415 Apr 24 2014 /usr/share/tzdb/tzdata_jdk/solar87 -rw-r--r-- 1 root root 20433 Apr 24 2014 /usr/share/tzdb/tzdata_jdk/solar88 -rw-r--r-- 1 root root 20709 Apr 24 2014 /usr/share/tzdb/tzdata_jdk/solar89
Confirmed, this is also impacting the latest version on Tumbleweed: timezone-java-2023d-1.1.noarch.
I've tested the approach you suggested, Andreas, and as you mentioned, it seems to solve the issue. I'm now looking into how we could use this tool during the build on OBS/IBS, especially the legal implications regarding licensing for Oracle's tzupdater.
I've sent an email to the legal team. Meanwhile, another fix that exists is to simply uninstall the timezone-java package. If this package isn't installed, then the data from the "timezone" package is used by the JDK to determine timezone information. That also solves this issue, and we don't need to use Oracle's tools and maintain two sets of timezone packages at the same time. Does anyone have an opinion here?
The legal team has sent me a message telling me it's strongly discouraged for us to use Oracle's tool, for legal reasons. Therefore I suggest we drop the timezone-java package altogether, instead letting the JDK rely on the 'timezone' package data for its timezone information.
(In reply to Martin Schreiner from comment #11) > The legal team has sent me a message telling me it's strongly discouraged > for us to use Oracle's tool, for legal reasons. > > Therefore I suggest we drop the timezone-java package altogether, instead > letting the JDK rely on the 'timezone' package data for its timezone > information. When the timezone-java is not installed, openjdk uses internal timezone data. Which is normally synced quarterly with every CPU update.
Request submitted: https://build.opensuse.org/request/show/1157982 We're dropping timezone-java.
Request for openSUSE:Factory: https://build.opensuse.org/request/show/1158028
A final comment here, before I close this ticket. Martin Schreiner, Fridrich Strba and Danilo Spinella have, collectively, removed the "timezone-java" package from SLE-15-SP6 and openSUSE Factory. The rationale applied was the same as has been explained on this ticket: "timezone-java" is not a requirement, as the JDK itself has its own timezone data that is refreshed whenever the JDK is upgraded. That is, each upgrade has the up-to-date timezone data from when it was released. In the case of SLE <= 15-SP5, even though the "timezone-java" package will still exist there, the JDK has been recompiled across all code streams to no longer care about the data provided by "timezone-java". So even though the package still exists, its contents are never used. We're not removing the package there as that requires a whole process. But this issue is fixed there as well, in practice.
SUSE-SU-2024:1452-1: An update that solves five vulnerabilities and has one security fix can now be installed. Category: security (low) Bug References: 1213470, 1222979, 1222983, 1222984, 1222986, 1222987 CVE References: CVE-2024-21011, CVE-2024-21012, CVE-2024-21068, CVE-2024-21085, CVE-2024-21094 Maintenance Incident: [SUSE:Maintenance:33457](https://smelt.suse.de/incident/33457/) Sources used: SUSE Linux Enterprise High Performance Computing 12 SP5 (src): java-11-openjdk-11.0.23.0-3.75.1 SUSE Linux Enterprise Server 12 SP5 (src): java-11-openjdk-11.0.23.0-3.75.1 SUSE Linux Enterprise Server for SAP Applications 12 SP5 (src): java-11-openjdk-11.0.23.0-3.75.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
SUSE-SU-2024:1451-1: An update that solves four vulnerabilities and has one security fix can now be installed. Category: security (low) Bug References: 1213470, 1222979, 1222983, 1222984, 1222986 CVE References: CVE-2024-21011, CVE-2024-21068, CVE-2024-21085, CVE-2024-21094 Maintenance Incident: [SUSE:Maintenance:33542](https://smelt.suse.de/incident/33542/) Sources used: openSUSE Leap 15.5 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 Legacy Module 15-SP5 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP3 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 SUSE Linux Enterprise High Performance Computing ESPOS 15 SP4 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP4 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 SUSE Linux Enterprise Server 15 SP2 LTSS 15-SP2 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 SUSE Linux Enterprise Server 15 SP3 LTSS 15-SP3 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 SUSE Linux Enterprise Server 15 SP4 LTSS 15-SP4 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 SUSE Linux Enterprise Server for SAP Applications 15 SP2 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 SUSE Linux Enterprise Server for SAP Applications 15 SP3 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 SUSE Linux Enterprise Server for SAP Applications 15 SP4 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 SUSE Enterprise Storage 7.1 (src): java-1_8_0-openjdk-1.8.0.412-150000.3.91.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
SUSE-SU-2024:1450-1: An update that solves four vulnerabilities and has one security fix can now be installed. Category: security (low) Bug References: 1213470, 1222979, 1222983, 1222984, 1222986 CVE References: CVE-2024-21011, CVE-2024-21068, CVE-2024-21085, CVE-2024-21094 Maintenance Incident: [SUSE:Maintenance:33541](https://smelt.suse.de/incident/33541/) Sources used: SUSE Linux Enterprise High Performance Computing 12 SP5 (src): java-1_8_0-openjdk-1.8.0.412-27.99.1 SUSE Linux Enterprise Server 12 SP5 (src): java-1_8_0-openjdk-1.8.0.412-27.99.1 SUSE Linux Enterprise Server for SAP Applications 12 SP5 (src): java-1_8_0-openjdk-1.8.0.412-27.99.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
SUSE-SU-2024:1499-1: An update that solves four vulnerabilities and has one security fix can now be installed. Category: security (low) Bug References: 1213470, 1222979, 1222983, 1222986, 1222987 CVE References: CVE-2024-21011, CVE-2024-21012, CVE-2024-21068, CVE-2024-21094 Maintenance Incident: [SUSE:Maintenance:33458](https://smelt.suse.de/incident/33458/) Sources used: openSUSE Leap 15.4 (src): java-17-openjdk-17.0.11.0-150400.3.42.1 openSUSE Leap 15.5 (src): java-17-openjdk-17.0.11.0-150400.3.42.1 Basesystem Module 15-SP5 (src): java-17-openjdk-17.0.11.0-150400.3.42.1 SUSE Linux Enterprise High Performance Computing ESPOS 15 SP4 (src): java-17-openjdk-17.0.11.0-150400.3.42.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP4 (src): java-17-openjdk-17.0.11.0-150400.3.42.1 SUSE Linux Enterprise Desktop 15 SP4 LTSS 15-SP4 (src): java-17-openjdk-17.0.11.0-150400.3.42.1 SUSE Linux Enterprise Server 15 SP4 LTSS 15-SP4 (src): java-17-openjdk-17.0.11.0-150400.3.42.1 SUSE Linux Enterprise Server for SAP Applications 15 SP4 (src): java-17-openjdk-17.0.11.0-150400.3.42.1 SUSE Manager Proxy 4.3 (src): java-17-openjdk-17.0.11.0-150400.3.42.1 SUSE Manager Retail Branch Server 4.3 (src): java-17-openjdk-17.0.11.0-150400.3.42.1 SUSE Manager Server 4.3 (src): java-17-openjdk-17.0.11.0-150400.3.42.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
SUSE-SU-2024:1498-1: An update that solves five vulnerabilities and has one security fix can now be installed. Category: security (low) Bug References: 1213470, 1222979, 1222983, 1222984, 1222986, 1222987 CVE References: CVE-2024-21011, CVE-2024-21012, CVE-2024-21068, CVE-2024-21085, CVE-2024-21094 Maintenance Incident: [SUSE:Maintenance:33455](https://smelt.suse.de/incident/33455/) Sources used: SUSE Linux Enterprise High Performance Computing LTSS 15 SP4 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Linux Enterprise Desktop 15 SP4 LTSS 15-SP4 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Linux Enterprise Server 15 SP2 LTSS 15-SP2 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Linux Enterprise Server 15 SP3 LTSS 15-SP3 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Linux Enterprise Server 15 SP4 LTSS 15-SP4 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Linux Enterprise Server for SAP Applications 15 SP2 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Linux Enterprise Server for SAP Applications 15 SP3 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Linux Enterprise Server for SAP Applications 15 SP4 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Manager Proxy 4.3 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Manager Retail Branch Server 4.3 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Manager Server 4.3 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Enterprise Storage 7.1 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 openSUSE Leap 15.5 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 Basesystem Module 15-SP5 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Package Hub 15 15-SP5 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Linux Enterprise High Performance Computing 15 SP2 LTSS 15-SP2 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP3 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 SUSE Linux Enterprise High Performance Computing ESPOS 15 SP4 (src): java-11-openjdk-11.0.23.0-150000.3.113.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
SUSE-SU-2024:1793-1: An update that solves four vulnerabilities and has one security fix can now be installed. Category: security (moderate) Bug References: 1213470, 1222979, 1222983, 1222984, 1222986 CVE References: CVE-2024-21011, CVE-2024-21068, CVE-2024-21085, CVE-2024-21094 Maintenance Incident: [SUSE:Maintenance:34021](https://smelt.suse.de/incident/34021/) Sources used: openSUSE Leap 15.6 (src): java-1_8_0-openj9-1.8.0.412-150200.3.45.2 SUSE Package Hub 15 15-SP5 (src): java-1_8_0-openj9-1.8.0.412-150200.3.45.2 SUSE Package Hub 15 15-SP6 (src): java-1_8_0-openj9-1.8.0.412-150200.3.45.2 openSUSE Leap 15.5 (src): java-1_8_0-openj9-1.8.0.412-150200.3.45.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.