[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#20605: marked as done (plan: cannot properly handle DST)

Your message dated Fri, 13 Mar 2020 22:37:55 +0000
with message-id <E1jCswF-000FUQ-8k@fasolo.debian.org>
and subject line Bug#953738: Removed package(s) from unstable
has caused the Debian Bug report #13945,
regarding plan: cannot properly handle DST
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 owner@bugs.debian.org
immediately.)


-- 
13945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=13945
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: plan
Version: 1.6.1

This is probably to forward to upstream author, along with my other
reports.

2 problems:

* The setup dialog regarding DST settings cannot have plan use the
system's DST settings.  It should allow to use the libc interface to
local time (and NOT worry about TZ, this is libc's job), and make it
the default.  I hate having to go into this dialog each time we switch
DST, just because the dates for the switches are *not* fixed, they
change from year to year, and these changes are already recorded in
the system in a standard way.

* After the DST system-switch, I got one (monthly) periodic alarm 1
our too late (see above the reason, and please note it just made me
forget an apointment), and then NOTHING.  Ie., the 2 daily alarms I've
set didn't show until I restarted pland.  Really can't think of a
reason for this.

* In the .dayplan file, some dates (eg. expiration date for a periodic
alarm) are recorded as UNIX integer-date.  I don't think it's the
Right Thing (tm), as 1) the user most probably specified a
*local-time* as expiration date, so this will probably be an error,
because plan doesn't seem to use libc's localtime features, and 2) if
not taken care of (didn't look at the code to check this), it will
probably skip the last alarm after a DST switchon (eg. if the expiration
is set relative to GMT+1, and we switch to GMT+2, then the expiration
will trigger one hour before the alarm time, and tha alarm won't ring).

-- 
Yann Dirson  <ydirson@a2points.com>      | Stop making M$-Bill richer & richer,
alt-email:     <dirson@univ-mlv.fr>      |     support Debian GNU/Linux:
debian-email:   <dirson@debian.org>      |         more powerful, more stable !
http://www.a2points.com/homepage/3475232 | Check <http://www.debian.org/>

--- End Message ---
--- Begin Message --- 
Version: 1.10.1-6+rm

Dear submitter,

as the package plan has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/953738

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
Reply to: