[PATCHv2] timezone:upgrade 2019b -> 2019c

[PATCHv2] timezone:upgrade 2019b -> 2019c

[Zang Ruochen]

-tzdata : upgrade from 2019b to 2019c.

-tzcode-native : upgrade from 2019b to 2019c.

-tzdata.bb and tzcode-native.bb require timezone.inc.

Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
---
 meta/recipes-extended/timezone/timezone.inc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-extended/timezone/timezone.inc b/meta/recipes-extended/timezone/timezone.inc
index ce16524..f6bab1a 100644
--- a/meta/recipes-extended/timezone/timezone.inc
+++ b/meta/recipes-extended/timezone/timezone.inc
@@ -4,7 +4,7 @@ SECTION = "base"
 LICENSE = "PD & BSD & BSD-3-Clause"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba"
 
-PV = "2019b"
+PV = "2019c"
 
 SRC_URI =" http://www.iana.org/time-zones/repository/releases/tzcode${PV}.tar.gz;name=tzcode \
            http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata \
@@ -12,7 +12,7 @@ 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[tzcode.md5sum] = "91e0978d947496fd6aaf46d351f9c41d"
-SRC_URI[tzcode.sha256sum] = "2e479d409337da41408629ce6c3b4d8410b10ba6d4431d862e22d2b137d7756d"
-SRC_URI[tzdata.md5sum] = "b26b5d7d844cb96c73ed2fb6d588daaf"
-SRC_URI[tzdata.sha256sum] = "05d9092c90dcf9ec4f3ccfdea80c7dcea5e882b3b105c3422da172aaa9a50c64"
+SRC_URI[tzcode.md5sum] = "195a17454c5db05cab96595380650391"
+SRC_URI[tzcode.sha256sum] = "f6ebd3668e02d5ed223d3b7b1947561bf2d2da2f4bd1db61efefd9e06c167ed4"
+SRC_URI[tzdata.md5sum] = "f6987e6dfdb2eb83a1b5076a50b80894"
+SRC_URI[tzdata.sha256sum] = "79c7806dab09072308da0e3d22c37d3b245015a591891ea147d3b133b60ffc7c"
-- 
2.7.4

Re: [PATCHv2] timezone:upgrade 2019b -> 2019c

[akuster808]

On 9/11/19 11:52 PM, Zang Ruochen wrote:
> -tzdata : upgrade from 2019b to 2019c.
>
> -tzcode-native : upgrade from 2019b to 2019c.
>
> -tzdata.bb and tzcode-native.bb require timezone.inc.

Not exactly what I had in mind.  When there is a TZ update they send out
what changed any why.  It looks like this"

Briefly:
    Fiji observes DST from 2019-11-10 to 2020-01-12.
    Norfolk Island starts observing Australian-style DST.

  Changes to future timestamps

    Fiji's next DST transitions will be 2019-11-10 and 2020-01-12
    instead of 2019-11-03 and 2020-01-19.  (Thanks to Raymond Kumar.)
    Adjust future guesses accordingly.

    Norfolk Island will observe Australian-style DST starting in
    spring 2019.  The first transition is on 2019-10-06.  (Thanks to
    Kyle Czech and Michael Deckers.)

  Changes to past timestamps

    Many corrections to time in Turkey from 1940 through 1985.
    (Thanks to Oya Vulaş via Alois Treindl, and to Kıvanç Yazan.)

    The Norfolk Island 1975-03-02 transition was at 02:00 standard
    time, not 02:00 DST.  (Thanks to Michael Deckers.)

    South Korea observed DST from 1948 through 1951.  Although this
    info was supposed to appear in release 2014j, a typo inadvertently
    suppressed the change.  (Thanks to Alois Treindl.)

    Detroit observed DST in 1967 and 1968 following the US DST rules,
    except that its 1967 DST began on June 14 at 00:01.  (Thanks to
    Alois Treindl for pointing out that the old data entries were
    probably wrong.)

    Fix several errors in pre-1970 transitions in Perry County, IN.
    (Thanks to Alois Triendl for pointing out the 1967/9 errors.)

    Edmonton did not observe DST in 1967 or 1969.  In 1946 Vancouver
    ended DST on 09-29 not 10-13, and Vienna ended DST on 10-07 not
    10-06.  In 1945 Königsberg (now Kaliningrad) switched from +01/+02
    to +02/+03 on 04-10 not 01-01, and its +02/+03 is abbreviated
    EET/EEST, not CET/CEST.  (Thanks to Alois Triendl.)  In 1946
    Königsberg switched to +03 on 04-07 not 01-01.

    In 1946 Louisville switched from CST to CDT on 04-28 at 00:01, not
    01-01 at 00:00.  (Thanks to Alois Treindl and Michael Deckers.)
    Also, it switched from CST to CDT on 1950-04-30, not 1947-04-27.

    The 1892-05-01 transition in Brussels was at 00:17:30, not at noon.
    (Thanks to Michael Deckers.)

  Changes to past time zone abbreviations and DST flags

    Hong Kong Winter Time, observed from 1941-10-01 to 1941-12-25,
    is now flagged as DST and is abbreviated HKWT not HKT.

  Changes to code

    leapseconds.awk now relies only on its input data, rather than
    also relying on its comments.  (Inspired by code from Dennis
    Ferguson and Chris Woodbury.)

    The code now defends against CRLFs in leap-seconds.list.
    (Thanks to Brian Inglis and Chris Woodbury.)

  Changes to documentation and commentary

    theory.html discusses leap seconds.  (Thanks to Steve Summit.)

    Nashville's newspapers dueled about the time of day in the 1950s.
    (Thanks to John Seigenthaler.)

    Liechtenstein observed Swiss DST in 1941/2.
    (Thanks to Alois Treindl.)



>
> Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
> ---
>  meta/recipes-extended/timezone/timezone.inc | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/meta/recipes-extended/timezone/timezone.inc b/meta/recipes-extended/timezone/timezone.inc
> index ce16524..f6bab1a 100644
> --- a/meta/recipes-extended/timezone/timezone.inc
> +++ b/meta/recipes-extended/timezone/timezone.inc
> @@ -4,7 +4,7 @@ SECTION = "base"
>  LICENSE = "PD & BSD & BSD-3-Clause"
>  LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba"
>  
> -PV = "2019b"
> +PV = "2019c"
>  
>  SRC_URI =" http://www.iana.org/time-zones/repository/releases/tzcode${PV}.tar.gz;name=tzcode \
>             http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata \
> @@ -12,7 +12,7 @@ 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[tzcode.md5sum] = "91e0978d947496fd6aaf46d351f9c41d"
> -SRC_URI[tzcode.sha256sum] = "2e479d409337da41408629ce6c3b4d8410b10ba6d4431d862e22d2b137d7756d"
> -SRC_URI[tzdata.md5sum] = "b26b5d7d844cb96c73ed2fb6d588daaf"
> -SRC_URI[tzdata.sha256sum] = "05d9092c90dcf9ec4f3ccfdea80c7dcea5e882b3b105c3422da172aaa9a50c64"
> +SRC_URI[tzcode.md5sum] = "195a17454c5db05cab96595380650391"
> +SRC_URI[tzcode.sha256sum] = "f6ebd3668e02d5ed223d3b7b1947561bf2d2da2f4bd1db61efefd9e06c167ed4"
> +SRC_URI[tzdata.md5sum] = "f6987e6dfdb2eb83a1b5076a50b80894"
> +SRC_URI[tzdata.sha256sum] = "79c7806dab09072308da0e3d22c37d3b245015a591891ea147d3b133b60ffc7c"

Re: [PATCHv2] timezone:upgrade 2019b -> 2019c

[Adrian Bunk]

On Thu, Sep 12, 2019 at 07:10:08AM -0700, akuster808 wrote:
> 
> 
> On 9/11/19 11:52 PM, Zang Ruochen wrote:
> > -tzdata : upgrade from 2019b to 2019c.
> >
> > -tzcode-native : upgrade from 2019b to 2019c.
> >
> > -tzdata.bb and tzcode-native.bb require timezone.inc.
> 
> Not exactly what I had in mind.  When there is a TZ update they send out
> what changed any why.  It looks like this"
>...

IMHO that would be far too long for a commit message,
and changelogs of this size would make the git history
unreadable if everyone would start pasting huge upstream
changelogs in their commits.

cu
Adrian

BTW: How is the legal handling of the metadata, when such lengthy
     3rd party texts copyrighted by various people under various 
     licences are distributed as part of the git metadata?

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [PATCHv2] timezone:upgrade 2019b -> 2019c

[akuster808]

On 9/12/19 7:28 AM, Adrian Bunk wrote:
> On Thu, Sep 12, 2019 at 07:10:08AM -0700, akuster808 wrote:
>>
>> On 9/11/19 11:52 PM, Zang Ruochen wrote:
>>> -tzdata : upgrade from 2019b to 2019c.
>>>
>>> -tzcode-native : upgrade from 2019b to 2019c.
>>>
>>> -tzdata.bb and tzcode-native.bb require timezone.inc.
>> Not exactly what I had in mind.  When there is a TZ update they send out
>> what changed any why.  It looks like this"
>> ...
> IMHO that would be far too long for a commit message,

I have been including that information for years. IMHO that make it the
standard for that package.

Up until now , no one has had an issue with it.

> and changelogs of this size would make the git history
> unreadable if everyone would start pasting huge upstream
> changelogs in their commits.

I have no fear of that ever happening as it has been totally acceptable
not to have a commit message included  and there is no enforcement of
that process.
We had this discussion in the past and we go round and round and nothing
ever changes. So I am not worried.

I applaud those who  take the time and  effort of providing additional
information in the commit messages.


> cu
> Adrian
>
> BTW: How is the legal handling of the metadata, when such lengthy
>      3rd party texts copyrighted by various people under various 
>      licences are distributed as part of the git metadata?
Interesting question. Since I am not a lawyer, maybe you can help guide
the community so we do the right thing. Now I am worried about the
stable branches,
do backports have  this same issue, are those 3-party texts?

- armin
>

Re: [PATCHv2] timezone:upgrade 2019b -> 2019c

[Adrian Bunk]

On Thu, Sep 12, 2019 at 10:30:30AM -0700, akuster808 wrote:
> On 9/12/19 7:28 AM, Adrian Bunk wrote:
>...
> I applaud those who  take the time and  effort of providing additional
> information in the commit messages.
>...

Blind pasting of the complete upstream changelog is not exactly an 
effort that would warrant applause.

A short summary of the relevant parts might be useful, but when you are 
asking to include details like
  The 1892-05-01 transition in Brussels was at 00:17:30, not at noon.
that's only adding noise in "git log".

> > BTW: How is the legal handling of the metadata, when such lengthy
> >      3rd party texts copyrighted by various people under various 
> >      licences are distributed as part of the git metadata?
> Interesting question. Since I am not a lawyer,

I am also not a lawyer.

> maybe you can help guide
> the community so we do the right thing. Now I am worried about the
> stable branches,
> do backports have  this same issue, are those 3-party texts?

Backporting does not make a difference here,
it is about under what licence the contents of the commit message is.

Pasting texts from elsewhere makes the licencing of the git metadata a 
complete mess, like you cannot claim it is MIT if it contains text from
GPLv3 software.

A person using Signed-off-by also certifies that the whole contribution 
is under an open source license, which would make pasting changelogs from 
components that are not under an open source license clearly off-limits.

Not sure how much actual lawyers care about such issues,
but once something is in the git history it is too late.

> - armin

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed