Обсуждение: The rh7.3 time errors
Was there a workaround for the errors in time handling for rh7.3 dist? I get there regression failures: abstime ... FAILED tinterval ... FAILED test horology ... FAILED I remember the discussion about old dates, but not if there was any fix for it... Magnus -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Programmer/Networker [|] Magnus Naeslund -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Magnus Naeslund(f) wrote: > Was there a workaround for the errors in time handling for rh7.3 dist? > > I get there regression failures: > abstime ... FAILED > tinterval ... FAILED > test horology ... FAILED > > I remember the discussion about old dates, but not if there was any fix for it... > Tom fixed this just before we went into beta. Are you using a recent snapshot? Joe
Joe Conway <mail@joeconway.com> wrote: > Magnus Naeslund(f) wrote: >> Was there a workaround for the errors in time handling for rh7.3 >> dist? >> >> I get there regression failures: >> abstime ... FAILED >> tinterval ... FAILED >> test horology ... FAILED >> >> I remember the discussion about old dates, but not if there was any >> fix for it... >> > > Tom fixed this just before we went into beta. Are you using a recent > snapshot? > > Joe As usual, i never remember to supply version information. I'm using latest stable, 7.2.2. Is there a quick workaround for this version, or must there be code ? Magnus -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Programmer/Networker [|] Magnus Naeslund -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Magnus
Magnus Naeslund(f) wrote: > Joe Conway <mail@joeconway.com> wrote: > > Magnus Naeslund(f) wrote: > >> Was there a workaround for the errors in time handling for rh7.3 > >> dist? > >> > >> I get there regression failures: > >> abstime ... FAILED > >> tinterval ... FAILED > >> test horology ... FAILED > >> > >> I remember the discussion about old dates, but not if there was any > >> fix for it... > >> > > > > Tom fixed this just before we went into beta. Are you using a recent > > snapshot? > > > > Joe > > As usual, i never remember to supply version information. > I'm using latest stable, 7.2.2. > Is there a quick workaround for this version, or must there be code ? The change was to use localtime() rather than mktime() in the code. There is no workaround available for 7.2.X, and I don't see that anyone backpatched it to 7.2 CVS. However, we are considering a 7.2.3 and a backpatch of that fix may be worthwhile. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
Bruce Momjian <pgman@candle.pha.pa.us> wrote: > > The change was to use localtime() rather than mktime() in the code. > There is no workaround available for 7.2.X, and I don't see that > anyone backpatched it to 7.2 CVS. However, we are considering a > 7.2.3 and a backpatch of that fix may be worthwhile. > That would be excellent, because it feels awkward installing stuff that doesn't pass the regression tests, as all our newlinux boxes will be rh7.3. But right now in our apps we're not relying on the time being right (isn't that the issue?) only the years... If it's a simple fix, i think we should include that in the next 7.2.X . Magnus -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Programmer/Networker [|] Magnus Naeslund -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-