New Upstream Release - python-imaplib2
More details
Historical runs
- quilt-patch-out-of-date: Quilt patch Do-not-use-TIMEOUT_MAX.patch no longer applies
- quilt-patch-out-of-date: Quilt patch Do-not-use-TIMEOUT_MAX.patch no longer applies
- quilt-refresh-error: An error occurred refreshing quilt patch Do-not-use-TIMEOUT_MAX.patch: Applying patch debian/patches/Do-not-use-TIMEOUT_MAX.patch can't find file to patch at input line 21 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |From: Ilias Tsitsimpis <iliastsi@debian.org> |Date: Sat, 25 Aug 2018 09:43:41 +0300 |Subject: Do not use TIMEOUT_MAX | |On some architectures, using threading.TIMEOUT_MAX for the timeout |parameter can overflow causing Condition.wait() to return immediately. |Instead of relying on TIMEOUT_MAX, remove it and wait forever. | |Bug-Debian: https://bugs.debian.org/899102 |Bug: https://github.com/imaplib2/imaplib2/issues/3 |Forwarded: https://github.com/imaplib2/imaplib2/pull/4 |--- | imaplib2.py | 5 ++--- | imaplib2.py3 | 4 ++-- | 2 files changed, 4 insertions(+), 5 deletions(-) | |diff --git a/imaplib2.py b/imaplib2.py |index 1fd47d2..3a8b6c0 100755 |--- a/imaplib2.py |+++ b/imaplib2.py -------------------------- No file to patch. Skipping patch. 3 out of 3 hunks ignored can't find file to patch at input line 51 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/imaplib2.py3 b/imaplib2.py3 |index 0aeff4d..e02f094 100755 |--- a/imaplib2.py3 |+++ b/imaplib2.py3 -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored Patch debian/patches/Do-not-use-TIMEOUT_MAX.patch does not apply (enforce with -f)