Package: bsdmainutils
Version: 8.0.10
Severity: normal
File: /usr/bin/calendar
Although 8.0.10 restored /etc/calendar/default, calendar never tries to
actually use it.
$ strace -e trace=file calendar
execve("/usr/bin/calendar", ["calendar"], [/* 33 vars */]) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/i686/cmov/libc.so.6", O_RDONLY) = 3
open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE) = 3
open("/etc/localtime", O_RDONLY) = 3
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
stat64("calendar", 0xbfee1c14) = -1 ENOENT (No such file or directory)
chdir("/home/jamessan") = 0
chdir(".calendar") = -1 ENOENT (No such file or directory)
calendar: no calendar file: ``calendar'' or ``~/.calendar/calendar''
This is due to a disconnect between the filename of the patch which adds
this functionality (calendar.diff) and the name being used in the series
file (calendars.diff).
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (499, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bsdmainutils depends on:
ii bsdutils 1:2.16.2-0 Basic utilities from 4.4BSD-Lite
ii debianutils 3.2.2 Miscellaneous utilities specific t
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libncurses5 5.7+20100313-2 shared libraries for terminal hand
bsdmainutils recommends no packages.
Versions of packages bsdmainutils suggests:
ii cpp 4:4.4.3-1 The GNU C preprocessor (cpp)
pn vacation <none> (no description available)
ii wamerican [wordlist] 6-3 American English dictionary words
ii whois 5.0.1 an intelligent whois client
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
