Pyongyang Time transition plan announced
Rodong Sinmun 2018-04-30 announced Pyongyang Time transition plan. https://www.nknews.org/kcna/wp-content/uploads/sites/5/2018/04/rodong-2018-0... I won't translate, but even if you don't know Korean it should be easy to confirm that the transition date is 2018-05-05. 2018 is Juche 107. Citation should be Decree No. 2232 of April 30, 2018, of the Presidum of the Supreme People's Assembly, as published in Rodong Sinmun. -- Seo Sanghyeon
Seo Sanghyeon wrote:
Rodong Sinmun 2018-04-30 announced Pyongyang Time transition plan. https://www.nknews.org/kcna/wp-content/uploads/sites/5/2018/04/rodong-2018-0...
I won't translate, but even if you don't know Korean it should be easy to confirm that the transition date is 2018-05-05. 2018 is Juche 107 Is the transition at 00:00 local time (midnight at the start of 2018-05-05), or at some other time of the day?
Also, that's a 6-page newspaper with a lot of fine print. Could you please let us know the page and column number? Thanks.
It appears to be the front page story at the top in the right-most column: The resolution of the PDF isn't good enough for a solid OCR read, but I'm working on getting something with the help of Google Translate's camera. At first glance, no mention of a specific transition time jumps out at me, but the 5 May 2018 transition date is pretty easy to spot as the second item in the decree, shown below the article. -- Tim Parenti On 29 April 2018 at 22:03, Paul Eggert <eggert@cs.ucla.edu> wrote:
Seo Sanghyeon wrote:
Rodong Sinmun 2018-04-30 announced Pyongyang Time transition plan. https://www.nknews.org/kcna/wp-content/uploads/sites/5/2018/ 04/rodong-2018-04-30.pdf
I won't translate, but even if you don't know Korean it should be easy to confirm that the transition date is 2018-05-05. 2018 is Juche 107
Is the transition at 00:00 local time (midnight at the start of 2018-05-05), or at some other time of the day?
Also, that's a 6-page newspaper with a lot of fine print. Could you please let us know the page and column number?
Thanks.
Tim Parenti wrote:
It appears to be the front page story at the top in the right-most column:
Thanks. In the absence of further info, let's assume the transition will be at 00:00 local time on May 5, and that the clocks will jump from 00:00 to 00:30. Proposed patch attached. If we find out later that this assumption is wrong, we'll need to update tzdb accordingly. We'll need a new tzdb release shortly, of course.
Sigh.... I guess my blog post (https://codeofmatt.com/2016/04/23/on-the-timing-of-time-zone-changes/) wasn't fruitful in this regard. Perhaps because there are fewer computer users in North Korea? -Matt ________________________________ From: tz <tz-bounces@iana.org> on behalf of Paul Eggert <eggert@cs.ucla.edu> Sent: Sunday, April 29, 2018 7:34 PM To: Tim Parenti Cc: Time Zone Mailing List; Kang Seonghoon Subject: Re: [tz] Pyongyang Time transition plan announced Tim Parenti wrote:
It appears to be the front page story at the top in the right-most column:
Thanks. In the absence of further info, let's assume the transition will be at 00:00 local time on May 5, and that the clocks will jump from 00:00 to 00:30. Proposed patch attached. If we find out later that this assumption is wrong, we'll need to update tzdb accordingly. We'll need a new tzdb release shortly, of course.
On 04/30/2018 12:51 PM, Matt Johnson wrote:
I guess my blog post (https://codeofmatt.com/2016/04/23/on-the-timing-of-time-zone-changes/) wasn't fruitful in this regard. Perhaps because there are fewer computer users in North Korea?
Yes, along with a government that is more powerful and/or capricious than elsewhere. It's not just North Korea: it's also Palestine (one week's notice in March), São Tomé and Príncipe (one week's notice late last year), Northern Cyprus (twelve days' notice last October), Sudan (two weeks' notice last October), and best of all Tonga where there was no notice even after-the-fact for last November's change, due to the government being dissolved, and as far as I know the airline industry is now unofficially in charge of Tonga's clocks.
They might have few computers, but report claims there are millions of smartphone in the country, although they're connected to an intranet instead of internet. Not sure how those phones are going to receive updates. And as the changes is clearly a political one, we should probably be grateful that they aren't going to implement the change immediately nor on the next day after the announcement 在 2018年5月1日週二 03:51，Matt Johnson <mj1856@hotmail.com> 寫道：
Sigh.... I guess my blog post ( https://codeofmatt.com/2016/04/23/on-the-timing-of-time-zone-changes/) wasn't fruitful in this regard. Perhaps because there are fewer computer users in North Korea?
-Matt
------------------------------ *From:* tz <tz-bounces@iana.org> on behalf of Paul Eggert < eggert@cs.ucla.edu> *Sent:* Sunday, April 29, 2018 7:34 PM *To:* Tim Parenti *Cc:* Time Zone Mailing List; Kang Seonghoon *Subject:* Re: [tz] Pyongyang Time transition plan announced
Tim Parenti wrote:
It appears to be the front page story at the top in the right-most column:
Thanks. In the absence of further info, let's assume the transition will be at 00:00 local time on May 5, and that the clocks will jump from 00:00 to 00:30. Proposed patch attached. If we find out later that this assumption is wrong, we'll need to update tzdb accordingly.
We'll need a new tzdb release shortly, of course.
On 05/01/2018 08:51 AM, Phake Nick wrote:
Not sure how those phones are going to receive updates.
If North Korea's intranet is well-run, all the cell phones that have been connected to the network since yesterday should have been updated by now. That's how things would be done in the US, anyway. (Perhaps I should have waited until next April to send this email....)
I picked up the 2018e tag from the GitHub repository, but AFAICT it’s not possible to build the rearguard tarballs on a system that doesn’t have lzip. The traditional_tarballs target doesn’t build the rearguard tarball. It probably should. Debbie
On May 1, 2018, at 9:47 AM, Paul Eggert <eggert@CS.UCLA.EDU> wrote:
On 05/01/2018 08:51 AM, Phake Nick wrote:
Not sure how those phones are going to receive updates.
If North Korea's intranet is well-run, all the cell phones that have been connected to the network since yesterday should have been updated by now. That's how things would be done in the US, anyway.
(Perhaps I should have waited until next April to send this email....)
Can you please remove me from your mailing list. Thank you. Ricardo Simmons On May 2, 2018, at 8:20 PM, Deborah Goldsmith <goldsmit@apple.com> wrote: I picked up the 2018e tag from the GitHub repository, but AFAICT it’s not possible to build the rearguard tarballs on a system that doesn’t have lzip. The traditional_tarballs target doesn’t build the rearguard tarball. It probably should. Debbie
On May 1, 2018, at 9:47 AM, Paul Eggert <eggert@CS.UCLA.EDU> wrote:
On 05/01/2018 08:51 AM, Phake Nick wrote:
Not sure how those phones are going to receive updates.
If North Korea's intranet is well-run, all the cell phones that have been connected to the network since yesterday should have been updated by now. That's how things would be done in the US, anyway.
(Perhaps I should have waited until next April to send this email....)
This appears to work: diff --git a/Makefile b/Makefile index 21fa488..8e00599 100644 --- a/Makefile +++ b/Makefile @@ -921,7 +921,7 @@ tarballs_version: traditional_tarballs_version \ tzdata$(VERSION)-rearguard.tar.gz \ tzdb-$(VERSION).tar.lz traditional_tarballs_version: \ - tzcode$(VERSION).tar.gz tzdata$(VERSION).tar.gz + tzcode$(VERSION).tar.gz tzdata$(VERSION).tar.gz tzdata$(VERSION)-rearguard.tar.gz signatures_version: $(ALL_ASC) traditional_signatures_version: $(TRADITIONAL_ASC) Debbie
On May 2, 2018, at 5:20 PM, Deborah Goldsmith <goldsmit@apple.com> wrote:
I picked up the 2018e tag from the GitHub repository, but AFAICT it’s not possible to build the rearguard tarballs on a system that doesn’t have lzip. The traditional_tarballs target doesn’t build the rearguard tarball. It probably should.
Debbie
On May 1, 2018, at 9:47 AM, Paul Eggert <eggert@CS.UCLA.EDU> wrote:
On 05/01/2018 08:51 AM, Phake Nick wrote:
Not sure how those phones are going to receive updates.
If North Korea's intranet is well-run, all the cell phones that have been connected to the network since yesterday should have been updated by now. That's how things would be done in the US, anyway.
(Perhaps I should have waited until next April to send this email....)
On 05/02/2018 05:20 PM, Deborah Goldsmith wrote:
I picked up the 2018e tag from the GitHub repository, but AFAICT it’s not possible to build the rearguard tarballs on a system that doesn’t have lzip.
It is possible. The following shell script worked for me: make version VERSION=`cat version` make VERSION=$VERSION tzdata$VERSION-rearguard.tar.gz This is an awkward hack, though, so thanks for reporting the issue. There should be a better way.
The traditional_tarballs target doesn’t build the rearguard tarball. It probably should.
I'd prefer that target to build just the two traditional tarballs that we've been building for ages, and to have a new target for the new stuff. How about the attached proposed patch? With it, one can build the tarball in question with 'make rearguard_tarballs', which is more convenient than the above hack.
Your proposal sounds good to me. Thanks! Debbie
On May 2, 2018, at 6:38 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
On 05/02/2018 05:20 PM, Deborah Goldsmith wrote:
I picked up the 2018e tag from the GitHub repository, but AFAICT it’s not possible to build the rearguard tarballs on a system that doesn’t have lzip.
It is possible. The following shell script worked for me:
make version VERSION=`cat version` make VERSION=$VERSION tzdata$VERSION-rearguard.tar.gz
This is an awkward hack, though, so thanks for reporting the issue. There should be a better way.
The traditional_tarballs target doesn’t build the rearguard tarball. It probably should.
I'd prefer that target to build just the two traditional tarballs that we've been building for ages, and to have a new target for the new stuff. How about the attached proposed patch? With it, one can build the tarball in question with 'make rearguard_tarballs', which is more convenient than the above hack. <0001-New-make-rule-rearguard_tarballs.txt>
participants (7)
-
Deborah Goldsmith -
Matt Johnson -
Paul Eggert -
Phake Nick -
Ricardo Simmons -
Seo Sanghyeon -
Tim Parenti