GNU bug report logs - #48298
Invalid time specification: encode-time((0 30 11 1 1 0 nil -1 nil))

Previous Next

Full log

Message #63 received at control <at> debbugs.gnu.org (full text, mbox):

From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
To: Евгений Михайлов
 <lewwadoo <at> gmail.com>
Cc: 48298-done <at> debbugs.gnu.org
Subject: Re: bug#48298:
Date: Tue, 11 May 2021 22:37:48 +0100

tags 48298 - moreinfo
found 48298 27.1
close 48298 28.1
quit

Евгений Михайлов <lewwadoo <at> gmail.com> writes:

> вс, 9 мая 2021 г. в 11:54, Basil L. Contovounesios <contovob <at> tcd.ie>:
>
>  Eli Zaretskii <eliz <at> gnu.org> writes:
>
>  >> From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
>  >> Cc: Евгений Михайлов
>  >>  <lewwadoo <at> gmail.com>,  48298 <at> debbugs.gnu.org
>  >> Date: Sun, 09 May 2021 09:19:47 +0100
>  >>
>  >> > I guess the problem is in decoded-time-set-defaults, if anywhere.
>  >>
>  >> Lars?
>  >
>  > As the minimum fix, perhaps instead of using zero as the missing year
>  > we should use 1970, as zero could not be representable on some
>  > systems.
>
>  Also 1970 is implied by the function's docstring and announcement.
>
>  All tests seem to pass with this:
>
>  Evgeny, does that fix the error that you see?
>
> It does! (encode-time '(0 30 11 1 1 1970 nil -1 nil)) yielded (0 30600). Thank you guys for your help!

Thanks for confirming.  I'm therefore closing this report.

-- 
Basil

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.