X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=sixwqjVCUBRuWyiZQJ/3Q7grj8QNCuqQKPfFMTnKkdBzZiwUCeSE4 QqEdi2FtPQp0/yh9Vd/cMyQM831PtptJOZn+xVrYf504mvMwZOO2vSh/dnXN8pX2 GnhpMVWG/KLJ1iIIJ4zC58NS7HJTA1g9/Z5D0m1QPDr2lKvKgie2v4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=WkgYAXF0EokYKUQhi5C1zlJP0mM=; b=PiUW+GcydhlneUKQ7ibpTD86JKuB dAYNckDLdD1L5sBjMUDBooH5QvQOpRDIiwLqBQWc11h4uvU19PwDkDDem+QedTEO r8G3cNjVtQz/UETLFeFOKMbkR2fWNNaLFezithdfNuNjYgpXvHwR68MOQaO8uOJM drWJkhvAevYuCbA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: plane.gmane.org To: cygwin AT cygwin DOT com From: Brian Inglis Subject: Re: Different (and wrong) timezones reported by both strftime(3) and date(1) Date: Sun, 2 Nov 2014 18:05:48 +0000 (UTC) Lines: 16 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Egor Tensin gmail.com> writes: > I've run into an issue of both strftime(3) and date(1) reporting > different (and wrong) timezones. I'm in the MSK timezone (switched > from +0400 to +0300 on 10/26/14). Wow - tzcode release is ancient - 2013c from April 2013 - went up to 2013i last year and current is 2014i. Okay if you live in NA or EU, but not the rest of the world, where DST changes on political whims, often on short notice. As this package is part of base, any chance of getting it updated with similar frequency to ca-certs, or splitting tzdata into a separate package which can be easily and frequently updated? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple