- tz - lists.iana.org

tzcode and tzdata tar base make checks fail
by Brian Inglis Dec. 31, 2025

Dec. 31, 2025

Cygwin uses separate packages of tzcode programs and tzdata files verbatim to support standard local time zones in preference to limited native data. Running make check on the separate tar file fails in both cases. When I took over the packages, I provided basic checks, but reviewed and changed the builds this release, and would like to reenable the built in checks you provide and mentioned recently. The attached logs show the results of having the package build scripts run `make check` from the package build directory which is set up with symlinks to each of the tar sources. Is there anything obviously missing or incorrect with `make check` invocations which could cause the observed failures, or things that may need changed? -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut -- Antoine de Saint-Exupéry

2 6

Time zones on Antarctica expedition
by Brooks Harris Dec. 30, 2025

Dec. 30, 2025

Those who have a New York Times subscription may find this entertaining: Does Anybody Really Know What Time It Is? The clocks aboard our icebreaker will be changed several times en route to Antarctica. It’s one of many things that make the expedition feel otherworldly. https://www.nytimes.com/2025/12/29/climate/antarctica-time-zone.html

1 0

[PROPOSED] Fix some unsequenced/reproducible commentary
by Paul Eggert Dec. 21, 2025

Dec. 21, 2025

* private.h (ATTRIBUTE_CONST, ATTRIBUTE_PURE): In commentary do not say that __attribute__((const)) is stricter than [[unsequenced]], as Jens Gustedt, an originator of [[unsequenced]], wrote in <https://lists.gnu.org/r/bug-gnulib/2025-01/msg00190.html> that some const functions are not unsequenced. To be safe, make a similar change for __attribute__((pure)) and [[reproducible]], though I don’t have confirmation from Jens. --- private.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/private.h b/private.h index 074da284..50d6a52a 100644 --- a/private.h +++ b/private.h @@ -619,11 +619,11 @@ typedef unsigned long uintmax_t; # define ATTRIBUTE_UNSEQUENCED /* empty */ #endif -/* GCC attributes that are useful in tzcode. - __attribute__((const)) is stricter than [[unsequenced]], - so the latter is an adequate substitute in non-GCC C23 platforms. - __attribute__((pure)) is stricter than [[reproducible]], - so the latter is an adequate substitute in non-GCC C23 platforms. */ +/* GNU C attributes that are useful in tzcode. + Although neither __attribute__((const)) nor __attribute__((pure)) are + stricter than their C23 counterparts [[unsequenced]] and [[reproducible]], + the C23 attributes happen to work in each tzcode use of ATTRIBUTE_CONST + and ATTRIBUTE_PURE. (This might not work outside of tzcode!) */ #if __GNUC__ < 3 # define ATTRIBUTE_CONST ATTRIBUTE_UNSEQUENCED # define ATTRIBUTE_FORMAT(spec) /* empty */ -- 2.51.0

2 5

TYPE_SIGNED(t) warnings..
by Christos Zoulas Dec. 19, 2025

Dec. 19, 2025

Hi, Gcc with -Wall -Wextra -Wtype-limits produces warnings with: #define TYPE_SIGNED(T) ((T)-1) < 0) error: comparison of unsigned expression in '< 0' is always false [-Werror=type-limits] Perhaps use something that checks the sign bit directly? #define TYPE_SIGNED(T) \ (((T)~(T)0 >> (sizeof(T) * CHAR_BIT - 1)) == (T)-1) Or something from NetBSD's <sys/cdefs.h>? christos

2 2

2025c zic.c calls fflush(3) on read only file pointer.
by Christos Zoulas Dec. 18, 2025

Dec. 18, 2025

Hello, This is undefined behavior. NetBSD returns EOF and sets errno to EBADFD. I am not sure why fflush(3) is called explicitly now, since fclose(3) does it anyway. Best, christos

6 7

[Feature Request] Add validation in zic for invalid DST intervals
by 任春辉 Dec. 17, 2025

Dec. 17, 2025

Hello tzdata maintainers, I would like to propose a feature enhancement for the zic compiler. Currently, the NOS time zone rules are defined as: Rule NOS 1970 2037 - Jan 27 23:43:01 2:0 SDST Rule NOS 1970 2037 - Jan 28 0:51:01 0 S Zone OS/NOS +7:0:0 NOS NO%s Issue: - The first rule enters DST at 23:43:01 with a +2 hour offset, moving local time to 01:43:01. - The second rule is intended to revert to standard time at 00:51:01. - Due to the offset, 00:51:01 local time never occurs, so the second rule will never trigger. - This creates unreachable local times and may cause incorrect results in time calculations. Proposal: - Add validation in the zic command to detect DST rules where the offset causes the subsequent rule's local time to be unreachable. - The validation could issue a warning or error to alert the author of potentially invalid rules. - This would improve the robustness of time zone definitions and prevent subtle bugs in downstream applications. Thank you for your consideration. Best regards

3 5

[PROPOSED] Make HTML view better on cell phones
by Paul Eggert Dec. 16, 2025

Dec. 16, 2025

Unfortunately without the meta viewport element described below, most mobile browers default to unreadably tiny text for backward compatibility with how the iPhone misbehaved in 2007. While we’re giving up on vanilla style, improve readability in minor ways for bigger screens too. Here are the changes made: * Add to HTML files the element <meta name="viewport" content="width=device-width, initial-scale=1">. This is the most common setting mentioned in <https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/meta/n…>. * Style pre elements with "overflow: auto", not "white-space: prewrap". * Decrease pre elements’ margins from 2em to 1.3rem, and change margins/padding for dd and ul to 1.3rem. * In tz-how-to.html, stop trying to package a wideish pre element inside a table, as that’s too painful to do portably and nicely on both narrow and wide screens. Just do a pre followed by a table. --- theory.html | 5 +++- tz-art.html | 4 +++ tz-how-to.html | 72 +++++++++----------------------------------------- tz-link.html | 5 +++- 4 files changed, 25 insertions(+), 61 deletions(-) diff --git a/theory.html b/theory.html index e6e64177..8c802858 100644 --- a/theory.html +++ b/theory.html @@ -3,8 +3,11 @@ <head> <title>Theory and pragmatics of the tz code and data</title> <meta charset="UTF-8"> + <meta name="viewport" content="width=device-width, initial-scale=1"> <style> - pre {margin-left: 2em; white-space: pre-wrap;} + dd {margin-left: 1.3rem;} + pre {margin-left: 1.3rem; overflow: auto;} + ul {padding-left: 1.3rem;} </style> </head> diff --git a/tz-art.html b/tz-art.html index 3039a86f..5f92fa1b 100644 --- a/tz-art.html +++ b/tz-art.html @@ -2,6 +2,10 @@ <html lang="en"> <head> <meta charset="UTF-8"> +<meta name="viewport" content="width=device-width, initial-scale=1"> +<style> +ul {padding-left: 1.3rem;} +</style> <title>Time and the Arts</title> </head> <body> diff --git a/tz-how-to.html b/tz-how-to.html index ccfdc9eb..ddafb2aa 100644 --- a/tz-how-to.html +++ b/tz-how-to.html @@ -3,14 +3,15 @@ <head> <title>How to Read the tz Database</title> <meta charset="UTF-8"> +<meta name="viewport" content="width=device-width, initial-scale=1"> <style> -pre {margin-left: 2em; white-space: pre-wrap;} -pre.td {margin-left: 0;} +pre {margin-left: 1.3rem; overflow: auto;} td {text-align: center;} table {border: 1px outset;} th, td {border: 1px inset;} table.rule {border: none; margin: auto;} td.footnote {text-align: left;} +ul {padding-left: 1.3rem;} </style> </head> <body> @@ -38,16 +39,7 @@ about the zones.</p> for Chicago (from the <code>northamerica</code> file in the <code>data</code> subdirectory):</p> -<table> -<tr> - <th colspan="6">From the Source File</th> -</tr> -<tr> - <td colspan="6"> - <table class="rule"> - <tr><td style="border:none;text-align:left"> -<pre class="td"> -#Rule NAME FROM TO - IN ON AT SAVE LETTER +<pre>#Rule NAME FROM TO - IN ON AT SAVE LETTER Rule Chicago 1920 only - Jun 13 2:00 1:00 D Rule Chicago 1920 1921 - Oct lastSun 2:00 0 S Rule Chicago 1921 only - Mar lastSun 2:00 1:00 D @@ -55,8 +47,7 @@ Rule Chicago 1922 1966 - Apr lastSun 2:00 1:00 D Rule Chicago 1922 1954 - Sep lastSun 2:00 0 S Rule Chicago 1955 1966 - Oct lastSun 2:00 0 S </pre> - </td></tr></table></td> -</tr> +<table> <tr> <th colspan="6">Reformatted a Bit</th> </tr> @@ -160,16 +151,7 @@ time changed in 1955. Got it?</p> <p>OK, now for the somewhat more interesting “US” rules:</p> -<table> -<tr> - <th colspan="6">From the Source File</th> -</tr> -<tr> - <td colspan="6"> - <table class="rule"> - <tr><td style="border:none;text-align:left"> -<pre class="td"> -#Rule NAME FROM TO - IN ON AT SAVE LETTER/S +<pre>#Rule NAME FROM TO - IN ON AT SAVE LETTER/S Rule US 1918 1919 - Mar lastSun 2:00 1:00 D Rule US 1918 1919 - Oct lastSun 2:00 0 S Rule US 1942 only - Feb 9 2:00 1:00 W # War @@ -184,8 +166,7 @@ Rule US 1987 2006 - Apr Sun>=1 2:00 1:00 D Rule US 2007 max - Mar Sun>=8 2:00 1:00 D Rule US 2007 max - Nov Sun>=1 2:00 0 S </pre> - </td></tr></table></td> -</tr> +<table> <tr> <th colspan="6">Reformatted a Bit</th> </tr> @@ -328,15 +309,7 @@ rule, so there should be no change.</li> <p>OK, now let’s look at a Zone record:</p> -<table> -<tr> - <th colspan="5">From the Source File</th> -</tr> -<tr> - <td colspan="5"> - <table class="rule"> - <tr><td style="border:none;text-align:left"> -<pre class="td"> +<pre> #Zone NAME STDOFF RULES FORMAT [UNTIL] Zone America/Chicago -5:50:36 - LMT 1883 Nov 18 12:09:24 -6:00 US C%sT 1920 @@ -347,8 +320,7 @@ Zone America/Chicago -5:50:36 - LMT 1883 Nov 18 12:09:24 -6:00 Chicago C%sT 1967 -6:00 US C%sT </pre> - </td></tr></table></td> -</tr> +<table> <tr> <th colspan="5">Columns Renamed</th> </tr> @@ -576,31 +548,14 @@ the true offset is undefined. <p>As a final example, here’s the complete history for Hawaii:</p> -<table> -<tr> - <th colspan="6">Relevant Excerpts from the US Rules</th> -</tr> -<tr> - <td colspan="6"> - <table class="rule"> - <tr><td style="border:none;text-align:left"> -<pre class="td"> +<pre># Relevant Excerpts from the US Rules</th> #Rule NAME FROM TO - IN ON AT SAVE LETTER/S Rule US 1918 1919 - Oct lastSun 2:00 0 S Rule US 1942 only - Feb 9 2:00 1:00 W # War Rule US 1945 only - Aug 14 23:00u 1:00 P # Peace Rule US 1945 only - Sep lastSun 2:00 0 S -</pre> - </td></tr></table></td> -</tr> -<tr> - <th colspan="6">The Zone Record</th> -</tr> -<tr> - <td colspan="6"> - <table class="rule"> - <tr><td style="border:none;text-align:left"> -<pre class="td"> + +# The Zone Record #Zone NAME STDOFF RULES FORMAT [UNTIL] Zone Pacific/Honolulu -10:31:26 - LMT 1896 Jan 13 12:00 -10:30 - HST 1933 Apr 30 2:00 @@ -608,8 +563,7 @@ Zone Pacific/Honolulu -10:31:26 - LMT 1896 Jan 13 12:00 -10:30 US H%sT 1947 Jun 8 2:00 -10:00 - HST </pre> - </td></tr></table></td> -</tr> +<table> <tr> <th colspan="6">What We Infer</th> </tr> diff --git a/tz-link.html b/tz-link.html index ba10a68b..5e941a8d 100644 --- a/tz-link.html +++ b/tz-link.html @@ -3,8 +3,11 @@ <head> <title>Time zone and daylight saving time data</title> <meta charset="UTF-8"> +<meta name="viewport" content="width=device-width, initial-scale=1"> <style> -pre {margin-left: 2em; white-space: pre-wrap;} +dd {margin-left: 1.3rem;} +pre {margin-left: 1.3rem; overflow: auto;} +ul {padding-left: 1.3rem;} </style> </head> <body> -- 2.51.0

1 0

Re: [PROPOSED] Mention -Dst_ctim=M in CFLAGS
by Paul Eggert Dec. 12, 2025

Dec. 12, 2025

On 2025-12-11 22:08, Robert Elz wrote: > Prior to this (since inception) we (everything BSD derived) had > st_ctimespec ... you might want to give an example of an actual use > of -Dst_ctim=M and that might be a useful one to use, as it was so > common Thanks, good suggestion. Come to think of it, it's probably clearer to give only the st_ctimespec example and let any (probably zero) builders for obscure OS versions deduce the more-general case. I installed the attached further proposed patch.

1 0

[PROPOSED] Mention -Dst_ctim=M in CFLAGS
by Paul Eggert Dec. 11, 2025

Dec. 11, 2025

* Makefile: Add comment about using -Dst_ctim=M in CFLAGS. As far as I know this matters only on POSIXish platforms so old that they’re no longer supported by their suppliers, e.g., FreeBSD 8.4 (2013), old NetBSD, old UnixWare. --- Makefile | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index eda8d53d..09f20100 100644 --- a/Makefile +++ b/Makefile @@ -284,8 +284,10 @@ LDLIBS= # -DHAVE_STRDUP=0 if your system lacks the strdup function # -DHAVE_STRNLEN=0 if your system lacks the strnlen function+ # -DHAVE_STRTOLL=0 if your system lacks the strtoll function+ -# -DHAVE_STRUCT_STAT_ST_CTIM=0 if struct stat lacks a member st_ctim -# and code should use st_ctime instead+ +# -DHAVE_STRUCT_STAT_ST_CTIM=0 if struct stat lacks a status-change member +# of type struct timespec, so code should use st_ctime instead; +# but if the status-change member is called M rather than st_ctim, +# use -Dst_ctim=M instead (default is guessed)+ # -DHAVE_STRUCT_TIMESPEC=0 if your system lacks struct timespec+ # -DHAVE_SYMLINK=0 if your system lacks the symlink function # -DHAVE_SYS_STAT_H=0 if <sys/stat.h> does not work* -- 2.51.0

1 0

[tz-announce] 2025c release of tz code and data available
by Paul Eggert via tz-announce Dec. 11, 2025

Dec. 11, 2025

The 2025c release of the tz code and data is available. This release mostly changes code and commentary. The only changed data are leap second table expiration and pre-1976 time in Baja California. This release contains the following changes: Briefly: Several code changes for compatibility with FreeBSD. 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. (Thanks to Alois Treindl.) Changes to build procedure Files in distributed tarballs now have correct commit times. Formerly, the committer’s time zone was incorrectly ignored. Distribution products (*.asc, *.gz, and *.lz) now have reproducible timestamps. Formerly, only the contents of the compressed tarballs had reproducible timestamps. By default, distributed formatted man pages (*.txt) now use UTF-8 and are left-adjusted more consistently. A new Makefile macro MANFLAGS can override these defaults. (Thanks to G. Branden Robinson for inspiring these changes.) Changes to code An unset TZ is no longer invalid when /etc/localtime is missing, and is abbreviated "UTC" not "-00". This reverts to 2024b behavior. (Problem and patch reported by Dag-Erling Smørgrav.) New function offtime_r, short for fixed-offset localtime_rz. It is defined if STD_INSPIRED is defined. (Patch from Dag-Erling Smørgrav.) tzset etc. are now more cautious about questionable TZ settings. Privileged programs now reject TZ settings that start with '/', unless they are TZDEFAULT (default "/etc/localtime") or start with TZDIR then '/' (default "/usr/share/zoneinfo/"). Unprivileged programs now require files to be regular files and reject relative names containing ".." directory components; formerly, only privileged programs did those two things. These changes were inspired by similar behavior in FreeBSD. On NetBSD, unprivileged programs now use O_REGULAR to check whether a TZ setting starting with '/' names a regular file, avoiding a minor security race still present elsewhere. TZ strings taken from tzalloc arguments are now treated with no less caution than TZ strings taken from the environment, as the old undocumented behavior would have been hard to explain. tzset etc. no longer use the ‘access’ system call to check access; instead they now use the system calls issetugid, getauxval, getresuid/getresgid, and geteuid/getegid/getuid/getgid (whichever first works) to test whether a program is privileged. Compile with -DHAVE_SYS_AUXV_H=[01] to enable or disable <sys/auxv.h> which (if it defines AT_SECURE) enables getauxval, and compile with -DHAVE_ISSETUGID=[01], -DHAVE_GETRESUID=[01], and -DHAVE_GETEUID=[01] to enable or disable the other calls’ use. The new CFLAGS option -DTZ_CHANGE_INTERVAL=N makes tzset etc. check for TZif file changes if the in-memory data are N seconds old or more, and are derived from the TZ environment variable. This is intended for platforms that want tzset etc. to reflect changes to whatever file TZ selects (including changes to /etc/localtime if TZ is unset). If N is negative (the default) these checks are omitted; this is the traditional behavior. The new CFLAGS options -DHAVE_STRUCT_STAT_ST_CTIM=0 and -DHAVE_STRUCT_TIMESPEC=0 port to non-POSIX.1-2008 platforms that lack st_ctim and struct timespec, respectively. tzset etc. now treat ' ' like '_' in time zone abbreviations, just as they treat other invalid bytes. This continues the transition begun in release 96k, which removed spaces in tzdata because the spaces break time string parsers. The new CFLAGS option -DTHREAD_PREFER_SINGLE causes tzcode in single-threaded processes to avoid locks, as FreeBSD does. This can save time in single-threaded apps. The threadedness testing costs CPU time and energy in multi-threaded apps. New options -DHAVE___ISTHREADED and -DHAVE_SYS_SINGLE_THREADED_H can help configure how to test for single-threadedness. The new CFLAGS option -DTHREAD_RWLOCK uses read-write locks, as macOS does, instead of mutexes. This saves real time when TZ is rarely changing and many threads call tzcode simultaneously. It costs more CPU time and energy. The new CFLAGS option -TTHREAD_TM_MULTI causes localtime to return a pointer to thread-specific memory, as FreeBSD does, instead of to the same memory in all threads. This supports unportable programs that incorrectly use localtime instead of localtime_r. This option affects gmtime and offtime similarly to localtime. Because the corresponding storage is freed on thread exit, this option is incompatible with POSIX.1-2024 and earlier. It also costs CPU time and memory. tzfree now preserves errno, consistently with POSIX.1-2024 ‘free’. tzcode now uses mempcpy if available, guessing its availability. Compile with -DHAVE_MEMPCPY=1 or 0 to override the guess. tzcode now uses strnlen to improve asymptotic performance a bit. Compile with -DHAVE_STRNLEN=0 if your platform lacks it. tzcode now hand-declares unistd.h-provided symbols like getopt if HAVE_UNISTD_H=0, not if HAVE_POSIX_DECLS=0. tzset etc. now have an experimental OPENAT_TZDIR option; see Makefile and localtime.c for details. On platforms like GNU/Hurd that do not define PATH_MAX, exceedingly long TZ strings no longer fail merely because they exceed an arbitrary file name length limit imposed by tzcode. zic has new options inspired by FreeBSD. ‘-D’ skips creation of output ancestor directories, ‘-m MODE’ sets output files’ mode, and ‘-u OWNER[:GROUP]’ sets output files’ owner and group. zic now uses the fdopen function, which was standardized by POSIX.1-1988 and is now safe to use in portable code. This replaces its use of the older umask function, which complicated maintenance. Changes to commentary The leapseconds file contains commentary about the IERS and NIST last-modified and expiration timestamps for leap second data. (Thanks to Judah Levine.) Commentary now also uses characters from the set –‘’“”•≤ as this can be useful and should work with current applications. This also affects data in iso3166.tab and zone1970.tab, which now contain strings like “Côte d’Ivoire” instead of “Côte d'Ivoire”. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2025c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2025c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2025c.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 7e1145bfdb9630c127841dc8ce808a937a300938 dated 2025-03-22 13:40:46 -0700 and tagged '2025c' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: d14bc0680b9cb33d6526a2c0e483f2abafc2593cfe5fbfe7dcab940aafdc1baaec065dbaa1bb58b03586a8631ffdf43ebb22ff5a70503298b6ea2cf061d82c16 tzcode2025c.tar.gz 1e33f7212fd0ae2ad3c16e68f0c1fc7a6ad26a126b8406c379a5768d79604c6a816054bd0fe3a63228d70cd6a1fc2b1bae2a9f8014e102d3727eb9d21affa1f1 tzdata2025c.tar.gz 6fa233d6a884acd24b52c44b2eecf683f9403f44b39dcbe85b1ec92fc11f4daf6ee5143f05332faf9258b8bd8f7ca7d4882e19b1e3d892b4761be43fd4f39d51 tzdb-2025c.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmk5+AQACgkQ7ZfpDmKq fjS7FQ/+OcQWOkAheWXB17w3dzqEaBTzzOFPoVWJkYDYYqRBFYcZHt6SL8NsJ6Vr 4PRv8UXvGZZhyamQY6CA3Te6/SRBTn4vKAPPYrwRxRENBHJtwf00H4khIqzL4iuu Lni7d3MyEurnQ99YKdCdsDM7V2GqGov8SFOIQWohAazL29n/396Me68Excr7WYh2 FY1qmbqQhBuh9WrQ9+YznWkKd5FcPj0a8+XBReABUR3yV58qZ4rvDhDpx+476U09 5PlOHgC3FdEII+I8ihKI+Y0FW20dDfyTc7Eechef2z3izlzaxSFbAXXQX1gs1Vj+ yhjp+MiJC9UiFP0VmafGdpuhNWafrRSF8uyhHEAPC2WRRSlz3hUBFchOWRBpgAkT yIhN7dUWPPT80Pu2vWn3Y647I8397b6mS5o8tLpgcU9S82phwY3zVtsXG4WjVVC/ RcNCyG0J2ybP+IA8r/jPdINLNm+lsdJKoU6Y19R+BJyAV1uycltUEx4yzxs8Mg/8 lxvg+JcKe94UhUHIQXo3j9lXg7KcFXCVjGBBBpfBn4FfcRmdA+IkgONF3MxWz86J 8jBJdSVi2/CjlteWVQ2pBKEEesjXjT0tX8dbVA2x4KAcWYT5jMMQxDEP+Q2uuKfj NhE4D99CiZwdYgi4JP4+86cTDArj9l17tWR9bmVXgyviFU4o3Go= =R12Y -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmk5+AUACgkQ7ZfpDmKq fjTtEg//VloILc1FvXSuFccnpY8G7rmCkL48q5628VbogfqLc3MSQ8FqlfBw3OkI LqiDAF22/nFcMhtQ9j61cFJ5GrAUF28MIKDl1ol5YEswQgiLxDxFbK2c5uWdYJed 4I5bqU8rs6RTA/5ZZ/MMDe7JIGEYClZhHzT9Hs9vLrg2aOW7vSzXjjuAy7FqUwpX k1m6KQtL6UPl4tkbDY9wLSifDtg6GqfZT9bYtPxxLKc89Mm0tFJP7aXuooELb0/k 1YsCFZDU7OK8ttgAlPbtAebfrFJbk1jKuBQqoqyH59QtA4OegHFjRVPFcHYevJsl FMhA10XEXS1C3T2KC9De9Xypt1aJIVIhtEHz7GjlubZRfgLGb+xAvTsJj2h20TIm mTAaJ9tBdr7TiVRlLdUgWdsLRwrVSOLbFCjL5Fa2+XpTNoowPmDp7YHmFsk+itDH 40fRFvBc842huCIsFbQ1EInjVpuUQqaMb1CmZlNMhJz6DoXEicOoo9iwqjRxZyVt 7NB4AQaqBwAKgvTw7iV4Iw0naWaKhwN9pP2AbnC5cMd3SRMneJ6Sxt4MtA9dqpFB mKIMF9Tlb+twuyOZXezaD/RqJs19gusdFmVlpJbNzez//pYMJ/9LcjB+xz61c5Zf mIPWE0mkzSRvhqca4L3inlC73aTRDp2OEt9+n+AJPnk27BRe5Xs= =1kyi -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmk5+AYACgkQ7ZfpDmKq fjRXzA/9GHRwVUZRXXmlwgpPZDVU5BtB2xrcJVQk3pFLs0J6cz+nUVRtsm3Gz400 qaksn6T+azBX5Lv6pSPYmDtj+cSbCA7vcaLxHh414gKu6SKkNTm566xGM3RIKome odhacZtLvPYpfONIGt0YRgwl6oO+Q1dXuu4aoi2H4jdYrHEjpTFY1Pg1TfRrpM/p JxarI/VUOvuXZHAsJRBJshEc5GcOnaUAzYKr/yAelbdowjW2DLetRhWU0YZ9zgZk w6xaVNvcU0i9fX2Ri0MMiTpo92xzRdZd1WZ8wfU3hqUMfolVSMJuk8Qs/NyYm8v9 DMtiQb0Ewi10Y0YyGUnQi3r6wpKQ2K1D2JVZj5eGLsbTfBpi+3bilJHtxBc05NaK HQyZhhgXSTwLkR4LUcsyTtWdiS9uUB2D18EtfxODWoeJsIcoU2fRPX3zVIn0EjTq YLSrGvbk69xAiyhDQlcYFEUoL6GQb0WbDOz1b1IwRJ6de7YcNkkCAlWTt4qIat65 6OfZURSGURRWd9BBNqF2m1OgaGfv4fn/HJL4TYYaEXATpTUxVoPujxl73In5Mu3O A8zVP2QouGD25RYmoQLdAYMyap9XJIS1HWRNBPAyRC8z5YZE1ptm+L0KzBD9+vwe rTejW79L/QMsu9Orz6Mnptraz6C83q7C1hi7STqwNPd4rE8grV8= =MFmx -----END PGP SIGNATURE-----

1 1