Package: remind
Version: 03.01.05-2
Severity: important

Previous versions of remind had no ''rem'' command on Debian. There was 
only ''remind''. According to the current changelog.Debian.gz this was
changed.

''remind'' previously assumed a default file ~/.reminders whereas the 
current version of ''remind'' does not. Hence, previously used command 
lines using ''remind'' cannot be used anymore. Assumingly, this affects 
also depending packages and third-party programs such as wxRemind.

In general, it should be sufficient to now use ''rem'' instead of 
''remind'' as the current package ships with a symbolic link ''rem'' 
pointing to ''remind''.

I would suggest some README.Debian file or a warning shown when 
installing or updating the package.

Sample of a shell session:

  [EMAIL PROTECTED]:~$ remind  
  REMIND 03.01.05 (English version) Copyright 1992-1998 David F. Skoll
  Copyright 1999-2008 Roaring Penguin Software Inc.
  Usage: remind [options] filename [date] [time] [*rep]
  Options:
   -n     Output next occurrence of reminders in simple format
  (...)

  [EMAIL PROTECTED]:~$ remind ~/.reminders
  Reminders for Sunday, 16th November, 2008 (today):
  (...)

  [EMAIL PROTECTED]:~$ rem
  Reminders for Sunday, 16th November, 2008 (today):
  (...)


-- System Information:
Debian Release: lenny/sid
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages remind depends on:
ii  libc6                         2.7-15     GNU C Library: Shared libraries

remind recommends no packages.

Versions of packages remind suggests:
pn  tkremind                      <none>     (no description available)
pn  wyrd                          <none>     (no description available)

-- no debconf information




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to