Your message dated Tue, 14 Apr 2020 02:53:20 +0000
with message-id <e1jobhq-000goh...@fasolo.debian.org>
and subject line Bug#956644: Removed package(s) from unstable
has caused the Debian Bug report #630525,
regarding please ignore (configuration) caches for dnspython too
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 ow...@bugs.debian.org
immediately.)


-- 
630525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-xmpp
Version: 0.4.1-cvs20080505.2
Severity: important
Tags: upstream patch

Hi,

while using Rene's great dvcs-autosync, I stumbled over a bug in xmpppy (which
dvcs-autosync uses inderectly through python-jabberbot, both authors CC'ed).

I've booted my machine at the university and also started dvcs-autosync there.
At this time my /etc/resolv.conf contained 192.168.10.1 as the only available
nameserver. After finishing work I sent my laptop to sleep and went home where
I resumed the laptop. After some time I accidenally looked at the console
dvcs-autosync was running in, and it was flooded with the following message:

 An error occurred while looking up _xmpp-client._tcp.example.com
 ERROR:jabberbot:unable to connect to server example.com.

I checked my WiFi, my resolver and all was fine, I could get SRV for
_xmpp-client._tcp.example.com without any problems, just not in the running
dvcs-autosync process. Then I realized the nameserver change, as the ns at home
is running on 192.168.0.1 and xmpppy was still trying to query 192.168.10.1.

A short look at the code and in the dnspython docs resulted in the attached
patch. Yes, it creates a new dns.resolver.Resolver object every time, but who
cares? :)

FIY: checked 0.5.0rc1, the problem ain't fixed there.

FIY2: marking as important as it affects every "long" running process on a
roaming machine, which should be pretty common in 2011 ;)

Regards
Evgeni

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-xmpp depends on:
ii  python                        2.6.6-14   interactive high-level object-orie
ii  python-central                0.6.17     register and build utility for Pyt

Versions of packages python-xmpp recommends:
ii  python-dnspython              1.8.0-1    DNS toolkit for Python

python-xmpp suggests no packages.

-- no debconf information
--- a/xmpp/transports.py        2011-06-14 20:56:48.426738823 +0200
+++ b/xmpp/transports.py        2011-06-14 21:07:57.900328939 +0200
@@ -77,7 +77,9 @@
             for query in possible_queries:
                 try:
                     if HAVE_DNSPYTHON:
-                        answers = [x for x in dns.resolver.query(query, 'SRV')]
+                        # new resolver, no cache of old configuration :)
+                        resolver = dns.resolver.Resolver()
+                        answers = [x for x in resolver.query(query, 'SRV')]
                         if answers:
                             host = str(answers[0].target)
                             port = int(answers[0].port)

--- End Message ---
--- Begin Message ---
Version: 0.4.1-cvs20080505.4+rm

Dear submitter,

as the package python-xmpp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/956644

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to