Package: gtimelog
Version: 0.0+svn65-1debian2
Severity: normal
Setting hours to a non integer value in .gtimelog/gtimelogrc (for the
'length' of the working day) causes gtimelog to fail to start:
Traceback (most recent call last):
File "/usr/bin/gtimelog", line 1223, in ?
main()
File "/usr/bin/gtimelog", line 1207, in main
settings.load(settings_file)
File "/usr/bin/gtimelog", line 605, in load
self.hours = config.getint('gtimelog', 'hours')
File "/usr/lib/python2.4/ConfigParser.py", line 321, in getint
return self._get(section, int, option)
File "/usr/lib/python2.4/ConfigParser.py", line 318, in _get
return conv(self.get(section, option))
ValueError: invalid literal for int(): 7.5
This bug is possibly wishlist, depending on the maintainer's view on how
important non-integer working day hours are :)
Cheers,
Neil
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages gtimelog depends on:
ii python 2.4.4-2 An interactive high-level object-o
ii python-glade2 2.8.6-8 GTK+ bindings: Glade support
ii python-gtk2 2.8.6-8 Python bindings for the GTK+ widge
ii vim-gnome 1:7.0-122+1etch3 Vi IMproved - enhanced vi editor -
gtimelog recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
