commit 9ea0013d1f2b04f1aa570aa042f2207867b35485 Author: David Steele <dsteele@gmail.com> Date: Mon Jul 24 12:37:31 2023 -0400 Make completion checking more compatible Topydo only flags a task as 'completed' if a completion date is detected. Make the field optional for completion checking. commit edb64419a7ff1dc72d906d0c036697dad3a264d5 Author: David Steele <dsteele@gmail.com> Date: Mon Aug 22 16:51:27 2022 -0400 Remove Python2 Build Deps commit 6d6a78804df22c6c587869dd6637d49f3a4d6e8b Author: root <root@bf0aeeb6f301> Date: Tue Mar 1 19:27:34 2022 +0000 Set upstream metadata fields: Bug-Database, Bug-Submit. Changes-By: lintian-brush Fixes: lintian: upstream-metadata-file-is-missing See-also: https://lintian.debian.org/tags/upstream-metadata-file-is-missing.html Fixes: lintian: upstream-metadata-missing-bug-tracking See-also: https://lintian.debian.org/tags/upstream-metadata-missing-bug-tracking.html commit 1ae5281e76a46f8b6f9540e4b193549a06d9df86 Author: David Steele <steele@debian.org> Date: Mon Dec 27 10:37:08 2021 -0500 Add debhelper-compat back in commit a4850deb6d255a99a4de83fd30cc3d5d201d0643 Author: David Steele <steele@debian.org> Date: Mon Dec 27 10:30:03 2021 -0500 Drop Python 3.2 support Resolve build conflict with get_terminal_size(). There was code supporting 3.2 comppatibility, which caused some current build problems. Drop support for that workaround. commit b1f8cc613706b634cfe1a21dd19aefa8b22861e5 Author: David Steele <dsteele@gmail.com> Date: Thu Oct 7 12:12:40 2021 -0400 Revert "Remove the auto-due date on recurred tasks" This reverts commit d500bdb4ec16e5106ac811ebbefc849bf2cbfc63. It turns out that recurrance "+" revisions are based on the due date. No due date, update is based on completion. Bummer commit d500bdb4ec16e5106ac811ebbefc849bf2cbfc63 Author: David Steele <steele@debian.org> Date: Wed Oct 6 10:24:59 2021 -0400 Remove the auto-due date on recurred tasks The due date was hard coded, and set to the same date as the threshold. This has a high likelihood of not meeting the user's expectations. Remove using a patch.
Among the 2 debian patches available in version 0.14-5.2 of the package, we noticed the following issues: