Date: Mon, 27 Apr 2015 00:34:36 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 168862] [tzcode] [patch] tzname set incorrectly Message-ID: <bug-168862-8-agH6sBhGJR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-168862-8@https.bugs.freebsd.org/bugzilla/> References: <bug-168862-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168862 Jonathan M Davis <freebsd.bugs@jmdavisprog.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd.bugs@jmdavisprog.co | |m --- Comment #3 from Jonathan M Davis <freebsd.bugs@jmdavisprog.com> --- This bug still exists in FreeBSD 10.1, and it's been almost three years since this was reported, which seems like a long time for this to be sitting around - particularly considering that a patch has been attached to it. And it affects a _lot_ more time zones than just "America/Los_Angeles". Comparing what tzname says to what's in the TZ files themselves (using D's std.datetime time zone code to read the TZ files), I'm seeing 133 time zones that have their tzname[0] wrong, and 249 that have their tzname[1] wrong. Curiously, the date command seems to print out the correct time zone names (at least in "America/Los_Angeles"), so I guess that date doesn't use tzname, and that may be why more folks haven't complained, but this needs to get fixed. What would it take for the patch to be reviewed and merged in? I'm not set up to develop on FreeBSD, so I don't know how to test the changes (and I'd really prefer to not have to figure out how to set that up), but from what I can tell from looking at the code, it looks like the change in the patch is correct. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-168862-8-agH6sBhGJR>