the new tarball contains a ~ backup file, can it still be removed, it makes the diff hard to review?
lintian4python also reports following: e: wakeup: pyflakes-undefined-name usr/bin/wakeup-settings:529: pluginPref e: wakeup: pyflakes-undefined-name usr/bin/wakeup-settings:535: pluginPref e: wakeup: pyflakes-undefined-name usr/share/wakeup/alarm.py:36: prop e: wakeup: pyflakes-import-shadowed-by-loop-var usr/share/wakeup/setnextalarm.py:37: alarm line 13
the first three look like real bugs, the last is probably just a potential future bug.
the new tarball contains a ~ backup file, can it still be removed, it makes the diff hard to review?
lintian4python also reports following: undefined- name usr/bin/ wakeup- settings: 529: pluginPref undefined- name usr/bin/ wakeup- settings: 535: pluginPref undefined- name usr/share/ wakeup/ alarm.py: 36: prop import- shadowed- by-loop- var usr/share/ wakeup/ setnextalarm. py:37: alarm line 13
e: wakeup: pyflakes-
e: wakeup: pyflakes-
e: wakeup: pyflakes-
e: wakeup: pyflakes-
the first three look like real bugs, the last is probably just a potential future bug.