Summary: | [TRACKER] UTC vs. TAI problems | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sascha Silbe <sascha-gentoo-bugzilla> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | as.gentoo, bangert, n-roeser, ulm |
Priority: | High | Keywords: | Tracker |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 78351, 111555, 124188, 125755, 137708, 183716, 184484 | ||
Bug Blocks: |
Description
Sascha Silbe
2006-06-23 03:49:21 UTC
Bug #109472 is/was somewhat related. It's about updating the leap seconds table contained in glibc. Wikipedia has a good description of TAI [1], also noting that UTC in fact is derived from TAI, so you might see why it's important to get the leap second correction right (instead of just ignoring it). [1] http://en.wikipedia.org/wiki/Atomic_time Fix dependancy sense (was inverted). err, what has curl got to do with this bug? the cookie timestamp was expired, not off by a leap second. See bug #111555 comment #23 for an explanation of why it's listed on this bug. so what exactly is the solution to all this? (In reply to comment #6) > so what exactly is the solution to all this? +1 The fact we dont have a solution shall not prevent talking about the issue. That's why BTS exist: list problemes that do not have solution yet. Please add "TRACKER" to "Keywords" field. Closing due to depending bugs being fixed. |