bin/155873: calendar recurring date not working
Jaakko Heinonen
jh at FreeBSD.org
Tue Jun 7 16:20:09 UTC 2011
The following reply was made to PR bin/155873; it has been noted by GNATS.
From: Jaakko Heinonen <jh at FreeBSD.org>
To: edwin at FreeBSD.org
Cc: Ivana Belgers <ivana at giga.giga.nl>, bug-followup at FreeBSD.org
Subject: Re: bin/155873: calendar recurring date not working
Date: Tue, 7 Jun 2011 19:18:06 +0300
On 2011-06-06, Jaakko Heinonen wrote:
> On 2011-03-22, Ivana Belgers wrote:
> > Until recently the following line in the .calendar file
> > delivered the expected result:
> > sat+3 Every third saturday of each month
> >
> > This worked in 8.1-STABLE installed on 2 august 2010.
> > Now, since we upgraded to 8.2-STABLE on march 25, this does not work
> > anymore, but generates the following message:
> > % calendar
> > Unprocessed:
> > -------
> > date: |Sat+3|
> > flags: 10a - dayofweek modifierindex variable
> > modifierindex: |+3|
> > dayofweek: |Sat| (6)
> > Ignored: Sat+3 Every third saturday of each month
>
> Seems that the behavior changed in r205821:
>
> ------------------------------------------------------------------------
> r205821 | edwin | 2010-03-29 09:49:20 +0300 (Mon, 29 Mar 2010) | 12 lines
>
> Long awaited update to the calendar system:
>
> - Repeating events which span multiple years (because of -A, -B or
> just the three days before the end of the year).
>
> - Support for lunar events (full moon, new moon) and solar events
> (equinox and solstice, chinese new year). Because of this, the
> options -U (UTC offset) and -l (longitude) are available to
> compensate if reality doesn't match the calculated values.
>
> MFC after: 1 month
>
> ------------------------------------------------------------------------
Looking at the code I can confirm that r205821 broke this. The new
function indextooffset() doesn't parse correctly modifierindexes such as
+3 and -3.
--
Jaakko
More information about the freebsd-bugs
mailing list