Ticket #1008 (closed defect: fixed)
[EXPLETIVE] Fucking Debian fucking ruined their fucking PHP package once again, and now we need to waste fucking time to fucking fix it
| Reported by: | david | Owned by: | david |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11.6 |
| Component: | translation | Version: | 0.11.5 |
| Severity: | normal | Keywords: | |
| Cc: | Patch attached: | no |
Description (last modified by david) (diff)
Debian ticks me off.
So, a user (Joe Orton) suggested to internals@ that the system timezone be consulted if the timezone identifier was System/Localtime, which it would be by default. internals@ declined ( http://thread.gmane.org/gmane.comp.php.devel/47609), and he produced a patch for Debian that was eventually included into their distribution.
New patch (use_embedded_timezonedb.patch) allows us to default to using the system provided timezone database instead of the one bundled with PHP. Many thanks to Joe Orten from Red Hat for the patch! (closes: #447174, #471104).
Now, if no timezone is configured anywhere, then such a Debian system (it's in lenny and sid, not in etch), will use "System/Localtime" as the default timezone, and PHP is patched to resolve meaningful data for this identifier. So DateTime, DateTimeZone etc work fine, because they all use this change that makes them look at /etc/localtime, but... we cannot get the actual timezone name, only the abbreviation, which is useless as it's not authoritative in many cases (example: actual timezone "Asia/Novosibirsk" returns "System/Localtime", but "NOVT" as the abbreviation). date_default_timezone_get() returns "System/Localtime", not the resolved value. Same with DateTimeZone or anything in DateTime.
Now, of course we could simply determine the offset of the resulting timezone and create an "anonymous" timezone, or the corresponding "GMT+x" one, but that doesn't give us correct daylight saving time information for the timezone in question, so we cannot do any kind of calculations properly.
So basically, we cannot handle that System/Localtime stuff at all, because the stupid patch does it wrong, and because it's useless, and because once again, some guy from the $random_linux_distribution camp thought he knew better.
Sad.
I really can't be bothered to implement yet another workaround. Debian and Ubuntu are causing us nothing but trouble.
Oh, also, Redhat/Fedora might do the same crap (looks like they didn't include it yet): https://bugzilla.redhat.com/show_bug.cgi?id=469532
God fucking damnit. What kind of a bullcrap idea is this.
Oh and Debian guys keep pointing at PHP in #debian on freenode. Great. They're also saying that it's only likely to be fixed if the application(s) affected by it are sufficiently "popular", whatever that means.
Attachments
-
debian_chatlog
(8.5 KB) - added by david
14 months ago.
- Logs of the discussion in #debian on irc.freenode.net today; I removed messages unrelated to the discussion and join/part/quit events
