All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>,
	openembedded-core@lists.openembedded.org
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] [openembedded-core] 10/35: tzcode: update to 2018f
Date: Wed, 21 Nov 2018 13:59:19 -0700	[thread overview]
Message-ID: <f9ff0b37-e05c-563f-0082-bb01ff670b8e@gmail.com> (raw)
In-Reply-To: <20181120195642.GA1825@jama>


[-- Attachment #1.1: Type: text/plain, Size: 6551 bytes --]



On 11/20/18 12:56 PM, Martin Jansa wrote:
> On Fri, Nov 16, 2018 at 04:33:46PM +0000, git@git.openembedded.org wrote:
>> This is an automated email from the git hooks/post-receive script.
>>
>> rpurdie pushed a commit to branch sumo
>> in repository openembedded-core.
>>
>> commit 9702041a732ca062a9899543d05e585c930407f3
>> Author: Armin Kuster <akuster808@gmail.com>
>> AuthorDate: Mon Oct 22 15:05:11 2018 +0100
>>
>>     tzcode: update to 2018f
> This breaks postgresql build in sumo:
>
> | postgresql/9.4.17-r0/recipe-sysroot-native/usr/bin/zic -d 'postgresql/9.4.17-r0/image/usr/share/postgresql/timezone' -p 'US/Eastern' postgresql/9.4.17-r0/build/../postgresql-9.4.17/src/timezone/data/tzdata.zi
> | "postgresql/9.4.17-r0/build/../postgresql-9.4.17/src/timezone/data/tzdata.zi", line 1595: Invalid rule name "+"
> | "postgresql/9.4.17-r0/build/../postgresql-9.4.17/src/timezone/data/tzdata.zi", line 1596: Invalid rule name "+"
> | "postgresql/9.4.17-r0/build/../postgresql-9.4.17/src/timezone/data/tzdata.zi", line 1597: Invalid rule name "+"
> | "postgresql/9.4.17-r0/build/../postgresql-9.4.17/src/timezone/data/tzdata.zi", line 1598: Invalid rule name "+"
> | "postgresql/9.4.17-r0/build/../postgresql-9.4.17/src/timezone/data/tzdata.zi", line 1599: Invalid rule name "+"
> | Makefile:52: recipe for target 'install' failed
> | make[2]: *** [install] Error 1
> | make[2]: Leaving directory 'postgresql/9.4.17-r0/build/src/timezone'
> | Makefile:35: recipe for target 'install-timezone-recurse' failed
> | make[1]: *** [install-timezone-recurse] Error 2
>
>
> Are you going to backport:
>
> commit 805e74d00cff3a7566335150f7e3b41972265cc1
> Author: Armin Kuster <akuster808@gmail.com>
> Date:   Mon Oct 22 16:47:55 2018 +0100
>
>     postgresql: Fix build issue with timezone 2018f update
>     
>     Sync our copy of the timezone library with IANA release tzcode2018f.
>
> to meta-oe/sumo?
I should.

- armin
>
> Thanks
>
>>     
>>      Changes to code
>>     
>>         zic now always generates TZif files where time type 0 is used for
>>         timestamps before the first transition.  This simplifies the
>>         reading of TZif files and should not affect behavior of existing
>>         TZif readers because the same set of time types is used; only
>>         their internal indexes may have changed.  This affects only the
>>         legacy zones EST5EDT, CST6CDT, MST7MDT, PST8PDT, CET, MET, and
>>         EET, which previously used nonzero types for these timestamps.
>>     
>>         Because of the type 0 change, zic no longer outputs a dummy
>>         transition at time -2**59 (before the Big Bang), as clients should
>>         no longer need this to handle historical timestamps correctly.
>>         This reverts a change introduced in 2013d and shrinks most TZif
>>         files by a few bytes.
>>     
>>         zic now supports negative time-of-day in Rule and Leap lines, e.g.,
>>         "Rule X min max - Apr lastSun -6:00 1:00 -" means the transition
>>         occurs at 18:00 on the Saturday before the last Sunday in April.
>>         This behavior was documented in 2018a but the code did not
>>         entirely match the documentation.
>>     
>>         localtime.c no longer requires at least one time type in TZif
>>         files that lack transitions or have a POSIX-style TZ string.  This
>>         future-proofs the code against possible future extensions to the
>>         format that would allow TZif files with POSIX-style TZ strings and
>>         without transitions or time types.
>>     
>>         A read-access subscript error in localtime.c has been fixed.
>>         It could occur only in TZif files with timecnt == 0, something that
>>         does not happen in practice now but could happen in future versions.
>>     
>>         localtime.c no longer ignores TZif POSIX-style TZ strings that
>>         specify only standard time.  Instead, these TZ strings now
>>         override the default time type for timestamps after the last
>>         transition (or for all time stamps if there are no transitions),
>>         just as DST strings specifying DST have always done.
>>     
>>         leapseconds.awk now outputs "#updated" and "#expires" comments,
>>         and supports leap seconds at the ends of months other than June
>>         and December.  (Inspired by suggestions from Chris Woodbury.)
>>     (From OE-Core rev: 4670dcdb6e2504469c30ebed828d4702d8c0003c)
>>     
>>     Signed-off-by: Armin Kuster <akuster808@gmail.com>
>>     Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>>     Signed-off-by: Armin Kuster <akuster808@gmail.com>
>> ---
>>  .../tzcode/{tzcode-native_2018e.bb => tzcode-native_2018f.bb}     | 8 ++++----
>>  1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/meta/recipes-extended/tzcode/tzcode-native_2018e.bb b/meta/recipes-extended/tzcode/tzcode-native_2018f.bb
>> similarity index 70%
>> rename from meta/recipes-extended/tzcode/tzcode-native_2018e.bb
>> rename to meta/recipes-extended/tzcode/tzcode-native_2018f.bb
>> index 9a4e465..816e34d 100644
>> --- a/meta/recipes-extended/tzcode/tzcode-native_2018e.bb
>> +++ b/meta/recipes-extended/tzcode/tzcode-native_2018f.bb
>> @@ -11,10 +11,10 @@ SRC_URI =" http://www.iana.org/time-zones/repository/releases/tzcode${PV}.tar.gz
>>  
>>  UPSTREAM_CHECK_URI = "http://www.iana.org/time-zones"
>>  
>> -SRC_URI[tzdata.md5sum] = "97d654f4d7253173b3eeb76a836dd65e"
>> -SRC_URI[tzdata.sha256sum] = "6b288e5926841a4cb490909fe822d85c36ae75538ad69baf20da9628b63b692e"
>> -SRC_URI[tzcode.md5sum] = "c4d7df0fff7ba5588b32c5f27e2caf97"
>> -SRC_URI[tzcode.sha256sum] = "ca340cf20e80b699d6e5c49b4ba47361b3aa681f06f38a0c88a8e8308c00ebce"
>> +SRC_URI[tzdata.md5sum] = "e5e84f00f9d18bd6ebc8b1affec91b15"
>> +SRC_URI[tzdata.sha256sum] = "0af6a85fc4ea95832f76524f35696a61abb3992fd3f8db33e5a1f95653e043f2"
>> +SRC_URI[tzcode.md5sum] = "011d394b70e6ee3823fd77010b99737f"
>> +SRC_URI[tzcode.sha256sum] = "4ec74f8a84372570135ea4be16a042442fafe100f5598cb1017bfd30af6aaa70"
>>  
>>  S = "${WORKDIR}"
>>  
>>
>> -- 
>> To stop receiving notification emails like this one, please contact
>> the administrator of this repository.
>> -- 
>> _______________________________________________
>> Openembedded-commits mailing list
>> Openembedded-commits@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-commits



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2018-11-21 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <154238601667.15427.9965417024860647033@git.openembedded.org>
     [not found] ` <20181116163337.4A962235D9B@git.openembedded.org>
2018-11-20 19:56   ` [oe-commits] [openembedded-core] 10/35: tzcode: update to 2018f Martin Jansa
2018-11-21 20:59     ` akuster808 [this message]
2018-11-21 21:22     ` akuster808

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f9ff0b37-e05c-563f-0082-bb01ff670b8e@gmail.com \
    --to=akuster808@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-commits@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.