[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#986673: marked as done (buster-pu: package python3-dnspython/1.16.0-1 -> 1.16.0-1deb10u1)

Your message dated Sat, 19 Jun 2021 10:56:39 +0100
with message-id <5c65c3ad2ac9b1b1f78bf73b1cf073041e619b51.camel@adam-barratt.org.uk>
and subject line Closing p-u requests for fixes included in 10.10 point release
has caused the Debian Bug report #986673,
regarding buster-pu: package python3-dnspython/1.16.0-1 -> 1.16.0-1deb10u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
986673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986673
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian.org@packages.debian.org
Usertags: pu

Dear stable release team,

This python library breaks creation of secondary zone in
Openstack's designate project included in buster.

This is known issue and already fixed in upstream.

Debian-Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986645
Upstream-Bug: https://github.com/rthalley/dnspython/issues/390
Upstream-Patch: https://github.com/nrhall/dnspython/commit/9403c1bdbdf562cb01ee492b207b1f26191976ca

Could you please approve upload to buster ?
Debdiff attached.

Cheers,

Michal Arbet (kevko)

diff -Nru dnspython-1.16.0/debian/changelog dnspython-1.16.0/debian/changelog
--- dnspython-1.16.0/debian/changelog	2018-12-23 02:13:05.000000000 +0100
+++ dnspython-1.16.0/debian/changelog	2021-04-08 19:09:26.000000000 +0200
@@ -1,3 +1,11 @@
+dnspython (1.16.0-1+deb10u1) buster; urgency=medium
+
+  * Team upload.
+  * d/patches: Add fix-do-not-compare-with-expiration-
+    if-None.patch from upstream (Closes: #986645)
+
+ -- Michal Arbet <michal.arbet@ultimum.io>  Thu, 08 Apr 2021 19:09:26 +0200
+
 dnspython (1.16.0-1) unstable; urgency=medium
 
   * Update debian/watch to use Github
diff -Nru dnspython-1.16.0/debian/patches/fix-do-not-compare-with-expiration-if-None.patch dnspython-1.16.0/debian/patches/fix-do-not-compare-with-expiration-if-None.patch
--- dnspython-1.16.0/debian/patches/fix-do-not-compare-with-expiration-if-None.patch	1970-01-01 01:00:00.000000000 +0100
+++ dnspython-1.16.0/debian/patches/fix-do-not-compare-with-expiration-if-None.patch	2021-04-08 19:08:31.000000000 +0200
@@ -0,0 +1,22 @@
+Description: When doing xfr, do not compare with
+ expiration if it is None.
+Author: Bob Halley <halley@dnspython.org>
+Date: Sun, 29 Sep 2019 13:39:41 -0700
+Origin: upstream, https://github.com/nrhall/dnspython/commit/9403c1bdbdf562cb01ee492b207b1f26191976ca
+Bug-Report: https://github.com/rthalley/dnspython/issues/390
+Last-Update: 2020-04-08
+
+diff --git a/dns/query.py b/dns/query.py
+index c0c517c..2a06c33 100644
+--- a/dns/query.py
++++ b/dns/query.py
+@@ -608,7 +608,8 @@ def xfr(where, zone, rdtype=dns.rdatatype.AXFR, rdclass=dns.rdataclass.IN,
+     first = True
+     while not done:
+         mexpiration = _compute_expiration(timeout)
+-        if mexpiration is None or mexpiration > expiration:
++        if mexpiration is None or \
++           (expiration is not None and mexpiration > expiration):
+             mexpiration = expiration
+         if use_udp:
+             _wait_for_readable(s, expiration)
diff -Nru dnspython-1.16.0/debian/patches/series dnspython-1.16.0/debian/patches/series
--- dnspython-1.16.0/debian/patches/series	1970-01-01 01:00:00.000000000 +0100
+++ dnspython-1.16.0/debian/patches/series	2021-04-08 19:08:49.000000000 +0200
@@ -0,0 +1 @@
+fix-do-not-compare-with-expiration-if-None.patch

--- End Message ---
--- Begin Message --- 
Package: release.debian.org
Version: 10.10

Hi,

Each of the updates referenced in these bugs was included in the 10.10
point release today.

Regards,

Adam

--- End Message ---
Reply to: