Re: [swift-corelibs-dev] TimeZone database

We have a list of required packages in our README.md - we could add tzdata to that. - Tony > On Jul 6, 2017, at 1:48 PM, Youming Lin via swift-corelibs-dev > wrote: > > Thanks for pointing me to the package. Turns out it was intentional: >

Re: [swift-corelibs-dev] TimeZone database

Thanks for pointing me to the package. Turns out it was intentional: https://github.com/docker-library/official-images/issues/2863 A caveat to Swift developers using official Docker Ubuntu images in the future. Youming Lin IBM Cloud, Swift@IBM, Kitura developer Austin, TX GitHub: @youming-lin

Re: [swift-corelibs-dev] TimeZone database

Looks like timezone files are in the ‘tzdata’ package. Maybe it got uninstalled or was never installed as part of the base. An ‘apt-get install tzdata’ might fix it. Simon > On 6 Jul 2017, at 20:20, Youming Lin via swift-corelibs-dev > wrote: > > That's odd.

Re: [swift-corelibs-dev] TimeZone database

Hm, good question - we do have our ‘bootstrap’ directory which includes some time zone headers, but those are the ones from unicode and not tzfile.h. - Tony > On Jul 6, 2017, at 11:42 AM, Alex Blewitt wrote: > > It looks like it's /usr/share/zoneinfo on all Ubuntu versions:

Re: [swift-corelibs-dev] TimeZone database

That's odd. Maybe my ubuntu:16.04 image is outdated or something, but here are my outputs: ylin@youming-mbpr:~/Swift/Kitura-Markdown$ docker run -it --rm ubuntu:16.04 find /usr -name zone.tab ylin@youming-mbpr:~/Swift/Kitura-Markdown$ docker run -it --rm ubuntu:14.04 find /usr -name zone.tab

Re: [swift-corelibs-dev] TimeZone database

It looks like it's /usr/share/zoneinfo on all Ubuntu versions: alblue.local[~]$ docker run -it --rm ubuntu:14.04 find /usr -name zone.tab /usr/share/zoneinfo/zone.tab alblue.local[~]$ docker run -it --rm ubuntu:16.04 find /usr -name zone.tab /usr/share/zoneinfo/zone.tab alblue.local[~]$ docker

Re: [swift-corelibs-dev] TimeZone database

Is the path to zoneinfo different on the Ubuntu docker image? - Tony > On Jul 6, 2017, at 9:36 AM, Youming Lin wrote: > > We were seeing this on Travis too. Specifically, on a Travis matrix build > using Swift 3.1.1 on a Ubuntu 16.04 docker image running inside a Travis >

Re: [swift-corelibs-dev] TimeZone database

We were seeing this on Travis too. Specifically, on a Travis matrix build using Swift 3.1.1 on a Ubuntu 16.04 docker image running inside a Travis 14.04 VM. The issue was specific to the Ubuntu 16.04 docker image; when I tested in Ubuntu 16.04 OS as a guest VM, the issue went away. Thanks,

Re: [swift-corelibs-dev] TimeZone database

I've only poked this briefly, but it looks like CFCopySystemVersionString() might give the info we'd need? On 6 July 2017 at 16:28, Tony Parker wrote: > Yes, we’re discussing this one internally too and trying to figure out what > the right answer is. Maybe the best

Re: [swift-corelibs-dev] TimeZone database

Yes, we’re discussing this one internally too and trying to figure out what the right answer is. Maybe the best solution for now is to find a good mechanism to check the underlying version of the OS and split it out into a function as you suggest. - Tony > On Jul 6, 2017, at 7:37 AM, Ian

Re: [swift-corelibs-dev] TimeZone database

Ian I also saw this error, I think its because the TZDIR is different in the headers shipped with Xcode 9. Maybe the location of the timezone directory was moved between Sierra and High Sierra. What version of macOS are you testing on? If it has indeed moved between 10.12 and 10.13 it may

Re: [swift-corelibs-dev] TimeZone database

Good shout Simon, you are right. I'm on Sierra. Compare and contrast: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/tzfile.h #define TZDIR "/usr/share/zoneinfo"

[swift-corelibs-dev] TimeZone database

Hi, I'm seeing quite a lot of tests failing when running the TestFoundation target in Xcode. The failures are timezone related. Most simply, the code let timeZone = TimeZone(abbreviation: "GMT") is returning nil. Walking through the CF code which sets things up, it seems to be trying to read