Your message dated Sun, 4 Apr 2010 15:51:56 +0200
with message-id <[email protected]>
and subject line Calendar file fixed
has caused the Debian Bug report #278843,
regarding bsdmainutils: [calendar] Incorrect date for US Election Day reported
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
278843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278843
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bsdmainutils
Version: 6.0.16
Severity: important
I use the bsdmainutils /usr/bin/calendar for scheduling on my server, and have
my PROMPTCOMMAND set to run calendar to remind me of the day's events. I also
have a cron job run nightly to mail me the week's events, so that I can see
upcoming deadlines.
This morning I received the following report:
From: Reminder Service <[email protected]>
To: [email protected]
Subject: Friday's Calendar
Date: Fri, 29 Oct 2004 06:25:07 -0700
X-Bogosity: No, tests=bogofilter, spamicity=0.500000, version=0.92.8
Oct 31* Daylight Savings Time ends in USA; clocks move back (Last Sunday in
October)
Oct 31 All Hallows Eve (Halloween)
Oct 31* SUNDAY FUNDAY
Nov 01 N: Japanese History Essay 1 due
Nov 05* Election Day in USA (1st Tuesday after 1st Monday for even years)
Now you can see that I have a goofy test entry for each Sunday, and a genuine
entry for 1 Nov. And I use "#include <calendar.usholiday>". However,
Election day in the USA is 2 November 2004, not 5 November! 5 November is a
Friday, and doesn't even match the comment in parentheses!
I looked in /usr/share/calendar/calendar.usholiday and see:
11/05* Election Day in USA (1st Tuesday after 1st Monday for even years)
It appears to be hard-coded! This would have been correct for 2002.
Using TueFirst would probably be more resistant to lack of change than simply
hard-coding it every two years. I tried doing MonFirst+1, but that syntax only
seems to work for Easter, which I find odd.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=en_US, LC_CTYPE=ja_JP.UTF-8
Versions of packages bsdmainutils depends on:
ii bsdutils 1:2.12-10 Basic utilities from 4.4BSD-Lite
ii debconf [debconf-2.0] 1.4.30.8 Debian configuration management sy
ii debianutils 2.8.4 Miscellaneous utilities specific t
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libncurses5 5.4-4 Shared libraries for terminal hand
-- debconf information:
bsdmainutils/calendar_lib_is_not_empty:
bsdmainutils/calendar_config_moved:
--- End Message ---
--- Begin Message ---
Well as far as possible. It now lists TueFirst which is the best approximation
we can get with the syntax possible. Therefore I think we can safely close this
bug report.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber [email protected]
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
--- End Message ---
