https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297243
--- Comment #3 from Mason Loring Bliss <[email protected]> --- > What exactly do you mean by mailx? There is nothing even remotely like what > you describe in our implementation. I mean Heirloom mailx, which is indeed distinct from bsd-mailx. I encountered a bug through my work, and then created a reproducer based on the code from Heirloom mailx. I noticed that gmtime(3) appeared to be returning different data based on the zonefile version, despite the zonefile not effectively changing until November 1st, which puzzled me. So, having verified that the issue existed on every version of RHEL with the new timezone, but with nothing else changed, I also checked Fedora and FreeBSD, and noted both showing the same symptoms with the newer zone data. Given that if Heirloom mailx does this, it's conceivable that other stuff does too, at least as modelled on this. But the odd bit remains - why does this code, even if problematic, show one result under 2026a and another under 2026b when the change isn't supposed to happen until November? That makes me wonder if there's underlying badness. I haven't had the time to dig though enough of the code to understand it, but I hope to do so. FWIW, the glibc list doesn't think it's a bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34480 I need to read the responses there in depth and I've not had a chance yet. -- You are receiving this mail because: You are the assignee for the bug.
