Bug#780685: /usr/bin/crontab: Should display error message when crontab doesn't exist yet

[Oxan van Leeuwen]

Package: systemd-cron
Version: 1.3.1+ds1-2
Severity: normal

If the crontab for your user doesn't exit and you run crontab -l, a Python 
stacktrace is produced instead of a user-friendly error message.

Traceback (most recent call last):
  File "/usr/bin/crontab", line 94, in <module>
    action(cron_file, args)
  File "/usr/bin/crontab", line 55, in list
    with open(cron_file, 'r') as f:
IOError: [Errno 2] No such file or directory: '/var/spool/cron/crontabs/oxan'

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (920, 'testing'), (910, 'stable'), (900, 'testing-proposed-updates'), (525, 'unstable'), (515, 'experimental'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.18.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-cron depends on:
ii  init-system-helpers  1.22
ii  python               2.7.8-4
pn  python:any           <none>
ii  systemd-sysv         215-12

systemd-cron recommends no packages.

systemd-cron suggests no packages.

-- no debconf information